- Zoho Corporation / Zoho Corporation PVT., Ltd. v. Meetrix IP, LLCSome claims unpatentablePTAB · Jul 16, 2024 · IPR2023-00379 · APJ Kara L Szpondowski · IPR · Final written decision
Claims 9–16 are unpatentable as obvious over Drell, Knappe, and Elliott; claims 17–20 were not shown unpatentable because the petition did not establish the separately recited mixers in claims 17 and 18.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“We agree with Petitioner. Although Patent Owner proposes an alternative level of ordinary skill in the art, Patent Owner does not explain how it impacts Petitioner’s contentions or Patent Owner’s arguments in opposition. Indeed, at the hearing, Patent Owner’s counsel stated “I can’t point to a material difference that would change the outcome of this.” Tr. 49:10–15. Therefore, it appears that neither party contends that the differences in their proposals affects the outcome of this proceeding. Nothing in the full record persuades us that our preliminary finding in the Institution Decision, adopting Petitioner’s proposal, was incorrect. See Paper 6, 9. Therefore, we maintain our adoption of Petitioner’s proposed level of ordinary skill in the art, as consistent with the ’525 patent’s specification and the level of ordinary skill in the art reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our findings would not change even under Patent Owner’s proposed level of skill in the art.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“We agree with Petitioner that no claim construction is necessary for purposes of this Decision. That is, Patent Owner does not argue, and we do 5 Petitioner was not a party to this district court litigation. See Tr. 8:21–23 (Petitioner’s counsel stating “[w]e were not involved, Zoho was not involved in that claim construction process that resulted in the construction from the Western District of Texas.”). not discern, that any claim terms are in controversy on the current record.6 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 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundMixed
“We are persuaded that the combination of Drell and Knappe teaches limitation [9.6]. Patent Owner’s arguments improperly address Drell and Knappe individually, rather than the combination of Drell and Knappe on which Petitioner relies. See Soft Gel Techs., Inc. v. Jarrow Formulas, Inc., 864 F.3d 1334, 1341 (Fed. Cir. 2017) (attacking a reference individually does not show non-obviousness where petitioner’s ground is premised on the combination of references); Reply 7. As described above, Petitioner provides extensive reasoning, supported by testimony from Dr. Houh, explaining how the combination of Drell and Knappe teaches limitation [9.6], and provides reasoning for why a person of ordinary skill in the art would combine the references. Patent Owner’s arguments largely do not address Petitioner’s contentions and fail to address Petitioner’s arguments in support of the combination. In addition, Petitioner supports its arguments with citations to the references and credible declarant testimony from the vantage of a person of ordinary skill in the art, while Patent Owner’s arguments as to the interpretation of the references and motivations (or lack thereof) of a person of ordinary skill in the art are insufficiently supported by testimony from the viewpoint of a person of ordinary skill in the art or citation to the references.9 See PO Resp. 18–19. We find Petitioner’s interpretation of the references and motivation to combine more persuasive than Patent Owner’s insufficiently supported attorney argument on these issues.” slip op. at 31
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“combination of references); Reply 7. As described above, Petitioner provides extensive reasoning, supported by testimony from Dr. Houh, explaining how the combination of Drell and Knappe teaches limitation [9.6], and provides reasoning for why a person of ordinary skill in the art would combine the references. Patent Owner’s arguments largely do not address Petitioner’s contentions and fail to address Petitioner’s arguments in support of the combination. In addition, Petitioner supports its arguments with citations to the references and credible declarant testimony from the vantage of a person of ordinary skill in the art, while Patent Owner’s arguments as to the interpretation of the references and motivations (or lack thereof) of a person of ordinary skill in the art are insufficiently supported by testimony from the viewpoint of a person of ordinary skill in the art or citation to the references.9 See PO Resp. 18–19. We find Petitioner’s interpretation of the references and motivation to combine more persuasive than Patent Owner’s insufficiently supported attorney argument on these issues.” slip op. at 32
Patent outcomesUS 9,094,525 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,094,525 - Apple Inc. v. Aire Technology LimitedSome claims unpatentablePTAB · Dec 15, 2023 · IPR2022-01136 · APJ Brian J Mcnamara · IPR · Final written decision
Claim 15 is unpatentable as obvious over Tobergte and Cole; claims 1–3 and 8–11 were not shown unpatentable because the references did not disclose claim 1’s search-signal limitation.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“Even a small amount of power that may be consumed by incorporating Cole into Tobergte likely exceeds the power consumed by Tobergte’s configuration in which the computer and oscillator are disconnected from power. Nevertheless, neither party provides a specific power consumption analysis. On this issue, we weigh Dr. Phinney’s testimony over Patent Owner’s attorney arguments and determine that Patent Owner has not sufficiently supported its contention that Cole teaches away from Tobergte on this basis. We determine that a person of ordinary skill would have had reason to combine the teachings of Tobergte with those of Cole to provide a system that detects the presence of data carriers automatically without the need for the user to activate the data carrier with a switch.” slip op. at 16
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner
“Tobergte’s computer 38 and oscillator 34 are disconnected from energy source 40. Pet. Reply 14–15. Petitioner acknowledges that Tobergte improves upon prior art systems, in which the fixed station emits the high frequency magnetic field continuously, by emitting the high frequency magnetic field “only upon awakening from a low power rest state.” Petitioner points to the testimony of Dr. Phinney concluding that Cole’s presence detector is at a power level too low to fully power the data carrier, but sufficient to allow the data carrier to change the impedance of the field. Id. at 21 (citing Ex. 1003, Phinney Decl. ¶ 53, commenting on Ex. 1006, 6:1–8 cited by Patent Owner); id. at 2 (citing Ex. 1005, 1:21–35). Even a small amount of power that may be consumed by incorporating Cole into Tobergte likely exceeds the power consumed by Tobergte’s configuration in which the computer and oscillator are disconnected from power. Nevertheless, neither party provides a specific power consumption analysis. On this issue, we weigh Dr. Phinney’s testimony over Patent Owner’s attorney arguments and determine that Patent Owner has not sufficiently supported its contention that Cole teaches away from Tobergte on this basis. We determine that a person of ordinary skill would have had reason to combine the teachings of Tobergte with those of Cole to provide a system that detects the presence of data carriers automatically without the need for the user to activate the data carrier with a switch.” slip op. at 16
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“sufficient for the data carrier to switch to passive mode. Id. at 6:1−5. When the data carrier is switched into passive mode, the data carrier’s supply device generates the operating voltage for the electric circuit from the received high frequency energy. Id. at 6:5–9. Claim 1 of Tobergte does not suggest that the fixed station performs any search function. Instead, Tobergte’s fixed station receives both energy and data from the data carrier for the brief period that the data carrier is in the active mode. There is no indication that Tobergte’s fixed station is emitting signals to search for the data carrier. Instead, Tobergte claims a system in which the data carrier that “wakes up” the fixed station is then powered by the energy of the high frequency field transmitted by the fixed station. None of Tobergte’s other claims explicitly recites a search limitation. In other words, Tobergte describes and claims changing a conventional data carrier that transmits data only when interrogated (id. at 3:48−52) into a data carrier that begins transmitting energy and data first, when activated by a user (id. at 3:55−58, 3:65−67).” slip op. at 25
- Expert testimonyPetitioner expert creditedOther
“Even a small amount of power that may be consumed by incorporating Cole into Tobergte likely exceeds the power consumed by Tobergte’s configuration in which the computer and oscillator are disconnected from power. Nevertheless, neither party provides a specific power consumption analysis. On this issue, we weigh Dr. Phinney’s testimony over Patent Owner’s attorney arguments and determine that Patent Owner has not sufficiently supported its contention that Cole teaches away from Tobergte on this basis. We determine that a person of ordinary skill would have had reason to combine the teachings of Tobergte with those of Cole to provide a system that detects the presence of data carriers automatically without the need for the user to activate the data carrier with a switch.” slip op. at 16
Patent outcomesUS 8,174,360 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,174,360 - Keysight Technologies, Inc. v. Centripetal Networks, Inc.Some claims unpatentablePTAB · Dec 15, 2023 · IPR2022-01097 · APJ Aaron W Moore · IPR · Final written decision
Claims 1–3, 5–13, and 15–20 are unpatentable as obvious; claims 4 and 14 were not shown unpatentable because Sourcefire did not disclose the claimed responsive updating of an existing packet flow log entry.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not address this issue, and neither side argues that it might affect the patentability analysis or otherwise change the outcome. Thus, as 2 Sourcefire 3D System User Guide, Ver. 4.10, Mar. 16, 2011 (Ex. 1004). 3 U.S. Patent App. Pub. No. 2015/0207809 A1 (Ex. 1029). we did at institution, we apply Petitioner’s description of an ordinarily skilled artisan, as we find it consistent with the ’917 patent and the asserted prior art. B.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“1. Threat Identifier and Threat Indicator Patent Owner identifies two terms that were construed in the ITC investigation involving the ’917 patent based on constructions agreed upon by the parties. PO Resp. 9. First, the parties in the ITC investigation agreed that “threat identifier” means “information that identifies one or more network threats.” Id. at 11 (citing Ex. 2004, 3). Second, the parties further agreed that “threat indicator” means “information that indicates a resource associated with a network threat,” “[f]or example, network addresses, ports, FQDNs, URLs, URIs, the type of threat, geographic information, anonymous proxies, actors, or the like.” Id. at 11–12 (citing Ex. 2004, 3). Patent Owner asserts that these constructions should be used in this proceeding. Id. at 12. Petitioner does not dispute these constructions, and we adopt them.4” slip op. at 12
- ExcludeMotion to exclude, grantedGranted
“Before we get to claim construction, we exclude Ex. 2018 as untimely because Patent Owner had the testimony before it filed the Response and was plainly aware of it, as it was alluded to in the Response. See PO Resp. 10; Mot. to Exclude Opp. 2 (admitting that the trial finished before the Response was filed and that Patent Owner filed other testimony excerpts with the Response). However, the exclusion is of little consequence because we find that the testimony would be devoid of probative value. Dr. Rubin is not a fact witness and has not been offered as an expert in this case. Patent Owner cites the testimony in an effort to show that Petitioner is taking inconsistent positions, but we fail to see how Petitioner’s conduct bears on the meaning of “flow” in the ’917 patent.” slip op. at 14
- Expert testimonyDecided for petitioner
“Before we get to claim construction, we exclude Ex. 2018 as untimely because Patent Owner had the testimony before it filed the Response and was plainly aware of it, as it was alluded to in the Response. See PO Resp. 10; Mot. to Exclude Opp. 2 (admitting that the trial finished before the Response was filed and that Patent Owner filed other testimony excerpts with the Response). However, the exclusion is of little consequence because we find that the testimony would be devoid of probative value. Dr. Rubin is not a fact witness and has not been offered as an expert in this case. Patent Owner cites the testimony in an effort to show that Petitioner is taking inconsistent positions, but we fail to see how Petitioner’s conduct bears on the meaning of “flow” in the ’917 patent.” slip op. at 14
Patent outcomesUS 10,193,917 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 10,193,917 - Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 7,069,560 - Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 7,069,560 - Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,851,115 - Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,851,115 - Microsoft Corporation v. Ipa Technologies Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,851,115 - Apple Inc. v. Omni Medsci, Inc.Some claims unpatentablePTAB · Aug 3, 2022 · IPR2021-00453 · APJ Brian J Mcnamara · IPR · Final written decision
Claims 1, 2, 7, and 15–23 are unpatentable under the asserted obviousness grounds; claims 3–6 and 8–14 were not shown unpatentable.
RulingsFinal written decision- BurdenMixed
“evidence, we conclude that Petitioner has demonstrated by a preponderance of the evidence that challenged claims 1, 2, 7, and 15–23 are unpatentable and that Petitioner has not demonstrated challenged claims 3–6 and 8–14 to be unpatentable.” slip op. at 2
- Skill levelOther
“7 The level of ordinary skill in this case is discussed in the Decision to Institute and is uncontested. Dec. to Inst. 7–8.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededTerm construed patent owner constructionDecided for patent owner
“Specification concerning the terms “identify” and “detect” involve actions not recited in the claims does not change the fact that these different claim terms are presumed to have different meanings. The dictionary definitions of “detect” and “identify” are different. The use of the term “identify” in claims 3 and 8 and the use of a different term, i.e., “detect,” in claim 16 indicates that the claims 3 and 8 mean something different from claim 16. Petitioner has not rebutted the presumption that different claim terms have matter. See SimpleAir, Inc. v. Sony Ericsson Mobile Commc’ns AB, 820 F.3d 419, 431 (Fed. Cir. 2016). Therefore, we decline to adopt Petitioner’s proposal to construe the terms “identify an object” and “detect an object” to have the same meaning. Instead, we construe these terms consistent with the dictionary definitions of “identify” and “detect,” i.e., we construe “to identify an object” to mean “to recognize or establish an object as being a particular thing,” and we construe “to detect an object” to mean “to discover or notice the existence or presence of something.” We address the specific implications of these constructions in our discussion of claims 3, 8, and 16.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“Specification concerning the terms “identify” and “detect” involve actions not recited in the claims does not change the fact that these different claim terms are presumed to have different meanings. The dictionary definitions of “detect” and “identify” are different. The use of the term “identify” in claims 3 and 8 and the use of a different term, i.e., “detect,” in claim 16 indicates that the claims 3 and 8 mean something different from claim 16. Petitioner has not rebutted the presumption that different claim terms have matter. See SimpleAir, Inc. v. Sony Ericsson Mobile Commc’ns AB, 820 F.3d 419, 431 (Fed. Cir. 2016). Therefore, we decline to adopt Petitioner’s proposal to construe the terms “identify an object” and “detect an object” to have the same meaning. Instead, we construe these terms consistent with the dictionary definitions of “identify” and “detect,” i.e., we construe “to identify an object” to mean “to recognize or establish an object as being a particular thing,” and we construe “to detect an object” to mean “to discover or notice the existence or presence of something.” We address the specific implications of these constructions in our discussion of claims 3, 8, and 16.” slip op. at 9
Patent outcomesUS 10,517,484 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,517,484 - Samsung Electronics Co., Ltd. v. Acorn Semi, LLCSome claims unpatentablePTAB · Feb 9, 2022 · IPR2020-01207 · APJ John R Kenny · IPR · Final written decision
Claims 1–6, 8–10, 15, and 16 are unpatentable as anticipated by Grupp ’483; claims 11, 12, and 14 were not shown unpatentable because Grupp ’483 is not prior art to them.
RulingsFinal written decision- BurdenNot shown unpatentable
“We agree with Patent Owner. “[A p]etitioner may not submit new evidence or argument in reply that it could have presented earlier, e.g., to make out a prima facie case of unpatentability.” Consolidated Trial Practice Guide5 73; see also 37 C.F.R. § 42.23(b). Here, Petitioner’s breadth challenge to the written description support for the genus of “the metal oxide of the interface layer comprises an oxide of 5 Consolidated Office Trial Practice Guide (Nov. 2019), available at https://www.uspto.gov/about-us/news-updates/consolidated-trial-practice-guide-november-2019. titanium” recited in claims 6, 8, 10, 11, and 14–16, was part of Petitioner’s prima facie case, which could have, and should have, been presented with the Petition. Thus, Petitioner could not properly wait until its Reply to specifically challenge the description support for the breadth of that class in the pre-2011 priority applications. See Henny Penny Corp. v. Frymaster LLC, 938 F.3d 1324, 1330–31 (Fed. Cir. 2019); Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1369–70 (Fed. Cir. 2016); Ariosa Diagnostics v. Verinata Heath, Inc., 805 F.3d 1359, 1368 (Fed. Cir. 2015). Accordingly, we will not consider the breadth challenge to a metal oxide comprising an oxide of titanium that Petitioner presented for the first time in its Reply. As for the breadth challenge presented in the Petition—that the pre- 2011 priority applications do not describe the breadth of the class of metal oxides, that challenge is inapplicable here because claims 11, 12, and 14 narrow the recited class to comprising an oxide of titanium, which is a far narrower class. Dr. Schubert provides examples of numerous metal oxides that do not comprise oxides of titanium. Ex. 1022, Schubert Decl. ¶ 94 (hafnium oxide and zirconium oxide); Ex. 1053, Schubert Reply Decl. ¶¶ 18, 19 (see the compounds identified in that paragraph beyond titanium dioxide), 20. Petitioner does not dispute that the pre-2011 priority applications disclose a species within the scope of the recited genus. Pet. 18–22. To the contrary, Petitioner relies on one of the pre-2011 priority applications (Grupp ’483) as disclosing a species (with TiO2) as proof that claims 11, 12, and 14 are anticipated. See id. at 40–44. Thus, we determine that Petitioner has not proven that the pre-2011 priority applications fail to describe the genus of the metal oxide of the interface layer comprises an oxide of titanium. Therefore, Petitioner has not proven that Patent Owner is not entitled to the benefit of the pre-2011 priority applications for claims 11, 12, and 14 due to a lack of written description support. Accordingly, Petitioner has not proven that Grupp ’483 is prior art for those claims.” slip op. at 27
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date, deniedPriority date awardedMixed
“2. Analysis We agree with Petitioner that the pre-2011 priority applications do not describe the recited genus. To support a claim to a genus, a specification must disclose “either a representative number of species falling within the scope of the genus or structural features common to the members of the genus so that one of skill in the art can ‘visualize or recognize’ the members of the genus.” Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1350 (Fed. Cir. 2010) (en banc). Here, the recited genus is an interface layer comprising a metal oxide. Ex. 1001, 18:45–52. It is undisputed that the only species the pre- 2011 priority applications disclose is TiO2, as set forth in the following passage: Two other properties of the dielectric deserve mention. First is the property of the height of the barrier compared to the semiconductor conduction band (for electrons). In making the barrier thinner than a silicide barrier, the tradeoff may be a higher tunnel barrier (e.g., 2 eV for nitride, compared with about half the gap of 0.6 eV for silicide). Spacer layers may be used with lower barriers (e.g., TiO2 has a barrier of less than 1 eV). Nevertheless, even with the higher barrier to electrons, the present inventors have determined that the resistance can still be one hundred times lower than a contact to silicon with a silicide barrier. Id. at 18:1–11 (emphasis added). The pre-2011 priority applications incorporate by reference U.S.” slip op. at 17
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“As set forth below, we find that Petitioner has proven that Grupp ’483 anticipates claims 1–6, 8–10, 15, and 16. a. Claim 1 Petitioner argues that Grupp ’483 discloses an electrical junction, citing Grupp 483’s disclosure that “the present invention provides an electrical junction.” Pet. 27 (citing Ex. 1021, Grupp ’483, 3:44–47). Petitioner further argues that Grupp ’483 discloses a region in a semiconductor substrate by describing a source or drain of a transistor. Id. at 28 (citing Ex. 1022, Schubert Decl. ¶ 110). According to Petitioner, Grupp ’483 discloses a metal electrical contact to said region by describing “an electrical device in which an interface layer is disposed between and in contact with a metal and a semiconductor.” Id. (quoting Ex. 1021, Grupp ’483, 4:21–23) (emphasis omitted). Petitioner asserts that Grupp ’483 discloses “said region being electrically connected to said metal electrical contact through said interface layer” by describing “the present invention provides an electrical device in which an interface layer is disposed between and in contact with a metal and a semiconductor and is configured to depin the Fermi level of the semiconductor while still permitting current flow between the metal and the semiconductor . . . .” Id. at 29 (quoting Ex. 1021, Grupp ’483, 4:21–26) (emphasis omitted). Petitioner further argues that Grupp ’483 discloses “said interface layer comprising a metal oxide and a semiconductor oxide” by describing an interface layer that includes (1) a passivation layer, which can be a semiconductor oxide; and (2) a separation layer, which can be titanium dioxide, a metal oxide. Pet. 29 (citing Ex. 1022, Schubert Decl. ¶ 114). Petitioner further asserts that Grupp ’483 discloses “being in contact with said region in the semiconductor substrate and said metal electrical contact” by describing “an interface layer is disposed between and in contact with a metal and a semiconductor.” Id. (quoting Ex. 1021, Grupp ’483, 4:21–23) (emphasis omitted). After reviewing Petitioner’s arguments and evidence, we find that Petitioner has proven that Grupp ’483 anticipates claim 1.” slip op. at 40
- ExcludeOther
“We dismiss Patent Owner’s Motion to Exclude as moot in light of our determination regarding Petitioner’s written description challenge to Patent Owner’s benefit of its pre-2011 priority applications for claims 11, 12, and 14. In particular, Petitioner relies on the testimony at issue to support its belated challenge to the breadth of written description support in the pre- 2011 priority applications for the class of comprising an oxide of titanium that is recited by those claims. Reply Br. 7–12. Because we decided not to consider that belated challenge (see Section III.A.1.b above), the Motion to Exclude is moot.” slip op. at 47
Patent outcomesUS 10,090,395 mixed§ 102 anticipationcites PhillipsPatents in suitUS 10,090,395
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.