• Guardant Health, Inc. v. University Of WashingtonNo claims unpatentable
  PTAB · Oct 14, 2026 · IPR2022-00817 · APJ Zhenyu Yang · IPR · Remand

  On remand, the Board found Travers ’075 did not enable RCR amplification followed by SMRT sequencing and held claims 1–30 not shown unpatentable under the asserted obviousness grounds.

  RulingsRemand decision

  • RemandOther

    “B. Scope on Remand On remand, we are bound by the terms of the Federal Circuit’s mandate. Intell. Pixels Ltd. v. Sony Interactive Ent. LLC, 181 F.4th 1216, 1220 (Fed. Cir. 2026) (“An administrative agency is bound by the mandate of a reviewing court much as a lower court is bound by the mandate of a higher court.”). According to the Federal Circuit, on appeal, Patent Owner “UW argues that ‘Travers ’075 does not enable the sequencing of an RCR concatemer using PacBio’s SMRT sequencing,’ and therefore because paragraph 122 is not enabled, it cannot be relied on for disclosing amplification followed by sequencing.” Paper 50, 14. Because “[t]he Board did not reach this issue,” the Federal Circuit “remand[ed] the case for consideration of this issue by the Board in the first instance.” Id. Thus, consistent with the court’s mandate, we must decide “whether Travers ’075 enabled RCR amplification followed by SMRT sequencing.” Id. at 8.” slip op. at 4

  • BurdenNot shown unpatentable

    “A prior art reference is presumed to be enabled. Amgen, Inc. v. Hoechst Marion Roussel, Inc., 314 F.3d 1313, 1355 (Fed. Cir. 2003) (holding that “a presumption arises that both the claimed and unclaimed disclosures in a prior art patent are enabled”); In re Antor Media Corp., 689 F.3d 1282, 1288 (Fed. Cir. 2012) (extending the presumption to prior art printed publications). A patent owner, however, may present persuasive evidence that the relevant disclosures of a prior art are not enabled and therefore are not pertinent prior art. Amgen, 314 F.3d at 1355; In re Antor Media, 689 F.3d at 1289 (discussing the applicant’s burden to submit rebuttal evidence of nonenablement during prosecution); Apple Inc. v. Corephotonics, Ltd., 861 Fed. App’x. 443, 450 (Fed. Cir. 2021) (“[R]egardless of the forum, prior art patents and publications enjoy a presumption of enablement, and the patentee/applicant has the burden to prove nonenablement for such prior art.”). “[T]here is no absolute requirement for a relied-upon reference to be self-enabling in the § 103 context, so long as the overall evidence of what was known at the time of invention establishes that a skilled artisan could have made and used the claimed invention.” Raytheon Techs. Corp. v. Gen. Elec. Co., 993 F.3d 1374, 1376–77 (Fed. Cir. 2021). But, “if an obviousness case is based on a non-self-enabled reference, and no other prior art reference or evidence would have enabled a skilled artisan to make the claimed invention, then the invention cannot be said to have been obvious.” Id. at 1377.” slip op. at 15

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached

    “The Federal Circuit stated that “the elements of the challenged claim are expressly taught by Travers ’075. Travers ’075 discloses performing RCR amplification followed by SMRT sequencing in a single embodiment.” Paper 50, 14. As a result, “no finding regarding a motivation to combine to arrive at those claimed elements is required.” Id. at 9. In addition, it was error to require Petitioner to show that a skilled artisan “would have had a reasonable expectation of success in performing RCR replication of SMRTbell templates followed by SMRT sequencing.” Id. at 13. “Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.” Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999). Therefore, the only issue for us to decide is “whether Travers ’075 enabled RCR amplification followed by SMRT sequencing.” Paper 50, 8.” slip op. at 14

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “polymerase-template complexes in the same ZMW.” Id. (citing Ex. 1035, 39). Citing the Larrea Declaration, Petitioner contends that loading of multiple templates “is easily mitigated.” Id. at 18 (citing Ex. 1033 ¶ 19; Ex. 1035, 39). We are not persuaded by this argument either. Dr. Larrea testifies that one of the two methods to “easily mitigate[]” loading multiple templates into a single ZMW is “bioinformatically trimming the read to only the high-quality region (HQR).” Ex. 1033 ¶ 19. Dr. Larrea, however, provides no support for this testimony. In fact, he does not even explain what a “high-quality region (HQR)” is. We, thus, accord little weight to this testimony. See Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 9 (August 24, 2022) (precedential) (holding “conclusory and unsupported” declaration testimony is entitled to little weight).” slip op. at 26

  Patent outcomesUS 10,760,127 not shown unpatentable
  § 103 obviousness
  Patents in suitUS 10,760,127
