• 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
• Shenzhen Tuozhu Technology Co. Ltd. v. Stratasys, Inc.Institution denied
  PTAB · Oct 6, 2025 · IPR2025-00585 · APJ Lilan Ren · IPR · Institution

  The Board denied institution on claims 1–6, 10–19 because claim 1’s scope is ambiguous and the petition did not show a reasonable likelihood of prevailing on any asserted obviousness ground.

  RulingsInstitution decision

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

    “review. See 35 U.S.C. § 314 (2024); 37 C.F.R. § 42.4(a) (2024). Institution of an inter partes review requires that “the information presented in the petition . . . and any 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.” 35 U.S.C. § 314(a). For the reasons set forth below, we determine that the scope of claim 1 is ambiguous and that there is not a reasonable likelihood that Petitioner will prevail with respect to at least one challenged claim, and we deny inter partes review.1” slip op. at 2

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

    “distinguishes and contrasts build material property from operational parameters. The diagnostic test passage therefore only describes a diagnostic test of the build material property but does not describe a subsequent diagnostic test to assess whether an operational parameter is suitable for the printer. Based solely on the diagnostic test passage and the prosecution history, a possible interpretation may be that the operational parameter determination in claim element 1b encompasses the diagnostic testing in claim element 1c. That is, “performing a diagnostic test to determine whether the operational parameter is suitable for the three-dimensional printer” in claim element 1c is subsumed as part of “determining an operational parameter of a fabrication process using the three-dimensional printer based upon the data, the operational parameter including at least one of a build platform temperature, a build volume temperature, an infill requirement, a rafting requirement, a support structure requirement, and a cooling requirement” in claim element 1b.” slip op. at 15

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther

    “benefit of the filing date of an earlier filed application only if the disclosure of the earlier application provides support for the claims of the later application, as required by 35 U.S.C. § 112.” PowerOasis, Inc. v. T-Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008); see also Research Corps. Techs. v. Microsoft Corp., 627 F.3d 859, 871–72 (Fed. Cir. 2010) (holding that claims of the later-filed application, which were not limited to a “blue noise mask,” were “not entitled to claim the benefit of their parent applications’ filing dates”); ICU Med., Inc. v. Alaris Med. Sys., 558 F.3d 1368, 1377–78 (Fed. Cir. 2009) (holding that “spikeless” claims “added years later during prosecution” were not supported by the specification which “describe[d] only medical valves with spikes”); Tronzo v. Biomet, Inc., 156 F.3d 1154, 1158–60 (Fed. Cir. 1998) (holding the generic shaped cup claims of the later-filed child application were not entitled to the filing date of the parent application that “disclosed only a trapezoidal cup and nothing more”). “To satisfy the written description requirement the disclosure of the prior application must convey with reasonable clarity to those skilled in the art that, as of the filing date sought, [the inventor] was in possession of the invention.” PowerOasis, 522 F.3d at 1306 (emphasis omitted; alteration in original). The sufficiency of written description support is based on “an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc).” slip op. at 20

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art in the field in the relevant time frame would have had “(1) at least a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a related field, and (2) at least two years of research or industry experience in 3D printing or materials used for 3D printing.” Pet. 5 (citing Ex. 1003 ¶ 20). Petitioner also contends that “[a]dditional experience could substitute for a formal degree or formal training (and vice versa).” Id. (citing the same). Patent Owner contends that an ordinarily skilled artisan “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Electrical Engineering, Chemical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” Prelim. Resp. 12. For purposes of this decision, we adopt Petitioner’s definition of the level of ordinary skill in the art as it appears unopposed and consistent with the disclosures of the ’464 patent and the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 9

  Claim construction§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 11,167,464
• 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
• AT&T Mobility LLC / AT&T Services Inc. et al. v. Daingean Technologies Ltd.No claims unpatentable
  PTAB · Jul 14, 2025 · IPR2024-00402 · APJ Mary C Hoffman · IPR · Final written decision

  The Board granted Patent Owner’s revised non-contingent motion to amend, canceling claims 1–4 and substituting claims 7 and 8, which Petitioner did not prove unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted

    “whether the motion to amend meets the statutory and regulatory requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121.” See Lectrosonics, Inc. v. Zaxcom, Inc., IPR2018-01129, Paper 15 at 4 (PTAB Feb. 25, 2019) (precedential). A “patent owner bears the burden of persuasion to show, by a preponderance of the evidence, that the motion to amend complies” with the applicable statutory and regulatory requirements. 37 C.F.R. § 42.121(d)(1). Specifically, a patent owner must demonstrate the following: (1) the amendment proposes a reasonable number of substitute claims; (2) the amendment responds to a ground of unpatentability involved in the trial; (3) the amendment does not seek to enlarge the scope of the claims of the patent; and (4) the amendment does not introduce new matter. See 35 U.S.C. § 316(d); 37 C.F.R. § 42.121(a)–(b). For the reasons explained below, Patent Owner satisfies its burden of persuasion to show that the amendments comply with the applicable statutory and regulatory requirements.” slip op. at 8

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Both parties rely on expert testimony for their respective positions relating to the number of years of experience needed to attain ordinary skill, but neither expert cites supporting evidence for their testimony. See Ex. 1002 ¶ 33; Ex. 2002 ¶ 15. Our decision is the same regardless of whether the length of experience is two years or three. We find Patent Owner’s proposed “wireless communications” is more consistent with the ’958 patent than Petitioner’s proposed “telecommunication,” which encompasses a variety of technologies including, e.g., landline and wireless telephones, cable, and satellite. See Ex. 1001, 1:11–62 (describing the invention in terms of wireless communications). Accordingly, we adopt a modified version of Petitioner’s proffered level of ordinary skill in the art, substituting “wireless communications” for “telecommunication.” Neither party, moreover, indicates the overall result would change based on a different definition.” slip op. at 18

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

    “We agree with Patent Owner that the recited second type SIBs exclude first type SIBs. The plain meaning of “first type” and “second type” indicates that the first type and second type are different in kind. RMTA 22 (App. A). Our interpretation is consistent with the Specification, which explains that second type SIBs exclude first type SIBs. As Patent Owner points out, the ’958 patent discloses “first type of system information (1TYP SIB) is . . . essential . . . for initial system access” and “second type of system information (2TYP SIB) is nonessential system information . . . defined as all other types of information, and thus excludes the [] information required for initial access.” Id. at 11–12 (citing Ex. 1001, 8:34– 46); see also Ex. 1001, Abstract (interchangeably using the terms second type and non-essential). Despite Petitioner’s argument that this disclosure is non-limiting and directed to a disclaimed example embodiment (Opp. 8–9), Petitioner could not identify any embodiment, among the approximately forty disclosed embodiments, describing something other than the first type SIB being essential information and the second type SIB being non-essential information. Tr. 22:18–26. Even the Petition acknowledges that “the ’958 Patent further classifies a second type of system information, the ‘non-essential’ SI, which is defined as all other types of information excluding that first type of information required for initial access.” Pet. 5. Furthermore, the prior art of record suggests that a person of ordinary skill would have understood second type SIBs exclude first type SIBs. See Ex. 1008 ¶ 48 (describing two categories of system information, “essential SI” and “Other SI”). Patent Owner’s expert also understood the recited first and second type SIBs as being mutually exclusive. See Ex. 1011, 49:10–13. For the above reasons, we do not agree with Petitioner that the recited second type SIB lacks any requirements, nor do we interpret claims 7 and 8 such that the first type SIB could be a second type SIB.” slip op. at 19

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

    “(d) Limitation 7h: Analysis We agree with Patent Owner that Petitioner’s arguments with respect to limitation 7h are insufficient because they fail to address the limitation as written and improperly incorporate previous arguments by reference. For example, Petitioner did not map the recited “group identifier” when opposing Patent Owner’s Revised Motion to Amend. See Opp. 16–17. In its Sur-reply, Petitioner contends that limitation 7h’s requirement of transmitting the group identifier was previously “set out in Patent Owner’s prior papers,” but does not refer to any specific papers or exhibits. Pet. Surreply 11–12. We decline to search for and piece together Petitioner’s arguments and evidence to develop a persuasive theory of unpatentability. See 37 C.F.R. section 42.6(a)(3). Petitioner similarly failed to address adequately where Lee discloses or suggests the recited “compressed format” and “plural parameters.” See Opp. 16–17. Aside from the above concerns, we also do not see sufficient explanation with respect to limitation 7h’s requirement that the transmitting by broadcast be based on a comparison of the value tag. Petitioner argues that, because Patent Owner does not dispute limitation 7g, “it would have been obvious to a POSITA to use the same value tag[] to determine the system information broadcast in Lee’s compressed format embodiment.” Pet. Sur-reply 12. This conclusory statement is not supported by any citations to evidence and was improperly introduced in the Sur-reply. Moreover, whether it was obvious to determine what system information is broadcast is not commensurate with the claim scope because limitation 7h requires that the broadcasting (not the broadcast content) be based on a comparison of the value tag. See supra III.B.4 and IV.B. Further, we are not persuaded that Lee’s transmitting by broadcast is” slip op. at 26

  Patent outcomesUS 10,841,958 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · Nautilus
  Patents in suitUS 10,841,958
• 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
• Snap Inc. / Facebook, Inc. et al. v. Palo Alto Research Center LLCAll claims unpatentable
  PTAB · Mar 24, 2023 · IPR2021-01294 · APJ Sheila F Mcshane · IPR · Final written decision

  The Board held all challenged claims 1–25 unpatentable under the asserted obviousness grounds and denied Patent Owner’s contingent motions to amend.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “2. Level of Ordinary Skill in the Art Snap proposes that a person of ordinary skill in the art at the time of the ’599 patent would have possessed “an undergraduate degree in electrical engineering, computer engineering, computer science or a related field along with at least two years of work experience in the field of content presentation and context-based systems/processes.” Snap Pet. 3 (citing Snap IPR, Ex. 1002 ¶¶ 30–32); Snap IPR, Ex. 1022 ¶ 32. Snap further asserts that additional “education can supplement practical experience and vice versa.” Id. In the Decision on Institution, we determined that Snap’s proposed description of the qualifications of a person of ordinary skill in the art aligned with the technology and claims of the ’599 patent. Snap Inst. Dec. 6–7. For this proceeding, Patent Owner and Dr. Martin apply this level of skill in the art. Snap PO Resp. 11–12; Snap IPR, Ex. 2003 ¶¶ 48–50. Accordingly, for the reasons given in the Decision on Institution, we adopt Snap’s proposed level of ordinary skill in the art. Snap Inst. Dec. 6–7.” slip op. at 11

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

    “Dr. Martin also provides consistent testimony on this issue. Snap IPR, Ex. 2003 ¶¶ 81–82. Put simply, the Specification’s disclosure is that the set of rules for multiple content packages includes an expected response, and actions are then performed based on whether an expected response is or is not provided. Moreover, as Dr. Almeroth testifies, neither the claims nor the Specification use the term “unexpected response”—rather the Specification only identifies an “expected response.” Snap IPR, Ex. 1022 ¶ 42. Accordingly, the disclosures in Table 1 and the Specification support Dr. Almeroth’s testimony that a person of ordinary skill would have understood that “the claimed ‘determin[e/ing]’ limitation requires what it plainly recites: ‘determin[e/ing] whether the received response matches the expected response[]’. . . . [i]t does not require an unexpected response not known to the system.” Snap IPR, Ex. 1022 ¶ 51.” slip op. at 18

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

    “time,’ ‘type of location,’ and other contextual information to automatically determine whether users would like to undertake learning activities.” Twitter Pet. Reply 18 (citing Twitter IPR, Ex. 1005, 2 3, 5 (“A check . . . to see if the information from the database corresponds with the location sensor (i.e. a check on whether the learner is really keeping his/her schedule).”), Fig.1; Twitter IPR, Ex. 1025 ¶ 49; Twitter IPR, Ex. 1003 ¶¶ 85, 157–162, 238, 435, 451, 517; Twitter Pet. 20–21). Accordingly, the evidence of record support that Yau teaches that context triggers the display of a content piece, such as an exercise/test/quiz. Patent Owner also argues that Twitter asserts that PALLES’ content piece is “‘exercise[s],’ ‘test[s],’ and/or ‘MP Quiz[zes],’” but also contends that Yau’s “formal assessment” is the claimed content piece. Twitter PO Resp. 32. Patent Owner argues that “Twitter points back to its limitation 12.1 PALLAS evidence for the purported ‘content piece’” and also does not mention Yau for limitation 12.5 and 12.6 and “only conclusorily states that ‘PALLAS in view of Yau renders obvious triggering an exercise/test/quiz.’” Id. Patent Owner’s arguments overlook Twitter’s assertion, with Dr. Turnbull’s supporting testimony, that a person of ordinary skill in the art would have understood that Yau’s formal assessments are “tests with answers for comparing against learner’s responses to assess knowledge/performance/skill (contrasting with ‘un-assessed’ exercises whose responses are unchecked).” Twitter Pet. 43; Twitter IPR, Ex. 1003 ¶ 154. Further, Patent Owner overlooks Petitioner’s assertion that it is implementing PALLAS’s context-triggerbased content display using Yau’s teachings of displaying assessments/questions based on context. Twitter Pet. 43. Patent Owner also asserts that in the PALLAS-Yau combination, Twitter does not explain how a person of ordinary skill in the art would have combined the prior art in the manner Petitioner alleges. Twitter PO Resp. 42. Patent Owner argues that “PALLAS says nothing about forcing quizzes, tests, or exercises on its users without the users asking for such exercises,” and a person of skill would understand that the combined system still requires that a student select a learning activity and that PALLAS’s system should be unobtrusive because learners “may have small time slots to engage in learning.” Id. (citing Twitter IPR, Ex. 2013 ¶ 168; Twitter IPR, Ex. 1004, 54). Patent Owner further contends that “Twitter’s conclusory, hindsight-driven statements” do not suffice and PALLAS teaches away from the modifications suggested by Twitter. Id. at 42–43 (citing Twitter IPR, Ex. 2013 ¶ 144). Patent Owner argues that because a learner may not have time to complete a test, a person of ordinary skill in the art would not be motivated to change PALLAS to trigger exercises/tests/quizzes based on location or time. Id. at 43 (citing Twitter IPR, Ex. 2013 ¶¶ 142–144). The evidence of record does not support Patent Owner’s arguments.” slip op. at 115

  • ScopeMotion to amend, grantedGranted

    “2. Enlarging Scope of Claims Patent Owner asserts that it proposes narrowing limitations in direct response to the grounds of unpatentability involved in this proceeding. See, e.g., Snap Mot. 3–4. Facebook argues Patent Owner is “improperly attempting to enlarge the scope of the original claims.” Facebook Pet. Opp. 1. Facebook asserts, “[i]f ‘an expected response’ means one or more expected responses, therefore, determining whether the received response ‘matches the expected response’ means that the received response must match [all of] the one or more previously-recited expected responses in the content package.” Id. at 3 (emphasis omitted). Facebook then argues “the term ‘predefined response’ is broader than ‘expected response,’” because “an ‘expected response’ does not include any conceivable or possible response; it is a response that is expected.” Id. at 4–5 (emphasis omitted). Twitter argues that “‘predefined response’ is broader than ‘expected response’ because a ‘predefined response’ can include any possible response as long as that response has been somehow defined in advance.” Twitter Pet. Opp. 2. We consider the amendments in view of the claim as a whole. Although the term “one predefined response” may be broader than “an expected response,” we also consider the amended portion “wherein the received response is expected if the received response matches one or more of the at least one predefined response,” and “the received response is unexpected if the received response does not match any of the at least one predefined response.” Unless the response had been predefined within the content package, any “received response” could not be considered “expected” under the claims, and the additional clause requires a match of the response with the predefined response to be deemed “expected.” This equates to an equivalent scope to the original claim. This is consistent with Dr. Martin’s testimony, which we credit, that he is not aware of a situation where the substitute but not original claims are infringed because “[t]he substitute claims would only be satisfied when a ‘predefined response’ in the substitute claims is an ‘expected response’ in the original claims.” Facebook IPR, Ex. 2023 ¶ 59.” slip op. at 136

  Patent outcomesUS 8,489,599 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo · Bilski · Electric Power · Phillips · KSR · Graham
  Patents in suitUS 8,489,599
