- Askeladden, L.L.C. v. Ohva, Inc.All claims unpatentablePTAB · Mar 10, 2025 · IPR2023-00921 · APJ Amee A Shah · IPR · Final written decision
Claims 1–4 are unpatentable as obvious: claim 1 over Cho, Aaron, and Carpenter; claim 2 over those references and de Geer; claim 3 over Cho and Aaron; and claim 4 over Cho, Aaron, and de …
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“application are similar, as indicated by the redline comparison of two provided as Exhibit 1015. Critically, however, the “Summary of the Invention” sections are completely different. Id. at 2–4. The question is whether one of ordinary skill in the art would have understood with reasonable clarity, without the benefit of the Summary added for the ’286 patent/’674 application, that the ՚030 application describes a smart telephone that executes coded instructions to “convert the analog variable voltage audio signal received at the microphone port to the transaction data as digital data.”” slip op. at 43
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“Here, although the ’286 patent distinguishes “account data” from “transaction data” in the embodiment of Figure 11, the “transaction data” is submitted by the user to perform a series of banking transactions after manually entering a PIN code, whereas the “account data” is stored on the server, and the token information is accepted from the smart card’s 1001, 10:12–18, 10:30–35, 10:40–42, 11:21–22, 11:65–12:4, 12:22–36. Thus, the claimed “transaction data” that is “accepted . . . from an output interface of a transaction card” and “accepted . . . from a transaction card at an input interface of the card reader,” as recited in independent claims 1 and 3, comprises data stored on and read from a card, such as an ID number, password, authentication information, or session information, that can be used to facilitate a transaction. The evidence indicates that the claimed “transaction data” is distinct from the “transaction data B1-Bn” described in connection with the Figure 11 embodiment.” slip op. at 24
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“As discussed above in Section II.C, we construe the term “transaction data” as encompassing any data involved in a transaction, including account data. Again, we emphasize that claim 1 requires that the transaction data is accepted by the card reader from an output interface of the transaction card. Cho provides that card reader 230 reads a digital signal that includes account information of card 130 whereby the account information “may include at least one of an account number, a card expiration data, etc.” Ex. 1005, 5:54–58. We further agree with Petitioner that to the extent “transaction data” is for the purpose of conducting banking transactions, Cho’s account data of a credit card number and expiration date can perform that purpose. Patent Owner’s arguments that the transaction data cannot be “static” and that claim 1 requires “processing actual transaction-specific data” are not commensurate with the scope of the claim 1. The claim does not recite any limitations that the transaction data be dynamic or “not static,” nor does it recite any processing of the transaction data outside of using it to “facilitate transactions.” Petitioner has shown that Cho teaches the claimed transaction data.” slip op. at 55
Patent outcomesUS 9,679,286 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 9,679,286 - Askeladden, L.L.C. v. Ohva, Inc.Rehearing grantedPTAB · Mar 15, 2024 · IPR2023-00921 · APJ Amee A Shah · IPR · Rehearing
Granted petitioner’s rehearing request and instituted IPR of claims 1–4 on all asserted grounds, finding a reasonable likelihood of prevailing based on the preliminary construction of “transaction data.”
RulingsRehearing decision- RehearingRehearing, grantedGranted
“institute has the burden of showing the decision should be modified, and the request for rehearing must specifically identify all matters the party believes the Board misapprehended or overlooked and the place where each matter was previously addressed in its papers. 37 C.F.R. § 42.71(d). “When rehearing a decision on petition, a panel will review the decision for an abuse of discretion.” Id. § 42.71(c).” slip op. at 5
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“Although the ’286 patent distinguishes “account data” from “transaction data” in the embodiment of Figure 11, the “transaction data” is submitted by the user to perform a series of banking transactions after manually entering a PIN code, whereas the “account data” is stored on the server, and the token information is accepted from the smart card’s embedded token, i.e., the output interface of the transaction card. See Ex. 1001, 10:12–18, 10:30–35, 10:40–42, 11:21–22, 11:65–12:4, 12:22–36. Thus, the claimed “transaction data” that is “accepted . . . from an output interface of a transaction card” and “accepted . . . from a transaction card at an input interface of the card reader,” as recited in independent claims 1 and 3, comprises data stored on and read from a card, such as an ID number, password, authentication information, or session information, that can be used to facilitate a transaction. Such claimed “transaction data” is distinct from the “transaction data” described in connection with the Figure 11 embodiment. We therefore do not limit the claimed “transaction data” and instead preliminarily construe that term as encompassing any data involved in a transaction, including account data. As described above, the claimed transaction data must come from the output interface of a transaction card. Should either party believe that a different construction should apply in the instituted trial, it should explain the proposed construction, how the construction is supported by the record, and how the construction affects our unpatentability analysis.” slip op. at 8
- Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateInstituted
“The dispute relates to whether the ’030 application describes the claimed “smart telephone” accepting transaction data and executing coded instructions to convert the analog signal to digital data representing transaction data as digital data. See Pet. 14–15, 19–27. In Petitioner’s view, that term is supported only by language added to the “Brief Summary of the Invention” during prosecution of the application resulting in the ’286 patent. Id. at 17. In contrast, argues Petitioner, the corresponding section of the ’030 application instead describes transmitting sound to a PC, not a smart telephone. Id. at 19–26. Patent Owner submits that the ’030 application describes generating sounds from a smart phone and using a “key jack sound pass generator” to communicate sounds. Prelim. Resp. 16. Patent Owner contends that the claim language is supported by disclosure of receiving the audio signal at a microphone port and converting the signal to transaction data. Id. at 16–18. Patent Owner points also to description of direct communication between a “client device” and server. Id. at 19. On the present record, we find that Petitioner, at this stage in the proceeding, has shown sufficiently how it contends that the earliest possible effective filing date for claims 1–4 of the ’286 patent is March, 3, 2015, such that the Cho, Aaron, Carpenter, and de Geer references qualify as prior art. Patent Owner has identified a factual dispute regarding the significance of the ’030 application’s disclosures, and we view that dispute as best resolved through trial.” slip op. at 9
- PTAB / AIA Trials › Real party in interest / privityDecided for petitioner
“35 U.S.C. § 312(a)(2) provides that one of the “Requirements of Petition” is that “the petition identifies all real parties in interest.” “Whether a non-party is a RPI is a ‘highly fact-dependent question’ and must be considered on a case-by-case basis.” SharkNinja Operating LLC. v. IROBOT Corp., No. IPR2020-00735, 2020 WL 6050687, at *4 (PTAB Oct. 13, 2020) (precedential) (citing Ventex Co. v. Columbia Sportswear N. Am., Inc., IPR2017-00651, Paper 148 at 6 (PTAB Jan. 24, 2019) (Paper 148) (precedential) (citing Office Trial Practice Guide, 77 Fed. Reg. 48,756, 48,759 (Aug. 14, 2012))). Here, addressing whether TCH is an unnamed RPI would not create a time bar or estoppel under 35 U.S.C. § 315. There is no allegation or evidence that TCH is “barred or estopped from this proceeding or that Petitioner purposefully omitted [TCH] to gain some advantage.” SharkNinja at *4. Rather, Patent Owner argues that for “once again willfully fail[ing] to identify TCH as a real party in interest, . . . the Petition should be denied on that basis.” Prelim. Resp. 7. In other words, Patent Owner contends only that we deny institution because of “the alleged failure of a procedural requirement that can be corrected under our precedent.” SharkNinja at *4. We understand that” slip op. at 11
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialPatents in suitUS 9,679,286
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.