• Uatp IP LLC v. Slick Slide LLCSome claims unpatentable
  PTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision

  Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.

  RulingsFinal written decision

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

    “1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13

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

    “5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33

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

    “2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20

  Patent outcomesUS 11,998,854 mixed
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
  Patents in suitUS 11,998,854
• Google LLC v. Sandpiper CDN, LLCInstituted
  PTAB · Nov 25, 2025 · IPR2025-00860 · APJ Sheila F Mcshane · IPR · Institution

  The Board instituted review of claims 1–20 on all asserted grounds, finding a reasonable likelihood that the Dilley, Pai, and Wang combination renders the claims obvious.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’573 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “III. ANALYSIS A. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art: would have had at least a bachelor’s degree in computer science, electrical engineering, or a related field, and at least two years of work or research experience in the field of content delivery management or networks. Work experience can substitute for formal education and additional formal education can substitute for work experience. Pet. 12 (citing Ex. 1006 ¶ 70). Patent Owner asserts that “the Board does not need to resolve the appropriate level of skill for a POSA [person of ordinary skill in the art] for purposes of deciding institution because the Petition fails under any articulation of a POSA.” Prelim Resp. 10. For the purposes of this Decision, we adopt the assessment offered by Petitioner as it is consistent with the ’573 patent and the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “Petitioner asserts that no claim terms need to be expressly construed by the Board and all terms should be given their ordinary meaning. Pet. 12. Patent Owner agrees that the Phillips standard applies. Prelim. Resp. 10. We determine that we need not expressly construe any claim terms at this juncture. 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 9

  • Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner

    “We consider the disclosures of the Provisional Application, which refer to cases 1 and 2, in which requests are redirected to an origin server for lower popularity content and to a parent server for medium popularity content at steps 522 and 524 as shown in Figure 5, respectively, wherein the edge server receives a redirect from the popularity service without a “followme” flag. See Ex. 1011 ¶¶ 43, 44. The Provisional Application also discloses that, by comparison, if there is a “follow-me” redirect sent to the edge server, it obtains and caches a resource as shown at step 528 for higher popularity content. Id. ¶ 44. On this record, as Patent Owner asserts, these disclosures are consistent with technical reasons provided in the Provisional Application for instructing the edge server not to cache unpopular resources. See Ex. 1011 ¶¶ 68–69. In light of these disclosures, we preliminarily find support for Dr. Shenoy’s testimony that, even with the words “instruction to not cache” are not literally recited in the Provisional Application, caching and not caching are alternative options that indicate the instruction to the edge server that will be implemented for each option. See Ex. 2014 ¶ 56. Further, these disclosures provide support for Dr. Shenoy’s testimony that the disclosures “reasonably convey to those skilled in the art that Patent Owner had possession of the edge server receiving an instruction to not cache the resource (and instead simply forward the redirect).” Id. In re Johnson states that “it is not true that the factual context out of which the question under § 112 arises is immaterial. Quite the contrary. Here, . . . the ‘written description’ in the [] specification supported the claims in the absence of the limitation, and that specification, having described the whole, necessarily described the part remaining.” See Johnson, 558 F.2d at 1019. This is consistent with M.P.E.P. § 2173.05(i) which states, “[i]f alternative elements are positively recited in the specification, they may be explicitly excluded in the claims.” M.P.E.P. § 2173.05(i). Further, “the failure of the specification to specifically mention a limitation that later appears in the claims is not a fatal one when one skilled in the art would recognize upon reading the specification that the new language reflects what the specification shows has been invented.” All Dental Prodx, LLC v. Advantage Dental Prod., Inc., 309 F.3d 774, 779 (Fed. Cir. 2002). Even though we do not discern that the Provisional Application explicitly discloses an “instruction to not cache,” at least on this preliminary record, and for the purposes of this Decision, there is positive recital of instructions to cache in the Provisional Application and Petitioner has provided sufficient supporting evidence that caching and not caching are alternative options. Further, there is sufficient evidence, in the context of the disclosures of written description support in the Provisional Application, providing support for Dr. Shenoy’s testimony that Patent Owner had possession of an edge server receiving an instruction to not cache the resource. Nonetheless, we invite additional briefing on these issues, including issues relating to alternative options of caching and not caching. On this preliminary record, we find that the ’573 patent has a priority date of April 2, 2008, which predates the earliest possible date on which Newton-471 could be effective as prior art, September 30, 2014 (the date on which the earliest application in the priority chain of Newton-471 was filed). Accordingly, we preliminarily find that Newton-471 is not prior art to the challenged claims. Thus, on the present record, Petitioner has not demonstrated a reasonable likelihood that it would prevail in showing that claims 1–20 are anticipated by Newton-471.” slip op. at 13

  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 10,924,573
