Rambus Inc. v. Rea

527 F. App'x 902
CourtCourt of Appeals for the Federal Circuit
DecidedJune 28, 2013
Docket2012-1480
StatusUnpublished
Cited by1 cases

This text of 527 F. App'x 902 (Rambus Inc. v. Rea) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Rambus Inc. v. Rea, 527 F. App'x 902 (Fed. Cir. 2013).

Opinions

Opinion for the court filed by Chief Judge RADER.

Dissenting opinion filed by Circuit Judge WALLACH.

RADER, Chief Judge.

This appeal arises from an inter partes reexamination proceeding before the United States Patent and Trademark Office (PTO). The Board of Patent Appeals and Interferences (Board) affirmed the Examiner’s rejection of all 25 claims of U.S. Patent No. 7,287,109 (the '109 Patent) under 35 U.S.C. § 102(a). Because substantial evidence does not support the Board’s conclusion, this court reverses.

I.

The technology at issue involves methods of controlling a dynamic random access memory device (DRAM). Storing information in a DRAM is referred to as a “write” operation, and retrieving information from a DRAM is referred to as a “read” operation. Information is written to, or read from, a DRAM using a memory controller. For example, in a write operation, a memory controller transmits control information to the DRAM, which includes a write request and “address” information indicating where (by row and column) the data will be stored. The DRAM receives the control information and executes the write operation, ie., writes the data to the corresponding location. Data and control information are transferred between the memory controller and the DRAM through a set of lines called a “bus.”

Prior to 1990, DRAMs operated “asynchronously” to the memory controller— that is, read and write operations were not conducted with reference to a system clock. A DRAM would execute read/write operations as quickly as possible after receiving control information from the memory controller. Between the time the memory controller transmitted the control information and the time the DRAM executed the operation, the memory controller had to wait for the DRAM to complete internal preparatory functions. This interface between the memory controller and the DRAM rendered the bus unusable because it would freeze in a “wait state” where the memory controller could not perform any other functions until the read/ write operation was executed.

As processor speeds increased, DRAMs could not keep up, which created a bottleneck that diminished the advantages of faster processors. The 1990s, however, introduced the synchronous DRAM, which executed read/write operations with reference to a system clock. After the memory controller transmitted a read/write request to the DRAM, the DRAM would wait a pre-determined number of clock cycles before executing the operation. This clock function eliminated the “wait state” and enabled the memory controller to perform other tasks and send additional requests to other DRAMs while the operation was pending. This process became known as “interleaving.” This case features different methods of interleaving.

[904]*904II.

Rambus is the owner of the '109 Patent, entitled “Method of Controlling a Memory Device Having a Memory Core.” It claims priority to U.S. Patent Application No. 08/545,292, filed on October 19, 1995, by Richard M. Barth, et al. In 2009, the PTO granted NVIDIA Corporation’s request for inter partes reexamination of the '109 Patent. The Examiner rejected all 25 claims as anticipated by an earlier Rambus patent, U.S. Patent No. 6,584,037 (Farm-wald). The Board affirmed the rejection and Rambus sought rehearing. Meanwhile, Rambus and NVIDIA settled, and NVIDIA withdrew from the proceedings. The Board denied rehearing, and Rambus appealed to this court where the sole issue on appeal is whether substantial evidence supports the Board’s finding that the '109 Patent is anticipated by Farmwald.

The '109 Patent discloses and claims certain methods of controlling data transfers to and from a DRAM. As the Board found, the specification describes “at least two embodiments,” which the Board referred to as the “strobe” embodiment and the “non-strobe” embodiment. J.A. 3; see '109 Patent col. 10 11. 25-67. In both embodiments, a memory controller transmits a request packet to the DRAM. '109 Patent col. 10 11. 25-67. The request packet contains control information indicating whether the DRAM will perform a read or a write operation. J.A. 3-4.

In the strobe embodiment, the memory controller then transmits a separate “strobe signal” to the DRAM, which causes the DRAM to execute the operation immediately (with a minimal inherent delay). J.A. 4; '109 Patent col. 8 1. 63-col. 9 1. 7; '109 Patent col. 9 11. 41-46. As the Board noted, the benefit of this invention “stems from latency minimization, resulting in a relatively free data bus for. other data transfers — i.e., the command control information tells the [DRAM] to pre-fetch the desired data ... and the [DRAM] then waits for the strobe signal to send the data.” J.A. 4.

In the non-strobe embodiment, the memory controller “varies the timing of data transmission without use of the above-described strobe signal.” J.A. 5. Rather, “the [request] packet contains a delay value that indicates to the DRAM when the [operation should be executed] relative to the time at which the request packet is sent.” J.A. 4-5 (quoting '109 Patent col. 10 11. 52-60). For example, if the request packet contained a write request and a delay value of eight clock cycles, the DRAM would execute the write operation after eight clock cycles elapse. As the Board noted, the benefit here is that the “[memory] controller is able to dynamically adjust the operative interleave.” J.A. 6 (emphasis added).

III.

The Farmwald patent, titled “Memory Device which Samples Data after an Amount of Time Transpires,” likewise discloses and claims a method of controlling data transfers to and from a DRAM. As the Board found, Farmwald teaches using a memory controller to send a request packet to the DRAM, which contains control information specifying a read or write operation. J.A. 8. Farmwald’s request packet also contains a bit that selects an “access-time register” within the DRAM. J.A. 8; Farmwald col. 9 1. 54-col. 10 1. 1. The access-time registers are central to Farmwald’s invention.

Each of Farmwald’s DRAMs contains “access-time registers 173 which store a set of one or more delay times at which the device can or should be available to send or receive data.” Farmwald col. 6 11. 40-45. For example, one access-time reg[905]*905ister might contain a delay value of two system clock cycles, another four system clock cycles, and another eight, and so forth. The access-time registers “can be modified and preferably are set as part of an initialization sequence that occurs when the system is powered up or reset.” Farmwald col. 6 11. 45-47. In other words, the delay values are stored in the access-time registers on start-up, prior to the memory controller transmitting any request packets to the DRAM. J.A. 10998 (“Farmwald relies upon the previously received [delay] value signal.... ”).

As the Board found, Farmwald teaches that after the memory controller transmits a request packet to the DRAM, the DRAM will wait to execute the specified read/ write operation depending on which access-time register is selected by the bit in the request packet. J.A. 8; Farmwald col. 9 11. 28-25 (“The time after which a data block is driven onto the bus lines is selected from values stored in slave access-time registers.”). For example, if the request packet contains a bit that selects access-time register no. 4, and access-time register no.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Classen Immunotherapies, Inc. v. Biogen Idec
968 F. Supp. 2d 660 (D. Maryland, 2013)

Cite This Page — Counsel Stack

Bluebook (online)
527 F. App'x 902, Counsel Stack Legal Research, https://law.counselstack.com/opinion/rambus-inc-v-rea-cafc-2013.