• Thermaltake Technology Co., Ltd. / Thermaltake Inc. v. Chien-Hao ChenAll claims unpatentable
  PTAB · Feb 17, 2026 · IPR2024-01230 · APJ Andreas Baltatzis · IPR · Final written decision

  Claims 1–5 are unpatentable; substitute claims 6 and 7 are unpatentable, and the Revised Motion to Amend is denied.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “our Institution Decision comports with the qualifications a person would have needed to understand and implement the teachings of the ’336 patent and the prior art of record. Inst. Dec. 15. Accordingly, we adopt the level of skill discussed in our Institution Decision. C.” slip op. at 11

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

    “Pharms. Inc. v. Amino Chemicals Ltd., 715 F.3d 1363, 1374 (Fed. Cir. 2013)). Accordingly, Patent Owner applies a different definition of “side,” in claim 1’s recitation of “an illumination area on at least two sides of the fan at top of the body,” to that definition used to understand “side[s] of the body,” discussed above. Specifically, Patent Owner argues that Petitioner’s dictionary definition of “side,” including “an area next to something” applies to “an illumination area on at least two sides of the fan at the top of the body.” See id. at 8–9.” slip op. at 17

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

    “Hasegawa, and Huang teaches or suggests the limitations of claim 3, and that one skilled in the art would have been motivated to combine those teachings with a reasonable expectation of success. See Ex. 1004 ¶¶ 136– 140; Ex. 1008, 8:4–15, 3:20–29. Accordingly, we determine that claim 3 would have been obvious over Lai and Huang, or Lai, Hasegawa, and Huang. F.” slip op. at 50

  • 112 supportMotion to amend, deniedDenied

    “c) Conclusion We conclude that Patent Owner's Revised Motion to Amend adds new” slip op. at 90

  Patent outcomesUS 10,690,336 unpatentable
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 10,690,336
• Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentable
  PTAB · Mar 12, 2024 · PGR2022-00053 · APJ Iftikhar Ahmed · PGR · Final written decision

  Claims 1–22 are unpatentable under collateral estoppel; revised substitute claims 23–37 are allowed because Petitioner did not prove them unpatentable.

  RulingsFinal written decision

  • BurdenFwd all claims unpatentableDecided for petitioner

    “The party seeking to invoke collateral estoppel must show: (1) the issue is identical to one decided in the first action; (2) the issue was actually litigated in the first action; (3) resolution of the issue was essential to a final judgment in the first action; and (4) [the party against who collateral estoppel is being asserted] had a full and fair opportunity to litigate the issue in the first action. Google, 54 F.4th at 1381 (quoting In re Freeman, 30 F.3d 1459, 1465 (Fed. Cir. 1994)). Collateral estoppel may also operate to bar re-litigation of common issues in actions involving different but related patents. Mycogen Plant Science, Inc. v. Monsanto Co., 252 F.3d 1306, 1310 (Fed. Cir. 2001) (citing Amgen, Inc. v. Genetics Inst., Inc., 98 F.3d 1328, 1329–32 (Fed. Cir. 1996); Interconnect Planning Corp. v. Feil, 774 F.2d 1132, 1136 (Fed. Cir. 1985)). We are persuaded that each of the four Google requirements is satisfied and, accordingly, agree with Petitioner that the challenged claims of the ’256 patent are unpatentable in light of our Final Written Decision in PGR2021-00096.” slip op. at 13

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable

    “specific requirements of the claims.” McRO, Inc. v. Bandai Namco Games America Inc., 837 F.3d 1299, 1313 (Fed. Cir. 2016) (quoting In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 611 (Fed. Cir. 2016)). But “failing to account for the specific requirements of the claims” is what Petitioner’s analysis of the claim limitations appears to do. Petitioner’s argument that “the focus of the claims” is captured by a single claim element (f3) not only ignores that that limitation recites performing two specific software tasks simultaneously—which we are not persuaded is an abstract idea—but also asks us to disregard multiple technical aspects recited in the claims, such as identifying a link, determining whether an installation client is available on the device, invoking the installation client, and redirecting to the device an app store. See, e.g., Ex. 1001, 21:12–41; Revised MTA 24–25. That is, under Step 2A of the Guidance, we are neither persuaded that limitation f3, which Petitioner points us to, recites an abstract idea (Prong 1), nor that the other limitations recited in the independent claims fail to integrate the alleged abstract idea into a practical application (Prong 2). Petitioner characterizes the claims as directed to multitasking, which Petitioner describes as an example applied to improve a user experience, i.e., as related to organizing human activity. Pet. 29. Although the Guidance recognizes certain methods of organizing human activity, including certain activity between a person and a computer, as constituting a patent-ineligible abstract idea, we are not persuaded that the claims here fall within the scope of such activity. See Guidance, 84 Fed. Reg. at 52 (listing fundamental economic principles or practices, commercial or legal interactions, and managing personal behavior or relationships as organizing human activity). The claimed invention may result in multitasking on the device, but the background instead of directing the user to an app store, thereby maintaining user experience with the foreground application, and do not recite an abstract idea. And although that process does result in improving user experience, the claims recite more than that mere result; they recite specific steps—invoking, without exiting the foreground software application, the installation client for downloading and installing applications on the device to run in the background—that accomplish the desired result. See Finjan, Inc. v. Blue Coat Sys., Inc., 879 F.3d 1299, 1305–06 (Fed. Cir. 2018) (finding a method that employs a new kind of file in a computer security system directed to a non-abstract improvement in computer functionality, rather than the abstract idea of computer security writ large). Petitioner thus fails to establish sufficiently that the claims are directed patent ineligible subject matter under Step 2A of the Guidance.” slip op. at 52

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

    “When the application package 172 has been received by the client system 130, the App Manager 180 may extract or retrieve a set of requested permissions 174 from the application package 172, and present a request to the user for asking for approval to perform operations corresponding to the requested permissions, e.g., opening files, accessing contact information, accessing a camera on the client device 130, and so on. . . . In particular embodiments, when the requested permissions 174 have been requested, and a response specifying a set of accepted permissions 176 has been received from the user, the set of accepted permissions 176 may be compared to the set of requested permissions 174. If the sets are the same, then the installation process may continue, and the App Manager 180 may invoke an installer 182 to install the application package 172. Ex. 1003, 8:67–9:22 (emphasis added). That is, the set of permissions to be checked are obtained by the App Manager once the download of the application package to be installed is initiated. See id. at 8:59–61 (“when the download is initiated by a request sent from the client system 130 to the server 162, the server 162 may send the requested object, e.g., the download page 168 or the application package 172, back to the client system 130”). And these permissions relate to operations that the installed applications may perform, e.g., opening files, accessing contact information, accessing a camera on the client device. Id. at 9:6–7. These permissions may also indirectly determine whether the installation client can install that app. See id. at 9:33–38. There is no suggestion in Pasha, however, that these permissions have anything to do with the host application, i.e., the second software application. said second software application is eligible to use capabilities of the installation client.” RMTA 25; see also Ex. 1001, 15:11–14 (“The installation client, upon receiving an instant install link, checks the eligibility of the caller and if identified as eligible continues the process of downloading the app.”). Pasha does not teach or suggest checking eligibility of its host application in any way or at any point. Moreover, as Patent Owner points out, Pasha’s App Manager performs the eligibility check after it downloads the app package, further supporting that Pasha’s eligibility check has nothing to do with the host application.9 Dr. Almeroth testifies that “Pasha discloses the App Manager 180 confirming that it has obtained the required permissions, which, in [his] opinion, a [person of ordinary skill in the art] would understand may include inter alia that the ‘second software application’ (e.g., the host application invoking the app manager) is eligible to use its capabilities.” Ex. 1035 ¶ 68. Dr. Almeroth fails to cite any supporting evidence or provide any technical reasoning to support his statement. Id. Because we find no basis in the record for Dr. Almeroth’s conclusion, we give little weight to this testimony.” slip op. at 40

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Dr. Almeroth testifies that “Pasha discloses the App Manager 180 confirming that it has obtained the required permissions, which, in [his] opinion, a [person of ordinary skill in the art] would understand may include inter alia that the ‘second software application’ (e.g., the host application invoking the app manager) is eligible to use its capabilities.” Ex. 1035 ¶ 68. Dr. Almeroth fails to cite any supporting evidence or provide any technical reasoning to support his statement. Id. Because we find no basis in the record for Dr. Almeroth’s conclusion, we give little weight to this testimony. 9 During oral argument, Petitioner pointed us to disclosure in Pasha that teaches that the permission dialog may be displayed to the user at different points in the download process. Tr. 47:24–48:8 (citing Ex. 1003, 22:21–42). As Patent Owner pointed out, this disclosure was not relied up on by Petitioner in its papers and is new evidence. Id. at 51:19–22; Paper 46, 4. Petitioner’s argument based on this new evidence is therefore forfeited. But even if we were to consider the cited disclosure from Pasha, it still only suggests that permissions need to come from the server after the download process has been initiated, and are therefore, unrelated to the host application. See Ex. 1003, 22:46–49 (“the requested permissions may be downloaded prior to downloading the application or may be extracted from the application package”). 24, 2022) (precedential) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”) (quoting 37 C.F.R. § 42.65(a)). As the Board explained in Xerox, such expert testimony “is particularly problematic in cases where, like here, expert testimony is offered not simply to provide a motivation to combine prior-art teachings, but rather to supply a limitation missing from the prior art.” Id. (citing Arendi S.A.R.L. v. Apple, Inc., 832 F.3d 1355, 1361–62 (Fed. Cir. 2016)).” slip op. at 41

  Patent outcomesUS 11,157,256 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Berkheimer · Enfish · Phillips
  Patents in suitUS 11,157,256
