• Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco NVNo claims unpatentable
  PTAB · Oct 5, 2026 · IPR2025-00598 · APJ David C Mckone · IPR · Final written decision

  Claims 1–31 were not shown unpatentable under either § 103 ground because the asserted combinations did not teach required claim limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “admissions by Patent Owner in litigation, contends that a person of ordinary skill in the art would have had “a Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field” and that “[a]dditional educational experience could substitute for some of the work experience.” Pet. 5 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art (Petition, 5) at this time.” PO Resp. 6. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is uncontested and is consistent with the technology described in the ’347 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

    “In the Preliminary Response, “Patent Owner accept[ed] the Petition’s claim construction.” Prelim. Resp. 6. However, in the Patent Owner Response, Patent Owner argues that “the claims of the ’347 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Based on the complete record, we do not find it necessary to provide express claim constructions of any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we 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

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Beel actually discloses the following: [0321] On the peripheral device 32 the video packets are received at the corresponding plug and play port, e.g. the USB port 11, read by the Human Interface Driver (HID) interface handler 13, unpacked to remove HID protocol headers in an unpacker 20 and then transmitted to the communications network by a transmitter 21. The network can be wireless for example WiFi or LiFi network. [0322] Having been routed over a communications network to the base unit 33, the incoming stream is read from the communications interface such as a WiFi access point 22, unpacked in an unpacker 25, decoded in a decoder 26 and then inserted into a suitable composition such as an OpenGL based composition in the compositor 29 for display on a central display device. Ex. 1005 ¶¶ 321–322 (emphasis added to portions quoted by Petitioner). Patent Owner notes that “[t]he Petition mistakenly cites to ¶ 322 of Beel but quotes ¶ 321.” PO Resp. 20 n.3. However, it appears that Petitioner has grafted together a portion of paragraph 321 that introduces peripheral device 32 with a portion of paragraph 322, which discusses features of base unit 33. However, this grafting has been done in such a way as to convey (incorrectly) that peripheral device 32, not base unit 33, includes unpacker 25, decoder 26, and compositor 29 that process the first processed video data received by the first peripheral device to generate second video data. Dr. Almeroth’s testimony, which copies Petitioner’s incorrectly altered quotation to paragraph 322 of Beel, is unreliable as to this claim limitation and is entitled to no weight.4 Thus, Petitioner has no expert testimony on which to rely for this claim limitation.” slip op. at 19

  • Strike new argumentNew argument disregardedDecided for patent owner

    “5 At the oral argument, when challenged on its reliance on paragraph 322, Petitioner argued that paragraph 321 of Beel teaches this limitation. Tr. 22:26–23:24. Petitioner did not make this argument in the Petition and, instead, raised it for the first time during oral argument; thus, it will not be considered. See Dell Inc. v. Acceleron, LLC, 884 F.3d 1364, 1369 (Fed. Cir. 2018) (“Unless it chose to exercise its waiver authority under 37 C.F.R. § 42.5(b), the Board was obligated to dismiss Dell’s untimely argument given that the untimely argument in this case was raised for the first time during oral argument.”). Even if we were to consider this new argument, it would not be persuasive. As Patent Owner observes (PO Resp. 20), any processing performed by peripheral device 32 in paragraph 321 is on data received from the processing device and destined for the base station via the network, rather than data flowing in the direction of the first processed video data of claim 1.” slip op. at 22

  Patent outcomesUS 11,966,347 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,966,347
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · Sep 23, 2026 · IPR2025-00915 · APJ Arthur M Peslak · IPR · Final written decision

  Claims 1–30 are unpatentable: claims 1–3, 5–16, and 18–30 as obvious over Menon, Trefethen, RS6000, and MPIref; claims 4 and 17 over those references plus POEref.

  RulingsFinal written decision

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

    “Ex. 1163 ¶ 37 (citing Ex. 1003 ¶ 71; Ex. 1005, 1–3). We credit Dr. Bajaj’s testimony which is unrebutted and supported by the record. We, thus, agree with Dr. Bajaj’s reasoning which is based on Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶ 75. 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. RS6000 is specifically referenced in Menon-Trefethen and adds operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Considering Menon as a whole, these facts are inconsistent with Patent Owner’s teaching away arguments. For these reasons, Patent Owner’s teaching away argument is unavailing. Motivation to Combine Conclusion We have reviewed Petitioner’s evidence and contentions which we” slip op. at 42

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

    “For the foregoing reasons, Petitioner establishes by a preponderance” slip op. at 79

  Patent outcomesUS 11,563,621 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,563,621