• Google LLC v. Sandpiper CDN, LLCInstituted
  PTAB · Nov 10, 2025 · IPR2025-00806 · APJ Sheila F Mcshane · IPR · Institution

  The Board instituted IPR on claims 1–20 and all asserted grounds, finding a reasonable likelihood of success on the § 103 challenges.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’517 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “application must comply with the written description requirement of 35 U.S.C. § 112.” Zenon Envtl., Inc. v. U.S. Filter Corp., 506 F.3d 1370, 1378 (Fed. Cir. 2007) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571 (Fed. Cir. 1997)); see also In re Hogan, 559 F.2d 595, 609 (CCPA 1977). To comply with the “written description” requirement of 35 U.S.C. § 112, first paragraph, an applicant must “convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention. The invention is, for purposes of the ‘written description’ inquiry, whatever is now claimed.” Vas-Cath, Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (emphasis omitted). The invention claimed does not have to be described in ipsis verbis to satisfy the written description requirement. Union Oil Co. v. Atlantic Richfield Co., 208 F.3d 989, 1000 (Fed. Cir. 2000). The question of written description support should not be confused, however, with the question of what would have been obvious to the artisan. Whether one skilled in the art would find the claimed invention obvious in view of the disclosure is not an issue in the “written description” inquiry. In re Barker, 559 F.2d 588, 593 (CCPA 1977). “A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood, 107 F.3d at 1572.” slip op. at 11

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

    “motivated to combine Beaumont and Hasan. Pet. 13–14. Petitioner argues that “Beaumont does not describe a specific interface for manually entering [policy and rules] preferences, Hasan discloses a GUI for exactly this type of policy specification.” Id. at 14 (citing Ex. 1003 ¶ 70). Petitioner asserts that Hasan discloses that its Java-based, “platform independent” GUI takes the form of a “familiar tree structure” and allows administrators to “configure device and service configuration data and policy information.” Id. (citing Ex. 1006, code (57), 7:7–26, 8:19–29, 18:9–20). Petitioner asserts that the combination of Beaumont and Hasan would have been straightforward, and a person of skill “would have been motivated to incorporate Hasan’s GUI so that administrators could conveniently configure preferences for Beaumont’s DNS servers through an intuitive interface.” Id. (citing, inter alia, Ex. 1003 ¶¶ 70–71; Ex. 1007 ¶ 23). Patent Owner does not present any arguments on the rationale to combine. See generally Prelim. Resp. We find that at this juncture Petitioner has presented sufficient rationale to combine Beaumont and Hasan.” slip op. at 16

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

    “We agree with Patent Owner that its understanding of a policy as a rule is consistent with the disclosure in the ’517 patent that “a policy may be created by generating a decision tree representing the ATC rules.” See Ex. 1001, 9:1–3. We do not agree with Patent Owner, however, that Beaumont in combination with Hasan does not disclose the claimed policy features as claimed. As discussed above, Petitioner relies upon Beaumont in combination with Hasan with its teachings on the use of Java-based GUIs in the form of a tree structure that allows administrators to configure device and service configuration data, as well as policy information. See Ex. 1006, code (57), 7:7–26, 8:19–29. For the policy teachings, Petitioner relies upon Beaumont’s “content provider DNS server that directs requests (traffic) according to a preference table (policy).” Pet. 15–16 (citing Fig. 1, ¶¶ 6, 17, 23). Petitioner also asserts that the Beaumont-Hasan GUI would enable an administrator to set policies for a selected content delivery server to allow setting server preferences and rules. Id. at 17–18 (citing, inter alia, Ex. 1007 ¶¶ 76–77). In support, Dr. Lin testifies that: The Beaumont-Hasan GUI would enable an administrator to select a content delivery server (e.g., in Japan) and set policies for that server. Hasan, 8:30–36, 10:25–34, 10:53–67; Beaumont, [0031]. For example, given the description in Hasan, selecting a server would bring up a menu enabling an administrator to assign the preferences shown in Fig. 3 of Beaumont. Hasan, 10:25–34; Beaumont, Figs. 2, 3, [0029]–[0031]. A POSITA would thus have recognized the combined GUI to “support[] the setting of said at least one policy using a decision tree representing rules” because it is presented in a “familiar tree structure” and would allow users to set server preferences and rules. Ex. 1003 ¶ 77 (emphasis added). Beaumont provides support for Dr. Lin’s testimony. Beaumont discloses that “rules such as selecting one [a server] based on user preferences can be used . . . [f]or example, a preference number can be assigned to each content delivery server and a destination domain.” Ex. 1007 ¶ 31. Beaumont further states that “FIG. 3 shows an illustrative example of incorporating preference numbers in a column.” Id. Thus, contrary to Patent Owner’s arguments, Beaumont discloses that rules or policies, represented by the preference number, are represented in the table shown in Figure 3 of Beaumont. Dr. Lin also testifies that in the Beaumont-Hasan combination “the GUI supports the setting of” policy is taught. Ex. 1003 ¶ 77. Hasan provides support that service policies can be modified by the use of a GUI. See Ex. 1006, 8:30–36, 10:25–34, 10:53–67. Accordingly, in the combination of Beaumont and Hasan, wherein the preference database is replaced by the GUI decision tree, Petitioner has provided sufficient evidence at this juncture that the combination of Beaumont and Hasan teaches that the GUI obtains a policy, the preference number, for the direction of network traffic, where the GUI supports the setting of the policy using a decision tree representing rules.” slip op. at 19

  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 8,645,517
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Maxell LtdNo claims unpatentable
  PTAB · Oct 31, 2025 · IPR2024-00777 · APJ Jameson Lee · IPR · Final written decision

  Claims 16–27 were not shown unpatentable because Petitioner failed to account for limitations 16[b] and 16[i] and their counterparts across the asserted obviousness grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner proposes that a person of ordinary skill in the art “would have a Bachelor of Science degree in Electrical Engineering, Computer Engineering, Computer Science, Human Computer Interaction, or a related technical field, with at least one year of experience working in the field of user interfaces and/or content management.” PO Resp. 11 (citing Ex. 2040 ¶ 53). The Decision on Institution adopted Petitioner’s proposed level of ordinary skill in the art. Inst. Dec. 10. We find Patent Owner’s stated level to be less precise than that proposed by Petitioner in that the modifier “at least” used by Patent owner imposes no upper bound on the amount of experience possessed by one of ordinary skill in the art. Also, Patent Owner states: “The difference between the Board’s definition and Patent Owner’s (EX2040. ¶53) does not change the arguments set forth herein.” PO Resp. 11. Thus, we continue to adopt Petitioner’s stated level of ordinary skill in the art.4 4 All of our findings and conclusions would still be the same, however, had we applied Patent Owner’s articulation of the level of ordinary skill in the art.” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for patent owner

    “In its Reply, Petitioner does not assert that the district court’s construction is incorrect. We agree with Patent Owner that the district court’s construction is better than Petitioner’s proposed construction, because for reasons indicated by Patent Owner, which are not disputed by Petitioner, settings in the computer, e.g., dedicated folders for each user are the user profiles, rather than simply data alone of any kind. Further, when asked about the appropriateness of the district court’s construction, counsel for Petitioner expressed that Petitioner has no objection to the Board’s adopting the district court’s construction for “user profile”: JUDGE LEE: So, you’d be fine with just going with the District Court’s construction? MR. HEINTZ: Yes, Your Honor. Tr. 15:22–24. For the foregoing reasons, we adopt the district court’s construction for “user profile,” i.e., “a collection of settings and information associated with a user.”” slip op. at 13

  • BurdenNot shown unpatentable

    “PO Resp. 30–31 (Figure 26 omitted). In its Reply, Petitioner still does not provide an articulated reason for placing user profile selection buttons, labeled with user names, within Horn’s panes 2601 or 2602. Reply 12–14. Although Horn does describe personalized profile, Petitioner points to no disclosure of Horn as to how a user would have selected his or her own profile from among a plurality of user profiles. Petitioner presents no reason for placing these user profile selection buttons, labeled with user names, gleaned from or suggested by Baumgartner, within either pane 2601 or pane 2602 in Horn’s workspace view. Further, pane 2602 contains “a list of all collections defined by MFS and the user,” and pane 2601 lists the source examined by the user to create his or her collections. Ex. 1005, 19:41–46. That disclosure suggests the contents of panes 2601 and 2602 are tied to one particular user. No rational basis is articulated by Petitioner to place user profile selection buttons within these panes which appear to be in the profile space of one user. For the foregoing reasons, Petitioner has not adequately accounted for limitation 16[b].” slip op. at 22

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “The test for sufficiency of a written description under 35 U.S.C. § 112 is whether the earlier application’s disclosure “reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date.” Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). The specification must “clearly allow persons of ordinary skill in the art to recognize that [the inventor] invented what is claimed.” Id. The Court of Appeals for the Federal Circuit has explained: One shows that one is “in possession” of the invention by describing the invention, with all its claimed limitations, not that which makes it obvious. Id. (“[T]he applicant must also convey to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention. The invention is, for purposes of the ‘written description’ inquiry, whatever is now claimed.”) (emphasis in original). One does that by such descriptive means as words, structures, figures, diagrams, formulas, etc., that fully set forth the claimed invention. Although the exact terms need not be used in haec verba, see Eiselstein v. Frank, 52 F.3d 1035, 1038, 34 USPQ2d 1467, 1470 (Fed.Cir.1995) (“[T]he prior application need not describe the claimed subject matter in exactly the same terms as used in the claims. . . .”), the specification must contain an equivalent description of the claimed subject matter. A description which renders obvious the invention for which an earlier filing date is sought is not sufficient. Lockwood v. American Airlines, Inc., 107 F.3d 1565 (Fed. Cir. 1997).” slip op. at 31

  Patent outcomesUS 11,017,815 not shown unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 11,017,815
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00509 · APJ Michael J Strauss · IPR · Final written decision

  Claims 1–4 and 6–19 are unpatentable as obvious over Throughtek-2012 and the Lorex Video; claims 1–3, 6, 10, 12–14, 17, and 18 are also unpatentable under two other grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Dr. Bims, Petitioner proposes that a person of ordinary skill in the art at the time of the ’842 patent would have been a person having a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies. Pet. 11 (citing Ex. 1001 ¶¶ 15–16). Patent Owner does not provide any proposed qualifications for a person of ordinary skill in the art. In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt the assessment offered by Petitioner as it is consistent with the ’842 patent and the asserted prior art.” slip op. at 7

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

    “Petitioner asserts “no claim elements need a formal construction for purposes of resolving the controversy in this proceeding.” Pet. 11 (citing Ex. 1001 ¶ 55; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011); Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. §42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See 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

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  Patent outcomesUS RE47,842 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
• Microsoft Corporation v. Interdigital Patent Holdings, Inc.No claims unpatentable
  PTAB · Jun 23, 2025 · IPR2024-00538 · APJ Miriam L Quinn · IPR · Final written decision

  The Board held all challenged claims of the ’933 and ’054 patents not unpatentable because the claims were entitled to the December 22, 2009 priority date, making the asserted prior art unavailable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “the time of the invention as someone that would have had “a bachelor’s degree in computer science, electrical engineering, computer engineering, or a closely related field, and one to three years of experience working with wirelessly connected mobile devices that used common wireless communications protocols such as Bluetooth and 802.11.” 537 Pet. 17 (citing Ex. 1203 ¶¶ 29–32). Petitioner also contends that this description “would not differ materially between December 2008 and June 2013,” the earliest possible priority date for the patents-at-issue and the priority date alleged by Petitioner, respectively. Petitioner further contends that more education “would compensate for less work experience and vice versa.” Id. Petitioner. 537 PO Resp. 6−7; 538 PO Resp. 6−7. Accordingly, for purposes of this Decision, we adopt Petitioner’s description as our own. We adopt Petitioner’s level of ordinary skill in the art particularly because it specifies having one to three years of experience working with wireless devices that use Bluetooth and 802.11.” slip op. at 16

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

    “Petitioner construes the claims to have their “plain and ordinary meaning” and contends “that no terms invoke means-plus-function analysis.” 537 Pet. 17–18; 538 Pet. 18−19. Patent Owner does not contend that any terms require construction. 537 PO Resp. 6; 538 PO Resp. 6. We have not identified any terms that require construction for us to decide the threshold issue of priority. And given that the parties have no disputed terms, no claim terms are hereby construed.” slip op. at 17

  • Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner

    “The written description requirement is satisfied when “the missing descriptive matter” is necessarily present in the original “application’s specification such that one skilled in the art would recognize such a disclosure.” Tronzo v. Biomet, Inc., 156 F.3d 1154, 1159 (Fed. Cir. 1998). Thus, it is sufficient to show that the written description actually or inherently discloses the claim element. TurboCare Div. of Demag Delaval Turbomachinery Corp. v. Gen. Elec. Co., 264 F.3d 1111, 1118−20 (Fed. Cir. 2001). We also note that Patent Owner argues that the field of the 948 application is a predictable application of wireless communications, which, compared to other complex and unpredictable technologies, would require a lower level of detail to satisfy the requirement. See Hologic, Inc. v. Smith & Nephew, Inc., 884 F.3d 1357, 1361 (Fed. Cir. 2018); see also Ariad Pharmaceuticals, Inc. v. Eli Lilly and Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (“the level of detail required . . . varies depending on the nature and scope of the claims and on the complexity and predictability of the relevant technology.”); 537 PO Resp. 26−27; 537 Edwards Decl. ¶¶ 82, 87; 537 Surreply 8.” slip op. at 20

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

    “1277 (Fed. Cir. 2011); PowerOasis, Inc. v. T-Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008). At issue in the instant proceedings is the first requirement, whether the written description of the 948 application is sufficient, because Petitioner contends that the claims of the ’933 and ’054 patent are not entitled to claim priority to ancestry applications under 35 U.S.C. § 120. 537 Pet. 18.43 We disagree with Petitioner because we find that the claims are supported by the written description of the 948 application disclosure.” slip op. at 18

  Patent outcomesUS 9,173,054 not shown unpatentable
  Claim construction§ 102 anticipation§ 112 disclosurecites Phillips
  Patents in suitUS 9,173,054