• Unified Patents, LLC v. Ideahub Inc.All claims unpatentable
  PTAB · Feb 5, 2024 · PGR2022-00044 · APJ Monica S Ullagaddi · PGR · Final written decision

  Claims 1–13 are unpatentable for lack of written description under § 112(a); the Board did not reach the anticipation and obviousness grounds based on HEVC265.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner contends that: A person of ordinary skill in the art at the priority date for the ’274 Patent (“POSITA”) would have had a bachelor’s degree in electrical or computer engineering, or a closely related scientific field such as physics or computer science, and two years of work experience with video processing. A lack of experience can be remedied with additional education (e.g., a Master’s degree), and likewise, a lack of education can be remedied with additional work experience (e.g., 4–5 years). This definition would apply at the earliest claimed priority date of the ’274 Patent as well as any later date. Pet. 12 (citing Ex. 1005 ¶¶ 50–52). Patent Owner does not dispute the level of ordinary skill in the art. See generally PO Resp. We adopt Petitioner’s definition as it appears to be consistent with the Specification of the ’274 patent and the cited reference.” slip op. at 14

  • PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner

    “A party is collaterally estopped from relitigating an issue if: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the prior action featured full representation of the estopped party. VirnetX Inc. v. Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)).” slip op. at 21

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable
  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “For the reasons that follow, we determine that the ’928 application does not provide sufficient written description support, for at least independent claim 1 of the ’274 patent, so as to “reasonably convey[] to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date” of the ’928 application. Ariad, 598 F.3d at 1351. Accordingly, we are persuaded that the ’928 application lacks sufficient written description support for the invention recited in claim 1 of the ’274 patent, and thus, claim 1 does not receive an effective filing date as early as that of the ’928 application (i.e., December 23, 2010). We further determine that Petitioner filed the Petition within the 9-month statutory period for requesting post-grant review in accordance with 35 U.S.C. § 321(c). The ’274 patent issued on September 14, 2021 (see Ex. 1001, code (45)), and the present Petition was accorded a filing date of June 9, 2022 (see Paper 5). Accordingly, the Petition was filed less than 9 months after the date of issuance of the ’274 patent. In view of the above, we are persuaded that the ’274 patent is eligible for post-grant review.” slip op. at 16

  Patent outcomesUS 11,122,274 unpatentable
  § 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 11,122,274
