- Metacluster LT, Uab v. Bright Data Ltd.InstitutedPTAB · 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 · GrahamPatents in suitUS 11,272,034 - Autodesk, Inc. v. Uniloc USA, Inc. And Uniloc Luxembourg, S.A.All claims unpatentablePTAB · Sep 11, 2017 · CBM2016-00043 · APJ Christopher M Kaiser · CBM · Final written decision
Claims 1, 2, 4–7, and 12–19 are unpatentable under § 101; claims 3, 8–11, and 20 are subject to adverse judgment after disclaimer.
RulingsFinal written decision- Adverse judgmentAdverse judgmentGranted
“B. Statutory Disclaimer During the pendency of this proceeding, Patent Owner filed a disclaimer pursuant to 35 U.S.C. § 253(a) and 37 C.F.R. § 1.321(a). Ex. 2014. According to this disclaimer, Patent Owner disclaims claims 3, 8–11, and 20 of the ’820 patent. Id.; see also Resp. 1 (“Contemporaneously with the filing of this Response, Patent Owner is disclaiming claims 3, 8, 9, 10, 11, and 20 of the ’820 Patent.”). Our rules provide for entry of adverse judgment against a Patent Owner who disclaims “a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). Although Patent Owner does not disclaim all the challenged claims, and although Patent Owner therefore has some claims remaining in this trial, we construe the disclaimer of claims 3, 8–11, and 20 as a request for the entry of adverse judgment solely with respect to those claims. We grant the request and enter adverse judgment with respect to claims 3, 8–11, and 20.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed patent owner constructionDecided for patent owner
“1. Add-On Computer Software Code Both parties propose construing “add-on computer software code,” a term that appears in every challenged claim. Ex. 1001, 78:43–82:36. Petitioner argues that this term should be interpreted as a “set of computer code that cannot be run independently from a parent program.” Pet. 22. Patent Owner argues that the term should be interpreted as “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.” Resp. 42–43. We agree with Patent Owner. Patent Owner’s construction is taken directly from the written description of the ’820 patent, which provides a reasonably clear, deliberate, and precise definition of the term. See Paulsen, 30 F.3d at 1480; Ex. 1001, 61:42–51 (“The plug-in (add-on) computer software code is . . . .”). To the extent that Petitioner’s proposed construction seeks to limit add-on software code further by requiring that the software code be incapable of running independently from a parent program, as opposed merely to being designed to run within the parent program as an internal component, this further limitation is inconsistent with the lexicography undertaken by the patentee of the ’820 patent. Accordingly, we construe “add-on computer software code” as a “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.”” slip op. at 6
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“As discussed above, the ’820 patent describes solving problems with the generation of cost estimates of construction projects, including that the process takes significant time and effort, that the estimates produced are difficult to revise, and that the estimates can be inaccurate, leading to cost overruns and difficulties obtaining construction loans. Ex. 1001, 1:15–62. The claims recite a computer readable medium or system for automating the process of generating a price schedule, which is used to develop the overall project cost estimate. Id. at 78:43–82:36. In so doing, the claims do not recite any “specific asserted improvement in computer capabilities,” such as the “self-referential table for a computer database” in Enfish, 822 F.3d at 1336. Instead, the claims of the ’820 patent “invoke[]” known aspects of computer technology, including “[a] non-transitory computer readable medium,” “a computer that includes a processor and a memory,” “an add-on computer software code,” “a software design tool,” and “a database,” “merely as a tool” for solving the problem of improving the known process of generating construction project cost estimates. Id.; Ex. 1001, 78:43–60. Accordingly, the claims of the ’820 patent are not like those considered in Enfish, where the claims were determined at the first step of the Alice framework not to be directed to abstract ideas because they were directed to “[a] specific asserted improvement in computer capabilities.” 822 F.3d at 1336. Instead, Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent are focused “on a process that qualifies as an ‘abstract idea.’” Id. The ’820 patent makes clear that the heart of the claimed subject matter is generating prices for construction projects, a process that can be accomplished without automation technology. Ex. 1001, 1:15–62. The claims themselves recite “[a] non-transitory computer readable medium [that] causes [a] computer to generate a price schedule” and “[a] system for creating a pricing schedule.” Id. at 78:43–51, 82:4. As discussed above, the computer technology recited in the claims is used merely as a tool to automate the process of determining the price of a construction project. Determining a price is an abstract idea. See Versata Dev. Grp., 793 F.3d at 1333–34 (Fed. Cir. 2015). Thus, on the current record, Petitioner has made a sufficient showing that the claims of the ’820 patent are directed to an abstract idea under the first step of the Alice analysis.” slip op. at 20
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“application of an abstract idea. Mayo, 566 U.S. at 78. Petitioner argues that the challenged claims have no such elements, because “the challenged claims add nothing more than well-understood, routine, conventional activity to the abstract idea of calculating a price.” Pet. 32–48. Patent Owner argues that the presence of the add-on computer software code limitations in the challenged claims transforms those claims into patent-eligible applications. Resp. 49–50. We are persuaded that Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent do not add an inventive concept sufficient to ensure that the patent in practice amounts to significantly more than a patent on the abstract idea itself. Alice, 134 S. Ct. at 2355.” slip op. at 23
Patent outcomesUS 8,515,820 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · EnfishPatents in suitUS 8,515,820 - Bank Of America, N.A. / PNC Financial Services Group, Inc. et al. v. Intellectual Ventures I LLCAll claims unpatentablePTAB · Apr 24, 2015 · CBM2014-00030 · APJ Thomas L Giannetti · CBM · Final written decision
Claims 1–23 are unpatentable under § 101 because they claim an abstract idea implemented with routine, conventional activity.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“are directed to the abstract idea of tailoring an information provider’s web page based on data about a particular user. Institution Dec. 12. Patent Owner responds that the claims do not fall within any of the “categories of abstract ideas enumerated by the Supreme Court.” PO Resp. 15. Citing Alice, Patent Owner asserts that the claims are not directed to “an idea itself, a mathematical formula or algorithm, a fundamental economic practice long prevalent in our system of commerce, or a method of organizing human activity.” Id. (internal quotation marks omitted). Therefore, Patent Owner asserts, the first step in the Alice/Mayo test is not met. Id. at 15–21. Petitioners respond that in Alice, the Supreme Court expressly declined to limit the categories of unpatentable abstract ideas as suggested by Patent Owner. Reply 3. We are persuaded by the Supreme Court’s opinion in Alice that Petitioners are correct, and that these enumerated categories were not intended as exclusive. Specifically, the Court wrote: “In any event, we need not labor to delimit the precise contours of the ‘abstract ideas’ category in this case.” 134 S. Ct. at 2357; accord Content Extraction, 776 F.3d at 1347. We are influenced also by the evidence from Patent Owner’s expert, who testified as follows: I’m trying to make clear that the patent is described at what may appear to be a fairly high abstract level, because it was generally known by persons of skill in the art that there are multiple ways to go about reducing the invention to practice depending upon the technologies that they have at hand. And it wasn’t the patent’s job to be that specific at the time. I shouldn’t say it wasn’t the patent’s job. The inventor did not choose to describe at that level of detail. Ex. 1037, 47:12–23 (emphasis added). We therefore conclude that the first step in the Alice/Mayo test is met for claims 1–23.” slip op. at 9
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“We are convinced by Petitioners’ argument that the ʼ382 patent claims do not contain an “inventive concept” sufficient to transform the claimed abstract idea into a patentable invention. Stated another way, we determine that the claims do not “significantly more than simply describe that abstract method.” Ultramercial, 772 F.3d at 715. Instead, “the claims simply instruct the practitioner to implement the abstract idea with routine, conventional activity.” Id.” slip op. at 12
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“Patent Owner’s expert does not rebut convincingly Dr. Myers’s claim- by-claim analysis. Instead, Patent Owner’s expert addresses the claims in two groups only. Ex. 2003, ¶¶ 26–28. We find this approach unconvincing, and therefore, credit Dr. Myers’s testimony as to specific claims over the testimony of Patent Owner’s expert. We are therefore persuaded, by a preponderance of the evidence, that, like the claims considered in Ultramercial, claims 1–23 of the ʼ382 patent simply instruct the practitioner to implement the abstract idea with routine, conventional activity. Ultramercial, 772 F.3d at 715. For the reasons stated above, none of the elements recited in the claims, including the “interactive interface” and the “plurality of data streams,” transforms the nature of the claims into patent-eligible subject matter. We credit the cited testimony of Patent Owner’s expert that the ʼ382 patent lacks implementation details because it is written at a “fairly high abstract level.” See supra. As a result of this choice by the patentee, the risk of preemption is great.” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“Patent Owner contends that neither Petitioners nor the Board provides any evidence that “interactive” and “Internet” have the same meaning, “either in the ʼ382 patent or as understood by one of skill in the art.” PO Resp. 7. Patent Owner further contends that Board should adopt a construction requiring the interface to be a “selectively tailored medium.” Id. at 8–9. Petitioners respond that there are not any claim terms “that could reasonably be construed in a manner that would impact the 35 U.S.C. § 101 analysis.” Reply 11. Petitioners further contend that the Board’s construction was nevertheless correct because the patent specification and claims make it clear that it is the information that is “selectively tailored,” not the information medium. Id. at 11–12. We are not convinced of any error in our initial construction of “interactive interface” as an Internet interface. Institution Dec. 6. Petitioners’ reliance on the Myers Declaration and the ʼ382 patent’s interchangeable use of interactive and Internet to describe the interface are persuasive. Pet. 15, 17 (citing Myers Dec., Ex. 1004 ¶ 52), 18 (citing Ex. 1001, Title, Abstract). We, therefore, determine that the correct construction of “interactive interface” is “an Internet interface that provides a medium for information users to communicate with information providers.”” slip op. at 6
Patent outcomesUS 7,603,382 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · BilskiPatents in suitUS 7,603,382
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.