- SAP America, Inc. v. Cyandia, Inc.InstitutedPTAB · Apr 7, 2025 · IPR2024-01433 · APJ Jason W Melvin · IPR · Institution
The Board instituted review of claims 1–7, 10, 11, 13, 18, 19, 23, 29, 35, and 36 based on the PCT publication and Austin-Lane under § 103.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Denied
“Petitioner’s Sotera stipulation will eliminate the overlap between this proceeding and invalidity at the district court. Unlike the other, related IPRs for which we discretionarily deny review (e.g., IPR2024-01432, -01495, & -01496), this proceeding does not involve references that fundamentally convey the same information as may be presented as system art in the Texas litigation. In light of the stipulation and nature of the asserted ground, we conclude that this ground strongly favors institution.” slip op. at 12
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We conclude that the claim language reads on Austin-Lane’s disclosure of determining “a presentation method of the notification” such as “using an instant message to the notebook computer” (Ex. 1105 ¶¶ 39, 46), in combination with teachings regarding the device to which the notification is sent and the protocol used to deliver it. We further conclude that Petitioner has provided an adequate reason that skilled artisans would have looked to Austin-Lane’s teachings and combined them with the system described in the PCT publication, as discussed. We have further reviewed the uncontested aspects of the challenge to claim 1 (Pet. 43–58) and determine that Petitioner is reasonably likely to prevail proving obviousness of claim 1. IV. CONCLUSION For the reasons discussed above, we conclude that Petitioner has shown a reasonable likelihood of prevailing with respect to unpatentability of at least one claim. Accordingly, we institute inter partes review. V. ORDER Accordingly, it is ORDERED that, pursuant to 35 U.S.C. § 314(a), inter partes review of claims 1–7, 10, 11, 13, 18, 19, 23, 29, 35, and 36 of the ’948 patent is instituted on the grounds raised in the Petition; and” slip op. at 26
- Skill levelSkill level petitioner adoptedDecided for petitioner
“of filing “would have had a bachelor’s degree in electrical engineering, computer science, or equivalent, with two or more years of experience developing and implementing graphical user interfaces for controlling server-based applications, including handling asynchronous notifications generated by those applications and web services, such as portal systems, or an equivalent amount of relevant work or research experience” and “would have been familiar with common approaches for presenting information on a graphical user interface, including various layouts for presenting multiple elements, such as icons, widgets, windows, etc.” Pet. 14–15. Petitioner describes further capabilities that such a person of ordinary skill in the art would have had. Id. at 15–16. Patent Owner asserts that a person of ordinary skill in the art at the time of filing “would have had a Bachelor’s degree in electrical engineering, computer science, or the like, and/or four or more years of experience in server-based applications” and that “[a]dditional experience may make up for a lack of education and vice versa.” Prelim. Resp. 14. Because Petitioner’s proposed level of ordinary skill in the art appears to be consistent with the challenged patent and prior art, we adopt it and use “skilled artisans” to refer to people with such skill at the time the invention was filed. We do not perceive a substantive distinction between the parties’ definitions, but note that Petitioner’s definition provides more detail about the capabilities of skilled artisans. Should either party believe that the definition of ordinary skill in the art affects a disputed issue in the trial, it should point out how and identify any potential dispute about the level of skill.” slip op. at 14
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“We do not agree. Petitioner notes that certain disclosures added to the April 2011 CIP application describe a “notification manager” to “determine the best alert notification method.” Pet. 27 (quoting Ex. 1110 ¶ 131; citing id. ¶¶ 90–93, 130–132, 145–147, 160). That does not mean that Petitioner construes the claim language to require determining the best method, only that disclosing a mechanism that “determine[s] the best alert notification method” provides written-description support for a requirement to “determin[e] a notification method.” Petitioner is clear in its position that the May 2009 application “does not describe how to determine a notification method or how to use ‘session data’ in the manner required by this claim limitation.” Pet. 27–28. Patent Owner asserts that the May 2009 application discloses “determining a notification method” through a channel alert server that can “determine the active devices of the subscriber . . . to provide a visual or auditory alert in the channel.” Prelim. Resp. 32 (quoting Ex. 1106 ¶ 39). That disclosure appears to address the claim language requiring an alert “based on the current state of the at least one external device indicated by the session data.” It does not, however, address the claim language “determining a notification method.” Patent Owner recognizes that Petitioner asserts disclosures in the prior art for “determining which devices to send the alert to, the protocols used to send the alert, and how alerts are presented.” Id. at 34 (emphasis omitted). But when Patent Owner asserts that the May 2009 application discloses determining how alerts are presented, it points to paragraphs that do not support the assertion. Id. at 35 (citing Ex. 1106 ¶¶ 23, 39). The first, paragraph 23, states that a “trigger may cause the information channel to change its appearance or to take other actions that may be implemented by the developer” and that “one action that may be implemented is to provide a notification to the user.” Ex. 1106 ¶ 23. Nothing about that indicates the system determines how an alert is presented. The second, paragraph 39, states that the channel alert server may “provide a visual or auditory alert in the channel” and that the “alert can appear as defined on other platforms.” Nothing about that indicates the system determines how an alert is presented. Patent Owner has not shown how the May 2009 application discloses a determining a notification method, as claimed. In Patent Owner’s view, Petitioner admits that the May 2009 application (which is the same as the asserted PCT publication) describes determining a delivery mechanism because Petitioner compares it to Austin-Lane, stating that the PCT publication “already includes a channel alert server that determines the active devices of the user and delivers an alert to the user’s device” and “discloses setting the same type of alert (stock alert) and presenting it in the same way (visually) as Austin-Lane.” Prelim. Resp. 35 (quoting Pet. 54) (emphasis omitted). But simply delivering an alert does not necessarily mean the notification method for that alert was determined. We conclude that Petitioner’s statement does not show the PCT publication discloses “determining a notification method” as claimed.” slip op. at 20
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites Phillips · GrahamPatents in suitUS 8,751,948 - PTAB · Jan 31, 2023 · IPR2022-01191 · APJ Jo-Anne M Kokoski · IPR · Institution
The Board instituted IPR on claims 1–7 under both asserted grounds, finding a reasonable likelihood of anticipation by Hafeman 670 and declining discretionary denial.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner
“We agree with Petitioner. Our binding guidance states that the Board “will not discretionarily deny institution of an IPR or PGR in view of parallel district court litigation where a petitioner stipulates not to pursue in a parallel district court proceeding the same grounds as in the petition or any grounds that could have reasonably been raised in the petition.” Memorandum, 7. Petitioner could not make such a stipulation in district court litigation to which it is not a party. Instead, LG, as the defendant in the LG Litigation and a real party in interest in this proceeding, made such a stipulation, and LG’s stipulation “mitigates concerns of potentially conflicting decisions and duplicative efforts between the district court and the PTAB.” Id. Indeed, in advocating for discretionary denial in view of the LG Litigation, Patent Owner argues that “for all intents and purposes, Google and Microsoft are ‘the same party’ as LG in the litigation.” Prelim. Resp. 22. Patent Owner, therefore, effectively treats Petitioner and LG as the same entity to argue for discretionary denial.” slip op. at 10
- Parallel petitionsDecided for petitioner
“In light of the priority dispute with respect to the challenged claims, we determine that two petitions are justified. See Patent Trial and Appeal Board Consolidated Trial Practice Guide6 (Nov. 2019), 59 (“[T]he Board recognizes that there may be circumstances in which more than one petition 6 Available at https://www.uspto.gov/TrialPracticeGuideConsolidated asserted a large number of claims in litigation or when there is a dispute about priority date requiring arguments under multiple prior art references.”). We also note the that two petitions together present a total of four grounds, and addressing the grounds in the two petitions does not create a substantial burden on the Board or the parties under these circumstances.” slip op. at 11
- Skill levelSkill level petitioner adoptedOther
“(“POSITA”) would have had “a bachelor’s degree in computer science, computer engineering, electrical engineering, or the equivalent and at least two years of experience in the relevant field, e.g., electronic communications systems.” Pet. 27 (citing Ex. 1003 ¶¶ 95–97). Petitioner also contends that “[s]ignificantly more practical experience could also qualify one not having the aforementioned education as a person of ordinary skill in the art while, conversely, a higher level of education could offset a lesser amount of experience.” Id. At this stage of the proceeding, Patent Owner neither addresses Petitioner’s proposed definition nor proposes a different level of skill in the art. To the extent necessary, and for purposes of this Decision, we accept the uncontested assessment offered by Petitioner, except that we delete the qualifier “at least” to eliminate vagueness as to the amount of experience. The qualifier expands the range indefinitely without an upper bound and thus precludes a meaningful indication of the level of ordinary skill in the art.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“We construe each claim “in accordance with the ordinary and customary meaning of such claim as understood by one of ordinary skill in the art and the prosecution history pertaining to the patent.” 37 C.F.R. § 42.100(b) (2021). Under this standard, claim terms are generally given their plain and ordinary meaning as would have been 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 v. AWH Corp., 415 F.3d 1303, 1313 (Fed. Cir. 2005) (en banc). Only those terms in controversy need to be construed, and only to the extent necessary to resolve the controversy. Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019). Petitioner presents two issues for claim construction. Pet. 23–27. First, Petitioner argues that certain language in each independent claim should be interpreted to require the automatic display of certain information “during or after every boot-up.” Id. at 23–26. Second, Petitioner argues that the return and recovery information recited in the claims is merely printed matter that is not entitled to patentable weight. Id. at 26–27. Patent Owner “takes no position” on Petitioner’s first claim construction argument, and disputes Petitioner’s second argument. Prelim. Resp. 8–12. We determine that no claim term requires express construction for purposes of this Decision.” slip op. at 13
Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 10,789,393 - PTAB · Jan 31, 2023 · IPR2022-01189 · APJ Daniel J Galligan · IPR · Institution
The Board instituted IPR on claims 1–7 and all petition grounds, finding a reasonable likelihood that Hafeman 670 anticipates the claims because the ’332 application lacked written-description support for remote initiating.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner
“We agree with Petitioner. Our binding guidance states that the PTAB will not discretionarily deny institution of an IPR or PGR in view of parallel district court litigation where a petitioner stipulates not to pursue in a parallel district court proceeding the same grounds as in the petition or any grounds that could have reasonably been raised in the petition. Interim Procedure 7. Petitioner could not make such a stipulation in district court litigation to which it is not a party. The defendant in that litigation, LG Electronics Inc., which is a real party in interest in this proceeding (Pet. 81),” slip op. at 6
- Parallel petitionsDecided for petitioner
“We find that two petitions are justified here due to the priority date issue that this Petition raises. See Trial Practice Guide 59 (“[T]he Board recognizes that there may be circumstances in which more than one petition may be necessary, including, for example, when the patent owner has asserted a large number of claims in litigation or when there is a dispute about priority date requiring arguments under multiple prior art references.”).” slip op. at 8
- Skill levelSkill level petitioner adoptedDecided for petitioner
“To the extent necessary, and for purposes of this Decision, we accept the uncontested assessment offered by Petitioner, except that we delete the qualifier “at least” to eliminate vagueness as to the amount of experience. The qualifier expands the range indefinitely without an upper bound, and thus precludes a meaningful indication of the level of ordinary skill in the art.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“D. Claim Construction We need not expressly construe any terms to determine whether to institute. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in” slip op. at 9
Claim construction§ 112 disclosureDiscretionary denialcites KSRPatents in suitUS 10,325,122 - PTAB · Mar 24, 2022 · PGR2021-00112 · APJ Bryan F Moore · PGR · Institution
Instituted PGR on claims 1–20 because Petitioner showed a reasonable likelihood that claim 1 lacks written description support; all petition grounds were included.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner
“content for output.” Id. at 89. We determine, however, that Petitioner’s argument under Step 2A Prong One that claim 1 is directed to the “obtaining content for output” is not substantially different from the Examiner’s determination that claims 1‒20 recite “collecting information, analyzing it, and displaying certain results of the collection and analysis.” Compare Pet. 37–88 (citing e.g. Electric Power), with Ex. 2001, 193–194 (also citing Electric Power). In both cases, the argument is the same or substantially the same, i.e., that similarly identified subject matter of the claim is obtaining (collecting) data and displaying (outputting) it. Nevertheless, as to Step 2A Prong Two, we determine that the claims at issue in the ’096 prosecution differ in material ways from the ’903 patent claims at issue in this PGR. Specifically, the ’096 patent claims recite a touchscreen interface not recited in the ’903 patent claims. Additionally, the ’903 claims focus on the “output device” as performing the patented steps but in the ’096 prosecution history the “‘information apparatus performs the patented steps and “is integral to the claims” (as the Applicant argued). See Ex. 2008 [comparison of ’096 prosecution claims and ’903 claims]; Ex. 2001, 150; see also Pet. 89 (“the claims at issue in the ’067 application were different than the claims of the ’903 patent addressed here.”). rejection and arguments in the ’096 prosecution history turns on whether the claims in this PGR recite different elements that must be determined to integrate the judicial exception into a practical application (i.e., Prong Two of Step 2A). Petitioner argues that an essential element different than the ’096 claims, i.e. the output device, does not integrate the judicial exception into a practical application because the claims do not amount to an improvement to computer functionality. Pet. 37–72. We find this a close case. Nevertheless, due to the differences in the claims, we determine that the Examiner’s withdrawal of the § 101 rejection in light of the applicant’s arguments regarding the claim being directed to a specific technical solution is not substantially the same argument that Petitioner’s presents in the Petition as to Prong Two of Step 2A.” slip op. at 22
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“C. Lack of Written Description Support Petitioner contends that the challenged claims are unpatentable for lack of written description for the same reasons it contends the ’903 patent is PGR eligible. Pet. 13–36. The Specification of the ’903 patent has substantially the same disclosures as the Specification of the ’413 application relied on by Patent Owner (see Prelim. Resp. 20) to which the ’903 patent claims priority. Having determined that the disclosures in the ’903 patent Specification and the ’413 application is insufficient to provide written description support for the at least claim 1, we also determine that Petitioner has demonstrated a reasonable likelihood that at least claim 1 is unpatentable for the same reasons. Thus, we exercise our discretion and institute post grant review of claims 1–20 challenged under this ground. See SAS Inst. Inc. v. Iancu, 138 S. Ct. 1348, 1369–60 (2018).” slip op. at 33
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateInstituted
“in the art at the time of the invention] would have understood that an output system/device could be (or include) an information apparatus. Prelim. Resp. 24. We determine that Patent Owner’s argument has a logical flaw––i.e., the fact that a particular device could be used alternately as an information apparatus or an output device does not necessarily mean that it was known by one of ordinary skill in the art to use a combined information apparatus/output device and have the new combined device perform all the additional functions required by the claims. “The knowledge of ordinary artisans may be used to inform what is actually in the specification, but not to teach limitations that are not in the specification, even if those limitations would be rendered obvious by the disclosure in the specification.” Rivera v. Int’l Trade Comm’n, 857 F.3d 1315, 1322 (Fed. Cir. 2017) (“Rivera”). “The question is not whether a claimed invention is an obvious variant of that which is disclosed in the specification . . . . It extends only to that which is 1997). Patent Owner has not pointed to any disclosure in the ’413 application teaching that an “output device” can perform the functions of the “information apparatus” including its interactions with the “output device.” For example, claim 1 recites “wirelessly receiving, by the output system . . . output data from at least one server of the one or more servers over the Internet.” Ex. 1001, 37:28–32. At this stage, we find sufficiently persuasive Petitioner’s argument, which we discuss above, that the only written description support for an “output device” that performs the claimed functions by accessing the Internet provided by Patent Owner is not an “output device” but an “information apparatus.” Prelim. Resp. at 27–29.” slip op. at 29
§ 112 disclosureDiscretionary denialcites Mayo · Bilski · Electric PowerPatents in suitUS 11,029,903
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.