• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00710 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1–7, 9, 13, and 16–20 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 8 was not shown unpatentable under either ground.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’294 patent and the asserted prior art references. See 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 7

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

    “Petitioner indicates that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction. Thus, no express construction is required.” Pet. 13 (citing Ex. 1003 ¶ 86). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

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

    “rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “and reliance on Figure 19 do not in any way explain how updating game costs by meter 502 with a new Cost_Table is relevant to a credit multiplier or even a multiplier being varied over time. Ex. 1003 ¶ 155. Considering this evidence, we determine that Petitioner and Mr. Crevelt’s reliance mainly on snippets from Schneier’s “Updating Cost Information protocol” embodiment does not sufficiently explain why or how a person of ordinary skill in the art would have understood updating game cost to encompass varying a multiplier of credits over time. We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004:158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to persuasive evidence in Schneier as to how or why a person of ordinary skill in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 8.” slip op. at 20

  Patent outcomesUS 10,825,294 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,825,294
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00709 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1, 2, 4, 6, 8, 10, 14–18, 21–23, 25, 27, and 29 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 9 was not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner states it “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.” PO Resp. 4. Patent Owner states further that “this [Patent Owner Response] and supporting declarations apply Petitioner’s proposed level of skill.” Id. On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’635 patent and the asserted prior art references. See 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 7

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

    “Petitioner indicated in the Petition that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction.[] Thus, no express construction is required.” Pet. 12–13 (citing Ex. 1003 ¶ 85). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004, 158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. Id. at 161:2–6. These explanations are unpersuasive because the testimony relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 9.” slip op. at 21

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

    “Discount Credit Pricing Structure The $0.20 discount described by Schneier for purchasing 20 credits, rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not address the idea of a time component, i.e., “over time,” as required by claim 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 18

  Patent outcomesUS 10,650,635 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,650,635
• Axon Enterprise, Inc. / Dedrone Holdings, Inc. et al. v. Airspace Defense, Inc.Some claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00629 · APJ Scott C Moore · IPR · Final written decision

  Original claim 12 is not unpatentable; substitute claim 37 is added, while substitute claims 21–28 and 30–36 are denied as obvious.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “F.3d at 1279–80, we begin our analysis with the Specification of the ’711 Patent. The Specification indicates when a UAV (such as the recited “reference aerial vehicle”) navigates autonomously, it flies without manual control, and can, for example, track and fly to a target using information captured onboard the vehicle itself. See Ex. 1001, 3:24–28 (“[I]t may not be desirable to manually control the interceptor aerial vehicle to follow the target UAV. In some embodiments, the interceptor aerial vehicle is able to autonomously track and fly to the target UAV using machine vision based on images captured by a camera of the interceptor aerial vehicle.”). The Specification also indicates that “autonomous” means more than just “automatic flight,” and clarifies that autonomous navigation occurs when a UAV that previously received a target location from an external source subsequently turns and flies itself towards the received location. See, e.g., id. at 4:15–17 (disclosing that the detected location of a target may be provided to an interceptor “to allow it to automatically and autonomously fly toward the direction of the detected location”); 15:64–16:3 (automatic and autonomous navigation occurs when an interceptor’s navigation component and/or flight controller receive the location of a target, and adjust the interceptor “to turn and fly towards the received location . . . based on the received location”); 16:49–60 (“For example, a flight direction and/or speed of an interceptor aerial vehicle are automatically and autonomously adjusted based on a location and size of the target within the captured image. . . . This allows the flight path of the interceptor aerial vehicle to be dynamically adjusted to track and follow a moving target.”).” slip op. at 11

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

    “have had reason to combine Beard and Laufer in the manner proposed by Petitioner, the combination would not satisfy the Autonomous Navigation limitation required by claim 12 because Laufer’s autopilot commands are generated by and transmitted from a remote command center (i.e., Laufer’s central controller 115). PO Resp. 15–16. In its Reply, Petitioner does not dispute that Laufer’s autopilot commands are generated by Laufer’s central controller 115, which is remote from the aircraft being controlled. See Reply 13–17. Petitioner asserts, however, that the combination still satisfies the Autonomous Navigation limitation because these autopilot commands are generated without human input. See id. Based on the complete trial record, Patent Owner’s arguments are persuasive. See PO Resp. 15–16; PO Sur-reply 42, 1–6; Ex. 2025 ¶¶ 84–87. The flight of Beard’s UAV 100 under the control of Laufer’s autopilot commands does not satisfy the Autonomous Navigation limitation of claim 12, as we have construed that limitation, because Laufer’s autopilot commands are generated at a location that is remote from UAV 100 (Laufer’s central controller 115.) See, e.g., Ex. 1010 ¶ 40 (“Central controller 115 uses autopilot command module 440 to generate autopilot aircraft commands”), ¶¶ 26, 30 (clarifying that central controller 115 and the controlled interceptor aircraft are separate devices that may communicate through a “wireless connection”), Fig. 4 (depicting “aircraft control commands 475” being generated externally from the depicted “Interceptor Aircraft”); see also Ex. 2025 ¶¶ 95–95. Petitioner never disputes that, in the proposed combination, Laufer’s central controller 115 would remain external to Beard’s UAV 100. See Reply 13–17. Instead, Petitioner relies on its proposed construction of the Autonomous Navigation limitation, which would have encompassed such an arrangement. See id. Our construction of the Autonomous Navigation limitation, which did not adopt Petitioner’s claim construction position, is dispositive of Petitioner’s argument. We thus determine that Petitioner has not shown by a preponderance of the evidence that claim 12 would have been obvious over Beard and Laufer.” slip op. at 15

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part

    “the legal requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121. Lectrosonics, Paper 15 at 4, 7–8. For the reasons that follow, we determine that Patent Owner has satisfied this burden. 1. Proposal of a Reasonable Number of Substitute Claims A motion to amend must “propose a reasonable number of substitute claims.” 35 U.S.C. § 316(d)(1)(B); see also 37 C.F.R. § 42.121(a)(3) (“A motion to amend may cancel a challenged claim or propose a reasonable number of substitute claims.”). “There is a rebuttable presumption that a reasonable number of substitute claims per challenged claim is one (1) substitute claim.” Lectrosonics, IPR2018-01129, Paper 15 at 4; see also 37 C.F.R. § 42.121(a)(3). Patent Owner has shown it proposes a reasonable number of substitute claims by proposing a single substitute claim for each of challenged claims 1–4, 8–11, and 13–20. MTA 1–2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 2. Amendments Respond to a Ground of Unpatentability “A motion to amend may be denied where … [t]he amendment does not respond to a ground of unpatentability involved in the trial.” 37 C.F.R. § 42.121(a)(2)(i). Patent Owner has responded to the grounds of unpatentability involved in this proceeding by amending the claims in response to the Petition’s asserted prior art. See MTA 2, 25, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 3. No Enlargement of the Scope of the Claims An amendment may not seek to enlarge the scope of the claims of the patent. 35 U.S.C. § 316(d)(3); 37 C.F.R. §§ 42.121(b)(1)–(b)(2). Patent Owner asserts that the amendments in the Motion do not enlarge the scope of the claims of the patent because each proposed substitute claim “retains all of the limitations of the corresponding challenged claim, and each proposed independent substitute claim adds further limitations.” See MTA 2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 4. No Introduction of New Matter An amendment may not introduce new matter. 35 U.S.C. § 316(d)(3);” slip op. at 22

  • 112 supportDecided for patent owner

    “Having considered the evidence and argument cited by both parties, we determine there is sufficient written description support for the disputed portions of limitations [37.e1], [37.e3,] and [37.e4]. The ’452 application discloses selecting between groups of processing schemes (e.g., algorithms) depending on a confidence level, where the groups are, for example: high cost, high robustness algorithms; medium cost, medium robustness algorithms; and low cost, low robustness algorithms. See Ex. 2019 ¶¶ 146–147. These schemes or algorithms may be neural networks. See, e.g., id. ¶ 50 (including neural network as a type of algorithm); see also id. ¶¶ 109–110); see generally MTA Opp 1 (not disputing that schemes may be neural networks). Specifically, the ’452 application describes “algorithms that process video frames of one or more video data streams,” and “produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Id. ¶ 141. The ’452 application also discloses the concept of switching between neural networks based on confidence levels. In particular, the ’452 application discloses that a “process cycles through the processing schemes to produce a detection of an object,” for example, where “if the confidence number is higher than an activation number, an action is performed to stop or change a running group (i) and select or switch to group (ii).” Id. ¶ 146. More particularly, “a processing scheme from the group of (i) High cost (low refresh rate), high robustness algorithm[s] can select a cheaper processing scheme from the group of (ii) Medium cost, medium robustness algorithms.” Id. The ’452 application additionally discloses that schemes or algorithms (e.g., neural networks) are applied to individual video frames, and that the confidence levels that determine which neural network will be applied in the future are also derived from individual video frames. For example, as discussed above, the ’452 application describes that “[t]he processing schemes produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Ex. 2019 ¶ 141 (emphases added). The ’452 application also describes selecting and applying an individual neural network, rather than only selecting and applying a group of processing schemes. For example, as highlighted above, the ’452 application describes that “a processing scheme from the” “High” group “can select a cheaper processing scheme from the” “Medium” group. Id. ¶ 146 (emphases added). In our view, these disclosures, read together, would reasonably convey to one skilled in the art that the inventor had possession of the disputed subject matter described above. See Ariad, 598 F.3d at 1351.” slip op. at 24

  Patent outcomesUS 10,514,711 mixed
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
  Patents in suitUS 10,514,711
