• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00710 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1–7, 9, 13, and 16–20 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 8 was not shown unpatentable under either ground.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’294 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7

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

    “Petitioner indicates that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction. Thus, no express construction is required.” Pet. 13 (citing Ex. 1003 ¶ 86). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed

    “rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “and reliance on Figure 19 do not in any way explain how updating game costs by meter 502 with a new Cost_Table is relevant to a credit multiplier or even a multiplier being varied over time. Ex. 1003 ¶ 155. Considering this evidence, we determine that Petitioner and Mr. Crevelt’s reliance mainly on snippets from Schneier’s “Updating Cost Information protocol” embodiment does not sufficiently explain why or how a person of ordinary skill in the art would have understood updating game cost to encompass varying a multiplier of credits over time. We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004:158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to persuasive evidence in Schneier as to how or why a person of ordinary skill in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 8.” slip op. at 20

  Patent outcomesUS 10,825,294 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,825,294
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00709 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1, 2, 4, 6, 8, 10, 14–18, 21–23, 25, 27, and 29 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 9 was not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner states it “does not dispute Petitioners’ proposed level of skill, and under any level of skill a POSITA would not understand the asserted Grounds to raise any unpatentability issue.” PO Resp. 4. Patent Owner states further that “this [Patent Owner Response] and supporting declarations apply Petitioner’s proposed level of skill.” Id. On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’635 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7

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

    “Petitioner indicated in the Petition that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction.[] Thus, no express construction is required.” Pet. 12–13 (citing Ex. 1003 ¶ 85). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004, 158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. Id. at 161:2–6. These explanations are unpersuasive because the testimony relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 9.” slip op. at 21

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed

    “Discount Credit Pricing Structure The $0.20 discount described by Schneier for purchasing 20 credits, rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not address the idea of a time component, i.e., “over time,” as required by claim 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 18

  Patent outcomesUS 10,650,635 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,650,635
