- PTAB · Dec 3, 2025 · IPR2025-01016 · APJ Arthur M Peslak · IPR · Institution
The Board instituted IPR on all challenged claims 1–13 and all petition grounds, finding a reasonable likelihood that Jurik anticipates at least one claim.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“determine whether to institute an inter partes review under 35 U.S.C. § 314(a). See 37 C.F.R § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Under 35 U.S.C. § 314(a), an inter partes review may not be instituted unless the information presented in the Petition shows “there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” Considering the Petition as well as all supporting evidence, we conclude that the information presented in the Petition establishes a reasonable likelihood that Petitioner would prevail in its challenge of at least one claim of the ’373 patent as unpatentable. Pursuant to 35 U.S.C. § 314, we hereby institute an inter partes review of all challenged claims of the ’373 patent on the grounds stated in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedOther
“[a] person of ordinary skill in the art (“POSITA”) at the time of the assumed effective filing date (March 30, 2023), would have had at least a B.S. degree in mechanical or electrical engineering and would have had at least two years of practical experience designing lighting systems. Alternatively, a POSITA would have at least two years of undergraduate training in a physical science (e.g., engineering or physics) and at least four years of practical experience designing lighting systems. Pet. 10 (citing Ex. 1004 ¶¶ 31–32). Patent Owner did not file a Preliminary Response. For the purposes of this Decision, we apply Petitioner’s currently uncontested definition except for the term “at least” because it may cause ambiguity resulting in potentially encompassing those with more than ordinary skill in the art. With that qualification, Petitioner’s proposal appears consistent with the problems addressed in the ’373 patent and the prior art.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Patent Owner did not file a Preliminary Response. We determine, at this stage of the proceeding, that we need not construe any claim terms to resolve the controversy before us. 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))). The parties are free to address the construction of any claim term in subsequent authorized briefing during trial. If either party chooses to present claim construction arguments, the arguments should be in a separately delineated portion of the brief labelled accordingly.” slip op. at 11
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“To establish anticipation under 35 U.S.C. § 102, each and every element in a claim, arranged as recited in the claim, must be found in a single prior art reference. Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008); Karsten Mfg. Corp. v. Cleveland Golf Co., 242 F.3d 1376, 1383 (Fed. Cir. 2001). Each element of the challenged claim must be found, either expressly or inherently, in the single prior art reference. Verdegaal Bros., Inc. v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). However, this is not an ipsissimis verbis test, i.e., identity of terminology is not required. See In re Bond, 910 F.2d 831, 832 (Fed. Cir. 1990). When evaluating a prior art reference in the context of anticipation, the reference must be “considered together with the knowledge of one of ordinary skill in the pertinent art.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994) (citing In re Samour, 571 F.2d 559, 562 (CCPA 1978)).” slip op. at 8
Claim construction§ 102 anticipationcites Phillips · KSR · GrahamPatents in suitUS 11,988,373 - PTAB · Nov 18, 2025 · IPR2025-00782 · APJ Ken B Barrett · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that any challenged claim was unpatentable over the asserted grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“An inter partes review may not be instituted “unless . . . the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has not demonstrated a reasonable likelihood of prevailing on at least one of the challenged claims of the ’469 patent. Accordingly, we do not institute an inter partes review of the challenged claims.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that: [A] POSITA would have had at least a bachelor’s degree in computer science, computer engineering, business information systems, software engineering, or systems engineering and at least two years of experience in computer networking or telecommunications. Ex.1002 ¶21; see also Ex.1001 (1:14-31). Additional education could substitute for professional experience. Ex.1002 ¶21. Significant work experience could substitute for formal education. Ex.1002 ¶21. Pet. 7–8. Patent Owner, at this stage, does not disagree or propose a different definition of the person of ordinary skill in the art. Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states that it “do[es] not believe explicit construction is required to resolve this Petition.” Pet. 7. Patent Owner proposes constructions for “Internet,” “access the Internet,” “subscriber access website.” Prelim. Resp. 12–15. On this record and for purposes of this decision, we determine that no claim terms require express construction. D. Alleged Anticipation of Claims 1, 2, 10, 11, and 24–28 by Bruner and” slip op. at 10
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentable
“We find Patent Owner’s argument to be persuasive. Petitioner does not explain adequately how Bruner discloses the positional requirement of a subscriber access unit being coupled between the satellite dish and the router. Accordingly, Petitioner has not shown sufficiently for purposes of institution that Bruner anticipates independent claim 24. Although, for the obviousness challenge, Petitioner contends that Clark discloses a wireless router (for limitation 24c), Petitioner relies solely on Bruner for the “between” limitation. See Pet. 17 (“Bruner and/or Bruner in view of Clark both disclose each limitation of claim 24c, including a router (e.g., Bruner’s ‘ADS’ and Clark’s ‘wireless router’)”); id. at 18–19 (the discussion of the “between” limitation 24d asserting that “Bruner discloses claim 24d,” with no mention of Clark). Furthermore, Petitioner merely asserts that both Bruner and Clark disclose a router. See id. at 17–18. Petitioner, however, does not indicate clearly which is used in the proposed combination, does not describe the configuration of a proposed combination or a proposed modification of Bruner’s system, and fails to set forth an adequate and persuasive reason with rational underpinning as to why a person of ordinary skill in the art would have modified Bruner’s system to arrive at the positional requirement of the subscription access unit being coupled between the satellite dish and a router. See id. at 13–14 (motivation section for this ground); id. at 18–19 (addressing the “between” limitation 24d). Accordingly, Petitioner has not shown a reasonable likelihood of prevailing on its challenge to independent claim 24 as obvious over Bruner in view of Clark.” slip op. at 14
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,324,469 - Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentablePTAB · Oct 1, 2025 · IPR2024-00943 · APJ Scott B Howard · IPR · Final written decision
Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and the stated Rao combinations render the remaining claims obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim 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 13
- Expert testimonyPetitioner expert creditedDecided for petitioner
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“preponderance of the evidence that claim 3 was anticipated by Rao.” slip op. at 25
Patent outcomesUS 8,589,541 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentablePTAB · Oct 1, 2025 · IPR2024-00942 · APJ Scott B Howard · IPR · Final written decision
Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and Rao-based combinations render the others obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim 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 13
- Expert testimonyOther
“157, and 171 are anticipated by Rao. Pet. 1, 19–39, 42. Petitioner’s arguments are supported by citations to the prior art and the testimony of Dr. Wolfe. See id. We have reviewed Petitioner’s arguments and evidence, agree with them, and, therefore, adopt Petitioner’s arguments and evidence as our own.” slip op. at 26
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“anticipated by Rao. Pet. 1, 30–31, 33–42. We have reviewed Petitioner’s arguments for each of those dependent claims. See Pet. 30–31, 33–42. For each of those dependent claims, the Petition appears to only argue a theory of obvious. That is, the Petition never states that the additional limitation is disclosed by Rao. See id. For example, claim 26 depends from claim 1 and further recites “wherein the policy is based on a background service class.” Ex. 1001, 112:49–52. We reproduce Petitioner’s arguments directed to claim 26 below: Rao’s policies 520 may “define prioritization” for network packets “based on whether an application is running in the foreground or the background.” [Ex. 1002] ¶ 182; id. ¶¶ 38–43, 180, 182, 188–89, 193, Figs. 5A, 5B. Each packet “may be placed and arranged in a priority order respective to all other . . . packets to provide a packet by packet prioritization across all applications 338a-338n and . . . network packets.” Id. ¶ 191. It would have been obvious to determine and apply a policy assigning a specific priority to packets associated with background applications, supra [1e]-[1f], and Rao thus discloses or renders obvious assigning a priority to network communications based on whether they are characterized as background services (class of services associated with application(s) running in the background of client 105), EX-1015 ¶¶195-96; supra [1e], [1f]. Pet. 33–34. Although the Petition sets forth why the claim limitation would have been obvious, there is no discussion as to how the additional limitation of claim 26—policy based on background class—is disclosed in Rao. See id. Similar arguments are presented for the other claims. See Pet. 30–31, 35–42. Because the Petition does not sufficiently show how the additional limitations recited in claims 20, 26, 58, 64, 165, and 169 were disclosed by Rao, Petitioner has not shown by a preponderance of the evidence that claims 20, 26, 58, 64, 165, and 169 were anticipated by Rao.” slip op. at 28
Patent outcomesUS 8,589,541 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - Lululemon USA Inc. v. Nike, Inc.Some claims unpatentablePTAB · May 21, 2025 · IPR2024-00159 · APJ Carl M Defranco · IPR · Final written decision
Claims 8, 9, 14, 15, and 19 are unpatentable over Minami; claims 1–3, 7, 16–18, and 20 were not shown unpatentable over Good or Munsing.
RulingsFinal written decision- Skill levelSkill level board ownOther
“lululemon contends, and Nike does not dispute, that a person skilled in the art in the relevant time frame would have had “at least a bachelor’s degree in mechanical engineering, textile engineering, or similar technical degree and at least 3 years of experience working with knitted textiles for use in fabric-based articles, including apparel such as footwear” and such person’s “additional experience compensates for any differences in that person’s education as stated above.” Pet. 13–14 (citing Ex.1003 ¶¶ 33–35); see also PO Resp. 14 (“For purposes of this proceeding, Nike applies lululemon’s proposed level of skill in the art.”). We find that lululemon’s proposed definition is consistent with the problems and solutions described in the ’046 patent and the prior art of record. Thus, we adopt the parties’ agreed-upon definition of the level of skill in the art.” slip op. at 6
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“We are not persuaded by lululemon’s attempt to equate the term “channel” in that passage with an open-periphery configuration. Nowhere does that passage indicate that the “channel” has an open-periphery. Instead, lululemon merely presumes, without support, that channels are open-periphery structures. More accurately, the terms “tunnel” and “channel” in the passage cited by lululemon are used synonymously. That is made clear by the overall context of the ’046 patent at issue, which is directed to how tubular rib structures 126 are formed by “first” and “second” curved portions 416 and 418 that are “knitted together” to define “hollow tube 112.” See Ex. 1001, 10:16–11:14, Figs. 4, 5 (emphasis added). In particular, the sentence cited by lululemon describes hollow tube 112 as being “disposed between” first and second curved portions 416 and 418, which Figures 4 and 5 of the ’046 patent clearly depict in a closed-periphery configuration. See id. at 10:66–11:3, Figs. 4, 5. Moreover, the very next sentence expressly describes that hollow tube 112 has “a generally cylindrical or elliptical shape” wherein “[t]he diameter of one hollow tube and the diameter of other hollow tubes may differ in some embodiments.” Id. at 11:3–14 (emphases added). We are not aware of any open-periphery channels being described as having a cylindrical or elliptical shape, nor are we aware of such a channel being described as having a diameter. Thus, lululemon’s proposed claim construction ignores the context surrounding the ’046 patent’s description of the tubular rib structures when it describes them as having the configuration of a tunnel or channel.” slip op. at 10
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We agree with Nike, given our construction of the claimed “tubular structures.” As shown in annotated Figures 1, 3, and 4 of Good (reproduced below), Good discloses a sock 12 having rib portions 22 (red) and webbed areas 24 (green). See PO Resp. 19. lululemon contends that Good’s rib portions 22 meet the claimed “tubular structures” because each rib portion 22 “roll[s] substantially together in the relaxed condition” and “has the shape of a tube, namely an elongate hollow structure.” Pet. 29–30. In support, lululemon points to Good’s Figure 3 (reproduced below center) as allegedly showing the tubular shape of Good’s rib portions 22. Id. at 30. Annotated Figure 3 is a vertical cross-section of rib portions 22 (red) shown in Good’s Figure 1. But, as Nike correctly notes, Good’s rib portions 22 are “C-shaped knitted portions,” which when stretched, go from an essentially C-shaped configuration (Figure 3) to a relatively flat, linear configuration (Figure 4). PO Resp. 19–20 (citing Ex. 2006 ¶¶ 48–49). Nowhere does Good disclose that the ends of C-shaped rib portions 22 ever meet and remain in a closed periphery configuration to form a hollow tube per our construction of “tubular structures” (as discussed above in Section II.B). In at least this way, Good’s C-shaped rib portions 22 differ from the claimed “tubular structures.”7 Thus, we find that Good does not disclose or otherwise suggest the claimed “tubular structures,” as properly construed, meaning that lululemon fails to demonstrate, by a preponderance of the evidence, that Good either anticipates claims 1–3, 7, 16–18, and 20, or, alternatively, renders obvious claim 3.” slip op. at 16
- Expert testimonyPetitioner expert discountedDecided for patent owner
“In our Institution Decision, we said that Munsing lacks the claimed “tubular structures” because “nowhere does Munsing indicate that the rows of stitches or loops form a rib that is tubular-like, let alone one with a closed periphery.” Inst. Dec. 10–12. During the trial phase, lululemon’s expert likewise agreed, conceding (on cross-examination) that Munsing only discloses non-tubular structures. See Ex. 2007, 40:9–41:11 (“Q [by Patent Owner’s counsel]: So you agree that . . . Munsing only discloses a nontubular rib? A [by lululemon’s expert]: That’s what I said.”). Nowhere does lululemon rebut that admission by its own expert, despite Nike noting it explicitly as a reason for rejecting Ground 2. Compare PO Resp. 25–26 (noting the admission of lululemon’s expert), with Pet. Reply 1–26 (addressing only Grounds 1 and 3, while omitting any mention of Ground 2, which is based on Munsing). Nor does lululemon ever dispute the preliminary findings in our Institution Decision as to why Munsing is not an anticipatory reference. Compare Inst. Dec. 10–12, with Pet. Reply 1–22. Thus, lululemon fails to demonstrate, by a preponderance of the evidence, that Munsing anticipates challenged claims 1–3, 7, 17, 18, and 20.” slip op. at 18
Patent outcomesUS 9,375,046 mixedClaim construction§ 102 anticipation§ 103 obviousnessPatents in suitUS 9,375,046 - Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCInstitution deniedPTAB · Dec 4, 2024 · IPR2024-00944 · APJ Scott B Howard · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that Rao anticipates or renders obvious claims 79 and 83.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“the information presented in the Petition does not demonstrate a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of any of the challenged claims of the ’541 patent. IV. ORDER In consideration of the foregoing, it is hereby: ORDERED that the Petition is denied.” slip op. at 24
- BurdenNot shown unpatentable
“the Petition (Ex. 1002 ¶¶ 189–193 (cited by Pet. 22)) and see no discussion as to what causes policies 520 to be sent to filter 322. See Ex. 2001 ¶¶ 42–43 (Mr. de la Iglesia testifying to same). Although Rao describes how agent 326 sends policies to filter 322, Rao is silent as to what causes that transmission: In some embodiments, the agent 326 indicates the priority to the filter 322 for management of network packet queues 540a- 540n to apply the indicated priorities. The agent 326 may communicate the priority of network packets to the filter 322 by any suitable means and/or mechanism such as via an application programming interface (API), such an IOCTL interface, or any other type and/or form of interface known to those ordinarily skilled in the art. Ex. 1002 ¶ 190. That is, Rao is silent as to whether filter 322 requests the policies (as Petitioner argues) or agent 326 acts on its own to send the policies (see Prelim. Resp. 3–6; Ex. 2001 ¶¶ 34–40). And without the message being sent to the filter, there is nothing for the filter to intercept.” slip op. at 19
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“the Petition (Ex. 1002 ¶¶ 189–193 (cited by Pet. 22)) and see no discussion as to what causes policies 520 to be sent to filter 322. See Ex. 2001 ¶¶ 42–43 (Mr. de la Iglesia testifying to same). Although Rao describes how agent 326 sends policies to filter 322, Rao is silent as to what causes that transmission: In some embodiments, the agent 326 indicates the priority to the filter 322 for management of network packet queues 540a- 540n to apply the indicated priorities. The agent 326 may communicate the priority of network packets to the filter 322 by any suitable means and/or mechanism such as via an application programming interface (API), such an IOCTL interface, or any other type and/or form of interface known to those ordinarily skilled in the art. Ex. 1002 ¶ 190. That is, Rao is silent as to whether filter 322 requests the policies (as Petitioner argues) or agent 326 acts on its own to send the policies (see Prelim. Resp. 3–6; Ex. 2001 ¶¶ 34–40). And without the message being sent to the filter, there is nothing for the filter to intercept.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“Neither the Petition nor Dr. Wolfe’s testimony provide any discussion as to why a person having ordinary skill in the art would have modified Rao to teach the additional limitation recited in either claim 79 or 83. See Pet. 22–23; Ex. 1015 ¶¶ 252–257. This stands in contrast to other portions of the Petition where Petitioner clearly set forth both anticipation and conditional obviousness arguments, including a reason to modify Rao. See, e.g., Pet. 13–15 (arguing that Rao discloses limitation 1e or that a person having ordinary skill in the art “would . . . have been motivated” to modify Rao). Thus, although the Petition purports to argue that claims 79 and 83 are obvious,8 the Petition lacks sufficient argument setting forth the basis for such an obviousness argument. At most, there is a conclusory statement that claims 79 and 83 are obvious. See Pet. 6 (“Rao anticipates most of the limitations discussed under this Ground for the reasons provided below. Rao renders these same limitations obvious for the same reasons.”). That is not sufficient. Where, as here, claims are alleged to be unpatentable as obvious over the prior art, Petitioner cannot make its case solely through mere conclusory statements. In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016). Moreover, it is not our role to examine the prior art advanced by Petitioner and fill the gaps in Petitioner’s reasoning and factual assertions. Magnum Oil Tools, 829 F.3d at 1381 (“[W]e find no support for the PTO’s position that the Board is free to adopt arguments on behalf of petitioners that could have been, but were not, raised 8 See Pet. 1 (“Rao ‘anticipates and/or renders obvious’ claims” 1, 79, and 83), 6 (“Rao anticipates most of the limitations discussed under this Ground for the reasons provided below. Rao renders these same limitations obvious for the same reasons. Rao also renders obvious the remaining limitations discussed under this Ground.”); Pet. Prelim. Reply 1 (“Rao therefore discloses or renders obvious intercepting a stack API level request by its filter requesting priorities from the agent.”). by the petitioner during an IPR.”); see also SAS Institute Inc. v. Iancu, 138 S.Ct. 1348 (U.S. 2008) (“in an inter partes review the petitioner is master of its complaint”); 37 C.F.R. § 42.104(b)(4) (“The petition must specify where each element of the claim is found in the prior art patents or printed publications relied upon”). Because Petitioner has not offered any reason why a person having ordinary skill in the art would have made a modification to claims 79 and 83, Petitioner has not sufficiently shown that claims 79 and 83 would have been obvious. See Belden Inc. v. Berk-Tek LLC, 805 F.3d 1064, 1073 (Fed. Cir. 2015) (“[O]bviousness concerns whether a skilled artisan not only could have made but would have been motivated to make the combinations or modifications of [the] prior art to arrive at the claimed invention.”).” slip op. at 22
Claim construction§ 102 anticipation§ 103 obviousnessDiscretionary denialcites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - PTAB · Dec 4, 2024 · IPR2024-00942 · APJ Scott B Howard · IPR · Institution
The Board instituted inter partes review of claims 2–23, 26, 41–60, 63, 64, 155–157, and 160–171 on all asserted grounds after finding a reasonable likelihood Rao anticipates claim 3.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“determine whether to institute an inter partes review under 35 U.S.C. § 314 and 37 C.F.R. § 42.4(a). Inter partes review may not be instituted unless “the information presented in the petition filed under section 311 and any response filed under section 313 shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). “When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.” 37 C.F.R. § 42.108(a).” slip op. at 2
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“corners of a single, prior art document describe every element of the claimed invention, either expressly or inherently, such that a person of ordinary skill in the art could practice the invention without undue experimentation.” Advanced Display Sys., Inc. v. Kent State Univ., 212 F.3d 1272, 1282 (Fed. Cir. 2000). “A single prior art reference may anticipate without disclosing a feature of the claimed invention if such feature is necessarily present, or inherent, in that reference.” Allergan, Inc. v. Apotex Inc., 754 F.3d 952, 958 (Fed. Cir. 2014). Moreover, the reference must also “disclose[] within the four corners of the document not only all of the limitations claimed but also all of the limitations arranged or combined in the same way as recited in the claim.” Net MoneyIN, Inc. v. Verisign, Inc., 545 F.3d 1359, 1371 (Fed. Cir. 2008). However, “the reference need not satisfy an ipsissimis verbis test.” In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009).” slip op. at 10
- Skill levelSkill level petitioner adoptedOther
“Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not yet disputed by Patent Owner, for purposes of this Decision, we adopt Petitioner’s formulation of the person having ordinary skill in the art.6” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. For the purposes of this Decision, we need not expressly construe any claim terms.7 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 13
Claim construction§ 102 anticipationcites Phillips · KSR · GrahamPatents in suitUS 8,589,541 - Iriusrisk, Inc. v. Threatmodeler Software Inc.All claims unpatentablePTAB · Nov 14, 2024 · IPR2023-00821 · APJ Stephen E Belisle · IPR · Final written decision
Claims 1 and 3 are unpatentable as anticipated by Jones; claims 2 and 4–20 are unpatentable as obvious over Jones, Zheng, and Keenan.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedOther
“B. Level of Ordinary Skill in the Art Petitioner contends that a person of ordinary skill in the art, at the time” slip op. at 14
- Expert testimonyPetitioner expert creditedDecided for petitioner
“9 In arguing that Jones does not disclose a “predefined interrelated group” of threat model components, Patent Owner, in a footnote, alleges that the testimony of Petitioner’s expert, Mr. Hurlbut, is “tainted by bias” arising from his “personal and professional connections” to Petitioner. PO Resp. 27 n.4; see PO Sur-reply 21–22. Patent Owner cites no authority to show that such connections necessarily render expert testimony biased, and identifies no actual testimony of Mr. Hurlbut that it alleges to be driven only by bias. On the other hand, Petitioner submits that Mr. Hurlbut also has personal and professional connections to Patent Owner—it’s a small world. See Pet. Reply 24 (“Mr. Hurlbut personally knows Mr. Agarwal, [Patent Owner’s] CEO and inventor of the ’008 patent.”). In this case, we assess the credibility of both parties’ experts based on the plausibility of and support for their testimony, and weigh such testimony accordingly. See Consolidated Trial Practice Guide (“CTPG”) at 32 (“[T]he credibility of experts often turns less on demeanor and more on the plausibility of their theories.”), 35 (“The Board has broad discretion to assign weight to be accorded expert testimony.”); see also 84 Fed. Reg. 64,280 (Nov. 21, 2019).” slip op. at 37
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
Patent outcomesUS 10,699,008 unpatentable§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,699,008 - 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 - Netflix, Inc. v. Videolabs, Inc.All claims unpatentablePTAB · Oct 2, 2024 · IPR2023-00628 · APJ Jeffrey S Smith · IPR · Final written decision
Claims 1–14 are unpatentable: claims 1–4 and 8–11 as anticipated by Mehta, and claims 1–14 as obvious over Mehta and Schläpfer.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“The level of ordinary skill in the art usually is evidenced by the references themselves. 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). As Petitioner’s description of a person of ordinary skill appears commensurate with the subject matter before us, we apply Petitioner’s definition for purposes of this Decision.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“We construe only those claim terms that require analysis to resolve the controversy. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that “only those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy”). Any special definition for a claim term must be set forth in the specification with reasonable clarity, deliberateness, and precision. In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994). Petitioner and Patent Owner agree that no claim terms require specific construction to resolve the unpatentability issues presented in the Petition. Pet. 23; PO Resp. 10–11. We agree and do not construe any terms.” slip op. at 9
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“Analysis We agree with Petitioner. Mehta discloses storing “functionally equivalent programs having the same name that are capable of running on multiple kinds of devices that even may be written using different languages.” Ex. 1003 ¶ 98. Mr. Wechselberger testifies that this disclosure shows that Mehta’s “MAS receives, stores and supports functionally equivalent programs capable of running on multiple devices because each program corresponds to a different device having different device capabilities (e.g., written using different languages).” Ex. 1002 ¶ 66. This testimony is consistent with that of Dr. Goodrich, who testifies that “each application has a single version made for a particular device type.” Ex. 2020 ¶ 66. Dr. Goodrich later testifies that paragraph 98 of Mehta describes that there could be two functionally equivalent programs with the same name that are compatible with a single user’s computer. Id. at ¶ 88; see PO Resp. 31–32 (citing Ex. 2020 ¶¶ 87–88). We do not credit this later testimony, because it is inconsistent with Dr. Goodrich’s earlier testimony that “each application,” or program of Mehta, is “made for a particular device type.” Ex. 2020 ¶ 66. We agree with Mr. Wechselberger and find that a person of ordinary skill in the art at the time of invention would have understood that Mehta’s disclosure of functionally equivalent programs having the same name that are capable of running on multiple kinds of devices means that each program corresponds to a different device having different capabilities. Further, Mehta discloses that “the MAS only lists those applications that are supported by the subscriber’s device. This allows the subscriber to avoid the problem of having to explicitly select a compatible application.” Ex. 1003 ¶ 117; see Pet. 36–37 (citing Ex. 1002 ¶¶ 75, 77). Mr. Wechselberger testifies that a person of ordinary skill in the art at the time of invention would have understood this disclosure to mean that the MAS provides the subscriber with only a single subscriber-appropriate version that will work for the subscriber. Ex. 1002 ¶ 77. Although Patent Owner contends that Mehta is silent on whether only a single description would be provided if there were multiple implementations (PO Sur-Reply 10–11), we agree with Mr. Wechselberger and find that when multiple implementations have the same name, each implementation corresponds to a different device, and therefore, the MAS would only present to the subscriber the one implementation that works with the subscriber’s device. Ex. 1002 ¶¶ 66, 75, 77.” slip op. at 28
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“piece of content, while the versions of Microsoft Word for Windows and Microsoft Word for Apple Macs are different implementations.” Ex. 2020 ¶ 39. Dr. Goodrich, in his deposition, when asked if “one of ordinary skill in the art at the time of the ’790 patent would also understand that Microsoft Word for Windows and Microsoft Word for Mac are also functionally equivalent, correct?” answered “Yes . . . . But they would be even stronger than simply functionally equivalent. They would be different implementations of the same product.” Ex. 1029, 43:14–24. However, later in his deposition, Dr. Goodrich testifies that Microsoft Word for Windows and Microsoft Word for Apple Mac are separate applications, not different implementations of the same application. Ex. 1029, 48:1–20. We disagree with this later testimony. Neither Dr. Goodrich nor Patent Owner persuasively explains why Dr. Goodrich changed his unambiguous position from both his declaration and his earlier deposition testimony. For example, Dr. Goodrich testifies in his deposition that “for the Lion King example, a .MP3 and a .MOV are different implementations of the same product. They’re also functionally equivalent, but functionally equivalent is broader.” Ex. 1029, 45:7–11. Dr. Goodrich continues, “when Mehta is disclosing functionally equivalent, it is not referring to it as different implementations of the same product. Instead, it’s [describing] how to disambiguate [applications] not clustered in terms of implementations . . . based on other metadata.” Id. at 45:14–21. This explanation is unpersuasive because it is inconsistent with Dr. Goodrich’s declaration testimony, in which Dr. Goodrich explicitly testifies that the different versions of Lion King, as well as the different versions of Microsoft Word, are different implementations of the same product. Ex. 2020 ¶ 39. Specifically, in his declaration, Dr. Goodrich testifies that the “various versions of Lion King (such as an .mp3 file or an .mov file) are the implementations of the Lion King. For another example, . . . the versions of Microsoft Word for Windows and Microsoft Word for Apple Macs are different implementations.” Ex. 2020 ¶ 39. Dr. Goodrich testifies again that “Microsoft Word for Windows and Microsoft Word for Apple Macs” are “multiple implementations of an individual item of digital content.” Ex. 2020 ¶ 70. Further, the reason given in the explanation in his deposition, that Mehta needs to disambiguate applications that are not clustered in terms of implementations based on other metadata, would also apply to the different versions of Lion King, yet Dr. Goodrich consistently testifies that these different versions are different implementations, both in his declaration and in his deposition. Id.; Ex. 1029, 45:7–10. Petitioner contends, and we agree, that the inconsistent testimony of Dr. Goodrich appears to be an attempt to cure Patent Owner’s and Dr. Goodrich’s incomplete analysis of Mehta’s disclosure. See Reply 7–8. In particular, the Petition quotes Mehta’s disclosure that the MAS stores “functionally equivalent programs having the same name that are capable of running on multiple kinds of devices that even may be written using different languages.” Pet. 28 (quoting Ex. 1003 ¶ 98). Dr. Goodrich addresses this disclosure by explaining that two applications, such as Microsoft Word and Apple Pages, are functionally equivalent but are two different applications, not multiple implementations of a single application. Ex. 2020 ¶ 70. In this analysis, Dr. Goodrich does not address the full disclosure of Mehta, which describes that the “functionally equivalent programs hav[e] the same name” (Ex. 1003 ¶ 98), such as Dr. Goodrich’s example of Microsoft Word for Windows and Microsoft Word for Apple Macs. See id. Thus, although Dr. Goodrich is correct in testifying that some functionally equivalent programs, such as Microsoft Word and Apple Pages, are not different implementations of an item of digital content, he is also correct in testifying that “Microsoft Word for Windows and Microsoft Word for Apple Macs” are “multiple implementations of an individual item of digital content.” Id. Yet Dr. Goodrich does not identify any difference between the multiple implementations of Microsoft Word and the functionally equivalent programs having the same name as described by Mehta.” slip op. at 18
Patent outcomesUS 7,233,790 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,233,790
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.