• 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
• 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
• Metacluster LT, Uab v. Bright Data Ltd.Other
  PTAB · Mar 19, 2024 · PGR2022-00052 · APJ Sheila F Mcshane · PGR · Final written decision

  The Board cancelled claims 1–27 and denied substitute claims 28–51 because the original disclosure lacked written-description support for the claimed CSP limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In our Institution Decision, we adopted Petitioner’s proposed level of ordinary skill in the art, with the exclusion of “at least” because it introduces ambiguity. Inst. Dec. 8. Patent Owner “does not dispute the Board’s findings on the qualifications of a POSA [person of ordinary skill in the art] for purposes of this proceeding.” See RMTA 13. We determine that Petitioner’s definition, with the exclusion of “at least,” is consistent with the prior art of record and the skill reflected in the Specification of the ’034 patent and we use this level of skill here in the evaluation of the Revised Motion to Amend.” slip op. at 9

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

    “Patent Owner argues that “claim construction is not necessary” and that “the meaning of the claims would be easily understood by a POSA.” RMTA 13. In the Petition, Petitioner proposed constructions for the terms “client device” and “first server,” and the original claims were rendered obvious under this construction. Pet. 23–27. Petitioner does not assert that the substitute claims of the Revised Motion to Amend are anticipated or rendered obvious by prior art or are patent ineligible. See generally RMTA Opp. Nor does Petitioner’s patentability challenge of the substitute claims contend that express construction is needed. See generally id. For purposes of this Decision, we determine that express claim construction is unnecessary. We need only construe terms that are necessary to resolve disputes. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017); 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.”).” slip op. at 10

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateDenied

    “written description requirement. In re Wright, 866 F.2d 422, 425 (Fed. Cir. 1989); All Dental Prodx LLC v. Advantage Dental Prods., 309 F.3d 774, 779 (Fed. Cir. 2002). The issue here, however, is whether the disclosure of the ’034 patent would have reasonably conveyed to a person of ordinary skill that the inventors had possession of the CSP Limitations. Ariad, 598” slip op. at 14

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part

    “to cancelling claims 1–27; and deny-in-part the Motion to Amend as to proposed substitute claims 28–51. In summary: Motion to Amend Outcome Claim(s) Original Claims Cancelled by Amendment 1–27 Substitute Claims Proposed in the Amendment 28–51 Substitute Claims: Motion to Amend Granted Substitute Claims: Motion to Amend Denied” slip op. at 20

  Claim construction§ 112 disclosure
  Patents in suitUS 11,272,034
• Netskope, Inc. v. Fortinet, Inc.Institution denied
  PTAB · Sep 11, 2023 · IPR2023-00457 · APJ James P Calve · IPR · Institution

  The Board denied institution because Netskope did not show a reasonable likelihood that claims 1–9 were unpatentable on any of its four §103 grounds.

  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) (2022) (“The Board institutes the trial on behalf of the Director.”). 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 evidence and arguments in the record, we determine that the information presented does not show a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. We therefore deny institution of an inter partes review.” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The parties substantially agree on the level of ordinary skill in the art and differ mainly in the level of experience required for different levels of education. We consider Patent Owner’s proposed level of ordinary skill to be slightly more consistent with the ’968 patent and the asserted prior art, and we apply it in our obviousness analysis below. We note, however, that our decision would be the same under either party’s proposed definition of the level of ordinary skill in the art.” slip op. at 8

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

    “B. Claim Interpretation We interpret claims “using the same claim construction standard that would be used to construe the claims in a civil action [held] under 35 U.S.C. 282(b).” 37 C.F.R. § 42.100(b). Under this standard, we construe a claim “in accordance with the ordinary and customary meaning of such claim as understood by one of ordinary skill in the art and the prosecution history pertaining to the patent.” Id. We construe the claims only to the extent necessary to determine whether to institute inter partes review. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017). The parties agree that no claim constructions are needed. Pet. 21; Prelim. Resp. 15. Having considered the record, we determine that no express claim construction is necessary to reach our decision.” slip op. at 9

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

    “3. Motivation to Combine Petitioner contends that a skilled artisan would have been motivated to combine Jordan and FortiGate because FortiGate analyzes content in real-time and downloads new or updated virus definitions to identify suspicious network traffic, and this capability would improve Jordan’s complementary system, which generates and updates rules for malware detection. Pet. 25.” slip op. at 12

  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR
  Patents in suitUS 9,231,968