• Resmed Corp. v. Cleveland Medical Devices, Inc.All claims unpatentable
  PTAB · Jun 29, 2026 · IPR2025-00246 · APJ Cynthia M Hardman · IPR · Final written decision

  Claims 15–29 are unpatentable as obvious over the asserted combinations; the contingent motion to amend claims 30–41 is denied for lack of written-description support.

  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 39. Petitioner filed an opposition. Paper 42. Patent Owner filed a reply. Paper 43. We denied the Motion to Terminate. Paper 51.” slip op. at 3

  • Skill levelSkill level board ownOther

    “understanding of a person of ordinary skill in the art at the time the invention was made.10 See Graham, 383 U.S. at 17–18. The parties agree that a person of ordinary skill in the art (sometimes referred to herein as “POSITA”) would have had: at least a bachelor’s degree in mechanical engineering, electrical engineering, computer science, biomedical engineering, or a similar technical field, with at least two years of relevant product design experience working with diagnostic sensor systems and network data systems, such as networked PAP machines. Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Pet. 3–4 (citing Ex. 1003 (Kirkness Decl.) ¶ 44); PO Resp. 4. 9 Patent Owner does not assert any objective indicia of nonobviousness. See generally PO Resp. 10 For purposes of this Decision, we apply a priority date of November 4, 2005. See supra n.4. Because the proposed level of ordinary skill in the art is consistent with the cited prior art and is undisputed on this record, we adopt it for purposes of this Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (indicating that the prior art itself may reflect an appropriate skill level).” slip op. at 9

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

    “Patent Owner does not persuade us to construe the term as “a value [or calculated value] that indicates how dire a patient’s symptoms are.” Patent Owner points to nothing in the intrinsic record that purportedly supports this construction, and we agree with Petitioner that “the patent specification’s disclosures regarding determining a level of symptom severity are broad, establishing that it can generally be derived from any sensor data and/or breathing events.” Pet. Reply 3–4; see also Ex. 1001, 3:44–46 (“Signals from the[] sensors are then analyzed to determine the level of severity of the symptoms of the subject’s sleep disorder.”). Patent Owner relies only on expert declarations to support its construction. But as indicated by the Federal Circuit, extrinsic evidence is “less significant than the intrinsic record in determining ‘the legally operative meaning of claim language.’” Phillips v. AWH Corp., 415 F.3d 1303, 1317 (Fed. Cir. 2005). This is especially applicable here, where neither Dr. D’Ambrosio’s nor Dr. Schwartz’s declaration was prepared for this proceeding, and neither declarant was subject to cross examination on their opinions. Moreover, neither of the declarants was opining on claim construction; rather, they were addressing indefiniteness and/or written description issues. See Ex. 1058 at 7 (heading addressing definiteness); Ex. 2026 at 18 (heading addressing written description). Further, Dr. Schwartz appears to have been making an argument about certain patent claims (not the challenged ’333 patent) based on Patent Owner’s own statements made during prosecution of a separate patent application. See Ex. 2026 ¶ 47 (“[T]he similar term used in the ’284 patent claims (‘data of severity of sleep disorder symptoms’) does not find written description support in the specification by a disclosure of the same statistics disclosed in Wright, because CleveMed argued those statistics are not related to severity of sleep disorder symptoms.” (emphasis added)). Patent Owner has not persuaded us that Dr. Schwartz’s testimony has direct applicability to the claim term at issue here. Dr. Borkholder’s testimony is likewise unpersuasive. Aside from citing Dr. D’Ambrosio’s and Dr. Schwartz’s declarations, Dr. Borkholder cites Exhibits 2027 and 2016. These exhibits discuss indices such as AHI and RDI that are used to assess the severity of a patient’s symptoms, but Patent Owner has not adequately explained how they bear on construction of the claim term at issue here, which is not addressed in these exhibits. Ex. 2022 ¶¶ 32–33. Accordingly, we accord Dr. Borkholder’s claim construction opinions little weight, because they are unsupported by reference to objective, corroborating evidence of record. See, e.g., Ashland Oil, Inc. v. Delta Resins & Refractories, Inc., 776 F.2d 281, 294 (Fed. Cir. 1985) (“Lack of factual support for expert opinion going to factual determinations . . . may render the testimony of little probative value in a validity determination.”); Xerox Corp. v. Bytemark, IPR2022-00624, Paper 9, 15 (PTAB 2023) (precedential) (explaining that declaration testimony that “is conclusory and unsupported” and which “adds little to the conclusory assertion for which it is offered to support . . . is entitled to little weight”).” slip op. at 23

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

    “We find that Petitioner has the better argument. Tidal volume refers to “the volume of air that is inspired or expired during a respiratory cycle.” Ex. 2028, 13–14; PO Resp. 10. “[H]ypopnea events are defined as a reduction of ≥50 % or 74 % in tidal volume from baseline and apnea events as absence of tidal volume for at least 10s.” Ex. 2028, 13–14 (emphasis omitted). Toge teaches that a control unit analyzes collected data (e.g., the flow rate) and calculates tidal volume. Ex. 1044 (Toge) ¶¶ 34–38. The calculated tidal volume is “a quantified level of severity data based on the subject’s sleep apnea symptoms during the therapy” because it represents, e.g., the “level of airway obstruction the patient experiences during the sleep apnea treatment using the PAP device.” Pet. 15. As Dr. Chatterjee explains: Toge discloses that tidal volume Fp is a quantified level of data because Toge discloses that Fp is monitored with respect to threshold values (id., [0051]) and because Fp is a function of Ft, Fa, and Fb, which are quantitative values. Toge discloses that tidal volume Fp is severity data because Toge discloses that tidal volume is indicative of whether the patient’s breathing warrants “emergency measures” (id., [0039]) and whether to “send an alert” in “an emergency where the patient’s breathing has drastically weakened” (id., [0055]). . . . . Because Toge discloses determining tidal volume (determine a quantified level of severity data) based on Ft, Fa, and Fb (id., [0035]), which corresponds to the subject’s condition (subject’s sleep apnea symptoms) while using the device (during the therapy) (id., [0036], [0037]), Toge discloses determin[ing] a quantified level of severity data based on the subject’s sleep apnea symptoms during the therapy. Ex. 1005 (Chatterjee Decl.) ¶¶ 122–125. Patent Owner’s attempt to dismiss tidal volume as a mere “breathing metric” is unavailing. First, Petitioner correctly “notes that in the paragraph PO cites to in Dr. Schwartz’s declaration, he indicates that breathing metrics are a level of severity data.” Pet. Reply 8 (citing Ex. 2026 ¶ 46 (“standard sleep disordered breathing metrics” [ ] were well validated indicators of the type and severity of sleep disordered breathing”)). Second, Dr. Kirkness explains that tidal volume represents the level of airway obstruction, e.g., apnea “is the most severe form of reduction in airflow [and] the absence of airflow results in quantified tidal volume of zero milliliters per breath.” Ex. 1003 (Kirkness Decl.) ¶¶ 157, 159; see also PO Resp. 10–11 (Patent Owner recognizing that an apnea is defined as absence of tidal volume for at least 10 seconds). The calculated tidal volume thus indicates severity because it is used to adjust the PAP system, e.g., in the case of decreasing tidal volume, a medical professional can change the airflow settings “to counter/treat the more severe level of airway obstruction observed from the decreasing tidal volume.” Ex. 1003 (Kirkness Decl.) ¶ 158; Pet. 15–16; Ex. 1044 (Toge) ¶ 39.” slip op. at 26

  Patent outcomesUS 11,857,333 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,857,333