• Home Depot U.S.A., Inc. v. Lynk Labs, Inc.All claims unpatentable
  PTAB · May 22, 2023 · PGR2022-00009 · APJ Monica S Ullagaddi · PGR · Final written decision

  Claims 1–5, 7–12, and 14–19 are unpatentable based on lack of written description, anticipation by Bruning, or obviousness over Bruning and Kabel.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “lighting device.” Accordingly, we determine that the level of ordinary skill in the art is “a bachelor’s degree in electrical engineering, or similar technical field, with two years of relevant experience in the field of design and/or development of LEDs and circuits,” as Petitioner proposes and that “the field of design and/or development” would be “in the context of lighting devices” as Patent Owner proposes, in which “[a]n increase in experience could compensate for less education.” Id.; Pet. 24 (citing Ex. 1002 ¶ 46).” slip op. at 15

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

    “theoretically fall under the “or greater” portion of the amended claim limitation “forward voltage of 6V or greater,” Applicant distinguished Colby on the basis that the 120V AC voltage from a wall outlet is not “the minimum voltage difference required between the anode and cathode of the LEDs in the claimed circuit to allow current to flow through the LEDs.” See Ex. 1023, 9 (emphasis added). Applicant’s argument specifically identifies the claim language at issue––“forward voltage of 6V or greater”––and specifically states that it is not disclosed because Colby does not disclose the minimum voltage and instead, discloses something else, something larger–– 120V AC voltage. Accordingly, we conclude that Applicant disclaimed any voltage that is more than “the minimum voltage difference required between the anode and cathode of the LEDs in the claimed circuit to allow current to flow through the LEDs” from the scope of “forward voltage.”” slip op. at 25

  • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

    “4. 35 U.S.C. § 112(a) With respect to the written description requirement, we are persuaded” slip op. at 32

  • Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Not enabledUnpatentable

    “Basis § Unpatentable Unpatentable Lack of written description, 3, 10, 17 112(a) 3, 10, 17 Lack of enablement 3, 10, 17 112(b) Indefiniteness 3, 10, 17 Lack of written description, 4, 11, 18 112(a) 4, 11, 18 Lack of enablement 4, 11, 18 112(b) indefiniteness 4, 11, 18” slip op. at 77

  Patent outcomesUS 10,932,341 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham · Nautilus
  Patents in suitUS 10,932,341