• Siemens Industry Software Inc. v. Synopsys, Inc.Some claims unpatentable
  PTAB · Jan 11, 2023 · IPR2021-01215 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–5, 7, 8, 11–15, 17, 18, and 21–24 are unpatentable over Yoshimura-based grounds; claims 6, 9, 10, 16, 19, and 20 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “B. Level of Skill in the Art Petitioner offers an assessment as to the level of skill in the art as of the time the ’655 patent was filed. Pet. 9. For purposes of this proceeding, Petitioner and Petitioner’s declarant “adopt the [following] definition for the person of ordinary skill in the art”: “a Bachelor of Science degree in Electrical Engineering or Computer Engineering, and has either received academic credits for an ASIC design course or completed at least one year of work experience in the VLSI design, electronic design automation for VLSI, or ASIC design fields.” Id. at 9–10; Ex. 1003 ¶ 78 (Robins Declaration). Patent Owner applies the same definition. Resp. 5. To the extent necessary, we accept this definition because it is supported by the Robins Declaration and consistent with the ’655 patent and the asserted prior art.” slip op. at 7

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “Although the phrase “separate from,” is not found in the claims, we look to the language of the claims, the description in the patent disclosure, and the prosecution history to determine what type of separateness is required by the claims. We start with the relied-upon Figure 4 of the ’655 patent, which illustrates a box labeled “Multi-Scenario ECO Database 426” that is near, but not overlapping with or surrounding, boxes labeled “Image 424” through “Image 422” and “Image 420.” Ex. 1001, Fig. 4. The ’655 patent also describes a storage device 408 as “storing scenario images 420– 424 that correspond to different scenarios,” and “can additionally store multi-scenario ECO database 426,” which “can include circuit information for multiple scenarios that can be used to estimate the impact of ECOs in multiple scenarios.” Ex. 1001, 5:9–11, 5:18–21.” slip op. at 9

  • Prior constructionPrior construction adoptedDecided for patent owner

    “determin[e/ing . . . ] an ECO to fix one or more design requirement violations, wherein said determining includes identifying an ECO to fix a design requirement violation in the scenario and checking that ECO against at least some of the multiple scenarios by estimating parameter values based on parameter values stored in the scenario image and the multi-scenario ECO database. Resp. 10 (citing Ex. 2001, 21-24). In reviewing the term, the District Court explained that the multi- scenario ECO database “stores parameters and allows for a quick estimation of an ECO’s impact across multiple scenarios.” Ex. 2001, 19. The District Court further summarized the ’655 patent as describing that a scenario image is “[f]irst” loaded, and if there is a design requirement violation, an ECO is determined for that scenario, and then subsequent scenarios are loaded to check whether the ECO from the first scenario will create new, or exacerbate existing, design violations. Id. (citing Ex. 1001, 4:21–33). However, as recognized by the Court, the process at the cited section is described in the ’655 patent as an “approach [that] may take an impracticably long time to fix design requirement violations in multiple scenarios” due to the long time that is required to load a scenario image. Id. at 24; Ex. 1001, 4:43–47. The Court reasoned that in order to determine an ECO to fix a violation, “determine” must involve “identifying” a possible fix and “checking” whether that fix is suitable. Id. at 23. Thus, the District Court’s construction requires both identifying and checking as part of the claimed determining step. Id. at 23–24. We agree with the District Court’s reasoning, and apply their construction in this proceeding.” slip op. at 11

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

    “Petitioner assertion that Yoshimura’s estimation in step S5 is performed to check an identified ECO is supported by the record. In determining the change to be made (the ECO), Yoshimura uses estimated parameters for the third and fourth corner conditions, calculated in step S5 through the “Hold Margin” equation. Ex. 1007, 6:63–67. Those third and fourth corner conditions are then used to check potential layouts identified in step S6. Id. at 7:18–20 (“In step S6, the automatic EC device 16 searches for a layout that does not cause a timing error under any one of the first to fourth comer conditions from the analysis results of step S4 and step S5.”). In this manner, step S5 sets an initial third corner condition having estimated parameter values that is included, as the initial step, in checking an identified ECO at steps S6–S8. Thus, Yoshimura’s determination of a change to satisfy the corner conditions is, to use Dr. Edward’s phrase, “based on” its third and fourth corner conditions having parameters estimated in step S5. For this reason, we determine that Petitioner has sufficiently shown that Yoshimura discloses the claimed limitation.” slip op. at 20

  Patent outcomesUS 8,407,655 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,407,655
• Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentable
  PTAB · Dec 22, 2022 · IPR2019-00836 · APJ Kevin C Trock · IPR · Remand

  On remand, claims 8 and 86–89 of the ’115 patent and claims 10 and 11 of the ’560 patent are unpatentable under § 103; claims 9, 10, and 63 of the ’115 patent and claim …

  RulingsRemand decision

  • RemandOther

    “the ’560 patent, we found in the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR that Petitioner did not present sufficient evidence to show how or why a person of ordinary skill in the art would have combined Kiss and FIPA97 to obtain the recited subject matter of these claims. 810 Final Dec. 145–149; 814 Final Dec. 135; 835 Final Dec. 108. On appeal, the Federal Circuit reversed our finding and remanded “for the Board to address any remaining obviousness disputes concerning these claims.” Microsoft, 2022 WL 989403, at *3–5. On remand, Patent Owner appears to disagree with the Federal Circuit’s decision and argues that Petitioner failed to show how a person of ordinary skill in the art would have combined Kiss and FIPA97. PO Remand Opening Br. 2–9; PO Remand Resp. Br. 2. In response, Petitioner argues Patent Owner’s argument is improper because the mandate rule “prevents parties from raising issues on remand that were within the scope of the judgment appealed from and resolved by the appellate court.” Pet. Remand Resp. Br. 3–4 (citing Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999)). Petitioner further argues that the Federal Circuit has expressly resolved the question of whether the Petition has sufficiently set forth “the ‘how’ and ‘why’ of the cited combination” in favor of Petitioner and, therefore, we should not address or revisit the issue on remand. Id. at 7. We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5. Pursuant to the Federal Circuit’s decision and mandate, we address below the remaining obviousness disputes concerning claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. In the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR, we did not reach the issue of whether Petitioner has shown sufficiently that the cited combination teaches or suggests all limitations of these claims. See 810 Final Dec. 144– 149; 814 Final Dec. 132–135; 835 Final Dec. 106–109. We do so now and address the parties’ disputes regarding the teachings of the cited prior art as they relate to the limitations recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent.” slip op. at 23

  • Skill levelSkill level board ownDecided for patent owner

    “B. Level of Ordinary Skill in the Art In the Final Written Decisions, we determined that a person of ordinary skill in the art at the time of the claimed invention would have had “a Bachelor’s degree in Computer Science or equivalent field and at least two years of work experience in design and development of distributed systems, software specification languages, or a related area.” 810 Final Dec. 12; 811 Final Dec. 12; 814 Final Dec. 11; 835 Final Dec. 12; 836 Final Dec. 12. We see no reason to depart from this determination, which the parties did not challenge on appeal.” slip op. at 18

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

    “claim term “trigger” recited in claim 8. See Ex. 1003 ¶ 371. We agree with this construction because claim 8 incorporates all of the limitations of claim 1 from which it depends and the same terms appearing in different portions of a claim should be given the same meaning absent compelling evidence to the contrary. See Paragon Sols., LLC v. Timex Corp., 566 F.3d 1075, 1087 (Fed. Cir. 2009) (“We apply a presumption that the same terms appearing in different portions of the claims should be given the same meaning unless it is clear from the specification and prosecution history that the terms have different meanings at different portions of the claims.” (internal quotation marks omitted) (citations omitted)); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1334 (Fed. Cir. 2003) (“[W]e presume, unless otherwise compelled, that the same claim term in the same patent or related patents carries the same construed meaning.”). We also agree with Dr. Lieberman’s proposed interpretation of the claim term “trigger declaration” as “a statement in a program that specifies the characteristics of a trigger” (Ex. 1003 ¶ 371) because the construction is consistent with the disclosure in the Specification. See Ex. 1001, 17:5–9 (“Each registered agent may be optionally associated with one or more triggers, which preferably could be referenced through their associated Trigger Declaration fields 712 in the parent facilitator Agent Registry 702.”); see also Ex. 1003 ¶ 374 (citing Ex. 1001, 17:5–9, Fig. 7).” slip op. at 28

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

    “the ’560 patent, we found in the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR that Petitioner did not present sufficient evidence to show how or why a person of ordinary skill in the art would have combined Kiss and FIPA97 to obtain the recited subject matter of these claims. 810 Final Dec. 145–149; 814 Final Dec. 135; 835 Final Dec. 108. On appeal, the Federal Circuit reversed our finding and remanded “for the Board to address any remaining obviousness disputes concerning these claims.” Microsoft, 2022 WL 989403, at *3–5. On remand, Patent Owner appears to disagree with the Federal Circuit’s decision and argues that Petitioner failed to show how a person of ordinary skill in the art would have combined Kiss and FIPA97. PO Remand Opening Br. 2–9; PO Remand Resp. Br. 2. In response, Petitioner argues Patent Owner’s argument is improper because the mandate rule “prevents parties from raising issues on remand that were within the scope of the judgment appealed from and resolved by the appellate court.” Pet. Remand Resp. Br. 3–4 (citing Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999)). Petitioner further argues that the Federal Circuit has expressly resolved the question of whether the Petition has sufficiently set forth “the ‘how’ and ‘why’ of the cited combination” in favor of Petitioner and, therefore, we should not address or revisit the issue on remand. Id. at 7. We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5.” slip op. at 23

  Patent outcomesUS 7,069,560 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,069,560
• Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentable
  PTAB · Dec 22, 2022 · IPR2019-00835 · APJ Kevin C Trock · IPR · Remand

  Claims 8 and 86–89 of the ’115 patent and claims 10 and 11 of the ’560 patent are unpatentable over Kiss and FIPA97; the remaining remanded claims were not shown unpatentable.

  RulingsRemand decision

  • RemandOther

    “On appeal, the Federal Circuit affirmed all of our determinations of unpatentability of challenged claims. See Microsoft, 2022 WL 989403, at *1. The Federal Circuit also affirmed our “determination of no proven unpatentability of claims 29–47 of the ’115 patent and claims 50–51 and 53–55 of the ’560 patent.” Id. The Federal Circuit reversed certain findings we made in concluding that claims 8–10, 63, and 86–89 of the ’115 patent and claims 10, 11, and 28 of the ’560 patent had not been proven unpatentable and remanded for further consideration of those claims. Id. Upon our authorization (Paper 45), the parties filed additional briefing limited to addressing the remanded claims. See Petitioner’s Remand Opening Brief (Paper 50, “Pet. Remand Opening Br.”), Patent Owner’s Remand Opening Brief (Paper 51, “PO Remand Opening Br.”), Petitioner’s Remand Response Brief (Paper 53,” slip op. at 6

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

    “Circuit’s decision and argues that Petitioner failed to show how a person of ordinary skill in the art would have combined Kiss and FIPA97. PO Remand Opening Br. 2–9; PO Remand Resp. Br. 2. In response, Petitioner argues Patent Owner’s argument is improper because the mandate rule “prevents parties from raising issues on remand that were within the scope of the judgment appealed from and resolved by the appellate court.” Pet. Remand Resp. Br. 3–4 (citing Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999)). Petitioner further argues that the Federal Circuit has expressly resolved the question of whether the Petition has sufficiently set forth “the ‘how’ and ‘why’ of the cited combination” in favor of Petitioner and, therefore, we should not address or revisit the issue on remand. Id. at 7. We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5.” slip op. at 23

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

    “In the context of claim 1 from which claim 8 depends, Petitioner argued in the Petition that a “trigger” recited in claim 1 (see Ex. 1001, 29:10–24) is “a general mechanism for requesting some action be taken when one or more conditions is met.” Pet. 11 (citing Ex. 1001, 21:21–22:31; Ex. 1003 ¶¶ 80–81). Patent Owner did not dispute Petitioner’s proposed meaning of “trigger” recited in claim 1. See PO Resp. 24–38. In the Final Written Decision in the 810 IPR, we adopted this undisputed interpretation of “trigger” because the construction is consistent with the disclosure in the Specification. 810 Final Dec. 120 (citing Ex. 1001, 21:22–24 (“triggers [provide] a general mechanism for requesting some action be taken when a set of conditions is met”)). This claim construction was not appealed and, as noted above, the Federal Circuit did not address the construction of this claim term. See Microsoft, 2022 WL 989403. Considering the full record, we see no reason to depart from the claim construction of the term “trigger” the same claim construction for purposes of this Remand Decision. Petitioner and Dr. Lieberman proposed the same interpretation for the claim term “trigger” recited in claim 8. See Ex. 1003 ¶ 371. We agree with this construction because claim 8 incorporates all of the limitations of claim 1 from which it depends and the same terms appearing in different portions of a claim should be given the same meaning absent compelling evidence to the contrary. See Paragon Sols., LLC v. Timex Corp., 566 F.3d 1075, 1087 (Fed. Cir. 2009) (“We apply a presumption that the same terms appearing in different portions of the claims should be given the same meaning unless it is clear from the specification and prosecution history that the terms have different meanings at different portions of the claims.” (internal quotation marks omitted) (citations omitted)); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1334 (Fed. Cir. 2003) (“[W]e presume, unless otherwise compelled, that the same claim term in the same patent or related patents carries the same construed meaning.”). We also agree with Dr. Lieberman’s proposed interpretation of the claim term “trigger declaration” as “a statement in a program that specifies the characteristics of a trigger” (Ex. 1003 ¶ 371) because the construction is consistent with the disclosure in the Specification. See Ex. 1001, 17:5–9 (“Each registered agent may be optionally associated with one or more triggers, which preferably could be referenced through their associated Trigger Declaration fields 712 in the parent facilitator Agent Registry 702.”); see also Ex. 1003 ¶ 374 (citing Ex. 1001, 17:5–9, Fig. 7).” slip op. at 27

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

    “Patent Owner’s argument is unavailing because, as discussed above, Dr. Lieberman persuasively explained that in FIPA97’s FIPA-AVEB- Request-Notification contract-net “[t]he GA is responsible for the creation and management of a content index, and uses this index to respond to requests from the CA” (Ex. 1003 ¶ 373 (citing Ex. 1011, 11)) and that a person of ordinary skill in the art would have understood that, for the GA to monitor for changes over a given time period and inform the CA of any changes to the status of a specific AV program that conform to a precondition “preconditions2” within that period, “the agent registry must include declaration functionality” for preconditions relating to the status of AV programs (id. ¶ 374). We are persuaded that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary skill in the art that the GA’s context index (the claimed “agent registry data structure”) includes a statement of a precondition relating to a specific AV program listed in the content index. In its remand paper, Patent Owner argues that “nothing in Part 6 FIPA97 explicitly teaches that a precondition2 is stored within a General Agent as asserted by Petitioner.” PO Remand Resp. Br. 7 (underlined emphasis added). Patent Owner’s argument is unavailing because Petitioner’s asserted theory of unpatentability is one of obviousness, not anticipation. Thus, Petitioner need not show “FIPA97 explicitly teaches that a precondition2 is stored within a [Guide] Agent,” as Patent Owner demands. See id. For the reasons discussed above, we are persuaded that Petitioner set forth sufficient evidence in the Petition to show that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary structure”) includes a statement of a precondition (the claimed “trigger declaration”) relating to a specific AV program listed in the content index. Thus, we determine that the Petition establishes sufficiently that FIPA97 teaches or suggests “the agent registry data structure includes at least one trigger declaration for one active agent,” as recited in claim 8.” slip op. at 29

  Patent outcomesUS 7,069,560 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,069,560
• Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentable
  PTAB · Dec 22, 2022 · IPR2019-00814 · APJ Kevin C Trock · IPR · Remand

  Claims 8 and 86–89 of the ’115 patent and claims 10 and 11 of the ’560 patent are unpatentable as obvious over Kiss and FIPA97; claims 9, 10, and 63 of the ’115 patent and …

  RulingsRemand decision

  • RemandOther

    “the ’560 patent, we found in the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR that Petitioner did not present sufficient evidence to show how or why a person of ordinary skill in the art would have combined Kiss and FIPA97 to obtain the recited subject matter of these claims. 810 Final Dec. 145–149; 814 Final Dec. 135; 835 Final Dec. 108. On appeal, the Federal Circuit reversed our finding and remanded “for the Board to address any remaining obviousness disputes concerning these claims.” Microsoft, 2022 WL 989403, at *3–5. On remand, Patent Owner appears to disagree with the Federal Circuit’s decision and argues that Petitioner failed to show how a person of ordinary skill in the art would have combined Kiss and FIPA97. PO Remand Opening Br. 2–9; PO Remand Resp. Br. 2. In response, Petitioner argues Patent Owner’s argument is improper because the mandate rule “prevents parties from raising issues on remand that were within the scope of the judgment appealed from and resolved by the appellate court.” Pet. Remand Resp. Br. 3–4 (citing Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999)). Petitioner further argues that the Federal Circuit has expressly resolved the question of whether the Petition has sufficiently set forth “the ‘how’ and ‘why’ of the cited combination” in favor of Petitioner and, therefore, we should not address or revisit the issue on remand. Id. at 7. We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5. Pursuant to the Federal Circuit’s decision and mandate, we address below the remaining obviousness disputes concerning claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. In the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR, we did not reach the issue of whether Petitioner has shown sufficiently that the cited combination teaches or suggests all limitations of these claims. See 810 Final Dec. 144– 149; 814 Final Dec. 132–135; 835 Final Dec. 106–109. We do so now and address the parties’ disputes regarding the teachings of the cited prior art as they relate to the limitations recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent.” slip op. at 23

  • BurdenDecided for patent owner

    “We note, as an initial matter, that it is Petitioner’s burden to explain how the challenged claims should be construed and how, as so construed, they are unpatentable. See 37 C.F.R. § 42.104(b)(3)–(4). Despite having been afforded an opportunity on remand to address our claim construction set forth in the Final Written Decisions, Petitioner does not address in its how the cited prior art teaches or suggests the limitation under our construction. See Pet. Remand Opening Br. 3–5, 7. Thus, Petitioner does not meet its burden to show by a preponderance of the evidence that claims 9, 10, and 63 of the ’115 patent and claim 28 of the ’560 patent are unpatentable over the combination of Kiss and FIPA97. In addition, for the reasons discussed below, Petitioner’s cited evidence does not show sufficiently that the cited prior art teaches or suggests “process characteristics” recited in the claims under our construction of the term—i.e., “characteristics of a process for an agent.” As noted above, Petitioner argued during trial that FIPA97’s “interaction-protocols” parameter is “analogous to both the Machine Type and Language examples [of Process Characteristics] from the specification.” See Pet. Reply 78. On remand, Petitioner does not present this “similarity” argument. See generally Pet. Remand Opening Br., Pet. Remand Resp. Br. Although Petitioner’s argument on the alleged similarity of FIPA97’s “interaction-protocols” to the Specification’s examples of Process Characteristics may be relevant to the question of whether FIPA97 teaches or suggests the recited “process characteristics” under our construction, we are not persuaded that Petitioner has cited sufficient evidence to show FIPA97’s “interaction-protocols” parameter is analogous to the Specification’s Machine Type and Language examples.” slip op. at 32

  • Skill levelSkill level board ownDecided for petitioner

    “B. Level of Ordinary Skill in the Art In the Final Written Decisions, we determined that a person of ordinary skill in the art at the time of the claimed invention would have had “a Bachelor’s degree in Computer Science or equivalent field and at least two years of work experience in design and development of distributed systems, software specification languages, or a related area.” 810 Final Dec. 12; 811 Final Dec. 12; 814 Final Dec. 11; 835 Final Dec. 12; 836 Final Dec. 12. We see no reason to depart from this determination, which the parties did not challenge on appeal.” slip op. at 18

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

    “argued in the Petition that a “trigger” recited in claim 1 (see Ex. 1001, 29:10–24) is “a general mechanism for requesting some action be taken when one or more conditions is met.” Pet. 11 (citing Ex. 1001, 21:21–22:31; Ex. 1003 ¶¶ 80–81). Patent Owner did not dispute Petitioner’s proposed meaning of “trigger” recited in claim 1. See PO Resp. 24–38. In the Final Written Decision in the 810 IPR, we adopted this undisputed interpretation of “trigger” because the construction is consistent with the disclosure in the Specification. 810 Final Dec. 120 (citing Ex. 1001, 21:22–24 (“triggers [provide] a general mechanism for requesting some action be taken when a set of conditions is met”)). This claim construction was not appealed and, as noted above, the Federal Circuit did not address the construction of this claim term. See Microsoft, 2022 WL 989403. Considering the full record, we see no reason to depart from the claim construction of the term “trigger” the same claim construction for purposes of this Remand Decision. Petitioner and Dr. Lieberman proposed the same interpretation for the claim term “trigger” recited in claim 8. See Ex. 1003 ¶ 371. We agree with this construction because claim 8 incorporates all of the limitations of claim 1 from which it depends and the same terms appearing in different portions of a claim should be given the same meaning absent compelling evidence to the contrary. See Paragon Sols., LLC v. Timex Corp., 566 F.3d 1075, 1087 (Fed. Cir. 2009) (“We apply a presumption that the same terms appearing in different portions of the claims should be given the same meaning unless it is clear from the specification and prosecution history that the terms have different meanings at different portions of the claims.” (internal quotation marks omitted) (citations omitted)); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1334 (Fed. Cir. 2003) (“[W]e presume, unless otherwise compelled, that the same claim term in the same patent or related patents carries the same construed meaning.”). We also agree with Dr. Lieberman’s proposed interpretation of the claim term “trigger declaration” as “a statement in a program that specifies the characteristics of a trigger” (Ex. 1003 ¶ 371) because the construction is consistent with the disclosure in the Specification. See Ex. 1001, 17:5–9 (“Each registered agent may be optionally associated with one or more triggers, which preferably could be referenced through their associated Trigger Declaration fields 712 in the parent facilitator Agent Registry 702.”); see also Ex. 1003 ¶ 374 (citing Ex. 1001, 17:5–9, Fig. 7).” slip op. at 27

  Patent outcomesUS 6,851,115 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,851,115
• Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentable
  PTAB · Dec 22, 2022 · IPR2019-00811 · APJ Kevin C Trock · IPR · Remand

  On remand, claims 8 and 86–89 of the ’115 patent and claims 10 and 11 of the ’560 patent are unpatentable under § 103; claims 9, 10, and 63 of the ’115 patent and claim …

  RulingsRemand decision

  • RemandOther

    “We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5. Pursuant to the Federal Circuit’s decision and mandate, we address below the remaining obviousness disputes concerning claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. In the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR, we did not reach the issue of whether Petitioner has shown sufficiently that the cited combination teaches or suggests all limitations of these claims. See 810 Final Dec. 144– 149; 814 Final Dec. 132–135; 835 Final Dec. 106–109. We do so now and address the parties’ disputes regarding the teachings of the cited prior art as they relate to the limitations recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent.” slip op. at 23

  • Skill levelSkill level board ownDecided for petitioner

    “B. Level of Ordinary Skill in the Art In the Final Written Decisions, we determined that a person of ordinary skill in the art at the time of the claimed invention would have had “a Bachelor’s degree in Computer Science or equivalent field and at least two years of work experience in design and development of distributed systems, software specification languages, or a related area.” 810 Final Dec. 12; 811 Final Dec. 12; 814 Final Dec. 11; 835 Final Dec. 12; 836 Final Dec. 12. We see no reason to depart from this determination, which the parties did not challenge on appeal.” slip op. at 18

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

    “argued in the Petition that a “trigger” recited in claim 1 (see Ex. 1001, 29:10–24) is “a general mechanism for requesting some action be taken when one or more conditions is met.” Pet. 11 (citing Ex. 1001, 21:21–22:31; Ex. 1003 ¶¶ 80–81). Patent Owner did not dispute Petitioner’s proposed meaning of “trigger” recited in claim 1. See PO Resp. 24–38. In the Final Written Decision in the 810 IPR, we adopted this undisputed interpretation of “trigger” because the construction is consistent with the disclosure in the Specification. 810 Final Dec. 120 (citing Ex. 1001, 21:22–24 (“triggers [provide] a general mechanism for requesting some action be taken when a set of conditions is met”)). This claim construction was not appealed and, as noted above, the Federal Circuit did not address the construction of this claim term. See Microsoft, 2022 WL 989403. Considering the full record, we see no reason to depart from the claim construction of the term “trigger” the same claim construction for purposes of this Remand Decision. Petitioner and Dr. Lieberman proposed the same interpretation for the claim term “trigger” recited in claim 8. See Ex. 1003 ¶ 371. We agree with this construction because claim 8 incorporates all of the limitations of claim 1 from which it depends and the same terms appearing in different portions of a claim should be given the same meaning absent compelling evidence to the contrary. See Paragon Sols., LLC v. Timex Corp., 566 F.3d 1075, 1087 (Fed. Cir. 2009) (“We apply a presumption that the same terms appearing in different portions of the claims should be given the same meaning unless it is clear from the specification and prosecution history that the terms have different meanings at different portions of the claims.” (internal quotation marks omitted) (citations omitted)); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1334 (Fed. Cir. 2003) (“[W]e presume, unless otherwise compelled, that the same claim term in the same patent or related patents carries the same construed meaning.”). We also agree with Dr. Lieberman’s proposed interpretation of the claim term “trigger declaration” as “a statement in a program that specifies the characteristics of a trigger” (Ex. 1003 ¶ 371) because the construction is consistent with the disclosure in the Specification. See Ex. 1001, 17:5–9 (“Each registered agent may be optionally associated with one or more triggers, which preferably could be referenced through their associated Trigger Declaration fields 712 in the parent facilitator Agent Registry 702.”); see also Ex. 1003 ¶ 374 (citing Ex. 1001, 17:5–9, Fig. 7).” slip op. at 27

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

    “Patent Owner’s argument is unavailing because, as discussed above, Dr. Lieberman persuasively explained that in FIPA97’s FIPA-AVEB- Request-Notification contract-net “[t]he GA is responsible for the creation and management of a content index, and uses this index to respond to requests from the CA” (Ex. 1003 ¶ 373 (citing Ex. 1011, 11)) and that a person of ordinary skill in the art would have understood that, for the GA to monitor for changes over a given time period and inform the CA of any changes to the status of a specific AV program that conform to a precondition “preconditions2” within that period, “the agent registry must include declaration functionality” for preconditions relating to the status of AV programs (id. ¶ 374). We are persuaded that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary skill in the art that the GA’s context index (the claimed “agent registry data structure”) includes a statement of a precondition relating to a specific AV program listed in the content index. In its remand paper, Patent Owner argues that “nothing in Part 6 FIPA97 explicitly teaches that a precondition2 is stored within a General Agent as asserted by Petitioner.” PO Remand Resp. Br. 7 (underlined emphasis added). Patent Owner’s argument is unavailing because Petitioner’s asserted theory of unpatentability is one of obviousness, not anticipation. Thus, Petitioner need not show “FIPA97 explicitly teaches that a precondition2 is stored within a [Guide] Agent,” as Patent Owner demands. See id. For the reasons discussed above, we are persuaded that Petitioner set forth sufficient evidence in the Petition to show that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary structure”) includes a statement of a precondition (the claimed “trigger declaration”) relating to a specific AV program listed in the content index. Thus, we determine that the Petition establishes sufficiently that FIPA97 teaches or suggests “the agent registry data structure includes at least one trigger declaration for one active agent,” as recited in claim 8.” slip op. at 29

  Patent outcomesUS 6,851,115 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,851,115
• Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentable
  PTAB · Dec 22, 2022 · IPR2019-00810 · APJ Kevin C Trock · IPR · Remand

  On remand, claims 8 and 86–89 of the ’115 patent and claims 10 and 11 of the ’560 patent were held unpatentable under §103; claims 9, 10, and 63 of the ’115 patent and claim …

  RulingsRemand decision

  • RemandOther

    “We agree with Petitioner’s argument. We disagree with and reject Patent Owner’s argument in its remand papers directed to Petitioner’s reasons for the cited combination as being inconsistent with the Federal Circuit’s decision, which determined that Petitioner has shown sufficiently and FIPA97 to obtain the subject matter recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. See Microsoft, 2022 WL 989403, at *3–5. Pursuant to the Federal Circuit’s decision and mandate, we address below the remaining obviousness disputes concerning claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent. In the Final Written Decisions in the 810 IPR, 814 IPR, and 835 IPR, we did not reach the issue of whether Petitioner has shown sufficiently that the cited combination teaches or suggests all limitations of these claims. See 810 Final Dec. 144– 149; 814 Final Dec. 132–135; 835 Final Dec. 106–109. We do so now and address the parties’ disputes regarding the teachings of the cited prior art as they relate to the limitations recited in claims 8–10 and 63 of the ’115 patent and claim 28 of the ’560 patent.” slip op. at 23

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

    “argued in the Petition that a “trigger” recited in claim 1 (see Ex. 1001, 29:10–24) is “a general mechanism for requesting some action be taken when one or more conditions is met.” Pet. 11 (citing Ex. 1001, 21:21–22:31; Ex. 1003 ¶¶ 80–81). Patent Owner did not dispute Petitioner’s proposed meaning of “trigger” recited in claim 1. See PO Resp. 24–38. In the Final Written Decision in the 810 IPR, we adopted this undisputed interpretation of “trigger” because the construction is consistent with the disclosure in the Specification. 810 Final Dec. 120 (citing Ex. 1001, 21:22–24 (“triggers [provide] a general mechanism for requesting some action be taken when a set of conditions is met”)). This claim construction was not appealed and, as noted above, the Federal Circuit did not address the construction of this claim term. See Microsoft, 2022 WL 989403. Considering the full record, we see no reason to depart from the claim construction of the term “trigger” the same claim construction for purposes of this Remand Decision. Petitioner and Dr. Lieberman proposed the same interpretation for the claim term “trigger” recited in claim 8. See Ex. 1003 ¶ 371. We agree with this construction because claim 8 incorporates all of the limitations of claim 1 from which it depends and the same terms appearing in different portions of a claim should be given the same meaning absent compelling evidence to the contrary. See Paragon Sols., LLC v. Timex Corp., 566 F.3d 1075, 1087 (Fed. Cir. 2009) (“We apply a presumption that the same terms appearing in different portions of the claims should be given the same meaning unless it is clear from the specification and prosecution history that the terms have different meanings at different portions of the claims.” (internal quotation marks omitted) (citations omitted)); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1334 (Fed. Cir. 2003) (“[W]e presume, unless otherwise compelled, that the same claim term in the same patent or related patents carries the same construed meaning.”). We also agree with Dr. Lieberman’s proposed interpretation of the claim term “trigger declaration” as “a statement in a program that specifies the characteristics of a trigger” (Ex. 1003 ¶ 371) because the construction is consistent with the disclosure in the Specification. See Ex. 1001, 17:5–9 (“Each registered agent may be optionally associated with one or more triggers, which preferably could be referenced through their associated Trigger Declaration fields 712 in the parent facilitator Agent Registry 702.”); see also Ex. 1003 ¶ 374 (citing Ex. 1001, 17:5–9, Fig. 7).” slip op. at 27

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

    “Patent Owner’s argument is unavailing because, as discussed above, Dr. Lieberman persuasively explained that in FIPA97’s FIPA-AVEB- Request-Notification contract-net “[t]he GA is responsible for the creation and management of a content index, and uses this index to respond to requests from the CA” (Ex. 1003 ¶ 373 (citing Ex. 1011, 11)) and that a person of ordinary skill in the art would have understood that, for the GA to monitor for changes over a given time period and inform the CA of any changes to the status of a specific AV program that conform to a precondition “preconditions2” within that period, “the agent registry must include declaration functionality” for preconditions relating to the status of AV programs (id. ¶ 374). We are persuaded that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary skill in the art that the GA’s context index (the claimed “agent registry data structure”) includes a statement of a precondition relating to a specific AV program listed in the content index. In its remand paper, Patent Owner argues that “nothing in Part 6 FIPA97 explicitly teaches that a precondition2 is stored within a General Agent as asserted by Petitioner.” PO Remand Resp. Br. 7 (underlined emphasis added). Patent Owner’s argument is unavailing because Petitioner’s asserted theory of unpatentability is one of obviousness, not anticipation. Thus, Petitioner need not show “FIPA97 explicitly teaches that a precondition2 is stored within a [Guide] Agent,” as Patent Owner demands. See id. For the reasons discussed above, we are persuaded that Petitioner set forth sufficient evidence in the Petition to show that the cited disclosures of FIPA97 at least would have suggested to a person of ordinary structure”) includes a statement of a precondition (the claimed “trigger declaration”) relating to a specific AV program listed in the content index. Thus, we determine that the Petition establishes sufficiently that FIPA97 teaches or suggests “the agent registry data structure includes at least one trigger declaration for one active agent,” as recited in claim 8.” slip op. at 29

  • BurdenNot shown unpatentable

    “We note, as an initial matter, that it is Petitioner’s burden to explain how the challenged claims should be construed and how, as so construed, they are unpatentable. See 37 C.F.R. § 42.104(b)(3)–(4). Despite having been afforded an opportunity on remand to address our claim construction set forth in the Final Written Decisions, Petitioner does not address in its how the cited prior art teaches or suggests the limitation under our construction. See Pet. Remand Opening Br. 3–5, 7. Thus, Petitioner does not meet its burden to show by a preponderance of the evidence that claims 9, 10, and 63 of the ’115 patent and claim 28 of the ’560 patent are unpatentable over the combination of Kiss and FIPA97. In addition, for the reasons discussed below, Petitioner’s cited evidence does not show sufficiently that the cited prior art teaches or suggests “process characteristics” recited in the claims under our construction of the term—i.e., “characteristics of a process for an agent.” As noted above, Petitioner argued during trial that FIPA97’s “interaction-protocols” parameter is “analogous to both the Machine Type and Language examples [of Process Characteristics] from the specification.” See Pet. Reply 78. On remand, Petitioner does not present this “similarity” argument. See generally Pet. Remand Opening Br., Pet. Remand Resp. Br. Although Petitioner’s argument on the alleged similarity of FIPA97’s “interaction-protocols” to the Specification’s examples of Process Characteristics may be relevant to the question of whether FIPA97 teaches or suggests the recited “process characteristics” under our construction, we are not persuaded that Petitioner has cited sufficient evidence to show FIPA97’s “interaction-protocols” parameter is analogous to the Specification’s Machine Type and Language examples. First, Petitioner did not explain during trial, nor does it explain on remand, why FIPA97’s “interaction-protocols” parameter is analogous to the Machine Type and Language examples in the Specification. See Pet. Reply 78; see generally Pet. Remand Opening Br., Pet. Remand Resp. Br. In addition, Petitioner did not cite, nor does it cite on remand, any declaration generally Pet. Remand Opening Br., Pet. Remand Resp. Br. Petitioner’s argument, therefore, is conclusory and unpersuasive as unsupported attorney argument. See Icon Health & Fitness, Inc. v. Strava Inc., 849 F.3d 1034, 1046 (Fed. Cir. 2017) (“Attorney argument is not evidence or explanation in support of a conclusion.”); Invitrogen Corp. v. Clontech Lab., Inc., 429 F.3d 1052, 1068 (Fed. Cir. 2005) (“Unsubstantiated attorney argument regarding the meaning of technical evidence is no substitute for competent, substantiated expert testimony.”).” slip op. at 32

  Patent outcomesUS 6,851,115 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,851,115
