- Savant Technologies LLC D/B/A GE Lighting / Ledvance LLC et al. v. Feit Electric Company, Inc.All claims unpatentablePTAB · Aug 28, 2026 · IPR2024-01357 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–3, 6, 7, 9, 10, 16–21, 25, 26, and 29 are unpatentable; substitute claims 30–49 were not reached.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art We consider the asserted ground of unpatentability in view of the” slip op. at 10
- Expert testimonyPetitioner expert creditedDecided for petitioner
“E. Credibility of Dr. Doolittle Patent Owner argues that we should give no weight to Dr. Doolittle’s testimony because, “[o]n cross examination, Prof. Doolittle repeatedly contradicted himself, dodged questions, and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions.” PO Resp. 25. Patent Owner raises two major complaints about Dr. Doolittle. First, Patent Owner argues that he took inconsistent positions by asserting in these IPR proceedings that the claims were entitled to their plain and ordinary meaning, while in the parallel district court proceeding, asserting that certain claim terms were indefinite. Id. at 26–28. Second, Patent Owner argues that Dr. Doolittle “repeatedly dodged questions and tried to shoehorn new and nonresponsive opinions into his answers to Patent Owner’s questions,” and that “[d]uring cross examination Patent Owner was forced to object to Prof. Doolittle’s nonresponsive answers no less than eighteen times.” Id. at 28. We strongly disagree with Patent Owner’s characterization of Dr. Doolittle’s testimony. We have reviewed the entirety of both of Dr. Doolittle’s depositions. We are impressed with his forthrightness, candor, and good humor in the face of Patent Owner’s counsel’s aggressive questioning. Contrary to Patent Owner’s assertions, we find that his testimony was well-reasoned, forthright, honest, and entitled to significant weight. Dr. Doolittle explained the different claim construction positions We also strongly disagree that Dr. Doolittle’s answers were nonresponsive or “evasive” as Patent Owner argues. Patent Owner’s numerous attempts to “strike” portions of his testimony belie Dr. Doolittle’s efforts to honestly and in good faith respond to Patent Owner’s counsel’s questions. Ex. 2025, 22:10–23:15, 25:9–26:14, 30:14–22, 40:3-9, 58:12–59:1, 60:18–61:13, 65:1–10, 83:15–84:16, 92:15–95:20, 96:18–99:9, 102:22–106:16, 135:3–136:22. An answer is not “non-responsive” simply because it does not conform to the conclusion you want or undermines the logic underlying your questioning. Dr. Doolittle explained his answers and addressed the issues Patent Owner asked about. Accordingly, we decline Patent Owner’s invitation to give Dr. Doolittle’s testimony no weight. Instead, we assess Dr. Doolittle’s testimony on a case-by-case basis as discussed below.” slip op. at 21
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“lower wavelength might offer, there were other drawbacks that a person of ordinary skill would have to balance. But “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006). Indeed, Petitioner has shown several references—including, Basin-2005, Shimizu, and Stokes—that made this tradeoff. Moreover, “[o]bviousness does not require absolute predictability of success. . . . [A]ll that is required is a reasonable expectation of success.” In re O’Farrell, 853 F.2d 894, 903–04 (Fed. Cir. 1988). We find that the prior art of record demonstrates that a person of ordinary skill in the art at the time of the invention would have such an expectation in making the combination of Basin-2007 and Basin-2005. Accordingly, we find that Petitioner has shown by a preponderance of the evidence that there would have been motivation to combine Basin-2007 and Basin-2005 with a reasonable expectation of success.” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerationsDecided for petitioner
“7. Summary As discussed above, we find that Patent Owner has failed to show a” slip op. at 35
Patent outcomesUS 8,604,678 unpatentable§ 103 obviousness§ 112 disclosurecites Phillips · GrahamPatents in suitUS 8,604,678 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Jul 28, 2026 · IPR2025-00491 · APJ Frederick C Laney · IPR · Final written decision
Claims 1–18 are unpatentable as obvious over Beel and Dinka, with or without Christison; the Kaplan, Van de Laar, and Christison ground fails for lack of motivation to combine.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art.” PO Resp. 6. On the complete record, we adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’972 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededPlain and ordinary meaningDecided for patent owner
“Rather than addressing Petitioner’s proposals, Patent Owner states “the claims of the ’972 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Our decision in this matter does not turn on resolving any particular differences between the parties’ constructions. Therefore, because only those terms in controversy need to be construed, and only to the extent necessary to resolve the controversy, we determine that no claim term requires express construction in this proceeding and that the ordinary and customary meaning of the claim terms apply. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019).” slip op. at 11
- Expert testimonyPatent owner expert discountedDecided for petitioner
“device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125.” slip op. at 27
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“First, we agree with Patent Owner that, under the ordinary meaning of the claim language, the endpoint is an endpoint of the peripheral device, and that it must be “a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device.” Ex. 1001, 23:11–17. The limitation thus identifies a structure—an endpoint, residing on the peripheral device, that is a source or sink and that corresponds to (is “of”) the functional device—through which the communication recited in subsequent element (g) is carried out. By its terms, it imposes no requirement as to the direction in which data flows; it requires only that the endpoint be a data “source” or a data “sink” that is able to “store or emit” data. The operative transmit-and-receive communication “from the functional device to the processing device via the . . . endpoint” is recited in subsequent element (g), which we take up separately below. The disputed question under this limitation is therefore the structural one: whether Beel discloses, on the peripheral device, an endpoint that is “of the functional device.” Because the inquiry is structural and non-directional, we are not persuaded that the audio-out orientation of Beel’s described embodiment, on which Patent Owner relies, is dispositive of this limitation. device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125. Third, we find that the endpoint Beel discloses is a data source or a data sink that is “able to store or emit data, of the functional device.” We begin with the words of the limitation. The endpoint need only be “able to store or emit data”—language of capability, not a requirement that particular data actually traverse the endpoint in operation, and still less in a particular direction. And the endpoint is defined by the character of the data it handles: it is “a data source or a data sink,” which the ’972 patent instructs An audio endpoint, so understood, is characterized as an audio source or sink; its structure is not tied to any single instance of an audio device. On that understanding, Beel’s disclosure establishes the required capability directly. Beel discloses that “audio data is captured through a virtual sound card interface added as a logical device over the physical interface provided in the peripheral device,” Ex. 1005 ¶ 43, that the peripheral device “acts as a composite device comprising for instance a (virtual) audio speaker device,” id. ¶ 317, and that “audio data is captured at this interface . . . internally in the peripheral device 32” and streamed over the communications network, id. ¶ 319. Beel thus shows the endpoint on the peripheral device actually storing and emitting audio—and, correspondingly, video—data, which is the very type of data produced and consumed by the audio/visual functional devices connected to the base unit, including the microphones, cameras, speakers, and displays. Id. ¶ 120. An endpoint shown to store or emit audio and video data is necessarily one that is “able to store or emit” such data; the capability the limitation requires is thus established by Beel’s disclosure.” slip op. at 26
Patent outcomesUS 10,684,972 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,684,972 - Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentablePTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision
Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.
RulingsFinal written decision- BurdenOther
“Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2
- Skill levelOther
“2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed
“1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17
Patent outcomesUS 11,069,337 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,069,337 - Rocket Media, LLC D/B/A Launch Labs v. Fullthrottle Technologies, LLCAll claims unpatentablePTAB · Jun 9, 2026 · IPR2025-00148 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Doughty and Van Boucq, and over Doughty, Van Boucq, and Maginnis.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person of ordinary skill in the art in June 2021 would have had “(1) at least a bachelor’s degree in computer science, computer engineering, electrical engineering, or an equivalent field plus at least one year of experience working on computer networking, or (2) at least 3 years of experience working on computer networking, even without a formal degree.” Pet. 14 (citing Ex. 1007 ¶¶ 44–47). Patent Owner does not contest Petitioner’s proffered definition. PO Resp. 23. Petitioner’s proposed definition appears to be consistent with the disclosure of the ’947 patent, and we adopt it for purposes of this Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that the prior art itself may “reflect[] an appropriate level” of ordinary skill in the art) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We determine that no terms require express construction to resolve the parties’ disputes in this case, but address certain claim construction arguments made by the parties in the analysis below. See id.; Inst. Dec. 11 (determining that “no express claim construction is necessary for any claim terms”); PO Resp. 23 (agreeing that “no express constructions are necessary to resolve this IPR”). slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageDisclaimer not foundDecided for petitioner
“We find that Petitioner has shown that the combination of Doughty and Van Boucq accounts for these limitations. We are not persuaded by Patent Owner’s arguments that claim 1 somehow excludes, what Patent Owner calls, the “Unique Identifier/Tracker Embodiment.” See PO Resp. 27, 31. Beginning with the language of the claims, the claims are silent as to where the “location data” recited in limitation 1[c] is stored. See Tr. 21:7– 16 (Patent Owner agreeing that “the stored location data does not actually have a required location at all” in the claim, and need not be stored in a database). Nor does Patent Owner direct us to any claim language that would specifically exclude “location data” stored on the user’s device. See Sur-reply 2–3. “The patentee is free to choose a broad term and expect to obtain the full scope of its plain and ordinary meaning unless the patentee clearly redefines the term (lexicography) or disavows claim scope (claim disavowal).” Aortic Innovations LLC v. Edwards Lifesciences Corp., 159 F.4th 1, 8 (Fed. Cir. 2025) (citing Thorner v. Sony Comput. Ent. Am. LLC, 669 F.3d 1362, 1367 (Fed. Cir. 2012)). Patent Owner directs us to statements in the Specification, stating “[f]or example, the computing device may access a database or other storage location that maintains a mapping of unique identifier to a browser session, a user computing device, and/or location data.” Ex. 1001, 9:52–55; see also id. at 39:26–30 (same), 43:55– 59 (same). But none of those passages amounts to lexicography or disavowal of claim scope. Indeed, when read in their full context, these passages support a broad reading, not a narrow reading, of the claims. The full passage of the Specification states: The computing device may determine, at 406, whether there is a unique identifier that is associated with the user (e.g., the user computing device, the browser, and/or the browser session) stored on the computing device. For example, the script may inform the computing device that there is no unique identifier for the user computing device. The computing device may determine that there is no unique identifier associated with the user computing device when there is no location data stored for the user computing device. For example, the computing device may access a database or other storage location that maintains a mapping of unique identifier to a browser session, a user computing device, and/or location data. Additionally or alternatively, the computing device may determine whether there is a unique identifier for associated with the user based on presence of a location tracker (e.g., cookie) installed in the browser application on the user computing device. Ex. 1001, 9:43–59. The passage above is full of language that indicates that the patentee did not intend to limit the claims to a single embodiment. Indeed, the specific portion of the passage cited by Patent Owner begins with “[f]or example” and further states “[a]dditionally or alternatively, the computing device may determine whether there is a unique identifier for associated with the user based on presence of a location tracker (e.g., cookie) installed in the browser application on the user computing device.” Id. at 9:52–59 (emphasis added). Moreover, the Specification states “[a]dditionally or alternatively, the computing device may determine the location data using the tracker installed in the browser application on the user computing device.” Id. at 10:2–5. The Specification also explains that the tracker may “maintain data related to the user and/or user computing device.” Id. at 12:62–63. Based on these disclosures, we find that the Specification supports a reading where the location data are stored in the user computing” slip op. at 25
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“We find persuasive Petitioner’s reasoning that a POSITA would have been motivated to modify Doughty, based on Doughty’s own teachings regarding cookies and similar files, and would have recognized that the techniques of Van Boucq would have offered an efficient and commonly used way to determine whether the user already has been assigned a unique identifier. See Ex. 1007 ¶ 153. Patent Owner’s arguments about the precise contents of Van Boucq’s connection cookie attack Van Boucq individually and ignore the combination and modifications that Petitioner proposes. In the combination, Petitioner proposes incorporating the unique identifier from Doughty into Van Boucq’s connection cookie. See Pet. 26 (citing Ex. 1008, 16:59–17:33; Ex. 1007 ¶ 153). As for Patent Owner’s contention that “[n]othing in the record suggests that Van Boucq’s connection cookie could contain any information about either Doughty’s table 105 Profile ID or Doughty’s hashed email address,” PO Resp. 33, as Dr. Gottesman testifies, “[a] cookie is a small piece of data (text file).” Ex. 2012 ¶ 55. We fail to see why a skilled artisan at the time of the invention would have any difficulty incorporating Doughty’s alphanumeric unique identifier into a text file. See Ex. 1007 ¶¶ 153, 166. Thus, we find that Petitioner has shown a motivation to combine Doughty and Van Boucq for these limitations.” slip op. at 30
Patent outcomesUS 11,556,947 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,556,947 - Mediatek Inc. v. Parkervision, Inc.All claims unpatentablePTAB · May 22, 2026 · IPR2024-00796 · APJ Iftikhar Ahmed · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Nevo and Avitabile, Young and Estabrook, and Young, Estabrook-1988, and Estabrook-1989.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“Network LLC, 929 F.3d 1350, 1357 (Fed. Cir. 2019). On its face, the language “energy transfer signal” does not specify any restrictions on the type of system in which it is utilized, nor its characteristics. In the context of claims 1 and 11, the “energy transfer signal” is the basis on which the “switch” operates, so as to “sub-sample and transfer energy from a first electromagnetic (EM) signal.” Ex. 1001, 50:63–65, 51:56–58. Accordingly, based on the claim language, the term “energy transfer signal” need only be a signal for operating a switch to sub-sample and transfer energy from an electromagnetic signal. That is its plain and ordinary meaning.” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“’686 patent broadly includes knowledge and experience as to RF circuit design. See supra § III.B. Petitioner contends that “Nevo’s transceivers [102a/102b] are for Bluetooth and IEEE 802.11,” and that a person of ordinary skill in the art would have understood that both protocols “required down-conversion in their receivers to obtain a baseband signal.” Id. at 35 (citing Ex. 1004, 4:45–50; Ex. 1002 ¶ 118). Nevo’s disclosure would have motivated a person of ordinary skill in the art to look to Avitabile, which provides the circuit level detail for down-converters. See Ex. 1006, Abstract. Avitabile specifically provides circuitry for down-conversion in the s-band frequency range, which is in the range of Bluetooth and IEEE 802.11 (2.4 GHz). Id. at Abstract, Figs. 6, 7. Accordingly, we determine a person of ordinary skill in the art would have been motivated to look to down-converters in the range of frequency needed, and would have been motivated to combine Avitabile’s teachings with those of Nevo, with a reasonable expectation of success.” slip op. at 55
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
Patent outcomesUS 7,483,686 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,483,686 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co. Ltd.Adverse judgmentPTAB · May 19, 2026 · IPR2025-01327 · APJ Sheila F Mcshane · IPR · Adverse judgment
The Board entered adverse judgment against Throughtek on claims 1–19 after finding it abandoned the contest by failing to file mandatory notices or respond to the show-cause order.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“The Order to Show Cause explained that under 37 C.F.R. § 42.73(b), “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” Paper 8, 3. The Order to Show Cause also explained that failure to participate in a proceeding, such as failure to file mandatory notices as required under 37 C.F.R. § 42.8, may be considered abandonment of the contest and result in adverse judgment against Patent Owner under 37 C.F.R. § 42.73(b). Id. (citing Cellpak, Inc. v. Mambate USA Inc., IPR2021-00007, Paper 4 at 2 (PTAB Mar. 23, 2021)). The Order to Show Cause gave Patent Owner ten calendar days to show cause why adverse judgment should not be entered against it. Id. Patent Owner did not respond to the Order to Show Cause. More than ten calendar days have elapsed since the date the Order to Show Cause was entered, and Patent Owner has not filed mandatory notices. In view of Patent Owner’s failure to file mandatory notices within the specified time period, we determine that Patent Owner has abandoned the contest. Pursuant to 37 C.F.R. § 42.73(b)(4), we construe Patent Owner’s abandonment of the contest as a request for adverse judgment. Under these circumstances, we determine that entry of judgment against Patent Owner is appropriate.” slip op. at 3
NonePatents in suitUS 9,727,655 - PTAB · May 13, 2026 · IPR2025-01444 · APJ George R Hoskins · IPR · Adverse judgment
The Board granted Patent Owner’s request for adverse judgment after it disclaimed the entire patent term, entering judgment against claims 1–6.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request entry of adverse judgment against itself at any time during an inter partes review proceeding. See 37 C.F.R. § 42.73(b). In addition, “[a]ctions construed to be a request for adverse judgment include: (1) Disclaimer of the involved application or patent; [and] (2) Cancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” Id. Because Patent Owner has explicitly requested adverse judgment against itself pursuant to Rule 42.73(b), and has disclaimed the entire term of the ’584 patent, Patent Owner’s request for adverse judgment is granted. ORDER In consideration of the foregoing, it is hereby: ORDERED that Patent Owner’s Request for Adverse Judgment is granted; and FURTHER ORDERED that adverse judgment is entered against Patent Owner with respect to claims 1–6 of the ’584 patent.” slip op. at 3
NonePatents in suitUS 7,547,584 - PTAB · May 13, 2026 · IPR2025-01082 · APJ David C Mckone · IPR · Adverse judgment
The Board granted Patent Owner’s request for adverse judgment after it disclaimed the entire patent term, entering judgment against claims 1–10.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request entry of adverse judgment against itself at any time during an inter partes review proceeding. See 37 C.F.R. § 42.73(b). In addition, “[a]ctions construed to be a request for adverse judgment include: (1) Disclaimer of the involved application or patent; [and] (2) Cancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” Id. Because Patent Owner has explicitly requested adverse judgment against itself pursuant to Rule 42.73(b), and has disclaimed the entire term of the ’181 patent, Patent Owner’s request for adverse judgment is granted.” slip op. at 3
NonePatents in suitUS 6,888,181 - Tableau Software, LLC v. Icharts LLCAll claims unpatentablePTAB · May 7, 2026 · IPR2024-01387 · APJ Iftikhar Ahmed · IPR · Final written decision
Claims 1–16 are unpatentable under the instituted obviousness grounds, including Becerra, the QlikView Manuals, and combinations with other references.
RulingsFinal written decision- ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part
“why it is trustworthy and how it archives dates by which the webpages were accessible, as this is an information resource on which librarians reasonably rely. See FED. R. EVID. 703. We agree with Petitioner that Dr. Hall-Ellis does have personal knowledge of the facts stated in the remaining testimony (e.g., what she actually downloaded from websites), and that FEDERAL RULE OF EVIDENCE 602 is inapplicable to her testimony offered as an expert. See Pet. Opp. 5–6 (citing Ex. 1030 ¶¶ 26, 29–32, 35, 37–39). We find her testimony to be relevant to the issues presented and specifically to whether the QlikView documents were publicly accessible. We also find no danger that the testimony would confuse the issues or mislead the Board or present unfair prejudice to Patent Owner. Accordingly, we deny Patent Owner’s Motion as to the remaining portion of Dr. Hall-Ellis’s declaration.” slip op. at 92
- Strike new argumentNew argument disregardedGranted
“FURTHER ORDERED that Petitioner’s Motion to Strike portions of Patent Owner’s Reply on its Motion to Exclude (Paper 32) is granted; and” slip op. at 102
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“1. Motivation to Combine Becerra and Couckuyt Petitioner argues that a person of ordinary skill in the art would have been motivated to combine the teachings of Becerra and Couckuyt because such a person would have recognized that Couckuyt discloses useful techniques of assigning data to Becerra’s charts, including assigning data to each axis. Pet. 34 (citing Ex. 1005 ¶¶ 19, 52, Fig. 5; Ex. 1003 ¶ 224). Petitioner contends that Couckuyt discloses associating data from a “spreadsheet document” with a chart, such as a “bar graph.” Id. at 35 (citing Ex. 1006, 6:1–37; Figs. 3a, 3c). below. Petitioner’s annotations to Figure 4 identify “Drop Zones” in red and “Data Fields” in Blue. Id. at 36. Petitioner contends Couckuyt discloses a “drag-and-drop user interface (DDUI) . . . associated with a data source, such as the two-dimensional data source 300,” and Figure 4 illustrates the DDUI permitting “value data fields and the characteristic data fields . . . to be dragged and dropped into drop zones.” Id. at 35–36 (citing Ex. 1006, 7:10–13). Petitioner contends that a “primary benefit of the charting DDUI is that the user can quickly change the data that is being presented in the chart,” and using Couckuyt’s techniques, a user can “quickly change the data” and see the desired effects. Id. at 36 (citing Ex. 1006, 1:18–19; Ex. 1003 ¶ 228). Petitioner contends that when Becerra’s control panel includes multiple charts, Couckuyt’s techniques would allow dragging-anddropping data from a data source to multiple charts, and would simplify the process of assigning data to multiple control panel components. Id. at 36–37 skill in the art would have also had a reasonable expectation of success combining Becerra with Couckuyt because the combination would amount to nothing more than incorporating Couckuyt’s well-known drag-and-drop techniques into Becerra’s system. Id. at 37 (citing Ex. 1003 ¶¶ 229–231). Patent Owner responds that Couckuyt focuses on selecting a data icon that corresponds to dragging and dropping data fields, not dragging and dropping data, while Becerra teaches that selecting various data ranges from the spreadsheet is desirable. PO Resp. 36–37 (citing Ex. 1004 7:48–52; Ex. 2001 ¶ 146). According to Patent Owner, a person of ordinary skill in the art would not have been motivated to merely select data fields that do not limit the selected data in any way. Id. Patent Owner further argues Becerra’s method of binding components to a spreadsheet range and extracting formulas from a spreadsheet teaches away from the multiple chart generation scheme of Couckuyt that uses drag and dropping of data fields. Id. at 37. According to Patent Owner, Couckuyt is directed to the need for a charting DDUI that can generate multiple charts at the same time and such a need does not exist in Becerra which in turn is focused on creating a control panel that is an interactive graphics simulation. Id. (citing Ex. 1004, 1:66–67, 2:5–8; Ex. 1005 ¶ 11; Ex. 2001 ¶ 148). Based on our review of the complete record, we determine that” slip op. at 31
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner
“2. Whether QlikView Manuals Qualify as Prior Art Petitioner argues that “the QlikView Manuals describe a well-known system and are printed publications available to the public at least by July 8, 2008.” Pet. 7–9. Petitioner offers ample evidence to demonstrate the QlikView Manuals were publicly accessible by July 8, 2008. See id. (citing Ex. 1008; Ex. 1009; Ex. 1014–1023; Ex. 1003 ¶ 129–140; Ex. 1030;11 Ex. 1068 ¶¶ 4–7; Ex. 1032; Ex. 1033). Petitioner contends in 2008, QlikView was a well-known software product sold by QlikTech International AB (“QlikTech”). Id. at 8 (citing Ex. 1003 ¶ 129; Ex. 1030 ¶ 23; Ex. 1068 ¶¶ 4–7). Petitioner asserts that QlikTech announced that QlikView version 8.50 was scheduled for release on June 30, 2008, and QlikTech’s website added the “QlikView 8.50” hyperlink by July 8, 2008. Id. (citing Ex. 1003 ¶¶ 129–131; Ex. 1022, 1; Ex. 1068 ¶ 7). Petitioner contends that, as of July 8, 2008, a person of ordinary skill in the art would have understood that they could view the QlikView Manuals in the installation package. Id. (citing Exs. 1014–1017; Ex. 1003 ¶¶ 131–132; Ex. 1068 ¶ 7). Petitioner further contends that the QlikView Manuals were also available on QlikTech’s website as of this 11 As discussed below (see infra § IV.A), we grant Patent Owner’s Motion to Exclude as to certain portions of Exhibit 1030 and do not give them any weight. However, we deny Patent Owner’s Motion as to the remaining portions of Dr. Hall-Ellis’s testimony as well as Ms. Lofton’s testimony and various other exhibits proffered by Petitioner to show public accessibility of the QlikView manuals as of July 8, 2008. QlikView 8.50 was published on July 8, 2008. Id. at 8–9 (citing Exs. 1008, 1009, 1017, 1059, 1060; Ex. 1030 ¶¶ 29, 37). In its Patent Owner Response, Patent Owner does not contest that the QlikView Manuals were published and publicly available by July 8, 2008. PO Resp. 50 n.2 (noting only that Patent Owner intends to move to exclude evidence Petitioner relies on to establish the publication date for QlikView Manuals); Tr. 45:3–19. We are persuaded that Petitioner has shown by a preponderance of the evidence that the QlikView Manuals were publicly available as of July 8, 2008.12” slip op. at 50
Patent outcomesUS 8,271,892 unpatentable§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,271,892 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01439 · APJ Frederick C Laney · IPR · Final written decision
Claims 1–11 and 13–21 are unpatentable under § 103 based on Ono and Corbett and Uchida and Grimshaw; the Board did not find Ichieda unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner contends that a person having ordinary skill in the art would have had at least a Master’s Degree in Electrical Engineering with . . . five years of work experience in computer science and embedded systems, or Master’s Degree in Computer Science with . . . five years of work experience in electrical and computer engineering and embedded systems. Additional educational experience could substitute for some of the work experience. level of skill in the art.” PO Resp. 10. We adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’951 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“determine that none of the claim terms the parties provide constructions for require an express construction in this proceeding. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019). The parties do appear to disagree on the meaning of “trigger,” however. Although neither party actually identifies that term as needing interpretation and neither party actually provides a claim construction analysis to support its respective position, the parties do dispute whether the evidence presented shows a “trigger,” both presumably giving that term its plain and customary meaning. In other words, while both parties appear to agree “trigger” carries its plain meaning, in application, the parties’ dispute regarding the particular limitations including that term appears to turn, not over what the evidence discloses, but only on whether the disclosure satisfies the plain meaning of “trigger” (see infra § II.E.2). Accordingly, while we apply the plain meaning of “trigger” in this proceeding, and in doing so, we address which party has properly applied the plain meaning and, in doing that, we address the scope properly afforded to “trigger.” That analysis, however, is done below in the context of the limitation in which this issue arises (see id.).” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“has now been developed, and in view of both parties’ arguments, we find Petitioner has persuasively shown that modifying Ono’s peripheral device (i.e., communications module 44) to include an input device/physical actuator like the one described for Ono’s remote controller 69 to control the display of image data from a particular user’s computer would have been obvious to a skilled artisan at the time of the invention. More specifically, Petitioner has shown persuasively Ono shows that the use of an input device/physical actuator to send a signal that causes a participant’s computer to transmit and control the image data presented on a shared display in an image display system was a known technique (see Ex. 1005 ¶¶ 7, 44–48, 66– 71, 77–78, 80–89, 144, Figs. 3, 6, 8, 9; Ex. 1002 ¶¶ 85–100, 121–127) and available location for such an input device/physical actuator to initiate the transmission of data (see Ex. 1007 ¶¶ 6, 18, 20, 22–23, 26, 28, 46, Fig. 1; Ex. 1002 ¶¶ 92–100). Petitioner has also persuasively shown that a skilled artisan recognized benefits to giving a participant the ability to locally control the display of their computer’s image data. See Ex. 1002 ¶¶ 87–91; Ex. 1008 ¶¶ 4, 19–20, 27–28; Ex. 1009 ¶¶ 10–13, 39–10, 70–72. When Ono and Corbett are considered together as a whole from the perspective of a skilled artisan, therefore, it is clear that applying a similar input device/physical actuator to Ono’s peripheral device would have been recognized to result in the benefit of providing a participant with the same ability to send a signal that causes a participant’s computer to transmit and control the image data presented on a shared display from their computer within an image display system. As a result, a motivation has been established because the combination is an application of a known technique to derive a known benefit using prior art elements according to their established functions. Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1380 (Fed. Cir. 2023).” slip op. at 24
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“that, from their perspective, the plain meaning of the term “trigger” does not exclude intervening steps between a user’s action on an input device and the ultimate transfer of the user selected arbitrary media content. Pet. Reply 11– 12 (indicating that “trigger” encompasses “a process that begins with and thus is triggered by a user pressing a button followed by an ‘image transfer’ from a PC to a projector”). For its part, Patent Owner maintains (at least implicitly) that intervening steps are excluded from the plain meaning. Neither party addresses with more specificity why, or why not, the scope of “trigger” supports their positions, however. Having now the complete record before us, we find that out preliminary assessment was wrong because the plain meaning of the term “trigger” does not exclude intervening steps between the cause-and-effect relationship of the trigger and the result it is intended to cause. Take, for example, a simple gun. Pulling the “trigger” to fire a gun necessarily includes intervening steps to occur: the trigger releases a hammer that, in turn, contacts a blasting cap within a bullet casing, which is what actually causes the gunpowder to ignite (i.e., fire) and expel the bullet. And there is no evidence in this record to suggest that this customary understanding of the word “trigger” is any different in the electrical arts, other than the trigger and result are generally electrical in nature, rather than mechanical. We find no clear disavowal of claim scope within the intrinsic record of the ’951 patent to indicate that the term “trigger” was intended to be understood any differently to exclude any intervening steps between a user’s action on an input device and the resulting transfer of user selected arbitrary media content. intervening steps would exist because the input device does not actually do the transferring of the media content; instead, the claims recite the transferring is “from the transmitter to the wireless communications network and [then] to the base node.” See Ex. 1001, 11:3–48, 27:62–28:1 (claim 1), 28:62–67 (claim 9), 29:42–46 (claim 16), 30:36–44 (claim 21) (emphasis added). A skilled artisan would have recognized that there would be intervening steps between the input device being acted upon and the content being displayed by base node’s display. See Ex. 1083 ¶¶ 11–12. In the claims, the input device is analogous to a gun’s trigger, the user carrying out a user action on the input device is analogous to pulling a gun’s trigger, and the transfer of user selected arbitrary media content is analogous the gun expelling a bullet. In both cases, there can be, and usually are, intervening steps, moreover, in both cases, inadvertent things can happen that may prevent the intended result (e.g., in the case of a gun, the hammer can jam; in the case of an input device, a connection can be rejected). Nevertheless, in both cases, the trigger is the thing that initiates an automated process that leads to a particular result, unless a conditional error occurs.” slip op. at 31
Patent outcomesUS 11,422,951 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,422,951
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.