• Ironsource Ltd. v. Digital Turbine Inc.Instituted
  PTAB · Mar 17, 2023 · PGR2022-00053 · APJ Iftikhar Ahmed · PGR · Institution

  The Board instituted PGR on claims 1–22 under § 101, § 102(a) over Pasha, and § 103 over Pasha, Pasha and Yamada, and Pasha and Molinet.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “Under 35 U.S.C. § 324(a), a post-grant review may not be instituted unless it is determined that it is more likely than not that at least one of the challenged claims is unpatentable. Based on the information presented in the Petition and the supporting evidence, we are persuaded that the Petition demonstrates it is more likely than not that at least one of the challenged claims is unpatentable. Accordingly, we institute a post-grant review of the challenged claims on the grounds set forth in the Petition.” slip op. at 2

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

    “[t]he words of a claim are generally given their ordinary and customary meaning as understood by a person of ordinary skill in the art when read in the context of the specification and prosecution history.” Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012) (citing Phillips, 415 F.3d at 1313). “There are only two exceptions to this general rule: 1) when a patentee sets out a definition and acts as his own lexicographer, or 2) when the patentee disavows the full scope of a claim term either in the specification or during prosecution.” Id. (citing Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1580 (Fed. Cir. 1996)). Neither of those exceptions apply here, and for the reasons below, we find the plain and ordinary meaning of “invoke” or “invoking” to be to call or activate, as proposed by Petitioner. slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner

    “to mean “to shift user interaction on the device,” and we disagree with Patent Owner that the claim term requires the shifting to take place without requiring a user interaction. We begin with the language of the independent claims. Claim 1 recites “redirect said device to an app store for downloading said first software application on said device.” Ex. 1001, 21:38–40. The claim language, therefore, does not recite any requirement relating to user interaction during the redirect.” slip op. at 15

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

    “3. Other Claim Terms We determine that we do not need to expressly construe any other terms in order to determine whether to institute. The parties are reminded claim terms will be based on the complete record developed during trial.” slip op. at 17

  Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnessDiscretionary denialcites Alice · Enfish · Phillips
  Patents in suitUS 11,157,256
