- Apple Inc. v. Proxense, LLCAll claims unpatentablePTAB · Sep 17, 2026 · IPR2025-00562 · APJ Thu A Dang · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board also finds the claims unpatentable under the Broadcom grounds.
RulingsFinal written decision- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“IPR2024-00783, Ex. 1001, 22:36–49. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112 ¶ 6. See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112 ¶ 6 is not overcome.” slip op. at 17
- Skill levelOther
“differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
- Expert testimonyPetitioner expert creditedDecided for petitioner
“We find persuasive Dr. Wolfe’s supporting testimony that a POSITA would have understood the terms “PDK” and “RDC” to have “definite structure.” Ex. 1013 ¶¶ 35–56. In particular, we find persuasive Dr. Wolfe’s testimony that the term “PDK,” for example, “encompasses at least ‘a collection of circuit components that includes an antenna, a transceiver, and a controller and memory for storing information particular to a user.’” Id. ¶ 35. Dr. Wolfe’s testimony is consistent with the Specification of the ’188 patent. See Ex. 1001, 5:42–6:7, 3:48–62. In particular, the Specification of the ’188 patent describes a microchip that stores information in memory and responds through an antenna when probed, which is consistent with Dr. Wolfe’s testimony. Id.; Ex. 1001, 1:30–62.” slip op. at 19
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
Patent outcomesUS 9,049,188 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,049,188 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Sep 1, 2026 · IPR2025-00914 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–19 are unpatentable as obvious over Menon, Trefethen, RS6000, and POEref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’679 patent, the prior art of record, and the testimony of both experts.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Petition relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard. Pet. 12–13 (citing 37 C.F.R. § 42.100(b)). The Petition also addresses the construction of “peer-to-peer architecture” recited in independent claim 1 of the ’679 patent, a limitation we need not construe to resolve the parties’ dispute in this proceeding. Id. at 13; see, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Owner relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard without further analysis. Resp. 7.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“RS6000 with Menon, namely because RS6000 provides an overview of the IBM SP2 multiprocessor and Menon teaches the use of “IBM SP2, a modern high performance distributed memory multiprocessor” used in the MultiMATLAB system. Id. at 24–25 (citing Ex. 1003 ¶¶ 142–145; Ex. 1005, 5–6, 14; Ex. 1007, 1, 11). The Petition also explains why POEref pertains to the field of cluster computing in a parallel operating environment. Id. at 26 (citing Ex.1008, 11 (“PE Software is designed to run on an … RS/6000 network cluster”)); (further citing Ex. 1001, 1:14–15; Ex. 1003 ¶¶ 146–149). The Petition contends that a POSITA would have been motivated to combine the teachings of POEref with Menon “because Menon suggests the combination by teaching that MultiMATLAB uses ‘POE, IBM's Parallel Operating Environment.’” Id. at 26–27 (citing Ex. 1005, 6); (further citing Ex. 1003 ¶¶ 150–153; Ex. 1005, 14; Ex. 1008, 11, 46). We agree with Petitioner’s analysis. We find the Petition’s argument and evidence of a motivation to combine the asserted prior art references in the manner claimed to be compelling, persuasive, consistent with the disclosures in the references, which include internal cross-references to each other, and supported by the expert testimony of Dr. Bajaj.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner
“skill, upon reading the reference, would be discouraged from following the path set out in the reference, or would be led in a direction divergent from the path that was taken by the applicant.” In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). Patent Owner argues that Menon teaches away from a combination with Trefethen because “Menon expressly states that Trefethen’s first-generation architecture is inadequate for the objectives that motivated the newer design.” Resp. 35–37. The evidence does not support Patent Owner’s position. First, Patent Owner’s teaching away argument is inconsistent with the strong evidence of a motivation to combine Menon and Trefethen discussed above. Second, Patent Owner’s teaching away argument is contrary to the evidence of record for the reasons given in Petitioner’s Reply. Reply 13–15 (e.g., “Menon explicitly cites Trefethen and explains that Menon builds on the teachings of Trefethen.”) (citing Pet. 22; Ex. 1003 ¶ 70; Ex. 1005, 1–3; Ex. 1163 ¶¶ 47–53). We are further persuaded by Dr. Bajaj’s reply testimony: the “MultiMATLAB teachings in Trefethen. In fact, Menon describes enhancing the system of Trefethen. For example, Menon describes a list of “goals” already achieved by MultiMATLAB and then states that the architecture has been “redesigned to achieve two further goals.” One of these two “further goals” is “extensibility,” which Menon achieves by its description of adding “MEX routines” to the system of Trefethen. Far from showing an “incompatibility” between Menon and Trefethen as the POR argues, Menon’s addition of the “MEX routines” to MultiMATLAB shows that such a modification was within the capabilities of a POSITA, because the authors of the Menon paper actually implemented the modification. Ex. 1163 ¶ 49 (citing Ex. 1005, 1–3). Dr. Bajaj’s testimony is unrebutted, credible, and supported by the record. We agree with Dr. Bajaj’s reasoning, which is based on direct quotes in Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶¶ 50–52. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine the teachings of Menon and Trefethen. RS6000 and POEref are specifically referenced in Menon-Trefethen and add operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Such facts are inconsistent with Patent Owner’s teaching away and lack of motivation arguments.” slip op. at 24
Patent outcomesUS 12,021,679 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 12,021,679 - Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentablePTAB · Aug 26, 2026 · IPR2025-00913 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–30 are unpatentable: claims 1–25, 27–28, and 30 as obvious over Menon, Trefethen, RS6000, and POEref; claims 26 and 29 over those references plus MPIref.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and experience of a POSITA. We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’034 patent, the prior art of record, and the testimony of both experts.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther
“processor,” “multi-core” processor, or “singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’” as Patent Owner contends. Resp. 11–12, 21; see also Ex. 1163 ¶ 22 (“The claim does not recite ‘single chip,’ ‘single package,’ ‘single die,’ or ‘single multi-core microprocessor.’”). Nor do the claims recite a plurality of processing cores “within” a single-chip package or read as “multi-core within a processor” as argued by Patent Owner. Resp. 12–14; Sur-Reply 2; see Reply 6 (citing Ex. 1163 ¶ 23 (“Thus, the phrase ‘with a plurality of processing cores’ identifies the required processing resources associated with the hardware processor; it does not import a packaging limitation.”)). The claims do recite a hardware processor “with” a plurality of processing cores; a critical distinction even Patent Owner reads as open-ended, i.e., as a hardware processor that “comprises” a plurality of processing cores. See Resp. 11 (“the claims require a singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’”). Consequently, the claim language does not support Patent Owner’s proposed construction of “a . . . hardware processor with a plurality of processing cores” as a single multi-core processor. cores it contains” in reliance on a parsed description in the ’034 patent specification: The specification explains: “Each processor can contain one or more processor cores that are capable of single-threaded execution. Processor cores are generally independent microprocessors, but more than one can be included in a single-chip package.” Id. at 1212 (partially quoting Ex. 1001, 5:11–16); Sur-Reply 2. The quoted description does not support Patent Owner’s contention that the claimed “a . . . hardware processor with a plurality of processing cores” must be limited to a “single multi-core processor” that “locates multiple cores within a ‘single-chip package,’” i.e. limited to a single multi-core microprocessor such as “a Core 2 Duo is one processor package with two cores.” Resp. 12– 13, 21 (citing Ex. 1001, 7:15–25). The description quoted above from column 5, moreover, describes a “processor” that “can contain one or more processor cores” each of which can be an independent microprocessor. Reply 2–3 (citing Ex. 1001, 5:11–16; Ex. 1163 ¶¶ 10–14). As Petitioner emphasizes, the specification distinguishes a “processor” from a “microprocessor” and describes a “processor” that “can be one or more general purpose single-core or multi-core microprocessors,” rather than limiting a “processor” to a single multi-core microprocessor. Reply 3–5 (citing Ex. 1001, 7:14–36, Fig. 1; Ex. 1163 ¶¶ 15–18).” slip op. at 13
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“art because they pertain to the same “field of cluster computing” as the ’034 patent and “are reasonably pertinent to the problem of the ’034 patent, namely, executing a single program on multiple nodes.” Pet. 22 (citing Ex. 1001, 1:14–15; Ex. 1003, ¶¶ 65–69; Ex. 1005, 2; Ex. 1006, Abstract). The Petition emphasizes that Menon expressly cites and builds on the MultiMATLAB system taught by Trefethen. Id. (citing Ex. 1003 ¶ 71; Ex. 1005, 1–2). The Petition contends that: combination of prior art elements according to known methods (executing MATLAB code on a multiprocessor system) to yield the predictable result discussed in both papers: the MultiMATLAB system executing MATLAB in parallel to perform mathematical calculations. Id. at 22–23 (citing Ex. 1003 ¶ 70; Ex. 1005, Abstract; Ex. 1006, 2–7). The Petition further contends that a POSITA would have found it predictable to combine Trefethen with Menon with a reasonable expectation of success “because researchers had a strong desire to parallelize MATLAB.” Id. at 23–24 (citing Ex. 1003 ¶ 73; Ex. 1005, 2; Ex. 1006, 11–12.)” slip op. at 27
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“A POSITA would have had an especially strong reason to read these references together because they address the same project, the same MATLAB-based parallel-computing problem, and the same MultiMATLAB command environment. Menon expressly identifies Trefethen’s MultiMATLAB work and then describes a redesigned architecture that preserves the same user-level objective––parallel MATLAB computations—while improving implementation details and extensibility. A POSITA therefore would not view the references as mutually exclusive alternatives. Rather, a POSITA would understand Trefethen as teaching specific MultiMATLAB commands and examples, including Eval, Send, Recv, and the architecture was implemented and improved in a later version. Ex. 1163 ¶¶ 71–72 (emphases added). We find the above reasoning persuasive and adopt it as our own. Petitioner and Dr. Bajaj demonstrate a sound technical motivation for a POSITA—someone having a bachelor’s degree in computer science, computer engineering, or electrical engineering and two years of experience working in the field of cluster computing or parallel processing—to combine Menon and Trefethen: to improve MATLAB’s operational performance and extensibility in a parallel operating environment. Menon builds on Trefethen to improve and extend the parallel processing capabilities of MultiMATLAB: “This system will enable users to access high-performance parallel routines from within the MATLAB environment, to extend the environment with new parallel routines, and to use these routines to develop parallel applications with the MATLAB language.” Ex. 1005 Abstract. Menon is intended to be read in conjunction with Trefethen, as would be expected from two references generated by the same research group at the same university addressed to the same technical subject matter about a year apart. Ex. 1005, 1; Ex. 1006, Ex. 1086 ¶¶ 65, 101, 102. The very first citation in Menon is to Trefethen. Ex. 1005, 2, 16.” slip op. at 30
Patent outcomesUS 11,570,034 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,570,034 - 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 - 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 - Apple Inc. v. DH International Ltd.All claims unpatentablePTAB · Apr 16, 2026 · IPR2025-00172 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Suga and Gorsuch; the Board denied Patent Owner’s motion to exclude.
RulingsFinal written decision- ExcludeMotion to exclude, deniedDenied
“Patent Owner also asserts prejudice for “not knowing” which Suga Exhibit “the Petitioner and Petitioner’s expert is relying on (see Exhibit 1021 and 1022),” without further explanation. Mot. Reply 6. Exhibit 1022 is a dictionary definition of “node.” How this relates to Patent Owner’s argument of prejudice is not explained. Id. at 5–6. The Board perceives no difficulty following Petitioner’s arguments and evidence, which cite Suga Exhibit 1005, including the testimony of Dr. Buehrer regarding the English language translation of Suga, which is identical in Exhibits 1005 and 1017. Patent Owner, moreover, opted not to depose Dr. Buehrer, did not file a deposition transcript of Dr. Buehrer in this proceeding, and does not allege any difference or substantive deficiency in the English language translation in Suga Exhibits 1005 and 1017, which are identical. We fail to see any prejudice to Patent Owner.” slip op. at 84
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“d. Conclusion for Claim 1 For the reasons given above, we determine the Petition establishes by” slip op. at 60
Patent outcomesUS 9,022,294 unpatentable§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,022,294 - Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentablePTAB · Apr 7, 2026 · IPR2024-01436 · APJ Meredith C Petravick · IPR · Final written decision
Claims 1–3, 9–11, 19, 21, and 22 are unpatentable as obvious over Kaplan, Ahmed, and Deforche, and over Maeda, Ahmed, and Deforche.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that a person having ordinary skill in the art (POSITA) would have had at least a Master’s Degree in Electrical Engineering and five years of work experience in computer science and embedded systems, or a Master’s Degree in Computer Science and five years of work experience in electrical and computer engineering and embedded systems. the work experience. Pet. 10 (citing Ex. 1002 ¶¶ 36–37). Patent Owner does not dispute Petitioner’s definition of the level of ordinary skill in the art. PO Resp. 12. We adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’002 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner
“term “pre-installed generic driver.” Pet. 13; PO Resp. 9–10. Those proposed constructions are consistent with the lexicographic definition provided in the ’002 patent. In a section titled “Definitions,” the ’002 patent states: The term “pre-installed generic driver” is intended to mean a driver which is installed on a processing device such as a computer as a standard driver, e.g. is installed with the installation of the operating system. Such a driver is standard for the operating system and can drive a standard class of peripheral devices coupled to or connected to the processing device. Ex. 1001, 14:32–38. We apply this lexicographic definition in our analysis below.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“a) Whether Dr. Almeroth’s Testimony should Be Given Little Weight Patent Owner argues that we should give little weigh to the testimony of Dr. Almeroth because Dr. Almeroth’s testimony is allegedly inconsistent across the related inter partes reviews. PO Resp. 13–19; PO Sur-reply 21– 22. We have reviewed the disputed portions of Dr. Almeroth’s testimony and, when read in context, we are not persuaded that the testimony is inconsistent so as to be afforded little weight. As Petitioner points out (Pet. Reply 2–3), Patent Owner’s arguments do not properly account for the context in which the testimony was given in the related inter partes review.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Patent Owner’s arguments are unpersuasive. We are not persuaded that these differences between Kaplan, Ahmed, and Deforche are dispositive. To the contrary, we find the differences establish why a POSITA would have further modified Kaplan and Ahmed with the teachings of Deforche. Deforche expressly teaches that a disadvantage of wireless modems is that they require installation of an appropriate driver before applications running on the computer device can use the functionality of the wireless modem to connect to wireless networks. Ex. 1030 ¶¶ 2–3. Deforche solves this problem by using the processing device’s pre-installed drivers, which can be for a human interface device, to set up a modem/host communication interface for communication. Id. ¶¶ 4, 9. Because “[d]ata traffic from the computer device towards the wireless communication network and vice versa is routed over this modem/host communication interface and uses the generic communication protocol provided by the preinstalled generic driver,” Deforche states this “has the advantage that the need for a specific driver for the communication between the wireless modem device and the computer device can avoided” and “the advantage that a user can use the wireless modem device on a computer device on which he has no administrator rights, i.e. a computer specific driver for the wireless modem device.” Id. ¶ 9. “The motivation-to-combine analysis is a flexible one. Any need or problem known in the field of endeavor at the time of and addressed by the patent can provide a reason for combining the elements in the manner claimed.” Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1379 (Fed. Cir. 2023) (internal quotations omitted). As the Federal Circuit held, “[t]here is a motivation to combine when a known technique has been used to improve one device, and a [skilled artisan] would recognize that it would improve similar devices in the same way.” Intel Corp., 61 F.4th at 1380. Here, Deforche establishes that utilizing an operating system’s preinstalled generic driver to provide a generic protocol communications between the processing device and a peripheral device was known for improving wireless modems because it does not require administrator rights and a specific driver to be installed to enable communications between the wireless modem device and the processing device.” slip op. at 20
Patent outcomesUS 10,762,002 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,762,002 - Google LLC v. DH International Ltd.All claims unpatentablePTAB · Feb 10, 2026 · IPR2024-01322 · APJ Brian P Murphy · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Mooney; the Board also found Mooney combined with Lee renders the disputed limitations obvious.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“A person of ordinary skill in the art (“POSITA”) at the time of the alleged invention of the ’294 patent would have had at least a bachelor’s degree in electrical engineering, or a related field, and at least two years of experience in design, development, and/or testing of network-enabled consumer devices, and familiarity with payment cards, or the equivalent, with additional education substituting for experience and vice versa. Pet. 2 (citing Lipoff Decl. Ex. 1003 ¶ 57). “Patent Owner agrees with the Petitioner on the level of ordinary skill in the art.” Resp. 4. Patent Owner adds that a POSITA would have had “at least three years of relevant industry or research experience in wireless communication between devices.” Id. (citing Ex. 2001 ¶¶ 26–29). Mr. Zaheer testifies that a POSITA “would” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“The claim language and specification define and describe an “activation cue” in functional terms: a data communication from an external source is received by the cell phone and recognized as an activation cue if it causes the switching element to be assigned its first (activated) state. Ex. 1001, 9:28–31, 9:42–46, 10:14–16, 13:55–60, 14:53–59, 15:4–6, 19:20–26. Patent Owner agrees that “upon an activation cue being received by portable electronic device 10, switching element 44b switches to its activated state.” Resp. 19 (quoting Ex. 1001, 10:14–16). The activation cue may be a predetermined bit sequence, a predetermined contactless data transmission, continuously emitted, pulsed, or punctual, but these are unclaimed non-limiting embodiments of the preferred form of data transmission. Id. at 9:25–26 (“for example a predetermined bit sequence”), 11:20–22 (“One example . . . emit an activation cue in the form of a predetermined contactless data transmission”), 14:65–15:3 (continuously emitted, pulsed or punctual cue). We will not read such preferred embodiments from the specification into claim language that is not so limited. See SuperGuide Corp. v. DirecTV Enterprises, Inc., 358 F.3d 870, 875 (Fed. Cir. 2004) (care should be taken “not to import into a claim limitations that are not part of the claim”); see also In re Van Geuns, 988 F.2d 1181, 1184 (Fed. Cir. 1993) (“limitations are not to be read into the claims from the specification”); see also IQRIS Techns. LLC v. Point Blank Enterprises, Inc., 2025 WL 727717, *4 (Fed. Cir. 2025) (“It is the claims, not the preferred embodiments, that” slip op. at 15
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“operatively linked to said electronic circuit” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. We note there is no presumption of applying means-plus-function analysis to the switching element, because the limitation does not use the words “means for” that would mandate such claim construction treatment, and “switching” may invoke structure as well as function. See Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1349–1350 (Fed. Cir. 2015) (en banc) (holding that “use of the word ‘means’ creates a presumption that § 112, ¶ 6 applies”). Regardless, we look to the meaning of the claim phrase at issue in view of the specification. We determine that the ’294 patent provides a clear, concise meaning for the switching element upon which both parties rely for construction. Patent Owner’s express agreement with Petitioner, that the claimed switching element is described in the ’294 patent as “any type of device allowing data to be conveyed according to alternate data conveyance operations in response to an activation cue being received by transceiver 18 or not,’” is particularly telling because it is not consistent with Patent Owner’s argument that the switching element means “switching of the data.” Resp. 7, 31 (citing Ex. 1001, 9:28–318). The claim language does not recite, and the specification does not describe, the switching element as a device that switches the data. Therefore, we determine the claimed “data conveyance switching element” means any type of switching device that allows data to be 8 We presume Patent Owner’s citation to “Exh. 2001, 9:28-31” on page 7 was intended to be a citation to the ’294 patent (Ex. 1001), as cited on page 31. whether or not an “activation cue” is received by the cell phone “cue receiver.”” slip op. at 21
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningDecided for petitioner
“[external] data exchange device” as a device with a data transceiver coupled to a circuit that carries out the function of exchanging data. Pet. 7–8 (citing Ex. 1001, 2:14–17, 4:7–14, 9:3–6; Ex. 1003 ¶¶ 67–68). As above, whether we construe the “[external] data exchange device” under 35 U.S.C. Section 112, sixth paragraph or not, the result is the same. Patent Owner, quoting the description of a data exchange device in the ’294 patent, contends that a “[external] data exchange device” “can be any sort of data exchange device comprising an electronic circuit (not shown) therein and a data transceiver 9a.” Resp. 8 (quoting Ex. 1001, 9:4–6). Patent Owner also responds to the Petition by clarifying that “[a]n external data exchange device is not a transceiver but a device with a transceiver.” Id. (citing Ex. 2001 ¶ 48). Petitioner argues in reply that Patent Owner does not contest Petitioner’s mappings of Mooney’s “cordless telephone base unit” or “cellular network infrastructure” to the claimed data exchange devices, such that no construction is necessary to resolve the dispute. Reply 5 (citing Resp. 16–37; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011)). Limitations [1.c] and [1.d] recite “a first [second] data transceiver operatively linked to said electronic circuit [in the cell phone],” both of which are defined functionally as “for exchanging data between said electronic circuit [in the cell phone] and a first [second] external data exchange device over a first [second] communication link.” Nothing in the the other independent claims, further limits the form or function of the “[external] data exchange device,” although a device external to the cell phone may invoke additional structure. We determine the plain meaning of “[external] data exchange device” as claimed and described in the ’294 patent governs: any [external] device that comprises an electronic circuit and data transceiver for exchanging data with the electronic circuit in the cell phone over a communication link. slip op. at 22
Patent outcomesUS 9,022,294 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,022,294 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentablePTAB · Jan 23, 2026 · IPR2024-01192 · APJ Michael J Strauss · IPR · Final written decision
Claims 1–10 and 16 are unpatentable as obvious over the asserted combinations of the Lorex Manual or Lorex Video with the identified references.
RulingsFinal written decision- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for petitioner
“Patent Owner does not dispute any of Petitioner’s contentions as to the effective filing date, stating in agreement with Petitioner’s asserted Effective Filing Date of the Challenged Claims that “[t]he ’916 Patent claims a priority of a provisional application 61/924,240 filed on January 7, 2014.” PO Resp. 8. Given that the parties are in agreement on the January 7, 2014, effective filing date, we similarly use January 7, 2014, as the effective filing date of the challenged claims for purposes of this Decision.” slip op. at 4
- Skill levelSkill level petitioner adoptedDecided for petitioner
“II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Vlad Kardashov, Petitioner proposes that a person of ordinary skill in the art at the time of the invention of the ’916 patent “would have had a bachelor’s degree in electrical engineering and two 7 US 2012/0198040 A1, published August 2, 2012 (Ex. 1011, “Kuo”). 8 The subject ’916 patent claims priority to Kuo as a continuation-in-part of that earlier filed application. Ex. 1001, code (63). 9 Lorex Technology Inc., “How to set up remote access for DVR using - Lorex Stratus Connectivity” (June 18, 2013), available at https://www. youtube.com/watch?v=fMPRi9WFuTM (Ex. 1012, the “Lorex Video”). 10 US 2012/0113265 A1, published May 10, 2012 (Ex. 1013, “Galvin”). years of work experience with network and communication technologies.” Pet. 8 (citing Ex. 1003 ¶¶ 12–14). Patent Owner does not contest Petitioner’s proposal or provide a proposal of its own. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is consistent with the technology described in the ’916 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner asserts that “no claim elements need a formal construction for purposes of resolving controversies in this proceeding.” Pet. 9 (citing Ex. 1003 ¶¶ 43–44; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011), Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. § 42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artPriority date awardedDecided for petitioner
“that Patent Owner fails to demonstrate that the Lorex Manual was based on a disclosure made by the inventor or joint inventor or by another who obtained the subject matter disclosed directly or indirectly from the inventor or a joint inventor. The Lorex Manual is relied on under Ground 1A, exclusively or in the alternative to or in combination with Kim, for all claim elements. Pet. 9– 31. Patent Owner fails to demonstrate that this subject matter was disclosed to Lorex by ThroughTek, much less by one of the inventors of the ’916 Patent.” slip op. at 22
Patent outcomesUS 9,774,916 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,774,916
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.