• 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

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.