The present application is related to commonly-owned U.S. patent application Ser. No. 14/715,486, filed on May 18, 2015; U.S. patent application Ser. No. 13/970,606, filed on Aug. 20, 2013, now U.S. Pat. No. 9,606,907; U.S. patent application Ser. No. 12/504,131, filed on Jul. 16, 2009, now U.S. Pat. No. 8,417,870; U.S. patent application Ser. No. 12/761,179, filed on Apr. 15, 2010, now U.S. Pat. No. 8,516,185; U.S. patent application Ser. No. 13/287,042, filed on Nov. 1, 2011, now U.S. Pat. No. 8,756,364; and U.S. patent application Ser. No. 13/287,081, filed on Nov. 1, 2011, now U.S. Pat. No. 8,516,188; each of which is incorporated herein by reference in its entirety.
The disclosure herein is related generally to memory modules, and more particularly to multi-rank memory modules and methods 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 “x64” or “by 64” organization. Similarly, a memory module having 72-bit-wide ranks is described as having an “x72” 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 as 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 there is an equal length 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 devices (I.D.) 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 command signals and a set of module control signals in response to each memory command from the memory controller. The module command signals are transmitted by the module control device to the memory devices via module C/A signal lines, and the module control signals (referred sometimes herein as module control signals) are transmitted by the module control device to the buffer circuits via module control signal lines.
The buffer circuits are associated with respective groups of memory devices and are distributed across the memory module at positions corresponding to the respective groups of memory devices. Thus, during certain high speed operations, each module 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 select a subgroup in the respective group of memory devices to communicate data with the memory controller in response to the module control signals. Thus, the memory module can have more ranks of memory devices than what is supported by the memory controller.
In one embodiment, each buffer circuit includes metastability detection circuits to detect metastability condition in the module control signals and signal adjustment circuits to adjust the module control signals and/or a module clock signal to mitigate any metastability condition in the module control signals.
Further, in one embodiment, each buffer circuit includes signal alignment circuits that determine, during a write operation, a time interval between a time when one or more module control signals are received from the module control circuit and a time when a strobe or data signal is received from the memory controller. This time interval is used during a subsequent read operation to time transmission of read data to the memory controller, such that the read data arrives at the memory controller within a time limit in accordance with a read latency parameter associated with the memory system.
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. Additionally, in one embodiment, each memory module 110 may include a dual in-line memory module (DIMM).
Referring to
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 Strove (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 command signals include, but are not limited to module/CS signals, which 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; 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 command signals may also include the module clock signal CK.
Examples of module control signals include, but are not limited to a mode signal (MODE), which specifies a mode of operation (e.g., test mode or operating mode) for the isolation devices 118; one or more enable signals, which are used by an isolation device to select one or more subgroups of memory devices to communicate data with the memory controller; and one or more ODT signals, which are used by the isolation devices to set up on-die termination for the data/strobe signals. In one embodiment, the module control signals are transmitted to the isolation devices 118 via respective module control signal lines 230. Alternatively, the module control signals can be packetized before being transmitted to the isolation devices 118 via the module control signal lines and decoded/processed at the isolation devices.
Module control device 116 transmits the module command signals to the memory devices 112 via module C/A signal lines 220. The memory devices 112 operate in response to the module command signals to receive write data or output read data as if the module command signals were from a memory controller. The module control device transmits the module control signals together with the module clock signal CK to the isolation devices 118 via module control signal lines 230. As shown in
As shown n
As shown, the isolation devices 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, isolation device ID-1 among the isolation devices 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, isolation devices ID-i among the isolation devices 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.
In one embodiment, each group or sets of memory devices are coupled to the associated isolation device 118 via a set of module data/strobe lines 210. 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 isolation device 118 via a same set of module data/strobe lines 210 (as shown in
In one embodiment, the isolation devices 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 isolation device 118 is configured to select a subgroup in the respective group of memory devices to communicate data with the MCH 101 in response to the module control signals, such that the memory module can include more ranks than what is supported by the MCH 101. Further, each isolation devices 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 isolation devices 118 are distributed across the memory module 110 or the module board 119 in positions corresponding to the respective groups of memory devices. For example, isolation device ID-1 is disposed in a first position corresponding to the first group of memory devices M11, M12, M13, and M14, and isolation device ID-i is disposed in an ith position separate from the first position and corresponding to the ith group of memory devices Mi1, Mi2, Mi3, and Mi4. In one embodiment, the first position is between the first group of memory devices and an edge 201 of the module board 119 where connections (not shown) to the data/strobe signal lines 130 are placed, and ith position is between the ith group of memory devices and the edge 201 of the module board 119. In one embodiment, the isolation devices 118 are distributed along the edge 201 of the memory module 110. In one embodiment, each isolation device 118 is a separate integrated circuit device packaged either by itself or together with at least some of the respective group of memory devices. In one embodiment, the module data/strobe signal lines 210, the module C/A signal lines 220, and the module control signal lines 230 include signal traces formed on and/or in the module board 119.
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, input and output signals electrical and logical level control information for the control circuit 116, 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 corresponding 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 isolation devices 118 before being transmitted to the memory devices 112 by the isolation devices 118. On the other hand, read data and strobe signals from the memory devices are received and buffered by the isolation devices 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 isolation devices 118, and the system 100 depends on the isolation devices 118 to properly time the transmission of the read data and strobe signals to the MCH 101.
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, load reduction mechanism in the isolation devices 118 would provide a single data bus interface to the respective set of memory devices, which is hidden from the system memory controller 101. Thus, a long sequence of interface timing training may be required due to limited controllability of the system memory controller 101 over the interface between the memory devices 112 and the associated isolation devices 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 associated isolation devices 118 due to the distributed architecture of the memory module 110 can cause synchronization issues. As the speed of memory operation increase, data period can become very close to the signal propagation delay time. Thus, such issues cannot simply be addressed by pipelining the data paths, as variation of the signal propagation time through I/Os becomes a very significant portion of a data period.
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 isolation devices 118 are controlled by the module control signals from the module control circuit 116, which generates the module control signals according to the C/A signals received from the MCH. Thus, the module control signals need to be properly received by the isolation devices 118 to insure their proper operation. In one embodiment, the module control signals are transmitted together with the module clock signal CK, which is also 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 module control signals. Since the isolation devices 118 are distributed across the memory module, the module control signal lines 230 can stretch across the memory module 110, over a distance of several centimeters. As the module control signals travel over such a distance, they can become misaligned with the module clock signal, resulting in metastability in the received module control signals. Therefore, in one embodiment, the isolation circuits 118 includes metastability detection circuits to detect metastability condition in the module control signals and signal adjustment circuits to adjust the module control signals and/or the module clock signal to mitigate any metastability condition in the module control signals, as explained in further detail below.
Because the isolation devices 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 module control signals to travel along the module control signals lines 230 from the module control device 116 to the farthest positioned isolation devices 118, such as isolation device ID-1 and isolation device ID-(n−1) in the exemplary configuration shown in
With the isolation devices 118 receiving module control signals at different times across more than one clock cycle, the module control signals alone are not sufficient to time the transmission of read data signals to the MCH 101 from the isolation devices 118. In one embodiment, each isolation devices includes signal alignment circuits that determine, during a write operation, a time interval between a time when one or more module 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 during a subsequent read operation to time the transmission of read data to the MCH 101, such that the read data follows a read command by a read latency value associated with the system 100, 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 isolation device 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 isolation device 118 further includes an ID 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 ID control circuit 310 also receives the module clock signal CK and the module control signals via the module control signal lines 230, and outputs ID 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 module control signals, a delay signal 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 module control signals, as explained in more detail below.
In certain embodiments, the ID control circuit 310 also provides a delay signal DS, which is used by the DQ routing circuits 320 to align read data output by the isolation device 118 with read data output by the other isolation devices 118, as explained in further detail below. In certain embodiments, the ID control circuit 310 regenerates a clock signal from the module clock signal CK, which can have a programmable delay from the module clock signal. The regenerated clock signal is used as the clock signal CK0 and a clock signal CKM that is provided to the corresponding set of memory devices, as explained in more detail below.
The memory devices 112 are coupled to the isolation devices 118 via a same set of module data/strobe signal lines or 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 isolation devices 118 may be used in place of one of the memory devices 112, which has the same data width as that of the isolation devices. For example, as shown in
In another embodiment, as shown in
The strobe routing circuit 620 also buffers strobe signals received from either the MCH 101 or the memory devices 112, and output either a write strobe WDQS or read strobe RDQS to the DQ routing circuits 320. In one embodiment, the ID control circuit 310 further includes a delay control circuit 650 that receives one of the module control signals and either a data signal or a strobe signal and determines a delay amount to be used by the DQ routing circuit 320 and the strobe routing circuit 620. The delay amount is provided to the DQ routing circuit 320 and the strobe routing circuit in a delay signal DS.
In a receiver circuit 630, the respective MCS is received in accordance with the module clock signal CK0. In one embodiment, receiver circuit 630 samples the respective MCS using rising (or falling) edges of the module clock CK0. Since the isolation devices 118 are distributed across the memory module 110 at positions corresponding to the respective groups of memory devices, the module control signal lines 230 that carry the MCS to the isolation devices can stretch over a distance of more than 10 centimeters, as shown in
For example, a module control signal, like the MCS 810 shown in
In one embodiment, as shown in
The receiver circuit 630 further includes a signal selection circuit 920 that receives the module clock CK and the at least one delayed version of the module clock via signal lines 916. The signal selection circuit 920 also receives the corresponding MCS and the at least one delayed version of the corresponding MCS via signal lines 918. The signal selection circuit 920 selects a clock signal CK, from among the module clock CK and the at least one delayed version of the module clock based on one or more of the metastability indicators. The signal selection circuit 920 may also select an MCS signal MCS, from among the corresponding MCS and the at least one delayed version of the corresponding MCS based on at least one other metastability indicator.
The receiver circuit 630 further includes a sampler or register circuit 930 that samples the selected module control signal MCS, according to the selected clock signal CK, and outputs the sampled signal as the received module control signal, which is provided to the command processing circuit 640 for further processing (if needed) before being provided to the DQ routing circuits 320 and DQS routing circuit 620.
In one embodiment, Z1 is the result of a logic operation (e.g., an XNOR operation) on the sampled result, e.g., Z1=
On the other hand, where a metastability condition of insufficient set-up time occurs, Z1=0 and Z2=1, and CK1 is output from multiplexor 1071 while MCS0 is output from multiplexor 1072. Sampler 930 thus samples MCS0 according to the rising edges of CK1. Since CK1 is shifted from CK0 toward the right, more set-up time is provided to mitigate the metastability condition.
In the case when no metastability is detected, Z1=1 and Z2=1, and CK0 is output from multiplexor 1071 while MCS0 is output from multiplexor 1072. So, the unshifted module control signal is sampled according to the unshifted module clock signal.
As stated above, in certain embodiments, since the isolation devices 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 memory devices 112. Thus, conventional read/write leveling techniques are not sufficient for managing read/write data timing. In one embodiment, the isolation devices 118 includes signal alignment mechanism to time the transmission of read data signals based on timing information derived from a prior write operation, 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 isolation device 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 isolation device 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 ID control circuit 310, as shown in
The DQS routing circuit further includes a plurality of read paths 1450 that are selectable by the one or more of the module control signals. Output from the selected read path is delayed in a delay circuit 1460 by an amount controlled by the delay signal DS, and sampled by a sampler circuit 1470. The sampled read data/strobe is transmitted by transmitter 1480 onto the corresponding data/strobe signal line 322/324 via the DQ/DQS pin 1401.
The DQS routing circuit further includes a read strobe path coupled between the first DQS pin 1501 and a selected one of the second and third DQS pins 1502A and 1502B. In the read strobe path, a select circuit 1550 (e.g., a multiplexor) selects either a read strobe signal received via DQS pin 1502A or a read strobe signal received via DQS pin 1502B based on one or both of the enable signals ENA or ENB. The selected read strobe signal is delayed in a delay circuit 1560 by an amount controlled by the delay signal DS, and sampled by a sampler circuit 1570 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 1580 onto the corresponding strobe signal line 324 via the first DQS pin 1501.
The DQ routing circuit further includes a read data path coupled between the first DQ pin 1601 and a selected one of the second and third DQ pins 1602A and 1602B. In the read data path, a select circuit 1650 (e.g., a multiplexor) selects either a read data signal received via DQ pin 1602A or a read data signal received via DQ pin 1602B based on one or both of the enable signals ENA or ENB. The selected read data signal is delayed in a delay circuit 1660 by an amount controlled by the delay signal DS. The delayed read data signal is then sampled by a receiver circuit 1670 according to the read strobe RDQS from the DQS routing circuit 620, and transmitted by transmitter 1680 onto the corresponding data signal line 130 via the first DQ pin 1601.
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 a 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 isolation device 118. The time interval CED can be used by the isolation device 118 to properly time the transmission of read data to the MCH 101, as described above and explained further below.
As shown in
During a read operation, another set of module control signals including, for example, one or more second enable signals, are received by the isolation device 118 from the module controller 116 (1860). 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 isolation device 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 (1870). 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.
In certain embodiments, especially the embodiments shown in
The present application is a continuation of U.S. patent application Ser. No. 15/820,076, filed Nov. 21, 2017, which is a continuation of U.S. patent application Ser. No. 15/426,064, filed Feb. 7, 2017 (U.S. Pat. No. 9,824,035), which is a continuation of U.S. patent application Ser. No. 14/846,993, filed Sep. 7, 2015 (U.S. Pat. No. 9,563,587), which is a continuation of U.S. patent application Ser. No. 13/952,599, filed Jul. 27, 2013, (U.S. Pat. No. 9,128,632), which claims priority to U.S. Provisional Pat. Appl. No. 61/676,883, filed on Jul. 27, 2012. Each of the above applications is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4368515 | Nielsen | Jan 1983 | A |
4392212 | Miyasaka et al. | Jul 1983 | A |
4571676 | Mantellina et al. | Feb 1986 | A |
4592011 | Mantellina et al. | May 1986 | A |
4633429 | Lewandowski et al. | Dec 1986 | A |
4670748 | Williams | Jun 1987 | A |
4706214 | Kassai | Nov 1987 | A |
4739473 | Ng | Apr 1988 | A |
4866603 | Chiba | Sep 1989 | A |
4958322 | Kosugi et al. | Sep 1990 | A |
4961172 | Shubat et al. | Oct 1990 | A |
4961204 | Tanaka et al. | Oct 1990 | A |
4980850 | Morgan | Dec 1990 | A |
5060188 | Zulian et al. | Oct 1991 | A |
5247643 | Shottan | Sep 1993 | A |
5272664 | Alexander et al. | Dec 1993 | A |
5313624 | Harriman | May 1994 | A |
5345412 | Shiratsuchi | Sep 1994 | A |
5357478 | Kikuda et al. | Oct 1994 | A |
5388072 | Matick et al. | Feb 1995 | A |
5388240 | Olderdissen et al. | Feb 1995 | A |
5392252 | Rimpo et al. | Feb 1995 | A |
5426753 | Moon | Jun 1995 | A |
5463590 | Watanabe | Oct 1995 | A |
5483497 | Mochizuki et al. | Jan 1996 | A |
5485589 | Kocis et al. | Jan 1996 | A |
5495435 | Sugahara | Feb 1996 | A |
5513135 | Dell et al. | Apr 1996 | A |
5532954 | Bechtolsheim et al. | Jul 1996 | A |
5537584 | Miyai et al. | Jul 1996 | A |
5541448 | Carpenter | Jul 1996 | A |
5572691 | Koudmani | Nov 1996 | A |
5581498 | Ludwig et al. | Dec 1996 | A |
5590071 | Kolor et al. | Dec 1996 | A |
5602999 | Hyatt | Feb 1997 | A |
5617559 | Le et al. | Apr 1997 | A |
5630096 | Zuravleff | May 1997 | A |
5638534 | Mote, Jr. | Jun 1997 | A |
5655113 | Le et al. | Aug 1997 | A |
5655153 | Leung | Aug 1997 | A |
5696917 | Sandorfi | Dec 1997 | A |
5699542 | Mehta et al. | Dec 1997 | A |
5702984 | Bertin et al. | Dec 1997 | A |
5703826 | Hush et al. | Dec 1997 | A |
5717851 | Yishay et al. | Feb 1998 | A |
5724604 | Moyer | Mar 1998 | A |
5729716 | Connolly et al. | Mar 1998 | A |
5745914 | Lee et al. | Apr 1998 | A |
5764590 | Iwamoto et al. | Jun 1998 | A |
5784705 | Leung | Jul 1998 | A |
5802395 | Connolly et al. | Sep 1998 | A |
5802541 | Reed | Sep 1998 | A |
5805520 | Anglada et al. | Sep 1998 | A |
5822251 | Bruce et al. | Oct 1998 | A |
5905401 | Sher | May 1999 | A |
RE36229 | Cady | Jun 1999 | E |
5909388 | Mueller | Jun 1999 | A |
5926827 | Dell et al. | Jul 1999 | A |
5926839 | Katayama | Jul 1999 | A |
5953215 | Karabatsos | Sep 1999 | A |
5953280 | Watsui | Sep 1999 | A |
5958025 | Sonobe | Sep 1999 | A |
5959930 | Sakurai | Sep 1999 | A |
5963464 | Dell et al. | Oct 1999 | A |
5966736 | Gittinger et al. | Oct 1999 | A |
5973392 | Senba et al. | Oct 1999 | A |
5974493 | Okumura et al. | Oct 1999 | A |
6011710 | Wieggers | Jan 2000 | A |
6018787 | Ip | Jan 2000 | A |
6044032 | Li | Mar 2000 | A |
6061754 | Cepulis | May 2000 | A |
6070217 | Connolly et al. | May 2000 | A |
6070227 | Rokicki | May 2000 | A |
6097652 | Roh | Aug 2000 | A |
6108745 | Gupta et al. | Aug 2000 | A |
6115278 | Deneroff et al. | Sep 2000 | A |
6134638 | Olarig et al. | Oct 2000 | A |
6141245 | Bertin | Oct 2000 | A |
6151271 | Lee | Nov 2000 | A |
6154418 | Li | Nov 2000 | A |
6154419 | Shakkarwar | Nov 2000 | A |
6173357 | Ju | Jan 2001 | B1 |
6185654 | Van Doren | Feb 2001 | B1 |
6188641 | Uchida | Feb 2001 | B1 |
6205516 | Usami | Mar 2001 | B1 |
6209074 | Dell et al. | Mar 2001 | B1 |
6223650 | Johnson | May 2001 | B1 |
6226709 | Goodwin et al. | May 2001 | B1 |
6226736 | Niot | May 2001 | B1 |
6247088 | Seo et al. | Jun 2001 | B1 |
6260127 | Olarig et al. | Jul 2001 | B1 |
6262938 | Lee | Jul 2001 | B1 |
6317352 | Halbert et al. | Nov 2001 | B1 |
6349051 | Klein | Feb 2002 | B1 |
6381140 | Liao | Apr 2002 | B1 |
6400637 | Akamatsu et al. | Jun 2002 | B1 |
6408356 | Dell | Jun 2002 | B1 |
6414868 | Wong et al. | Jul 2002 | B1 |
6415374 | Faue et al. | Jul 2002 | B1 |
6438062 | Karabatsos | Aug 2002 | B1 |
6446158 | Dell et al. | Sep 2002 | B1 |
6446184 | Yuan et al. | Sep 2002 | B2 |
6453381 | Kolor et al. | Sep 2002 | B1 |
6470417 | Tokutome et al. | Oct 2002 | B1 |
6487102 | Halbert et al. | Nov 2002 | B1 |
6502161 | Perego et al. | Dec 2002 | B1 |
6518794 | Coteus et al. | Feb 2003 | B2 |
6526473 | Kim | Feb 2003 | B1 |
6530007 | Olarig et al. | Mar 2003 | B2 |
6530033 | Raynham et al. | Mar 2003 | B1 |
6546476 | Gillingham | Apr 2003 | B1 |
6553449 | Dodd et al. | Apr 2003 | B1 |
6553450 | Dodd et al. | Apr 2003 | B1 |
6618320 | Hasegawa et al. | Sep 2003 | B2 |
6618791 | Dodd et al. | Sep 2003 | B1 |
6621496 | Ryan | Sep 2003 | B1 |
6625081 | Roohparvar et al. | Sep 2003 | B2 |
6625687 | Halbert et al. | Sep 2003 | B1 |
6636446 | Lee | Oct 2003 | B2 |
6636935 | Ware et al. | Oct 2003 | B1 |
6646949 | Ellis et al. | Nov 2003 | B1 |
6658509 | Bonella et al. | Dec 2003 | B1 |
6674684 | Shen | Jan 2004 | B1 |
6681301 | Mehta et al. | Jan 2004 | B1 |
6683372 | Wong et al. | Jan 2004 | B1 |
6697888 | Halbert et al. | Feb 2004 | B1 |
6704910 | Hong | Mar 2004 | B2 |
6705877 | Li et al. | Mar 2004 | B1 |
6717855 | Underwood | Apr 2004 | B2 |
6717885 | Lai | Apr 2004 | B2 |
6721843 | Estakhri | Apr 2004 | B1 |
6721860 | Klein | Apr 2004 | B2 |
6728150 | LaBerge | Apr 2004 | B2 |
6738880 | Lai et al. | May 2004 | B2 |
6742098 | Halbert et al. | May 2004 | B1 |
6747887 | Halbert et al. | Jun 2004 | B2 |
6754746 | Leung et al. | Jun 2004 | B1 |
6754797 | Wu et al. | Jun 2004 | B2 |
6785189 | Jacobs et al. | Aug 2004 | B2 |
6788592 | Nakata et al. | Sep 2004 | B2 |
6799252 | Bauman | Sep 2004 | B1 |
6807125 | Coteus et al. | Oct 2004 | B2 |
6807650 | Lamb et al. | Oct 2004 | B2 |
6813196 | Park et al. | Nov 2004 | B2 |
6832303 | Tanaka | Dec 2004 | B2 |
6834014 | Yoo et al. | Dec 2004 | B2 |
6854042 | Karabatsos | Feb 2005 | B1 |
6880094 | La Berge | Apr 2005 | B2 |
6889304 | Perego et al. | May 2005 | B2 |
6912615 | Nicolai | Jun 2005 | B2 |
6912628 | Wicki et al. | Jun 2005 | B2 |
6925028 | Hosokawa et al. | Aug 2005 | B2 |
6944694 | Pax | Sep 2005 | B2 |
6948084 | Manapat et al. | Sep 2005 | B1 |
6950366 | Lapidus et al. | Sep 2005 | B1 |
6954281 | Fukuda et al. | Oct 2005 | B2 |
6961281 | Wong et al. | Nov 2005 | B2 |
6981089 | Dodd et al. | Dec 2005 | B2 |
6982892 | Lee et al. | Jan 2006 | B2 |
6982893 | Jakobs | Jan 2006 | B2 |
6990043 | Kuroda et al. | Jan 2006 | B2 |
6996686 | Doblar et al. | Feb 2006 | B2 |
7007130 | Holman | Feb 2006 | B1 |
7007175 | Chang et al. | Feb 2006 | B2 |
7024518 | Halbert et al. | Apr 2006 | B2 |
7046538 | Kinsley et al. | May 2006 | B2 |
7047361 | Chong et al. | May 2006 | B2 |
7054179 | Cogdill et al. | May 2006 | B2 |
7065626 | Schumacher et al. | Jun 2006 | B2 |
7072231 | Pax | Jul 2006 | B2 |
7073041 | Dwyer et al. | Jul 2006 | B2 |
7078793 | Ruckerbauer et al. | Jul 2006 | B2 |
7093066 | Klein | Aug 2006 | B2 |
7120727 | Schumacher et al. | Oct 2006 | B2 |
7124260 | Lee et al. | Oct 2006 | B2 |
7127584 | La Berge et al. | Oct 2006 | B1 |
7130308 | Haddock et al. | Oct 2006 | B2 |
7130952 | Nanki et al. | Oct 2006 | B2 |
7133960 | Thompson et al. | Nov 2006 | B1 |
7133972 | Jeddeloh | Nov 2006 | B2 |
7142461 | Janzen | Nov 2006 | B2 |
7149841 | La Berge | Dec 2006 | B2 |
7167967 | Bungo et al. | Feb 2007 | B2 |
7181591 | Tsai | Mar 2007 | B2 |
7191302 | Usami | Apr 2007 | B2 |
7200021 | Radhuram | May 2007 | B2 |
7225303 | Choi | Jun 2007 | B2 |
7227910 | Lipka | Aug 2007 | B2 |
7254036 | Pauley et al. | Sep 2007 | B2 |
7266639 | Radhuram | Sep 2007 | B2 |
7272709 | Zitlaw et al. | Oct 2007 | B2 |
7281079 | Bains et al. | Oct 2007 | B2 |
7289386 | Bhakta et al. | Oct 2007 | B2 |
7334150 | Ruckerbauer et al. | Mar 2008 | B2 |
7346750 | Ishikawa | Apr 2008 | B2 |
7356639 | Perego et al. | May 2008 | B2 |
7370238 | Billick et al. | May 2008 | B2 |
7379361 | Co et al. | May 2008 | B2 |
7461182 | Fukushima et al. | May 2008 | B2 |
7433992 | Wong | Oct 2008 | B2 |
7437591 | Bains | Oct 2008 | B1 |
7464225 | Tsern | Dec 2008 | B2 |
7471538 | Hofstra | Dec 2008 | B2 |
7532537 | Solomon et al. | May 2009 | B2 |
7730254 | Risse | Jun 2010 | B2 |
7865674 | Gower et al. | Jan 2011 | B2 |
7884619 | Chong | Feb 2011 | B1 |
7916574 | Solomon et al. | Mar 2011 | B1 |
7990746 | Rajan | Aug 2011 | B2 |
8001434 | Lee et al. | Aug 2011 | B1 |
8089795 | Rajan | Jan 2012 | B2 |
8130560 | Rajan et al. | Mar 2012 | B1 |
8189328 | Kanapathippillai | May 2012 | B2 |
8214616 | Ware | Jul 2012 | B2 |
8233303 | Best | Jul 2012 | B2 |
8244971 | Rajan | Aug 2012 | B2 |
8335894 | Rajan | Dec 2012 | B1 |
8565033 | Manohararajah | Oct 2013 | B1 |
8654556 | Wu et al. | Feb 2014 | B2 |
8782350 | Lee et al. | Jul 2014 | B2 |
8856464 | Karamcheti | Oct 2014 | B2 |
8949519 | Rajan | Feb 2015 | B2 |
20010008006 | Klein | Jul 2001 | A1 |
20020038405 | Leddige | Mar 2002 | A1 |
20020039323 | Tokutome | Apr 2002 | A1 |
20020112119 | Halbert et al. | Aug 2002 | A1 |
20020122435 | Mundkur | Sep 2002 | A1 |
20030070052 | Lai | Apr 2003 | A1 |
20040098528 | Janzen | May 2004 | A1 |
20040105292 | Matsui | Jun 2004 | A1 |
20050010737 | Ware | Jan 2005 | A1 |
20050257109 | Averbuj | Nov 2005 | A1 |
20050281096 | Bhakta | Dec 2005 | A1 |
20060077731 | Ware | Apr 2006 | A1 |
20060117152 | Amidi et al. | Jun 2006 | A1 |
20060179206 | Brittain et al. | Aug 2006 | A1 |
20060233012 | Sekiguchi et al. | Oct 2006 | A1 |
20060259711 | Oh | Nov 2006 | A1 |
20060262586 | Solomon | Nov 2006 | A1 |
20060267172 | Nguyen et al. | Nov 2006 | A1 |
20060277355 | Ellsberry | Dec 2006 | A1 |
20070058409 | Hermann | Mar 2007 | A1 |
20070064462 | Matsui | Mar 2007 | A1 |
20070070669 | Tsern | Mar 2007 | A1 |
20070217559 | Stott | Sep 2007 | A1 |
20070293094 | Aekins | Dec 2007 | A1 |
20080025137 | Rajan et al. | Jan 2008 | A1 |
20080037412 | Geile | Feb 2008 | A1 |
20080046631 | Takaku et al. | Feb 2008 | A1 |
20080104352 | Talbot | May 2008 | A1 |
20080162790 | Jeon-Taek | Jul 2008 | A1 |
20090103387 | Shau | Apr 2009 | A1 |
20090198924 | Shaeffer et al. | Aug 2009 | A1 |
20090248969 | Wu | Oct 2009 | A1 |
20090296503 | Chu et al. | Dec 2009 | A1 |
20100070690 | Amer | Mar 2010 | A1 |
20100125681 | Patel | May 2010 | A1 |
20100228891 | Talbot | Sep 2010 | A1 |
20100271092 | Zerbe | Oct 2010 | A1 |
20110016250 | Lee et al. | Jan 2011 | A1 |
20110016269 | Lee | Jan 2011 | A1 |
20110085408 | Neubauer | Apr 2011 | A1 |
20120170389 | Kizer | Jul 2012 | A1 |
20120256639 | Pausini | Oct 2012 | A1 |
20140029370 | Koshizuka | Jan 2014 | A1 |
20140036607 | Koshizuka | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
1816570 | Aug 2007 | EP |
10-092169 | Apr 1998 | JP |
2000285674 | Oct 2000 | JP |
2000285674 | Oct 2000 | JP |
2000311485 | Nov 2000 | JP |
2000311485 | Nov 2000 | JP |
2002184176 | Jun 2002 | JP |
2002184176 | Jun 2002 | JP |
2003007963 | Jan 2003 | JP |
2003007963 | Jan 2003 | JP |
2008046989 | Feb 2008 | JP |
Entry |
---|
Lee, Office Action, U.S. Appl. No. 15/426,064, dated Jun. 2, 2017, 11 pgs. |
Lee, Notice of Allowance, U.S. Appl. No. 15/426,064, dated Sep. 21, 2017, 9 pgs. |
Lee, Notice of Allowance, U.S. Appl. No. 14/846,993, dated Sep. 23, 2016, 8 pgs. |
Lee, Office Action, U.S. Appl. No. 13/952,599, dated Jul. 31, 2014, 12 pgs. |
Lee, Notice of Allowance, U.S. Appl. No. 13/952,599, dated Apr. 23, 2015, 8 pgs. |
Lee, Notice of Allowance, U.S. Appl. No. 15/820,076, dated Jul. 3, 2018, 9 pgs. |
Notice of Allowance, U.S. Appl. No. 13/970,606, filed Aug. 20, 2013, dated Jun. 27, 2016. |
Non-Final Office Action, U.S. Appl. No. 13/970,606, filed Aug. 20, 2013, dated Nov. 23, 2015. |
Response to Non-Final Office Action, U.S. Appl. No. 13/970,606, filed Aug. 20, 2013, dated Mar. 23, 2016. |
U.S. Appl. No. 11/075,395, filed Mar. 7, 2005 Netlist Inc., Entire Prosecution History. |
U.S. Appl. No. 11/173,175, filed Jul. 1, 2005 Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 11/335,875, filed Jan. 19, 2006, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 11/862,931, filed Sep. 27, 2007 Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/408,652, filed Mar. 20, 2009, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/422,853, filed Apr. 13, 2009, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/422,925, filed Apr. 13, 2009, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/504,131, filed Jul. 16, 2009, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/577,682, filed Oct. 12, 2009, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/629,827, filed Dec. 2, 2009, Netlist Inc., Entire Prosecution History. |
U.S. Appl. No. 12/761,179, filed Apr. 15, 2010, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/912,623, filed Oct. 26, 2010, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/954,492, filed Nov. 24, 2010, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/955,711, filed Nov. 29, 2010, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 12/981,380, filed Dec. 29, 2010, Netlist Inc., Entire Prosecution History. |
U.S. Appl. No. 13/032,470, filed Feb. 22, 2011, Netlist Inc., Entire Prosecution History. |
U.S. Appl. No. 13/154,172, filed Jun. 6, 2011, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/183,253, filed Jul. 14, 2011, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/287,042, filed Nov. 1, 2011, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/287,081, filed Nov. 1, 2011, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/288,850, filed Nov. 3, 2011, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/411,344, filed Mar. 2, 201, Lee, Entire Prosecution. |
U.S. Appl. No. 13/411,344, filed Mar. 2, 2012, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/412,243, filed Mar. 5, 2012, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/473,413, filed May 16, 2012, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/745,790, filed Jan. 19, 2013, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/952,599, filed Jul. 27, 2013, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 13/970,606, filed Aug. 20, 20, Netlist, Entire Prosecution. |
U.S. Appl. No. 13/971,231, filed Aug. 20, 20, Netlist, Entire Prosecution. |
U.S. Appl. No. 13/971,231, filed Aug. 20, 2013, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 14/229,844, filed Mar. 29, 2014, Netlist, Inc., Entire Prosecution History. |
U.S. Appl. No. 14/229,844, Mar. 29, 20, Netlist, Entire Prosecution. |
U.S. Appl. No. 14/324,990, filed Jul. 7, 201, Netlist, Entire Prosecution. |
U.S. Appl. No. 14/337,168, filed Jul. 21, 20, Netlist, Entire Prosecution. |
Non-Final Office Action, U.S. Appl. No. 13/412,243, dated Jan. 2, 2014, 20 pages. |
Non-final office action, U.S. Appl. No. 13/288,850, dated Oct. 11, 2013, 24 pages. |
Non-final office action, U.S. Appl. No. 13/411,344, dated Dec. 31, 2013, 28 pages. |
Non-final office action, U.S. Appl. No. 13/473,413, dated Nov. 17, 2011, 46 pages. |
Response to non-final office action dated Oct. 14, 2013 for U.S. Appl. No. 13/288,850, filed Jan. 13, 2014, 15 pages. |
Response to non-final office action dated Dec. 31, 2013 for U.S. Appl. No. 13/411,344, filed Mar. 31, 2014, 12 pages. |
Patent Owner's Response to Office Action dated Nov. 13, 2012 for Reexamination Control Nos. 95/000,578; 95/000,579, and 95/001,339, filed Jan. 14, 2013, 96 pages. |
Patent Owner's Response to Office Action dated Dec. 19, 2012 for Reexamination Control No. 95/001,758, filed Mar. 19, 2013, 61 pages. |
Patent Owner's Response to Office Action dated Sep. 26, 2013 for Reexamination Control No. 95/001,758, filed Nov. 26, 2013, 85 pages. |
Third Party Requester's Comments after Non-Final Action dated Sep. 26, 2013 for Reexamination Control No. 95/001,758, filed Dec. 26, 2013,. |
Patent Owner's Appeal Brief for Reexamination Control Nos. 95/000,546 and 95/000,577, filed Oct. 2, 2013, 46 pages. |
Patent Trial and Appeal Board Decision on Appeal for Reexamination Control No. 95/001,337, mailed Jan. 16, 2014, 30 pages. |
Patent Trial and Appeal Board Decision on Appeal for Reexamination Control No. 95/001,381, mailed Jan. 16, 2014, 24 pages. |
Action Closing Prosecution mailed Mar. 27, 2014 for Reexamination Control No. 95/001,758, filed Sep. 14, 2011, 40 pages. |
Action Closing Prosecution mailed Mar. 27, 2014 for Reexamination Control No. 95/001,339, filed Jun. 8, 2010, 106 pages. |
Notice of Allowance, U.S. Appl. No. 12/504,131, dated Feb. 12, 2013, 52 pgs. |
Response to Non-Final Office Action dated Jan. 2, 2014, filed Apr. 2, 2004, for U.S. Appl. No. 13/287,042, filed Nov. 1, 2011, 12 pages. |
Non-Final Action Closing Prosecution dated Sep. 1, 2010, for Control No. 95/001,339, filed Apr. 10, 2010, 17 pages. |
Non-Final Action Closing Prosecution dated Jun. 21, 2011, for Control No. 95/001,381, filed Jun. 9, 2010, 34 pages. |
Non-Final Action Closing Prosecution dated Mar. 12, 2012, for Control No. 95/001,337, filed Apr. 19, 2010, 33 pages. |
Non-Final Action dated Aug. 27, 2010, for Control No. 95/000,546, filed May 11, 2010, 16 pages. |
Non-Final Action dated Sep. 8, 2010, for Control No. 95/001,381, filed Jun. 9, 2010, 17 pages. |
Non-Final Action dated Apr. 4, 2011, for Control No. 95/001,339, filed Apr. 20, 2010, 61 pages. (merged with 95/000,578 and 95/000,579). |
Non-Final Action dated Jun. 15, 2011, for Control No. 95/001,381, filed Jun. 9, 2010, 33 pages. |
Non-Final Action dated Sep. 27, 2011, for Control No. 95/001,337, filed Apr. 19, 2010, 19 pages. |
Non-Final Action dated Oct. 4, 2011, for Control No. 95/001,339, filed Apr. 20, 2010, 77 pages. (merged with 95/000,578 and 95/000,579). |
Non-Final Action dated Oct. 14, 2011, for Control No. 95/001,339, filed Apr. 30, 2010, 99 pages. (merged with 95/000,578 and 95/000,579). |
Non-Final Office Action dated Nov. 16, 2011, for U.S. Appl. No. 95/001,758, filed Sep. 14, 2011, 25 pages. |
Order Granting Request for Inter Partes Reexamination mailed Nov. 16, 2011, for U.S. Appl. No. 95/001,758, filed Sep. 14, 2011, 13 pages. |
Order Granting Request for Inter Partes Reexamination mailed Aug. 9, 2010, for Control No. 95/000,546, filed May 11, 2010, 22 pages. |
Order Granting Request for Inter Partes Reexamination mailed Aug. 27, 2010, for Control No. 95/001,337, filed Apr. 19, 2010, 21 pages. |
Order Granting Request for Inter Partes Reexamination mailed Sep. 1, 2010, for Control No. 95/001,339, filed Apr. 20, 2010, 14 pages. |
Order Granting Request for Inter Partes Reexamination mailed Sep. 8, 2010, for Control No. 95/000,381, filed Jun. 9, 2010, 21 pages. |
Order Granting Request for Inter Partes Reexamination mailed Jan. 14, 2011, for Control No. 95/000,579, filed Oct. 21, 2010, 12 pages. |
Order Granting Request for Inter Partes Reexamination mailed Jan. 18, 2011, for Control No. 95/000,577, filed Oct. 20, 2010, 17 pages. |
Right of appeal Notice mailed Feb. 7, 2012, for Control No. 95/001,381, 33 pages. |
Right of Appeal Notice mailed Jun. 22, 2012, for Control No. 95/001,337, filed Jun. 4, 2010, 34 pages. |
Number | Date | Country | |
---|---|---|---|
20190347220 A1 | Nov 2019 | US |
Number | Date | Country | |
---|---|---|---|
61676883 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15820076 | Nov 2017 | US |
Child | 16391151 | US | |
Parent | 15426064 | Feb 2017 | US |
Child | 15820076 | US | |
Parent | 14846993 | Sep 2015 | US |
Child | 15426064 | US | |
Parent | 13952599 | Jul 2013 | US |
Child | 14846993 | US |