• Unified Patents, LLC v. Ideahub Inc.Instituted
  PTAB · Feb 6, 2023 · PGR2022-00044 · APJ Monica S Ullagaddi · PGR · Institution

  The Board instituted post-grant review of claims 1–13 on all grounds, finding it more likely than not that at least claim 1 lacks written-description support.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “review. 35 U.S.C. § 324(c); 37 C.F.R. § 42.4(a) (2021). Under 35 U.S.C. § 324(a), 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.” After considering the Petition, Patent Owner’s Preliminary Response, Petitioner’s Preliminary Reply, Patent Owner’s Preliminary Sur-reply, as well as all supporting evidence, we determine that Petitioner satisfies its burden under 35 U.S.C. § 324(a) to show that it is more likely than not that at least one of the challenged claims of the ’274 patent is unpatentable. Therefore, we authorize a post-grant review to be instituted as to all grounds and all challenged claims. 37 C.F.R. § 42.208(a) (“When instituting post-grant review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther

    “Id. at 7:24–8:4 (emphasis added). The ’928 application repeatedly makes clear that directionality and intra mode are related, but distinct concepts. They are not interchangeable as Patent Owner argues. On this point, we find Dr. Freedman’s explanation in paragraph 85 of his Declaration on the relationship between “intra mode” and “directionality” to be particularly well-reasoned and persuasive. As Dr. Freedman explains, [t]hroughout the ’928 application, the text uses the term “directionality” to refer to characteristics of neighboring blocks, whereas the term “intra mode” is used when referring to the current block. For example, the ’928 application describes that “directionality” of neighboring blocks is “estimated from the neighboring blocks” that “have already been reconstructed” while the “intra mode” is selected for the current block for purposes of reconstructing that current block. This is likely because the neighboring blocks “have already been reconstructed” and thus, the intra mode number that was used in reconstructing those blocks is no longer pertinent. Instead, what is pertinent in the ’928 application’s method is the directionality characteristic of those neighboring blocks. Phrased differently, in the ’928 application, directionality is a concept that is evaluated after performance of intra prediction (i.e., after reconstruction), whereas the intra mode or number is a concept used during performance of intra prediction. They are not equivalent in the context of the ’928 application. Ex. 1005 ¶ 86 (citing Ex. 1028, 11:14–12:4, 25:10–15; Ex. 1036, 706 (“The DCT coefficients gathered from the MPEG 2 process are used to estimate the directional features in a picture. The estimated directional features are then used to compute the intra prediction modes in the H.264 encoding stage.”)).8 Thus, we are persuaded by Dr. Freedman’s testimony, supported by Kalva, that these terms are not synonymous, as is Patent Owner’s and its expert’s position.” slip op. at 31

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityNot reached

    “Patent Owner argues that HEVC265 is not prior art because it was published in 2013. Prelim. Resp. 24. Insofar as we determine that the ’928 application does not provide sufficient written description support for at least claim 1, and insofar as no other patent or application in the priority chain of the ’274 patent was filed before 2013 (see Pet. 19), Patent Owner’s argument is unavailing as to this claim. As we preliminarily conclude that Petitioner demonstrates that it is more likely than not to prevail on its challenge to independent claim 1 based on lack of written description support, we institute review on all challenged claims on all grounds set forth in the Petition, including Petitioner’s anticipation and obviousness challenges to claims 1–4 and 6 applying HEVC265. See SAS, 138 S. Ct. at 1354; PGS, 891 F.3d at 1360.” slip op. at 38

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

    “F. Anticipation and Obviousness Challenges Based on HEVC265 Petitioner contends that claims 1–4 and 6 are anticipated by, or alternatively, rendered obvious in view of HEVC265. Pet. 49–52. Patent Owner argues that HEVC265 is not prior art because it was published in 2013. Prelim. Resp. 24. Insofar as we determine that the ’928 application does not provide sufficient written description support for at least claim 1, and insofar as no other patent or application in the priority chain of the ’274 patent was filed before 2013 (see Pet. 19), Patent Owner’s argument is unavailing as to this claim. As we preliminarily conclude that Petitioner demonstrates that it is more likely than not to prevail on its challenge to independent claim 1 based on lack of written description support, we institute review on all challenged claims on all grounds set forth in the Petition, including Petitioner’s anticipation and obviousness challenges to claims 1–4 and 6 applying HEVC265. See SAS, 138 S. Ct. at 1354; PGS, 891 F.3d at 1360.” slip op. at 38

  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 11,122,274
• Honeywell International, Inc. / Sierra Wireless, Inc. et al. v. 3g Licensing SAAll claims unpatentable
  PTAB · Jan 11, 2023 · IPR2021-01141 · APJ Russell E Cass · IPR · Final written decision

  Claims 34–40 are unpatentable as obvious over Samsung and C.S0002-0, or Samsung, Airvana, and C.S0002-0; the Board did not reach the Chung ground.

  RulingsFinal written decision

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “’653 patent are not supported by Korean App. No. 6839. Claim limitation 34(d) requires that “a bit is sent on a reverse packet data control channel to indicate whether the mobile station has enough power and data to increase its data transmission rate on a reverse packet data channel,” and claim 37 recites a similar limitation. Ex. 1001, 20:19–22 (emphasis added), 20:44– 48. The ’653 patent discloses an MS_IAB bit that indicates whether the mobile station has enough power and data to increase its data transmission rate on a reverse packet data channel. Id. at 14:3–20. More specifically, the ’653 patent states that the MS_IAB value is set to “increase” when “transmission power margin (i.e., remaining transmission power) is above a certain level,” the “number of bits in the transmission buffer is above a certain level,” and “the data rate of the current transfer . . . is below a maximum data rate . . . set by the system.” Id. at 14:10–19. Thus, the ’653 patent’s disclosure of an MS_IAB supports limitation 34(d). This disclosure, however, does not appear in Korean App. No. 6839, and Patent Owner does not contend otherwise. See Pet. 8–9; Pet. Reply 3–4; Ex. 1002 ¶¶ 116–119; PO Resp. 31–46; PO Sur-reply 2–22. Nor is there any similar disclosure in Korean App. No. 6839 of a value that indicates whether the mobile station has enough power and data to increase its data transmission rate, whether referred to as an “MS_IAB” or otherwise. We also find that the RRI in Korean App. No. 6839 does not provide support for claim limitation 34(d). The relevant portion of the ’6839 application states that the base station determines “information on the increase and decrease of transmission data rate (Reverse Activity Bit, RAB) for each mobile station” and sends the RAB to the mobile station. Ex. 1011 ¶¶ 6–7. It then states that “the mobile station that has received its RAB information changes the transmission data rate one step at a time according to the RAB command and transmits it, and informs a base station of its transmission data rate through an RRI (Reverse Rate Indicator).” Id. ¶ 7 (emphasis added). The ’6839 application includes a comparable disclosure in two additional locations, paragraphs 22 and 44. Id. ¶¶ 22 (“the mobile station that has received its RAB information changes the transmission data rate one step at a time according to the RAB command and transmits it, and informs the base station of its transmission data rate through an RRI (Reverse Rate Indicator)”), 44 (same). These disclosures merely state that the RRI informs the base station of the mobile station’s transmission rate; they do not disclose that the RRI includes a bit that “indicate[s] whether the mobile station has enough power and data to increase its data transmission rate,” as the claims require.” slip op. at 27

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

    “4. Motivation to Combine Samsung and Airvana Petitioner argues that one of ordinary skill would have been motivated to combine Samsung and Airvana because “Samsung incorporates Airvana by reference.” Pet. 39. “Specifically,” Petitioner asserts, “Samsung expressly references the disclosures of Airvana and then, importantly, makes a proposal that builds upon and improves Airvana’s ideas.” Id. Petitioner also argues that, even if Samsung and Airvana are “treated as entirely separate references,” one of ordinary skill would have been motivated to combine them because “Samsung specifically references and discusses the content of ‘Airvana’s proposal[] for 1xEV-DV’ in the context of reverse link rate control.” Pet. 40. “Moreover,” Petitioner contends, “Samsung was a contribution to the same 3GPP2 TSG working group (3GPP2 TSG-C WG5) as Airvana, so Samsung’s reference to ‘Airvana’s proposal[]’ for a dedicated control scheme for reverse link data rates could not be misunderstood.” Id. (citing Ex. 1004, 4; Ex. 1002 ¶¶ 161–163). Petitioner further argues that Samsung “states that its proposal for an increase availability bit (‘IAB’) from the mobile station ‘can be applicable for both common and dedicated control scheme[s] for reverse link data rate,” and that “Airvana proposes such a control scheme.” Id. (citing Ex. 1003, 5). Patent Owner does not argue a lack of motivation to combine Samsung and Airvana. See PO Resp. Based on the full trial record, including the testimony of Mr. Proctor, Petitioner has proven by a preponderance of the evidence that one of ordinary skill would have been motivated to combine Samsung and Airvana based on Samsung’s incorporation by reference of Airvana’s proposal, the fact that Samsung was a contribution to the same 3GPP2 TSG working group as Airvana, and Samsung’s statement that its proposal for an IAB can be applicable to a control scheme such as that proposed by Airvana. See Ex. 1002 ¶¶ 161–163; Ex. 1004, 4.” slip op. at 45

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

    “We agree with Petitioner that C.S0002-0 teaches mapping control messages, such as power control messages having potential values of +1, -1, and 0, with the bit not being present meaning a value of 0, the bit being present and set to 1 meaning a value of -1, and the bit being present and set to 0 meaning a value of +1. Pet. 48–49; Ex. 1006, 3-8, 3-21. We also agree that this information is disclosed by Figure 3.1.3.1.1.1-4 of CS.S0002-0. Pet. 49; Ex. 1006, 3-8. Additionally, as discussed in Section II.E.5 above, we find that Petitioner has proven by a preponderance of the evidence that it would have been obvious to use C.S0002-0’s signal point mapping technique with Samsung’s (or Samsung/Airvana’s) messages with Samsung’s signaling by the base station to indicate whether the mobile station should increase, decrease, or maintain its current data transmission data rate. We disagree with Patent Owner’s contentions for the reasons discussed above in Section II.E.5. Consequently, based on the full trial record, we find that Petitioner has proven by a preponderance of the evidence that the combination of Samsung (or Samsung/Airvana) and C.S0002-0 teaches this limitation.” slip op. at 57

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “Our conclusion is supported by the testimony of Mr. Proctor. Mr. Proctor testifies that “RRIs were adopted as part of prior art specifications, including for the [3GPP] cdma2000 High Rate Packet Data Air Interface at least as early as October 2000.” Ex. 1019 ¶¶ 6, 8 (citing Ex. 1018). As Mr. Proctor explains, the cdma2000 specification describes a “Reverse Rate Indicator Channel . . . used by the access terminal to indicate the data rate at which the Data Channel is transmitted.” Ex. 1019 ¶¶ 8–9 (citing Ex. 1018, 9-35). Mr. Proctor also testifies that “the Reverse Rate Indicator (RRI) symbols sent on the RRI Channel by the mobile station (access terminal) to the base station ‘indicate the data rate at which the Data Channel is transmitted.’” Id. ¶ 9 (citing Ex. 1018, 9-35). “In other words,” Mr. Proctor explains, “the mobile station sends RRI symbols to tell the base station the data rate at which the mobile is transmitting information on the reverse link’s Data Channel (the data Channel of the Reverse Traffic Channel), as the RRI Channel is used to indicate the data rate of the Data Channel being transmitted on the Reverse Traffic Channel.” Id. (citing Ex. 1018, 9-26, 9- 33, 9-34, 9-35, 9-39). Additionally, Mr. Proctor testifies that “RRIs are only briefly mentioned three times, in paragraphs 7, 22, and 48” in the ’6839 application, and “the prior art 3GPP specification has the same basic disclosure of RRIs as the ’6839 application: using the RRI to confirm to the base station what data rate the mobile station/access terminal is using.” Id. ¶¶ 7, 11 (citing Ex. 1018, 9-35; Ex. 1011 ¶¶ 7, 22, 48). “Indeed,” Mr. Proctor states, “the ’6839 application references the same data rates between 9.6 and 153.6 kbps on the reverse link that are referenced in the prior art [3GPP] specification.” Id. ¶ 11 (citing Ex. 1011 ¶ 16; Ex. 1018, 9-33, 9-35). We find this testimony to be credible because it is consistent with the disclosures of the ’6839 application and the 3GPP specification (Exhibit 1018). We also rely on and find credible Mr. Proctor’s testimony that “neither the ’6839 application nor the prior art High Rate Packet Data Specification disclose” an “RRI or other signal that comprises a bit that the mobile station sends to indicate it has sufficient power and data for a subsequent increase.” Ex. 1019 ¶ 12. As Mr. Proctor explains, “the only disclosure relating to the RRI within the ’6839 application” is the “single sentence[] referring to the RRI as informing the base station of its transmission data rate,” which is “repeated three times in separate paragraphs.” Id. (citing Ex. 1011 ¶¶ 7, 22, 48). We agree with and find credible Mr. Proctor’s testimony that this sentence “provides no additional teachings beyond what a [person of ordinary skill in the art] would have known to be conventional (e.g., beyond what was known in the current HDR system available at that time, and referenced within the ’6839 application),” id. ¶ 12, and that “[n]o person of skill in the art reviewing” this disclosure would understand it to disclose “a bit that indicates whether the mobile station has power and data to accept an increase in its data rate,” id. ¶ 13.” slip op. at 28

  Patent outcomesUS 7,215,653 unpatentable
  § 103 obviousness§ 112 disclosurecites KSR · Graham
  Patents in suitUS 7,215,653
• Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentable
  PTAB · Jan 4, 2023 · PGR2021-00096 · APJ Iftikhar Ahmed · PGR · Final written decision

  Claims 1–18 are unpatentable; the contingent motion to amend proposing claims 19–36 is denied, and the parties’ motions to exclude are denied in part and granted in part.

  RulingsFinal written decision

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'IneligibleUnpatentable

    “3. Analysis On the full record developed during trial, we are persuaded by Patent Owner’s argument. Petitioner’s analysis of the independent claims described above only loosely corresponds to the actual limitations recited in the claim. The Federal Circuit has “cautioned that courts ‘must be careful to avoid oversimplifying the claims’ by looking at them generally and failing to account for the specific requirements of the claims.” McRO, Inc. v. Bandai Namco Games America Inc., 837 F.3d 1299, 1313 (Fed. Cir. 2016) (quoting In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 611 (Fed. Cir. 2016)). Petitioner’s analysis of the claim limitations appears to do. Petitioner’s argument that “the essence of all the claims” is captured by a single claim element (f3) not only ignores that that limitation recites performing two specific software tasks simultaneously—which we are not persuaded is an abstract idea—but also asks us to disregard multiple technical aspects recited in the claims, such as identifying a link, determining whether an installation client is available on the device, invoking the installation client, and redirecting to the device an app store. See, e.g., Ex. 1001, 21:6–35. That is, under Step 2A of the Guidance, we are neither persuaded that limitation f3, which Petitioner points us to, recites an abstract idea (Prong 1), nor that the other limitations recited in the independent claims fail to integrate the alleged abstract idea into a practical application (Prong 2). Petitioner characterizes the claims as directed to multitasking, which Petitioner describes as representing a basic task in organizing human activity. Pet. 30. Although the Guidance recognizes certain methods of organizing human activity, including certain activity between a person and a computer, as constituting a patent-ineligible abstract idea, we are not persuaded that the claims here fall within the scope of such activity. See Guidance, 84 Fed. Reg. at 52 (listing fundamental economic principles or practices, commercial or legal interactions, and managing personal behavior or relationships as organizing human activity); October 2019 Update at 5 (“this grouping is limited to activity that falls within the enumerated sub-groupings . . . , and is not to be expanded beyond these enumerated sub-groupings except in rare circumstances”). The claimed invention may result in multitasking on the device, but the claims are directed to downloading and installing an application in the background instead of directing the user to an application, and do not recite an abstract idea. And although that process does result in improving user experience, the claims recite more than that mere result; they recite specific steps—invoking, without exiting the foreground software application, the installation client for downloading and installing applications on the device to run in the background—that accomplish the desired result. See Finjan, Inc. v. Blue Coat Sys., Inc., 879 F.3d 1299, 1305–06 (Fed. Cir. 2018) (finding a method that employs a new kind of file in a computer security system directed to a non-abstract improvement in computer functionality, rather than the abstract idea of computer security writ large). Petitioner thus fails to establish sufficiently that the claims are directed patent ineligible subject matter under Step 2A of the Guidance. We also agree with Patent Owner that the challenged claims are somewhat similar to those that the Federal Circuit held patentable in DDR Holdings. The claims there were directed to a method of generating a composite webpage that combined visual elements of a host website with content from a third-party, e.g., by combining the logo, background color, and fonts of the host website with product information from a merchant. DDR Holdings, 773 F.3d at 1248. When a user clicked on a link on the host website, the system would construct the composite web page comprising a look and feel description from the host website along with content based on product information from the merchant’s product catalog. Id. at 1250. The court held those claims were not directed at an abstract idea because they addressed the problem of retaining website visitors that, absent the claimed invention, would be instantly transported away from a host’s website after clicking on an advertisement and activating a hyperlink. Id. at 1257.” slip op. at 29

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

    “1. Independent Claim 1 a) “A mobile device configured for running software applications, comprising:” Petitioner contends that Pasha discloses computer system 600, which” slip op. at 38

  • 112 supportMotion to amend, deniedDenied

    “4. Support in the Original Disclosure A motion to amend may not present substitute claims that introduce new subject matter. 35 U.S.C. § 326(d)(3); 37 C.F.R. § 42.221(a)(2)(ii) (“A motion to amend may be denied where . . . [t]he amendment seeks . . . introduce new subject matter.”). “Normally, a claim element without support in the original disclosure (i.e., the application as originally filed) merits a rejection under 35 U.S.C. § 112 for lack of written description support.” Lectrosonics, Paper 15, 7. Accordingly, a motion to amend must set forth written description support in the originally filed disclosure of the subject patent for each proposed substitute claim.” Id.” slip op. at 74

  • ExcludeMotion to exclude, grantedGranted in part

    “CTPG at 73–74. Accordingly, Rule 42.23(b) prohibits filing of new evidence other than deposition transcripts of the cross-examination of any reply witness with a sur-reply. Patent Owner does not argue that the opinions presented in paragraphs 4–13 of Dr. Mao’s declaration are within the scope of §42.23(b). See generally PO MTE Opp. Nor do we find it in the interests of justice to allow this evidence in the case file. Accordingly, we grant in part Petitioner’s Motion to Exclude paragraphs 4–13 of Exhibit 2013 pursuant to 37 C.F.R. § 42.23(b).22” slip op. at 90

  Patent outcomesUS 10,782,951 unpatentable
  § 101 eligibility§ 102 anticipationcites Alice · Enfish · Phillips · KSR · Graham
  Patents in suitUS 10,782,951