• Penumbra, Inc. v. Rapidpulse, Inc.All claims unpatentable
  PTAB · Sep 6, 2023 · IPR2022-00608 · APJ Jamie T Wisz · IPR · Final written decision

  Claims 1–21 are unpatentable: claims 1–14, 17–19, and 21 as obvious over Teigen and Grey; claims 15–16 over Teigen, Grey, and Yang; and claim 20 over Teigen, Grey, and Matteo.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. PERSON OF ORDINARY SKILL IN THE ART In determining the level of skill in the art, we consider the type of problems encountered in the art, the prior art solutions to those problems, the rapidity with which innovations are made, the sophistication of the technology, and the educational level of active workers in the field. Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986). The level of ordinary skill in the art is “a prism or lens through which . . . the Board views the prior art and claimed invention” to prevent hindsight bias. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner

    “as adopted by the Board in the Institution Decision. The ’253 patent explicitly defines this term, stating: The term “forward flow” is used herein to define an amount of liquid in the lumen 662 that exits the distal end 664 in a distal direction. Forward flow is defined as greater than 6 microliters of fluid (approximately 1 mm of catheter length of ID 0.071″=5.7 μL). Ex. 1001, 38:18–23 (emphasis added). Moreover, in discussing problems with the prior art systems, the ’253 patent states that “[w]hen positive pressure exists at the distal end of the lumen, liquid from inside the lumen exits out from the distal end of the catheter in a distal direction. This is referred to as forward flow.” Id. at 3:8–11. In the ’253 patent, the patentee acted as its own lexicographer as evidenced by usage of language such as “is used herein to define,” “is defined,” and “is referred to as,” to discuss “forward flow.” We find that the definition of “forward flow” in the ’253 patent specification would provide a person of ordinary skill with “reasonable clarity, deliberateness, and precision” as to the meaning of the term. See Paulsen, 30 F.3d at 1480; see also Ex. 1034 ¶¶ 13–14. Thus, we construe the term, “forward flow,” to mean “an amount of liquid in the lumen that exits the distal end in the distal direction that is greater than 6 microliters.” We disagree with Patent Owner’s contention that our construction imports limitations from a single embodiment into the claims. As explained above, the ’253 patent clearly defines the term “forward flow” and this definition is not limited to a single embodiment. In fact, the ’253 patent indicates that, while “[f]orward flow is defined as greater than 6 microliters of fluid . . . [l]ess forward flow is also included in this definition.” Ex. 1001, 38:21–24. The ’253 patent specifies that “the amount of forward flow can be restricted to no greater than 2 microliters or, in a particularly beneficial embodiment, forward flow is approximately zero microliters.” Id. at 38:24– 29. This language indicates that our construction encompasses multiple embodiments from the ’253 patent. We also disagree with Patent’s Owner’s proposed construction of “forward flow” because it is not supported by the ’253 patent specification. Patent Owner contends that “there is ‘no forward flow’ until the full extent of the distal portion” exits the distal end and thus forward flow is prevented when only less than “the full extent of the distal portion” exits the distal end. PO Resp. 9 (emphasis omitted). To adopt Patent Owner’s proposed construction, we would have to essentially ignore the ’253 patent’s express definition of this term. Further, there is no support in the ’253 patent specification for “full extent” or “fully exiting.” We also agree with Petitioner that Patent Owner’s construction effectively eliminates the concept of preventing forward flow because, as Patent Owner acknowledges, it could allow, for example, 20 milliliters of fluid to exit the catheter, which could displace the thrombus into the patient’s vasculature, a problem that the ’253 patent seeks to avoid. See PO Resp. 10–12 (citing Ex. 2014 ¶¶ 48–51); Pet. Reply 8–9 (citing Ex. 1034 ¶¶ 14–15).” slip op. at 13

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

    “As discussed above, we construe “forward flow” to mean “an amount of liquid in the lumen that exits the distal end in the distal direction that is greater than 6 microliters.” Thus, for the ’011 provisional to provide support for this limitation, the provisional must demonstrate that the inventors had possession of preventing greater than 6 microliters of fluid out of the distal end of the catheter. While Patent Owner points to disclosures from the ’011 provisional application that describe the desire to have “a minimal amount of momentum transfer from the fluid column to the stuck clot to unstick the clot sufficiently” and “[t]he exiting movement of fluid [being] limited to a specific volume and/or pressure and is automatically and precisely controlled” to prevent the “possibility of overshooting,” these disclosures would not convey to one of ordinary skill in the art that the inventors were in possession of a device that limited forward flow to no greater than 6 microliters of fluid. PO Resp. 35 (citing Ex. 1003 ¶¶ 15, 16, 138). Patent Owner also contends that the ’011 provisional application provides “multiple examples of liquid flow exiting the distal end of the catheter such that no forward flow occurs, such as 1 microliter or 0.5 mm of column shift.” PO Resp. 36–37 (citing Ex. 1003 ¶ 91). However, the disclosure cited by Patent Owner provides ranges of liquid flow of “approximately 0.001 ml to approximately 1.0 ml, in particular, approximately 0.1 ml to approximately 0.5 ml” and exemplary length of shift distances of “approximately 0.5 mm to approximately 30 mm, in particular, approximately 0.5 mm to approximately 15 mm.” Ex. 1003 ¶ 91. There is nothing in the ’011 provisional application that specifically directs the person of ordinary skill to the portions of these ranges that fall within the ’253 patent’s definition of “forward flow” (i.e., no greater than 6 microliters of fluid). In fact, the majority of the cited ranges are greater than 6 microliters, going all the way up to 1,000 microliters, such that there would be forward flow in these examples. See Ex. 1034 ¶ 25; Purdue Pharma, 230 F.3d at 1326–27 (“[O]ne cannot disclose a forest in the original application, and then later pick a tree out of the forest and say here is my invention. In order to satisfy the written description requirement, the blaze marks directing the skilled artisan to that tree must be in the originally filed disclosure.”); Fujikawa v. Wattanasin, 93 F.3d 1559, 1571 (Fed. Cir. 1996). Further, we note that the ’253 patent differentiates between embodiments that allow forward flow and embodiments in which no forward flow occurs. See Ex. 1001, 32:58–60, 37:19–22; Pet. Reply 10–11. For example, the ’253 patent describes an embodiment in which the “momentum causes a small amount of fluid to move through the distal portion of the catheter [] and create a small distal movement of the clot.” Ex. 1001, 32:47– 51. This same embodiment is disclosed in the ’011 provisional application. Compare Ex. 1003 ¶ 126 with Ex. 1001, 32:16–60. The ’253 patent describes this disclosure as an “exemplary embodiment” in which the “flow of fluid forward . . . is intentional, which is in contrast to other exemplary embodiments herein where substantially no forward flow occurs.” Ex. 1001, 32:57–60; see also, id. at 37:19–22 (“Turning now to embodiments . . . without the forward flow”).8 The ’011 provisional application does not include the subsequent embodiments from the ’253 patent that are described as being “without the forward flow.” See Ex. 1005 ¶ 68; Ex. 1034 ¶¶ 22–23. This further demonstrates that the ’011 provisional application does not support the limitation of “prevent[ing] forward flow.” We also note that the ’011 provisional application does not contain adequate support for the limitation of “substantially prevent[ing] forward flow” even under Patent Owner’s proposed construction. While the ’011 provisional discloses “controlling the distal movement of the fluid column” (Ex. 1003 ¶¶ 15, 16), this does not support Patent Owner’s assertion that the ’011 provisional teaches that “the distal portion of the fluid column is substantially prevented from fully exiting the distal end.” PO Resp. 35–36. For example, as discussed above, the ’011 provisional application discloses permitting distal flow of up to 1,000 microliters, which would likely exceed the amount that could be characterized as the full distal portion. Ex. 1003 ¶ 91; Ex. 1034 ¶ 25. Thus, we find that the ’011 provisional application does not “clearly allow persons of ordinary skill in the art to recognize that [the inventors] invented what is claimed.” In re Gosteli, 872 F.2d 1008, 1012 (Fed. Cir. 1989); Lockwood v. American Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 8 Patent Owner contends that the statement in the ’253 patent regarding the “exemplary embodiment” of “forward flow” is referring to an embodiment in which the volume of the liquid drawn out from the lumen of the catheter is “approximately 0.2 ml.” PO Resp. 40–41 (citing Ex. 1001, 32:35–36; Ex. 1003 ¶ 126; Ex. 2014 ¶ 99). Even if this is correct, the ’011 provisional application does not include the embodiments that the ’253 patent specifically characterizes as being “without the forward flow.” Pet. Reply 10–11; Ex. 1005 ¶ 68; Ex. 1034 ¶ 22–25.” slip op. at 20

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

    “Based on the above, we determine that, for prior-art determinations under AIA § 102, “there is no need to evaluate whether any claim of [a reference] patent document is actually entitled to priority or benefit under 35 U.S.C. 119, 120.” MPEP § 2154.01(b) (emphasis added). Rather, under the AIA, a reference patent document need only meet the “ministerial requirements” of §§ 119 and 120, and the provisional or other earlier application(s) to which the reference patent document claims a right of priority must “describe[] the subject matter” relied upon in the reference patent document as prior art. 35 U.S.C. § 102(d)(2). Patent Owner has not contested that Teigen meets the procedural requirements for claiming priority to the ’712 patent or the ’095 PCT application. Teigen also appears to meet the ministerial requirements for claiming priority to the provisional applications because it properly claims the benefit of these applications, the ’095 PCT application was filed co-pending with the provisional applications, and the applications share common inventors. Ex. 1007, codes (22), (60), (63), (72); Ex.1008, 2; Ex. 1009, 2; Ex. 2005, codes (22), (30), (72). Patent Owner does not dispute that Teigen meets the “ministerial requirements” of § 119. Because we find that the Dynamic Drinkware analysis does not apply here, we agree with Petitioner and Patent Owner, that we need not reach the issue of whether a claim from Teigen is supported by either Teigen provisional application. PO Sur-Reply 8; Pet. Reply 12–13.” slip op. at 30

  Patent outcomesUS 10,722,253 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 10,722,253