• 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
• 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
• Resmed Corp. v. Cleveland Medical Devices, Inc.No claims unpatentable
  PTAB · Jun 5, 2026 · IPR2025-00160 · APJ Sheridan K Snedden · IPR · Final written decision

  Claims 1–5, 7, 8, 10–13, 15–18, and 20–31 were not shown unpatentable because the proposed Toge-Kumar combination did not establish the claimed remote internet site hosted on a server.

  RulingsFinal written decision

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

    “Patent Owner filed a Response. Paper 23 (“PO Resp.”). Petitioner filed a Reply. Paper 27 (“Reply”). Patent Owner filed a Sur-reply. Paper 35 (“Sur-reply”). Additionally, during trial, Patent Owner filed an authorized Motion to Terminate, alleging that Petitioner failed to name a real party in interest (namely, Petitioner’s corporate parent, Resmed Inc.). Paper 37. Petitioner filed an opposition. Paper 38. Patent Owner filed a reply. Paper 39. We denied the Motion to Terminate. Paper 44.” slip op. at 2

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

    “We determine 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))). To the extent further discussion of the meaning of any claim term is necessary to our decision, we provide that discussion below in our analysis of the asserted grounds of unpatentability. C. Level of Ordinary Skill in the Art” slip op. at 11

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We adopt Petitioner’s proposed level of ordinary skill in the art because it appears to be consistent with the cited prior art and is undisputed on this record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (indicating that the prior art itself may reflect an appropriate skill level). D. Summary of the Asserted Prior Art” slip op. at 12

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

    “summarized above, we determine that a person of ordinary skill in the art would not have implemented Toge’s physician-side computer as a web server using a “localhost” architecture as proposed by Petitioner because such a configuration cannot communicate with external devices over the public internet, a deficiency that directly contradicts Petitioner’s stated motivations for the combination of permitting broad data access. Petitioner’s expert, Dr. Chatterjee, expressly acknowledged in his Reply Declaration that when a client and server reside on the same machine, the communications between them do not traverse the internet. Ex. 1069 ¶ 8. Specifically, Dr. Chatterjee cited the Microsoft Computer Dictionary’s definition of “localhost” as “[t]he name that is used to represent the same computer on which a TCP/IP message originates,” noting that “[a]n IP packet sent to localhost has the IP address 127.0.0.1 and does not actually go out to the Internet.” Id. (citing Ex. 1070, 316). Accordingly, Petitioner’s proposed configuration of placing both the client and web server on Toge’s physician-side computer would create a closed loop of communication that does not reach the broader network. Id. As noted by Patent Owner, “[i]f ‘the physician-side computer and the web server are on one machine,’ the local web server would not communicate with other devices via the Internet.” Sur-Reply, 3–4 (comparing Ex. 1069 ¶ 19 with id. at ¶ 8). Thus, the consequence of Petitioner’s proposed Toge-Kumar configuration is that other devices in the system, such as the PAP device that generates the treatment data and any remote client devices that might need to access that data, would be unable to send data to or retrieve data from the localhost web server. Patent Owner persuasively argues, supported by evidence of record, that under Petitioner’s proposed configuration, “the PAP device could not send data thereto nor could other clients receive data therefrom, as only the local client browser can exchange data.” Id. (citing Ex. 1069 ¶ 8); see Ex. 2003, 4 (one-tier architecture “is not suitable for a web application” because “it can only access data available in a single computer or server” and therefore “is not suitable for a web application.”); Ex. 2022, 3 (Unlike more advanced multi-tier systems, a one-tier architecture “cannot transmit information from one client machine to another.”); Ex. 2020, 4 (While “the client process and server process can be on the same computer,” this architecture “is rarely used today” precisely because it cannot “take advantage of the distributed computing environment.”).” slip op. at 29

  Patent outcomesUS 11,786,680 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,786,680
