• Tesla, Inc. v. Intellectual Ventures II LLCSome claims unpatentable
  PTAB · Jul 1, 2026 · IPR2025-00222 · APJ Frederick C Laney · IPR · Final written decision

  Claims 1, 2, 4, 5, 8–11, 13, and 14 are unpatentable over Yu and Miyazaki; claims 15, 16, and 19 were not shown unpatentable over Matsushima.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art “at, and before, the earliest claimed priority date of the ’158 patent . . . would have had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field and 2–3 years of experience in digital imaging systems,” adding that “[l]ess experience may be sufficient with additional education, and likewise, less education may be sufficient with additional work experience.” Pet. 6–7 (citing Ex. 1003 ¶¶ 16–18). Patent Owner does not offer a competing definition or dispute Petitioner's articulation. Based on the entire record, we adopt Petitioner’s characterization of the level of skill for one of ordinary skill in the art because that characterization, we find, is consistent with the ’158 patent and the asserted prior art.” slip op. at 9

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

    “We determine that the claims require a per-channel determination of integration time—that is, an integration time arrived at for each sensor or channel individually—and cannot be satisfied by a single global value merely applied uniformly across the sensors. We do not, however, read the independent claims to require that the per-channel integration times differ from one another.” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed board ownDecided for patent owner

    “We adopt the definition clearly and unambiguously set forth in the specification, which was likewise adopted by the Court in the related litigation. See Pet. 7–8, 55; Pet. Reply 1–2 (district court construing the term to mean “the time the image sensor collects and integrates signal from the scene”). The specification states that the integrated photo-charge “is directly related to the time the image sensor collects and integrates signal from the scene,” and that “[t]his is known as integration time.” Ex. 1001, 4:4–7. Accordingly, the ’158 patent demonstrates that the inventors indisputably acted as a lexicographer for the term “integration time.”” slip op. at 13

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther

    “We construe “during a frame” to mean the period during which data for a single frame of an image is captured. The limitation is satisfied where the per-channel integration time is effectuated during the frame; it does not require that the integration time be re-determined mid-frame, nor does it require actuation of a “charge integration switch.” The specification’s only use of the phrase confirms this reading: “each camera channel is controlled during a frame under an independent integration time.” Ex. 1001, 3:45–50. Consistent with that usage, the specification describes selecting an integration time for each channel and then integrating the photo-signal “within a single frame of data,” and describes placing the charge-integration switch in a state to allow charge to accumulate for the selected period and then transferring the accumulated charge upon completion of the integration period. Id. at 4:51–54, 11:3–18. We decline Patent Owner’s proposal to require in-frame actuation of a charge-integration switch, for the same reason we decline to import that structure into “integration time.” We also decline to read the phrase to require mid-frame re-determination of the integration time, because the patent’s own embodiment selects an integration time and then integrates charge during the frame under that selected time. Ex. 1001, 4:51–54, 11:3– 18. So construed, “during a frame” is not redundant of the independentclaim limitation: it adds that the per-channel control occurs within a single frame (intrascene), as distinct from adjustment from one frame to the next (interscene).” slip op. at 15

  Patent outcomesUS 9,232,158 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,232,158