• Hope Medical Enterprises, Inc. v. Oregon Health & Science UniversityOther
  PTAB · Apr 18, 2023 · IPR2022-00123 · APJ Zhenyu Yang · IPR · Final written decision

  The Board cancelled original claim 1 and denied substitute claim 2 for lack of written-description support; it did not reach the obviousness or enablement grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “ordinary skill is inappropriate because it “requires qualifications that exclude even the sole inventor of the ’190 Patent, Dr. Edward Neuwelt.” MTA Opp. 1. According to Petitioner, Dr. Neuwelt is “a neurosurgeon,” not a pediatric oncologist, and lacks the requisite “at least 2 years” experience in platinum-based therapies. Id. (citing Ex. 1003, 18; Ex. 1038, 98:9–17, 100:15–101, 4). We agree with Petitioner. It is well settled that inventors are typically persons skilled in the field of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1313 (Fed. Cir. 2005) (en banc). Petitioner presents persuasive evidence to show that under Patent Owner’s proposed definition of the level of ordinary skill, Dr. Neuwelt, the sole inventor, would not qualify as an ordinarily skilled artisan, because he is not a pediatric oncologist, even though he is considered “one of the world leading experts on this compound [STS] and otoprotection” and “an expert in the area of [STS] as a . . . drug to use in children with medulloblastoma.” Ex. 1038, 98:9–17, 99:17–18, 101:18–102:13.” slip op. at 10

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “Paragraph 102 of Dr. Rassekh’s Declaration, however, does not support Patent Owner’s assertion. Instead, Dr. Rassekh testifies that [t]he stratum of previous craniospinal radiation therapy contained 8 participants: 2 of the 4 (50%) participants receiving STS had hearing loss compared to 4 of the 4 (100%) participants not receiving STS, and none of the hearing loss assessments were changed at the 1 year follow up period. (Ex. 1001 at 20: 28-32, 47-50.) Ex. 2024 ¶ 102. Dr. Rassekh offers no opinion on how many osteosarcoma patients with prior cranial irradiation and how many medulloblastoma patients with prior cranial irradiation had hearing loss.” slip op. at 20

  • 112 supportMotion to amend, deniedDenied

    “In sum, we find the disclosures of the ’243 application that Patent Owner relies on do not provide sufficient written-description support for the ototoxicity efficacy limitation.” slip op. at 21

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

    “F. Petitioner’s Asserted Unpatentability Grounds In light of our determination above that Patent Owner has not shown sufficient written-description support for proposed substitute claim 2 in the ’243 application, we do not reach the grounds of unpatentability set forth in Petitioner’s Opposition. See Revised MTA Opp. 17–25 (alleging non-enablement and obviousness).” slip op. at 26

  § 103 obviousness§ 112 disclosurecites Phillips
  Patents in suitUS 10,596,190