• Microsoft Corporation v. Interdigital Patent Holdings, Inc.No claims unpatentable
  PTAB · Jun 23, 2025 · IPR2024-00537 · APJ Miriam L Quinn · IPR · Final written decision

  The Board held all challenged claims of the ’933 and ’054 patents not unpatentable because the claims are entitled to priority to December 22, 2009, making Forutanpour not prior art.

  RulingsFinal written decision

  • BurdenFwd all claims patentableNot shown unpatentable

    “VI. ANALYSIS OF UNPATENTABILITY Because of our determination that the priority date of December 22, 2009 is appropriate, we conclude that the Forutanpour reference (a U.S. patent application published on April 7, 2011) is not prior art. presented in either Petition. VII. CONCLUSION Having reviewed the argument and supporting evidence of record, and after a full and fair hearing, we determine that Petitioner has not demonstrated by a preponderance of the evidence that any of the challenged claims of the ’933 and ’054 patents are unpatentable.” slip op. at 36

  • Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateDecided for patent owner

    “Thus, we find that the 948 application reasonably conveys to a person of ordinary skill in the art that the inventors contemplated the communication of wireless devices to continue using the known method of file/data transfers via Wi-Fi and that the technique for device discovery using Bluetooth would additionally provide environment information useful for assessing which nearby device has the TapApp functionality. Disclosure of the knowledge of wireless radio dialogue between devices to collect further information to provide a particular location of a device informs a person of ordinary skill in the art that the 948 application was not limited to using only Bluetooth for the method performed by the WTRU, culminating in data transfer.” slip op. at 23

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artDecided for patent owner

    “sufficiency of the written description, we conclude that the 948 application sufficiently describes Wi-Fi transfer for data transmissions in WTRUs even if the method also uses Bluetooth for selecting target WTRUs. Accordingly, the claims of the ’933 and ’054 patents are entitled to the priority date of December 22, 2009, the date of the 948 application. VI. ANALYSIS OF UNPATENTABILITY Because of our determination that the priority date of December 22, 2009 is appropriate, we conclude that the Forutanpour reference (a U.S. patent application published on April 7, 2011) is not prior art.” slip op. at 36

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “F. Level of Ordinary Skill in the Art Petitioner identifies a person of ordinary skill in the art (“POSITA”) at the time of the invention as someone that would have had “a bachelor’s degree in computer science, electrical engineering, computer engineering, or a closely related field, and one to three years of experience working with wirelessly connected mobile devices that used common wireless communications protocols such as Bluetooth and 802.11.” 537 Pet. 17 (citing Ex. 1203 ¶¶ 29–32). Petitioner also contends that this description “would not differ materially between December 2008 and June 2013,” the earliest possible priority date for the patents-at-issue and the priority date alleged by Petitioner, respectively. Petitioner further contends that more education “would compensate for less work experience and vice versa.” Id. Petitioner. 537 PO Resp. 6−7; 538 PO Resp. 6−7. Accordingly, for purposes of this Decision, we adopt Petitioner’s description as our own. We adopt Petitioner’s level of ordinary skill in the art particularly because it specifies having one to three years of experience working with wireless devices that use Bluetooth and 802.11.” slip op. at 16

  Patent outcomesUS 8,737,933 not shown unpatentable
  § 102 anticipation§ 112 disclosurecites Phillips
  Patents in suitUS 8,737,933
