- PTAB · Apr 21, 2025 · IPR2024-01489 · APJ Barbara A Parvis · IPR · Institution
The Board instituted IPR on claims 1–30 on all asserted grounds, finding a reasonable likelihood that Cohen anticipates the challenged claims.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“To show anticipation under 35 U.S.C. § 102, each and every claim element, arranged as in the claim, must be found in a single prior art reference. Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359 (Fed. Cir. 2008); Verdegaal Bros., Inc. v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Identity of terminology is not required for a claim element to be met directly by the prior art. In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009); In re Bond, 910 F.2d 831, 832 (Fed. Cir. 1990) (citations omitted) (“[T]his is not an ‘ipsissimis verbis’ test.”). For anticipation, we take into account not only the specific teachings of the reference, but also the inferences which one skilled in the art would reasonably be expected to draw therefrom. In re Preda, 401 F.2d 825, 826 (CCPA 1968). B. Level of Ordinary Skill in the Art” slip op. at 13
- Parallel petitionsDecided for petitioner
“Wrinkl, Inc. v. Slack Technologies, LLC, No. 1:24-cv-00620 (D. Del. May 23, 2024). Pet. 1; Paper 4, 1. Patent Owner also states that a “second IPR was filed against the same patent in proceeding IPR2024-01490.” Paper 4, 1. Patent Owner does not argue that we should exercise discretion under 35 U.S.C. § 314(a) because Petitioner uses more than one petition to challenge the ’731 patent. challenges the alleged priority date of the ’731 patent (IPR2024-01489) (‘First Petition’) and the second petition assumes that the Patent Owner’s claimed priority date is valid, and addresses prior art references predating that priority date (IPR2024-01490) (‘Second Petition’).” Ex. 1019, 1. In accordance with the Consolidated Trial Practice Guide1 (“CTPG”), issued in November 2019, “there may be circumstances in which more than one petition may be necessary” including “when there is a dispute about priority date requiring arguments under multiple prior art references.” CTPG 59. Such is the case here. Patent Owner does not file any Preliminary Response or other paper disputing Petitioner’s use of two petitions to challenge the claims of the ’731 patent. Based on the record before us, we consider the merits of both petitions because Petitioner’s stated reasons for filing two petitions are consistent with the CTPG. See generally Ex. 1019 (citing CTPG, 59 (“the Board recognizes that there may be circumstances in which more than one petition may be necessary, including, for example, . . . when there is a dispute about priority date requiring arguments under multiple prior art references)). C. The ’731 Patent” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther
“reasonable likelihood that it would prevail on a ground of unpatentability. 35 U.S.C. § 314(a); Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3)) (“In an [inter partes review], the petitioner has the burden from the onset to show with particularity why the patent it challenges is unpatentable.”). Petitioner first must raise the issue of entitlement to a claimed priority date by “identifying, specifically, the features, claims, and ancestral application or applications allegedly lacking § 112 support for the claims based on the identified features.” Focal Therapeutics, Inc. v. Senorx, Inc., IPR2014-00116, Paper 8 at 9–10 (PTAB Apr. 22, 2014); Mission Integrated Techs., LLC v. Joshua Clemente, IPR2023-01285, Paper 16 at 18 (PTAB Feb. 23, 2024). Then, Patent Owner must make a sufficient showing of entitlement to earlier filing date(s), in a manner that is commensurate in scope with the specific points and contentions raised by the petitioner. See id.” slip op. at 11
- Skill levelSkill level petitioner adoptedOther
“two years of experience in the graphical user interface field” or, alternatively “a master’s degree in computer science (or similar discipline) and at least two years of similar experience.” Pet. 16 (citing Ex. 1003 ¶ 40). We find that “at least” in Petitioner’s formulation of the level of skill in the art is vague and open-ended. Otherwise, we preliminarily adopt Petitioner’s formulation of the level of skill in the art, which appears consistent with the specification and prior art presented. C. Claim Construction” slip op. at 14
Claim construction§ 102 anticipation§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 11,973,731 - Apple Inc. v. Paul PoniatowskiInstitutedPTAB · Oct 7, 2024 · IPR2024-00731 · APJ Jennifer S Bisk · IPR · Institution
The Board instituted review of claims 1–6, 8–13, 15–20, and 22–27 based on a reasonable likelihood that Wang, Dua, and Yong render them obvious.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Pursuant to 35 U.S.C. § 314(a), the Director may not authorize an inter partes review unless the information in the petition and preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons that follow, we institute an inter partes review as to claims 1–6, 8–13, 15–20, and 22–27 of the ’578 patent on the sole ground of unpatentability asserted in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“understanding of a person of ordinary skill in the art at the time of the invention. Graham v. John Deere Co., 383 U.S. 1, 17 (1966). For purposes of this proceeding, Petitioner argues a person of ordinary skill in the art at the time of the invention would have had “a bachelor’s degree in computer science, computer engineering, or equivalent with one to two years of experience in the field of mobile transactions.” Pet. 8 (citing Bederson Decl. ¶¶ 35–37). Petitioner adds that “[a]dditional education or experience might substitute for the above requirements.” Id. To the extent necessary, and for purposes of this Decision, we accept this assessment offered by Petitioner, as it is supported by Dr. Bederson’s testimony and appears consistent with the ’578 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“scanner, reader, or camera” that is aimed at a barcode or special code of a product, the price of which is then added to the retail bill. Pet. 10–11 (quoting Ex. 1001, 7:45–49, 9:5–11). According to Petitioner, the Specification does not elaborate further on the meaning of the term “information concerning prices of goods.” Id. at 11. Petitioner, thus, interprets the term to encompass scenarios in which price information is received directly or indirectly. Id. Petitioner notes that during prosecution of the ’578 patent, the Examiner rejected this limitation over prior art, stating that prior art “sends the scanned bar code information to the server,” which “then preferably returns a description of the item and information,” and “[t]his item description and price information is displayed on the telephone’s display.” Id. at 12 (quoting Ex. 1002, 231). According to Petitioner, this is an example of indirectly receiving information concerning the prices of goods as it comes from a queried server, not from the item itself. Id. Petitioner notes that Patent Owner never disputed, and in fact, made statements supporting that these actions were encompassed by the claim limitation. Id. (citing Ex. 1002, 214). We agree with Petitioner that nothing in the claim language or the Specification requires that the claimed optical input receive information concerning the prices of goods directly from the goods themselves. Thus, on this record, we preliminarily construe the term “receiving information concerning the prices of goods” to encompass receiving pricing information from a server.” slip op. at 9
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“In an inter partes review, the burden is on the petitioner to show a reasonable likelihood that it would prevail on a ground of unpatentability. 35 U.S.C. § 314(a). With respect to entitlement to any earlier effective filing date, however, a patent owner is not presumed to be entitled to the earlier filing dates of ancestral applications that do not share the same disclosure, such as in a continuation-in-part situation. See PowerOasis, Inc. v. T–Mobile USA, Inc., 522 F.3d 1299, 1305–06 (Fed.Cir.2008) (stating that once a defendant establishes that a reference is § 102(b) prior art, burden is on patent owner to come forward with evidence proving priority to an earlier filing date).” slip op. at 12
Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,270,578 - Sophos Ltd. / Sophos Inc. v. Open Text Inc.Institution deniedPTAB · Nov 29, 2023 · PGR2023-00031 · APJ Barbara A Parvis · PGR · Institution
The Board denied institution because Petitioner did not show that any challenged claim was more likely than not unpatentable over the asserted obviousness or indefiniteness grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“review under 35 U.S.C. § 324 and 37 C.F.R. § 42.4. A post-grant review may not be instituted “unless . . . the information presented in the petition . . . , if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324 (2018). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has not demonstrated that it is more likely than not that at least one of the claims challenged in the patent is unpatentable. Accordingly, we do not institute a post-grant review of the challenged claims of the ’869 patent.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Pet. 10 (citing Ex. 1004 ¶ 16). Patent Owner does not dispute Petitioner’s proposal. Prelim. Resp. 33. Considering the subject matter of the ’869 patent, the background technical field, and the asserted prior art, we agree with Petitioner’s proposed qualifications for an ordinary level of skill, except we decline to adopt “at least” as that language is vague and open-ended. Otherwise, Petitioner’s proposed definition is consistent with the level of skill reflected in the Specification of the ’869 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). Accordingly, for purposes of this Decision, and based on the current record, except as noted above, we adopt Petitioner’s assessment of the level of skill for one of ordinary skill in the art.” slip op. at 13
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“We agree with Patent Owner that the claims are directed to the classification stage, as they require extracting “a plurality of static data points” from an executable file and “generating a feature vector from [that] plurality of static data points using a classifier” (emphasis added). The claims also recite that the classifier has been “trained to classify” (emphasis added). Further, the claims recite that “features of the feature vector” are selectively turned on or off, indicating that the feature vector has been generated. We also agree with Patent Owner that Petitioner has not shown that Ideses teaches or suggests a classification method in which one or more features of a feature vector generated from a plurality of static data points are selectively turned on or off based on the value of the static data point. As explained in the summary of Ideses above, Ideses describes “methods and systems for generating classifiers” (Ex. 1005 ¶ 2) in which “extracted features [may be] identified for pruning to generate the group of classifying features,” and “the selection [may be] based on identifying a classification effectiveness rank for each of the features of the training software applications” or “based on identifying resource requirements for each of the features of the training software applications.” See id. ¶¶ 98, 99. “[T]he group of classifying features [may be] selected based on the significance of the extracted features,” such that “[s]ignificant features, such as those that have a large effect on the classification outcomes, may be retained” and “[i]nsignificant features, such as those that have a small, negligible or no effect on classification outcome may be pruned.” Id. ¶¶ 101, 106. Petitioner argues that “Ideses explains that in the method depicted in Figure 1, ‘[t]he full feature list is optionally selectively pruned,’ i.e., ‘selectively turned off’ as required by [1.e],” and “[f]urther, ‘each feature of the group is selected from-the-ground-up; added to the group as opposed to removed from or retained within a larger group,’ i.e., ‘selectively turned on’ as required by [1.e].” Pet. 33 (citing Ex. 1005 ¶ 71). Petitioner also argues element 1.e is taught by Ideses’s “approaches to pruning insignificant features,” which Petitioner argues are “to selectively includ[e]/exclud[e] features based on whether a feature coefficient ‘is within a predetermined range’ as required” by element 1.e. Id. at 34 (citing, e.g., Ex. 1005 ¶¶ 107, 109–110). But all of the selection and pruning described in Ideses concerns the” slip op. at 22
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“We agree with Patent Owner that the claims are directed to the classification stage, as they require extracting “a plurality of static data points” from an executable file and “generating a feature vector from [that] plurality of static data points using a classifier” (emphasis added). The claims also recite that the classifier has been “trained to classify” (emphasis added). Further, the claims recite that “features of the feature vector” are selectively turned on or off, indicating that the feature vector has been generated. We also agree with Patent Owner that Petitioner has not shown that Ideses teaches or suggests a classification method in which one or more features of a feature vector generated from a plurality of static data points are selectively turned on or off based on the value of the static data point. As explained in the summary of Ideses above, Ideses describes “methods and systems for generating classifiers” (Ex. 1005 ¶ 2) in which “extracted features [may be] identified for pruning to generate the group of classifying features,” and “the selection [may be] based on identifying a classification effectiveness rank for each of the features of the training software applications” or “based on identifying resource requirements for each of the features of the training software applications.” See id. ¶¶ 98, 99. “[T]he group of classifying features [may be] selected based on the significance of the extracted features,” such that “[s]ignificant features, such as those that have a large effect on the classification outcomes, may be retained” and “[i]nsignificant features, such as those that have a small, negligible or no effect on classification outcome may be pruned.” Id. ¶¶ 101, 106. Petitioner argues that “Ideses explains that in the method depicted in Figure 1, ‘[t]he full feature list is optionally selectively pruned,’ i.e., ‘selectively turned off’ as required by [1.e],” and “[f]urther, ‘each feature of the group is selected from-the-ground-up; added to the group as opposed to removed from or retained within a larger group,’ i.e., ‘selectively turned on’ as required by [1.e].” Pet. 33 (citing Ex. 1005 ¶ 71). Petitioner also argues element 1.e is taught by Ideses’s “approaches to pruning insignificant features,” which Petitioner argues are “to selectively includ[e]/exclud[e] features based on whether a feature coefficient ‘is within a predetermined range’ as required” by element 1.e. Id. at 34 (citing, e.g., Ex. 1005 ¶¶ 107, 109–110). But all of the selection and pruning described in Ideses concerns the” slip op. at 22
§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · NautilusPatents in suitUS 11,409,869 - Cradlepoint, Inc. / Honeywell International, Inc. et al. v. 3g Licensing S.A.All claims unpatentablePTAB · Sep 12, 2022 · IPR2021-00584 · APJ Monica S Ullagaddi · IPR · Final written decision
Claims 16–19, 21, 22, 39, 40, and 42 are unpatentable under § 103: Meeting45 anticipates claims 16–19, 21, 22, and 39, and Meeting45 with Meeting45bis renders claims 40 and 42 obvious.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“In order to obtain the benefit of the filing date of an earlier application, 35 U.S.C. § 120 requires that the earlier application include a disclosure that complies with the written description requirement of 35 U.S.C. § 112. Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571–2 (Fed. Cir. 1997). To comply with the written description requirement, a specification “must describe the invention sufficiently to convey to a person of skill in the art that the patentee had possession of the claimed invention at the time of the application, i.e., that the patentee invented what is claimed.” Lizardtech, Inc. v. Earth Res. Mapping, Inc., 424 F.3d 1336, 1345 (Fed. Cir. 2005) (emphasis added). The written description requirement “guards against the inventor’s overreaching by insisting that he recount his invention in such detail that his future claims can be determined to be encompassed within his original creation.” Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1561 (Fed. Cir. 1991). “[O]ne skilled in the art, reading the original disclosure, must immediately discern the limitation at issue in the claims.” Purdue Pharma L.P. v. Faulding Inc., 230 F.3d 1320, 1323 (Fed. Cir. 2000) (emphasis added). “Entitlement to a filing date extends only to the subject matter that is disclosed; not to that which is obvious . . . Therefore the parent application must actually or inherently disclose the elements of the later-” slip op. at 23
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Disclaimer not foundDecided for petitioner
“We are not persuaded that the disclosures of the ’625 patent cited by Patent Owner “‘clearly set forth a definition of the disputed claim term’ other than its plain and ordinary meaning.” See Thorner v. Sony Comput. Fitness, Inc. v. Brunswick Corp., 288 F.3d 1359, 1366 (Fed. Cir. 2002)). “We depart from the plain and ordinary meaning of claim terms based on the specification in only two instances: lexicography and disavowal.” Hill-Rom Servs., Inc. v. Stryker Corp., 755 F.3d 1367, 1371 (Fed. Cir. 2014) (citing Thorner, 669 F.3d at 1365). “‘To act as its own lexicographer, a patentee must clearly set forth a definition of the disputed claim term other than its plain and ordinary meaning’ and must ‘clearly express an intent to redefine the term.’” Id. (quoting Thorner, 669 F.3d at 1365). “Disavowal requires that ‘the specification [or prosecution history] make[] clear that the invention does not include a particular feature,’ or is clearly limited to a particular form of the invention.” Id. at 1372 (alterations in original) (internal citations omitted).” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We determine that the usage and description of the term E-AGCH in documents accompanying the 3GPP TS 25.211 v6.2.0 (2004-09) standard along with at least one later version––3GPP TS 25.211 v6.7.0 cited by Patent Owner in its infringement complaint (see, e.g., Ex. 1017, 3)––are consistent and that E-AGCH would have been known and understood by a POSITA to carry the meaning set forth therein as of the filing date of the application underlying the ’625 patent, March 31, 2005.10 We further conclude that one of skill in the art would have understood that the patentee used that term in the ’625 patent in accordance with the 3GPP’s definition.” slip op. at 14
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“accessibility with respect to any of the cited references. See generally PO Resp. 17–18. For the reasons that follow, we find that Petitioner’s showing sufficiently demonstrates public availability and accessibility for Meeting45, Meeting39, and Meeting45bis prior to March 31, 2005. 1. Meeting45 Petitioner asserts that Meeting45 (Ex. 1004) “is a 3GPP change request document that was publicly available on the 3GPP FTP server no later than December 3, 2004.” Pet. 18 (citing Ex. 1021 ¶¶ 64, 77). In support of this assertion, Petitioner cites the Bishop Declaration, in which Mr. Bishop describes in detail how he searched for and found the Meeting45 document by navigating the 3GPP FTP website. Ex. 1021 ¶¶ 54–63. Based on this process, Mr. Bishop testifies that “by December 3, 2004, an interested POSITA using reasonable diligence could have located Meeting45 on the 3GPP website, downloaded the reference without providing any credentials, and disseminated the reference to others without restriction.” Id. ¶ 64. We have reviewed the relevant portions of Mr. Bishop’s Declaration and are persuaded that his testimony sufficiently demonstrates that Meeting45 was publicly available and accessible prior to March 31, 2005 (the earliest priority date to which the ’625 patent is entitled). See id. ¶¶ 54– 63; see also id. ¶¶ 55–57 (testimony as to availability and accessibility of attachment distributed via email and stored on an email list archive).” slip op. at 27
Patent outcomesUS 7,551,625 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 7,551,625 - PTAB · Jun 16, 2022 · IPR2022-00300 · APJ John D Hamann · IPR · Institution
The Board instituted IPR on claims 1–20 and 22 on all asserted grounds, finding a reasonable likelihood that at least one challenged claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsInstitution denied 325dDenied
“(1) whether the same or substantially the same art previously was presented to the Office or whether the same or substantially the same arguments previously were presented to the Office; and (2) if either condition of first part of the framework is satisfied, whether the petitioner has demonstrated that the Office erred in a manner material to the patentability of challenged claims.” slip op. at 7
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2018); see 37 C.F.R. § 42.108. Upon consideration of the papers, we conclude that the information presented shows that there is a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of at least one challenged claim of the ’570 patent.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field, and at least two years of experience in the research, design, development, and/or testing of touch and/or proximity sensors, human-machine interaction and interfaces, and related firmware and software, or the equivalent, with additional education substituting for experience and vice versa.” Pet. 5 (citing Ex. 1002 ¶ 46). Patent Owner does not identify a proposed level of skill in the art that one would have had at the time of the invention of the ’570 patent or identify any specific shortcoming in Petitioner’s formulation. See generally Prelim. Resp. For purposes of this Decision, and based on the current record, we adopt Petitioner’s assessment of the level of skill for one of ordinary skill in the art, except we decline to adopt “at least” as that language is vague and open-ended. Pet. 5. This assessment is consistent with the ’570 patent and the asserted prior art, and we apply it in our analysis below.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningOther
“same claim construction standard that would be used in a civil action under 35 U.S.C. § 282(b), following the standard articulated in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). 37 C.F.R. § 42.100(b). In applying such standard, claim terms are generally given their ordinary and customary meaning, as would be understood by a person of ordinary skill in the art, at the time of the invention and in the context of the entire patent disclosure. Phillips, 415 F.3d at 1312–13. “In determining the meaning of the disputed claim limitation, we look principally to the intrinsic evidence of record, examining the claim language itself, the written description, and the prosecution history, if in evidence.” DePuy Spine, Inc. v. Medtronic Sofamor Danek, Inc., 469 F.3d 1005, 1014 (Fed. Cir. 2006) (citing Phillips, 415 F.3d at 1312–17). The parties do not identify any claim terms for construction. Pet. 15; see generally Prelim. Resp. Thus, at this stage of the proceeding, we do not provide any express constructions, and we afford the claim terms their plain and ordinary meaning. See, e.g., 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)) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”).” slip op. at 12
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites Phillips · GrahamPatents in suitUS 7,952,570 - Satco Products, Inc. v. The Regents Of The University Of CaliforniaInstitution deniedPTAB · Nov 8, 2021 · IPR2021-00661 · APJ Steven M Amundson · IPR · Institution
The Board denied institution of review for claims 1 and 2 under § 314(a), finding the Fintiv factors weighed against review because of the advanced, overlapping ITC investigation.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Institution denied fintivDenied
“The Fintiv factors “relate to whether efficiency, fairness, and the merits support the exercise of authority to deny institution in view of an earlier trial date in the parallel proceeding.” Fintiv, IPR2020-00019, Paper 11 at 6. A stay of parallel litigation pending resolution of a Board proceeding “allays concerns about inefficiency and duplication of efforts.” Id. That the E.D.N.Y. case was stayed “at its earliest stage,” however, does not “allay[] concerns about inefficiency and duplication of efforts” in view of the 1220 investigation. Additionally, the E.D.N.Y. case was stayed “pending completion” of the 1220 investigation, not because of any Board proceeding. Ex. 3002, 1. With dates set in the 1220 investigation for the ALJ’s initial determination and the ITC’s final determination, a stay seems highly unlikely, especially with the initial determination date about a week away. Hence, factor (1) weighs against institution. See Fitbit, Inc. v. Koninklijke Philips N.V., IPR2020-00771, Paper 14 at 16–17 (PTAB Oct. 19, 2020).” slip op. at 18
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied
“to institute an inter partes review. We may institute an inter partes review only if “the information presented in the petition filed under section 311 and any response filed under section 313 shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2018). But we have discretion to deny a petition even when a petitioner satisfies the “reasonable likelihood” threshold standard for instituting trial. See, e.g., Cuozzo Speed Techs., LLC v. Lee, 136 S. Ct. 2131, 2140 (2016) (“[T]he agency’s decision to deny a petition is a matter committed to the Patent Office’s discretion.”). Based on the current record and for the reasons explained below, we exercise our discretion under 35 U.S.C. § 314(a) to deny institution of an inter partes review.” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not reached
“essentially the same argument about the ’557 patent’s effective filing date for its challenge based on Nakamura-959 and Nakamura-949 as for its invalidity defense based on insufficient written-description support for claim 1. See Pet. 7, 12–21, 37; Ex. 2004, 29–33; Ex. 2005, 245–48; Ex. 2014, 64–65, 70. As we understand the arguments, resolving the ’557 patent’s effective filing date does not require interpreting any part of § 1.57. See Pet. 12–21; Prelim. Resp. 29–31. Instead, the issue turns on whether the ’154 application supports claim 1 according to § 112’s first paragraph. See Pet. 12–21; Prelim. Resp. 29–31. Also, the challenges based on Tanda present a similar issue whether the ’447 provisional supports claim 1 according to § 112’s first paragraph. See Pet. 12–21, 61; Prelim. Resp. 29–31, 36–37. “[T]he test for sufficiency is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date.” Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). Under the circumstances here, the ITC can apply the test for sufficiency of disclosure to the ’154 application and the ’447 provisional just as well as the Board.” slip op. at 27
§ 112 disclosureDiscretionary denialPatents in suitUS 10,658,557 - Unified Patents Inc. v. KCG Technologies LLCAll claims unpatentablePTAB · Feb 10, 2021 · IPR2019-01536 · APJ Kalyan K Deshpande · IPR · Final written decision
Claims 1–13 are unpatentable as obvious; the revised motion to amend is denied because proposed substitute claims 14–26 are unpatentable as obvious or indefinite.
RulingsFinal written decision- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied
“We agree with Petitioner. Proposed substitute claim 24 recites “the handheld device” without antecedent basis. This lack of antecedent basis renders proposed substitute claim 24 indefinite, as we noted in our Preliminary Guidance. Pet. Opp. to RMTA 25; Prelim. Guidance 8 (“Proposed substitute claim 24 also recites ‘the handheld device’ and also suffers from the lack of antecedent basis). Despite having the opportunity to correct its error and amend proposed substitute dependent claim 24 when independent claim 14 was amended to remove the recitation of “a handheld device,” Patent Owner did not do so in its Contingent Revised Motion to Amend. RMTA 31. Proposed substitute claim 24 is indefinite because the claim “fails to inform, with reasonable certainty, those skilled in the art about the scope of the invention.” Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898, 901 (2014); see USPTO Memorandum on the Approach to Indefiniteness Under 35 U.S.C. § 112 in AIA Post-Grant Proceedings (Jan. 6, 2021)13; see MPEP 2173.05(e) (9th ed., Rev. 08.2017, June 2020). This is because “the handheld device” is only recited in proposed substitute claim 24, and the proposed substitute claim fails to inform one skilled in the art the scope of invention related to synchronizing “data on the handheld device” “in the virtual smart phone.” Because proposed substitute claims 25 and 26 depend from proposed substitute claim 24, we similarly agree with Petitioner that claims 25 and 26 also are indefinite for lacking an antecedent basis for the term “handheld device.” Pet. Opp. to RMTA 25. Accordingly, we determine Petitioner has demonstrated by a preponderance of the evidence that proposed substitute claims 24–26 are unpatentable under 35 U.S.C. § 112 as indefinite.” slip op. at 40
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner
“Whether to treat a preamble term as a claim limitation is determined on the facts of each case in light of the claim as a whole and the invention described in the patent.” Am. Med. Sys., Inc. v. Biolitec, Inc., 618 F.3d 1354, 1358 (Fed. Cir. 2010) (quoting Storage Tech. Corp. v. Cisco Sys., Inc., 329 F.3d 823, 831 (Fed. Cir. 2003) (internal quotation marks omitted). “Absent clear reliance on the preamble in the prosecution history, or in situations where it is necessary to provide antecedent basis for the body of the claim, the preamble generally is not limiting.” Symantec Corp. v. Computer Assoc. Int’l, Inc., 522 F.3d 1279, 1288 (Fed. Cir. 2008) (internal quotation marks omitted). When the limitations in the body of the claim rely upon or derive essential structure from the preamble, then the preamble acts as a necessary component of the claimed invention and is limiting. See Eaton Corp. v. Rockwell Int’l Corp., 323 F.3d 1332, 1339 (Fed. Cir. 2003). A claim preamble also is limiting if the preamble is “necessary to give life, meaning, and vitality” to the claim. Pitney Bowes, Inc., 182 F.3d at 1305. We disagree with Patent Owner. Specifically, we do not agree that limitations in the body of the claims require the preamble to serve as an antecedent basis nor do they derive essential structure from the preamble. Rather, all of the elements recited in the body of claim 1 comprise a “virtual smart phone.” That is, we do not discern, and Patent Owner fails to persuasively point us to, any structure imparted by the preamble’s recitation of a “virtual smart phone.” See Pet. Reply 1–2. We similarly do not agree that the without the term “virtual smart phone” there would be no understanding of the “emulating” or “handheld device” limitations. Rather, the recited “software application executing on the processor” limitation provides the structure and meaning for the “emulating” of the “handheld device” features. Furthermore, we agree with the Petitioner that there is no evidence in the record that the prosecution history requires that the preamble is limiting, and the claims were distinguished during prosecution based on the recitation of a “virtual” smart phone. Id. at 2–3. Accordingly, we do not agree with Patent Owner that the preamble is limiting. slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“on the process to . . . emulate features of a handheld device.” Ex. 1001, 12:58–60 (emphasis added). Patent Owner argues that the term “‘emulate’ has a meaning in the art that is common and understood to mean ‘to imitate.’” PO Resp. 18. Patent Owner provides a dictionary definition to support its contention. Ex. 2004 (defining “emulate” as “to imitate in an effort to equal or surpass”). Patent Owner contends the use of “emulate” in claim 1 comports with its commonly understood meaning as “to imitate,” as does the use of the term “emulate” in the written description. Pet. 18–20 (citing Ex. 1001, 1:66–2:3, 2:6–3:5, 12:54–13:2 (claim 1)). Petitioner argues that the term “emulate” should be given its plain and ordinary meaning and does not contest Patent Owner’s construction of the term “emulate” as “to imitate.” Pet. 6–7; Pet. Reply 7. Petitioner, however, contests Patent Owner’s application of that construction to the asserted prior art. Pet. Reply 4–7 (citing Ex. 1034 ¶¶ 24–26). Petitioner specifically argues that Patent Owner implies that “(1) the imitation must be an exact duplicate in display and manner of input . . . or (2) the imitation relates only to the display and touch screen aspects.” Pet. Reply 4–5. In support of its position that Patent Owner’s interpretation of “to imitate” improperly narrows the meaning of “emulate,” Petitioner contends the written description discloses “less than full replication as emulation” and “controlling the handheld device th[r]ough control of a projected image using a variety of control input mechanisms provides emulation.” Pet. Reply 5–6 (citing Ex. 1001, 2:2–5, 3:57–61, 4:63–66, 6:24–42). Petitioner also notes that the dictionary definition Patent Owner proffered indicates that an exact duplication is not required. Pet. Reply 7 (“The complete definition of emulate [as] ‘to imitate in an effort to equal or surpass.’ Ex. 1004, 3”). We conclude that a preponderance of evidence supports the construction of the term “emulate” to mean “to imitate,” without any further restriction such as exact duplication or only display or touch screen aspects. Accordingly, we construe the term “emulate” as “to imitate.”” slip op. at 9
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts that a person of ordinary skill in the art at or before the priority date of the ’955 patent “would have had a bachelor’s degree in electrical engineering, computer science, computer engineering, physics, or a related subject, and two to three years of work experience in the field of automotive information systems.” Pet. 6 (citing Ex. 1002 ¶¶ 38–39); Ex. 1034 ¶ 14 (Petitioner’s expert reiterating the same level of ordinary skill in the art). Patent Owner does not propose an ordinary level of skill in the art. We agree with and adopt the level of ordinary skill in the art as articulated by Petitioner.” slip op. at 10
Patent outcomesUS 9,671,955 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 9,671,955 - Amazon.Com, Inc. / Amazon Digital Services, Inc. et al. v. Uniloc Luxembourg S.A.Some claims unpatentablePTAB · Aug 1, 2018 · IPR2017-00948 · APJ David C Mckone · IPR · Final written decision
Claims 1–8, 18–22, and 25 are unpatentable; claims 9–17, 23, and 24 are not unpatentable; substitute claims 26–28 are denied.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“The “verify” limitation of claim 1 expressly recites a check based “at least in part on a device identity.” The specification describes such a check as occurring at steps 15 and 16, not step 13. Steps 15 and 16 check whether the device identity is on record and, in response to that check, allow a digital product to be used on a device (steps 17, 18) or start a process to authorize the device. Id. at 5:1–9, 5:13–18. Although steps 15 and 16 are not expressly described as a verification of validity, steps 15 and 16, not step 13, logically track and most closely align with the language of claim 1’s “verify” and “in response to” limitations. Thus, the specification supports Petitioner’s view that the “verify” limitation can encompass checking whether unique device information is reflected in a database as authorized for a license.” slip op. at 12
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner
“claim 1 is limiting, with Patent Owner arguing that it is and Petitioner arguing that it is not. Id. at 12–13. Patent Owner now argues that “[t]he preambles [of claims 1 and 22] expressly state that the claimed system and method are both directed to ‘adjusting’ the license in terms of its allowed copy count, which the preambles expressly define.” PO Resp. 9. We explained in the Institution Decision, however, that even if the preamble is limiting (e.g., by virtue of it providing antecedent basis (“at least one allowed copy count”) for “set the allowed copy count”), the language “[a] system for adjusting a license for a digital product over time” constitutes a 2 The preamble of claim 25 is not similar to that of claims 1 and 22, and Patent Owner does not propose an “adjusting” limitation for the language “in response to the device identity not being on the record, set the allowed copy count to a first upper limit for a first time period after an initial authorization of the digital product,” as recited in claim 25. statement of intended purpose and does not purport to modify any particular claim language, such as “set the allowed copy count.” Dec. 13–14. Patent Owner argues that our preliminary construction would vitiate the purpose of the preamble language and that, instead, “the claim limitations must be understood in light of the ‘adjusting’ context introduced in the preamble.” PO Resp. 9. However, “the mere fact that a structural term in the preamble is part of the claim does not mean that the preamble’s statement of purpose or other description is also part of the claim.” Marrin v. Griffin, 599 F.3d 1290, 1295 (Fed. Cir. 2010). Rather, the Federal Circuit has held that “a preamble is not limiting ‘where a patentee defines a structurally complete invention in the claim body and uses the preamble only to state a purpose or intended use for the invention.’” Catalina Mktg. Int’l, Inc. v. Coolsavings.com, Inc., 289 F.3d 801, 808 (Fed. Cir. 2002) (quoting Rowe v. Dror, 112 F.3d 473, 478 (Fed. Cir. 1997)). Thus, an intended purpose set forth in a claim preamble and the context that purpose might provide, without more, are not limiting. Moreover, as Petitioner points out, “the claimed invention could be used to adjust an allowed device limit, at least to a higher limit, thereby satisfying the intended purpose of the invention.” Reply 4.” slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“On the complete record, we find that DeMello’s authentication, which checks a Passport ID and machine ID against stored records to authenticate a device, discloses executable code for the processor to “verify that a license data associated with the digital product is valid based at least in part on a device identity generated by sampling physical parameters of the given device,” as recited in claim 1 and similarly recited in claim 22.” slip op. at 29
- Obviousness (§103) › KSR rationalesUnpatentableNot shown unpatentableMixed
“The Federal Circuit has cautioned that “references to ‘common sense’—whether to supply a motivation to combine or a missing limitation—cannot be used as a wholesale substitute for reasoned analysis and evidentiary support, especially when dealing with a limitation missing from the prior art references specified.” Arendi S.A.R.L. v. Apple Inc., 832 F.3d 1355, 1362 (Fed. Cir. 2016). That is not the case here. As explained above, both the ’960 patent and DeMello describe precise numbers of days as arbitrary and that their respective inventions contemplate other numbers. We find that it would have been reasonable for the skilled artisan to have selected six days, as recited in claim 6, in light of DeMello’s disclosure.” slip op. at 45
Patent outcomesUS 8,566,960 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Alice · Bilski · Berkheimer · GrahamPatents in suitUS 8,566,960 - Wombat Security Technologies v. Phishme, Inc.Rehearing deniedPTAB · Jul 20, 2017 · PGR2017-00009 · APJ Jennifer S Bisk · PGR · Rehearing
The Board denied Wombat’s rehearing request, leaving institution of PGR denied because the petition did not show the patent was eligible for PGR.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“DISCUSSION The applicable standard for granting a request for rehearing is abuse of discretion. 37 C.F.R. § 42.71(c). The requirements of a request for rehearing are set forth in 37 C.F.R. § 42.71(d), which provides in relevant part: A party dissatisfied with a decision may file a single request for rehearing without prior authorization from the Board. The burden of showing a decision should be modified lies with the party challenging the decision. The request must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, or a reply.” slip op. at 3
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“sufficiently shown that the ’038 patent was eligible for post-grant review. Inst. Dec. 8–13. Specifically, we found deficient Petitioner’s contention that the challenged claims were not entitled to the benefit of the filing date of Application No. 13/785,252 (“the ’252 application”) to which the ’038 patent claims priority as a continuation-in-part. Inst. Dec. 8–13. This finding was based on the following deficiencies of the Petition: (1) the Petition did not discuss the relevant disclosure of the application to which the ’038 patent claims priority—Application No. 13/785,282 (“the ’252 application”)—as originally filed, citing instead to the ’940 patent, which issued from the ’252 application; (2) the Petition did not address the Examiner’s statements in the Notice of Allowability that “[t]he present application is being examined under the pre-AIA first to invent provisions”; and (3) Petitioner did not satisfy its burden to show that a person of ordinary skill in the art would not have understood the inventor to have possession of “providing feedback to the individual confirming that the identified email was a simulated phishing attack” (“the feedback limitation”). Id. For the third deficiency, we found the feedback limitation supported by at least paragraphs 5 and 18 of the ’252 application, which discuss training individuals who receive simulated phishing attacks such that users are better able to recognize and thwart a real phishing attack. Id. at 11–12.” slip op. at 2
- BurdenDecided for patent owner
“being recited expressly in the ’252 application it “satisf[ied] its burden to establish that it was more likely than not that the ’038 patent was not entitled to the filing date of the [’252 application].” Reh’g Req. 3. In Blue Calypso, LLC v. Groupon, Inc., however, the Federal Circuit explicitly found that identifying a limitation as not being recited expressly in the specification at issue was not enough to support a finding of lack of written description. 815 F.3d 1331, 1345 (Fed. Cir. 2016). The Federal Circuit explained that it was “troubled by the fact that the Board did not cite any evidence other than the fact that the terms were not present in the specification to support its finding,” concluding this placed “undue weight on the absence of the [exact] terms appearing in the specification.” Id. at 1345–46. Petitioner’s burden, therefore, is not established simply by pointing out that the ’252 application does not explicitly state the feedback limitation.” slip op. at 4
- Disclosure Requirements (§112) › Written description (Ariad)Not reached
“being recited expressly in the ’252 application it “satisf[ied] its burden to establish that it was more likely than not that the ’038 patent was not entitled to the filing date of the [’252 application].” Reh’g Req. 3. In Blue Calypso, LLC v. Groupon, Inc., however, the Federal Circuit explicitly found that identifying a limitation as not being recited expressly in the specification at issue was not enough to support a finding of lack of written description. 815 F.3d 1331, 1345 (Fed. Cir. 2016). The Federal Circuit explained that it was “troubled by the fact that the Board did not cite any evidence other than the fact that the terms were not present in the specification to support its finding,” concluding this placed “undue weight on the absence of the [exact] terms appearing in the specification.” Id. at 1345–46. Petitioner’s burden, therefore, is not established simply by pointing out that the ’252 application does not explicitly state the feedback limitation.” slip op. at 4
§ 112 disclosurePatents in suitUS 9,398,038 - Google, Inc. / Apple Inc. v. Smartflash LLCAll claims unpatentablePTAB · Nov 10, 2016 · CBM2015-00130 · APJ Jennifer S Bisk · CBM · Final written decision
Claims 3–10, 15–31, and 33 are unpatentable under § 101; claim 22 is also indefinite under § 112.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“We are persuaded that the challenged claims are drawn to a patent- ineligible abstract idea. Specifically, the challenged claims are directed to performing the fundamental economic practice of conditioning and controlling access to content. For example, claim 17 recites “code to evaluate the use status data using the use rules data to determine whether access is permitted to the stored data.” Ex. 1001, 27:1–15. As discussed above, the ’221 patent discusses addressing recording industry concerns of data pirates offering unauthorized access to widely available compressed audio recordings. Ex. 1001, 1:20–55. The Specification explains that these pirates obtain data either by unauthorized or legitimate means and then make the data available over the Internet without authorization. Id. The Specification further explains that once data has been published on the Internet, it is difficult to police access to and use of it by internet users who may not even realize that it is pirated. Id. The ’221 patent proposes to solve this problem by restricting access to data on a portable data carrier based upon payment validation. Id. at 1:59–2:4. The ’221 patent makes clear that the crux of the claimed subject matter is restricting access to stored data based on supplier-defined access rules and validation of payment. Id. at 1:59–2:15. Although the Specification refers to data piracy on the Internet, the challenged claims are not limited to the Internet. The underlying concept of the challenged claims, particularly when viewed in light of the Specification, is controlling access to content based upon payment as Petitioner contends. As discussed further below, this is a fundamental economic practice long in existence in commerce. See Bilski, 561 U.S. at 611.” slip op. at 10
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“recite only well-known, routine, and conventional computer components and activities, which is insufficient to establish an inventive concept.” Reply 6. Petitioner adds that “[t]he specification [of the ’221 patent] itself disclaims [the claimed hardware elements] as non-inventive.” Id. (citing Ex. 1001, 4:4–13, 11:28–29, 12:29–32, 13:35–38, 16:46–50, 18:7–17). We are persuaded that claims 3–10, 15–31, and 33 do not add an inventive concept sufficient to ensure that the patent in practice amounts to significantly more than a patent on the abstract idea itself. Alice, 134 S. Ct. at 2355; see also Accenture Global Servs., 728 F.3d at 1344 (holding claims directed to the abstract idea of “generating tasks [based on] rules . . . to be completed upon the occurrence of an event” to be unpatentable even when applied in a computer environment and within the insurance industry). Specifically, we agree with and adopt the rationale articulated in the Petition that the additional elements of the challenged claims are generic features of a computer that do not bring the challenged claims within § 101 patent eligibility. Pet. 49–82; Reply 6–19; ’126 Pet. 25–31; ’126 Reply 8–12.” slip op. at 15
- Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteUnpatentable
“Upon consideration of the entire record, we are persuaded sufficiently byPetitioner’s argument that a person of ordinary skill in the art would not know that the antecedent basis for “said use rules” refers back to the “use rules data” introduced in claim 17. Although lack of antecedent basis alone is insufficient to render a claim indefinite, here the lack of antecedent basis introduces ambiguity into the claim. It is unclear whether claim 22 should recite “use rules” or “said use rules data,” rather than “said use rules.” As indicated above, we have construed “use rules” and “use rules data” differently. Accordingly, we are persuaded that claim 22 is amenable to two plausible claim interpretations, and we determine that the phrase “said use rules” does not inform those skilled in the art about the scope of the invention with reasonable certainty and, therefore, is indefinite under 35 U.S.C § 112, ¶ 2. In re Packard, 751 F.3d 1307, 1311 (Fed. Cir. 2014) (affirming Board’s conclusion, in context of ex parte appeal, that claims were indefinite “on grounds that they ‘contain[ ] words or phrases whose meaning is unclear.’”).” slip op. at 32
- ExcludeMotion to exclude, deniedDenied
“Patent Owner has not articulated a persuasive reason for excluding Dr. Tygar’s Declaration. Because Exhibit 1002 relates to the underlying factual issues related to patent eligibility, we are not persuaded that it is irrelevant under FRE 401 and 402. It is within our discretion to determine the appropriate weight to be accorded to the evidence presented, including the weight accorded to expert opinion, based on the disclosure of the underlying facts or data upon which the opinion is based. Our discretion includes determining whether the expert testimony is the product of reliable principles and methods and whether the expert has reliably applied the principles and methods to the facts of the case. See FRE 702. Accordingly, we decline to exclude Exhibit 1002 in its entirety or any paragraph therein.” slip op. at 34
Patent outcomesUS 8,118,221 unpatentable§ 101 eligibility§ 112 disclosurecites Alice · Mayo · Bilski · EnfishPatents in suitUS 8,118,221
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.