• Veeam Software Corp. v. Hybir Inc.Some claims unpatentable
  PTAB · Dec 2, 2021 · IPR2020-01038 · APJ John R Kenny · IPR · Final written decision

  Claims 30, 32, 33, 35, and 37–40 are unpatentable as obvious; claims 31, 34, and 36 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for patent owner

    “E. Level of Skill in the Art To determine the level of an ordinarily skilled artisan, various factors” slip op. at 10

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

    “claim terms for construction at that stage of the proceeding, and we did not construe any claim terms expressly as none of the terms were in dispute. Inst. Dec. 22. In the briefing following institution, Patent Owner proposed a construction for the term “inventory,” see, e.g., PO Resp. 21–28, and it became clear that the parties dispute the meaning of the term. Accordingly, we address the parties’ proposed constructions for “inventory” and the arguments they present for those constructions.” slip op. at 13

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

    “As set forth above, we resolved those disputed issues in favor of Petitioner. For the portions of the preamble and limitations of claim 35 that are not recited in claim 30, we have reviewed Petitioner’s arguments and evidence for claim 35 and are persuaded that Field teaches or suggests the preamble and claim limitations. Pet. 25–28 (and the exhibits cited therein). Thus, we find that Field teaches or suggests all limitations of claim 35. Accordingly, we determine Petitioner has proven that claim 35 would have been obvious over Field.” slip op. at 55

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

    “metadata into its signature generating algorithm to create a more robust signature. Ex. 1005 ¶ 46. An ordinarily skilled artisan would have been motivated to use such an augmented signature generating algorithm in Field’s environment. Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40. Thus, an ordinarily skilled artisan would have modified Field’s cryptographic signature generating algorithm so it would compute a file’s signature using a file’s metadata. Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40. Accordingly, Field and Anderson disclose that “the cryptographic signature is also computed with the metadata.” Ex. 1002 ¶¶ 138–139; Ex. 1004 ¶ 40.” slip op. at 76

  Patent outcomesUS 8,051,043 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 8,051,043

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.