• Uatp IP LLC v. Slick Slide LLCInstituted
  PTAB · Apr 8, 2025 · PGR2024-00054 · APJ Julia Heaney · PGR · Institution

  The Board instituted PGR on claims 1–17 and 22–28 and all asserted grounds, finding a sufficient likelihood that at least one challenged claim is unpatentable.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “Institution of a post-grant review is authorized by statute when “the information presented in the petition . . . would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a) (2018). Upon consideration of the parties’ submissions and the evidence of record, we determine that Petitioner has demonstrated that it is more likely than not that at least one claim challenged in the Petition is unpatentable. Further, Patent Owner has not persuaded us that it is appropriate to exercise our discretion not to institute review. Accordingly, we institute a post-grant review of all claims and all grounds asserted in the Petition.1” slip op. at 2

  • Skill levelSkill level patent owner adoptedOther

    “On this record, we do not find Patent Owner’s proposed experience level of at least five years in measurement and analysis of coefficient of friction to be supported. As to the necessity of experience in textile engineering and fiber science, Patent Owner’s position, although not supported by declarant analysis of the factors listed above, is consistent with the disclosure of the ’854 patent, which describes features of a mesh layer in textile and fiber terms. See e.g., Ex. 1001, 10:17–11:14, 12:65–13:8, 14:20–24. On the whole, however, we do not discern on this record how specific experience in textile engineering and fiber science of a person of ordinary skill would materially alter the outcome at this stage of the proceeding. For purposes of this decision only, we apply Patent Owner’s proposed definition of a person of ordinary skill in the art, except for the requirement of five years of experience in measurement and analysis of coefficient of friction. The level of skill in the art remains an open issue in this proceeding. Further submissions by the parties may include argument and evidence that would assist in the resolution of this issue at the close of trial.” slip op. at 8

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

    “Petitioner contends “no formal claim construction is necessary in this proceeding.” Pet. 10; Reply 1, 4. Patent Owner contends the terms “mesh layer” and “coefficient of friction” require construction. Prelim. Resp. 14–16; Sur-reply 2–5. We have considered the parties’ arguments and discuss them below with regard to each of the terms Patent Owner contends should be construed. Because our determination that Petitioner demonstrates at least one challenged claim meets the threshold for institution (see SAS Inst., 138 S. Ct. at 1359–60) is not based on construing the term “mesh layer” or “coefficient of friction,” we determine we need not construe either claim term at this stage of the proceeding. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”)). As further discussed below, we invite the parties to address claim construction at trial.” slip op. at 9

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageDisclaimer not foundDecided for petitioner

    “We agree with Petitioner that the ’854 patent specification does not include clear and explicit lexicography or a disclaimer that would support requiring “coefficient of friction” to be determined by a specific ASTM test method. The portion of the specification Patent Owner asserts as a definition of “coefficient of friction” (see Ex. 1001, 11:31–42) is a description of an embodiment; we find it does not express patentee intent to redefine the term. Further, the statement that “the coefficient of friction … may be determined using the … ASTM D1894 standard test method” (id. at 11:32–35) indicates that use of that specific test method is optional. Accordingly, in the absence of patentee lexicography or disavowal, we do not limit the scope of the term “coefficient of friction” to require that it be measured by a specific ASTM standard. Luminara Worldwide, LLC v. Liown Elecs. Co., 814 F.3d 1343, 1353 (Fed. Cir. 2016) (“Absent lexicography or disavowal, we do not depart from the plain meaning of the claims.”); In re Am. Acad. Of Sci. Tech Ctr., 367 F.3d 1359, 1369 (Fed. Cir. 2004) (“We have cautioned against reading limitations into a claim from the preferred embodiment described in the specification, even if it is the only embodiment described, absent clear disclaimer in the specification.”). We note that the ’854 patent specification sets forth a definition for the coefficient of friction between the surfaces of the mesh material and the slide surface. Ex. 1001, 4:38–46. As stated above, however, we do not expressly construe any claim term at this stage of the proceeding. Should the parties address the construction of “coefficient of friction” at trial, we will make a determination after the close of evidence and any hearing.” slip op. at 13

  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · Graham
  Patents in suitUS 11,998,854