• CSPC Megalith Biopharmaceutical Co., Ltd. v. Lepu Biopharma Co. Ltd.All claims unpatentable
  PTAB · Oct 8, 2026 · IPR2025-00685 · APJ Ryan H Flax · IPR · Final written decision

  Claims 1–23 are unpatentable as obvious over Wei and Liu, and over Leanna, Wei, and Liu.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “appears to be generally consistent with the level of skill presented in the cited prior art. See generally, e.g., Exs. 1005–1008; see also Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art itself may reflect an appropriate level of skill in the art). However, as at institution, we reject the portion of Petitioner’s proposed definition that includes having “access to other individuals with that knowledge and experience,” as not reflecting the individual level of skill of a given skilled artisan. See, e.g., Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986) (holding that “[t]he person of ordinary skill is a hypothetical person who is presumed to be aware of all the pertinent prior art.”) (emphasis added, footnotes omitted); but see Indivior Inc. v. Dr. Reddy’s Labys., S.A., 930 F.3d 1325, 1343 (Fed. Cir. 2019) (no clear error in determination that “a person of ordinary skill . . . ‘would be on a team with an engineer or scientist . . . .’”). Consequently, we find the person of ordinary skill in the art was a person who had a Ph.D. in immunology, molecular biology, cellular biology, or a similar field, or an M.D. with similar experience, and had at least five years of experience with antibodies and antibody engineering.” slip op. at 11

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

    “Petitioner submits that no term of the Challenged Claims requires construction to resolve the challenges in this Petition.” Pet. 32. We did not construe any terms in our Institution Decision. See DI 6–7. Patent Owner presents no express positions on claim construction. See generally Resp. For the purposes of this Decision, no terms of the challenged claims require construction. Phillips, 415 F.3d at 1312–13. D. slip op. at 12

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “2 G. Wei et al., US 2015/0071923 Al, pub. March 12, 2015. Ex. 1005 (“Wei”). 3 J. Liu, CN 103772504 A, pub. May 7, 2014. Ex. 1007. The Liu reference is published in Simplified Chinese and Petitioner filed a certified English translation, to which we refer herein. See Ex. 1008 (“Liu”). Patent Owner does not contest the accuracy of the translation. See generally Resp. 4 M.R. Leanna & C.L. Becker, WO 2014/152199 A1, pub. Sept. 25, 2014. Ex. 1006 (“Leanna”). 5 Based on our review of each deposition transcript in view of the record as a whole, although each witness appears competent, we are left with the impression that Dr. Bournazos’s testimony is somewhat more credible than Dr. Atanackovic’s. This conclusion is based, inter alia, on each witness’s ability to recall the relevant record and respond to questions on evidentiary and technical issues.” slip op. at 8

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

    “We find that combining Liu’s BA03 antibody with Wei’s ADC platform would have been desirable, predictable, and routine for the ordinarily skilled artisan based on the facts that: (1) cetuximab was a wellknown and well-studied, U.S. regulatory approved, anti-EGFR antibody that would have served as a starting point for new cancer therapies; (2) humanization of therapeutic antibodies is generally desired (and “[e]very antibody can be humanized” and it is advantageous according to Patent Owner’s counsel); (3) BA03 was a well-known humanized version of cetuximab that had several known advantages over cetuximab in addition to lower immunogenicity from humanization; and (4) Wei taught a similar cetuximab-derived antibody, and a humanized cetuximab-derived antibody, each provided in an ADC with a well-known and validated off-the-shelf linker-drug platform, i.e., vc-MMAE, that exhibited a strong anti-tumor response. See, e.g., Ex. 1001, 1:57–2:32, 2:50–3:1, 5:6–53, 18:3–33, 19:26– 29; Ex. 1002 ¶¶ 14, 38, 42–43, 45–53, 56–73, 84–92, 109–117, 178–189, 202–271; Ex. 1005 ¶¶ 9–10, 229–232, 434, 437, 476, 491–506, 664–675, 685, 688, 715, 732, 1103, 1092–1141; Ex. 1008 ¶¶ 3–6, 60, 74, 141–160; Ex. 2027 ¶¶ 7–8, 38, 50, 57 (confirming our understandings regarding the claimed antibody and linker-drug payload); Ex. 2023, 173, 300; see also Resp. 1, 5–6, 23 (Patent Owner made the “choice” to use the prior-art-known BA03 antibody, and known-candidate cytotoxic payload MMAE); Hr’g Tr. 34:20–23, 36:6–38:20, 47:16–50:16 (Patent Owner’s counsel’s argument). When Liu’s BA03 antibody is provided in an ADC with a vc- MMAE or a Mc-vcPAB-MMAE platform (and used as cancer therapy as the references instruct) the invention of the challenged claims is achieved.” slip op. at 52

  Patent outcomesUS 10,792,370 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,792,370
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCAll claims unpatentable
  PTAB · Oct 8, 2026 · IPR2025-00711 · APJ Linda E Horner · IPR · Final written decision

  Claims 1, 2, 4–7, 9, 11–13, 15, 19, 23, 24, and 29 are unpatentable as obvious over Kelly, Kelly and Paulsen, or Walker and Schneier.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “B. Level of Ordinary Skill in the Art There is no evidentiary dispute about the level of ordinary skill in the art.7 Based on the testimony of Mr. Crevelt, we determine that a person of ordinary skill in the art would have had at least a bachelor’s degree in computer science or computer engineering, with at least three years of experience in game development. Pet. 12 (citing Ex. 1003 ¶¶ 100–103). Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Id. We determine that the level of ordinary skill in the art adopted above is consistent with the level of technical understanding and competence reflected in the ’164 patent Specification and the asserted prior art references, based on our review of the record.” slip op. at 10

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

    “Petitioner argues that it is not necessary for the Board to provide an express construction for any claim term because the Petition “establishes the prior art meets each claim limitation under any reasonable construction.” Pet. 13. Patent Owner similarly submits that “[t]he Board need not construe any terms at this stage, because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” Resp. 8–9. Patent Owner notes, however that “it has relied on the plain meaning of ‘frequency of play’ in Claim 7.” Id. at 9. We agree that no explicit claim construction is necessary for this decision because, even were we to adopt Patent Owner’s proffered plain meaning of “frequency of play,” Petitioner has demonstrated that the prior art renders obvious this claim limitation. To the extent the parties’ arguments raise any implicit issues of claim construction, we address those issues within the context in which they are raised in our analysis below.” slip op. at 11

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “Patent Owner does not contest Petitioner’s showing that Kelly renders obvious the subject matter of claims 1, 2, 4–6, 11–13, 15, 19, 23, 24, and 29. Resp., passim; Tr. 50:4–13.8 We have reviewed Petitioner’s arguments and 8 Patent Owner argued in its Preliminary Response that Kelly does not disclose limitations [1.c.iii] and [1.c.v]. Prelim. Resp. 10–12. In our Institution Decision, we did not find these contentions persuasive based on the initial record. Dec. 20–24. Patent Owner has not presented these or any other arguments contesting Ground 1 as to claim 1 in its Response. Resp., the evidence and, based on that analysis, we find that Petitioner has shown by a preponderance of evidence that Kelly renders obvious the subject matter recited in these claims.” slip op. at 17

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

    “and Paulsen render obvious claims 2 and 4. Pet. 36–40. Petitioner submits that to the extent Kelly’s player account is not player’s club information or information on non-cash amounts, a person having ordinary skill in the art would have been motivated to implement these features based on the teachings of Paulsen. Id. Specifically, Petitioner asserts that Paulsen teaches player tracking cards and player tracking programs including player tracking points. Id. at 38–40 (citing Ex. 1007 ¶¶ 8, 9, 49). Petitioner argues that a person having ordinary skill in the art would have been led to add these features to Kelly’s system to provide a more detailed view of tracking play, which would allow for rewarding patronage and engagement. Id. at 36–37, 39–40 (citing Ex. 1003 ¶ 264; Ex. 1007 ¶ 10). Paulsen discloses a “gaming machine bonusing method utilizing a player tracking card.” Ex. 1007, code (54). Paulsen discloses that player tracking programs and player tracking cards were used in the art to provide rewards, or “comps,” to players based on the player’s level of patronage (e.g., to the player’s playing frequency and/or total amount of game plays at a given casino). Id. ¶ 8. These rewards were intended to maintain a player’s interest in additional game play during a visit and provide loyalty incentives to players. Id. at ¶ 9.” slip op. at 29

  Patent outcomesUS 11,335,164 unpatentable
  Claim construction§ 103 obviousness
  Patents in suitUS 11,335,164