• Innoscience America, Inc. v. Infineon Technologies Americas Corp.No claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00175 · APJ Jo-Anne M Kokoski · IPR · Final written decision

  Claims 1–17 were not shown unpatentable because Petitioner failed to establish that Usui’s interconnect structure or Yu’s metal gate stacks satisfy the construed “electrode stack” limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “(“POSITA” or “POSA”) would have had “at least a four-year degree in electrical engineering or a closely related field, and at least two years of experience in semiconductor device design,” and “[a]dditional education could substitute for professional experience and vice versa.” Pet. 6 (citing Ex. 1002 ¶¶ 80–82). Patent Owner does not dispute Petitioner’s proposed level of ordinary skill. PO Resp. 1–76. Neither party explains why the outcome of this case would be affected by the adoption of the proffered definition of a person of ordinary skill in the art. In the Institution Decision, we adopted the assessment offered by Petitioner. Dec. 6–7. Because Petitioner’s definition of the level of skill in the art is consistent with the ’562 patent and the asserted prior art, we maintain Petitioner’s definition for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir 2001).” slip op. at 9

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

    “comprises the recited metals and has the recited thickness, which forms an electrical contact for use on a semiconductor device generally or a group III- V semiconductor in particular. This is consistent with our determination that “electrode stack” is a conductor that provides a path for current entering or leaving a medium such as a semiconductor device We disagree with Patent Owner that “electrode stack” as used in the challenged claims should be limited to the specific electrodes shown in the embodiments described in the Specification. See PO Resp. 4–9. Although the Specification describes embodiments using source, drain, and Schottky gate electrodes as electrical contacts, we see no reason to construe the term “electrode stack” itself to be limited to these components as Patent Owner proposes. Claims 1 and 13 expressly recite that electrode stacks comprise the claimed “electrical contact,” without expressly including or precluding any specific type of electrode. Ex. 1001, 5:54–63, 6:37–47. The Federal Circuit advises that the Specification “is not a substitute for, nor can it be used to rewrite, the chosen claim language. ‘Specifications teach. Claims claim.’” SuperGuide, 358 F.3d at 875 (quoting SRI Int’l v. Matsushita Elec. Corp. of Am., 775 F.2d 1107, 1121 n.14 (Fed. Cir. 1985) (en banc)). The Specification does teach electrical contacts that include source, drain, and Schottky gate electrodes, but claims 1 and 13 are directed to electrical contacts that are not expressly so limited. Patent Owner’s proposed construction would effectively rewrite the claim by adding limitations, which we decline to do under the guise of claim construction. See id. (“Though understanding the claim language may be aided by the explanations contained in the written description, it is important not to import into a claim limitations that are not a part of the claim.”). In view of the foregoing, we construe the claim term “electrode stack” to mean “a conductor that provides a path for current entering or leaving a medium such as a semiconductor device.”” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential). In contrast, Patent Owner’s declarant Dr. Piner testifies, with evidentiary support, that interconnects (such as Usui’s interconnect metallurgy structure) and electrical contacts (such as that claimed in the ’562 patent) are not the same thing. See Ex. 2024 ¶¶ 63–70. For example, Dr. Piner explains: In other words, not all metals in a semiconductor device have the same purpose and could not be said to be interchangeable. By August 2009 it was well known to a POSA how to discern if a metal component in a transistor is an interconnect or serves as an electrical contact such as a gate contact or ohmic contact, based on the structure and functionality of the metal component. For example, interconnects are made up of metal strips and are deposited on insulators. EX-1011 (Mishra) at 216. Interconnects are low resistance conductors that can carry very high current densities. Id., 216, 217. Unlike Schottky contacts and ohmic contacts, interconnects do not provide non-linear IV response like Schottky contacts nor inject electrons and holes into semiconductors like ohmic contacts. Id., 218. As many of the references cited by Dr. Zhao illustrate, electrical contacts had their own highly complex design challenges. EX-1008 (Pearton), 41-59 (Pages 53-71 of 383) (discussing electrical contacts); EX-1017 (Kramer), 11-126 (Pages 18-130 of 151) (same). And while Dr. Zhao cites these as supporting a POSA’s knowledge of an electrical contact, none of these references describe electrical contacts as interconnects. Id. ¶ 71. Dr. Piner further testifies that Usui’s interconnect metallurgy structure is an interconnect, and not an electrical contact, because “Usui states that ‘[t]he structures fabricated by the process of the present invention are especially useful for forming electrical connections or wiring such as between active and/or passive devices of an integrated circuit structure.’” Id. ¶ 148 (citing Ex. 1004, 1:11–14) (alteration in original); see also id. ¶¶ 150– 151 (Dr. Piner testifying that Usui’s interconnect metallization structure is not an “electrode stack” under a broad definition of electrode). Dr. Piner’s testimony in this regard rebuts Petitioner’s and Dr. Zhao’s conclusory assertions to the contrary.” slip op. at 21

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “conductor that provides a path for current entering or leaving a medium such as a semiconductor device.” Thus, Petitioner must show that Usui’s layers 13–15, 18, and 19 provide a path for current entering or leaving a medium such as a semiconductor device. After reviewing the complete trial record, we are not persuaded that Petitioner has done so. Petitioner relies on the testimony of Dr. Zhao to support its contention that the identified layers in Usui’s interconnect metallurgy structure form an “electrode stack including a plurality of metal layers and a capping layer formed over said plurality of metal layers” as recited in claim 1. See Pet. 11–12 (citing Ex. 1002 ¶¶ 89–91). Neither Petitioner nor Dr. Zhao, however, provide adequate explanation or evidence as to why Usui’s interconnect metallurgy structure forms an “electrode stack,” i.e., a conductor that provides a path for current entering or leaving a medium such as a semiconductor device. Dr. Zhao’s testimony merely repeats the disclosures in Usui and concludes, without further technical detail, explanation, or reference to objective evidence, that Usui’s Figure 8 discloses an electrode stack. Ex. 1002 ¶¶ 89–91. Dr. Zhao’s testimony sets forth Petitioner’s conclusory assertions as though they are facts, rather than setting forth facts and evidence in support of those assertions. Compare id. with Pet. 11–12. Absent underlying facts or evidence to support Dr. Zhao’s opinion, the cited testimony “adds little to the conclusory assertion for which it is offered to support, and is entitled to little weight.” Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 at 15 (PTAB Aug. 24, 2022) (precedential).” slip op. at 21

  Patent outcomesUS 8,686,562 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,686,562
