- Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco NVNo claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 11,966,347 - 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 - Apple Inc. v. Proxense, LLCAll claims unpatentablePTAB · Nov 12, 2025 · IPR2024-01399 · APJ Thu A Dang · IPR · Final written decision
Claims 1–6, 8–15, and 17–20 are unpatentable under § 103, based on Buer alone or in the combinations listed.
RulingsFinal written decision- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“1 Apple Inc. filed a motion for joinder and a petition in IPR2024-01399, which were granted, and, therefore, Apple Inc. has been joined as petitioner in this proceeding. We also granted a Joint Motion to Terminate Inter Partes Review Proceeding as to the other petitioner, leaving Apple Inc. as the sole petitioner.” slip op. at 1
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“Here, as Petitioner points out, “[n]one of the elements of the Challenged Claims . . . use the word ‘means,’” similar to the challenged claims in the previous related proceedings. Pet. Reply 2–3; see also IPR2024-00405, Ex. 1001, 22:43–60; IPR2024-00407, Ex. 1001, 22:36–49; IPR2024-00573, Ex. 1001, 21:51–65. 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
- Prior constructionPrior construction adoptedDecided for patent owner
“invoke 35 U.S.C. § 112 ¶ 6. See PO Resp. 4; Pet. Reply 2; PO Sur-reply 8. However, we addressed similar arguments with respect to this issue in previous related proceedings. See IPR2024-00405, Paper 24 at 8–25; IPR2024-00407, Paper 25 at 8–26; IPR2024-00573, Paper 27 at 8–29. In fact, during Oral Argument in this proceeding, Patent Owner acknowledged that “this panel construed the claims at issue in [previous proceedings,] IPR2024-573 and 2024-407.” Tr. 20:3–5. In particular, Patent Owner acknowledged that “the Board would rely on and import the construction from those IPRs, . . . 2024-407 and ’573 for the sake of consistent office determination.” Id. at 20:9–11. That is, Patent Owner agreed that the Board should use the prior constructions for the same claim terms at issue in this proceeding. Id. at 26:12–16 (“JUDGE MCKONE: -- it sounds like everybody agrees, that we should use the prior claim constructions from [the] other proceedings . . . Do you agree? MR. HECHT: -- if the Board agrees, absolutely.”). Petitioner also agreed that the Board should use the prior constructions. See id. at 31:23–32:3 (“JUDGE MCKONE: And so I assume you want us to use the same claim construction in this case as the previous case[s]; is that correct? MR WOO: That is correct, Your Honor.”). We agree with the parties that, for the sake of consistency, we apply our claim constructions from the previous proceedings. Tr. 20:22–25. As set forth in the previous related proceedings, we determined that the claims do not invoke 35 U.S.C. § 112 ¶ 6. See IPR2024-00405, Paper 24 at 8–25; IPR2024-00407, Paper 25 at 8–26; IPR2024-00573, Paper 27 at 8–29. Thus, for consistency, and for the reasons given in the previous related proceedings, in this proceeding, we also determine that the claims do not invoke 35 U.S.C. § 112 ¶ 6, as discussed below.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“We find Patent Owner’s arguments unavailing. In particular, we disagree with Patent Owner’s contention that the District Court provided a construction for “one or more of the integrated RDC and integrated PDK enabling one or more of an application, a function, and a service,” as recited in claim 1. Although Patent Owner points to the District Court’s Memorandum in Support of Claim Construction Order (id. at 32 (citing Ex. 2002, 26)) to support its contention that the District Court construed the term “enabled,” as we determined in the Decision to Institute, this portion of the District Court’s Memorandum merely discusses that “hybrid device” is not indefinite, and discusses exemplary operations of the “hybrid device” from which a POSITA “could reasonably ascertain the scope of the claim.” See Dec. Inst. 9. As we explained, a determination of whether a term is indefinite is not the same thing as construing a claim term. Id. Thus, as we previously explained, by determining that “hybrid device” is not indefinite, the District Court did not construe the term “enabled.” Id.; see also Ex. 2002, 26. Accordingly, nothing in the Memorandum provides a construction of “enabled” as Patent Owner contends. Id. Thus, we find unavailing Patent Owner’s contention that Buer does not disclose the “enabled” limitation because, in Buer, “no key is provided in exchange for the information.” PO Resp. 33. That is, we decline to adopt Patent Owner’s proposed construction that an application, function or service is “enabled” by a PDK “when it receives information from a PDK in exchange for an access key.” Id. at 32. Here, as Petitioner points out, Buer discloses an authentication component for providing credentials to a service provider to authenticate access to secured services, wherein the authentication component generates an RF signal providing the necessary authentication information to a service provider. Pet. 45; see Ex. 1005 ¶¶ 152, 174. Buer further discloses a mobile device with an RFID client to authenticate a user to another processing system, the mobile device transmitting an enablement signal to a computer with a point-of-sale device. Pet. 47; see Ex. 1005 ¶¶ 192–195. We find availing Petitioner’s contention that Buer’s authentication component “enables” a wide variety of applications, functions, or services. Pet. 56. Petitioner’s contention is supported by Dr. Wolfe’s testimony and is consistent with the teachings of Buer. See Ex. 1003 ¶ 229. Based on the complete record presented, we determine that Petitioner has persuasively shown that Buer teaches “one or more of the integrated RDC and integrated PDK enabling one or more of an application, a function, and a service on one or more of the hybrid device and a device associated with the external RDC,” as recited in claim 1.” slip op. at 39
Patent outcomesUS 8,646,042 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,646,042 - Apple Inc. v. Proxense, LLCAll claims unpatentablePTAB · Nov 12, 2025 · IPR2025-00075 · APJ Thu A Dang · IPR · Final written decision
Claims 1–20 are unpatentable under § 103 over the asserted combinations of Dua, Giobbi ’157, Kotola, Buer, and Nishikawa.
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
“Challenged Claims. . . use the word ‘means,’” similar to the challenged claims in the previous related proceedings. Pet. Reply 3; see also IPR2024- 00405, Ex. 1001, 22:43–60; IPR2024-00407, Ex. 1001, 22:36–49; IPR2024- 00573, Ex. 1001, 21:51–65. 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 18
- Prior constructionPrior construction adoptedDecided for patent owner
“invoke 35 U.S.C. § 112 ¶ 6. See PO Resp. 4; Pet. Reply 2; PO Sur-reply 10. However, we addressed similar arguments with respect to this issue in previous related proceedings. See IPR2024-00405, Paper 24 at 8–25; IPR2024-00407, Paper 25 at 8–26; IPR2024-00573, Paper 27 at 8–29. In fact, during Oral Argument in this proceeding, Patent Owner acknowledged that “this panel construed the claims at issue in [previous proceedings,] IPR2024-573 and 2024-407.” Tr. 20:3–5. In particular, Patent Owner acknowledged that “the Board would rely on and import the construction from those IPRs, . . . 2024-407 and ’573 for the sake of consistent office determination.” Id. at 20:9–11. That is, Patent Owner agreed that the Board should use the prior constructions for the same claim terms at issue in this proceeding. Id. at 26:12–16 (“JUDGE MCKONE: -- it sounds like everybody agrees, that we should use the prior claim constructions from the other proceedings . . . Do you agree? MR. HECHT: -- if the Board agrees, absolutely.”). Petitioner also agreed that the Board should use the prior constructions. See id. at 31:23–32:3 (“JUDGE MCKONE: And so I assume you want us to use the same claim construction in this case as the previous case[s]; is that correct? MR WOO: That is correct, Your Honor.”). We agree with the parties that, for the sake of consistency, we apply our claim constructions from the previous proceedings. Tr. 20:22–25. As set forth in the previous related proceedings, we determined that the claims do not invoke 35 U.S.C. § 112 ¶ 6. See IPR2024-00405, Paper 24 at 8–25; IPR2024-00407, Paper 25 at 8–26; IPR2024-00573, Paper 27 at 8–29. Thus, for consistency, and for the reasons given in the previous related proceedings, in this proceeding, we also determine that the claims do not invoke 35 U.S.C. § 112 ¶ 6, as discussed below.” slip op. at 9
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“would have found it obvious to combine the teachings of Dua and Giobbi ’157 (Pet. 31), citing Dr. Wolfe’s supporting testimony (Ex. 1003). In particular, Petitioner posits that POSITA would have been motivated and found it obvious to “securely store the financial information in its tamper-resistant tag ‘to prevent hackers from retrieving confidential information’” (Pet. 31 (citing Ex. 1003 ¶¶ 105, 109)), as disclosed by Giobbi ’157. As Petitioner points out, Giobbi ’157 teaches “credit/debit card information” that is stored in a “profile memory field 232” in the “physical access secured and tamperproof” memory (id.; see Ex. 1006 ¶¶ 36, 42, 63), and we find persuasive Petitioner’s contention that a POSITA would have reasonably expected to succeed in “storing the ‘credit card profile or other payment information’ in Dua’s tamper resistant tag memory,” wherein such combination “would have been no more than combining prior art elements according to known methods to yield predictable results.” Id. (citing Ex. 1003 ¶ 158).” slip op. at 40
- Skill levelOther
“Principles of Law B. A patent claim is unpatentable under 35 U.S.C. § 103(a) if the 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.9 See Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966).” slip op. at 25
Patent outcomesUS 9,679,289 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,679,289 - PLR Worldwide Sales Ltd. v. Flip Phone Games Inc.All claims unpatentablePTAB · Nov 5, 2025 · IPR2024-00133 · APJ Scott B Howard · IPR · Final written decision
Claims 1–10 are unpatentable as obvious over Sturman and Ho; the Board found the Ho/Jiau/Choi grounds, with and without Ellis, insufficient.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“We see very little difference between the parties’ respective proposals. We adopt Patent Owner’s marginally more specific proposal as it better reflects the ’089 patent. Additionally, because we would reach the same conclusions under Petitioner’s proposal, we agree with Patent Owner that this does not affect our analysis.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“Consistent with Phillips, we begin with the “ordinary and customary meaning” of the words of the claims. Phillips, 415. F.3d at 1312–13 (quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)). The parties agree that the ordinary and customary meaning of the phrase “background object” is consistent with the dictionary definition and means an object that is “not in the foreground.” Tr. 8:10–16; PO Resp. 8–9; Ex. 2008 (AMERICAN HERITAGE DICTIONARY 2006); see also Ex. 2009 (“the scenery or ground behind something,” “the part of a painting representing what lies behind objects in the foreground”) (MERRIAM- WEBSTER DICTIONARY 2007); Ex. 2010 (“the part of a picture or pattern that is behind the main people or things in it” (MACMILLIAN ENGLISH DICTIONARY 2007); Ex. 2011 (“the ground or parts, as of a scene, situated in the rear (opposed to foreground)”) (RANDOM HOUSE WEBSTER’S COLLEGE DICTIONARY 2005). Having determined the ordinary and customary meaning, we need only look to see if there is some reason—such as the applicant acting as a lexicographer or the ordinary and customary meaning being improperly subjective—why the ordinary and customary meaning is not controlling.” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner
“We do not find that the prosecution history demonstrates that the applicant acted as a lexicographer by “clearly set forth a definition of the disputed claim term,” or “clearly express[ing] an intent to define the term” as required by Thorner, 669 F.3d at 1365. Instead, the language in the prosecution history is consistent with the ordinary and customary meaning. That is, the applicant focuses on the location of the object relative to the area of game play, i.e., the foreground. For example, the applicant distinguishes Chu’s object as not being “background objects” because they “are featured in the forefront of [the] game play as primary objects to be manipulated or used during game play (see Chu at ¶¶ [0063]–[0065]).” Ex. 1002, 85 (emphasis added).12 The applicant continued by arguing that Chu’s objects “exist in the background, outside of the primary focus of game play and as unexpectedly interactive components, and are not themselves needed or required in order to play the game.” Id. If anything, this demonstrates an intent of the applicant to use the customary and ordinary meaning—not in the foreground—and not act as a lexicographer.” slip op. at 17
- Expert testimonyPetitioner expert creditedDecided for petitioner
“We do not agree with Patent Owner’s argument. Under our rules, “[e]xpert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.” 37 C.F.R. § 42.65(a). We have reviewed Dr. Zagal’s testimony on this subject (see Ex. 1003 ¶¶ 156–160, 163, 166, 172, 177–178) and find that it complies with our requirements. Specifically, Dr. Zagal provides his opinion and identifies specific evidence in the record that supports it. We do not find MarkForged, a nonprecedential decision, persuasive. Although MarkForged cites 37 C.F.R. § 42.65(a) as support for the proposition that expert testimony “is entitled to little to no weight [if] it merely parrots the Petition,” the rule is silent on that point. Patent Owner has not directed us to any rule or precedential decision that says that non- 17 The decision was affirmed by the Director. Xerox Corp. v. Bytemark, Inc., IPR2022-00624, Paper 12 (PTAB Aug. 24, 2022). conclusory testimony which cites underlying factual support, such as Dr. Zagal gives in this proceeding, is entitled to no weight.” slip op. at 49
Patent outcomesUS 8,688,089 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,688,089 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00653 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution on all claims because the Petition did not show a reasonable likelihood that any challenged claim was unpatentable over the asserted grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“An inter partes review may be instituted only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’504 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Additionally, only terms that are in controversy need to be construed, and these need be construed only to the extent necessary to resolve the controversy. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in 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)). The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 9; Prelim. Resp. 4 (citing Ex. 2009 ¶ 72); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13
- Expert testimonyPetitioner expert discountedDecided for patent owner
“Ex. 1002 ¶ 47. As reflected above, Dr. Wooley’s testimony as to element [1.2] does not even assert that Cardamone discloses a tank, let alone one or more sensors disposed at a tank as recited in element [1.2]. Thus, Dr. Wooley’s testimony does not support Petitioner’s argument on this issue.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,726,504 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00652 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–23 and 25–30 were unpatentable over the asserted grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsDenied
“presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’403 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 10; Prelim. Resp. 4 (citing Ex. 2009 ¶ 73); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We agree with Patent Owner that the Petition fails to demonstrate that Kahn discloses element [1.2] because the evidence cited does not disclose a “first computer system being configured to provide remote control of the first pump or first valve” (i.e., a fluid-handling device). Kahn is directed to providing access to fluid sensing data and analyzing and providing visual information on that data, but Petitioner has not identified any disclosure of the capability to remotely control fluid-handling devices. See, e.g., Ex. 1005, code (54), 1:27–36, 2:50–3:2. More specifically, Kahn’s disclosures that Petitioner relies on for allegedly teaching remote control are deficient. We discuss each. First, Petitioner points to the following, “[f]or instance, as illustrated in FIG. 1C, a fluid control device such as a valve 15A is located on the input side of a sen[s]or unit 110.” Ex. 1005, 8:19–21, cited in Pet. 13. This portion of Kahn, however, does not disclose remote control. Second, Petitioner cites to the following: Finally, or in addition to, the communication unit 112B can include on-site alerts such as optical (indicator lights), audible alerts (e.g., alarm sounds), tactile (e.g., vibration of the unit) or can be interfaced to an appropriate control valve for simply shutting off the supply of fluid upon the detection of emergency events, for instance. Pet. 13 (citing Ex. 1005, 10:62–67). We agree with Patent Owner that this portion of Kahn teaches on-site alerts and local control of the fluid-handling device. See Prelim. Resp. 7. This portion of Kahn does not disclose remote control.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,294,403 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · Oct 10, 2025 · IPR2025-00651 · APJ Bart A Gerstenblith · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–3, 6, 7, and 9–20 were unpatentable over any asserted ground.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsDenied
“presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’680 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“target value” is part of a command that is sent from a computing device to a server and then to a controller. The controller then receives a measurement of the fluid by a sensor and determines whether the measurement satisfies the “target value.” If the measurement does not satisfy the “target value,” further operations are undertaken. The recited operation sequence makes clear that the plain and ordinary meaning of “target value” is not as Dr. Wooley opines because the particular operating condition that a device is in at a particular time is represented by the measurement taken by the sensor, 11 Some claim language less relevant to construing “target value” was omitted for ease of reference. which the controller then uses to determine whether the measurement satisfies the “target value.” Additionally, claim 1 recites that the “target value” is sent as part of a command to the controller. The “target value” is not sent to the controller from the sensor, as might be expected if the plain and ordinary meaning of “target value” were as Dr. Wooley opines. Petitioner and Dr. Wooley’s construction would also result in “target value” meaning effectively the same thing as the measurement of the fluid by the sensor, a concept that is separately recited in claim 1 and to which the “target value” is compared. The Specification of the ’680 patent does not support Petitioner’s understanding of the plain and ordinary meaning of “target value.” Although the Specification does not recite “target value,” it recites “target state,” and describes “target state” sufficiently to understand the plain and ordinary meaning of “target” as used in “target value” and “target state.” In particular, the ’680 patent explains that “[i]n some embodiments, the process 104 includes receiving, via a network interface, from a remote user device, (e.g., via a command-center server) a command to change a state of a fluid-handling device to a target state.” Ex. 1001, 11:48–51. This portion reflects that the command is seeking to change a state of a fluid-handling device to a target state. In other words, the “target value” or “target state” is not generally “the particular operating condition that a device is in at a particular time”; rather, it is a value or state that the fluid-handling device is desired to be in, as Patent Owner and Dr. Durham explain. Additionally, just as claim 1 recites a directional component for the “target value” to be sent to the controller in a command, so too does the Specification describe a “target state” as being sent in a command from a remote user device. Thus, the Specification clearly supports the plain and ordinary meaning proposed by Patent Owner and Dr. Durham and not the plain and ordinary meaning proposed by Petitioner and Dr. Wooley. slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“time-stamped process data, report exception therein to the remote host, and extract and transmit time-stamped process data to the remote host.” Ex. 1005, Abst. (emphases added). Almadi explains that its remote field systems must include a plurality of controller units “to issue commands to, and gather and process data from a plurality of field devices, including remote systems and instruments, . . . [and] a database server for the storage of process data retrieved from the remote subsystems and instruments.” Id. at 2:22–30 (emphases added). Based on these disclosures, we agree with Patent Owner that Petitioner has not established that Almadi discloses element [1.4]. Specifically, the teachings from Almadi identified by Petitioner refer to process data, which is data retrieved from the remote subsystems/field devices. Thus, we understand that Almadi’s teaching—of using an Ethernet switch to transmit “process data”—describes transmitting data from the remote subsystems/field devices. See Ex. 1005, 3:13–17, cited in Pet. 15. But claim 1 and particularly element [1.4], recites “sending, with the server, the target value to the network address [which identifies a controller of the fluid-handling device13] via the network,” which is different than sending process data from the field devices to the remote host or database server for storage.” slip op. at 19
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,175,680 - Tanklogix, LLC v. SiteproInstitution deniedPTAB · Oct 10, 2025 · IPR2025-00650 · APJ Sheila F Mcshane · IPR · Institution
The Board denied institution because Petitioner did not show a reasonable likelihood that claims 18–32 and 34 were unpatentable over Kahn or Kahn and Gutierrez.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). Upon consideration of the Petition, the Preliminary Response, and the evidence of record, we determine that Petitioner has not established a reasonable likelihood of prevailing with respect to the unpatentability of at least one claim of the ’871 patent. Accordingly, for the reasons that follow, we decline to institute an inter partes review of claims 18–32 and 34 of the ’871 patent.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“The respective proposed levels of qualifications for a person of ordinary skill in the art are similar, with Patent Owner proposing two years of experience compared to Petitioner proposing significant experience with remotely controlling fluid-handling devices, like SCADA systems. Patent Owner also proposes more extensive experience in lieu of educational experience. While we find Petitioner’s proposed qualifications to be acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of skill necessary to understand and implement the teachings of the ’871 patent and the asserted prior art. Our analysis and findings herein, however, do not turn on any differences in the qualifications adopted.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“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 10
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“actuators and the remote control of fluid handling devices, including the receipt with the user-interface module of “a user command to actuate an actuator via a presented control interface” (limitation [18.7]) and “account authorized to send commands to remotely control fluid handling devices” (limitation [18.11]). We agree with Patent Owner that the Petition fails to demonstrate that Kahn discloses or teaches these limitations because the evidence does not provide support that there is remote control of fluid handling devices or the use of a user command on a control interface to send a command to a fluid handling device, for instance. Kahn is directed to providing access to fluid sensing data and analyzing and providing visual information on that data, but we do not discern that it teaches or discloses the capability to remotely control fluid handling devices. See, e.g., Ex. 1005, code (54), 1:27–36, 2:50–3:2. More specifically, the Kahn disclosures that Petitioner repeatedly relies upon for allegedly teaching this control are deficient. See Ex. 1005, 10:62–67, 14:35– 15:2, 15:62–16:32; see also Pet. 12–14, 16–18. Kahn discloses that “the communication unit 112B can include on-site alerts such as optical (indicator lights), audible alerts (e.g., alarm sounds), tactile (e.g., vibration of the unit) or can be interfaced to an appropriate control valve for simply shutting off the supply of fluid upon the detection of emergency events, for instance.” Ex. 1005, 10:62–67. Communication unit 112B is part of the local “sensor unit,” wherein the detection conditions determined by the sensor are communicated to remote devices by communication unit 112B. See id. at 3:31–33, 5:62–6:2, 6:27–35, 7:33–37, 13:7–12, Figs. 1A–1C. Kahn discloses that the sensor units, which include communication units 112B, can be located near shut-off valves and can communicate with distant locations. See id. at 11:1–13. There are no disclosures, however, in the above passages that there is remote control of fluid handling devices, that there is a user command on a control interface that actuates an actuator, or that there is a command sent to the facility actuators via a network connection, as required in limitations [18.5]–[18.7] and [18.9]–[18.12], respectively. Rather, the disclosure indicates that the communication unit 112B includes on-site alerts and that the local (non-remote) communication unit 112B can be interfaced with the control valve.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,488,871 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.InstitutedPTAB · Jul 29, 2025 · IPR2025-00491 · APJ Frederick C Laney · IPR · Institution
The Board instituted IPR of claims 1–18 on all asserted grounds after finding a reasonable likelihood that claims 1, 9, and 15 are unpatentable over Ground 1.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is 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.” slip op. at 26
- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioners contend that a person having ordinary skill in the art would have had “Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field. Additional educational experience could substitute for some of the work experience.” Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). Patent Owner does not dispute this position at this time. See generally Prelim. Resp. For purposes of this Decision, we adopt Petitioners’ 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 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionTerm construed board ownDecided for patent owner
“We do not agree with Patent Owner that “fixed” or “configurable” requires more than what is agreed to by the parties––i.e., the characteristics and operational parameters of the endpoint are either set prior to operation or can be set during operation. We disagree that the ’972 patent defines “fixed or a configurable endpoint” as “a number of descriptive fields of the endpoint.” Rather column 8, lines 5–6, of the ’972 patent states that “[a]n endpoint is defined by a number of descriptive fields,” which speaks more about the mechanism used to establish the characteristics and operational parameters of the endpoint than it does about how “fixed” or “configurable” would be understood by a skilled artisan. And the fact that an endpoint may be defined by descriptive fields does not inform a skilled artisan that “fixed” or “configurable” requires the endpoint to allow the processing device to correctly interpret and utilize the data from the endpoint. Correctly interpreting and utilizing data may be the goal, but that goal is not turned into a requirement of the claims because the recited endpoint is fixed or configurable. Similarly, there is no basis for making that goal a requirement simply because a fixed endpoint is described as providing basic functionality and a configurable endpoint is described as being configurable by the base unit either while pairing or via the processing device. As a result, we find little merit in Patent Owner’s contention that the language “fixed or a configurable” requires a process for setting up the characteristics and operational parameters of an endpoint within a device so that the processing device can correctly interpret and utilize the data of this endpoint. Patent Owner, however, will have an opportunity during trial to further develop this contention.” slip op. at 11
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableInstituted
“Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is 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. Petitioners’ offers evidence, supported by its expert declarant, that the endpoints disclosed in Beel are either fixed, such as a mass storage unit with predefined characteristics, or configurable, such as a virtual audio interface that may change configuration based on driver instructions or use context. Pet. 32–33. As Petitioners point out, the ’972 patent itself acknowledges that Beel’s Figure 11 illustrates a system comprising a combination of vendor-specific and standard endpoints, and further interprets these endpoints to correspond to drivers and host applications used for functionality like screen sharing and audio streaming, which demonstrates a direct conceptual and structural alignment between the ’972 patent and Beel. Id. Furthermore, Petitioner’s evidence demonstrates sufficiently that Beel describes a peripheral device acting as a virtual composite device capable of emulating different functions—such as a USB audio speaker—while rerouting the data stream (e.g., RTP audio stream) over the network. Id. For instance, Petitioners’ evidence demonstrates sufficiently Beel discloses or suggests that audio data can be captured by a virtual sound card interface implemented within the peripheral device, re-encoded, and transmitted to the base unit for playback or synchronization with video content. Id. In addition, Petitioners have demonstrated sufficiently that Beel’s architecture supports the requirement that the endpoint of the functional device—whether it is a camera, microphone, or speaker—is made available through or exposed on the peripheral device. Id. The functional device’s capabilities are effectively rendered accessible to the processing device by way of the peripheral device, which acts as an intermediary. Id. Petitioners’ evidence demonstrates sufficiently that this exposure can occur via logical interfaces, such as USB Audio Class (UAC) virtual drivers, that allow the processing device to recognize and interact with these endpoints using standard protocols. Id. Furthermore, Petitioners show sufficiently Beel discloses that the peripheral device may include software that facilitates communication with and presentation of media content on the processing device, further demonstrating that the endpoints are not only present but also actively used for data transmission. Id. Patent Owner’s arguments, at least at this stage of the proceeding, fail to undermine Petitioners’ showing because they are largely just that–– attorney arguments––without sufficient evidentiary backing and because they lack sufficient clarity regarding how the recited claim language distinguishes Beel’s disclosed system. First, Patent Owner makes several representations that Petitioners misplace its reliance on certain teachings or suggests found in Beel and that Beel does not support the contention Petitioners make, but Petitioners’ positions are backed the testimony of Dr. Almeroth and Patent Owner offers no contradictory evidence for why a skilled artisan would understand Beel differently. And, suffice it to say that, when the declaration of Dr. Almeroth is considered in juxtaposition with the cited evidence from Beel, we have found declarant Dr. Almeroth sufficiently persuasive to demonstrate Petitioner is reasonably likely to prevail on the point. For example, Patent Owner simply argues that “there is no indication in Beel of using any fixed or a configurable endpoint of the functional device exposed or made available on the first peripheral device” (Prelim. Resp. 31), but declarant Dr. Almeroth states that “Beel discloses that a peripheral device can act as a ‘virtual audio device’ using a USB Audio Class (UAC) interface,” which “indicates that endpoints of the functional device are ‘exposed or made available on the first peripheral device’” (Ex. 1002 ¶ 130 (emphasis added); see also id. ¶¶ 128–129). Patent Owner’s argument, without any evidentiary support, does little to undermine the opinion testimony from Dr. Almeroth about what Beel’s teachings would indicate to a skilled artisan. Second, although Patent Owner repeatedly states that Beel fails to” slip op. at 26
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,684,972
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.