• Cradlepoint, Inc. / Honeywell International, Inc. et al. v. 3g Licensing SAAll claims unpatentable
  PTAB · Sep 15, 2022 · IPR2021-00639 · APJ Juliet Mitchell Dirba · IPR · Final written decision

  Claims 1–25 are unpatentable as obvious; the Board denied the motion to amend because proposed substitute claims 26–50 would have been obvious over Oksala or Oksala and Yoshioka.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “B. The Level of Ordinary Skill in the Art Our reviewing court has explained that “the level of skill in the art is a prism or lens through which a judge, jury, or the Board views the prior art and the claimed invention.” Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (citing Al-Site Corp. v. VSI International, Inc., 174 F.3d 1308, 1324 (Fed. Cir. 1999)). “This reference point prevents these factfinders from using their own insight or, worse yet, hindsight, to gauge obviousness.” Id.” slip op. at 10

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

    “e. Conclusion For the reasons provided above, we are persuaded that each limitation of independent claim 1 is either taught or suggested by Oksala. We are also persuaded that Oksala’s disclosure would have motivated a person of ordinary skill in the art to modify Oksala, as Petitioner contends, to yield the subject matter of claim 1. Accordingly, we conclude that Petitioner has shown, by a preponderance of the evidence, that the subject matter of claim 1 would have been obvious over Oksala.” slip op. at 52

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied

    “Accordingly, we determine that Petitioner has shown, by a preponderance of the evidence, that the subject matter of proposed substitute claims 35 and 43 would have been obvious over Oksala.” slip op. at 78

  • Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteNot shown unpatentable

    “2. Indefiniteness In its Opposition, Petitioner contends the limitations “wherein each established data connection is a packet-switched connection; and wherein each requested data connection is a packet-switched connection,” as recited in substitute claim 26, and similarly recited in substitute claims 35 and 43, render the proposed substitute claims indefinite. MTA Opp. 12 (emphases added). First, according to Petitioner, the term “packet-switched connection” does not have a claim construction, which means that it can refer to two different types of packet-switched data (i.e., Layer 1 and packet network). Id. at 12. Second, Petitioner contends that there are two recitations of “a packet-switched connection,” making it “unclear if they are the same packet-switched connection or a different one.” Id. at 12–13. Third, Petitioner contends that the claims include “another antecedent issue” because “a wireless network” appears twice in the claim. Id. at 13.” slip op. at 81

  Patent outcomesUS 8,189,611 unpatentable
  § 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 8,189,611
• Cradlepoint, Inc. / Honeywell International, Inc. et al. v. 3g Licensing S.A.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 7,551,625

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.