• Kubota North America Corporation v. Vermeer Manufacturing CompanySome claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00167 · APJ Meredith C Petravick · IPR · Final written decision

  Claims 1–13, 21, 22, 64, and 65 are unpatentable over the asserted grounds; claims 15, 17, 19, 20, 23–30, 66, and 67 were not shown unpatentable over KR996, JP705, and Beltrami.

  RulingsFinal written decision

  • ExcludeMotion to exclude, deniedDenied

    “B. Analysis “The moving party has the burden of proof to establish that it is” slip op. at 9

  • Skill levelOther

    “B. Level of Ordinary Skill in the Art We review the grounds of unpatentability in view of the” slip op. at 21

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

    “lexicographical, we agree with the parties that “mainframe” is not limited to a single weldment. Pet. Init. CC Br. 1; PO Init. CC Br. 1–2. Instead, a single-weldment “mainframe” is merely one disclosed embodiment. See Pet. Init. CC Br. 3 (stating that “by including the term ‘generally’ in a statement, the feature (i.e., single weldment) is expressly identified as merely included in some, but not all embodiments”); PO Init. CC Br. 3 (“This language is merely exemplary, using reference numerals to refer to the embodiment’s features and qualifying ‘single weldment’ as referring ‘generally’ to specific embodiments.”). The Iowa District Court reached the same conclusion. See Ex. 1020 at 4 (holding that “‘mainframe’ will be given its plain and ordinary meaning and does not require a single weldment” (emphasis added)), cited at Pet. Init. CC Br. 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”).” slip op. at 33

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

    “probative and cogent evidence in the record” and “may often establish that an invention appearing to have been obvious in light of the prior art was not.” Transocean Offshore Deepwater Drilling, Inc. v. Maersk Drilling USA, Inc., 699 F.3d 1340, 1349 (Fed. Cir. 2012). Thus, notwithstanding what the teachings of the prior art would have suggested to one skilled in the art, secondary considerations (objective evidence of non-obviousness) may lead to a conclusion that the challenged claims would not have been obvious. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). Our obviousness analysis includes consideration and weighing of Patent Owner’s objective indicia of non-obviousness.” slip op. at 55

  Patent outcomesUS 9,321,386 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,321,386
• Kubota North America Corporation v. Vermeer Manufacturing CompanySome claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00171 · APJ Eric C Jeschke · IPR · Final written decision

  Claims 1–13 and 28 are unpatentable over KR996; claims 14–16 and 19–27 were not shown unpatentable over Bares and Beltrami.

  RulingsFinal written decision

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

    “(“This language is merely exemplary, using reference numerals to refer to the embodiment’s features and qualifying ‘single weldment’ as referring ‘generally’ to specific embodiments.”). The Iowa District Court reached the same conclusion. See Ex. 1020 at 4 (holding that “‘mainframe’ will be given its plain and ordinary meaning and does not require a single weldment” (emphasis added)), cited at Pet. Init. CC Br. 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”). Turning to the prosecution history, neither Petitioner nor Patent Owner has highlighted any specific statements that impact the scope of the term “mainframe.” And from our independent review, we do not discern any such statements. For these reasons, the intrinsic evidence as a whole supports construing “mainframe” as a primary supporting structure.” slip op. at 35

  • Obviousness (§103) › Objective indicia / secondary considerationsObjective indicia no nexusNot shown unpatentable

    “probative and cogent evidence in the record” and “may often establish that an invention appearing to have been obvious in light of the prior art was not.” Transocean Offshore Deepwater Drilling, Inc. v. Maersk Drilling USA, Inc., 699 F.3d 1340, 1349 (Fed. Cir. 2012). Thus, notwithstanding what the teachings of the prior art would have suggested to one skilled in the art, secondary considerations (objective evidence of non-obviousness) may lead to a conclusion that the challenged claims would not have been obvious. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). Our obviousness analysis includes consideration and weighing of Patent Owner’s objective indicia of non-obviousness.” slip op. at 54

  • ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part

    “For these reasons, we are persuaded by Petitioner to exclude, as” slip op. at 28

  Patent outcomesUS 10,202,266 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 10,202,266