• Facebook, Inc. v. Palo Alto Research Center LLCAll claims unpatentable
  PTAB · Mar 22, 2023 · IPR2021-01461 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–5, 7–11, 13–17, 19, and 20 are unpatentable under § 103; PARC’s contingent motion to amend is denied because the pending substitute claims lack written-description support and are obvious.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Relying on Mr. Schmandt’s testimony, Facebook argues that a person of ordinary skill in the art “would have possessed at least a bachelor’s degree in electrical engineering or computer science, and two years of work experience in the field of context-based computer systems, such as the collection, processing and use of context data in computer systems capable of adapting their operation based on context.” Pet. 6 (citing Ex. 1002 ¶¶ 15– 18). Facebook also contends that a person might qualify as an ordinarily skilled artisan “with more formal education and less technical experience, or vice versa.” Id. For this proceeding, PARC does not dispute this proposed level of ordinary skill. PO Resp. 16–17. Because Facebook’s uncontroverted articulation of the level of ordinary skill in the art is supported by testimonial evidence and appears consistent with the types of problems and solutions in the ’439 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:4–33 (“Background” section of the ’439 patent, describing the field and related art as relating to the use of using contextual data in computer systems).” slip op. at 10

  • Strike new argumentNew argument consideredDecided for petitioner

    “construction of the term “facts and assertions” or the identification of facts and assertions within Cheng. See Paper 23, 1–2. Having reviewed the arguments, we do not consider them untimely. As we discuss in more detail below, Facebook relied on the ordinary and customary meaning of the term “facts and assertions” in its Petition, and then when PARC raised an alternative construction of the term in its Response, Facebook responded to those arguments. See infra Sections IV.B.2, IV.C.4(a). Facebook’s Reply only responded to arguments raised in PARC’s Response and was not untimely. See 37 C.F.R. § 42.23(b) (permitting a petitioner to respond to arguments in a patent owner response); Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018) (“[T]he petitioner in an inter partes review proceeding may introduce new evidence after the petition stage if the evidence is a legitimate reply to evidence introduced by the patent owner, or if it is used ‘to document the knowledge that skilled artisans would bring to bear in reading the prior art identified as producing obviousness.’” (quoting Genzyme Therapeutic Prod. Ltd. P’ship v. Biomarin Pharm. Inc., 825 F.3d 1360, 1369 (Fed. Cir. 2016))). Moreover, PARC had a meaningful opportunity to address the arguments in its Sur-reply and in oral argument. See PO Sur-reply 7–12; Tr. 22–34. Thus, we do not find Facebook’s contested arguments untimely and we have considered them in our decision.7” slip op. at 8

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

    “We agree with Facebook. As we discuss below, Cheng teaches a graph-based model that stores data in memory on a per-user basis. See infra Section IV.C.4(a); Ex. 1003, Fig. 7. Also, as PARC acknowledges, Facebook’s expert Mr. Schmandt stated in deposition that he assumed, for his analysis, that the term “context graph” requires a “graph-based model.” PO Resp. 22 (citing Ex. 2019, 36:16–37:8); see also PO Sur-reply 4. Thus, because Facebook’s analysis of Cheng is consistent with the assumption that “context graph” has the meaning PARC proposes in this proceeding, we do not need to construe the term “context graph” to reach our decision. 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 13

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

    “We agree with the parties that a person of ordinary skill in the art would have understood the term “fact” to include an indication of truth, whereas an assertion need not include such an indication. However, we disagree with PARC that a person of ordinary skill would have considered the term “assertion” to exclude facts. Indeed, in its ordinary and customary meaning, a fact stored in a context graph would be a type of assertion. We appreciate PARC’s argument that when two different terms appear in a claim, they presumably refer to different things. See PO Resp. 27 (citing CAE Screenplates, 224 F.3d at 1317). And we agree that the two terms have different meanings in claim 1 based on the plain meaning of each term. However, the specification refers to “stor[ing] facts and assertions about a user’s behavior and interests,” which simply appears to identify a single category of data for storage, i.e., “facts and assertions,” without specifying a clear difference between “facts” and “assertions.” See Ex. 1001, 3:21–22. In any event, we find no evidence of record suggesting that either (1) the (citing Pet. Reply 8–9). Because Facebook appears to have been relying on what it regarded as the plain meaning of the terms without proposing an explicit construction, we do not interpret Facebook’s argument in the Petition (Pet. 20–21) to imply that there is no distinction between a fact and an assertion, and do not find Mr. Schmandt’s later testimony (see, e.g., Ex. 2019, 41:3–11) inconsistent with arguments made in the Petition. ordinary and customary meaning of the term “assertion” excludes facts, or (2) that the ’439 patent uses these terms in a way that departs from their ordinary and customary meaning. That claim 1 requires the presence of both “facts” and “assertions” does not render the two terms superfluous, as this would exclude prior art in which a context graph includes only assertions but not facts. On the other hand, a disclosure of a collection of facts would meet the term “facts and assertions” because a person of ordinary skill in the art would have regarded any subset of the facts to also be assertions.” slip op. at 15

  Patent outcomesUS 9,208,439 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 9,208,439