• Axon Enterprise, Inc. / Dedrone Holdings, Inc. v. Airspace Defense, Inc.Other
  PTAB · Oct 6, 2026 · IPR2025-00530 · APJ Scott C Moore · IPR · Final written decision

  Original claims 1–9 were canceled; the non-contingent motion to add substitute claims 10–18 was denied for lack of written-description support, and claim 18 was also indefinite.

  RulingsFinal written decision

  • 112 supportMotion to amend, deniedDenied

    “that either the ’303 application or the ’838 provisional contain adequate written description support for the disputed feature of limitation [10.d]. Though the disclosures cited by Patent Owner indicate that a secondary identifier can be used to aid in verification of a UAV, these disclosures also make clear that both first and second identifiers are transmitted by and received from the UAV. See, e.g., Ex. 2002, 4:15–17, 30:24–31:6; Ex. 2003 ¶¶ 14, 66. Patent Owner’s reliance on disclosure characterized as transmitting an identifier from a remote computing system “through the UAV” (Reply 2) is not persuasive. The cited disclosures from the ’303 application and ’838 provisional generally disclose that the identifiers transmitted by a UAV can be “generated remotely,” such as by a “remote computing system.” Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45. But Patent Owner has not identified disclosure indicating that a remote computing system may transmit an identifier to the identification receiver. In the ’303 application and ’838 provisional, only the UAV (which is part of the discrimination system, and thus not “remote”) actually transmits identifiers to the identification receiver. Patent Owner is correct in its assertion that an “aerial system identifier can be generated on-board the aerial system” or “generated remotely . . . at a remote computing system.” Mot. 7 (citing Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45). But even if a UAV’s identifier was at some time in the past generated by a remote computing system, the subsequent transmission of that identifier from the UAV to the identification receiver would not satisfy the plain language of limitation [10.d]. The claim language “receive … a second identifier from a computing system that is remote to the discrimination system” requires the receipt of a transmission of the second identifier from a remote computing system. This claim language limits the source of the received transmission (i.e., where the particular transmission is “receive[d] … from”). Thus, the relevant issue is from where was the recited second identifier received. The relevant is not where the second identifier was originally generated.” slip op. at 12

  • Disclosure Requirements (§112) › Definiteness (Nautilus)DefiniteIndefiniteMixed

    “We determine that the disputed language in limitation [10.d] is not indefinite. There is no recitation in proposed substitute claim 10 that the second identifier is transmitted solely from the identifier transmission system. Thus, the alleged irreconcilable contradiction cited by Petitioner is not recited in the claims. Petitioner’s position appears to rest on the fact that the ’303 application and ’838 provisional do not disclose receiving the second identifier from a remote computing system. See Sur-reply 6 (“To manufacture written description support, [Patent Owner] argues the claim encompasses identifiers routed ‘through the UAV.’”). Though we agree that limitation [10.d] lacks adequate written description support, this defect does not render the claim indefinite because the scope of limitation [10.d] is otherwise reasonably certain based on its plain language. See supra § III.C.4.” slip op. at 18

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference not prior artPriority date, deniedDecided for patent owner

    “In contrast, the ’393 provisional never discloses that the described drone defense system may use the identity of a detected drone to develop a particular countermeasure. The disclosed RTSS certainly uses identity information to determine whether a drone is a threat. And if a threat is identified, the RTSS immediately starts “a series of processes … to determine what rule of engagement will be applied on the intruding drone.” Ex. 1006 ¶ 10. The ’393 provisional discloses that the system may select a particular countermeasure based on (i) the particular zone within a protected area within which a drone is located, (ii) “the behavior of the hostile drone,” or (iii) “other instructions.” Id. ¶¶ 9, 10. But the ’393 provisional never discloses that these “other instructions” may include the identity of the drone. The system disclosed in the ’393 provisional uses the identity of a drone to determine whether to activate the countermeasure system. See id. ¶¶ 16–18. But there is no disclosure in the ’393 provisional that the countermeasure system, once activated, uses the identity of the drone to develop the particular countermeasure to be employed. See generally Ex. 1006. Thus, though the Whitmarsh reference itself contains ample written description support for limitation [19e], the earlier-filed ’393 provisional does not. On this record, and having reviewed the ’393 provisional in its entirety, we determine that the ’393 provisional does not “reasonably convey[] to those skilled in the art that the inventor had possession of” the subject matter of limitation [19e] of Whitmarsh’s claim 19 “as of the filing date” of the ’393 provisional. See Ariad, 598 F.3d at 1351.” slip op. at 27

  § 102 anticipation§ 112 disclosurecites Nautilus
  Patents in suitUS 10,249,199
