throbber
Trials@uspto.gov
`Tel: 571-272-7822
`
`Paper 35
`Entered: May 19, 2016
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`SONY CORPORATION, SONY ELECTRONICS INC.,
`SONY MOBILE COMMUNICATIONS AB, and
`SONY MOBILE COMMUNICATIONS (USA) INC.,
`Petitioner,
`
`v.
`
`MEMORY INTEGRITY, LLC,
`Patent Owner.
`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`
`
`
`
`
`
`
`
`Before JENNIFER S. BISK, NEIL T. POWELL, and
`KERRY BEGLEY, Administrative Patent Judges.
`
`POWELL, Administrative Patent Judge.
`
`FINAL WRITTEN DECISION
`35 U.S.C. § 318(a) and 37 C.F.R. § 42.73
`
`
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`I. INTRODUCTION
`
`A. Background
`Sony Corporation, Sony Electronics Inc., Sony Mobile
`Communications AB, and Sony Mobile Communications (USA) Inc.
`(collectively, “Petitioner”) filed a Petition requesting an inter partes review
`of claims 1–3, 8, 11, 12, and 14–25 (the “challenged claims”) of U.S. Patent
`No. 7,296,121 B2 (Ex. 1001, “the ’121 patent”). Paper 1 (“Pet.”). On May
`21, 2015, we instituted a review (Paper 7, “Institution Decision” or “Inst.
`Dec.”) based upon Petitioner’s assertion that claims 19–24 are unpatentable
`under 35 U.S.C. § 103. Inst. Dec. 35.
`This is a Final Written Decision under 35 U.S.C. § 318(a) and
`37 C.F.R. § 42.73. For the reasons set forth below, Petitioner has shown by
`a preponderance of the evidence that claims 19–24 are unpatentable.
`
`B. Related Matters
`The parties indicate that the ’121 patent is the subject of several
`proceedings in the United States District Court for the District of Delaware.
`Pet. 1; Paper 4, 1–2. In addition, other petitions seeking inter partes review
`of the ’121 patent have been filed, including IPR2015-00159, IPR2015-
`00161, IPR2015-00163, IPR2015-00172, IPR2015-01353, and IPR2015-
`1376. Of these other proceedings at the Office, only IPR2015-00159 and
`IPR2015-00163 are ongoing.1
`
`
`1 IPR2015-01353 was terminated and the petitioner in that case was joined
`to IPR2015-00163. Similarly, IPR2015-01376 was terminated and the
`petitioner in that case was joined to IPR2015-00159.
`
`2
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`C. The Pending Grounds of Unpatentability
`We instituted inter partes review involving the following grounds of
`unpatentability:
`Reference(s)
`Ground
`24
`Koster2
`§ 103
`19–23
`Koster and Kuskin3
`§ 103
`Petitioner supports its challenge with declarations executed by
`Dr. Daniel J. Sorin on November 3, 2014 (Ex. 1013) and on November 28,
`2015 (Ex. 1015). Patent Owner relies on a declaration executed by Dr.
`Vojin Oklobdzija on August 11, 2015 (Ex. 2016).
`
`Challenged Claims
`
`D. The ’121 Patent
`The ’121 patent relates to accessing data in computer systems that
`include more than one processor. Ex. 1001, 1:23–24. Specifically, the
`’121 patent discusses multiple processor systems with a point-to-point
`architecture—a cluster of individual processors (also referred to as
`processing nodes) that are directly connected to each other through point-to-
`point links, each with an associated cache memory. Id. at 4:38–40. To
`increase the number of available processors, multiple clusters may be
`connected. Id. at 4:50–53. Figure 1A is reproduced below.
`
`
`2 U.S. Patent No. 7,698,509 B1 (Ex. 1005) (“Koster”).
`3 Jeffrey Kuskin et al., The Stanford FLASH Multiprocessor, in
`PROCEEDINGS OF THE 21ST ANNUAL INTERNATIONAL SYMPOSIUM ON
`COMPUTER ARCHITECTURE 302 (1994) (Ex. 1006, “Kuskin”).
`
`3
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`
`Figure 1A shows an example of a multiple cluster, multiple processor
`system described by the ’121 patent. Id. at 6:10–12. Figure 1A includes
`four processing clusters: 101, 103, 105, and 107, each of which can, in turn,
`include multiple processors. Id. at 6:12–14. The clusters are connected
`through point-to-point links 111a–f. Id. at 6:14–16.
`The ’121 patent explains that cache coherency problems can arise in
`such a system, because it may contain multiple copies of the same data. Id.
`at 1:26–38. For example, if the caches of two different processors have a
`copy of the same data block and both processors “attempt to write new
`values into the data block at the same time,” then the two caches may have
`different data values and the system may be “unable to determine what value
`to write through to system memory.” Id. at 1:37–45. Solutions to cache
`coherency problems often involve an increase in communication traffic and
`a resulting decrease in efficiency. Id. at 1:23–26, 2:46–48. The ’121 patent
`
`4
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`discloses “techniques . . . for increasing data access efficiency in a multiple
`processor system,” while also addressing cache coherency. Id. at 4:36–38.
`The system disclosed by the ’121 patent includes a probe filtering
`unit. Id. at 2:52–65. A probe is defined as “[a] mechanism for eliciting a
`response from a node to maintain cache coherency in a system.” Id. at 5:45–
`47. As opposed to a traditional approach of broadcasting probes to all
`nodes, the probe filtering unit reduces traffic by intercepting the probes and
`transmitting them only to those nodes that require the information based on
`probe filtering information, i.e., “[a]ny criterion that can be used to reduce
`the number of clusters or nodes probed.” Id. at 2:52–3:5, 14:50–52; see id.
`at 28:29–58, 29:43–46. The probe filtering unit may also accumulate
`responses from those nodes selected to receive the probes and respond to the
`node from which the probe originated. Id. at 3:5–8, 28:59–67, 29:46–51.
`Figure 18 of the ’121 patent is reproduced below.
`
`5
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`
`
`Figure 18 shows a multiple processor system with a probe filtering
`unit. Id. at 3:61–63, 26:58–27:20, Fig. 18. Specifically, Figure 18 depicts
`multiple processor system 1800 with processing nodes 1802a–d
`interconnected by point-to-point communication links 1808a–e. Id. at
`26:58–27:1. System 1800 also includes probe filtering unit 1830 as well as
`I/O switch 1810, one or more Basic I/O systems (“BIOS”) 1804, I/O
`adapters 1816, 1820, and a memory subsystem with memory banks 1806a–d.
`Id. at 3:61–63, 26:58–27:20, Fig. 18.
`
`E. Challenged Claims
`The challenged claims are all dependent and depend either directly or
`indirectly from independent claim 16. Claim 16 recites as follows:
`16. A probe filtering unit for use in a computer system
`comprising a plurality of processing nodes interconnected by a
`
`6
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`first point-to-point architecture, each processing node having a
`cache memory associated therewith,
`the probe filtering unit being operable to receive probes
`corresponding to memory lines from the processing nodes and to
`transmit the probes only to selected ones of the processing nodes
`with reference to probe filtering information representative of
`states associated with selected ones of the cache memories.
`Ex. 1001, 32:7–15 (line break added).
`
`II. ANALYSIS
`
`A. Claim Construction
`We interpret claims of an unexpired patent using the broadest
`reasonable construction in light of the specification of the patent in which
`they appear. 37 C.F.R. § 42.100(b). We presume a claim term carries its
`“ordinary and customary meaning,” which is “the meaning that the term
`would have to a person of ordinary skill in the art in question” at the time of
`the invention. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed. Cir.
`2007) (citation and quotations omitted). This presumption, however, is
`rebutted when the patentee acts as his own lexicographer by giving the term
`a particular meaning in the specification with “reasonable clarity,
`deliberateness, and precision.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir.
`1994).
`Petitioner and Patent Owner proffer proposed constructions of various
`claim terms. In the Institution Decision, we construed several terms,
`including “states associated with selected ones of the cache memories.” Inst.
`Dec. 8–13. After institution, the parties’ briefing addressed only the
`construction of “states.” We address below the parties’ arguments regarding
`the construction of “states” and otherwise maintain our constructions from
`the Institution Decision.
`
`7
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`1. “states”
`Claim 16 recites “probe filtering information representative of states
`associated with selected ones of the cache memories.” Before our Institution
`Decision, Patent Owner proposed a construction of the term “states.”
`Prelim. Resp. 14–22. Patent Owner proposed that the term means “cache
`coherence protocol states associated with data blocks stored in selected ones
`of the cache memories” where a “cache coherence protocol state” means
`“the current state of a data block in a protocol used to maintain the
`coherency of caches, in which a data block can only be in one current state
`at a time, and in which the current state can transition to a different state
`upon one or more triggering events or conditions.” Prelim. Resp. 14–15. In
`the Institution Decision, we did not adopt Patent Owner’s proposed
`construction, but found that “the term is not limited to cache coherence
`protocol states and is broad enough to include the condition of presence—
`i.e., what is stored in cache memory.” Inst. Dec. 10.
`In its Response, Patent Owner continues to argue that “the appropriate
`construction of states is limited to cache coherence states, and does not
`include mere presence.” Paper 17 (“PO Resp.”), 2. Petitioner does not
`agree that the term should be so limited. Paper 25 (“Pet. Reply”), 2–5. In
`particular, Petitioner asserts that the broadest reasonable construction of the
`term “states” is not limited to cache coherency states (id. at 2–4) and is
`broad enough to encompass the condition of presence (id. at 4–5).
`
`a. Cache Coherence States
`The language of the challenged claims “states associated with selected
`ones of the cache memories” plainly links the “states” to “cache memories.”
`In addition, in the challenged claims, the term “representative of states
`
`8
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`associated with selected ones of the cache memories” modifies “probe
`filtering information” (Ex. 1001, 31:5–7, 32:14–15, 32:52–55 (emphasis
`added)), which the patent defines as “[a]ny criterion that can be used to
`reduce the number of clusters or nodes probed” (id. at 14:50–52). Thus, the
`recited “states” relate, not just to any aspect of the cache memory, but to the
`contents of that memory.
`For the reasons discussed below, however, despite the arguments and
`evidence in Patent Owner’s Response, we remain unpersuaded that the
`’121 patent supports limiting the broadest reasonable construction of “states”
`solely to cache coherence protocol states. A claim term will be interpreted
`more narrowly than its ordinary and customary meaning only under two
`circumstances: (1) the “patentee sets out a definition and acts as [its] own
`lexicographer,” or (2) the “patentee disavows the full scope of a claim term
`either in the specification or during prosecution.” Aventis Pharma S.A. v.
`Hospira, Inc., 675 F.3d 1324, 1330 (Fed. Cir. 2012). To disavow claim
`scope, the specification or prosecution history must “make[] clear that the
`invention does not include a particular feature” and the feature is then
`“deemed to be outside the reach of the claims of the patent, even though the
`language of the claims, read without reference to the specification” or
`prosecution history, “might be considered broad enough to encompass the
`feature in question.” SciMed Life Sys., Inc. v. Advanced Cardiovascular
`Sys., Inc., 242 F.3d 1337, 1341 (Fed. Cir. 2001); see Aventis, 675 F.3d at
`1330. To disavow claim scope, the patentee may “include[] in the
`specification expressions of manifest exclusion or restriction, representing a
`clear disavowal of claim scope.” Aventis, 675 F.3d at 1330 (internal
`
`9
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`quotations omitted). In this context, it is not sufficient “that the only
`embodiments, or all of the embodiments, contain a particular limitation.” Id.
`Here, beginning with the claims, the relevant language in the
`independent claims, “states associated with selected ones of the cache
`memories,” expressly recites “states” alone—not cache coherency states, to
`which Patent Owner seeks to limit the term. Patent Owner’s proposed
`construction seeks to add additional narrowing descriptive language to the
`term “states.”
`Moreover, the claims do not recite “cache coherence states” or “cache
`coherence protocol states.” Dependent claim 3, which depends indirectly
`from claim 1, however, recites “a cache coherence controller” and “a cache
`coherence directory.” Ex. 1001, 31:12–14. Similarly, claim 5, another
`claim that depends indirectly from claim 1, requires a “cache coherence
`controller.” Id. at 31:24. Thus, had the patentees intended to limit “states,”
`as recited in the independent claims of the ’121 patent, to cache coherence
`states, they demonstratively could have done so by explicitly modifying the
`disputed term with “cache coherence”—but did not.4
`
`
`4 Patent Owner notes that our Institution Decision “preliminary determined
`that ‘states’ in the claims of the ’121 Patent are not limited to ‘cache
`coherence protocol states,” “despite the fact that the Board determined that
`the term ‘probe’ in the claims should be construed as a ‘mechanism for
`eliciting a response from a node to maintain cache coherency in a system.’”
`PO Resp. 2. We do not agree with Patent Owner’s implication that our
`construction of “probe” conflicts in any way with our construction of
`“states.” The two words recite different parts of the claimed invention.
`Moreover, the ’121 patent expressly defines the term “probe” consistent with
`our construction (see Ex. 1001, 5:45–47; Inst. Dec. 8), but provides no
`definition for “state” or “states.” If “states” were intended to be limited to
`cache coherency protocol states, the ’121 patent could have provided an
`
`10
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`Turning to the written description, we do not find persuasive Patent
`Owner’s arguments that the remainder of the specification supports limiting
`“states” to cache coherency states. Rather, we agree with Petitioner that the
`’121 patent uses broad language in describing “states,” explaining that
`“particular implementations may use a different set of states” and “[t]he
`techniques of the present invention can be used with a variety of different
`possible memory line states.” Ex. 1001, 14:30–36; see Inst. Dec. 9–10;
`Reply 2–3.
`Patent Owner asserts that the teachings of the ’121 patent make it
`clear that its inventions are directed to the specific field of cache coherency
`and the term “state” has “a specific meaning in the field of cache
`coherency—a cache coherency state.” PO Resp. 3–4; see Tr. 63:13–64:2.
`As to the field of the ’121 patent, we find that it is directed, generally, to
`“data access and cache coherency in systems having multiple processors.”
`E.g., Ex. 1001, 2:39–47. The ’121 patent explains that data access, and the
`disclosed invention, involve techniques for reducing probe traffic as well as
`cache coherency techniques. See, e.g., id. at 1:21–27 (“The present
`invention relates to accessing data in a multiple processor system. More
`specifically, the present invention provides techniques for reducing memory
`transaction traffic in a multiple processor system. Data access in multiple
`processor systems can raise issues relating to cache coherency.”); see also,
`e.g., id. at [54] (title) (“Reducing Probe Traffic in Multiprocessor Systems”);
`
`
`express definition for “state” or “states,” as it does for “probes.” Patent
`Owner does not provide evidence or reasoning persuading us that a person
`of ordinary skill in the art would find the express definition of “probes” as
`somehow limiting the term “states.”
`
`11
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`id. at 2:45–48 (“According to the present invention, various techniques are
`provided for reducing traffic relating to memory transactions in
`multiprocessor systems”). Although we agree with Patent Owner that the
`field of the ’121 patent includes cache coherency, we are not persuaded that
`this fact, alone, limits the term “state” to “cache coherence states.”
`Patent Owner, in fact, concedes that the term “state” “may have many
`broad and different meanings . . . in the general field of computers.” PO
`Resp. 4 (citing Ex. 2016 ¶ 15). Indeed, in our Institution Decision, we relied
`on a dictionary definition of “state” from the MICROSOFT COMPUTER
`DICTIONARY: “[t]he condition at a particular time of any of numerous
`elements of computing—a device, a communications channel, a network
`station, a program, a bit, or other element—used to report on or to control
`computer operations.” Ex. 3001 (MICROSOFT COMPUTER DICTIONARY (5th
`ed. 2002)), 497–98. Patent Owner agrees that this dictionary is directed “to
`the entire field of computing.” PO Resp. 4; Pet. Reply 4. And Patent Owner
`relies on this same dictionary when proposing a construction for another
`term in the ’121 patent—“programmed.” See IPR2015-00163, Paper 31, 15.
`Patent Owner has not persuaded us that a person of ordinary skill in the art
`would not base its definition of the term “states” on the field of computers
`generally, but instead would rely on a meaning specific to the “field of cache
`coherency.”
`To begin with, Patent Owner agrees that a person of ordinary skill in
`the art would have a degree in electrical engineering, computer engineering,
`or computer science and at least two years of experience in the design of
`multiprocessor systems. Ex. 2016 ¶ 8. Nothing in this definition points to a
`specific field, known as cache coherency, with its own terminology
`
`12
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`displacing the more general terminology used by those in the field of
`computing.
`Moreover, Patent Owner’s position with respect to Koster belies
`Patent Owner’s argument that, in the context of a patent describing data
`access and cache coherence in multiprocessor systems, the term “state,” used
`on its own, necessarily refers to a cache coherency state. Koster, titled
`“snooping based cache-coherence filter for a point-to-point connected
`multiprocessing node,” refers to his shadow tag memory as a “local state
`memory.” Ex. 1005, [54], 6:11–12. Yet, Patent Owner takes the position
`that Koster’s local state memory/shadow tag memory does not constitute
`“information representative of states associated with selected ones of the
`cache memories,” as required by the disputed claim language. PO Resp. 13–
`16.5 Essentially, Patent Owner attempts to argue in the claim construction
`section of its Response that a person of ordinary skill in the art would
`understand that, in the context of the ’121 patent, the term “state” on its own,
`means “cache coherency state,” where the actual cache coherency states
`encompass an open set of states used by any cache coherency protocol. See
`
`5 Indeed, in IPR2015-00163, Patent Owner argues that “the mere fact that
`Koster refers to his shadow tag memory as ‘local state memory’ does not
`mean that it contains ‘information representative of states associated with
`selected ones of the cache memories’ as that phrase is used in the ’121
`patent.” IPR2015-00163, Paper 31, 23. Instead, according to Patent Owner,
`to determine the meaning of “local state memory,” “it is necessary to
`consider what information Koster stores in the shadow tag memory and
`whether such information satisfies the properly construed limitation.” Id.
`Patent Owner concludes that because tags only indicate the address of data,
`“despite Koster’s reference to such tags as ‘state’ information,” the tags “are
`not representative of cache coherency states as required by the properly
`construed limitations of the ’121 patent.” Id.
`
`13
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`Prelim. Resp. 14–15; PO Resp. 1–7. However, when analyzing the prior art,
`which involves the same field as the ’121 patent, Patent Owner takes the
`position that the same person of ordinary skill would understand the term
`“state” on its own does not mean cache coherency state. Patent Owner does
`not explain sufficiently why the term state would mean one thing in the
`’121 patent and another in Koster when both involve the same field of art.
`Patent Owner relies, for its assertions, on a few excerpts of the
`’121 patent, which allegedly “demonstrate that the use of the term ‘state’ in
`the patent is directed to cache coherence protocol states.” PO Resp. 5–7.
`For example, Patent Owner points to the following passage of the
`specification as “mak[ing] it clear that the relevant state is a cache coherence
`protocol state” (PO Resp. 5–6):
`It should be noted that a coherence protocol can contain several
`types of messages. In one example, a coherence protocol
`includes four types of messages; data or cache access requests,
`probes, responses, or probe responses, and data packets. Data or
`cache access requests usually target the home node memory
`controller. Probes are used to query each cache in the system.
`The probe packet can carry information that allows the caches to
`properly transition the cache state for a specified line.
`
`Ex. 1001, 9:21–29 (emphases added). Similarly, Patent Owner points to the
`specification’s statement that “[b]y using a coherence directory, global
`memory line state information (with respect to each cluster) can be
`maintained and accessed by a memory controller or a cache coherence
`controller in a particular cluster,” asserting that this statement only makes
`sense if the coherence directory concerns solely cache coherence states. PO
`Resp. 6 (quoting Ex. 1001, 13:4–7).
`
`14
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`We are not persuaded that these passages of the ’121 patent limit the
`term “states” as asserted by Patent Owner. Neither of the passages relied
`upon by Patent Owner actually uses the term “state” as recited in the
`challenged claims. Instead, the first passage Patent Owner relies on for a
`narrower construction uses the term “cache state” and the second uses the
`term “global memory line state information.” Thus, even if the passages
`describe a concept narrower than “states associated with selected ones of the
`cache memories,” as recited in the challenged claims, this difference can be
`attributed to the fact that different terms are used. More importantly, these
`passages do not expressly disclaim or disavow the broader scope of the
`claim language, particularly given the expansive language used elsewhere in
`the specification allowing states to include “a variety of different possible
`memory line states.” Ex. 1001, 14:30–36.
`Patent Owner also points to Figures 7 and 8 of the ’121 Patent as
`allegedly “strongly illustrative that the ’121 patent uses ‘state’ to mean cache
`coherence protocol states.” PO Resp. 7. According to Patent Owner, the
`specification equates the word state with cache coherence states by stating
`“the coherence directory 701 [of Figure 7] includes state information 713”
`and by stating “[i]n some embodiments, the memory line states are modified,
`owned, shared, and invalid.” Id. (quoting Ex. 1001, 13:55–59) (emphases
`added by Patent Owner). In other words, Patent Owner argues that because
`Figure 7 shows a column labeled “state,” and describes this column as
`including in some embodiments the states used in common cache coherence
`protocols such as MOESI and MOSI, the term “state” must be equivalent to
`cache coherence protocol. See Tr. 77:20–78:18.
`
`15
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`Figures 7 and 8, however, also are not persuasive as defining the term
`state because they are clearly described as exemplary embodiments. See,
`e.g., Ex. 1001, 3:15–18; 4:11–35 (“[I]t is not intended to limit the invention
`to the described embodiments. On the contrary, it is intended to cover
`alternatives, modification, and equivalents as may be included within the
`spirit and scope of the invention as defined by the appended claims.”);
`13:44–59 (describing Figure 7 using the term “example” or “embodiment”
`no less than five times); 14:48–50; 30:57–64 (“[T]he scope of the invention
`should not be limited by reference to such advantages, aspects, and objects.
`Rather, the scope of the invention should be determined with reference to the
`appended claims.”). We are not persuaded that Figure 7 shows anything
`more than what it purports to show—one example with a column labeled
`“state,” that may refer to “memory line states” of “modified, owned, shared,
`and invalid.” Again, nothing in this example expressly disclaims or
`disavows the broad claim language, particularly in light of other statements
`in the specification allowing states to include “a variety of different possible
`memory line states.” Ex. 1001, 14:30–36.
`Patent Owner further argues that the ’121 patent distinguishes
`between state information and tags in certain examples disclosed therein.
`PO Resp. 14–15. We also find this information unpersuasive, as Patent
`Owner’s citation of portions of the ’121 patent that discuss both tags and
`state information does not persuade us that tags and state information are
`mutually exclusive, as these portions of the ’121 patent are examples.
`See id. 14–15 (citing Ex. 1001, 7:67–8:4; 13:44–14:47; Fig. 7). Patent
`Owner does not identify any portion of the ’121 patent that clearly disavows
`tags as mutually exclusive from state information.
`
`16
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`Patent Owner also proffers extrinsic evidence to support its proposed
`construction of the term “state.” Extrinsic evidence is “less significant than
`the intrinsic record in determining the legally operative meaning of claim
`language.” Phillips v. AWH Corp., 415 F.3d 1303, 1317 (Fed. Cir. 2005)
`(citations omitted) (internal quotations omitted). For example, Patent Owner
`points to “one of the treatises on cache coherency,” Daniel J. Sorin et al., A
`PRIMER ON MEMORY CONSISTENCY AND CACHE COHERENCE (2011) (Ex.
`2010, “Sorin”), as equating the term “state” with cache coherence protocol
`states. PO Resp. 4 (citing Ex. 2010, 88–89; Ex. 2016 ¶ 15). We do not find
`this evidence persuasive. Evidence of the use of shorthand within one
`section in one publication does not indicate that that same shorthand will be
`recognized, by a person of ordinary skill, as necessarily having the same
`meaning in other contexts. Dr. Oklobdzija’s testimony referring to this
`treatise does not persuade us to the contrary. See Ex. 2016 ¶ 15. Indeed, Dr.
`Sorin, as one of the authors of Sorin, testifies that Sorin does not use the
`term “state” as meaning only a cache coherence protocol state. Ex. 1015 ¶
`19; Pet. Reply 4. To the contrary, Dr. Sorin testifies that a person of
`ordinary skill in the art would not understand the term “states” in the
`disputed claim language as limited to cache coherency states. Ex. 1015
`¶¶ 17–18; Pet. Reply 4.
`Patent Owner also points to another article, where the authors—three
`of whom are the authors of Sorin, discussed above—state that “[a]
`processor’s access to a cache block is determined by the state of that block
`in its cache, and this state is generally one of the five MOESI (Modified,
`Owned, Exclusive, Shared, Invalid) states.” PO Resp. 5 (citing Ex. 2003, 1)
`(emphasis added); see Reply 4. Again, this isolated use of a shorthand of
`
`17
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`“states” in a publication, with several of the same authors as the other cited
`publication, does not persuade us that this shorthand is universally accepted
`to have a particular meaning whenever a particular type of software is being
`discussed. Moreover, the use of the term “generally” in this statement
`shows that it is not limiting the term “states” to cache coherency states, or
`more specifically, MOESI states. Therefore, we are not persuaded that
`Patent Owner’s extrinsic evidence regarding ordinary meaning overcomes
`the intrinsic record of this case. See Phillips, 415 F.3d at 1318 (“[A] court
`should discount any expert testimony that is clearly at odds with the claim
`construction mandated by the claims themselves, the written description, and
`the prosecution history, in other words, with the written record of the
`patent.”) (citations and internal quotations omitted).
`In summary, we conclude that the recited “states” relate to the
`contents of cache memory, but are not limited solely to cache coherence
`protocol states.
`
`b. Presence
`Even if we did agree with Patent Owner’s assertion that the term
`“states” is limited to cache coherence states, we find unpersuasive Patent
`Owner’s arguments relating to presence.
`The ’121 patent directly touches on the subject of presence when
`discussing cache coherency states. For example, when describing certain
`embodiments associated with Figure 7, including cache coherency memory
`line states of “modified, owned, shared, and invalid,” the ’121 patent
`declares “[i]n the invalid state, a memory line is not currently available in
`cache associated with any remote cluster.” Ex. 1001, 13:58–61. Patent
`Owner argues that, contrary to the ordinary meaning of these words, the
`
`18
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`disclosed “invalid” state does not refer only to a lack of presence, but instead
`means that the memory line “can be present but invalid,” because it cannot
`be rel[ied] on,” or is “not available to use because it is invalid.” Paper 34
`(“Tr.”), 80:20–81:13. Patent Owner, however, does not explain sufficiently
`why a person of ordinary skill in the art would understand the statement in
`this way, as opposed to the plain meaning of the “currently available”
`language in the specification. See Tr. 80:13–84:8.
`Instead, Patent Owner points to other portions of the specification,
`asserting that the ’121 patent teaches “‘state’ provides additional information
`about ‘a particular cached line’ that is known to already be ‘somewhere’ (i.e.
`it is already known to be present).’” PO Resp. 8. In particular, Patent
`Owner bases this assertion on a passage of the ’121 patent stating “because
`the cache coherence directory provides information about where [i.e., in
`which cluster the line is present] memory lines are cached as well as their
`states, probes only need be directed toward the clusters in which the
`requested memory line is cached” and “[t]he state of a particular cached
`line will determine what type of probe is generated.” Id. at 7–8 (quoting
`Ex. 1001, 19:36–43 (emphases added by Patent Owner)). According to
`Patent Owner, this passage “plainly indicates” that the state of a memory
`line is different from where it is located and that “state” only exists for a
`cached line. Id. at 8.
`Patent Owner also points to the ’121 patent’s discussion of an
`“occupancy vector” as demonstrating that the patent does not consider
`presence to be a state. PO Resp. 8–9. According to Patent Owner, the ’121
`patent’s statement that “[a]ny mechanism for tracking what clusters hold a
`copy of the relevant memory line in cache [i.e., in which clusters the
`
`19
`
`

`
`Case IPR2015-00158
`Patent 7,296,121 B2
`
`memory line is present] is referred to herein as an occupancy vector,” and its
`treatment of the “occupancy vector” different than the “state” filed in Figure
`7, indicate that the ’121 patent understands presence and “state” to be
`different. Id. (citing Ex. 1001, 13:55–57, 13:67–14:2, Fig. 7); Ex. 2016 ¶ 24.
`We are not persuaded that the ’121 patent limits cache coherency
`states as argued by Patent Owner. Intrinsic and extrinsic evidence
`contradicts Patent Owner’s and Dr. Oklobdzija’s suggestion that a cache
`coherency state necessarily needs to indicate more than whether a memory
`line is present in cache memory. As noted above, the ’121 patent itself
`discloses that “[i]n the invalid state, a memory line is not currently available
`in cache associated with any remote cluster.” Ex. 1001, 13:60–61 (emphasis
`added). As also noted above, the plain meaning of this statement is that the
`“invalid” cache cohere

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket