PTAB
Advanced fields
23 decisions · 414msnewest first
  • 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
  • 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
  • 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
  • PTAB · Dec 3, 2024 · IPR2023-01020 · APJ Scott Raevsky · IPR · Final written decision

    Claims 1–20 are unpatentable as obvious over Lyren and Reif; the Board did not reach the Clement, Osman, and Sauk ground.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “A POSA [person of ordinary skill in the art or “POSITA”] in the relevant timeframe (2015 to 2019) would have had a Bachelor’s degree in computer science/engineering, music technology, or a related field, and at least two years of industry experience, or academic research experience, in virtual/augmented reality, audio engineering, or an equivalent. Additional education can compensate for less experience, and vice-versa.” slip op. at 7

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

      “1. environment Patent Owner initially argues that “environment” should mean “physical surroundings in which a user operates.” PO Resp. 6. Petitioner responds that the plain meaning of environment “encompasses physical and virtual environments.” Reply 2. During the hearing, Patent Owner conceded that Petitioner’s construction for environment is correct. Tr. 49:24–50:10. We agree with this construction and apply it here. See, e.g., Ex. 1001, 28:16 (referring to “a physical or a virtual environment”). “Environment” encompasses physical and virtual environments.” slip op. at 8

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

      “insufficient to support the concept of alerting a user that the user is leaving a virtual environment. In so deciding, we need not address the parties’ contentions about boilerplate. Regardless of whether the sentence at 168:15–16 of the ’140 application is boilerplate, we agree with Petitioner that “there is no suggestion of the specific claimed combination.” Reply 22 (citing Ex. 1146 ¶ 82). That is, if one views the “[e]xamples herein” from Figure 6 as taking place “in computer rendered spaces (VR)” or “in partially computer rendered spaces (AR),” there is still no disclosure of alerting a user that a user is leaving a virtual environment. See Ex. 1028, 168:15–16. For instance, if Alice in the Figure 6 example mentioned above is entering a virtual car instead of a real car, Alice is still in a virtual environment. See id. at 120:13–27. Thus, relying on Figure 6 to take place “in computer rendered spaces (VR)” does not support alerting that a user is leaving those virtual spaces. See id. at 168:15–16. Petitioner also correctly identifies a problem with analogizing the Alice example to a virtual environment—namely, it would no longer make sense to give Alice an audible warning. See Reply 22 (citing Ex. 1146 ¶ 82). In the example, Alice’s earphones switch from binaural sound to mono sound when Alice enters a real car because “[t]he state where Alice is located . . . prohibits drivers from localizing sound while driving a motorized vehicle.” Ex. 1028, 120:15–18. But it would not make sense (nor does the ’140 application disclose) for a state to prohibit Alice to localize sound while driving a virtual vehicle. We therefore find compelling Petitioner’s argument, supported by the testimony of Dr. Roginska, which we credit, that there is no “disclosure that 3D audio would not be permitted in a 3D virtual space.” Reply 22 (citing Ex. 1146 ¶ 82). Accordingly, Patent Owner’s second support argument fails.10” slip op. at 18

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

      “One benefit Petitioner proposes to support a rationale to combine is that a POSITA “would have implemented this feature to help protect the users from injury by bumping, hitting, tripping over, etc., real-world objects when moving around while viewing the virtual environment in the HMD (i.e., a type of head-mounted WED).” Id. at 43–44 (citing, e.g., Ex. 1003 ¶¶ 90, 251–254). Petitioner provides additional argument and evidence supporting a motivation to combine, with a reasonable expectation of success. See id. at 42–46. We agree that, in the combination, a POSITA would have implemented Lyren’s audible alerts to alert the user that the user is leaving Reif’s safe zone (and thus the virtual environment) to help keep users safe. Id. at 52 (citing Ex. 1003 ¶¶ 250–268). We also agree with Petitioner’s articulated benefit that the combination would “help protect the users from injury by bumping, hitting, tripping over, etc., real-world objects when moving around while viewing the virtual environment in the HMD (i.e., a type of head-mounted WED).” Id. at 43–44. Accordingly, we agree with Petitioner that the combination of Lyren and Reif discloses each limitation of claim 14, as well as similar limitations of claims 1 and 7, and that one of ordinary skill in the art would have combined Lyren and Reif in the manner proposed, with a reasonable expectation of success.” slip op. at 24

    Patent outcomesUS 10,448,184 unpatentable
    Claim construction§ 103 obviousness§ 112 disclosurecites KSR · Graham
    Patents in suitUS 10,448,184
  • PTAB · Dec 3, 2024 · IPR2023-01019 · APJ Scott Raevsky · IPR · Final written decision

    Claims 1–20 are unpatentable as obvious over Lyren and Reif; the Board did not reach the Clement, Osman, and Sauk ground.

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

      “Accordingly, we are not persuaded that the ’140 application supports the claimed concept of warning or alerting a user that the user is leaving the virtual environment. Thus, the ’140 application does not support the full scope of the limitations “warning the user that the user is leaving the 3D virtual environment” in claim 1 and “alerting the user that the user is leaving the environment” in claims 7 and 14. The parties have not made any additional arguments regarding support in the ’140 application for limitations of the dependent claims. We conclude that no claim of the ’179 patent is entitled to priority to the ’140 application.” slip op. at 22

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

      “We agree that, in the combination, a POSITA would have implemented Lyren’s audible alerts to alert the user that the user is leaving Reif’s safe zone (and thus the virtual environment) to help keep users safe. Id. at 51 (citing Ex. 1003 ¶¶ 250–263). We also agree with Petitioner’s articulated benefit that the combination would “help protect the users from injury by bumping, hitting, tripping over, etc., real-world objects when moving around while viewing the virtual environment in the HMD (i.e., a type of head-mounted WED).” Id. at 43. Accordingly, we agree with Petitioner that the combination of Lyren and Reif discloses each limitation of claim 14, as well as similar limitations of claims 1 and 7, and that one of ordinary skill in the art would have combined Lyren and Reif in the manner proposed, with a reasonable expectation of success.” slip op. at 26

    • ExcludeMotion to exclude, deniedGranted in part

      “paragraphs of Dr. Roginska’s declarations in Exhibits 1003 and 1146. Mot. 1; Reply to Opp. 1. Some of these paragraphs support Petitioner’s challenge based on Clement, Osman, and Sauk. Mot. 2–5, 7–11. Because we do not reach Petitioner’s challenge based on Clement, Osman, and Sauk, we do not rely on the portions of Dr. Roginska’s declarations addressing Clement, Osman, and Sauk. Accordingly, we dismiss this portion of Patent Owner’s Motion to Exclude as moot.” slip op. at 27

    Patent outcomesUS 10,368,179 unpatentable
    § 103 obviousness§ 112 disclosurecites KSR · Graham
    Patents in suitUS 10,368,179
  • PTAB · Oct 7, 2024 · IPR2024-00731 · APJ Jennifer S Bisk · IPR · Institution

    The Board instituted review of claims 1–6, 8–13, 15–20, and 22–27 based on a reasonable likelihood that Wang, Dua, and Yong render them obvious.

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

      “Pursuant to 35 U.S.C. § 314(a), the Director may not authorize an inter partes review unless the information in the petition and 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 that follow, we institute an inter partes review as to claims 1–6, 8–13, 15–20, and 22–27 of the ’578 patent on the sole ground of unpatentability asserted in the Petition.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “understanding of a person of ordinary skill in the art at the time of the invention. Graham v. John Deere Co., 383 U.S. 1, 17 (1966). For purposes of this proceeding, Petitioner argues a person of ordinary skill in the art at the time of the invention would have had “a bachelor’s degree in computer science, computer engineering, or equivalent with one to two years of experience in the field of mobile transactions.” Pet. 8 (citing Bederson Decl. ¶¶ 35–37). Petitioner adds that “[a]dditional education or experience might substitute for the above requirements.” Id. To the extent necessary, and for purposes of this Decision, we accept this assessment offered by Petitioner, as it is supported by Dr. Bederson’s testimony and appears consistent with the ’578 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need” slip op. at 7

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

      “scanner, reader, or camera” that is aimed at a barcode or special code of a product, the price of which is then added to the retail bill. Pet. 10–11 (quoting Ex. 1001, 7:45–49, 9:5–11). According to Petitioner, the Specification does not elaborate further on the meaning of the term “information concerning prices of goods.” Id. at 11. Petitioner, thus, interprets the term to encompass scenarios in which price information is received directly or indirectly. Id. Petitioner notes that during prosecution of the ’578 patent, the Examiner rejected this limitation over prior art, stating that prior art “sends the scanned bar code information to the server,” which “then preferably returns a description of the item and information,” and “[t]his item description and price information is displayed on the telephone’s display.” Id. at 12 (quoting Ex. 1002, 231). According to Petitioner, this is an example of indirectly receiving information concerning the prices of goods as it comes from a queried server, not from the item itself. Id. Petitioner notes that Patent Owner never disputed, and in fact, made statements supporting that these actions were encompassed by the claim limitation. Id. (citing Ex. 1002, 214). We agree with Petitioner that nothing in the claim language or the Specification requires that the claimed optical input receive information concerning the prices of goods directly from the goods themselves. Thus, on this record, we preliminarily construe the term “receiving information concerning the prices of goods” to encompass receiving pricing information from a server.” slip op. at 9

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

      “In an inter partes review, the burden is on the petitioner to show a reasonable likelihood that it would prevail on a ground of unpatentability. 35 U.S.C. § 314(a). With respect to entitlement to any earlier effective filing date, however, a patent owner is not presumed to be entitled to the earlier filing dates of ancestral applications that do not share the same disclosure, such as in a continuation-in-part situation. See PowerOasis, Inc. v. T–Mobile USA, Inc., 522 F.3d 1299, 1305–06 (Fed.Cir.2008) (stating that once a defendant establishes that a reference is § 102(b) prior art, burden is on patent owner to come forward with evidence proving priority to an earlier filing date).” slip op. at 12

    Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham
    Patents in suitUS 8,270,578
  • PTAB · Jul 31, 2024 · PGR2023-00016 · APJ Stephen E Belisle · PGR · Final written decision

    Claims 1–3, 5, 7–10, 12, 14–17, and 19 are unpatentable based on lack of written description, indefiniteness, anticipation, and obviousness.

    RulingsFinal written decision
    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateUnpatentable

      “B. Claims 1–20 of the ’705 Patent Petitioner argues that claims 1–20 of the ’705 patent have an effective” slip op. at 19

    • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not enabledUnpatentable
    • Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteUnpatentable
    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
    Patent outcomesUS 11,297,705 unpatentable
    Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · Nautilus
    Patents in suitUS 11,297,705
  • PTAB · Jul 10, 2024 · IPR2023-00319 · APJ Brent M Dougal · IPR · Final written decision

    Claims 5, 15, and 25 were not shown unpatentable because Barsoum supports their priority date, and neither Barsoum nor ATSC327 qualifies as prior art.

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

      “Petitioner does not sufficiently explain why claim 5 requires this type of optimization, or why this would be required in order for Barsoum to provide written description support for the claim. Claim 5 does not expressly require optimization of phase considerations and Petitioner does not argue for a claim construction that would include such a requirement.” slip op. at 17

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

      “(3) Conclusion – Written Description In view of the above, we find that either disclosure in Barsoum identified by Patent Owner satisfies the written description requirement. 2. 35 U.S.C. § 103 As noted previously, Petitioner argues that dependent claims 5, 15, and 25 are obvious over the combination of Barsoum and ATSC327. Pet. 67–79. Having determined the Barsoum provides written description support for claims 5, 15, and 25, Barsoum cannot be prior art under 35 U.S.C. §102(a)(1) as asserted by Petitioner. Pet. 2; 35 U.S.C. § 102(a)(1) (requiring that “the claimed invention was patented . . . before the effective filing date of the claimed invention). Furthermore, having determined that the ’700 patent is entitled to an effective filing date of Barsoum ’777, which is June 5, 2008, the asserted March 2019 date of ATSC327 does not qualify it as prior art to the ’700 patent. Thus, the Petition does not establish by a preponderance of the evidence that claims 5, 15, and 25 are obvious over the combination of Barsoum and ATSC327.” slip op. at 22

    • Adverse judgmentAdverse judgmentOther

      “1 Claims 2, 3, 12, 13, 22, and 23, though challenged by Petitioner, were disclaimed by Patent Owner after trial was instituted. Ex. 2024. 2 The Petitioner Sur-reply was authorized in view of our authorization for Patent Owner to file declarant testimony with the Patent Owner Sur-reply.” slip op. at 2

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “We are persuaded that Petitioner’s proposal is consistent with the problems and solutions in the ’700 patent and prior art of record. We also find that Dr. Caire’s statement of a “Ph.D.,” “and possibly some years of work after Ph.D.” is consistent with Petitioner’s statement that the level of skill includes “[s]uperior education” to “compensate for a deficiency in work experience.” The complexity of the evidence of record emphasizes the importance of “at least two years of experience . . . including the use of constellations in transmitting signals between devices” or “[s]uperior education” in the same area. We adopt Petitioner’s definition of the level of skill as discussed above.” slip op. at 9

    Patent outcomesUS 10,693,700 not shown unpatentable
    § 103 obviousness§ 112 disclosurecites KSR · Graham
    Patents in suitUS 10,693,700
  • 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
  • PTAB · Dec 6, 2023 · IPR2023-01020 · APJ Scott Raevsky · IPR · Institution

    Instituted review of claims 1–20 on all grounds; the Lyren and Reif combination showed a reasonable likelihood of obviousness for at least one claim.

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

      “Under 35 U.S.C. § 314(a), an inter partes review may not be instituted unless it is determined that there is a reasonable likelihood that the petitioner would prevail with respect to at least one of the claims challenged in the petition. After considering the parties’ arguments and evidence, and for the reasons set forth below, Petitioner demonstrates a reasonable likelihood of prevailing with respect to at least one of the challenged claims of the ’184 patent. Accordingly, we institute an inter partes review with respect to all challenged claims and grounds asserted in the Petition. 37 C.F.R. § 42.108(a) (2022).” slip op. at 2

    • PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner

      “could have reasonably been raised before the PTAB.” Director’s Memo 3. With our authorization, Petitioner has filed a stipulation which stipulates that If the PTAB institutes the pending IPR in IPR2023-01020 challenging the patentability of claims 1-20 of the ’184 patent, then [Defendants Meta Platforms, Inc., Meta Platforms Technologies, LLC, and Twisted Pixel Games, LLC] will not pursue as to the challenged claims any ground raised or that could have been reasonably raised in the IPR in the above-captioned district court litigation (No. 6:22-cv-00575-ADA).” slip op. at 8

    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “A POSA [person of ordinary skill in the art or “POSITA”] in the relevant timeframe (2015 to 2019) would have had a Bachelor’s degree in computer science/engineering, music technology, or a related field, and at least two years of industry experience, or academic research experience, in virtual/augmented reality, audio engineering, or an equivalent. Additional education can compensate for less experience, and vice-versa. Pet. 6 (citing Ex. 1003 ¶¶ 34–36). Patent Owner uses Petitioner’s proposed level of skill in the art at this stage. Prelim. Resp. 7. We are persuaded, on the present record, that Petitioner’s proposal is consistent with the problems and solutions in the ’184 patent and prior art of record. We adopt Petitioner’s definition of the level of skill for the purposes of this Decision.” slip op. at 10

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

      “The parties do not propose any claim constructions. See Pet. 7; Prelim. Resp. 7. As no terms are in dispute, we determine that no terms require construction at this stage. 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 10

    Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites KSR · Graham
    Patents in suitUS 10,448,184
Page 1 of 3
← Previous123Next →

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.