• Twitter, Inc. v. Palo Alto Research Center LLCAll claims unpatentable
  PTAB · Mar 22, 2023 · IPR2021-01430 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–5, 7–11, 13–17, 19, and 20 are unpatentable under § 103; PARC’s contingent motion to amend is denied because the proposed substitute claims lack written-description support and are unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “Relying on Dr. Turnbull’s testimony, Twitter argues that a person of ordinary skill in the art “would at minimum have a bachelor’s in software, computer, or electrical engineering or computer science with at least two years’ experience in software development, including with respect to context-aware devices and systems, or the equivalent.” Pet. 16 (citing Ex. 1003 ¶ 24). Also, “[a]dditional graduate education could substitute for professional experience, or significant experience in electronic messaging could substitute for formal education.” Id. (citing Ex. 1003 ¶ 24). For this proceeding, PARC does not dispute this proposed level of ordinary skill. PO Resp. 21. Because Twitter’s uncontroverted articulation of the level of ordinary skill in the art is supported by testimonial evidence and appears consistent with the types of problems and solutions in the ’439 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:4–33 (“Background” section of the ’439 patent, describing the field and related art as relating to the use of contextual data in computer systems).” slip op. at 9

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

    “We agree as to Twitter’s last point, as we discuss below, that Cheng teaches a graph-based model that stores data in memory on a per-user basis. See infra Section IV.C.4(a); Ex. 1005, Fig. 7. Moreover, this decision does not address grounds of the Petition that omit Cheng as a reference, Cheng discloses a “context graph” under either party’s construction. Thus, we need not construe the term for this decision. See Nidec, 868 F.3d at 1017. Because the terms “recommender” and “application event data and/or operating system data” are not contested and are not material to our decision, we do not construe these two terms. 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))). To the extent that other claim terms are significant, we discuss them below in the context of the asserted prior art.” slip op. at 12

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

    “We determine that Twitter has persuasively, and with sufficient specificity, shown that the combination of Huomo and Cheng teaches all aspects of limitation 13[d], and that it would have been obvious to modify Huomo by using Cheng’s personal interest graph as the model for how facts and assertions are stored in Huomo’s “blackboard.” This modification would have been compatible with Huomo and would simply affect the form of the information, or types of information, that are stored in Huomo’s blackboard. See Intel Corp., v. PACT XPP Schweiz AG, No. 2022-1037 at 10–13 (Fed. Cir. Mar. 13, 2023) (there is motivation to combine where one reference addresses a problem in one way, and another reference addresses the same problem in an alternative way that would be a suitable option). We agree with Twitter that this modification would have been within the ordinary skill in the art, that there would have been a reasonable expectation of success, and that an ordinarily skilled artisan would have recognized benefits to using Cheng’s graph-based structure such as the ability to better track social relationships through annotating the nodes and edges, and the ability to more easily track users’ shared interests and the influences that users may have on each other. See Pet. 53–55; Ex. 1003 ¶¶ 156–161.” slip op. at 30

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightDecided for petitioner

    “We determine that Twitter has persuasively, and with sufficient specificity, shown that the combination of Huomo and Cheng teaches all aspects of limitation 13[d], and that it would have been obvious to modify Huomo by using Cheng’s personal interest graph as the model for how facts and assertions are stored in Huomo’s “blackboard.” This modification would have been compatible with Huomo and would simply affect the form of the information, or types of information, that are stored in Huomo’s blackboard. See Intel Corp., v. PACT XPP Schweiz AG, No. 2022-1037 at 10–13 (Fed. Cir. Mar. 13, 2023) (there is motivation to combine where one reference addresses a problem in one way, and another reference addresses the same problem in an alternative way that would be a suitable option). We agree with Twitter that this modification would have been within the ordinary skill in the art, that there would have been a reasonable expectation of success, and that an ordinarily skilled artisan would have recognized benefits to using Cheng’s graph-based structure such as the ability to better track social relationships through annotating the nodes and edges, and the ability to more easily track users’ shared interests and the influences that users may have on each other. See Pet. 53–55; Ex. 1003 ¶¶ 156–161.” slip op. at 30

  Patent outcomesUS 9,208,439 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 9,208,439