• Ecto World, LLC / Sv3, LLC v. Rai Strategic Holdings, Inc.Institution denied
  PTAB · Mar 10, 2025 · PGR2024-00049 · APJ Jo-Anne M Kokoski · PGR · Institution

  The Board denied institution because Petitioner did not show the patent was eligible for PGR; the challenged claims were supported by the 2006 priority application.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “Accordingly, we determine that Petitioner does not demonstrate that it is more likely than not that the challenged claims lack written support in the Specification (and the ’634 application). That is, on this record, it appears that the challenged claims properly claim priority to the ’634 application and, accordingly, have an effective filing date in October 2006. 2. Conclusion: PGR Eligibility For the foregoing reasons, and based on the record before us, we determine that Petitioner has not demonstrated that it is more likely than not that the ’202 patent has, or had, at least one claim having an effective filing date on or after March 16, 2013. Accordingly, we determine that the ’202 patent is entitled to the filing date of the ’634 application (October 18, 2006), and, thus, the ’202 patent is not eligible for post-grant review.” slip op. at 18

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed board ownDecided for patent owner

    “Accordingly, the ’202 patent consistently and repeatedly characterizes the invention as incorporating tobacco in some form and ties the stated benefits of the invention to the inclusion of tobacco. Moreover, the Specification is directed to smoking articles containing tobacco, all of the embodiments include tobacco, and “the present invention” is described as a smoking article, where the smoking article includes tobacco. Consequently, we determine that “smoking article” as it is used in the challenged claims is limited to devices that include tobacco. See Mosaic Brands, Inc. v. Ridge Wallet LLC, 55 F.4th 1354, 1361 (Fed. Cir. 2022) (finding claimed “lip” is limited to “extrudable plastic materials” where specification states that “the device of the present invention is constructed of extrudable plastic materials” and “emphasizes the benefits of using extrudable plastics and describes them as benefits of the invention as a whole”); Poly-Am., L.P. v. described in the specification has inwardly extended short seals and every section of the specification indicates the importance of inwardly extended short seals. These two facts provide together a proper reason to limit the claims in this way.”); Phillips v. AWH Corp., 415 F.3d 1303, 1312–1317 (Fed. Cir. 2005) (en banc) (“[T]he specification may reveal an intentional disclaimer, or disavowal, of claim scope by the inventor. In that instance as well, the inventor has dictated the correct claim scope, and the inventor’s intention, as expressed in the specification, is regarded as dispositive.”).” slip op. at 13

  • Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateNot shown unpatentable

    “Petitioner’s argument is dependent on accepting Petitioner’s assertion that the claims include a smoking article that does not contain tobacco, which we have not done. Instead, as set forth above, we construe “smoking article” as being limited to devices that include tobacco. See § II.B.2, supra. Based on our construction of “smoking article” and the evidence of record in this proceeding, we determine that the challenged claims are supported by the specification of the ’202 patent, which is identical to the specification of all of the continuations in the chain leading back to the October 18, 2006 that the specification of the ’202 patent and every patent in its priority chain “have identical specifications”); Prelim. Resp. 13 (noting that Petitioner does not identify other limitations in the challenged claims “allegedly lacking support in the ’202 patent family’s applications dating back to U.S. App. No. 11/550,634, filed on October 18, 2006”). Accordingly, we determine that Petitioner does not demonstrate that it is more likely than not that the challenged claims lack written support in the Specification (and the ’634 application). That is, on this record, it appears that the challenged claims properly claim priority to the ’634 application and, accordingly, have an effective filing date in October 2006.” slip op. at 17

  Claim construction§ 112 disclosurecites Phillips
  Patents in suitUS 11,925,202
