• 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
• Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Sep 17, 2026 · IPR2025-00562 · APJ Thu A Dang · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board also finds the claims unpatentable under the Broadcom grounds.

  RulingsFinal written decision

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner

    “IPR2024-00783, Ex. 1001, 22:36–49. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112 ¶ 6. See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112 ¶ 6 is not overcome.” slip op. at 17

  • Skill levelOther

    “differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We find persuasive Dr. Wolfe’s supporting testimony that a POSITA would have understood the terms “PDK” and “RDC” to have “definite structure.” Ex. 1013 ¶¶ 35–56. In particular, we find persuasive Dr. Wolfe’s testimony that the term “PDK,” for example, “encompasses at least ‘a collection of circuit components that includes an antenna, a transceiver, and a controller and memory for storing information particular to a user.’” Id. ¶ 35. Dr. Wolfe’s testimony is consistent with the Specification of the ’188 patent. See Ex. 1001, 5:42–6:7, 3:48–62. In particular, the Specification of the ’188 patent describes a microchip that stores information in memory and responds through an antenna when probed, which is consistent with Dr. Wolfe’s testimony. Id.; Ex. 1001, 1:30–62.” slip op. at 19

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

    “differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25

  Patent outcomesUS 9,049,188 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,049,188
• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Sep 3, 2026 · IPR2025-00673 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–7 are unpatentable as obvious over the combined teachings of the asserted references, including Shin and Aoyama and Shimomura and Iwase.

  RulingsFinal written decision

  • PTAB / AIA Trials › Motions to amend / substitute claimsOther

    “1 SoundClear also filed a Contingent Motion to Amend that proposed to replace originally challenged claim 5 of the ’675 patent with proposed substitute claim 8. Paper 21. We, however, granted SoundClear’s request to withdraw its Contingent Motion to Amend and, as a result, the Contingent Motion to Amend will no longer be considered in this proceeding. Paper 30.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 21

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

    “combination because (1) configuring Shin’s processor 120 accordingly “would have been trivial, involving straightforward changes to enhance the processor’s approach to simplifying and abbreviating its output”; and (2) this approach was well-known as evidenced by Ha’s disclosure of replacing “team meeting” and “date” with “schedules” based on the user’s environment.6 Id. at 27–28 (first quoting Ex. 1011 ¶ 97, then quoting Ex. 1011 ¶ 98) (citing Ex. 1002 ¶ 102; Ex. 1011, Fig. 7).” slip op. at 33

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “4. Dr. Stern’s Testimony is Reliable In its Patent Owner Response, SoundClear contends that “Dr. Stern’s” slip op. at 125

  Patent outcomesUS 11,244,675 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,244,675
• 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
• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.

  RulingsFinal written decision

  • BurdenOther

    “Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  Patent outcomesUS 11,069,337 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,069,337
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision

  Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. 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)). D.” slip op. at 12

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

    “search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24

  Patent outcomesUS 7,370,035 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 7,370,035
• Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9

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

    “In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23

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

    “different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27

  Patent outcomesUS 10,552,490 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 10,552,490
• Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentable
  PTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision

  Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther

    “Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. 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)).” slip op. at 11

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

    “We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34

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

    “Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42

  Patent outcomesUS 9,633,139 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,633,139
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co. Ltd.Adverse judgment
  PTAB · May 19, 2026 · IPR2025-01327 · APJ Sheila F Mcshane · IPR · Adverse judgment

  The Board entered adverse judgment against Throughtek on claims 1–19 after finding it abandoned the contest by failing to file mandatory notices or respond to the show-cause order.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “The Order to Show Cause explained that under 37 C.F.R. § 42.73(b), “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” Paper 8, 3. The Order to Show Cause also explained that failure to participate in a proceeding, such as failure to file mandatory notices as required under 37 C.F.R. § 42.8, may be considered abandonment of the contest and result in adverse judgment against Patent Owner under 37 C.F.R. § 42.73(b). Id. (citing Cellpak, Inc. v. Mambate USA Inc., IPR2021-00007, Paper 4 at 2 (PTAB Mar. 23, 2021)). The Order to Show Cause gave Patent Owner ten calendar days to show cause why adverse judgment should not be entered against it. Id. Patent Owner did not respond to the Order to Show Cause. More than ten calendar days have elapsed since the date the Order to Show Cause was entered, and Patent Owner has not filed mandatory notices. In view of Patent Owner’s failure to file mandatory notices within the specified time period, we determine that Patent Owner has abandoned the contest. Pursuant to 37 C.F.R. § 42.73(b)(4), we construe Patent Owner’s abandonment of the contest as a request for adverse judgment. Under these circumstances, we determine that entry of judgment against Patent Owner is appropriate.” slip op. at 3

  None
  Patents in suitUS 9,727,655
• Taiwan Semiconductor Manufacturing Company Ltd. v. Marlin Semiconductor LimitedAdverse judgment
  PTAB · May 13, 2026 · IPR2025-01444 · APJ George R Hoskins · IPR · Adverse judgment

  The Board granted Patent Owner’s request for adverse judgment after it disclaimed the entire patent term, entering judgment against claims 1–6.

  RulingsAdverse judgment

  • Adverse judgmentAdverse judgmentGranted

    “A party may request entry of adverse judgment against itself at any time during an inter partes review proceeding. See 37 C.F.R. § 42.73(b). In addition, “[a]ctions construed to be a request for adverse judgment include: (1) Disclaimer of the involved application or patent; [and] (2) Cancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” Id. Because Patent Owner has explicitly requested adverse judgment against itself pursuant to Rule 42.73(b), and has disclaimed the entire term of the ’584 patent, Patent Owner’s request for adverse judgment is granted. ORDER In consideration of the foregoing, it is hereby: ORDERED that Patent Owner’s Request for Adverse Judgment is granted; and FURTHER ORDERED that adverse judgment is entered against Patent Owner with respect to claims 1–6 of the ’584 patent.” slip op. at 3

  None
  Patents in suitUS 7,547,584

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.