• ARM Ltd v. Daedalus Prime LLCAll claims unpatentable
  PTAB · Sep 9, 2026 · IPR2025-00207 · APJ Gregg I Anderson · IPR · Final written decision

  Claims 1–7, 11–14, and 16–19 are unpatentable as obvious over the asserted grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “would have (1) at least a bachelor’s degree in electrical engineering, computer engineering, physics, or a similar field, and (2) approximately two years of industry or academic experience in a field related to microelectronic architecture design, including experience with cache management in multicore systems-on-a-chip (SoCs). (Ex-1003 ¶¶50-51.) More related education would compensate for fewer years of work experience (and vice versa). (Ex-1003 ¶¶50-51.) Pet. 4–5. This definition was adopted in the Institution Decision. Inst. Dec. 13. Patent Owner does not dispute the finding. PO Resp. 5–6. For the purpose of our Decision, we maintain the finding made in the Institution Decision.” slip op. at 15

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

    “1. “a single caching agent” (claim 1) We note a construction issue from the ’1344 IPR where we construed a “single caching agent,” which is recited in claim 1 here. ’1344 IPR Final Decision, 16–18. We concluded that a “‘single caching agent’ means ‘one caching agent for the processor, which may be formed from distributed portions.’” Id. at 18. We adopted that construction in our Institution Decision in this case. Inst. Dec. 15.” slip op. at 16

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

    “2. Remaining claim terms Independent claims 11 and 16 include different language as to “caching agent.” Claim 11 recites “a caching agent.” Ex. 1001, 8:18. Claim 16 similarly recites “a first caching agent.” Id. at 8:47–48. Neither claims 11 or 16 includes claim 1’s recitation of “distributed portions. The “caching agent” limitations of claims 11 and 16, are not at issue. Accordingly, no construction is necessary.” slip op. at 18

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

    “(1) the issue is identical to one decided in the first action; (2) the issue was actually litigated in the first action; (3) resolution of the issue was essential to a final judgment in the first action; and (4) plaintiff had a full and fair opportunity to litigate the issue in the first action. Pet. Br. 2. Further, Petitioner alleges the ’1344 Final Decision was not appealed by Patent Owner and is therefore a basis for issue preclusion. Id. (citing Power Integrations, Inc. v. Semiconductor Components Indus., LLC, 926 F.3d 1306, 1311–12 (Fed. Cir. 2019)).” slip op. at 19

  Patent outcomesUS 8,984,228 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,984,228
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,021,679
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,570,034
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Aug 20, 2026 · IPR2025-00343 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1–6 and 8–13 were not shown unpatentable because Petitioner did not establish a reason to combine Bucknell’s multiplexing techniques with Eckert.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “Patent Owner does not expressly dispute Petitioner’s definition of a person of ordinary skill in the art. See generally PO Resp. On this record, Petitioner’s proposed level of ordinary skill in the art is not disputed and is consistent with our review and understanding of the technology and descriptions in the ’138 patent and the asserted prior art references. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 12

  • Prior constructionPrior construction adoptedDecided for petitioner

    “1. a subset of radio bearers Petitioner points out that in IPR2022-01127 the Board “preliminarily determined that a subset of the plurality of radio bearers” means “less than all of the plurality of radio bearers.” Pet 12 (citing Ex. 1019, 18–19). Petitioner explains that, in the present proceeding, it has applied “the prior art in accordance with that construction; however, in view of the asserted grounds, no claim term requires express construction to find the Challenged Claims unpatentable.” Id. (citing Nidec 868 F.3d 1017). Patent Owner neither disputes the prior construction of “a subset of radio bearers,” nor offers additional constructions. See generally PO Resp. To the extent necessary, and in accordance with our prior determination, we construe “a subset of the plurality of radio bearers” to mean “less than all of the plurality of radio bearers.”” slip op. at 13

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

    “bears pointing out that the specification of the ’138 patent appears to explain what “a single allocation” means: If there are multiple QoS requirements within a single 3GPP PDP context, a single physical allocation of radio resources may be made to the UE. In this manner, a single PDP context implies a single CCTrCh. This single physical allocation of radio resources provided to a UE is shared amongst a number of services, in proportion to their respective QoS requirements, for example in proportion to the signalled weight values (Stier). Ex. 1001, 9:36–43 (emphasis added). Petitioner’s expert, Dr. Ding, explains that the “abbreviation CCTrCh was understood in the art to refer to a transport channel known as the Coded Composite Transport Channel.” Ex. 1003 ¶ 88. Dr. Ding testifies that Eckert teaches selecting data for uplink within a determined TTI and scheduling the uplink transmission on a transport channel, E-DCH, where scheduling of the E-DCH in a UE is controlled by a base station. Eckert, [0012] (“[A] new dedicated transport channel called Enhanced Dedicated Channel (E-DCH) has been introduced for this purpose. The fundamental characteristics of this new transport channel include . . . scheduling controlled by the base station, also called NodeB in UMTS…” Id. ¶ 90. In addition to Eckert disclosing a single transport channel E-DCH, Petitioner argues that Eckert discloses using a “finite quantum of physical resources” where “[t]he ’138 patent disclosure parallels Eckert, with both the E-DCH and CCTrCH transport channels relating to a UMTS uplink, employing spreading codes in code division multiple access (CDMA), and Reply 6 (citing Ex. 1005, ¶¶ 3, 8, 15, 23; Ex. 1071 ¶¶ 17–20; Ex. 1011 ¶¶ 6, 51). We do not need to specifically interpret this claim phrase because there is no actual dispute as to the meaning of the claim language itself and because, ultimately, the construction of this phrase plays no part in our Decision.” slip op. at 15

  • BurdenNot shown unpatentable

    “D. Ground 1: Claims 1–4 and 8–11 – Alleged Obviousness over Eckert in view of Bucknell and Lohr-1 On the complete record now before us, Petitioner has not established a preponderance of evidence that claims 1–4 and 8–11 would have been obvious over Eckert, Bucknell, and Lohr-1. For the reasons explained below we determine that Petitioner has failed to show why a person of ordinary skill in the art would have modified Eckert in view of Bucknell in the manner claimed. We focus our analysis below on claim 1, and more specifically on those limitations for which the combination of Eckert and Bucknell is asserted. 1. Limitations [1.0]–[1.2] and the combination of Eckert and Bucknell The combination of Eckert and Bucknell is essential to each of Petitioner’s asserted grounds in this proceeding. Pet. 13. At the outset, we address this issue because our determination that Petitioner has failed to show why a person of ordinary skill in the art would have combined Eckert and Bucknell is dispositive as to all grounds.” slip op. at 20

  Patent outcomesUS 10,292,138 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,292,138
• Tesla, Inc. v. Intellectual Ventures II LLCSome claims unpatentable
  PTAB · Aug 18, 2026 · IPR2025-00339 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 22, 23, 28, and 30 are unpatentable over Choi, Labaziewicz, and Yu; claims 1–3, 10–12, 24, 25, 32, and 33 were not shown unpatentable.

  RulingsFinal written decision

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningOther

    “We decline Patent Owner’s invitation to construe “during a frame” of “independently controlling simultaneous data acquisition with each of the first and second channels during a frame” by importing the extraneous limitations “at some point between the beginning and the end of the exposure interval during which the image sensors capture a single image.” As pointed out by Petitioner, Patent Owner’s proposed construction is unsupported by the language of claim 22 and the ’180 Specification because Specification does not disclose an exposure interval nor suggest “during a frame” is limited to an exposure interval. Patent Owner and its expert Dr. Saber cite only extrinsic evidence (Exs. 2006, 2009) to support its argument that claim 22 should be limited to an “exposure interval during which the image sensors capture a single image.” See PO Resp. 16–17; Ex. 2020 ¶ 64. Similarly, Patent Owner relies only on extrinsic evidence (e.g., Ex. 2011, 1; Ex. 2022, 1; Ex. 2020 ¶ 66) to limit “during” to “at some point between the beginning and the end.” See id. at 18. When considered in the context of claim 22 and the ’180 Patent Specification which do not limit “during a frame” to an exposure interval, we find that we cannot rely on Patent Owner’s citations to extrinsic evidence to yield a reliable construction for “during a frame.” As demonstrated in the analysis below, we need not provide an explicit construction for “during a frame” to resolve the parties’ disputes regarding the merits of the patentability challenges. See Realtime, 912 F.3d at 1375. We apply the ordinary and customary meaning for “during a frame.” To the extent that an explicit identification of the ordinary and customary meaning may aid the understanding of our analysis, consistent with the language of claim 22 and the ’180 Patent Specification, we find that the ordinary and customary meaning for “during a frame” is “during the period of time that data for an image frame is acquired.” See Ex. 1001, code (57), 20:6–24, 25:23–35.” slip op. at 12

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field and 2-3 years of experience in digital imaging systems,” and that “[l]ess experience may be necessary with additional education, and likewise, less education may be necessary with additional work experience.” Pet. 6 (citing Ex. 1003 ¶¶ 16–19). Patent Owner does not dispute Petitioner’s definition. See generally PO Resp. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is consistent with the level of skill reflected by the ’180 Patent Specification and the prior art of record.” slip op. at 20

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

    “Owner to show that Labaziewicz is not prior art because the ’180 Patent is entitled to the earliest August 25, 2004, filing date of the ’854 Provisional Application. See Dynamic Drinkware, 800 F.3d at 1379–1380. For a claim in a later-filed application to be entitled to the filing date of an earlier application, the earlier application must provide written description support for the claimed subject matter. Anascape, Ltd. v. Nintendo of Am. Inc., 601 F.3d 1333, 1337 (Fed. Cir. 2010). To satisfy the written description requirement, “a prior application itself must describe an invention, and do so in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997); see also VasCath v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (“[T]he applicant must . . . convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention . . . now claimed.” (emphasis omitted)), Ariad Pharm. Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1352 (Fed. Cir. 2010) (en banc) (“[I]t is the specification itself that must demonstrate possession.”). Patent Owner’s arguments fail to meet this burden of production because, aside from addressing deficiencies of written description support the ’854 Provisional Application provides written description support for all of the limitations of the claimed invention. See PO Resp. 60–64; PO Sur-reply 25–28. Specifically, Patent Owner does not address written description support in the ’854 Provisional Application for “independently controlling simultaneous data acquisition with each of the first and second channels during a frame”––limitation [22.3]––the heart of the parties’ claim construction disputes addressed above in Section II.A. See PO Resp. 60–64; PO Sur-reply 25–27. Accordingly, Patent Owner has not met its burden of production in coming forward with evidence or argument to show possession of the claimed invention in the ’854 Provisional Application. As a result, the burden of production does not shift back to Petitioner, and, therefore, the ’180 Patent is not entitled to the benefit of the August 25, 2004, filing date of the ’854 Provisional Application.” slip op. at 23

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

    “Petitioner does not present arguments that it would have been obvious to a person of ordinary skill in the art at the time of the invention to modify the teachings of Matsushima to acquire data for images 62A and 62B at the argues that Matsushima renders obvious this limitation. See id. at 21, 23, 30; PO Resp. 33–34 (“[T]he Petition provides no further explanation why Matsushima renders this limitation obvious.”). In the Reply for the first time, Petitioner asserts that “a POSITA would understand that Matsushima’s disclosure, including its multi-channel architecture, synchronous control of channels, and capturing two images that are scaled versions of the same scene, renders obvious simultaneous acquisition during a frame. Pet. Reply 13 (citing Ex. 1069 ¶ 49). We do not consider Petitioner’s belated argument because it exceeds the proper scope of a reply. A reply may only respond to arguments raised in the corresponding patent owner response. See 37 C.F.R. § 42.23. As explained in the Trial Practice Guide, “respond” “does not mean proceed in a new direction with a new approach as compared to the positions taken in a prior filing.” Trial Practice Guide at II.I. (December 2025)(citing 37 C.F.R. § 42.23).10 A reply that raises a new issue or belatedly presents evidence may not be considered. See id. For example, a “[p]etitioner may not submit new evidence or argument in reply that it could have presented earlier, e.g. to make out a prima facie case of unpatentability.” Id.” slip op. at 32

  Patent outcomesUS 7,916,180 mixed
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 7,916,180
• Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,684,972
• Tesla, Inc. v. Intellectual Ventures II LLCSome claims unpatentable
  PTAB · Jul 21, 2026 · IPR2025-00339 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 22, 23, 28, 30, and 33 are unpatentable over Choi, Labaziewicz, and Yu under § 103; claims 1–3, 10–12, 24, 25, and 32 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art “would have had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field and 2-3 years of experience in digital imaging systems,” and that “[l]ess experience may be necessary with additional education, and likewise, less education may be necessary with additional work experience.” Pet. 6 (citing Ex. 1003 ¶¶ 16–19). Patent Owner does not dispute Petitioner’s definition. See generally PO Resp. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is consistent with the level of skill reflected by the ’180 Patent Specification and the prior art of record.” slip op. at 20

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

    “Owner to show that Labaziewicz is not prior art because the ’180 Patent is entitled to the earliest August 25, 2004, filing date of the ’854 Provisional Application. See Dynamic Drinkware, 800 F.3d at 1379–1380. For a claim in a later-filed application to be entitled to the filing date of an earlier application, the earlier application must provide written description support for the claimed subject matter. Anascape, Ltd. v. Nintendo of Am. Inc., 601 F.3d 1333, 1337 (Fed. Cir. 2010). To satisfy the written description requirement, “a prior application itself must describe an invention, and do so in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997); see also VasCath v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (“[T]he applicant must . . . convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention . . . now claimed.” (emphasis omitted)), Ariad Pharm. Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1352 (Fed. Cir. 2010) (en banc) (“[I]t is the specification itself that must demonstrate possession.”).” slip op. at 23

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

    “We do not agree with Petitioner’s arguments based on retrieval of data from CCD 18A and CCD 18B. Although Matsushima’s CCD drive circuits 20A and 20B are driven synchronously by timing generator 28 (see Ex. 1007 ¶ 27), Matsushima discloses that “accumulated signal charges are retrieved by CCD drive pulses applied by CCD drive circuits 20A and 20B, and are sequentially output from CCD 18A and CCD 18B as voltage signals (analog image signals) corresponding to each signal charge” (see Ex. 1007 ¶ 23) (emphasis added). In other words, regardless of whether CCD drive circuits 20A and 20B are driven synchronously by timing generator 28, Matsushima discloses that voltage signals corresponding to the accumulated 8 Petitioner’s citation erroneously includes ¶¶ 34–36 of Exhibit 1069. CCD 18A and CCD 18B sequentially––not output at the same time or simultaneously.” slip op. at 30

  • Strike new argumentNew argument disregardedDecided for patent owner

    “argues that Matsushima renders obvious this limitation. See id. at 21, 23, 30; PO Resp. 33–34 (“[T]he Petition provides no further explanation why Matsushima renders this limitation obvious.”). In the Reply for the first time, Petitioner asserts that “a POSITA would understand that Matsushima’s disclosure, including its multi-channel architecture, synchronous control of channels, and capturing two images that are scaled versions of the same scene, renders obvious simultaneous acquisition during a frame. Pet. Reply 13 (citing Ex. 1069 ¶ 49). We do not consider Petitioner’s belated argument because it exceeds the proper scope of a reply. A reply may only respond to arguments raised in the corresponding patent owner response. See 37 C.F.R. § 42.23. As explained in the Trial Practice Guide, “respond” “does not mean proceed in a new direction with a new approach as compared to the positions taken in a prior filing.” Trial Practice Guide at II.I. (December 2025)(citing 37 C.F.R. § 42.23).9 A reply that raises a new issue or belatedly presents evidence may not be considered. See id. For example, a “[p]etitioner may not submit new evidence or argument in reply that it could have presented earlier, e.g. to make out a prima facie case of unpatentability.” Id. Petitioner clarifies that the Petition does not argue inherency. See Pet.” slip op. at 33

  Patent outcomesUS 7,916,180 mixed
  § 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 7,916,180
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jul 21, 2026 · IPR2025-00342 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1, 2, and 6–11 were not shown unpatentable because the cited combinations did not teach guiding a vehicle to a fixed destination or calculating the claimed optimized path from stored destination data.

  RulingsFinal written decision

  • Adverse judgmentOther

    “reserves consideration of discretionary issues to the Director. The relief Patent Owner requests is that the panel exercise discretion to terminate these proceedings based on actions taken in related district court proceedings as done in Hulu. Supp. PO Resp. 2. Because the basis for Patent Owner’s requested relief is discretionary, the panel lacks the authority to grant the request. In this regard, the present situation is different from that in Hulu and Sinclair Pharma Limited v. Hydrafacial LLC (IPR2025-00145, Paper 41, Squires, Feb. 12, 2026), cited by Patent Owner. In those cases, the 9 Available at: https://www.uspto.gov/sites/default/files/documents/Director_Institution_of _AIA_Trial_Proceedings.pdf (“Director Institution Memo”). Director ordered de-institution, not the panel. The Director has not made such a determination or delegated such authority to the panel in these proceedings. Indeed, as noted above, Patent Owner has already briefed, and the Director has previously ruled on, discretionary denial issues. Paper 10. Accordingly, we decline to vacate our Institution Decision and focus our analysis on the merits of the case as presented by the parties.” slip op. at 8

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We consider the asserted grounds of unpatentability in view of the understanding of a person of ordinary skill in the art. In assessing 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) (quoting Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “[O]ne or more factors may predominate.” Id. Petitioner asserts that ordinarily skilled artisans “would have had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related subject, and four years of work experience in image processing, automated vehicle control/navigation, or a related field.” Pet. 7. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’805 patent, and we adopt it here. See generally, PO Resp. Based on this record, and because there is no dispute, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’805 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art, itself, can reflect appropriate level of ordinary skill in art).” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed patent owner constructionDecided for patent owner

    “Here, in our opinion, Patent Owner has shown that the Specification describes the potential destinations of a vehicle as limited to physically fixed, non-transient objects or features. PO Resp. 18–21. As an initial matter the ’805 patent is titled “Docking Assistant” and explains its purpose for guiding a “vehicle to a stop at a specific location.” Ex. 1001, codes (53), (57), Abstract. We acknowledge that claim 1 does not expressly recite that “at least one potential destination” is a fixed destination or location. See id. at 7:61– 63 (Claim 1 requiring “extracting from the acquired image data positional parameters of at least one potential destination relative to the motor vehicle;”). Yet, in the context of the relatively brief specification, there is no explanation, example, or embodiment which reasonably extends the meaning of “destination” or “potential destination” beyond a fixed location. The ’805 patent describes in the Abstract that [m]any day-to-day driving situations require that an operator of a motor vehicle guide the motor vehicle along a specific course and bring the vehicle to a stop at a specific location, for example in a parking bay or at a loading platform. Id. at code (57) Abstract. The Abstract explains in the next sentence that “[t]o assist a vehicle operator in such situations, a method and a suitable device for implementing this method, include detecting the potential target objects in the image data of an image sensor and identifying the potential target objects as potential destinations in a multi-stage exclusionary method.” Id. (emphasis added). Nowhere in this initial description of the invention, nor anywhere else that Petitioner points to, is there is expansion of the “specific location” or “potential destination” beyond a docking station or parking bay. Of course, the claim is not limited to these examples, as it would be inappropriate to read in such limitations from the Specification. See Acceleration Bay, LLC v. Activision Blizzard Inc., 908 F.3d 765, 771 (Fed. Cir. 2018) (“Acceleration again attempts to import structural limitations into claims lacking those limitations. . . . While the specifications discuss a broadcast channel overlaying a network, the claims at issue are not so limited.”).” slip op. at 14

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “Patent Owner’s declarant, Dr. Majumder, testifies to the contrary that “[r]ead as an engineer, the ‘805 patent’s present invention is framed around guiding a vehicle to fixed, physical destinations (exemplified by docking stations and similar structures) without fiducials or special markings.” Ex. 2010 ¶ 81. Considering Broggi, Dr. Majumder testifies further that “[a] moving object, such as a preceding car, is not a valid destination under the ‘805 Patent, because it is not a stationary location at which the host vehicle can be guided to stop. To treat such a vehicle as a ‘potential destination’ would lead to collision, not guidance.” Id. ¶ 86. As discussed in our claim construction, given a plain reading of claim 1 in light of the Specification, our understanding of the ’805 patent is consistent with Dr. Majumder’s testimony. We agree that Broggi is directed expressly to the platooning of moving vehicles, and not physically fixed destinations as the proper claim construction requires. Because Broggi does not disclose the use of physically fixed “potential destinations” as required, e.g., in limitations [1.2]–[1.3], and neither Huttenlocher nor Brady are relied upon to overcome this deficiency, Petitioner has not met its burden of persuasion to show by a preponderance of the evidence that claim 1 would have been obvious over Broggi in view of Huttenlocher and Brady.” slip op. at 27

  Patent outcomesUS 7,336,805 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Markman · KSR · Graham
  Patents in suitUS 7,336,805

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.