• Apple Inc. v. Carbyne Biometrics, LLCInstitution denied
  PTAB · Aug 1, 2024 · IPR2024-00507 · APJ Jameson Lee · IPR · Institution

  The Board denied institution because Apple did not show a reasonable likelihood of proving claims 2, 4–6, 12, 15, 21, 23–25, 31, and 34 obvious.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “review. See 35 U.S.C. § 314 (2018); 37 C.F.R. § 42.4(a) (2024). An inter partes review may not be instituted unless the information presented in the Petition “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Upon consideration of the contentions and the evidence of record before us, we conclude Petitioner has not shown a reasonable likelihood that it would prevail in establishing the unpatentability of at least one challenged claim of the ’105 patent. Accordingly, we decline to institute inter partes review.” slip op. at 2

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “The test for written description support is whether the application reasonably would have conveyed to one with ordinary skill in the art “the inventor possessed the invention at the time of that original disclosure.” Pandrol USA, LP v. Airboss Ry. Prods., Inc., 424 F.3d 1161, 1165 (Fed. Cir. 2005); see also Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (“the applicant must also convey with reasonable clarity to those skilled in the art that, as of the filing date sought, she or he was in possession of the invention”). The disclosure in the provisional application as cited by Patent Owner regarding policies is broad and does not convey with reasonable clarity what specifically are the policies, such as a policy for backup based on whether the first and second devices are of the same brand. The broad disclosure does not provide written description support for the narrow and specific limitation recited in independent claims 1, 18, and 25, i.e., “based at least in part on the first device being a same brand as a second device, initiating a backup, to the second device, of at least a portion of the at least one record.” Ex. 1001, 25:7–10, 26:30–32, 28:23–25.” slip op. at 14

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “ordinary skill in the art “would have had a bachelor’s degree in [] electrical engineering, computer engineering, computer science, or a related field, and at least two years of experience in the research, design, development, and/or testing of authentication techniques, and related firmware and software, or the equivalent, with additional education substituting for experience and vice versa.” Pet. 8 (citing Ex. 1003 ¶¶ 18–22). On this record, we adopt Petitioner’s statement of the level of ordinary skill in the art, except for the qualifier “at least” which applies to experience and which would improperly extend the scope of experience to the realm of an expert. It is supported by the testimony of Dr. McDaniel and not disputed by Patent Owner (Prelim. Resp. 11). Further, it appears consistent with what is reflected by the content of the applied prior art. Cf. Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill).” slip op. at 16

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

    “and assuming that Cheng discloses backing up of data from a first user device to a second, new user device, without any user service bureau in between, Petitioner has not shown sufficient motivation to combine the teachings of Kodama with the teachings of Kesanupalli and Cheng to account for the remainder of limitation [1.8], i.e., initiate the backup “based at least in part on the first device being a same brand as a second device.” Ex. 1001, 25:7–10. Petitioner explains:” slip op. at 40

  § 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · Graham
  Patents in suitUS 11,475,105

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.