• Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentable
  PTAB · Oct 14, 2026 · IPR2025-00712 · APJ Kevin W Cherry · IPR · Final written decision

  Claims 1, 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 were not shown unpatentable because Walker was not prior art and Kelly did not teach limitations 1[d.i] and 1[d.ii].

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference not prior artPriority date awardedDecided for patent owner

    “b) Walker Priority Date Under Dynamic Drinkware, the Petitioner is required to show that “the provisional application provides support for the claims of the patent or published application.” In re Riggs, 131 F.4th 1377, 1384 (Fed. Cir. 2025). Thus, Petitioner must show that (1) at least one claim of Walker is supported by its provisional (U.S. Provisional Application No. 60/378,289 (the “’289PROV”) and (2) the specific subject matter relied upon as prior art is supported by the ’289PROV. Id. Petitioner does provide a detailed explanation about how the ’289PROV supports claim 1 of Walker. See Reply 5–10. However, as Patent Owner argues, Petitioner fails to show that the ’298PROV provides support for the specific subject matter relied on in Walker. See Sur-Reply 3–9. Petitioner only explains how the ’298PROV discloses “predetermined criteria” but does not provide any other explanation for how the other subject matter relied on in Walker is supported by the ’298PROV. Thus, we find that Petitioner has failed to show that Walker is entitled a priority date before May 1, 2003. See Riggs, 131 F.3d at 1384 (noting while “a prior art patent or published application cannot be accorded the benefit of its provisional application’s filing date absent a showing that the provisional application provides support for the claims of the patent or published application,” the challenger must also show that “the specific portions of the patent specification identified and relied on” to demonstrate purported invalidity have written description support).” slip op. at 25

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “evidence that Kelly teaches limitations 1[d.i] and 1[d.ii]. As Patent Owner persuasively argues, “the recorded information regarding particular game play events” of limitations 1[d.i] and 1[d.ii] refers to “memory to . . . record game play information regarding particular game play events” in limitation 1[b.ii], but Petitioner does not map “the game play events” identified in limitation 1[b.ii] to limitations 1[d.i] and 1[d.ii]. In its Reply, Petitioner does not dispute Patent Owner’s assertion, but largely reiterates its arguments from the Petition. However, none of these arguments or evidence demonstrates that the “game play events” in limitations 1[d.i] and 1[d.ii] are same the “game play events” that are allegedly stored in limitation 1[b.ii]. Even if we accept Petitioner’s contention that it was not identifying button presses or the “game identifier,” but rather includes “game states and game events in the game process,” Petitioner provides no evidence or even arguments that what it has identified here relates to what it has identified for limitations 1[d.i] and 1[d.ii]. See Pet. 29–33 (citing Ex. 1005, 25:23–24, 26:59–27:1, 32:27–33, 37:1–10, 38:66–39:7 40:33–45, 56:49–51, 57:27–33). For these reasons, Petitioner has failed to show by a preponderance of the evidence that Kelly teaches or suggests limitations 1[d.i] and 1[d.ii]. Accordingly, we find that Petitioner has failed to show that claim 1 would have been obvious over Kelly. 2. Claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 Claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 all depend (either directly or indirectly) from claim 1. See PO Resp. 16 (explaining that the arguments for independent claim 1 also apply to the dependent claims inherent the deficiencies asserted with respect to the independent claims). We find Patent Owner’s arguments availing, as explained above. Accordingly, we find that Petitioner has failed to show by a preponderance of the evidence that claims 3–9, 13, 17, 18, 23, 25, 26, 28, and 29 would have been obvious over Kelly.” slip op. at 44

  • Expert testimonyPetitioner expert creditedDecided for patent owner

    “programmable variable parameter sets to achieve the mandated parameters,” we find that Patent Owner sufficiently explained “the notes from the 12/4/02 meeting reflect that the inventors proposed that their invention could raise the global payout percentage ‘to 75%’ – a mandated parameter – by ‘increas[ing] % of wins by the level 2,’ i.e., a secondary game level – a variable parameter.” See PO Resp. 28–32, 37, 38; Ex. 2016; Ex. 2017 ¶¶ 23–24, 41–42; Ex. 2012 ¶ 90, 63–64. Indeed, Mr. Crevelt confirmed that that a POSITA would unequivocally regard disclosure of “win rate[s]” and “global payout percentage[s]” as disclosing the claimed “mandated parameters” that are achieved by utilizing variable parameters. See Ex. 2020, 15:7–18:4, 19:14–21:16, 24:25–25:15 (global payout percentages), 21:18– 24:24 (win rates).” slip op. at 33

  Patent outcomesUS 11,393,279 not shown unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,393,279
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCNo claims unpatentable
  PTAB · Oct 14, 2026 · IPR2025-00708 · APJ Kevin W Cherry · IPR · Final written decision

  Claims 1, 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 were not shown unpatentable over Kelly or Walker and Schneier.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art (“POSITA”). In assessing the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (quoting Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “[O]ne or more factors may predominate.” Id. Based on the testimony of Mr. Crevelt, we determine that a person of ordinary skill in the art would have had at least a bachelor’s degree in computer science or computer engineering, with at least three years of experience in game development. Pet. 14 (citing Ex. 1003 ¶¶ 62–65). Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Id. We determine that the level of ordinary skill in the art adopted above is consistent with the level of technical understanding and competence reflected in the ’336 patent Specification and the asserted prior art references, based on our review of the record. Patent Owner states that “[f]or the purposes of this response, Patent Owner does not dispute Petitioners’ proposed level of skill, and under any level of skill a POSITA would not understand the asserted Grounds to raise any unpatentability issue,” and “this POR and supporting declarations apply Petitioner’s proposed level of skill.” PO Resp. 8. Thus, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’336 patent and the asserted prior art, and we apply it in our obviousness analysis below.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We determine that no terms require express construction to resolve the parties’ disputes in this case. See id. slip op. at 13

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

    “b) Walker Priority Date Under Dynamic Drinkware, the Petitioner is required to show that “the provisional application provides support for the claims of the patent or published application.” In re Riggs, 131 F.4th 1377, 1384 (Fed. Cir. 2025). Thus, Petitioner must show that (1) at least one claim of Walker is supported by its provisional (U.S. Provisional Application No. 60/378,289 (the “’289PROV”) and (2) the specific subject matter relied upon as prior art is supported by the ’289PROV. Id. Petitioner does provide a detailed explanation about how the ’289PROV supports claim 1 of Walker. See Reply 6–12. However, as Patent Owner argues, Petitioner fails to show that the ’298PROV provides support for the specific subject matter relied on in Walker. See Sur-Reply 3–8. Petitioner only explains how the ’298PROV discloses “predetermined criteria” but does not provide any other explanation for how the other subject matter relied on in Walker is supported by the ’298PROV. Thus, we find that Petitioner has failed to show that Walker is entitled a priority date before May 1, 2003. See Riggs, 131 F.3d at 1384 (noting while “a prior art patent or published application cannot be accorded the benefit of its provisional application’s filing date absent a showing that the provisional application provides support for the claims of the patent or published application,” the challenger must also show that “the specific portions of the patent specification identified and relied on” to demonstrate purported invalidity have written description support).” slip op. at 24

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “We find that Petitioner has failed to show by a preponderance of the evidence that Kelly teaches limitation 1[f]. As Patent Owner persuasively argues, “the game play events” of limitation 1[f] refers to “game play events” in limitation 1[d], but Petitioner does not map “the game play events” identified in limitation 1[d] to limitation 1[f]. In its Reply, Petitioner does not dispute Patent Owner’s assertion, but merely reiterates its arguments from the Petition. See Reply 23–24, 26. However, none of these arguments or evidence demonstrates that the “game play events” in limitation 1[f] are same the “game play events” that are allegedly stored in limitation 1[d]. Even if we accept Petitioner’s contention that it was not identifying button presses, but rather includes “game states and game events in the game process,” Petitioner provides no evidence or even arguments that what it has identified here relates to what it has identified for limitation 1[f]. See Pet. 25–26 (citing Ex. 1005, 25:23–24, 32:27–33, 40:33–45, 56:49–51). For these reasons, Petitioner has failed to show by a preponderance of the evidence that Kelly teaches or suggests limitation 1[f]. Accordingly, we find that Petitioner has failed to show that claim 1 would have been obvious over Kelly. 2. Claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 Claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 all depend from claim 1. See PO Resp. 16 (explaining that the arguments for independent claim 1 also apply to the dependent claims inherent the deficiencies asserted with respect to the independent claims). We find Patent Owner’s arguments availing, as explained above. Accordingly, we find that Petitioner has failed to show by a preponderance of the evidence that claims 3–5, 12, 13, 18–20, 22, 24–26, 29, 42, 44–47, and 50 would have been obvious over Kelly.” slip op. at 40

  Patent outcomesUS 8,529,336 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,529,336
• 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
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Aug 20, 2026 · IPR2025-00343 · APJ Scott A Daniels · IPR · Final written decision

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

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

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

  • Prior constructionPrior construction adoptedDecided for petitioner

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

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

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

  • BurdenNot shown unpatentable

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

  Patent outcomesUS 10,292,138 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,292,138
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jul 21, 2026 · IPR2025-00342 · APJ Scott A Daniels · IPR · Final written decision

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

  RulingsFinal written decision

  • Adverse judgmentOther

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

  • Skill levelSkill level petitioner adoptedDecided for petitioner

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

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

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

  • Expert testimonyPatent owner expert creditedDecided for patent owner

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

  Patent outcomesUS 7,336,805 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Markman · KSR · Graham
  Patents in suitUS 7,336,805
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jun 23, 2026 · IPR2025-00219 · APJ Frederick C Laney · IPR · Final written decision

  Claims 11–22 were not shown unpatentable under any § 103 ground because the prior art did not teach or suggest receiving the claimed resource allocation and multi-level TPC command on one physical channel.

  RulingsFinal written decision

  • BurdenNot shown unpatentable

    “onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). Moreover, a petitioner should 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284 (2011), amended 35 U.S.C. § 103, effective March 16, 2013. Because the application from which the ’153 patent issued claims priority to an application filed before this date, the pre-AIA version of § 103 applies. not “place the burden on [the Board] to sift through information presented by the Petitioners, determine where each element [of the challenged claims] is found in [the cited references], and identify any differences between the claimed subject matter and the teachings of [the cited references.]” Google Inc. v. EveryMD.com LLC, IPR2014-00347, Paper 9 at 25 (PTAB May 22, 2014).” slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “The second and third asserted benefits—reduced complexity and reduced latency—rest on the declaration of Dr. Kotzin (Ex. 1003 ¶ 64) rather than on any disclosure of Andersson or Khan. We accord that testimony little weight on this point because it asserts the benefits in conclusory terms without explaining why they would result from inserting a scheduling grant into Andersson’s undefined “other bits,” as distinct from Khan’s separate-slot design.” slip op. at 20

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A. Level of Ordinary Skill in the Art Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 14. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’500 Patent. Therefore, we adopt it as the ordinary level of skill of an artisan in the field of the patented technology for our analysis below.” slip op. at 7

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

    “Patent Owner offers a proposed construction for the recited “single physical channel” found in limitation 11.2 and “an accumulation of TPC commands” found in independent claims 12 and 18. PO Resp. 9–17. Petitioner likewise addresses the scope of an accumulation of TPC commands, but Petitioner does not contest directly Patent Owner’s proposed construction for “single physical channel.” Pet. Reply 2–7. We determine, however, that no express construction of any claim term is necessary to resolve the dispute between the parties. 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 8

  Patent outcomesUS 9,706,500 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,706,500
• Tesla, Inc. v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Jun 22, 2026 · IPR2025-00217 · APJ Frederick C Laney · IPR · Final written decision

  The Board held claims 1–5, 10–15, and 20 not unpatentable under four §103 grounds because the petitioner did not establish the claimed enabled-accumulation indication or single-channel combination.

  RulingsFinal written decision

  • BurdenNot shown unpatentable

    “onset to show with particularity why the patent it challenges is 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112-29, 125 Stat. 284 (2011), amended 35 U.S.C. § 103, effective March 16, 2013. Because the application from which the ’153 patent issued claims priority to an application filed before this date, the pre-AIA version of § 103 applies. 2 US 6,334,047 B1, iss. Dec. 25, 2001 (Ex. 1009). 3 US 2001/0036238 A1, pub. Nov. 1, 2001 (Ex. 1010) 4 US 2004/0190485 A1, pub. Sept. 30, 2004 (Ex. 1005). 5 US 2004/0077370 A1, pub. Apr. 22, 2004 (Ex. 1008). 6 US 6,600,772 B1, iss. July 29, 2003 (Ex. 1004). 7 US 6,529,741 B1, iss. Mar. 4, 2003 (Ex. 1007). unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). Moreover, a petitioner should not “place the burden on [the Board] to sift through information presented by the Petitioners, determine where each element [of the challenged claims] is found in [the cited references], and identify any differences between the claimed subject matter and the teachings of [the cited references].” Google Inc. v. EveryMD.com LLC, IPR2014-00347, Paper 9 at 25 (PTAB May 22, 2014).” slip op. at 5

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “A. Level of Ordinary Skill in the Art Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 15. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’153 patent. Therefore, we adopt it as the ordinary level of skill of an artisan in the field of the patented technology for our analysis below.” slip op. at 7

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

    “apparent agreement between the parties: “TPC command accumulation” refers to a process that collects and uses TPC commands from a network device to cumulatively affect transmission power. And having studied the intrinsic record of the ’153 patent, we are in accord. But, we decline to further limit the construction of “TPC command accumulation” in the manner proposed by either party––i.e., (1) each TPC command adjustment must be summed to cumulatively affect transmission power (as proposed by Petitioner) or (2) a TPC command value must be added to an integrator. Although both parties are able to point to disclosures in the ’153 Patent where the TPC command accumulation of an exemplary embodiment is described as using an integrator and/or summing each TPC command adjustment to cumulatively affect a UE’s transmission power (PO Resp. 16 (citing Ex. 1001, 3:39–43, 7:15–29, 9:27–42; Ex. 2016 ¶¶ 35–42); Pet. Reply 4–5 (citing Ex. 1001, 3:39–43, 7:2–6, 7:8–22, 9:28–40)), neither party has demonstrated persuasively that the intrinsic record of the ’153 Patent demonstrates a clear intent to limit “TPC command accumulation” to those particular embodiments.” slip op. at 11

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

    “A rationale supports obviousness only where the proffered benefit would flow from the specific modification proposed; a benefit that the prior art realizes in a different structural context does not, without more, establish that the same benefit would result from inserting one reference’s element into the other. On this record, the nexus between Khan’s benefits and Petitioner’s “other bits” modification is missing.” slip op. at 40

  Patent outcomesUS 10,952,153 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,952,153
• 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

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.