• GD Energy Products, LLC v. Kerr Machine CompanyAll claims unpatentable
  PTAB · Jun 29, 2026 · PGR2025-00031 · APJ Ryan H Flax · PGR · Final written decision

  Claims 1–14 are unpatentable as obvious under each of four asserted grounds: Kerr; Aplex and Stanton; Blume, Stanton, and Wilkinson; and the sale of the Kerr Pump.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The person of ordinary skill in the art would have a minimum of a bachelor’s degree in mechanical or petrochemical engineering, or a comparable engineering discipline, and a minimum of 3-5 years of work experience in the design and/or manufacturing of reciprocating pumps and valves, including fluid ends and/or comparable high pressure fluid components, for industrial applications, including for use in the oil and gas industry. See, e.g., EX1003, ¶32.” slip op. at 12

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

    “[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We decline to expressly construe any claim language. slip op. at 12

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

    “Regarding the combining of Aplex and Stanton, Petitioner asserts that the ordinarily skilled artisan would have understood that providing a packing/stuffing arrangement, as taught by Stanton, within a fluid end housing, as taught by Aplex, would improve pressure and fluid isolation compared with an arrangement where the packing was bolted to the outside of the fluid end as in Aplex unmodified. Pet. 66 (citing Ex. 1003 ¶¶ 189, 236). Patent Owner does not dispute this rationale. We find this to be a reason, with rationale underpinning, why the person of ordinary skill in the art would have combined these references with a reasonable expectation of success.” slip op. at 29

  • Adverse judgmentOther

    “The record indicates that Patent Owner has statutorily disclaimed claim 15 as of April 28, 2025. Ex. 2206.” slip op. at 8

  Patent outcomesUS 12,152,582 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,152,582
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightMotivation not foundNot shown unpatentable

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Geneoscopy, Inc. v. Exact Sciences CorporationAll claims unpatentable
  PTAB · Feb 5, 2026 · IPR2024-01330 · APJ Ryan H Flax · IPR · Final written decision

  Claims 3, 4, and 12–19 are unpatentable as obvious under each asserted ground.

  RulingsFinal written decision

  • Skill levelOther
  • Expert testimonyOther
  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “embody claims of the ’746 patent, the product has features not covered by the ’746 patent’s claims, some of which are critical unclaimed elements according to Patent Owner. Accordingly, Cologuard is not coextensive with the challenged claims, and no nexus between the product and the challenged claims is shown on this record.” slip op. at 35

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

    “developed where the patient need not manipulate their fecal sample to portion it, but the law of obviousness does not require an option to be the best option to be obvious. For these reasons, bearing in mind that the ultimate burden here is always on Petitioner, we are not persuaded by Patent Owner’s argument. We also reject Patent Owner’s argument that only impermissible” slip op. at 60

  Patent outcomesUS 11,970,746 unpatentable
  § 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,970,746
• Allstate Insurance Company v. Atos, LLCSome claims unpatentable
  PTAB · Jan 30, 2026 · IPR2021-01449 · APJ Jon M Jurgovan · IPR · Remand

  Claims 3–5 are unpatentable; claims 1 and 2 are not shown unpatentable. Claims 3 and 4 are obvious over the applied grounds under the remand construction of “movement vector.”

  RulingsRemand decision

  • RemandOther

    “was incorrect, vacated the Final Written Decision as to claims 3 and 4, and remanded the case to the Board to determine the ordinary and customary meaning of “movement vector” and decide the outcome for claims 3 and 4 in accordance with that meaning. Atos, LLC v. Allstate Insurance Company, 2025 WL 1482404, at *5 (Fed. Cir. May 23, 2025); Paper 35 (“Federal Circuit Remand,” “Remand,” or “Fed. Cir. Remand”). Pursuant to the Federal Circuit’s instructions, the Board authorized the” slip op. at 3

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner

    “considered individually and together, have well-understood, common meanings to ordinarily skilled artisans as of the invention date, reflected by the ’174 patent’s specification and other evidence of record noted above. Accordingly, we determine that the ordinary and customary meaning of “movement vector” is “a vector indicating movement of an object.” 3) “operation indicator” Petitioner” slip op. at 20

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

    “Dr. Kanellakopoulos’s explanation that angular momentum is not inherent to an object, and its computation requires an arbitrary choice of a point of origin that has no physical meaning in the context of vehicle motion, also supports Patent Owner’s position. Id. ¶ 71 (citing Ex. 2004, 262). Accordingly, Patent Owner’s argument, that angular momentum cannot be used to detect a vehicle turning, is persuasive. Id. We also find persuasive, as Dr. Kanellakopoulos explains, that Petitioner’s argument regarding the figure on Kleppner 234 is based on misinterpretation of the vectors in that figure. Id. ¶ 67 (explaining that Kleppner 233–234 does not depict a gravity vector).” slip op. at 35

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable

    “Kleppner does not disclose a rotation vector, a person of ordinary skill would have used the knowledge of a rotation vector (because it is a term of art) alongside Kleppner’s teaching, to arrive at claim 1. See Pet. Reply 11. This argument does not satisfy Petitioner’s burden to provide articulated reasoning with some rational underpinning to support the conclusion of obviousness. See KSR, 550 U.S. at 419 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Petitioner does not explain which teaching of Kleppner a person of ordinary skill would have selected and combined with their knowledge of a rotation vector to yield the method of claim 1, or explain why a person of ordinary skill would have recognized based on Kleppner that estimating the angle between a rotation vector and gravity vector could be used to detect a vehicle turning. Nor does Petitioner respond to Patent Owner’s assertion that Kleppner provides no rationale for estimating an angle of alignment between a rotation vector and gravity vector as a way of detecting a vehicle turning. See Ex. 2001 ¶ 65.” slip op. at 35

  Patent outcomesUS 9,846,174 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,846,174