• Resmed Corp. v. Cleveland Medical Devices, Inc.No claims unpatentable
  PTAB · Jun 4, 2026 · IPR2025-00158 · APJ Sheridan K Snedden · IPR · Final written decision

  Claims 1–20 were not shown unpatentable because Orbach did not disclose a single computer or processor performing all claimed remote analysis, output, and display functions.

  RulingsFinal written decision

  • BurdenNot shown unpatentable

    “After considering all of the arguments and evidence presented on the full trial record, we determine that Petitioner has not demonstrated by a preponderance of the evidence that claims 1–6, 8–17, 19, and 20 are unpatentable as obvious over the combination of Ciulla and Orbach. We find that the deficiencies in Petitioner’s arguments regarding claim limitations [1.d], [1.f], and [1.g] are dispositive and we address the parties’ arguments concerning those limitations below.” slip op. at 24

  • Skill levelSkill level petitioner adoptedOther

    “Pet. 8. Patent Owner agrees to apply Petitioner’s proposed definition of POSITA. PO Resp. 4. We adopt Petitioner’s proposed definition of a POSITA because the proposed level of ordinary skill in the art appears to be consistent with the cited prior art and is undisputed on this record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (indicating that the prior art itself may reflect an appropriate skill level).” slip op. at 11

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

    “the Board need not construe any terms. Pet. 9. Patent Owner agrees. PO Resp. 4. We determine 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))). Nevertheless, in our analysis of the asserted grounds of unpatentability below, we discuss the scope of certain claim terms, e.g., “the computer” and “the processor.” C. Level of Ordinary Skill in the Art” slip op. at 11

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

    “Accordingly, to show obviousness, Petitioner must show in Orbach that either (a) remote server 140’s output to viewing station 150 constitutes “display” within the meaning of the claim, or (b) viewing station 150 receives data “over cell towers” notwithstanding the intervening server. We determine that Petitioner has failed to do so on this record. Our analysis follows.” slip op. at 33

  Patent outcomesUS 11,690,512 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,690,512