• Resmed Corp. v. Cleveland Medical Devices, Inc.No claims unpatentable
  PTAB · Jun 29, 2026 · IPR2025-00247 · APJ Cynthia M Hardman · IPR · Final written decision

  Claims 1–19 were not shown unpatentable under any of six obviousness grounds because Truitt did not teach or suggest the claimed severity calculation and index, and the Mumford combinations lacked the required sensor disclosures.

  RulingsFinal written decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “Patent Owner filed an authorized Motion to Terminate, alleging that Petitioner failed to name its corporate parent, Resmed Inc., as a real party in interest. Paper 29. Petitioner filed an opposition. Paper 31. Patent Owner filed a reply. Paper 32. We denied the Motion to Terminate. Paper 40.” slip op. at 2

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

    “disorder symptoms” require a “quantitative” calculation or use of an algorithm, we also disagree. See PO Resp. 14–16. First, nothing in the language of the claims themselves describes or requires a “quantitative” calculation or an algorithm. See generally Ex. 1001, 23:6–26:59. To be sure, the ’029 patent discloses embodiments that use known algorithms to “quantify the level of severity of the subject’s sleeping disorder or symptoms.” See, e.g., id. at 20:16–19. But the Specification does not require an algorithm. The Specification also indicates that quantification is merely “preferable” (i.e., not required), and is merely one embodiment. See, e.g., id. at 19:8–12 (“The signals from the one or more sensors used in various embodiments of the present invention are preferably analyzed using a processor and software that can quantitatively estimate or determine the severity of the subject’s sleeping disorder or symptoms.”) (emphasis added), 4:51–59 (“Finally, in still another embodiment, the present invention includes a sleeping disorder treatment system comprising a device for diagnosing and creating a quantitative output of a level of severity of a subject’s sleeping disorder or symptoms . . . .”) (emphasis added); see also Reply 5–6 (citing Ex. 1001, 4:3–59 and 19:8–12 and stating that the ’029 patent lists “numerous embodiments where only one of seven include a quantitative assessment”). Elsewhere, the Specification more generally states that signals from sensors are “analyzed to determine the level of severity of the symptoms,” without specifying that such analysis must be “quantitative” or performed by an algorithm. See Ex. 1001, 3:41–44. In view of these disclosures, Patent Owner does not persuade us to adopt its narrowing claim construction. Indeed, our reviewing court has “repeatedly warned against confining the claims” to specific embodiments disclosed in the Specification. Phillips, 415 F.3d at 1323. Patent Owner’s reliance on a prior Board decision in PGR2024- 00012, which related to the parent of the ’029 patent, is unavailing. See PO Resp. 15–16. We agree with Petitioner that in the cited case, “[t]he Board made no findings about the meaning of the term calculating ‘the data of a severity of the sleep disorder symptoms of the subject’ for claim construction.” Reply 8. Indeed, neither party offered any claim construction, and the Board determined that no claim construction was necessary for purposes of that decision. See ResMed Corp., PGR2024- 00012, Paper 7 at 8. The page of the decision Patent Owner cites addresses written description support in the specification for the claims challenged in that PGR, not claim construction. See id. at 16. In any event, the cited decision is a decision on institution. The Board’s statements there are, by nature, preliminary findings and conclusions based on a preliminary record, and are not binding here. For at least the above reasons, Patent Owner does not persuade us to adopt its narrowing claim construction and we find that the term “data of a severity” does not need construction because the words of the term are clear on their face.” slip op. at 31

  • Strike new argumentNew argument disregardedDecided for patent owner

    “skilled artisan would have incorporated only portions of Mumford’s algorithm into Truitt’s PAP (i.e., only those portions related to “the detection of sleep disordered events” and not the portions of the algorithm related to “determin[ing] sleep stage”) comes too late because this argument was not in the Petition. See, e.g., Wasica Fin. GmbH v. Cont’l Auto. Sys., Inc., 853 F.3d 1272, 1286–87 (Fed. Cir. 2017) (rejecting petitioner’s “attempts to cure the petition’s deficiencies in its subsequent briefing to the Board”). The Petition does not discuss modifying Mumford’s sleep efficacy algorithm before incorporating it into Truitt’s PAP device or incorporating only certain features of the algorithm. Indeed, the Petition and Dr. Kirkness rely on Mumford’s ability to detect sleep arousals when mapping Mumford to the claimed “data of a severity” and “index.” See Pet. 69–70; Ex. 1003 (Kirkness Decl.) ¶¶ 323–325. Mumford discloses that the mask electrodes detect arousals. See Ex. 1009 (Mumford) 2:4–10, 11:39–48. The same lack of disclosure plagues Petitioner’s belated Reply argument that Truitt’s ports 74 and 76 can incorporate electric sensing elements that would have functioned similar to Mumford’s electrodes. See Reply 22. The Petition did not mention ports 74 and 76 or otherwise suggest that a skilled artisan would have added functionality similar to Mumford’s electrodes to Truitt’s PAP, and we find that it is too late on Reply for Petitioner to posit this modification.” slip op. at 40

  • Expert testimonyPetitioner expert creditedPatent owner expert creditedMixed

    “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). This is especially applicable to Dr. Jafari’s opinions. His declaration was not prepared for this proceeding and thus Dr. Jafari was not subject to cross examination in this proceeding. See Reply 6 n.3. Moreover, Dr. Jafari was not opining on claim construction; rather, he was addressing the alleged indefiniteness. See Ex. 2020 (Jafari Decl.) 12 (heading addressing definiteness), ¶¶ 41–42, 46. Additionally, paragraphs 41–42 of Dr. Jafari’s declaration discuss claim terms phrases in a different patent (US 11,375,921), which explicitly include the terms “quantified” and “quantitative.” See Reply 6–7; Ex. 2020 (Jafari Decl.) ¶ 34. For at least these reasons, Patent Owner has not persuaded us that Dr. Jafari’s testimony is applicable here. Further, regarding the portion of Patent Owner’s proposed construction reciting “the degree of deviation from the baseline characteristics of a patient without sleep disorder symptoms,” Dr. Borkholder does not do his own analysis, but instead simply states that he “agree[s] with the litigation claim construction opinions of Dr. Jafari.” Ex. 2019 (Borkholder Decl.) ¶ 53. This is insufficient, and thus we do not credit Dr. Borkholder’s testimony regarding claim construction. We instead credit Dr. Kirkness’s statement that “[s]everity data is frequently calculated as the deviation from baseline characteristics of the patient himself, not a generic person ‘without sleep disorder symptoms.’” Ex. 1071 (Kirkness Reply Decl.) ¶ 13; Reply 9. As Dr. Kirkness explains, and Patent Owner does not dispute (see generally Sur-reply), “[t]he ‘baseline characteristics of a [generic] patient without sleep disorder symptoms’ would be irrelevant to any particular patient with their own unique breathing patterns and sleep disorder symptoms.” Ex. 1071 (Kirkness Reply Decl.) ¶ 13 (second alteration in original). For at least these reasons, we reject Patent Owner’s proposed claim construction.” slip op. at 30

  Patent outcomesUS 11,872,029 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,872,029
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jun 23, 2026 · IPR2025-00219 · APJ Frederick C Laney · IPR · Final written decision

  Claims 11–22 were not shown unpatentable under any § 103 ground because the prior art did not teach or suggest receiving the claimed resource allocation and multi-level TPC command on one physical channel.

  RulingsFinal written decision

  • BurdenNot shown unpatentable

    “onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). Moreover, a petitioner should 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284 (2011), amended 35 U.S.C. § 103, effective March 16, 2013. Because the application from which the ’153 patent issued claims priority to an application filed before this date, the pre-AIA version of § 103 applies. not “place the burden on [the Board] to sift through information presented by the Petitioners, determine where each element [of the challenged claims] is found in [the cited references], and identify any differences between the claimed subject matter and the teachings of [the cited references.]” Google Inc. v. EveryMD.com LLC, IPR2014-00347, Paper 9 at 25 (PTAB May 22, 2014).” slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “The second and third asserted benefits—reduced complexity and reduced latency—rest on the declaration of Dr. Kotzin (Ex. 1003 ¶ 64) rather than on any disclosure of Andersson or Khan. We accord that testimony little weight on this point because it asserts the benefits in conclusory terms without explaining why they would result from inserting a scheduling grant into Andersson’s undefined “other bits,” as distinct from Khan’s separate-slot design.” slip op. at 20

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A. Level of Ordinary Skill in the Art Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 14. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’500 Patent. Therefore, we adopt it as the ordinary level of skill of an artisan in the field of the patented technology for our analysis below.” slip op. at 7

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

    “Patent Owner offers a proposed construction for the recited “single physical channel” found in limitation 11.2 and “an accumulation of TPC commands” found in independent claims 12 and 18. PO Resp. 9–17. Petitioner likewise addresses the scope of an accumulation of TPC commands, but Petitioner does not contest directly Patent Owner’s proposed construction for “single physical channel.” Pet. Reply 2–7. We determine, however, that no express construction of any claim term is necessary to resolve the dispute between the parties. Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 8

  Patent outcomesUS 9,706,500 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,706,500
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jun 22, 2026 · IPR2025-00217 · APJ Frederick C Laney · IPR · Final written decision

  The Board held claims 1–5, 10–15, and 20 not unpatentable under four §103 grounds because the petitioner did not establish the claimed enabled-accumulation indication or single-channel combination.

  RulingsFinal written decision

  • BurdenNot shown unpatentable

    “onset to show with particularity why the patent it challenges is 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284 (2011), amended 35 U.S.C. § 103, effective March 16, 2013. Because the application from which the ’153 patent issued claims priority to an application filed before this date, the pre-AIA version of § 103 applies. 2 US 6,334,047 B1, iss. Dec. 25, 2001 (Ex. 1009). 3 US 2001/0036238 A1, pub. Nov. 1, 2001 (Ex. 1010) 4 US 2004/0190485 A1, pub. Sept. 30, 2004 (Ex. 1005). 5 US 2004/0077370 A1, pub. Apr. 22, 2004 (Ex. 1008). 6 US 6,600,772 B1, iss. July 29, 2003 (Ex. 1004). 7 US 6,529,741 B1, iss. Mar. 4, 2003 (Ex. 1007). unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). Moreover, a petitioner should not “place the burden on [the Board] to sift through information presented by the Petitioners, determine where each element [of the challenged claims] is found in [the cited references], and identify any differences between the claimed subject matter and the teachings of [the cited references].” Google Inc. v. EveryMD.com LLC, IPR2014-00347, Paper 9 at 25 (PTAB May 22, 2014).” slip op. at 5

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A. Level of Ordinary Skill in the Art Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 15. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’153 patent. Therefore, we adopt it as the ordinary level of skill of an artisan in the field of the patented technology for our analysis below.” slip op. at 7

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “apparent agreement between the parties: “TPC command accumulation” refers to a process that collects and uses TPC commands from a network device to cumulatively affect transmission power. And having studied the intrinsic record of the ’153 patent, we are in accord. But, we decline to further limit the construction of “TPC command accumulation” in the manner proposed by either party––i.e., (1) each TPC command adjustment must be summed to cumulatively affect transmission power (as proposed by Petitioner) or (2) a TPC command value must be added to an integrator. Although both parties are able to point to disclosures in the ’153 Patent where the TPC command accumulation of an exemplary embodiment is described as using an integrator and/or summing each TPC command adjustment to cumulatively affect a UE’s transmission power (PO Resp. 16 (citing Ex. 1001, 3:39–43, 7:15–29, 9:27–42; Ex. 2016 ¶¶ 35–42); Pet. Reply 4–5 (citing Ex. 1001, 3:39–43, 7:2–6, 7:8–22, 9:28–40)), neither party has demonstrated persuasively that the intrinsic record of the ’153 Patent demonstrates a clear intent to limit “TPC command accumulation” to those particular embodiments.” slip op. at 11

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

    “A rationale supports obviousness only where the proffered benefit would flow from the specific modification proposed; a benefit that the prior art realizes in a different structural context does not, without more, establish that the same benefit would result from inserting one reference’s element into the other. On this record, the nexus between Khan’s benefits and Petitioner’s “other bits” modification is missing.” slip op. at 40

  Patent outcomesUS 10,952,153 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,952,153
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

  Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms … that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). D.” slip op. at 12

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

    “search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24

  Patent outcomesUS 7,370,035 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,370,035
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23

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

    “different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27

  Patent outcomesUS 10,552,490 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 10,552,490
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

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

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

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

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139

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.