• Avation Medical, Inc. v. Emkinetics, Inc.All claims unpatentable
  PTAB · Jan 7, 2026 · PGR2024-00043 · APJ Ryan H Flax · PGR · Final written decision

  Claims 1–39 are unpatentable under Grounds 1–10; Petitioner did not prove lack of enablement under Ground 11, and Patent Owner’s motion to exclude was denied.

  RulingsFinal written decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “REAL PARTIES-IN-INTEREST Petitioner identifies Avation Medical, Inc. as the real party-in-interest. Pet. x. Patent Owner identifies EMKinetics, Inc. as the real party-in-interest. Paper 5, 1; Paper 6, 1. Neither party contests the other’s assertions on this. C.” slip op. at 3

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A POSA at the time of the claimed invention would have had an undergraduate degree in the field of biomedical engineering or a related discipline, such as electrical engineering, and at least two years of experience in the design and/or analysis of biomedical devices. Additional work experience could substitute for a formal degree and vice versa. Ex.1003, ¶21. Pet. 20 (citing Ex. 1003). Patent Owner does not contest this proposed definition or offer an alternative. See generally Resp. We accept and use Petitioner’s uncontested definition of the ordinarily skilled artisan, which appears to comport with the level of skill in the art reflected in the prior art of record and the ’943 patent. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“the prior art itself [may]” slip op. at 19

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

    “same claim construction standard that is used to construe patent claims in a civil action in federal district court. 37 C.F.R. § 42.200(b). In construing claims, district courts and the Board here, by default, give claim terms their ordinary and customary meaning, which is “the meaning that the term would have to a person of ordinary skill in the art in question at the time of the invention.” Phillips v. AWH Corp., 415 F.3d 1303, 1312–13 (Fed. Cir. 2005) (en banc). Petitioner states that, “no terms require construction for purposes of this Petition.” Pet. 21. Patent Owner presents no express position on claim construction. See generally Resp. We do not expressly construe any claim terms. E.” slip op. at 20

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedReference is prior artDecided for petitioner

    “question, based on factual findings. VidStream, 981 F.3d at 1063–64. Moreover, public accessibility is the touchstone in determining whether a reference is a printed publication and such depends on whether the reference was available to interested, ordinarily skilled persons exercising reasonable diligence, which is determined on a case-by-case basis. Id. at 1065. Particularly pertinent here is that “[w]hen there is an established publisher there is a presumption of public accessibility as of the publication date.” Id. Hulu (which cites VidStream on this issue) concerned, inter alia, whether certain asserted references were shown to be publicly available and could be considered as prior art. Hulu, 2021 WL 487622. Hulu holds that, although testimonial evidence is one way to prove public accessibility, there are also a variety of hallmarks of publication and other evidence that may be considered as a totality of the evidence to determine if an asserted reference was publicly accessible and prior art. Id. at *10–13, 21. Facts to be considered in analyzing the issue, other than testimonial evidence, include, for example, whether there is an established publisher, a copyright date/notice, other publication-related dates (impression, printing, etc.), an ISBN number, citations to the reference before (and to a lesser degree, after) the priority date at issue corroborating its availability and/or that the publisher was established, and whether the reference’s “purpose of publishing . . . was ‘dialogue with an intended audience.’” Id. at *10–21 (citing Valve Corp. v. Ironburg Inventions Ltd., 8 F.4th 1364, 1374 (Fed. Cir. 2021)).” slip op. at 30

  Patent outcomesUS 11,844,943 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham
  Patents in suitUS 11,844,943

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.