PTAB
Advanced fields
11 decisions · 518msnewest first
  • Apple Inc. v. Corephotonics, Ltd.Some claims unpatentable
    PTAB · Nov 2, 2021 · IPR2020-00878 · APJ Bryan F Moore · IPR · Final written decision

    Claims 1, 2, 4–6, 9–15, 17, 18, 20–23, and 25–29 are unpatentable; claims 3, 8, 16, 19, 24, and 30 were not shown unpatentable.

    RulingsFinal written decision
    • BurdenMixed

      “35 U.S.C. § 6. This Final Written Decision is issued pursuant to 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73. For the reasons discussed herein, we determine that Petitioner has shown, by a preponderance of the evidence, that claims 1, 2, 4–6, 9–15, 17, 18, 20–23, and 25–29 of the ’897 patent are unpatentable and that Petitioner has not shown, by a preponderance of the evidence, that claims 3, 8, 16, 19, 24, and 30 of the ’897 patent are unpatentable.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “would include someone who had, at the priority date of the ’897 Patent, (i) a Bachelor’s degree in Physics, Optical Sciences, or equivalent training, as well as (ii) approximately three years of experience in designing multi-lens optical systems. Such a person would have had experience in analyzing, tolerancing, adjusting, and optimizing multi-lens systems for manufacturing, and would have been familiar with the specifications of lens systems and their fabrication. In addition, a POSITA [person of ordinary skill in the art] would have known how to use lens design software such as Code V, Oslo, or Zemax, and would have taken a lens design course. Pet. 6–7 (citing Ex. 1003 ¶¶ 19–20). Patent Owner applied the same level of skill for the purposes of this IPR. PO Resp. 14–15 (citing Ex. 2001 ¶ 19). We regard Petitioner’s formulation of the level of skill as consistent with the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (prior art itself may reflect an appropriate level of skill). Therefore, for purposes of this Final Written Decision, we adopt Petitioner’s assessment of the level of skill in the art because it is consistent with the ’897 patent and the asserted prior art, and we apply it in our analysis below.” slip op. at 11

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

      “Patent Owner argues that no “dispute between the parties in this IPR depends on the construction of EFL, TTL, or of any other claim term [and] submits that the Board should refrain from construing any terms in the patent for the purposes of this proceeding.” PO Resp. 17. Petitioner does not respond to this argument. See generally Pet. Reply. We agree with Patent Owner. If we were to adopt either construction, it would not change the determination made in this Decision. Thus, we decline to construe any claim terms for purposes of this Final Written Decision. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”).” slip op. at 10

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “unpatentable under 35 U.S.C. § 102 as anticipated by Ogino. Pet. 10–40. Patent Owner does not present arguments related to this ground. See generally PO Resp. For the reasons that follow, we are persuaded that the evidence supports Petitioner’s arguments and thus, Petitioner establishes by a preponderance of the evidence that claims 1, 4, 9–15, 17, 20, and 25–29 are unpatentable under 35 U.S.C. § 102 as anticipated by Ogino.” slip op. at 17

    Patent outcomesUS 10,330,897 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 10,330,897
  • PTAB · May 23, 2019 · IPR2018-00180 · APJ Kamran Jivani · IPR · Final written decision

    Claims 4–7, 9–16, and 18 are unpatentable over Hwang or Hwang and Balakrishnan; claim 17 was not shown unpatentable over Hwang.

    RulingsFinal written decision
    • Skill levelSkill level patent owner adoptedDecided for patent owner

      “Although the parties formulate slightly differently their respective assessments of the skill level, neither party disputes directly the other’s assessment nor makes any arguments related to the assessments. See generally Pet.; PO Resp. The ’221 patent states its disclosure “relates, in general, to integrated circuits and, more particularly, to power converter integrated circuits.” Ex. 1001, 1:9–11. In view of the foregoing, we adopt Patent Owner’s formulation of the level of ordinary skill in the art. Further, this level of ordinary skill is reflected by the prior art of record. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art itself can reflect the appropriate level of ordinary skill in the art).” slip op. at 8

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

      “construction must begin with the words of the claims themselves.”); In re NTP, Inc., 654 F.3d 1279, 1288 (Fed. Cir. 2011) (citing Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc)) (“As with any claim construction analysis, we begin with the claim language.”). None of the challenged claims (nor even unchallenged claim 8) recites the claimed disabling or terminating occurs in response to the detect signal independent of other circuit conditions or in response only to the detect signal. See Ex. 1001, 12:5–14:36. For instance, independent claim 4 merely recites, “wherein the control circuit disables the switched drive control signal in response to the detect signal.” Id. at 12:49–51. Independent claim 7 similarly recites, “wherein the gating circuit disables the drive control signal in response to the detect signal.” Id. at 13:11–13. Independent claim 9 discloses only, “a first comparator . . . having an output for disabling the pulse generator.” Id. at 13:27–30. Finally, independent claim 15 requires, “comparing the error signal to a reference signal . . . to terminate the step of generating in response to the error signal.” Id. at 14:21–23. Therefore, the plain language of the challenged claims does not, standing alone, support adoption of Patent Owner’s proposed construction.” slip op. at 13

    • Expert testimonyPetitioner expert creditedDecided for petitioner

      “testimony from their respective declarants on whether one of ordinary skill in the art would understand “in response to” as requiring “independent of other circuit conditions.” Compare Reply 2–3 (citing Ex. 1016 ¶¶ 18–21, 26–30; Ex. 2003, 43:16–45:1) with PO Resp. 14–15, 17 (citing Ex. 2001 ¶¶ 42, 44–45.) and Sur-Reply 11–12 (citing Ex. 2001 ¶ 45). Patent Owner further directs our attention to a single sentence of deposition testimony in which Petitioner’s declarant Dr. Szepesi appears to agree with Patent Owner’s construction by stating, in the context of claim 9, that “the output signal of this first comparator disables the output pulses driving the gate of that independent of anything else.” PO Resp. 8 (citing Ex. 2003, 44:16– 45:1). Petitioner rebuts Patent Owner’s arguments by identifying additional deposition testimony and statements made in a second declaration offered by Dr. Szepesi opposing Patent Owner’s construction. Reply 2–3 (citing Ex. 1016 ¶¶ 18–21, 26–30; Ex. 2003, 43:16–45:1). For instance, immediately before the statement Patent Owner cites, Dr. Szepesi testified: Q: “So is it your opinion that an output for disabling the pulse generator must disable the pulse generator regardless of the other conditions in the circuit?” . . . A: “I don't understand your question. I said disabling the pulse generator means that the output of the pulse generator which is providing the pulses to the gate of the main switch, those pulses are disabled. That’s what it means in my opinion in this context.” Ex. 2003, 43:24–44:9. And, in his supplemental declaration, Dr. Szepesi states: As a first matter, I opined during my deposition that “an output disabling a pulse generator” means that “the output signal of this first comparator disables the output pulses driving the gate of that independent of anything else.” But, at the time of my deposition I had not done a focused claim construction analysis of the limitation “a first comparator […] having an output for disabling the pulse generator.” This is because I hadn’t anticipated there being a dispute relevant to the validity analysis in view of what I understood as the plain meaning of the language. Despite the quote that Patent Owner relied upon, I believe now that a POSITA would not understand the claim language to require the first comparator to disable the output pulses independent of anything else. This belief is consistent with my responses to the first two of three successive questions in which I was asked about “disabling the pulse generator.” It is my opinion that the operation of the disclosed embodiment requires the presence of other conditions precedent before the first comparator can disable the drive pulses and this requirement is not excluded by the claim language. Ex. 1016 ¶ 18 (emphasis added). Our reviewing court has made clear that extrinsic evidence “is generally of less significance than the intrinsic record” in matters of claim construction. Wi-LAN, Inc. v. Apple Inc., 811 F.3d 455, 462 (Fed. Cir. 2016) (citation omitted). Here, beyond competing declarant testimony, neither party has entered into the record extrinsic evidence, such as dictionary definitions or contemporaneous usage in the art, addressing the scope of “in response to.” Having considered the testimony upon which Patent Owner relies and weighing it against the claim language itself, the Specification’s disclosures set forth above, and the contrary testimony of Petitioner’s declarant, we find on balance that it does not warrant departing from the plain and ordinary meaning of “in response to” as Patent Owner urges. See In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994) (holding that an inventor may define specific terms used to describe invention, but must do so “with reasonable clarity, deliberateness, and precision”) (quoting Intellicall, Inc. v. Phonometrics, Inc., 952 F.2d 1384, 1387-88 (Fed. Cir. 1992)).” slip op. at 17

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Claim 4 further recites, “a control circuit having an input coupled for receiving the detect signal, wherein the control circuit disables the switched drive control signal in response to the detect signal.” Patent Owner’s sole contention with respect to claim 4 is that “[t]he alleged detect signal in Hwang does not satisfy this limitation” because “unlike the ’221 patent, the alleged ‘control circuit’ does not disable the switched drive control signal ‘in response to the detect signal’ independent of other circuit conditions.” PO Resp. 15–16. As discussed above, we decline to import into claim 4 a requirement that the claimed disabling must occur independent of other circuit conditions. See supra Section III.C.1. Because Patent Owner’s argument relies on a claim construction that we rejected above, we are not persuaded that Hwang fails to meet the limitations of claim 4. Rather, having reviewed the evidence cited by Petitioner, we agree with Petitioner that Hwang discloses the limitations of independent claim 4, arranged as recited in the claim. Petitioner’s analysis, as supported by the Szepesi Declaration, further demonstrates where Petitioner contends each element of dependent claims 5 and 6 is disclosed in Hwang. Pet. 21–24. Patent Owner does not dispute Petitioner’s analysis beyond the argument raised with respect to claim 4. See PO Resp. 17. Having reviewed the evidence cited by Petitioner, we agree with Petitioner that Hwang discloses the limitations of dependent claims 5 and 6, arranged as recited in these claims, and we adopt that analysis as our own. Accordingly, for the foregoing reasons, we find Petitioner has shown by a preponderance of the evidence that Hwang anticipates claims 4–6.” slip op. at 25

    Patent outcomesUS 6,597,221 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 6,597,221
  • PTAB · Aug 14, 2017 · IPR2016-00591 · APJ Garth D Baer · IPR · Final written decision

    Claims 1, 3, 6, 9, 12-14, 16, 19, 22, and 23 are unpatentable as anticipated by Avrahami; claims 10, 15, and 25 were not shown obvious.

    RulingsFinal written decision
    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “We agree with Petitioner. Avrahami describes its algorithm as providing “for semi-automatic 3D spatial polygon extraction from a pair of colored aerial images with a known external model solution.” Ex. 1004, 43 (emphasis added). Avrahami touts that one of the advantages of its system is that “the operator can identify at a glance which buildings can be mapped by this method so as to combine it with traditional manual extraction or other semi-automatic method.” Id. at 48 (emphasis added). Further to this point, Figure 1 shows a side-by-side comparison of the images in the pair. See id. at Fig. 1 (displaying left and right polygons going through Avrahami’s iterative matching process). Further, we credit the testimony from Petitioner’s Expert, Mr. Schuch, that one skilled in the art would understand Avrahami’s images to be what “you see . . . on a computer screen” as “part of the production.” Ex. 2017, 69:20–21; see also id. at 71:2–4 (explaining that “[t]his is an actual production image”). Therefore, we find that Petitioner has proffered sufficient evidence that Avrahami discloses the disputed limitation.” slip op. at 10

    • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia with nexusDecided for patent owner

      “We are persuaded by Patent Owner’s extensive evidence of nexus between its Render House and Twister products and the challenged claims. Patent Owner steps through each challenged claim on an element-by-element basis and directs us to images and specific passages from its Render House and Twister user guides that it argues embody the limitations of each challenged claim. PO. Resp. 50–58. Patent Owner also supports its assertion of nexus with testimony in the form of a Declaration from Dr. Chandrajit L. Bajaj that includes a claim chart detailing where each limitation of the challenged claim is found in its Twister and Render House products. Ex. 2010, 44–91.5 The Federal Circuit has held that “if the marketed product embodies the claimed features, and is coextensive with them, then a nexus is presumed and the burden shifts to the party asserting obviousness to present evidence to rebut the presumed nexus.” Brown & Williamson Tobacco Corp. v. Philip Morris Inc., 229 F.3d 1120, 1130 (Fed. Cir. 2000). Patent Owner has put forth sufficient evidence to show that its Twister and Render House products embody the elements of the challenged claims and thus, we look to Petitioner to rebut this presumed nexus and acknowledge that the presumption “cannot be rebutted with mere argument; evidence must be put” slip op. at 17

    • Obviousness (§103) › Objective indicia / secondary considerations › Commercial successObjective indicia with nexusDecided for patent owner

      “with the purportedly unique characteristics of the claimed invention and that for which there is alleged commercial success.” Reply 23–24. Our reviewing court has held that for evidence of commercial success to be relevant, “the patentee must establish a nexus between the evidence of commercial success and the patented invention.” Wyers v. Master Lock Co., 616 F.3d 1231, 1246 (Fed. Cir. 2010). As noted above, however, Patent Owner has provided extensive evidence that the Twister and Render House products are coextensive with claims 10, 15, and 25 and that the reports sold were created using the Twister and Render House products. Thus, we are persuaded that nexus exists between the challenged claims and the commercially successful products at issue. Petitioner also asserts that “Patent Owner has failed to make any showing as to market share, thus rendering their sales figures irrelevant and not adequately defined.” Reply 24. Patent Owner provided unrebutted evidence that “approximately 96 percent of the top 25 insurance carriers rely on [Eagle View Technologies 3D aerial roof measurement reports] in their claims departments.” Ex. 2020, 1; see also Ex. 2029, 8 (Verisk Analytics presentation noting that 24 of top 25 insurance companies and 30,000 contractors are Eagle View customers). In addition, Patent Owner’s evidence shows that its products are used by “about one-fifth of the roofing contractor market, according to an estimate by market researcher IbisWorld.” Ex. 2024. Patent Owner’s financial reports show both that it sold a significant number of roofing reports and that its sales grew significantly between 2009 and 2015. See PO Resp. 60–61. We find that this information, taken together with statement from others in the industry (see Ex. 2029) gives us a view of Patent Owner’s place in the relevant market and persuades us that Patent Owner’s Twister and Render House products experienced significant commercial success and wide-spread use in the industry.” slip op. at 20

    • Obviousness (§103) › Objective indicia / secondary considerations › Skepticism / industry praiseDecided for patent owner

      “iii. Industry Praise Praise from industry participants, especially competitors, is probative as to obviousness because such participants “are not likely to praise an obvious advance over the known art. Thus, if there is evidence of industry praise of the claimed invention in the record, it weighs in favor of the non-obviousness of the claimed invention.” Apple Inc. v. Samsung Elecs. Co., 839 F.3d 1034, 1053 (Fed. Cir. 2016). Petitioner described Patent Owner’s products as “[u]sing aerial photography and patent-pending software [to] accurately calculate[] measurements for the roof’s ridges, rafters, valleys, slopes and more.” Ex. 2021, 1. Petitioner further noted that the “process saves contractors and roofers hours of time spent measuring and scoping a roof.” Id.” slip op. at 23

    Patent outcomesUS 8,209,152 mixed
    § 102 anticipation§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 8,209,152
  • Sandisk Corp. v. Netlist, Inc.Some claims unpatentable
    PTAB · Sep 28, 2016 · IPR2015-01020 · APJ Peter P Chen · IPR · Final written decision

    Claims 17, 22, 24, 26, and 33 are unpatentable as obvious over Takeda, JEDEC, and Connolly; claims 15, 16, 31, and 32 were not shown unpatentable over Takeda and JEDEC.

    RulingsFinal written decision
    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

      “We are unpersuaded by Patent Owner’s position. First, the claim language does not recite any physical or structural connection, rather, only “electrically coupling.” Pet. Reply 3, 8–9. In addition, the specification of the ’150 patent does not define explicitly the term “selectively electrically coupling.” Therefore, as in IPR2014-00882 and IPR2014-01011, we refer to its ordinary and customary meaning, as would be understood by one of ordinary skill in the art in the context of the entire disclosure. Translogic Tech., 504 F.3d at 1257. A technical dictionary, the IEEE Dictionary,4 defines “electrical coupling” as “[e]lectrical charges in conductors of a disturbed circuit formed by electrical induction.” Ex. 3001. The IEEE Dictionary explains that “[s]ince the ratio of a conductor’s electrostatic charge to the potential difference between conductors (required to maintain that charge) is the general definition of capacitance, electrical coupling is also called capacitive coupling.” Id. The IEEE Dictionary defines” slip op. at 9

    • Skill levelSkill level board ownOther

      “Based on our review of the ’150 patent and the types of problems and solutions described in the ’150 patent and cited prior art, we conclude a person of ordinary skill in the art at the time of the ’150 patent would have a Bachelor’s degree in electrical engineering, computer engineering, computer science, or related field, and at least one year of work experience, including familiarity with computer memory systems and related industry standards such as JEDEC standards for DRAM memories and memory modules. We further note that the applied prior art reflects the appropriate level of skill at the time of the claimed invention. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). D. Declarant Testimony” slip op. at 13

    • Expert testimonyPetitioner expert creditedDecided for petitioner

      “To testify as an expert under Federal Rule of Evidence 702, a person need not be a person of ordinary skill in the art, but rather must be “qualified in the pertinent art.” Sundance, Inc. v. DeMonte Fabricating Ltd., 550 F.3d 1356, 1363–64 (Fed. Cir. 2008); see SEB S.A. v. Montgomery Ward & Co., 594 F.3d 1360, 1372–73 (Fed. Cir. 2010) (upholding a district court’s ruling to allow an expert to provide testimony at trial because the expert “had sufficient relevant technical expertise” and the expert’s “knowledge, skill, experience, training [and] education . . . [wa]s likely to assist the trier of fact to understand the evidence”); Mytee Prods., Inc. v. Harris Research, Inc., 439 F. App’x 882, 886–87 (Fed. Cir. 2011) (non-precedential) (upholding admission of the testimony of an expert who “had experience relevant to the field of the invention,” despite admission that he was not a person of ordinary skill in the art). As noted above, Dr. Jagannathan has designed and implemented hardware virtual memory caches, and researched theoretical performance measures of various cache coherency protocols, and has experience in the design of memory systems. We find that, although Dr. Jagannathan may be less experienced than Dr. Sechen in the area of memory module design, he is nonetheless qualified sufficiently to testify about memory systems and memory modules. E. Asserted Obviousness of Claims 15, 16, 31, and 32 in view of Takeda” slip op. at 14

    • ExcludeMotion to exclude, deniedDenied

      “We have reviewed the parties’ contentions on this issue, and exercise our discretion to determine that Petitioner’s Reply and the Jagannathan Supplemental Declaration will not be excluded. We find that, although they may be “inartfully” drafted, the first Jagannathan declaration and Petition sufficiently outlined Petitioner’s position on the function of the chip select signal, namely, that the chip select signal was not itself the logic signal enabling operation of bit-switches. We further find that Petitioner’s Reply and the Supplemental Jagannathan Declaration did not present an entirely new rationale of unpatentability based on Takeda, JEDEC, and Connolly. Cf. Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1369–70 (Fed. Cir. 2016) (affirming Board’s exclusion of reply brief and declaration that changed unpatentability theory to “an entirely new rationale”). Moreover, there is no dispute that Patent Owner was aware of Petitioner’s position by no later than the Jagannathan deposition, which preceded Patent Owner’s Response by ten days. Patent Owner could have addressed Petitioner’s chip select signal contention, procedurally or substantively, in its Response, but chose to raise the issue only after Petitioner filed its Reply and Supplemental Jagannathan Declaration. Accordingly, Patent Owner had notice of Petitioner’s position and an opportunity to refute that position in its Response.” slip op. at 24

    Patent outcomesUS 7,881,150 mixed
    Claim construction§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 7,881,150
  • PTAB · May 31, 2016 · IPR2015-00378 · APJ Robert J Weinschenk · IPR · Final written decision

    Claims 14 and 16–24 are unpatentable as obvious over Bace and Russinovich; claims 25 and 26 were not shown unpatentable because the evidence did not establish the claimed feature-likelihood limitations.

    RulingsFinal written decision
    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionDecided for patent owner

      “contends that this construction is necessary to clarify that the challenged claims require monitoring registry accesses because Petitioner’s declarant, Dr. Michael T. Goodrich, testified during his deposition that the records “may be records that don’t have direct impact on the registry.” Id. at 7–8. Even if Patent Owner’s characterization of Dr. Goodrich’s deposition testimony is accurate, Petitioner does not argue in the Petition or the Reply that the challenged claims do not require monitoring registry accesses. See Pet. 13–15, 21–32; Pet. Reply 1, 3–8. As such, there does not appear to be a dispute that requires claim construction. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”). Nonetheless, in order to avoid any ambiguity, we provide an express construction of the phrase “records regarding processes that access the operating system registry.” We determine that the evidence supports Patent Owner’s proposed construction. The written description of the ’084 patent consistently indicates that records of processes are obtained by monitoring accesses to the operating system registry. Ex. 1001, col. 5, ll. 6–18, col. 8, ll. 9–10, col. 8, ll. 22–24, col. 13, ll. 28–31, col. 13, ll. 46–52. In addition, Petitioner acknowledges that the challenged claims require monitoring accesses to the operating system registry. Tr. 12:15–13:3. Patent Owner’s proposed construction, however, omits the claim terms “processes” and “operating system,” which are part of the phrase being construed. Ex. 1001, col. 23, ll. 32–34. Therefore, we modify Patent Owner’s proposed construction to include those terms. Specifically, we construe the phrase “records regarding processes that access the operating system registry” to mean “records regarding processes obtained by monitoring accesses to the operating system registry.”1” slip op. at 6

    • Skill levelOther

      “of ordinary skill in the art at the time of the ’084 patent would have had “a Master’s degree in computer science or a related field with two to three years of experience in the field of software security systems.” Ex. 1003 ¶ 20. Patent Owner’s declarant, Dr. George Cybenko, testifies that a person of ordinary skill in the art at the time of the ’084 patent would have had “an undergraduate degree in computer science or mathematics, and one or two years of experience in the field of computer security.” Ex. 2019 ¶ 28. Thus, Petitioner’s declarant, Dr. Goodrich, defines the level of ordinary skill in the art slightly higher in both education and experience. Patent Owner points out this difference, but does not argue that it materially impacts either party’s analysis. PO Resp. 9–10. In fact, Petitioner’s declarant, Dr. Goodrich, testifies that his analysis would not change under the slightly lower level of ordinary skill in the art set forth by Patent Owner. Ex 1029 ¶¶ 7–8; Ex. 2018, 78:2-23. In other words, the minor distinctions between the parties’ proposed levels of ordinary skill in the art are not material. As a result, we determine that both parties define the level of ordinary skill in the art appropriately in this case. Patent Owner argues that, even if Petitioner correctly defines the level” slip op. at 9

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

      “90–93, 128, 139 (pp. 68–69); Ex. 1029 ¶¶ 9–10. Therefore, the teachings of Bace, together with the background knowledge and perspective of a person of ordinary skill in the art, would have made it obvious to use records obtained by monitoring registry accesses as an information source for an anomaly detection system. See Randall Mfg. v. Rea, 733 F.3d 1355, 1362– 63 (Fed. Cir. 2013); Ariosa Diagnostics v. Verinata Health, Inc., 805 F.3d 1359, 1365 (Fed. Cir. 2015).” slip op. at 13

    • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed

      “Thus, Petitioner identifies evidence indicating that Bace teaches determining the likelihood of observing an event, but does not identify evidence indicating that Bace teaches determining the likelihood of observing a feature, as recited in claim 25. Pet. 41–42; Pet. Reply 23–24; Tr. 30:2–15, 31:6–12. Petitioner instead argues that an event is the “same thing” as a feature. Tr. 30:20–24, 32:9–13. Petitioner, however, improperly presented this argument for the first time at the oral hearing. Id. at 30:13– 15; Pet. 41–42; Pet. Reply 23–24; see Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,768 (Aug. 14, 2012) (“No new evidence or arguments may be presented at the oral argument.”). Moreover, Petitioner does not identify any evidence from the ’084 patent (or otherwise) to support its argument that an event is the same thing as a feature. Tr. 31:1–5; see Helmsderfer v. Bobrick Washroom Equip., Inc., 527 F.3d 1379, 1381–82 (Fed. Cir. 2008) (“Our precedent instructs that different claim terms are presumed to have different meanings.”). Therefore, we determine that Petitioner has not shown by a preponderance of the evidence that claim 25 would have been obvious over Bace and Russinovich.” slip op. at 28

    Patent outcomesUS 7,448,084 mixed
    Claim construction§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 7,448,084
  • Sandisk Corporation v. Netlist, Inc.Some claims unpatentable
    PTAB · Dec 14, 2015 · IPR2014-00970 · APJ Linda M Gaudette · IPR · Final written decision

    Claims 1, 14, 15, 19–25, and 27–34 are unpatentable; the Board found other challenged claims not shown unpatentable on the grounds decided.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “The difference in the opinions of the two experts is that Dr. Sechen believes a person of ordinary skill in the art would have an additional four years of experience, education, or a combination of the two, beyond that proposed by Dr. Alpert. See Ex. 1009 ¶ 7. According to Dr. Alpert, the difference in the proposed levels of ordinary skill in the art is not material to any dispute over claim construction or patentability in this inter partes review. Id. We accord greater weight to Dr. Alpert’s opinion as to the level of ordinary skill in the art because he has experience in both teaching students and working with engineers in the industry, while Dr. Sechen’s experience is primarily in teaching. Compare Ex. 1007 ¶¶ 7, 21 with Ex. 2012 ¶¶ 3, 5. Moreover, based on our review of the ’434 patent and the types of problems and solutions described in the ’434 patent and cited prior art, we agree with Dr. Alpert’s opinion on the level of ordinary skill. Accordingly, we find that a person of ordinary skill in the art at the time of the ’434 patent would have a Bachelor’s degree in electrical engineering, computer engineering, or in a related field and at least one year of work experience relating to memory systems, and would be familiar with the design of memory devices, memory modules, and BIST.” slip op. at 10

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

      “The above disclosure uses the term “operable independently” to describe the data handlers as being discrete and functioning without being physically or logically connected to each other. Based on our review of the ’434 patent, the specification and claim 27 both use the term “operable independently” in the same manner, i.e., to describe a feature of the data handler that is distinct from its data generation feature. We agree with Petitioner, therefore, that when interpreted in the context of the ’434 patent in its entirety, the claim term “operable independently” “merely means that each data handler can operate without influence or control by any of the other data handlers.” Reply 5. The ’434 patent specification uses the term “operable independently” in accordance with its plain and ordinary meaning, and we find no basis for applying the narrower construction advanced by Patent Owner to any of the challenged claims. Accordingly, we interpret “operable independently” as “operable without influence or control by another.” See Cuozzo, 793 F.3d at 1278–79.” slip op. at 19

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Based on the above description in Averbuj, we agree with Patent Owner that Averbuj describes memory interfaces (the alleged data handlers) that are configured to produce address and control signals, and that Averbuj describes producing address and control signals in certain circumstances, e.g., when Averbuj’s sequencer (the alleged control module) specifies writing data in a particular pattern that requires transformation to conform to a particular configuration of a memory module. See PO Resp. 33. We also agree with Petitioner, however, that Averbuj’s memory interfaces are further configured to apply to the memory modules the same address and control signals received from, and produced by, the sequencers for testing (see Reply 15), e.g., when the sequencer sends signals that can be applied, without modification or transformation (see Ex. 1003 ¶ 56), directly to a memory module irrespective of its physical configuration. Thus, Petitioner has shown, by a preponderance of the evidence, that Averbuj’s sequencer meets the limitation of “a control module configured to generate address and control signals for testing the memory devices” as recited in challenged independent claims 1, 20, and 29 of the ’434 patent.” slip op. at 41

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successReasonable expectation not foundNot shown unpatentableNot shown unpatentable

      “As discussed in Section IV.B.2.e., a petition must include “[a] full statement of the reasons for the relief requested, including a detailed explanation of the significance of the evidence including material facts, and the governing law, rules, and precedent” (37 C.F.R. § 42.22(a)(2)), and “[a] reply may only respond to arguments raised in the corresponding . . . patent owner response” (37 C.F.R. § 42.23(b)). We agree with Patent Owner that the Reply does more than merely respond to or rebut arguments made in Patent Owner’s Response; rather, it sets forth a theory that was not presented clearly in the Petition. Patent Owner’s position is supported by the fact that Dr. Sechen, whose skill level is at least (and appears to exceed) that of the ordinary artisan, apparently was unable to envision how Huang and Averbuj could be combined. Further, Dr. Alpert’s second declaration includes, at a minimum, opinions as to the understanding of the ordinary artisan with respect to the teachings of Huang and Averbuj that were not presented in his first declaration. In our judgment, consideration by the Board of the above-noted arguments in the Reply and evidence presented in Dr. Alpert’s second declaration in support thereof would be improper under 37 CFR § 42.23 and unfair to Patent Owner. We have, however, reviewed and considered the arguments in the Petition and evidence therein, and are in agreement with Patent Owner that Petitioner has not provided adequate explanation or evidence to support its contention that one of ordinary skill in the art would have had a reasonable expectation of success in combining Huang and Averbuj. Accordingly, Petitioner has not met its burden to show, by a preponderance of the evidence, that claims 7–12, 17, 18, 20–25, 27, 28, and 30–35 would have been unpatentable over Huang and Averbuj.” slip op. at 59

    Patent outcomesUS 8,001,434 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 8,001,434
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 3, 2015 · IPR2013-00562 · APJ Scott A Daniels · IPR · Final written decision

    Claims 31, 41, and 42 are unpatentable: claim 31 is anticipated by Chang, and claims 41 and 42 are obvious over Chang with Webb and Chang with Horn, respectively.

    RulingsFinal written decision
    • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Decided for petitioner

      “implemented function is the algorithm disclosed in the specification.” Aristocrat Techs. Austl. Party Ltd. vs. Int’l Game Tech., 521 F.3d 1328, 1333 (Fed. Cir. 2008) (quoting Harris Corp. v. Ericsson Inc., 417 F.3d 1241, 1249 (Fed. Cir. 2005)). Additionally, specific portions of the specification must clearly link or associate a computer program or algorithm to the function corresponding to the claimed means. See Medical Inst. and Diag. Corp. v. Elektra AB, 344 F.3d 1205, 1211 (Fed. Cir. 2003). For the reasons set forth below, we conclude that the four steps and other ’604 patent specification portions identified by Enfish do not describe an algorithm for the recited function of “configuring memory according to a logical table.” We further conclude that Enfish has not clearly linked or associated the recited function to the four steps or the other portions of the ’604 patent specification that Enfish identifies.” slip op. at 11

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

      “We determine that adopting Enfish’s proposed construction without further context would create ambiguity. Additionally, limitations are not to be read into the claims from embodiments in the specification. See In re Van Geuns, 988 F.2d 1181 at 1184. Furthermore, we agree with Microsoft that Enfish relies on insufficient extrinsic evidence for support, for example, that an OID is “immutable.” We also note that Enfish’s contentions are not commensurate with the scope of the claims because each of the independent claims recites that an OID is included “to identify” each logical row and each logical column, but does not recite using an OID to retrieve data from memory. We, therefore, determine that the construction of “OID” in the Decision to Institute should not be changed.” slip op. at 18

    • Expert testimonyPatent owner expert creditedPetitioner expert discountedOther

      “We give little weight to Dr. Hosking’s testimony with respect to the limitations in claim 34 because he does not provide an explanation or evidence as to why Dickerson’s synchronization of data in the same column across separate databases teaches reciprocal synchronization between columns in the same table. Dr. Hosking states that a person of skill in the art would be motivated to combine Chang and “the synchronization concept as taught in Dickerson in the case that similar elements were to be reciprocally synchronized.” Ex. 1022 ¶ 225. The premise of this argument is the assumption that Dickerson’s synchronization across separate databases is the same as synchronizing two logical columns reciprocally in the same database table. Dr. Hosking does not provide support for this assumption. This argument, therefore, does not sufficiently explain why mirroring data across separate databases leads to data synchronization between logical columns in the same table. Dr. Hosking’s testimony does not explain why, or how, one of ordinary skill in the art would use the database management disclosed by Chang in cooperation with the linked database elements between separate databases to achieve reciprocal synchronization “to achieve such coordination of the data” between logical columns in the same table. See id. at ¶¶ 283–294.” slip op. at 41

    • Skill levelOther
    Patent outcomesUS 6,151,604 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 6,151,604
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 2, 2015 · IPR2013-00561 · APJ Barbara A Parvis · IPR · Final written decision

    Claims 46 and 54 were held unpatentable; claims 55, 56, and 60 were not shown unpatentable; claims 16, 24–26, and 30 were terminated because their means-plus-function limitation lacked sufficient disclosed structure.

    RulingsFinal written decision
    • BurdenMixed

      “Microsoft has shown by a preponderance of the evidence that claims 46 and 54 of the ’775 patent are unpatentable. Microsoft has not shown that claims 55, 56, and 60 of the ’775 patent are unpatentable. For the reasons discussed below, we are unable to reach a determination on the alleged grounds of unpatentability over prior art for claims 16, 24–26 and 30. Accordingly, we terminate this proceeding with respect to claims 16, 24–26 and 30 under 37 C.F.R. § 42.72.” slip op. at 3

    • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Decided for petitioner

      “1249 (Fed. Cir. 2005)). Additionally, specific portions of the specification must clearly link or associate a computer program or algorithm to the function corresponding to the claimed means. See Medical Inst. & Diag. Corp. v. Elektra AB, 344 F.3d 1205, 1211 (Fed. Cir. 2003). For the reasons set forth below, we conclude that the four steps and other ’775 patent specification portions identified by Enfish do not describe an algorithm for the recited function of “configuring memory according to a logical table.” We further conclude that Enfish has not clearly linked or associated the recited function to the four steps or the portions of the ’775 patent specification that Enfish identifies.” slip op. at 10

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

      “We determine that Enfish’s proposed construction of OID introduces requirements beyond what is needed for an OID to identify data and retrieve data from memory. Enfish, for example, contends that “an OID is unique among all rows and columns of the logical table.” PO Resp. 29. Additionally, claims 46 and 54 recite that an OID is included “to identify” each attribute set and each record, but do not specifically recite using an OID to retrieve data from memory.” slip op. at 14

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “80, PG 453, 471, 481, 482, 484, Ex. 1219 ¶¶ 67–93, 119–131). For example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses configuring memory according to a logical table, as recited in claim 54. In the cited portions above, Visual Basic discloses storing data in a computer formatted as a table object, which is “a logical representation of a physical table.” Ex. 1204, LR 558. The table object comprises “records (rows) and fields (columns).” Id. As an additional example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses each record and each attribute set including an OID, as recited in claim 54. In the cited portions above, Visual Basic describes assigning a primary key and that “[a] table’s primary key is the determining factor when testing to see if the record is unique within the table.” Ex. 1204, PF 39. According to Visual Basic “[Visual Basic] creates an index on the primary key of the table and uses it to find records and to create joins between tables.” Id. Regarding each column including an OID, according to Visual Basic, “[e]ach Field in the Fields collection of a TableDef has a unique value in the OrdinalPosition property.” Id. at LR 425. Furthermore, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses indexing data stored in the table and a cell including a pointer to an index record, as recited in claim 54. In the cited portions above, Visual Basic discloses an index object used for creating indexes to “speed up the process of finding records.” Ex. 1204, LR 276; see also id. at PF 37, 38, PG 482. Visual Basic also discloses a cell pointing to an index object. Id. at LR 280, PG 484.” slip op. at 17

    Patent outcomesUS 6,163,775 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
    Patents in suitUS 6,163,775
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 2, 2015 · IPR2013-00560 · APJ Barbara A Parvis · IPR · Final written decision

    Claims 47–48 are unpatentable as anticipated by Visual Basic, and claims 49–50 as obvious over Visual Basic and Jensen; claims 51–53 were not shown unpatentable, and claims 17–23 were terminated.

    RulingsFinal written decision
    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownNo construction neededDecided for patent owner

      “Enfish contends that our construction for “object identification number” is incomplete. PO Resp. 15. We evaluate Enfish’s contention below. Enfish also provides a proposed construction for “anchor,” recited in claims 21 and 51. PO Resp. 22. Because we determine that Microsoft has not met its burden with respect to these claims for other reasons, no construction of this term for the purposes of this Decision is necessary. We discern no reason, based on the complete record now before us, to change our constructions in the Decision to Institute of “logical table,” “object identification number,” and “attribute set.”” slip op. at 8

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “evidence, and the detailed claim analysis, which reads persuasively all elements of claim 47 onto the disclosure of Visual Basic. Pet. 33–46 (citing Ex. 1104, LR 162, 185, 280, 425, 484, 532, 558, PF 1, 3, 18, 37–39, 40, 47, 76, 80, PG 453, 471, 481, 482 ; Ex. 1119 ¶¶ 67–98). For example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses configuring memory according to a logical table, as recited in claim 47. In the cited portions above, Visual Basic discloses storing data in a computer formatted as a table object, which is “a logical representation of a physical table.” Ex. 1104, LR 558. The table object comprises “records (rows) and fields (columns).” Id.” slip op. at 16

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

      “2007 ¶ 231. In contrast to Dr. Jagadish’s statement, however, Jensen teaches an object-oriented application for managing information retrieved from a structured database, such as a relational database. Ex. 1106, Abstract. Enfish further contends that Microsoft does not explain why one of ordinary skill in the art would have been motivated to apply the pointers of Jensen to the indexing structure in Visual Basic. PO Resp. 35. We, however, are persuaded that Microsoft has shown a sufficiently articulated reason with rational underpinning to support obviousness (Pet. 48–49 (citing Ex. 1119 ¶¶ 387–404)). Microsoft, for example, states “[i]t was well known in the art at the time that indexes such as the index disclosed in [Visual Basic], maintain object identification numbers of the cell for locating data.” Pet. 49 (emphasis added). Microsoft continues, “Jensen discloses containing the address in a pointer, e.g., a physical memory address (i.e., OIDs).” Id. (citing Ex. 1106, 7:29–35). Dr. Hosking testifies “[i]t was well known in the art at the time that Index Objects locate data by maintaining object identification numbers in the internal pointers as disclosed in Jensen.” Ex. 1119 ¶ 403 (emphasis added). Dr. Hosking further testifies “[a] person of ordinary skill in the art would be motivated to combine Jensen’s teaching of maintaining the OIDs in a pointer with [Visual Basic’s] disclosure of identifying the logical columns / rows with the OIDs.” Ex. 1119 ¶ 404. The predictable use of familiar prior art elements according to their established functions renders the recited invention obvious. See KSR Int’l Co. v. Teleflex, Inc., 550 U.S. 398, 417 (2007).” slip op. at 19

    • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

      “invention, the totality of the evidence submitted, including objective evidence of nonobviousness, may lead to a conclusion that the claimed invention would not have been obvious to one with ordinary skill in the art. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). However, to accord substantial weight to objective evidence requires the finding of a nexus between the evidence and the merits of the claimed invention. In re GPAC Inc., 57 F.3d 1573, 1580 (Fed. Cir. 1995); see also In re Huang, 100 F.3d 135, 140 (Fed. Cir. 1996) (“success is relevant in the obviousness context only if there is proof that the sales were a direct result of the unique characteristics of the claimed invention.”). Enfish contends that the claimed invention received industry accolades, including praise from Microsoft, satisfied a long-felt need, resulted in success where others had failed, as well as commercial success. PO Resp. 42–47. Enfish points to features of claim 17, which Enfish contends are the features of the claimed invention that resulted in the objective indicia of success to which Enfish refers. Id. at 43–44. Claim 17 of the ’775 patent, however, is challenged on the basis that it is anticipated by Visual Basic. Secondary considerations do not weigh into determinations regarding anticipation. Cohesive Techs., Inc. v. Waters Corp., 543 F.3d 1351, 1364 (Fed. Cir. 2008). Because we conclude that Microsoft has not shown that claims 51–53 of the ’775 patent are unpatentable for other reasons, the only claims that we need to evaluate are dependent claims 49 and 50 of the ’775 patent. Microsoft asserts that claims 49 and 50 are obvious over the combination of Visual Basic with a reference that teaches referencing objects through two-way pointers. Pet. 49 (citing Ex. 1106, 7:29–35). Enfish has not shown a nexus between any of the accolades or successes it says occurred and the use of two-way pointers.” slip op. at 24

    Patent outcomesUS 6,163,775 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
    Patents in suitUS 6,163,775
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 2, 2015 · IPR2013-00563 · APJ Barbara A Parvis · IPR · Final written decision

    Claims 46–50 and 54 are unpatentable: claims 47, 48, and 54 as anticipated by Visual Basic; claim 46 as obvious over SQL-92 and Chawathe; claims 49 and 50 as obvious over Visual Basic and Jensen.

    RulingsFinal written decision
    • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Decided for petitioner

      “[T]he corresponding structure for a § 112 ¶ 6 claim for a computer- implemented function is the algorithm disclosed in the specification.” Aristocrat Techs. Austl. Party Ltd. vs. Int’l Game Tech., 521 F.3d 1328, 1333 (Fed. Cir. 2008) (quoting Harris Corp. v. Ericsson Inc., 417 F.3d 1241, 1249 (Fed. Cir. 2005)). Additionally, specific portions of the specification must clearly link or associate a computer program or algorithm to the function corresponding to the claimed means. See Medical Inst. & Diag. Corp. v. Elektra AB, 344 F.3d 1205, 1211 (Fed. Cir. 2003). For the reasons set forth below, we conclude that the four steps and other ’604 patent specification portions identified by Enfish do not describe an algorithm for the recited function of “configuring memory according to a logical table.” We further conclude that Enfish has not clearly linked or associated the recited function to the four steps or the portions of the ’604 patent specification that Enfish identifies. slip op. at 10

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner

      “Enfish contends that our construction for “object identification number” is incomplete. PO Resp. 16. We evaluate Enfish’s contention below. Enfish also provides contentions regarding two other terms: “anchor,” recited in claims 21 and 51, and “external documents,” recited in claims 30 and 60. PO Resp. 23. Because we determine that Microsoft has not met its burden with respect to these claims for other reasons, no construction of these terms for the purposes of this Decision is necessary. We discern no reason, based on the complete record now before us, to change our constructions in the Decision to Institute of “logical table” and “object identification number.”” slip op. at 9

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

      “We determine that Enfish’s proposed construction of OID introduces requirements beyond what is needed for an OID to identify data and retrieve data from memory. Enfish, for example, contends that “an OID is unique among all rows and columns of the logical table.” PO Resp. 32. Additionally, each of the independent claims recites that an OID is included “to identify” each logical row and each logical column, but does not specifically recite using an OID to retrieve data from memory.” slip op. at 15

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Pet. 31–43 (citing Ex. 1104, LR 162, 185, 276, 277, 280, 532, 425, 558, PF 1, 3, 18, 37–40, 47, 76, 80, PG 471, 481, 482, 484; Ex. 1119 ¶¶ 68–93, 119). For example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses configuring memory according to a logical table, as recited in claims 47 and 54. In the cited portions above, Visual Basic discloses storing data in a computer formatted as a table object, which is “a logical representation of a physical table.” Ex. 1104, LR 558. The table object comprises “records (rows) and fields (columns).” Id. As an additional example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses each row and each column including an OID, as recited in claims 47 and 54. In the cited portions above, Visual Basic describes assigning a primary key and that “[a] table’s primary key is the determining factor when testing to see if the record is unique within the table.” Ex. 1104, PF 39. According to Visual Basic “[Visual Basic] creates an index on the primary key of the table and uses it to find records and to create joins between tables.” Id. Regarding each column including an OID, according to Visual Basic, “[e]ach Field in the Fields collection of a TableDef has a unique value in the OrdinalPosition property.” Id. at LR 425. Furthermore, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses indexing data stored in the table, as recited in claims 47 and 54, and a cell including a pointer to an index record, as recited in claim 54. In the cited portions above, Visual Basic discloses an index object used for creating indexes to “speed up the process of finding records.” Ex. 1104, LR 276–277; see also” slip op. at 18

    Patent outcomesUS 6,151,604 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
    Patents in suitUS 6,151,604
Page 1 of 2
← Previous12Next →

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.