- Google LLC / Apple Inc. v. Proxsense LLCAdverse judgmentPTAB · Nov 1, 2024 · IPR2024-01335 · APJ Kevin F Turner · IPR · Adverse judgment
The Board granted Patent Owner’s request for adverse judgment after disclaimer of claims 1–7 and 9–18 of the ’905 patent.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request adverse judgment against itself at any time. 37 C.F.R. § 42.73(b). Here, Patent Owner requests adverse judgment because no claims remain in the trial after Patent Owner’s disclaimer of all the claims at issue in this proceedings. See 37 C.F.R. § 42.73(b)(2). We grant Patent Owner’s request and enter judgment against Patent Owner under 37 C.F.R. § 42.73(b) in this proceeding. ORDER Accordingly, it is: ORDERED that Patent Owner’s request for adverse judgment is granted, and judgment is entered against Patent Owner under 37 C.F.R. § 42.73(b) with respect to claims 1–7 and 9–18 of U.S. Patent No. 9,298,905 B1.” slip op. at 2
NonePatents in suitUS 9,298,905 - Google LLC / Apple Inc. v. Proxsense LLCAdverse judgmentPTAB · Nov 1, 2024 · IPR2024-00234 · APJ Kevin F Turner · IPR · Adverse judgment
The Board granted Patent Owner’s request for adverse judgment after disclaimer of claims 1–7 and 9–18.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request adverse judgment against itself at any time. 37 C.F.R. § 42.73(b). Here, Patent Owner requests adverse judgment because no claims remain in the trial after Patent Owner’s disclaimer of all the claims at issue in this proceedings. See 37 C.F.R. § 42.73(b)(2). We grant Patent Owner’s request and enter judgment against Patent Owner under 37 C.F.R. § 42.73(b) in this proceeding.” slip op. at 2
NonePatents in suitUS 9,298,905 - Apple Inc. v. Proxsense LLCInstitutedPTAB · Oct 8, 2024 · IPR2024-01335 · APJ Kevin F Turner · IPR · Institution
The Board instituted IPR on claims 1–7 and 9–18 under the petition’s § 103 grounds and joined Apple to IPR2024-00234.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“In view of these representations by Petitioner, and Patent Owner’s statement that it does not oppose joinder, and having reviewed the Petition, we determine that, under the current circumstances, it is appropriate to exercise our discretion to institute inter partes review of the challenged claims based upon the same grounds authorized and for the same reasons discussed in the Google DI (Google IPR, Paper 10). Petitioner has shown a reasonable likelihood that it would prevail with respect to each of the claims challenged in the Petition for the same reasons given in the Google DI considering the same issues.” slip op. at 4
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“The Petition does not present any new grounds or issues. Joinder Mot. 1, 3–5. Petitioner agrees to the schedule in the Google IPR and, thus, has shown that the trial schedule is not likely to be affected by joinder. Id. at 5–6. No changes in the schedule are anticipated or necessary, and the limited participation, if at all, of Petitioner will not impact the timeline of the ongoing trial. Petitioner has agreed to an “understudy” role, which will simplify matters in the ongoing Google IPR and will be an efficient use of resources.” slip op. at 7
NonePatents in suitUS 9,298,905 - Apple Inc. v. Proxsense LLCInstitutedPTAB · Oct 8, 2024 · IPR2024-01334 · APJ David C Mckone · IPR · Institution
The Board instituted IPR on claims 1–7, 10, 12–19, and 22–27 under the asserted § 103 grounds and granted Apple’s motion to join the Google IPR.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“C. Institution of Inter Partes Review This Petition is substantially identical to the petition in the Google IPR, challenging the same patent and claims, based on the same grounds of unpatentability, and relying upon the same evidence (including the same prior art combinations supported by the same expert declaration). According to Petitioner, “the 1334 Petition involves the same patent, challenges the same claims, relies on the same expert declaration, and is based on the same grounds and combinations of prior art submitted in the Google Petition.” Joinder Mot. 3; accord id. at 5 (“The Google Petition and 1334 Petition” slip op. at 3
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“The Petition does not present any new grounds or issues. Joinder Mot. 1, 3–5. Petitioner agrees to the schedule in the Google IPR and, thus, has shown that the trial schedule is not likely to be affected by joinder. Id. at 5–6. No changes in the schedule are anticipated or necessary, and the limited participation, if at all, of Petitioner will not impact the timeline of the ongoing trial. Petitioner has agreed to an “understudy” role, which will simplify matters in the ongoing Google IPR and will be an efficient use of resources. Id. at 3, 5–6. Petitioner will assume a primary role only if the Google IPR petitioner ceases to participate in the IPR. Id. at 6. Accordingly, we determine that Petitioner has met its burden of showing that we should exercise our discretion to join Petitioner to the Google IPR (IPR2024-00233).” slip op. at 7
NonePatents in suitUS 8,886,954 - Apple Inc. v. Proxsense LLCInstitutedPTAB · Oct 8, 2024 · IPR2024-01333 · APJ David C Mckone · IPR · Institution
The Board instituted IPR on claims 1–6 and 8–17 under the petition’s § 103 grounds and granted Apple’s motion to join IPR2024-00232.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314 (2016); 37 C.F.R. § 42.4(a) (2019). The standard for instituting an inter partes review is set forth in 35 U.S.C. § 314(a), which provides that an inter partes review may not be instituted “unless . . . 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 explained below, we institute an inter partes review of the ’730 patent. We also join Petitioner as a party to IPR2024-00232.” slip op. at 2
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“The Petition does not present any new grounds or issues. Joinder Mot. 1, 3–5. Petitioner agrees to the schedule in the Google IPR and, thus, has shown that the trial schedule is not likely to be affected by joinder. Id. at 5–6. No changes in the schedule are anticipated or necessary, and the limited participation, if at all, of Petitioner will not impact the timeline of the ongoing trial.” slip op. at 7
NonePatents in suitUS 8,352,730 - Iriusrisk, Inc. v. Threatmodeler Software Inc.No claims unpatentablePTAB · Oct 2, 2024 · IPR2023-00656 · APJ Stephen E Belisle · IPR · Final written decision
Claims 1–20 were not shown unpatentable because Keenan did not disclose the claimed stored threats, and the obviousness combinations did not establish the mapping limitations or a reason to combine.
RulingsFinal written decision- Expert testimonyPatent owner expert creditedDecided for patent owner
“construction of “threat,” which we find in the context of the ’366 patent does not encompass “risk.” See supra § III.D.3.a.1 (discussing “‘Threats’ versus ‘Risks’”). We agree with Patent Owner that Petitioner’s premise that “risk” includes “threats” or knowing risk allows for determination of threats is false, and belied by the parties’ experts who do not disagree on this distinction, namely that “risk” is not a “threat,” but rather represents the likelihood of a threat occurring compounded by the impact of such a threat on a given system (discussed above). See Ex. 2002, 24:3–25:5, 31:5–33:2 (Petitioner’s expert, Mr. Hurlbut, agreeing that “Risk = Likelihood x Impact”); Ex. 2009 ¶ 80; PO Sur-reply 9–10. Thus, we find unavailing Petitioner’s attempt to walk backwards from Keenan’s explicit disclosure of “risk” modeling into an anticipatory (explicit) disclosure of stored “threats” that may give rise to such risk. Viewing Keenan in the light agreed upon by the parties’ experts, where “risk” is a product of the “likelihood” of a threat occurring and the “impact” of such a threat on a given system, persuades us that although Keenan discloses “risk,” “types of risk,” and “risk ranking” (see, e.g., Ex. 1004, 16:21–63), Keenan uses such “risk” as a given value without explicitly disclosing any underlying stored threats or use thereof. See Ex. 2009 ¶ 112 (“Keenan does not disclose a system for measuring risk. The risk for objects is determined before the objects are imported into the [Integrated Object Environment]. Keenan does not make that measurement.”). Indeed, in order to “store” “threats” in “one or more databases” as recited in claim 1, such “threats” must be identified (i.e., known) at some level of specificity to the system. Petitioner does not direct us to any persuasive evidence that Keenan explicitly discloses using “threats” or “storing” an identified “threat,” let alone storing such “threat” in a database along with its association with a particular threat model component, and even more so with a threat model component that itself is correlated with a third-party diagram component as recited in claim 1.” slip op. at 32
- Skill levelSkill level petitioner adoptedDecided for petitioner
“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 also may be reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). Neither party argues that the outcome of this case would differ based on our adoption of any particular definition of the level of ordinary skill in the art. Considering the subject matter of the ’366 patent, the background technical field, the prior art, and Petitioner’s unopposed definition of the skilled artisan, we apply the level of skill set forth above, which is consistent with the testimony of Mr. Hurlbut (Ex. 1003 ¶ 33).” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“43:21–61. Contrary to Petitioner’s arguments (Pet. Reply 3–5), this “subset” feature shows that the “threats” stored in databases in claim 1 represent “potential events” that may or may not occur depending on the composition of a given system undergoing threat modeling—a system may implicate all stored threats, some of them, or even just one of them, leaving the remaining stored threats for use in preparing threat models for other systems. See PO Sur-reply 2–3 (discussing Figure 2 and arguing that “not every threat is necessarily included in the threat model”). We find the claim language itself supports interpreting “threats” as “potential events that, if they occur, can cause adverse effects to a target system.”” slip op. at 19
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“Claim 1 recites, in part, “the one or more mapping files correlating the threat model components with [“third party diagram components”].” Ex. 1001, 43:30–35. Generally, from the standpoint of what claim 1 requires, the parties’ views of “mapping file” are in alignment. Claim 1 plainly recites that a “mapping file” (where a “file” in the context of computer systems is data itself) correlates data A with data B, and when construed in the context of the subject claim language, correlates threat model components (i.e., data A) with third party diagram components (i.e., data B). We find that this interpretation of “mapping files” is sufficient to resolve the controversy between the parties. See Nidec Motor, 868 F.3d at 1017.” slip op. at 39
Patent outcomesUS 10,713,366 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,713,366 - Samsung Electronics Co., Ltd / Samsung Electronics America, Inc. et al. v. Staton Techiya, LLCInstitutedPTAB · Aug 16, 2024 · IPR2024-00559 · APJ Nathan A Engels · IPR · Institution
The Board instituted IPR of claims 1–12 on all asserted grounds, finding a reasonable likelihood that at least one challenged claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“On the current record, Petitioner’s arguments and evidence sufficiently show that the teachings of Fiedler and Broussard satisfy each limitation of claim 1 and that a person of ordinary skill would have had reasons to combine the references’ teachings. At this stage, Petitioner’s arguments and evidence are unrebutted, and we preliminarily determine Petitioner has shown a reasonable likelihood that it will prevail in its challenge to claim 1.” slip op. at 8
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art at the time of the alleged invention would have had a “Bachelor’s of Science degree (or equivalent) in electrical engineering, computer science, or a similar field and two years of experience in the design of digital audio systems and associated” slip op. at 5
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Petitioner states that no constructions are necessary and that the claim should be given their plain and ordinary meaning. Pet. 11. Based on the current record, we determine that it is not necessary to provide an express interpretation of any claim terms at this stage of the proceeding. See Realtime Data, LLC v. Iancu, 912 F.3d 1368 (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 6
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundInstituted
“Petitioner contends Fiedler suggests use of a processor, and Petitioner additionally cites Broussard as providing details of how to implement a recording device similar to Fiedler’s with a general-purpose computer, including a data processor, among other things. Pet. 22–26 (citing, e.g., Ex. 1002 ¶¶ 143–152; Ex. 1008 ¶¶ 2, 12, 15, 21, 24, Fig. 2). Petitioner contends a person of ordinary skill would have looked to Broussard’s teachings of signal processing to implement Fiedler’s teachings regarding event-activated recording and that combining the references’ teachings would have amounted to use of known techniques to improve a similar device. Pet. 28–32. On the current record, Petitioner’s arguments and evidence sufficiently show that the teachings of Fiedler and Broussard satisfy each limitation of claim 1 and that a person of ordinary skill would have had reasons to combine the references’ teachings. At this stage, Petitioner’s arguments and evidence are unrebutted, and we preliminarily determine Petitioner has shown a reasonable likelihood that it will prevail in its challenge to claim 1.” slip op. at 8
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,610,587 - Keysight Technologies, Inc. / Palo Alto Networks, Inc. v. Centripetal Networks, LLCSome claims unpatentablePTAB · Aug 5, 2024 · IPR2023-01353 · APJ Kevin F Turner · IPR · Final written decision
Claims 1–4, 6–11, and 13–20 are unpatentable as obvious over Sourcefire and Emerging Threats; claims 5 and 12 were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner, supported by Dr. Staniford’s testimony, proposes that 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 an equivalent, and four years of industry experience,” and “would have had a working knowledge of packet-switched networking, firewalls, security policies, communication protocols and layers, and the use of customized rules to address cyber-attacks.” Pet. 16 (citing Ex. 1003 ¶¶ 23, 25). Patent Owner does not challenge the qualifications proposed by Petitioner for a person of ordinary skill in the art. See generally PO Resp. We find Petitioner’s proposal consistent with the level of ordinary skill in the art reflected by the prior art of record, see Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978), and, therefore, we adopt Petitioner’s unopposed position as to the level of ordinary skill in the art for purposes of this Decision” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningNo construction neededOther
“We largely agree with Patent Owner that there is no explicit claim- construction dispute. We address Patent Owner’s issues of what ordinarily skilled artisans would have considered in creating and implementing packetfiltering rules in the discussion below. The preservation of the flow of normal legitimate network traffic without disruption is one aspect that those with a working knowledge of packet-switched networking, firewalls, security policies, communication protocols and layers, and the use of customized rules to address cyber-attacks would have considered. Nonetheless, overall, we determine that the plain and ordinary meaning of “configured to prevent an exfiltration operation,” does not require preventing all exfiltrations from occurring, nor allowing all non-exfiltration traffic, and that we need not consider the preservation of the flow of normal legitimate network traffic without disruption in the context of that claim construction. We determine that no claim terms need to be construed expressly for purposes of this Decision.” slip op. at 10
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“We agree with Petitioner. The identified aspects of Emerging Threats website would have allowed interested parties to locate the rule sets, download the rule sets and make determinations regarding what rule to use in a packet-handling system, such as Sourcefire. Emerging Threats need not be indexed or broadly searchable under Petitioner’s theory of the ground of unpatentability, namely that Emerging Threats was known, one of ordinary skill in the art would have gone to Emerging Threats, and downloaded the emerging-all.rules file, guided by the documentation wiki. As such, we do not agree with Patent Owner’s argument that “the record evidence of this” slip op. at 16
- PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner
“With respect to Petitioner’s assertions of collateral estoppel, notably in the Petition at pages 47, 49, 51, 52, and 54, with respect to limitations [1a] through [1d], we agree with Petitioner that Patent Owner is estopped from asserting that Sourcefire is not prior art to the challenged claims, and also estopped from asserting that those limitations are not taught or suggested by Sourcefire, to the extent that the limitations “do not materially alter the question” of patentability relative to the elements of the claims of the ’552 patent. See Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778 F.3d 1311, 1319 (Fed. Cir. 2015). Independent Claim 1 a. Petitioner’s Assertions As discussed above, we concur with Petitioner that collateral estoppel exists with respect to limitations [1a] through [1d]. Thus, we begin with a discussion of Petitioner’s assertions regarding claim limitation [1e].” slip op. at 21
Patent outcomesUS 10,567,343 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,567,343 - Keysight Technologies, Inc. / Palo Alto Networks, Inc. v. Centripetal Networks, LLCSome claims unpatentablePTAB · Aug 5, 2024 · IPR2023-00446 · APJ Kevin F Turner · IPR · Final written decision
Claims 1–4, 6–11, and 13–20 are unpatentable as obvious over Sourcefire and Emerging Threats; claims 5 and 12 were not shown unpatentable.
RulingsFinal written decision- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“We agree with Petitioner. The identified aspects of Emerging Threats website would have allowed interested parties to locate the rule sets, download the rule sets and make determinations regarding what rule to use in a packet-handling system, such as Sourcefire. Emerging Threats need not be indexed or broadly searchable under Petitioner’s theory of the ground of unpatentability, namely that Emerging Threats was known, one of ordinary skill in the art would have gone to Emerging Threats, and downloaded the emerging-all.rules file, guided by the documentation wiki. As such, we do not agree with Patent Owner’s argument that “the record evidence of this” slip op. at 16
- PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner
“With respect to Petitioner’s assertions of collateral estoppel, notably in the Petition at pages 47, 49, 51, 52, and 54, with respect to limitations [1a] through [1d], we agree with Petitioner that Patent Owner is estopped from asserting that Sourcefire is not prior art to the challenged claims, and also estopped from asserting that those limitations are not taught or suggested by Sourcefire, to the extent that the limitations “do not materially alter the question” of patentability relative to the elements of the claims of the ’552 patent. See Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778 F.3d 1311, 1319 (Fed. Cir. 2015). Independent Claim 1 a. Petitioner’s Assertions As discussed above, we concur with Petitioner that collateral estoppel exists with respect to limitations [1a] through [1d]. Thus, we begin with a discussion of Petitioner’s assertions regarding claim limitation [1e].” slip op. at 21
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“how and why persons of ordinary skill in the art would have modified the existing rules to prevent exfiltrations. PO Sur-reply 3. Patent Owner also argues that Petitioner’s assertions to make them “drop” rules, per Sourcefire, relies on what an administrator could have done, not what they would have been motivated to do. Id. at 4–5 (citing Pet. 57–58). We disagree with Patent Owner’s arguments. We continue to be persuaded that one of ordinary skill in the art, combining Sourcefire and Emerging Threats, would have understood that downloaded rules should be reviewed, and it would have been obvious to enable rules that such persons deemed appropriate. We find Dr. Staniford’s testimony to be persuasive on this point. See Ex. 2011, 67:10–68:24, 69:8–72; Ex. 1020, 109. We acknowledge that downloading all of a particualr ruleset from Emerging Threats and enabling all the rules, might have resulted in a drop in performance of the network appliance, but, at the same time, we are significant drop in performance, especially if a potential threat might be sufficient to warrant a minor performance hit. Patent Owner’s counsel acknowledged at oral hearing that instituting all rules of a set in “alert” mode would not result in a decrease in performance, even though some computational outlay must be engaged to engage those alert rules. See Hr’g Tr. 24:24–25:4. We are persuaded that judiciously implementing certain rules would not necessary result in a network device that is unusable. Additionally, there is testimony from Dr. Staniford that “you start out with your rules in alert because there might be false positives. I mean, for the best rule in the world, Snort wasn’t known for false positives in the rules, when you apply them to a large network.” Ex. 2011, 68:2–7. As such, we continue to determine that it would have been obvious, in combining Sourcefire with Emerging Threats, for one of ordinary skill in the art to have downloaded rules and implemented specific rules.” slip op. at 24
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightDecided for petitioner
“Reviewing all of the evidence of record, we are persuaded that the Petition’s obviousness rationale based on Sourcefire and Emerging Threats is not guided by impermissible hindsight bias. We find persuasive Dr. Staniford’s testimony that one of ordinary skill in the art would have understood that “this rule [SID:2003021] was not directed to looking for instances of exploits or attacks (which would be invisible within the encryption) but rather was looking for exfiltration of some kind of encrypted data.” Ex. 1003 ¶ 228. As discussed by Petitioner, such recognition was also made by Mr. Marinho and Dr. Goodrich, such that the rule would have been understood to possibly prevent exfiltrations. We continue to be persuaded that Petitioner provides that a correspondence exists between the REQUIRE-TLS-1.1-1.2 operator in the ’343 Patent and SID:2003021 in Emerging Threats, in that both detect an SSL/TLS version in application packet header field values to detect exfiltration attempts using out-of-date encryption protocols. Pet. 43 (citing Ex. 1003 ¶¶ 229–230). We are ’343 Patent discloses the interruption of a similar type of exfiltration, without resorting to impermissible hindsight bias, that Patent Owner asserts. Patent Owner has provided no evidence that Petitioner used the specification of the ’343 Patent to find an applicable rule in Emerging Threats, as opposed to the testified-version provided by Dr. Staniford that he recalls “working on a similar feature where we looked for large encrypted transmissions outbound from the network on non-HTTP ports as a possible symptom of exfiltration of large amounts of data.” Ex. 1003 ¶ 228. Thus, we are not persuaded by Patent Owner’s arguments.” slip op. at 30
Patent outcomesUS 10,567,343 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,567,343 - Google LLC v. Proxense, LLCInstitutedPTAB · Jul 24, 2024 · IPR2024-00232 · APJ David C Mckone · IPR · Institution
Instituted IPR of claims 1–6 and 8–17 based on reasonable likelihood that Google would prevail on the asserted obviousness grounds over Ludtke, alone or with Kon.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314 (2016); 37 C.F.R. § 42.4(a) (2020). The standard for instituting an inter partes review is set forth in 35 U.S.C. § 314(a), which provides that an inter partes review may not be instituted “unless . . . 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 explained below, we institute an inter partes review of the ’730 patent.” slip op. at 2
- Prior constructionPrior construction adoptedDecided for patent owner
“third-party trusted authority” to exclude any active participant in a transaction. This would exclude the trusted key authority of the preferred embodiments of the ’730 patent, which actively participates in a transaction, for example by receiving a request for authentication with a code, determining whether the code is valid, authenticating the code, and transmitting an access code to the requester, which allows a user access to an application. Ex. 1001, 7:10–22, Fig. 7. Although the trusted key authority in this example is not a principal party to the transaction (here, those parties are the user and the application), it is an active participant in facilitating the transaction. In another preferred embodiment of the ’730 patent, trusted key authority 320 plays an active role in transactions, e.g., verifying to a grocery store that a biometric key presented by a customer is legitimate, thereby allowing the transaction to proceed. Id. at 5:42–56, Figs. 3–4. However, despite the trusted key authority’s active participation, the parties to such a transaction are the customer and the grocery store, not trusted key authority 320. The “witness” role mentioned in the Specification (Ex. 1001, 6:35–38) refers to an agent’s relationship to the principal parties to the transaction, not to the level of activity the agent engages in. See id. at 6:32–64, Fig. 5 (describing activities of an agent). slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“2. Remaining claim terms Based on the preliminary record, we do not find it necessary to provide express claim constructions for any other terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we 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 12
- Skill levelSkill level petitioner adoptedDecided for petitioner
“1. Level of skill in the art Petitioner contends that a person of ordinary skill in the art “would have had at least a bachelor’s degree in Computer or Electrical Engineering or an equivalent engineering discipline, and at least three years of experience in the field of encryption and security, or the equivalent,” and that “[a]dditional education could substitute for professional experience, and significant work experience could substitute for formal education.” Pet. 5 (citing Ex. 1003 ¶¶ 31–32, 54–56). Patent Owner does not challenge Petitioner’s proposed level of skill or propose an alternative. Petitioner’s proposal is consistent with the technology described in the Specification and the cited prior art. For purposes of this Decision, we adopt Petitioner’s proposed level of skill.” slip op. at 13
Claim construction§ 103 obviousnessDiscretionary denialcites GrahamPatents in suitUS 8,352,730
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.