• Penumbra, Inc. v. Rapidpulse, Inc.All claims unpatentable
  PTAB · Mar 10, 2023 · IPR2021-01466 · APJ Jamie T Wisz · IPR · Final written decision

  Claims 1–18 are unpatentable under §103: claims 1–12, 15, 16, and 18 over Teigen and Grey; claims 13–14 over Teigen, Grey, and Yang; claim 17 over Teigen, Grey, and Matteo.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Based on our consideration of the full record, we find that, overall, Patent Owner’s definition is more specifically tailored to the claimed subject matter of the ’883 patent. We also find that, a person with a biomedical engineering degree could have the required background in fluid mechanics. See Ex. 1031, 45:21–46:7. Therefore, we find that a person of ordinary skill in the art would have a B.S. in mechanical or biomedical engineering with at least three years of experience in designing systems for minimally invasive intravascular procedures for treating occluded vessels or the equivalent and in consultation with medical professionals such as interventional neurosurgeons. Although we agree with, and have primarily adopted Patent Owner’s definition for an ordinarily skilled artisan in this proceeding, our analysis and conclusions herein would not change even under Petitioner’s definition. The parties also do not indicate that the outcome would differ based on the definition of the person of ordinary skill in the art. See Pet. 15; PO Resp. 6; Pet. Reply 1.” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner

    “as adopted by the Board in the Institution Decision. The ’883 patent explicitly defines this term, stating: The term “forward flow” is used herein to define an amount of liquid in the lumen 662 that exits the distal end 664 in a distal direction. Forward flow is defined as greater than 6 microliters of fluid (approximately 1 mm of catheter length of ID 0.071″=5.7 μL). Ex. 1001, 36:18–23 (emphasis added). Moreover, in discussing problems with the prior art systems, the ’883 patent states that “[w]hen positive pressure exists at the distal end of the lumen, liquid from inside the lumen exits out from the distal end of the catheter in a distal direction. This is referred to as forward flow.” Id. at 2:62–65. In the ’883 patent, the patentee acted as its own lexicographer as evidenced by usage of language such as “is used herein to define,” “is defined,” and “is referred to as,” to discuss “forward flow.” We find that the definition of “forward flow” in the ’883 patent specification would provide a person of ordinary skill with “reasonable clarity, deliberateness, and precision” as to the meaning of the term. See Paulsen, 30 F.3d at 1480; see also Ex. 1030 ¶¶ 13–14; Ex. 2001 ¶¶ 53, 62. Thus, we construe the term, “forward flow,” to mean “an amount of liquid in the lumen that exits the distal end in the distal direction that is greater than 6 microliters.”” slip op. at 14

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

    “As discussed above, we construed “forward flow” to mean “an amount of liquid in the lumen that exits the distal end in the distal direction that is greater than 6 microliters.” Thus, for the ’011 provisional to provide support for this limitation, the provisional must demonstrate that the inventors had possession of preventing greater than 6 microliters of fluid out of the distal end of the catheter. While Patent Owner points to disclosure from the ’011 provisional application which describes “a minimal amount of momentum transfer from the fluid column to the stuck clot to unstick the clot sufficiently” and “[t]he exiting movement of fluid [being] limited to a specific volume and/or pressure and is automatically and precisely controlled” to prevent the “possibility of overshooting,” it would not convey to one of ordinary skill in the art that the inventors were in possession of a device that limited forward flow to no greater than 6 microliters of fluid. PO Resp. 33 (citing Ex. 1003 ¶¶ 16, 138). Patent Owner also contends that the ’011 provisional application provides “multiple examples of liquid flow exiting the distal end of the catheter such that no forward flow occurs, such as 1 microliter or 0.5 mm of column shift.” PO Resp. 34 (citing Ex. 1003 ¶ 91). However, the disclosure cited by Patent Owner provides ranges of liquid flow of “approximately 0.001 ml to approximately 1.0 ml, in particular, approximately 0.1 ml to approximately 0.5 ml” and exemplary length of shift distances of “approximately 0.5 mm to approximately 30 mm, in particular, approximately 0.5 mm to approximately 15 mm.” Ex. 1003 ¶ 91. There is nothing in the disclosure of the ’011 provisional application that specifically directs the person of ordinary skill to the portions of these ranges which fall within the ’883 patent’s definition of no “forward flow” (i.e., no greater than 6 microliters of fluid). In fact, the majority of the cited ranges are greater than 6 microliters, going all the way up to 1,000 microliters, such that there would be forward flow in these examples. See Ex. 1030 ¶ 29; Purdue Pharma, 230 F.3d at 1326–27 (“[O]ne cannot disclose a forest in the original application, and then later pick a tree out of the forest and say here is my invention. In order to satisfy the written description requirement, the blaze marks directing the skilled artisan to that tree must be in the originally filed disclosure.”); Fujikawa v. Wattanasin, 93 F.3d 1559, 1571 (Fed. Cir. 1996).” slip op. at 21

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

    “AIA § 102 draws a distinction between actually being entitled to a right of priority to, or the benefit of, a prior-filed application according to the definition of “effective filing date” of a claimed invention in AIA 35 U.S.C. § 100(i)(1)(B), and merely being entitled to claim a right of priority to, or the benefit of, a prior-filed application for prior-art purposes according to the use of “effectively filed” in AIA 35 U.S.C. § 102(d). See 35 U.S.C. §§ 100(i)(1)(B), 102(a)(2), 102(d)(2); MPEP § 2154.01(b). USPTO guidance also indicates that AIA § 102 prior-art reference effective-filing-date determinations differ from pre-AIA law. For example, a 2018 Memorandum to the Patent Examining Corps states, in the context of prior-art determinations, that “[t]he requirement that one of the claims in the patent [document] . . . be supported by the written description of the provisional application in compliance with pre-AIA 35 U.S.C. § 112, first paragraph (or AIA 35 U.S.C. § 112(a)), is not applicable when examining an application subject to the first inventor to file provisions of the AIA.” Robert W. Bahr, Memorandum re: Critical Reference Date Under pre-AIA 35 U.S.C. §102(e) (Apr. 5, 2018), available at http://www.uspto.gov/sites/ default/files/documents/dynamic_memo_05apr2018_0.pdf (emphasis added) (citing Dynamic Drinkware, 800 F.3d at 1381 n.2; 157 Cong. Rec. 3423 (2011) (explaining the distinction between being entitled to claim priority or benefit in AIA 35 U.S.C. § 102(d) and actually being entitled to priority or benefit under 35 U.S.C. § 119, 120, or 365)). This Memorandum further indicates: The date subject matter was “effectively filed” under AIA 35 U.S.C. § 102(d) for purposes of considering a U.S. patent, a U.S. patent application publication, or an international application publication as prior art under AIA 35 U.S.C. § 102(a)(2) is discussed in MPEP § 2154.01(b), and is not affected by Dynamic Drinkware or [Amgen v. Sanofi, 872 F.3d 1367, 1380 (Fed. Cir. 2017)] and is not being modified by this memorandum. Id. at 2. MPEP § 2154.01(b) explicitly states, as a result of the distinction discussed above, in application of the AIA version of § 102, “the question of whether a patent or published application is actually entitled to priority or benefit with respect to any of its claims is not at issue in determining the date the patent or published application was ‘effectively filed’ for prior art purposes.” MPEP § 2154.01(b) (emphases added).” slip op. at 31

  Patent outcomesUS 10,531,883 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 10,531,883

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.