• Resmed Corp. v. Cleveland Medical Devices, Inc.No claims unpatentable
  PTAB · May 18, 2026 · IPR2025-00159 · APJ Cynthia M Hardman · IPR · Final written decision

  Claims 1, 2, 4, 5, 7–9, 11–14, and 16 were not shown unpatentable under either § 103 ground because Petitioner did not establish the proposed remote internet site modification.

  RulingsFinal written decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for patent ownerDecided for patent owner

    “Patent Owner filed an authorized Motion to Terminate, alleging that Petitioner failed to name a real party in interest (namely, Petitioner’s corporate parent, Resmed Inc.). Paper 37. Petitioner filed an opposition. Paper 38. Patent Owner filed a reply. Paper 39. We denied the Motion to Terminate. Paper 44.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time the invention was made.8 See Graham, 383 U.S. at 17–18. The parties agree that a person of ordinary skill in the art (sometimes referred to herein as a POSITA) would have had: at least a bachelor’s degree in mechanical engineering, electrical engineering, computer science, biomedical engineering, or a similar technical field, with at least two years of relevant product design experience working with diagnostic sensor systems and network data systems, such as networked PAP machines. Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Pet. 12–13 (citing Ex. 1003 (Kirkness Decl.) ¶¶ 44–46); PO Resp. 7–8. Because the proposed level of ordinary skill in the art is consistent with the cited prior art and is undisputed on this record, we adopt it for purposes of this Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (indicating that the prior art itself may reflect an appropriate skill level).” slip op. at 11

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

    “We find it unnecessary to construe any claim term to resolve the issues in this case. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we 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 12

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

    “its burden of explaining why a person of ordinary skill in the art would have implemented a remote internet site in Toge’s system in the specific fashion Petitioner asserts (i.e., using the physician-side computer as a web server). As Patent Owner aptly states, the operative question is not merely whether a person of ordinary skill in the art would have modified Toge’s system to include a remote internet site, but whether the artisan would have modified Toge’s system to include a remote internet site “on a physician’s client computer” in accordance with the specific implementation argued by Petitioner. Sur-reply 2. On this critical question, Petitioner’s arguments are thin. Petitioner’s declarant Dr. Kirkness states that a person of ordinary skill in the art “would have understood that one common way to access data transmitted over the internet, like the data from Toge’s wireless PAP device, is via a remote internet site.” Ex. 1003 ¶ 214. This assertion is reasonable. Indeed, prior art of record, such as Kumar, illustrates use of a central server that hosts a browser-based engine that can be accessed through web pages. See, e.g., Ex. 1008 (Kumar) Fig. 1A, ¶¶ 67, 72, 79, Pet. 10. Petitioner, however, elected to argue a specific implementation, namely that the skilled artisan would have modified Toge’s physician-side computer to operate as a web server. See, e.g., Pet. 15; Ex. 1005 (Chatterjee Decl.) ¶ 146; Reply 4. We find that this implementation is unsupported on this record. Petitioner has not pointed us to any disclosure in Toge, Burton, or Kumar (or any other prior art reference of record) that teaches or suggests “that a doctor’s computer should act a web server hosting sensitive patient data.” PO Resp. 9 (emphasis added). And critically, the Petition is silent as to why a person of ordinary skill in the art would have selected this implementation in particular. See, e.g., Pet. 49.” slip op. at 25

  Patent outcomesUS 11,375,921 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,375,921
• Stryker Corporation / Wright Medical Technology, Inc. v. Osteomed LLCAll claims unpatentable
  PTAB · May 4, 2026 · IPR2022-00189 · APJ Sheridan K Snedden · IPR · Remand

  Claim 16 is unpatentable because Slater anticipates it.

  RulingsRemand decision

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

    “undisputed limitations of claim 16 and find that Petitioner establishes that Slater discloses each limitation of claim 16 for the reasons provided by Petitioner. Specifically, Petitioner shows, and Patent Owner does not dispute, that Slater describes a plate with “flared hips” comprising opposing “generally parabolic wings” as recited in dependent claim 16. Pet. 28–30; Ex. 1005, Fig. 2; Ex. 1002 ¶ 106. We adopt Petitioner’s arguments and evidence as to these limitations as our own. See Pet. 28–30. Based on the foregoing, Petitioner proves by a preponderance of the evidence that Slater anticipates claim 16.” slip op. at 12

  Patent outcomesUS 8,529,608 unpatentable
  § 102 anticipation
  Patents in suitUS 8,529,608

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.