• Metacluster LT, Uab v. Bright Data Ltd.Instituted
  PTAB · Mar 23, 2023 · PGR2022-00052 · APJ Sheila F Mcshane · PGR · Institution

  Instituted PGR on claims 1–27; the Board found it more likely than not that the claims are obvious over Mithyantha, with claim 19 also challenged over Mithyantha and RFC 2616.

  RulingsInstitution decision

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

    “We may not institute a post-grant review “unless . . . the information presented in the petition filed under section 321, if such information is not rebutted, 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). Upon consideration of the arguments and evidence, we determine Petitioner has demonstrated that it is more likely than not that at least one of the challenged claims is unpatentable. Accordingly, we institute a post-grant review of the challenged claims of the ’034 patent.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “had at least a bachelor’s degree in Computer Science or related field (or equivalent experience), and at least two years’ experience working with and programming networked computer systems.” Pet. 13 (referencing Ex. 1002 ¶ 33).” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for petitioner

    “The district court considered the issue of whether a client device, for instance, should be construed in a role-based or structural manner, and the evaluation included whether a device could sometimes be operated as a client and at other times could operate as something else. Ex. 1018, 48–51. In support, the district pointed the patent disclosure that: Any network element in the system may be a dedicated device that assumes only a single role, and thus being only a client (using tunnels), a tunnel, a client (using agents/ peers), an agent, or a peer device. Alternatively or in addition, a network element may be capable of assuming two or more roles, either at different times or simultaneously, from the list of roles including a client (using tunnels), a tunnel, a client (using agents/peers), an agent, or a peer device. Alternatively or in addition, a device may be capable of assuming all of the above roles. Ex. 1018, 50 (quoting ’866 patent at 125:33–42, with identical disclosure in ’034 patent (Ex. 1001, 125:24–33)).” slip op. at 10

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

    “At this stage of the proceedings, we do not agree that Mithyantha’s second appliance 200’/200b cannot be considered the claimed “second client device” and its first appliance 200/200a cannot be considered the claimed “third server.” As discussed supra Section II.C, we have adopted the district court’s constructions of claim terms. More specifically, the district court determined, and we concur based on the present record, that “client device” is “a device that is operating in the role of a client by requesting services, functionalities, or resources from other devices” and a “first server” functions as “a server that is not the client device.” On this record, Petitioner has demonstrated that Mithyantha’s second appliance 200’/200b functions as the claimed “second client device,” as it operates as a client by requesting services, functionalities, or resources from other devices, that is, it transmits HTTP web requests over the network to a server. See Pet. 44– 45. Mithyantha also discloses that its first appliance 200/200a functions in a server role, with appliance 200/200a sending back responses to client 102a, that is, content from the web server, and it is a separate element from a client device. See id. at 41–42. Moreover, as discussed above, Petitioner’s assertions are consistent with the role-based nature of the elements as disclosed in the ’034 patent. Further, we do not find that Petitioner’s applications of the claim elements to Mithyantha are arbitrary because they are consistent with the district court’s claim construction of the respective claimed elements and the elements’ functions and roles, as discussed. Moreover, Mithyantha discloses that its appliances can provide different functions (see e.g. Ex. 1009, 5:31–33, 8:65–67, 9:8–21, 9:53–55; 23:58–64), and may be implemented in many forms. That is, the implementation of appliance 200 is generally described as being on any form of computing device such as “computing device 100,” and “computing device 100 can be any workstation, desktop computer, laptop or notebook computer, server, handheld computer, mobile telephone.” See id. at 13:65– 142, 16:58–64. We do not agree with Patent Owner’s allegations regarding a required architecture. Patent Owner does not explain how these requirements are recited in the limitations of claims. Instead, at this juncture, it appears that the arguments are an attempt to impermissibly introduce limitations into the claim that are not recited. Similarly, we do not agree with Patent Owner’s arguments on required anonymity because this requirement is not recited in the claims.” slip op. at 18

  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo · KSR · Graham
  Patents in suitUS 11,272,034
• 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

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.