PTAB
Advanced fields
32 decisions · 559msnewest first
  • 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
  • PTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision

    Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.

    RulingsFinal written decision
    • BurdenOther

      “Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2

    • Skill levelOther

      “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed

      “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

    Patent outcomesUS 11,069,337 unpatentable
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 11,069,337
  • PTAB · Jul 14, 2025 · IPR2024-00465 · APJ Bart A Gerstenblith · IPR · Final written decision

    Claims 1–24 are unpatentable: claims 1–10 and 12–24 as obvious over Szrek and Llach, and claim 11 as obvious over Szrek, Llach, and Gilmore.

    RulingsFinal written decision
    • Skill levelSkill level board ownDecided for petitioner

      “B. Level of Ordinary Skill in the Art Petitioner proposes that the level of ordinary skill in the art is an artisan with a working knowledge of POS activation systems and lottery systems that was gained through a mixture of training and work experience in the relevant field such as (i) having a Bachelor’s degree in computer science, computer communications, electrical engineering, or equivalent degree, coupled with at least three years of work experience; (ii) having a Master’s degree in computer science, computer communications, or electrical engineering, but having less work experience; or (iii) having no formal degree, but having experience in the relevant field of at least six years of work experience. Pet. 2–3 (citing Ex. 1003 ¶¶ 13–14).9 Patent Owner states that, “[f]or the purpose of this proceeding, Patent Owner adopts the Petition’s proposed definition of the level of ordinary skill in the art.” PO Resp. 19 (citing Pet. 2–3). We find that the parties’ agreed-upon level of ordinary skill in the art is consistent with the level of ordinary skill in the art reflected by the ’451 patent and the prior art of record. See Inst. Dec. 14; see Okajima v. 9 Petitioner proposes the same level of ordinary skill in the art that the Board adopted in PGR2020-00084 (Pet. 2–3 (citing Ex. 1008, 11)), and IPR2023- 01235 (see IPR2023-01235, Paper 34 at 12–13). 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). Therefore, we adopt the parties’ agreed-upon level of ordinary skill in the art, as articulated above, in our consideration of the issues presently before us.” slip op. at 13

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

      “We need not construe “transaction processor” expressly because its meaning is not in dispute and its construction is not necessary to resolve the controversy before us.” slip op. at 16

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

      “On balance, we find that even with the alleged disadvantages identified by Patent Owner, one of ordinary skill in the art would have been motivated to modify Szrek with Llach’s third-party transaction processor because the advantage of having a “centralized intermediary” allows Szrek’s system to support different game providers, such as different lottery companies, which would reduce some implementation costs and allow the system to be more easily and cheaply extended. Pet. 47 (citing Ex. 1003 ¶ 181); see Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006) (“a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine”) (citing Winner Int’l Royalty Corp. v. Wang, 202 F.3d 1340, 1349 n.8 (Fed. Cir. 2000)); see also Intel Corp. v. Qualcomm Inc., 21 F.4th 784, 795 (Fed. Cir. 2021) (stating the same). We acknowledge that the combination comes with some disadvantages, including “add[ed] delay, reduce[d] efficiency, and . . . implementation complexities by converting a simple, direct communication exchange into an exchange that traverses multiple systems.” PO Resp. 52 (citing Ex. 2052 ¶ 163). But, “[t]he fact that the motivating benefit comes at the expense of another benefit, however, should not nullify its use as a basis to modify the disclosure of one reference with the teachings of another. Instead, the benefits, both lost and gained, should be weighed against one another.” Winner, 202 F.3d at 1349 n.8. Here, Szrek expressly teaches indirect communication as a possible implementation of its system and Petitioner’s combination—employing Llach’s third-party transaction processor as part of the indirect communication channel—offers the attractive benefit of allowing Szrek’s system to support different game providers, which would reduce some implementation costs even if it might increase other costs, e.g., by having to program certain components (e.g., the cash registers) differently. Specifically, we find that the ability to expand Szrek’s system to support different game providers provides advantages that outweigh the disadvantages discussed above in the circumstance where one desires a more robust and comprehensive system. See Pet. Reply 23 (noting three advantages of the combination— (1) “allow[ing] Szrek’s system to use ‘a centralized system for activating lottery tickets from different retailers and different locations,’” (2) “allow[ing] support for different game providers, such as different lottery companies,” “reduc[ing] implementation costs,” and (3) “allow[ing] Szrek’s system to ‘communicate with individual card” slip op. at 37

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

      “On balance, we find that even with the alleged disadvantages identified by Patent Owner, one of ordinary skill in the art would have been motivated to modify Szrek with Llach’s third-party transaction processor because the advantage of having a “centralized intermediary” allows Szrek’s system to support different game providers, such as different lottery companies, which would reduce some implementation costs and allow the system to be more easily and cheaply extended. Pet. 47 (citing Ex. 1003 ¶ 181); see Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006) (“a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine”) (citing Winner Int’l Royalty Corp. v. Wang, 202 F.3d 1340, 1349 n.8 (Fed. Cir. 2000)); see also Intel Corp. v. Qualcomm Inc., 21 F.4th 784, 795 (Fed. Cir. 2021) (stating the same). We acknowledge that the combination comes with some disadvantages, including “add[ed] delay, reduce[d] efficiency, and . . . implementation complexities by converting a simple, direct communication exchange into an exchange that traverses multiple systems.” PO Resp. 52 (citing Ex. 2052 ¶ 163). But, “[t]he fact that the motivating benefit comes at the expense of another benefit, however, should not nullify its use as a basis to modify the disclosure of one reference with the teachings of another. Instead, the benefits, both lost and gained, should be weighed against one another.” Winner, 202 F.3d at 1349 n.8. Here, Szrek expressly teaches indirect communication as a possible implementation of its system and Petitioner’s combination—employing Llach’s third-party transaction processor as part of the indirect communication channel—offers the attractive benefit of allowing Szrek’s system to support different game providers, which would reduce some implementation costs even if it might increase other costs, e.g., by having to program certain components (e.g., the cash registers) differently. Specifically, we find that the ability to expand Szrek’s system to support different game providers provides advantages that outweigh the disadvantages discussed above in the circumstance where one desires a more robust and comprehensive system. See Pet. Reply 23 (noting three advantages of the combination— (1) “allow[ing] Szrek’s system to use ‘a centralized system for activating lottery tickets from different retailers and different locations,’” (2) “allow[ing] support for different game providers, such as different lottery companies,” “reduc[ing] implementation costs,” and (3) “allow[ing] Szrek’s system to ‘communicate with individual card” slip op. at 37

    Patent outcomesUS 11,488,451 unpatentable
    Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 11,488,451
  • PTAB · Feb 6, 2025 · IPR2023-01235 · APJ Bart A Gerstenblith · IPR · Final written decision

    Claims 1–6 were not shown unpatentable under either obviousness ground because Szrek did not disclose a pre-printed lottery ticket without lottery numbers associated at customer purchase.

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

      “real party in interest. Prelim. Resp. 1–2, 32–34. In the Institution Decision, we stated: To the extent Patent Owner seeks to pursue its argument that Linq3 is a real party of interest to Petitioner, even though no time bar under 35 U.S.C. § 315(b) has been asserted, Patent Owner may raise the issue of real party in interest again in its Patent Owner Response and the parties may brief and argue the issue during trial. Inst. Dec. 11. In its Patent Owner Response, Patent Owner did not raise the issue of challenging Petitioner’s identified real party in interest. See generally PO Resp. Thus, we need not address this issue further because we find that Patent Owner has waived any challenge to Petitioner’s identification of the real parties in interest in this proceeding. See Paper 12 (Scheduling Order), 9 (“Patent Owner is cautioned that any arguments not raised in the response may be deemed waived.”).” slip op. at 5

    • Skill levelSkill level petitioner adoptedDecided for patent owner

      “B. Level of Ordinary Skill in the Art Petitioner proposes that the level of ordinary skill in the art is an artisan with a working knowledge of POS activation systems and lottery systems that was gained through a mixture of training and work experience in the relevant field such as (i) having a Bachelor’s degree in computer science, computer communications, electrical engineering, or equivalent degree, coupled with at least three years of work experience; (ii) having a Master’s degree in computer science, computer communications, or electrical engineering, but having less work experience; or (iii) having no formal degree, but having experience in the relevant field of at least six years of work experience. Pet. 2–3 (citing Ex. 1003 ¶ 13).5 Patent Owner states that, “[f]or the purpose of this proceeding, Patent Owner adopts the Petition’s proposed definition of the level of ordinary skill in the art.” PO Resp. 19. 5 Petitioner proposes the same level of ordinary skill in the art that the Board adopted in PGR2020-00084. Pet. 2–3 (citing Ex. 1008, 11). We find that the parties’ agreed-upon level of ordinary skill in the art is consistent with the level of ordinary skill in the art reflected by the ’135 patent and the prior art of record. See Inst. Dec. 14; 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). Therefore, we adopt the parties’ agreed-upon level of ordinary skill in the art, as articulated above, in our consideration of the issues presently before us.” slip op. at 12

    • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed patent owner constructionDisclaimer foundDecided for patent owner

      “Following the block quote from Yacenda, the applicant then stated, “[b]ased on the foregoing, Yacenda’s system is directly opposite of the instant claims, as the instant claims require a ‘pre-printed lottery ticket’ which has no lottery numbers associated with it at the time of customer purchase.’” Ex. 1002, 76. This statement is clear and unmistakable. It (1) specifically states that “the instant claims require” and (2) then states what the claims require—a “‘pre-printed lottery ticket’ which has no lottery numbers associated with it at the time of customer purchase.” We fail to see how the applicant could have been more clear in stating a requirement of the Challenged Claims. And, by doing so, the applicant narrowed the scope of what would otherwise be encompassed in the meaning of “pre-printed lottery ticket” and therefore what would otherwise be encompassed in the scope of the Challenged Claims—a lottery ticket which has lottery numbers associated with it at the time of customer purchase.” slip op. at 27

    • Expert testimonyPetitioner expert discountedDecided for patent owner

      “We do not find Mr. Hutton’s testimony particularly helpful. First, we have addressed the points raised by his testimony in our discussion above because they are largely the same as the arguments raised in Petitioner’s Reply. Second, we find his testimony entitled to very little weight because he applies an incorrect understanding of the caselaw, which mirrors Petitioner’s incorrect and arguably misleading quotations of the Federal Circuit’s decision in Quest. In particular, in paragraph 5, Mr. Hutton states the following as his understanding of the law as it applies to prosecution disclaimer: “I also understand that in order to disclaim embodiments within the specification, the statements should have some indication that the applicant intended to surrender embodiments from the specification.” Ex. 1038 ¶ 5 (emphasis added). This then leads Mr. Hutton to state: “[t]hus, in my opinion, a [person of ordinary skill in the art] would not view applicant’s statements as a disclaimer, because the applicant never stated that they intended to surrender multiple embodiments described in the specification.” Id. ¶ 13 (emphasis added). As we explained above in responding to a similar argument by Petitioner, the caselaw does not require an applicant to expressly state whether a disclaimer excludes particular embodiments of the subject specification when disclaiming claim scope during prosecution. See Quest, 924 F.3d at 1229. And, as noted above, counsel for Petitioner agreed that such a statement explicitly disclaiming particular embodiments is not required. Tr. 12:18–13:17. Third, although we have considered Mr. Hutton’s testimony, we find it “less significant than the intrinsic record in determining the legally operative meaning of” “pre-printed lottery ticket.” Phillips, 415 F.3d at 1317. In particular, we are cognizant of the Federal Circuit’s guidance that we “should discount any expert testimony that is clearly at odds with the claim construction mandated by . . . the prosecution history.” Id. at 1318 (internal quotation omitted). In this instance, for the reasons explained above, we find that Mr. Hutton’s testimony is clearly at odds with the applicant’s arguments during prosecution and that his testimony is based on a misunderstanding of what is required by the governing caselaw for prosecution history disclaimer.” slip op. at 43

    Patent outcomesUS 9,865,135 not shown unpatentable
    Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 9,865,135
  • Apple Inc. v. Fintiv, Inc.No claims unpatentable
    PTAB · May 23, 2024 · IPR2023-00399 · APJ Juliet Mitchell Dirba · IPR · Final written decision

    Claims 1–22 were not shown unpatentable under § 103 over Dill, Vadhri, and Akashika because Dill did not teach or render obvious the hardware SIM card and integration tier limitations.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “In the Institution Decision, we determined that a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering, computer science, or equivalent training, and approximately two years of work experience in software development with a basic knowledge of accounting” and “working knowledge of mobile payment systems and techniques,” as Petitioner proposes. Inst. Dec. 9 (quoting Pet. 3–4). We stated that “this definition generally comports with the level of skill necessary to understand and implement the teachings of the ’488 patent and the asserted prior art.” Id. (citing Ex. 1003 ¶ 22; Ex. 2001 ¶ 35).” slip op. at 10

    • Expert testimonyPetitioner expert discountedMixed

      “In addition, Petitioner’s reliance on Dr. Houh’s testimony (see Pet. 23–24) is unavailing. Although Dr. Houh agrees with the arguments in the Petition and includes quotes from the cited portions of Dill and Bykov (see Ex. 1002 ¶¶ 95–97), he provides no additional analysis or explanation beyond what was provided in the Petition. As a result, his testimony suffers the same deficiencies as the Petition. Also, we do not credit his conclusion that Dill includes the requisite disclosure (see id. ¶ 97) because he fails to provide sufficient supporting explanation or evidence (see 37 C.F.R. § 42.65(a)). Finally, we note that Petitioner misrepresents Dr. Shamos’s testimony by stating that Dr. Shamos “agrees that if a mobile device executes a mobile wallet over a cellular network, the mobile device has a SIM card for the mobile wallet.” Pet. Reply 22 (emphasis added) (citing Ex. 1022, 29:4–7, 40:9–10). In the cited testimony, Dr. Shamos agrees that mobile devices have SIM cards, but he does not address where a mobile wallet application would be installed. Ex. 1022, 29:4–7, 40:9–10. Thus, contrary to Petitioner’s argument, we determine that Dr. Shamos’s testimony does not support Petitioner’s position.” slip op. at 27

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

      “for the term “hardware SIM card” because the important points are undisputed. In particular, the parties agree that a “hardware SIM card” is a SIM card implemented in hardware rather than software. See Pet. Reply 9 (citing Ex. 1021 ¶ 36); Tr. 40:25–41:2 (Patent Owner’s counsel explaining that the language in its proposed construction was “to differentiate it from a software SIM card”); see also PO Resp. 16, 19 (asserting that the term refers to a specific type of hardware, namely a “chip” or a “smart card”) (citing Ex. 2003 ¶¶ 32–33). The parties also agree that an ordinarily skilled artisan would have known that a “SIM card” is a component in a mobile device involved in identifying and authenticating a user to a mobile network. See Tr. 30:23–31:3 (Petitioner’s counsel stating “a SIM card, just as known in the art . . . would allow the user to be able to access the mobile network” 10 Each page in Exhibit 2021 includes at least two page numbers. For clarity, we refer to the page number of the exhibit (shown in the bottom right corner), and we have adjusted Patent Owner’s citation accordingly. given “the user’s identification information on it”), 39:24–40:2 (Patent Owner’s counsel stating that “I think everyone is in agreement that the critical aspect of what makes a SIM card a SIM card is that it can authenticate a mobile device to a wireless network”). The evidence supports the parties’ understanding. The word “SIM” is an acronym for “subscriber identity module” (see, e.g., Ex. 1001, 6:58–67; Ex. 2021, 5), and the record shows that a SIM is a specific component in a mobile device that is involved in identifying and authenticating a user to a mobile network (see Ex. 2003 ¶¶ 30–31; see also e.g., Ex. 2021, 7 (stating that a SIM’s “primary function” is “to authenticate the subscriber to the network”); Ex. 2025, 3 (describing the SIM)).11 Consequently, we determine that an ordinarily skilled artisan would have understood a “hardware SIM card” to be a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. We do not need to further construe the term, or determine whether the additional requirements proposed by Patent Owner are appropriate, because Petitioner fails to show that the prior art teaches or suggests the claimed “hardware SIM card,” as explained below. See infra § II.D.2.a (analyzing the parties’ substantive contentions).” slip op. at 13

    • BurdenNot shown unpatentable

      “Petitioner has not shown, by a preponderance of the evidence, that Dill discloses “a mobile wallet application installed on a hardware SIM card,” as required by element 1.3B. See Pet. 23–24. In particular, even assuming that Dill teaches installing a mobile wallet application somewhere on a mobile device (see Pet. 23),14 Dill does not teach installing it on a hardware SIM card,15 as specifically required by the claim. Petitioner relies upon paragraph 106 of Dill (see Pet. 23), but that paragraph does not disclose this claim limitation (see Ex. 1005 ¶ 106). In relevant part, that paragraph of Dill simply states: 14 Patent Owner disagrees with this premise, arguing that Dill does not disclose a mobile device that includes a mobile wallet application. See PO Resp. 52–56. We need not resolve that dispute because, even assuming Petitioner’s premise (as we have done in this Decision), Petitioner still fails to show that the claims are unpatentable. 15 As noted above, a “hardware SIM card” is a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. See supra § II.C.1 (addressing meaning of term). It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software. Ex. 1005 ¶ 106 (emphases added). This teaches storing instructions on “other types of machine-readable mediums,” but it fails to teach storing instructions on a hardware SIM card, much less storing Dill’s mobile wallet application there. In short, Dill is silent with respect to this issue, and silence is not disclosure. Notably, Petitioner does not contend (or show) that a mobile wallet application installed on a mobile device would necessarily be installed on a hardware SIM card. See Pet. 23–24; Ex. 1003 ¶¶ 95–97. Indeed, the record indicates that a mobile wallet application installed on a mobile device could instead be installed on a different component. See, e.g., Ex. 1001, 7:1–3, 9:33–35 (identifying device memory as alternate component); Ex. 2021, 5 (describing SIM as the “smaller of two computer chips inside a GSM mobile handset”); cf. Pet. Reply 9 (distinguishing between hardware SIM cards and software ones). Thus, Petitioner fails to show that this claim limitation is inherent in Dill. See PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1196 (Fed. Cir. 2014) (explaining that inherency requires a showing that “the limitation at issue necessarily must be present”).” slip op. at 22

    Patent outcomesUS 9,208,488 not shown unpatentable
    Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 9,208,488
  • Medivis, Inc. v. Novarad Corp.Some claims unpatentable
    PTAB · Apr 12, 2024 · IPR2023-00045 · APJ Scott Raevsky · IPR · Final written decision

    Claims 1–4, 6, and 7 are unpatentable over Jones and/or Doo; claim 5 was not shown unpatentable because the obviousness grounds lacked adequate motivation to combine.

    RulingsFinal written decision
    • Skill levelOther

      “A. Level of Ordinary Skill in the Art” slip op. at 6

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther

      “2. “augmentation tag” Petitioner proposes the following construction for “augmentation tag”” slip op. at 21

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed

      “Accordingly, Petitioner persuades us that Jones discloses limitation” slip op. at 31

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

      “reasoning why the POSITA would be motivated to combine, ‘what was known in the art at the relevant time,’ whatever that may be.” PO Resp. 42. We agree. “[R]ejections on obviousness grounds cannot be sustained by mere conclusory statements; instead, there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). “Obviousness requires more than a mere showing that the prior art includes separate references covering each separate limitation in a claim under examination.” Unigene Labs., Inc. v. Apotex, Inc., 655 F.3d 1352, 1360 (Fed. Cir. 2011) (citation omitted). Rather, “obviousness concerns whether a skilled artisan not only could have made but would have been motivated to make the” slip op. at 53

    Patent outcomesUS 10,945,807 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR
    Patents in suitUS 10,945,807
  • Netflix, Inc. v. Divx, LLCNo claims unpatentable
    PTAB · Feb 22, 2024 · IPR2020-00558 · APJ Iftikhar Ahmed · IPR · Remand

    The majority determined claims 1–24 were not shown unpatentable over Chen, Lindahl, and Hurst; the dissent would have found them obvious.

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

      “We determine Patent Owner’s reading of the claim limitation is the better one. The limitation begins with the verb “locating,” and it therefore makes sense that the clause would recite what is located (i.e., encryption information) and where it is located (i.e., within the requested portions of the selected stream of protected video). In other words, it is reasonable that the second and third clauses of the limitation both modify the first clause (for example, as could perhaps be expressed through the use of commas as “locating encryption information, that identifies encrypted portions of frames of video, within the requested portions of the selected stream of protected video”).10 On the other hand, Petitioner’s reading of the limitation, 10 In general, we recognize that the use of commas to set off phrases in claim drafting is not consistent. We included commas above to illustrate Patent Owner’s understanding of the claim limitation. allowing only the second clause to modify the first, while not unreasonable, makes less sense. That is, the encrypted information identifies the encrypted portions of frames, which in turn are within the requested portions of the selected stream of protected video. Reading the claim in its entirety, the encrypted portions of frames would be understood to be located within the requested portions of the stream; it does not seem necessary for the claim to expressly recite that aspect. For example, the very next limitation— limitation [m] of claim 1—refers to “each encrypted portion of the frames of video” but does not expressly recite “within the requested portions of the selected stream.” Ex. 1001, 27:58–60. Thus, when limitation [l] recites “within the requested portions of the selected stream,” it seems more likely that the clause refers to where that encrypted information is located rather than simply to indicate the obvious location of the encrypted portion of the frames of video. We therefore view Patent Owner’s reading of the claim language as the better one.” slip op. at 13

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

      “I am persuaded that the Petition demonstrates that one of ordinary skill in the art would have had a motivation to combine Chen, Lindahl, and Hurst, as asserted by Petitioner. As the Federal Circuit found, the Petition pointed to and relied upon the portions in Chen describing pre-Chen art, without scalability or FEC features that were part of what Chen describes as aspects of its own inventive system. Netflix, slip op. at 9–10 (citing Pet. 17– 19, 69–70). I agree with Petitioner that “Chen-924 teaches several embodiments that adaptively stream alternative representations of a video using partially encrypted container files.” Pet. 20 (citing Ex. 1010, 14:41– 15:60). I determine that Chen-924 provides support for the rationale provided in the Petition, and that one of ordinary skill in the art would have been motivated to combine Chen and Lindahl in view of the disclosure of Chen-924. As discussed above, the Petition does not rely solely on privacy concerns and improvements to efficiency as its motivation to combine the references. See Pet. 18–19 (specifying piracy concerns, improvements to the efficiency of adaptive streaming, optimization of the balance between bitrate and bandwidth, and improvements to the end-user experience with fast startup and seek). With respect to whether one of ordinary skill in the art would have” slip op. at 52

    • Strike new argumentNew argument disregardedDecided for petitioner

      “I agree with Petitioner that Patent Owner’s Remand Brief, specifically pages 1–7, attempt to address aspects of claim 1 for the first time on remand. I also agree that Patent Owner’s arguments attempt to recharacterize limitations [j] and [k] to raise issues that Patent Owner did not raise previously, in contravention of our Order that issues raised needed support from “where those issues were raised in previous briefings by the parties.” Paper 56, 2. I have addressed whether scalability and FEC are integral to how Chen operates above, as well as whether the Petition relies on those aspects, supra. The questions about how Chen operates and what portions of Chen are asserted in the ground of unpatentability were previously raised, but now are being considered or reconsidered, based on the Federal Circuit’s decision. In Patent Owner’s Remand Brief, pages 1–7, the citations to argument previously raised do not support the arguments now presented by Patent Owner on remand. As such, I determine Patent Owner’s new arguments fall outside the scope of remand, and I dismiss these arguments seeking to distinguish limitations [j] and [k] from the cited prior art combination.24” slip op. at 62

    • ExcludeMotion to exclude, grantedMixed

      “7 Patent Owner’s Brief on Remand recognizes that there are two arguments Patent Owner raised in its Patent Owner Response that were not addressed in the Final Written Decision. See PO Remand Br. 1 (citing PO Resp. 24–37 (the construction of “locating encrypted information . . . within requested portions”), 38–58 (referring to Patent Owner’s “common keys” argument)). 8 The Final Decision also addressed Petitioner’s Motion to Exclude (Paper 42). See Final Dec. 28–37 (granting-in-part, denying-in-part, and dismissing-in-part Petitioner’s Motion). Our determinations on that Motion were part of Petitioner’s appeal to the Federal Circuit. See Paper 52. Because the Federal Circuit did not address this aspect of the Final Written Decision and the Federal Circuit’s decision does not impact our previous rulings on the Motion, we maintain those rulings here. Additionally, on remand, Petitioner requested authorization to file a motion for sanctions, which we held in abeyance until the parties’ briefing on remand was complete. See Ex. 3003, 1. Petitioner requests sanctions because of the impropriety of Patent Owner’s remand brief, including new claim construction arguments for limitations [1j] and [1k], and prejudice to Petitioner. Id. at 3, 5. Although we reserved further consideration of Petitioner’s request, we expanded both the time and pages allowed for Petitioner’s responsive brief, and also allowed Petitioner to address any related issues in its responsive brief. Id. at 1. Having considered the parties’ briefing on remand, and given that we do not reach the claim construction arguments that Petitioner objected to in its request for authorization to file a motion for sanctions, we deny Petitioner’s request.” slip op. at 5

    Patent outcomesUS 10,225,588 not shown unpatentable
    Claim construction§ 103 obviousnesscites KSR · Graham
    Patents in suitUS 10,225,588
  • PTAB · May 10, 2023 · IPR2022-00076 · APJ Juliet Mitchell Dirba · IPR · Final written decision

    Claims 1 and 8–20 are unpatentable as obvious; claims 2–7 were not shown unpatentable because the petitioner did not establish motivation to combine for their error-processing limitations.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “Petitioner asserts that the level of ordinary skill in the art corresponds to “a bachelor’s degree in electrical engineering, computer science, computer engineering, or equivalent field” and “two years of prior experience with image capturing/scanning technology, involving transferring and processing of image data to and at a server.” Pet. 14 (citing Ex. 1002 ¶ 45). Petitioner further asserts that “[l]ess work experience may be compensated by a higher level of education and vice versa.” Id. For purposes of the Institution Decision, we adopted Petitioner’s proposal (Inst. Dec. 16), and neither party alleges that a different level of ordinary skill should be applied in this proceeding (see PO Resp. 5; Pet. Reply). In this Decision, we again adopt the level of ordinary skill proposed by Petitioner. We are satisfied that it generally comports with the level of and the asserted prior art. Accord Inst. Dec. 15–16.” slip op. at 11

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

      “In the Petition, Petitioner states that it is unnecessary to construe any claim terms or phrases (Pet. 12–14), but for two phrases in claim 1, Petitioner specifically argues that the prior art teaches or suggests the phrase under each of two alternate meanings (id. at 34–35, 37). In the Institution Decision, we agreed with Petitioner’s primary understanding of these phrases and, as a result, did not reach the alternative contentions. Inst. Dec. 33 n.18, 38 n.21. At trial, Patent Owner states that claim construction is unnecessary to resolve the issues disputed in this proceeding. PO Resp. 6; Tr. 46:4–16. Petitioner agrees, but contends that Patent Owner’s arguments regarding dependent claim 3 are premised on a narrowing construction of one of its terms. Tr. 15:4–16:2. Patent Owner contends that the plain and ordinary meaning of the terms in that claim should apply. Id. at 46:12–16. We agree that it is not necessary to expressly construe any claim terms or phrases in this proceeding. See Nidec Motor Corp. v. Zhongshan Broad need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 12

    • BurdenNot shown unpatentable

      “motivated to add error processing to Garcia’s mobile phone so that it could address errors before transmitting the check image in order “to avoid wasting communications resources and adding delays.” Pet. 42. But, Petitioner does not support this rationale with a persuasive explanation or evidence. Indeed, we assume that Petitioner’s theory is that the error checking at the mobile device would have conserved bandwidth and reduced delay because it would have allowed the mobile device to identify some unsuitable images before they were sent to the payee bank; however, the Petition does not actually include an explanation to this effect. Rather, it simply states that an ordinary artisan would have known that mobile telephone networks (such as that used by Garcia) “are bandwidth and resource-constrained, and that communications over such networks takes time.” Id.; see also Ex. 1002 ¶ 115. However, all networks have bandwidth and resource constraints, and all communications take time, and neither the Petition nor Dr. Mowry explain why these considerations would have been relevant to an ordinary artisan implementing Garcia. Indeed, the Petition next asserts that “Byrne provides the requisite solution to this problem” (Pet. 42), but neither the Petition nor Dr. Mowry identify any problem. For example, Dr. Mowry does not testify that an ordinary artisan would have expected Garcia’s system to consume excessive bandwidth or incur for claim 2). In addition, Petitioner recognizes that the verification process is performed by the payee bank in Garcia, yet does not address the fact that its proposal would apparently shift a portion of the verification process to the mobile phone. See Pet. 40–44. Dr. Mowry’s trial testimony casts further doubt on Petitioner’s rationale for this claim. Dr. Mowry testifies that conserving bandwidth would “potentially” have been one of the goals of an ordinary artisan “depend[ing] on how precious their resource is.” Ex. 2020, 68:12–24. But Dr. Mowry “wouldn’t necessarily characterize [Garcia] as bandwidth intensive.” Id. at 76:13–23. In addition, he disagreed that “in the Garcia system, the motivation would have been to shift it to the client side for the verification,” noting simply that “[t]here are tradeoffs” associated with doing the verification processing on either the client or the server. Id. at 241:22– 242:13. Petitioner attempts to limit the impact of Dr. Mowry’s answers (Pet. Reply 16); however, the fact remains that Petitioner has the burden of proof, and it does not identify persuasive evidence to support its contention. Petitioner’s Reply asserts that these considerations were “particularly important in 2006, when 3G bandwidth was at a premium” (id. at 22 (citing Ex. 1029 ¶ 49)), but neither Petitioner nor Dr. Mowry provide analysis or evidence to support this conclusory assertion. Moreover, the Petition also fails to address whether the proposed combination would have, in fact, conserved communications resources or reduced delays. In Petitioner’s proposed combination, Byrne’s thin client application would be downloaded to Garcia’s mobile phone at each use (which would require communication resources and incur latency), but the Petition fails to address whether the net result of the proposed combination 148:1 (Dr. Mowry agreeing that the impact of downloading the thin client is not discussed in his report). Moreover, Garcia touts the “speed” of its process, stating that its “immediate processing . . . allows the immediate availability in the user’s account” (Ex. 1003, 7:18–8:3), which indicates that an ordinary artisan would not have perceived a problematic delay in Garcia’s system. Petitioner’s attempt to shift the burden to Patent Owner to determine whether or not its purported benefits would be realized (see Pet. Reply 17) is unavailing. In its Reply, Petitioner cites testimony from Dr. Mowry (see Ex. 1029 ¶ 37), but it simply compares the size of a compressed image with the size of a “large” application. This evidence does not outweigh the other evidence above, and it was submitted too late to remedy the Petition. See supra § II.A.; see also Trial Practice Guide 73 (explaining that a petitioner “may not submit new evidence or argument in reply that it could have presented earlier, e.g. to make out a prima facie case of unpatentability”). Finally, on this record, we are also not persuaded by Petitioner’s” slip op. at 60

    • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

      “would have been motivated to implement Garcia’s application by downloading, onto the mobile device, a thin client application, as disclosed by Byrne. See Pet. 19–25. Byrne touts the benefits of downloading a thin client rather than storing an application on a user’s device (Ex. 1004 ¶¶ 45– 46; see also id. ¶¶ 47–48), and Dr. Mowry testifies that an ordinary artisan would have understood downloading a thin client to be a well-known way of distributing software in the relevant time period and suited for mobile devices (Ex. 1002 ¶¶ 64–65, 70). In addition, Dr. Mowry testifies that a thin client improves security and ease of software maintenance. Id. ¶ 65 (citing Ex. 1004 ¶¶ 46–47); see also Ex. 1033, 140:11–141:2 (Dr. Creusere agreeing that thin clients “dramatically simplif[y]” software maintenance), 143:13–20 (agreeing that security is important for financial data); Ex. 1005 ¶¶ 20–21 (evidence that the general background knowledge in the art identifies security as a concern for remote check deposit).14 In addition, we agree with Petitioner (see Pet. 21–22; Ex. 1002 ¶¶ 66, 72) that an ordinary artisan would have understood such an implementation to apply a known 14 Patent Owner’s argument that security and software maintenance would have instead weighed against the proposed combination (see, e.g., PO Sur-reply 9–10) is untimely because it was not advanced in the Response and is not fairly responsive to the Reply. See supra § II.A; Pet. Reply 15–16 (noting that the Response had not addressed these issues). Moreover, even if this argument had been properly raised, it would not be persuasive because Patent Owner does not identify persuasive evidence to support its position. See, e.g., Icon Health & Fitness, Inc. v. Strava, Inc., 849 F.3d 1034, 1043 (Fed. Cir. 2017) (“Attorney argument is not evidence.”). (Garcia’s mobile phone) with predictable results. We are also persuaded that a person of ordinary skill in the art would have been motivated to implement Garcia’s application such that the application provides a user-interface and controls the image capture device, as disclosed by Byrne. See, e.g., Pet. 22–23. Garcia suggests that the application should perform these functions (see Ex. 1003, 5:1–6:10, 9:19– 10:18), and we credit Dr. Mowry’s testimony that an ordinary artisan would find this desirable (see Ex. 1002 ¶¶ 65, 67). Moreover, the references lend themselves to the combination because Garcia and Byrne both describe remotely depositing a check via the Internet using software on a user’s device that opens an interactive session, and both perform substantially similar steps. See Pet. 22–23; Ex. 1003, 9:21–10:3, 10:10–18, 11:7–15; Ex. 1004 ¶¶ 41, 48, 174–175, 177–178. Finally, Dr. Mowry testifies that the ordinary artisan would have had a reasonable expectation of success in implementing the combination, and he provides supporting analysis and evidence. Ex. 1002 ¶¶ 68–72; see also Ex. 1029 ¶¶ 38–39. We credit this testimony from Dr. Mowry because it draws reasonable inferences and is supported by the cited evidence.” slip op. at 25

    Patent outcomesUS 10,769,598 mixed
    Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 10,769,598
  • Veeam Software Corp. v. Hybir Inc.Some claims unpatentable
    PTAB · Dec 2, 2021 · IPR2020-01038 · APJ John R Kenny · IPR · Final written decision

    Claims 30, 32, 33, 35, and 37–40 are unpatentable as obvious; claims 31, 34, and 36 were not shown unpatentable.

    RulingsFinal written decision
    • Skill levelSkill level board ownDecided for patent owner

      “E. Level of Skill in the Art To determine the level of an ordinarily skilled artisan, various factors” slip op. at 10

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

      “claim terms for construction at that stage of the proceeding, and we did not construe any claim terms expressly as none of the terms were in dispute. Inst. Dec. 22. In the briefing following institution, Patent Owner proposed a construction for the term “inventory,” see, e.g., PO Resp. 21–28, and it became clear that the parties dispute the meaning of the term. Accordingly, we address the parties’ proposed constructions for “inventory” and the arguments they present for those constructions.” slip op. at 13

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

      “As set forth above, we resolved those disputed issues in favor of Petitioner. For the portions of the preamble and limitations of claim 35 that are not recited in claim 30, we have reviewed Petitioner’s arguments and evidence for claim 35 and are persuaded that Field teaches or suggests the preamble and claim limitations. Pet. 25–28 (and the exhibits cited therein). Thus, we find that Field teaches or suggests all limitations of claim 35. Accordingly, we determine Petitioner has proven that claim 35 would have been obvious over Field.” slip op. at 55

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

      “metadata into its signature generating algorithm to create a more robust signature. Ex. 1005 ¶ 46. An ordinarily skilled artisan would have been motivated to use such an augmented signature generating algorithm in Field’s environment. Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40. Thus, an ordinarily skilled artisan would have modified Field’s cryptographic signature generating algorithm so it would compute a file’s signature using a file’s metadata. Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40. Accordingly, Field and Anderson disclose that “the cryptographic signature is also computed with the metadata.” Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40.” slip op. at 76

    Patent outcomesUS 8,051,043 mixed
    Claim construction§ 103 obviousnesscites Phillips
    Patents in suitUS 8,051,043
  • Veeam Software Corp. v. Hybir Inc.Some claims unpatentable
    PTAB · Dec 2, 2021 · IPR2020-01037 · APJ John R Kenny · IPR · Final written decision

    Claims 1, 2, 5, 6, 8–15, 18, 19, 21–29, and 34 are unpatentable as obvious over Field and Anderson; claims 3, 4, 7, 16, 17, and 20 were not shown unpatentable.

    RulingsFinal written decision
    • Skill levelSkill level board ownDecided for patent owner

      “regarding the level of ordinary skill in the art, and Petitioner does not address our preliminary finding in its Reply. Accordingly, we see no reason to disturb that finding, and, therefore, we maintain and reaffirm that one of ordinary skill in the art at the time of the invention would have had a Bachelor of Science degree in Computer Science, Computer Engineering, Electrical Engineering, Software Engineering, or an equivalent field, as well as at least three to five years of academic or industry experience in the fields of data storage, data backup, data restoration, data replication and deduplication, and/or data synchronization.” slip op. at 16

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

      “Accordingly, we find that the record does not support construing” slip op. at 32

    • Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner

      “away and (2) whether one of ordinary skill in the art would have been motivated to not transmit an inventory with multiple signatures due to a concern with backup efficiency. With respect to whether Field teaches away, Patent Owner’s argument is premised, in part, on a requirement derived from its proposed construction of “inventory”—that the claimed “inventory” must include additional data, such as filenames and directories. As discussed above, we do not agree with Patent Owner’s construction. Similar to Patent Owner’s earlier argument of a teaching away, Patent Owner fails to identify anything in Field that criticizes, discredits, or otherwise discourages one of ordinary skill in the art from creating an inventory, as properly construed. Accordingly, we do not find that Field teaches away from using or creating an inventory.” slip op. at 81

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

      “144, 202; Pet. Reply 20–21; Ex. 1024 ¶¶ 59–62. Accordingly, we determine that Petitioner has not proven that claims 3 and 16 would have been obvious over Field and Anderson. Ex. 2008 ¶¶ 129–130.” slip op. at 101

    Patent outcomesUS 8,051,043 mixed
    Claim construction§ 103 obviousnesscites Phillips
    Patents in suitUS 8,051,043
Page 1 of 4
← Previous1234Next →

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.