• Visa Inc. v. Cortex MCP, Inc.Some claims unpatentable
  PTAB · Jul 29, 2025 · IPR2024-00489 · APJ Russell E Cass · IPR · Final written decision

  Claims 1, 3–9, 11–18, and 20 are unpatentable over the stated obviousness grounds; claims 2, 10, 19, and 21 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “skill in the art at the time of the alleged invention “would typically have a bachelor’s degree in computer science, computer engineering, or a related field, with at least two years of work involving electronic payment systems, network authentication systems, or related areas.” Pet. 9 (citing Ex. 1005 ¶¶ 76–81). Petitioner further states that a person of ordinary skill “could have less education but significant professional experience in one or more of those fields.” Id. In our Institution Decision, we adopted Petitioner’s assessment of the level of ordinary skill in the art. Patent Owner states that it agrees with the level of ordinary skill set forth in our Institution Decision. PO Resp. 9. Based on the full trial record, we continue to adopt Petitioner’s assessment of the level of skill in the art, which is consistent with the ’859 patent and the asserted prior art of record.” slip op. at 8

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

    “In our Institution Decision, we preliminarily determined that the term “OVER file” encompasses a virtual representation of one or more credentials, to be used for verification of those credentials. Inst. Dec. 11. We also explained that we did not need to determine for purposes of institution whether the term “OVER file” necessarily includes “tokens” as a general matter, or further elaborate on what additional characteristics might be required to qualify as an “OVER file.” Id. We also determined that Petitioner had made a sufficient showing for purposes of institution that Oborne’s tokens qualify as “OVER files.” Id. at 11, 24–27.” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed board ownDecided for petitioner

    “After considering the full trial record, we adhere to the construction in our Institution Decision interpreting the claim language at issue “to require that an issuing agency ha[s] verified a virtual representation in an OVER file as being an official representation of the credential.” Inst. Dec. 13. In light of Patent Owner’s statements in its Sur-reply, we further clarify that this construction encompasses (1) considering the OVER file as the credential and verifying the OVER file, or (2) verifying a virtual representation of the credential contained within the OVER file.” slip op. at 12

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

    “3. Other Terms The parties do not propose constructions for any other claim terms, and we determine that it is not necessary to provide an express interpretation of any other claim terms for purposes of this proceeding. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017); Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999).” slip op. at 13

  Patent outcomesUS 10,749,859 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,749,859
• Tesla, Inc. v. Iqar Inc.Some claims unpatentable
  PTAB · Jul 21, 2025 · IPR2024-00543 · APJ Sean P O’Hanlon · IPR · Final written decision

  Claims 1–7, 9–17, 19, and 20 are unpatentable as obvious; claims 8 and 18 were not shown unpatentable because Newstrom’s database was not shown to be remote.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “Patent Owner does not contest Dr. Morellas’s proposed definition or proffer a definition of its own. See generally PO Resp.; see also Ex. 2007 ¶ 43 (setting forth a substantially similar definition as Dr. Morellas). We find Dr. Morellas’s unopposed definition to be consistent with the problems and solutions disclosed in the patent and prior art of record, and adopt it as our own for purposes of this Decision. See, e.g., In re GPAC, 57 F.3d at 1579 (approving the determination of the level of ordinary skill in the art by appeal to the references of record).” slip op. at 8

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

    “We disagree with Patent Owner’s assertion that claim 1 requires that a route from the vehicle’s current position to a final destination must be known. See PO Resp. 7. Initially, claim 1 does not recite “destination.” Instead, claim 1 recites only “determining a segment of a vehicle route.” Ex. 1001, 27:44 (emphasis added). Nor does the ’399 patent specification require the interpretation proffered by Patent Owner. Notably, the ’399 patent discloses that the power management device may rely on historical route information to optimize the energy used to travel each segment of a route. Ex. 1001, 17:39–43, 17:64–67. Such reliance on historical data beneficially reduces the amount of required computing power. Id. at 18:5–9. Under this approach, “the location of the vehicle is periodically determined” and “used to determine[] a historical segment corresponding to the current location.” Id. at 18:30–33 (emphasis added). If the vehicle has moved into a new route segment, the historical data is queried to determine the most efficient speed to travel for the current segment. Id. at 18:39–56. Thus, the ’399 patent explicitly discloses calculating and applying power to a vehicle based on the route segment in which the vehicle is currently traveling. See id. at 18:64–67 (“The flowchart shown in FIG. 5 illustrates a continuous process, in which the power management device can determine a probable optimal speed as the current segment changes (e.g., as the vehicle moves).”), Fig. 5. Furthermore, the ’399 patent explains that “[t]he route used by the power management device typically includes a starting position . . . , an ending position, . . . , and any intermediate positions between the initial and the final positions.” Id. at 14:6–10 (emphasis added). Notably, the ’399 patent sometimes refers to the “entire route,” indicating that use of “route” in the claims does not necessarily mean the entire route. Indeed, the ’399 patent explains that, “[i]n some variations, the entire route (or the entire predicted route) may be divided up into N segments” and “[i]n some variations, probable optimal speeds may be identified for the entire route.” Ex. 1001, 14:38–39, 19:1–2 (emphases added). This strongly suggests that, in some other variations, the entire route is not divided into segments and optimal speeds are not identified for the entire route, further indicating that the recited “route” is not the entire path the vehicle will take. Therefore, we find that the ’399 patent contemplates routes that, although not typical, do not include an ending position. Moreover, to the extent a destination is required, the ’399 patent discloses that the destination can be derived based on the vehicle’s location or driving history, and there can be multiple “likely destinations” and the system can “continuously infer the vehicle’s destination” and the probable destination “may constantly change to revise the destination” while the vehicle is traveling along the route. Ex. 1001, 12:16–59. Contrary to Patent Owner’s arguments, neither the claim language nor the specification of the ’399 patent requires the route be predetermined or extend from the vehicle’s current position to a final destination.” slip op. at 16

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

    “have been obvious in view of Hongo, Obradovich, and Niki. Pet. 4–62. In support of its showing, Petitioner relies upon the Morellas Declaration. Id. (citing Ex. 1003). We have reviewed the parties’ briefs and the evidence of record and determine that, for the reasons explained below, Petitioner has shown, by a preponderance of the evidence, that claims 1, 2, 5, 6, 9–12, 15, 16, 19, and 20 would have been obvious in view of Hongo, Obradovich, and Niki and that Petitioner has set forth reasoning with rational underpinning why it would have been obvious to combine the teachings of these references.” slip op. at 10

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

    “limiting, Hongo and Niki support Petitioner’s contentions. We determine that Petitioner sets forth reasoning with rational underpinning as to why a person having ordinary skill in the art would have combined the teachings of Hongo and Niki. See, e.g., Pet. 21–23 (arguing that the modification “would have involved choosing from a finite number of identified, predictable solutions, with a reasonable expectation of success” and “Niki’s teachings and/or suggestions improve vehicle control in the Hongo vehicle”).” slip op. at 14

  Patent outcomesUS 10,882,399 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,882,399
• Apple Inc. v. Masimo CorporationSome claims unpatentable
  PTAB · Jun 25, 2025 · IPR2024-00290 · APJ Richard H Marschall · IPR · Final written decision

  Claims 1–3, 6, 11–17, 19, 21, 22, 27, 28, 32, 34, 36, 37, and 42–44 are unpatentable as obvious; claims 4, 18, and 20 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In our Institution Decision, we deemed the differences in the parties’ proposals not material due to their substantial overlap, adopted Patent Owner’s proposal for purposes of that Decision, noted that the outcome of the Decision would not change if we adopted Petitioner’s proposal, and instructed the parties to “explain the differences and their relevance to the patentability issues in this case, and state whether any issue in the case turns on those differences” if either party continued to propose differing proposals during trial. Inst. Dec. 10–11. After institution, neither party has explained the materiality of the differences in their proposals or argued that any issues in this case turn on those differences. Based on our review of the parties’ proposals, we find Patent Owner’s proposal consistent with the level of skill exemplified by the prior art of record and the disclosure of the ’223 patent. Accordingly, we apply Patent Owner’s proposal in our analysis in this Decision. See Okajima, 261 F.3d at 1355 (“[T]he prior art itself” may reflect an appropriate level of the ordinary level of skill in the art. (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985))). The outcome of this Decision would not change if we applied Petitioner’s proposed definition.” slip op. at 9

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionDecided for petitioner
  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “preponderance of the evidence that the combination of Naghavi, Hochstedler, and Burnes discloses all of the limitations in claim 1. b. Motivation to Combine After summarizing its proposed combination, Petitioner provides a number of reasons for combining the references. Pet. 9–17. Petitioner breaks its motivation to combine arguments into three separate categories that we address below. See id. at 13–17. Patent Owner raises a number of arguments in support of its contention that “a POSITA would not have been motivated to combine the references to replace a measured value of one parameter with the measured value of another parameter,” which we address in the context of Petitioner’s arguments below. See PO Resp. 44–57. Many of Patent Owner’s arguments rely on Patent Owner’s proposed claim constructions for “replaced” and “measured value,” which we do not adopt for the reasons discussed above. For example, the first sentence in Patent Owner’s argument contends that “Naghavi, Hochstedler and Burnes do not disclose using the same screen area to display two currently measured parameters,” but we do not read the claims as requiring the display of “two currently measured parameters” consistent with Patent Owner’s construction for “measured values.” See id. at 44 (citing Ex. 2042 ¶ 125). Such arguments lack weight given that we have rejected their premise, and although Patent Owner’s arguments are suffused with references to its claim constructions, we attempt to identify where Patent Owner does not rely on those constructions in our analysis below.” slip op. at 47

  Patent outcomesUS 8,190,223 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,190,223
• Charter Communications, Inc. / Altice USA, Inc. v. Touchstream Technologies, Inc.Some claims unpatentable
  PTAB · Jun 12, 2025 · IPR2024-01231 · APJ Georgianna W Braden · IPR · Final written decision

  Claims 22–26 are unpatentable under §103; claims 1–21 were not shown unpatentable because the cited combinations do not teach or justify the claimed server-side command conversion.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner contends that a person of ordinary skill in the art of the ’251 patent would have had: (1) the equivalent of a four-year, B.S. degree from an accredited institution in computer science, computer engineering or an equivalent field; (2) approximately two years of professional experience with Internet-based video delivery systems; and (3) working proficiency with network architecture, including Internet-hosted server-client systems, and with computer programming. PO Resp. 21 (citing Ex. 2025 ¶¶ 24–25). Patent Owner’s declarant, Dr. Wicker, testifies that the parties’ definitions are only “slightly different,” and that if Dr. Wicker were to adopt Petitioner’s definition, that would not change any of his opinions. Ex. 2025 ¶ 24. Because the parties’ definitions of a person of ordinary skill in the art only “slightly differ,” we accept the assessment offered by Petitioner, which appears consistent with the ’251 patent and the asserted prior art. Regardless of which definition is applied, our analysis and decision would not change.” slip op. at 11

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

    “C. Claim Construction Both parties propose construing the claim term “media player” because it was construed in a related inter partes review proceeding as well as in a district court case. Pet. 19; PO Resp. 21. According to Patent Owner, construing “media player” to mean “software for playing media” would be consistent with the construction applied in both related proceedings. PO Resp. 21. Petitioner agrees, noting that the term “media player” “‘refers to software and not to a hardware device.’” Pet. 19 (citing Ex. 1164, 13). player” used by both parties, and we need not engage in any further claim construction because there are no claim construction disputes that bear on the issues before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Alleged Obviousness of Claims 1–26 in View of Danciu and Mahajan or” slip op. at 11

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedMixed

    “Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position. To the contrary, we find Dr. Wicker’s testimony to be credible because it is supported by the disclosures in both Mahajan and Danciu. Specifically, we agree with Dr. Wicker, who testified that Mahajan does not describe an abstraction layer as ever being on “a server in the network.” See Ex.1197, 18:21–24. We also find Dr. Wicker’s testimony credible when he explained that even if Mahajan’s abstraction layer were implemented on a server in a network as posited by Petitioner, it still would not result in the claim mapping proposed by Petitioner. See Ex. 2025 ¶ 45 (Dr. Wicker: “[T]he two abstraction modules work together to create a ‘collaboration media abstraction layer 130.’”) (citing Ex. 1114 ¶ 22; Ex. 2027, 39:6–40:12, 44:10–19 (Mr. Lett reading from and agreeing with paragraph 45 of Dr. Wicker’s Declaration)).” slip op. at 25

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

    “Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position.” slip op. at 25

  Patent outcomesUS 8,356,251 mixed
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 8,356,251
• Charter Communications, Inc. / Altice USA, Inc. v. Touchstream Technologies, Inc.Some claims unpatentable
  PTAB · Jun 12, 2025 · IPR2024-01262 · APJ Georgianna W Braden · IPR · Final written decision

  Claims 22–26 are unpatentable as obvious; claims 1–21 were not shown unpatentable because the asserted combinations did not teach or justify the claimed server-side command conversion.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner contends that a person of ordinary skill in the art of the ’251 patent would have had: (1) the equivalent of a four-year, B.S. degree from an accredited institution in computer science, computer engineering or an equivalent field; (2) approximately two years of professional experience with Internet-based video delivery systems; and (3) working proficiency with network architecture, including Internet-hosted server-client systems, and with computer programming. PO Resp. 21 (citing Ex. 2025 ¶¶ 24–25). Patent Owner’s declarant, Dr. Wicker, testifies that the parties’ definitions are only “slightly different,” and that if Dr. Wicker were to adopt Petitioner’s definition, that would not change any of his opinions. Ex. 2025 ¶ 24. Because the parties’ definitions of a person of ordinary skill in the art only “slightly differ,” we accept the assessment offered by Petitioner, which appears consistent with the ’251 patent and the asserted prior art. Regardless of which definition is applied, our analysis and decision would not change.” slip op. at 11

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

    “C. Claim Construction Both parties propose construing the claim term “media player” because it was construed in a related inter partes review proceeding as well as in a district court case. Pet. 19; PO Resp. 21. According to Patent Owner, construing “media player” to mean “software for playing media” would be consistent with the construction applied in both related proceedings. PO Resp. 21. Petitioner agrees, noting that the term “media player” “‘refers to software and not to a hardware device.’” Pet. 19 (citing Ex. 1164, 13). player” used by both parties, and we need not engage in any further claim construction because there are no claim construction disputes that bear on the issues before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Alleged Obviousness of Claims 1–26 in View of Danciu and Mahajan or” slip op. at 11

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

    “attempts to extrapolate Mahajan’s specific teachings and specific architecture into a general principle such that specific commands are converted to universal commands and then universal commands are converted to specific commands regardless of the location of the process within a distributed system. See Tr. 14:5–11. Rather, we agree with Patent Owner that Petitioner’s extrapolation arguments are unsupported by Mahajan. We understand Petitioner argues that Mahajan’s “distributed computing environments” would have rendered it obvious to alter the location where command conversions occur. Pet. 41; Reply 10–11, 14. Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain” slip op. at 24

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedOther

    “Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position. To the contrary, we find Dr. Wicker’s testimony to be credible because it is supported by the disclosures in both Mahajan and Danciu. Specifically, we agree with Dr. Wicker, who testified that Mahajan does not describe an abstraction layer as ever being on “a server in the network.” See Ex.1197, 18:21–24. We also find Dr. Wicker’s testimony credible when he explained that even if Mahajan’s abstraction layer were implemented on a server in a network as posited by Petitioner, it still would not result in the claim mapping proposed by Petitioner. See Ex. 2025 ¶ 45 (Dr. Wicker: “[T]he two abstraction modules work together to create a ‘collaboration media abstraction layer 130.’”) (citing Ex. 1114 ¶ 22; Ex. 2027, 39:6–40:12, 44:10–19 (Mr. Lett reading from and agreeing with paragraph 45 of Dr. Wicker’s Declaration)).” slip op. at 25

  Patent outcomesUS 8,356,251 mixed
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 8,356,251
• Lululemon USA Inc. v. Nike, Inc.Some claims unpatentable
  PTAB · May 21, 2025 · IPR2024-00159 · APJ Carl M Defranco · IPR · Final written decision

  Claims 8, 9, 14, 15, and 19 are unpatentable over Minami; claims 1–3, 7, 16–18, and 20 were not shown unpatentable over Good or Munsing.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “lululemon contends, and Nike does not dispute, that a person skilled in the art in the relevant time frame would have had “at least a bachelor’s degree in mechanical engineering, textile engineering, or similar technical degree and at least 3 years of experience working with knitted textiles for use in fabric-based articles, including apparel such as footwear” and such person’s “additional experience compensates for any differences in that person’s education as stated above.” Pet. 13–14 (citing Ex.1003 ¶¶ 33–35); see also PO Resp. 14 (“For purposes of this proceeding, Nike applies lululemon’s proposed level of skill in the art.”). We find that lululemon’s proposed definition is consistent with the problems and solutions described in the ’046 patent and the prior art of record. Thus, we adopt the parties’ agreed-upon definition of the level of skill in the art.” slip op. at 6

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

    “We are not persuaded by lululemon’s attempt to equate the term “channel” in that passage with an open-periphery configuration. Nowhere does that passage indicate that the “channel” has an open-periphery. Instead, lululemon merely presumes, without support, that channels are open-periphery structures. More accurately, the terms “tunnel” and “channel” in the passage cited by lululemon are used synonymously. That is made clear by the overall context of the ’046 patent at issue, which is directed to how tubular rib structures 126 are formed by “first” and “second” curved portions 416 and 418 that are “knitted together” to define “hollow tube 112.” See Ex. 1001, 10:16–11:14, Figs. 4, 5 (emphasis added). In particular, the sentence cited by lululemon describes hollow tube 112 as being “disposed between” first and second curved portions 416 and 418, which Figures 4 and 5 of the ’046 patent clearly depict in a closed-periphery configuration. See id. at 10:66–11:3, Figs. 4, 5. Moreover, the very next sentence expressly describes that hollow tube 112 has “a generally cylindrical or elliptical shape” wherein “[t]he diameter of one hollow tube and the diameter of other hollow tubes may differ in some embodiments.” Id. at 11:3–14 (emphases added). We are not aware of any open-periphery channels being described as having a cylindrical or elliptical shape, nor are we aware of such a channel being described as having a diameter. Thus, lululemon’s proposed claim construction ignores the context surrounding the ’046 patent’s description of the tubular rib structures when it describes them as having the configuration of a tunnel or channel.” slip op. at 10

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “We agree with Nike, given our construction of the claimed “tubular structures.” As shown in annotated Figures 1, 3, and 4 of Good (reproduced below), Good discloses a sock 12 having rib portions 22 (red) and webbed areas 24 (green). See PO Resp. 19. lululemon contends that Good’s rib portions 22 meet the claimed “tubular structures” because each rib portion 22 “roll[s] substantially together in the relaxed condition” and “has the shape of a tube, namely an elongate hollow structure.” Pet. 29–30. In support, lululemon points to Good’s Figure 3 (reproduced below center) as allegedly showing the tubular shape of Good’s rib portions 22. Id. at 30. Annotated Figure 3 is a vertical cross-section of rib portions 22 (red) shown in Good’s Figure 1. But, as Nike correctly notes, Good’s rib portions 22 are “C-shaped knitted portions,” which when stretched, go from an essentially C-shaped configuration (Figure 3) to a relatively flat, linear configuration (Figure 4). PO Resp. 19–20 (citing Ex. 2006 ¶¶ 48–49). Nowhere does Good disclose that the ends of C-shaped rib portions 22 ever meet and remain in a closed periphery configuration to form a hollow tube per our construction of “tubular structures” (as discussed above in Section II.B). In at least this way, Good’s C-shaped rib portions 22 differ from the claimed “tubular structures.”7 Thus, we find that Good does not disclose or otherwise suggest the claimed “tubular structures,” as properly construed, meaning that lululemon fails to demonstrate, by a preponderance of the evidence, that Good either anticipates claims 1–3, 7, 16–18, and 20, or, alternatively, renders obvious claim 3.” slip op. at 16

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “In our Institution Decision, we said that Munsing lacks the claimed “tubular structures” because “nowhere does Munsing indicate that the rows of stitches or loops form a rib that is tubular-like, let alone one with a closed periphery.” Inst. Dec. 10–12. During the trial phase, lululemon’s expert likewise agreed, conceding (on cross-examination) that Munsing only discloses non-tubular structures. See Ex. 2007, 40:9–41:11 (“Q [by Patent Owner’s counsel]: So you agree that . . . Munsing only discloses a nontubular rib? A [by lululemon’s expert]: That’s what I said.”). Nowhere does lululemon rebut that admission by its own expert, despite Nike noting it explicitly as a reason for rejecting Ground 2. Compare PO Resp. 25–26 (noting the admission of lululemon’s expert), with Pet. Reply 1–26 (addressing only Grounds 1 and 3, while omitting any mention of Ground 2, which is based on Munsing). Nor does lululemon ever dispute the preliminary findings in our Institution Decision as to why Munsing is not an anticipatory reference. Compare Inst. Dec. 10–12, with Pet. Reply 1–22. Thus, lululemon fails to demonstrate, by a preponderance of the evidence, that Munsing anticipates challenged claims 1–3, 7, 17, 18, and 20.” slip op. at 18

  Patent outcomesUS 9,375,046 mixed
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 9,375,046
• LG Electronics, Inc. / LG Electronics U.S.A., Inc. et al. v. Multimedia Technologies Pte. Ltd.Some claims unpatentable
  PTAB · May 19, 2025 · IPR2024-00699 · APJ St John Courtenay III · IPR · Final written decision

  Claims 1, 2, 6–11, and 14–18 are unpatentable under § 103; claims 3–5, 12, and 13 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “contends that an ordinarily skilled artisan for the ’805 patent “would have been someone knowledgeable about and familiar with the television display technology that is pertinent to the ’805 patent. A POSITA would have had a bachelor’s degree in Electrical Engineering, Software Engineering, or Computer Engineering, or equivalent training, and approximately two years of experience working in the field of television systems and networking, human-computer interaction, or related technologies. Lack of work experience can be remedied by additional education, and vice versa.” Pet. 9 (citing Ex. 1003 ¶¶ 18–20). In its Preliminary Response Patent Owner indicated it “adopts Petitioner’s definition of a person of ordinary skill in the art (‘POSITA’) for the purposes of [its] Preliminary Response.” Prelim. Resp. 28. We note Patent Owner does not dispute or otherwise disavow Petitioner’s definition of a POSITA in its Response or Sur-reply. See generally PO Resp.; PO Surreply. level of ordinary skill in the art. On the present record, we are satisfied that this definition comports with the level of skill necessary to understand and implement the teachings of the ’805 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that the prior art itself can reflect appropriate level of ordinary skill in art).” slip op. at 10

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

    “We disagree with Patent Owner. Id. We see nothing in the preamble 1.0, or “receiving” step 1.1.1, or “wherein” clause 1.1.2 that defines a data format prior to organizing step 1.2.1, and we decline to read limitations from the specification into the claim, i.e., a “pre-defined format” being defined prior to organizing step 1.2.1, as argued by Patent Owner. 5 PO Resp. 20. Preamble 1.0 is silent regarding any mention of a data format: “A method of providing content for a television (TV), the method comprising: . . . .” Although step 1.1.1 requires “receiving, by a processor, data relevant to one or more scheduled events from one of a corresponding subservice of a plurality of subservices,” at best this merely requires a type of data that is “relevant to one or more scheduled events” and does not require a particular data format to be used for “data relevant to one or more scheduled events,” nor the “pre-defined” format argued by Patent Owner. PO Resp. 20–21. (emphases added). Nor do we read step 1.1.2 as defining a particular data format used by the three recited types of subservices: “[1.1.2] wherein the plurality of subservices comprises a video-on-demand (VOD) subservice, electronic programming guide (EPG) subservice, and a media subservice.” 5 We emphasize that patentability is based upon the claims. “It is the claims that measure the invention.” SRI Int’l v. Matsushita Elec. Corp. of America, 775 F.2d 1107, 1121 (Fed. Cir. 1985) (en banc). A basic canon of claim construction is that one may not read a limitation into a claim from the written description. Renishaw PLC v. Marposs Societa' per Azioni, 158 F.3d 1243, 1248 (Fed. Cir. 1998). according to a pre-defined format corresponding to each of the plurality of subservices.” (emphases added). However, we find Patent Owner’s contention unavailing that the term “pre-defined format” recited in step 1.2.1 requires three different data model pre-defined formats because claim 1 is silent regarding the argued term “different.” See PO Sur-reply 9 (regarding Patent Owner’s response to the question of “whether element [1.2.1] and the term ‘pre-defined format’ requires three different data models.” Patent Owner responds: “For the above reasons, they do.”). Moreover, we note the term “data model” is not introduced until subsequent “wherein” clause 1.2.2, which merely requires that “the predefined format comprises one of a VOD data model, an EPG data model and a media data model.” (emphasis added).” slip op. at 20

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

    “Regarding the claim 1 term “uniform format” Petitioner replies that Patent Owner “does not dispute that the prior art teaches a ‘uniform format’” in step 1.2.4. Pet. Reply 8 (citing generally PO Resp.). Therefore, Petitioner argues “for the purposes of this proceeding, the term “uniform format” does not require express construction.” Pet. Reply 8 (citing Nidec (Fed. Cir. 2017)). Nevertheless, at the Board’s request (Dec. 29), Petitioner proceeds to address the scope of the claim 1 term “uniform format.” Pet. Reply 8. Petitioner notes that the ’805 patent uses the term “uniform format” in column 33: “The data models provide uniform formats for the respective subservices (i.e., VOD subservice 1420, EPG subservice 1424, and media subservice 1428) and/or the internal content provider modules 1416 which interface with applications 416.” Pet. Reply 8 (quoting Ex.1001, 33:25–30). Petitioner further notes that Dr. Lippmann explains, “the ’805 patent does not appear to ascribe any specific meaning to the term ‘uniform format’ and the passage does not limit the scope of this term to require a plurality of uniform formats.” Pet. Reply (quoting Ex. 1020 ¶ 13).” slip op. at 22

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artDecided for petitioner

    “Patent Owner’s arguments are not persuasive because on January 14, 2025, the Federal Circuit in Lynk Labs Inc. v. Samsung Electronics Co. Ltd., (125 F.4th 1120, 1132 (Fed. Cir. 2025)) held that Title 35 U.S.C. sections “311(b) and 102(e)(1) permit IPR challenges based upon published patent applications, and such published patent applications can be deemed prior art in IPRs as of their filing date.” (emphasis added). Accordingly, we conclude both Melnychenko and Choi are prior art for the purpose of this IPR pursuant to 35 U.S.C. § 311(b) under the holding of Lynk Labs.” slip op. at 6

  Patent outcomesUS 10,419,805 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,419,805
• LG Electronics, Inc. / LG Electronics U.S.A., Inc. et al. v. Multimedia Technologies Pte. Ltd.Some claims unpatentable
  PTAB · May 19, 2025 · IPR2024-00354 · APJ St John Courtenay III · IPR · Final written decision

  Claims 1, 2, 6–11, and 14–18 are unpatentable as obvious; claims 3–5, 12, and 13 were not shown unpatentable.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artDecided for petitioner

    “Patent Owner’s arguments are not persuasive because on January 14, 2025, the Federal Circuit in Lynk Labs Inc. v. Samsung Electronics Co. Ltd., (125 F.4th 1120, 1132 (Fed. Cir. 2025)) held that Title 35 U.S.C. sections “311(b) and 102(e)(1) permit IPR challenges based upon published patent applications, and such published patent applications can be deemed prior art in IPRs as of their filing date.” (emphasis added). Accordingly, we conclude both Melnychenko and Choi are prior art for the purpose of this IPR pursuant to 35 U.S.C. § 311(b) under the holding of Lynk Labs.” slip op. at 6

  • Skill levelSkill level petitioner adoptedDecided for patent owner

    “Relying upon the declaration testimony of Dr. Lippman, Petitioner contends that an ordinarily skilled artisan for the ’805 patent “would have been someone knowledgeable about and familiar with the television display technology that is pertinent to the ’805 patent. A POSITA would have had a bachelor’s degree in Electrical Engineering, Software Engineering, or Computer Engineering, or equivalent training, and approximately two years of experience working in the field of television systems and networking, human-computer interaction, or related technologies. Lack of work experience can be remedied by additional education, and vice versa.” Pet. 9 (citing Ex. 1003 ¶¶ 18–20). In its Preliminary Response Patent Owner indicated it “adopts Petitioner’s definition of a person of ordinary skill in the art (‘POSITA’) for the purposes of [its] Preliminary Response.” Prelim. Resp. 28. We note Patent Owner does not dispute or otherwise disavow Petitioner’s definition of a POSITA in its Response or Sur-reply. See generally PO Resp.; PO Surreply. level of ordinary skill in the art. On the present record, we are satisfied that this definition comports with the level of skill necessary to understand and implement the teachings of the ’805 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that the prior art itself can reflect appropriate level of ordinary skill in art).” slip op. at 10

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

    “We disagree with Patent Owner. Id. We see nothing in the preamble 1.0, or “receiving” step 1.1.1, or “wherein” clause 1.1.2 that defines a data format prior to organizing step 1.2.1, and we decline to read limitations from the specification into the claim, i.e., a “pre-defined format” being defined prior to organizing step 1.2.1, as argued by Patent Owner. 5 PO Resp. 20. Preamble 1.0 is silent regarding any mention of a data format: “A method of providing content for a television (TV), the method comprising: . . . .” Although step 1.1.1 requires “receiving, by a processor, data relevant to one or more scheduled events from one of a corresponding subservice of a plurality of subservices,” at best this merely requires a type of data that is “relevant to one or more scheduled events” and does not require a particular data format to be used for “data relevant to one or more scheduled events,” nor the “pre-defined” format argued by Patent Owner. PO Resp. 20–21. (emphases added). Nor do we read step 1.1.2 as defining a particular data format used by the three recited types of subservices: “[1.1.2] wherein the plurality of subservices comprises a video-on-demand (VOD) subservice, electronic programming guide (EPG) subservice, and a media subservice.” 5 We emphasize that patentability is based upon the claims. “It is the claims that measure the invention.” SRI Int’l v. Matsushita Elec. Corp. of America, 775 F.2d 1107, 1121 (Fed. Cir. 1985) (en banc). A basic canon of claim construction is that one may not read a limitation into a claim from the written description. Renishaw PLC v. Marposs Societa' per Azioni, 158 F.3d 1243, 1248 (Fed. Cir. 1998). according to a pre-defined format corresponding to each of the plurality of subservices.” (emphases added). However, we find Patent Owner’s contention unavailing that the term “pre-defined format” recited in step 1.2.1 requires three different data model pre-defined formats because claim 1 is silent regarding the argued term “different.” See PO Sur-reply 9 (regarding Patent Owner’s response to the question of “whether element [1.2.1] and the term ‘pre-defined format’ requires three different data models.” Patent Owner responds: “For the above reasons, they do.”). Moreover, we note the term “data model” is not introduced until subsequent “wherein” clause 1.2.2, which merely requires that “the predefined format comprises one of a VOD data model, an EPG data model and a media data model.” (emphasis added).” slip op. at 20

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

    “Regarding the claim 1 term “uniform format” Petitioner replies that Patent Owner “does not dispute that the prior art teaches a ‘uniform format’” in step 1.2.4. Pet. Reply 8 (citing generally PO Resp.). Therefore, Petitioner argues “for the purposes of this proceeding, the term “uniform format” does not require express construction.” Pet. Reply 8 (citing Nidec (Fed. Cir. 2017)). Nevertheless, at the Board’s request (Dec. 29), Petitioner proceeds to address the scope of the claim 1 term “uniform format.” Pet. Reply 8. Petitioner notes that the ’805 patent uses the term “uniform format” in column 33: “The data models provide uniform formats for the respective subservices (i.e., VOD subservice 1420, EPG subservice 1424, and media subservice 1428) and/or the internal content provider modules 1416 which interface with applications 416.” Pet. Reply 8 (quoting Ex.1001, 33:25–30). Petitioner further notes that Dr. Lippmann explains, “the ’805 patent does not appear to ascribe any specific meaning to the term ‘uniform format’ and the passage does not limit the scope of this term to require a plurality of uniform formats.” Pet. Reply (quoting Ex. 1020 ¶ 13). In its Sur-reply, Patent Owner notes that “Petitioners do not appear to” slip op. at 22

  Patent outcomesUS 10,419,805 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,419,805
• Inergy Technology, Inc. v. Force Mos Technology Co., Ltd.Some claims unpatentable
  PTAB · May 16, 2025 · IPR2024-00094 · APJ Mary C Hoffman · IPR · Final written decision

  Claims 1 and 3–5 are unpatentable over Kobayashi and Hshieh; claims 2 and 6 were not shown unpatentable over the asserted combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that a person of ordinary skill in the art (“POSITA”), “at the filing date of the ’409 [p]atent[,] would have a master’s degree in electrical engineering, and at least two years of relevant work experience in the field of integrated circuit design and manufacturing.” Pet. 13 (citing Ex. 1003 ¶ 52). Patent Owner does not dispute Petitioner’s proffered level of ordinary skill in the art. PO Resp. 9 (citing Ex. 2021 ¶ 55). We adopt Petitioner’s proffered level of ordinary skill in the art, which is supported by unopposed declaration testimony and consistent with the ’409 patent and prior art of record. See, e.g., Ex. 1001, 1:6–3:8 (describing the invention and related art in terms of integrated circuit design and fabrication). Neither party, moreover, indicates the overall result would change based on a different definition.” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “Based on the arguments and evidence, we disagree with Petitioner’s proposed construction requiring the corners to be rounded via a particular process, because doing so would improperly import a process of manufacture from the Specification into apparatus claims. See Cont’l Circuits LLC v. Intel Corp., 915 F.3d 788, 799 (Fed. Cir. 2019) (explaining that, generally, a novel product that meets the criteria of patentability is not limited to the process by which it was made, however, process steps can be treated as part of a product claim if the patentee has made clear that the process steps are an essential part of the claimed invention). Here, the portions of the Specification relied on by Petitioner (Ex. 1001, 2:10–20, 4:53–64) disclose a process for manufacturing but do not make clear that the process is an essential part of the claimed invention. We also disagree with Petitioner’s assessment of the prosecution history, i.e., that the claims were amended to distinguish the claimed rounded corners from Pfirsch’s rounded corners, which, presumably, are formed as an incidental result of lithography. On the contrary, the Examiner found (and Patent Owner acknowledged) that Pfirsch has rounded corners. Ex. 1002, 276, 295, 302. As Patent Owner correctly points out, the claims were amended during prosecution to include a “circular” contact to distinguish over Pfirsch’s square contact. See id. Petitioner does not otherwise point to evidence that Patent Owner clearly and unmistakably limited the claim scope to rounded corners formed by a particular process.” slip op. at 12

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “is ‘known’ is not sufficient for a motivation to combine.” PO Resp. 47. However, the motivation-to-combine analysis is a flexible one, and the “known-technique” rationale is adequate to show a motivation to combine. For example, “if a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious unless its actual application is beyond his or her skill.” KSR, 550 U.S. at 417; see also Intel Corp. v. PACT XPP Schweiz AG, 61 F.4th 1373, 1380 (Fed. Cir. 2023) (quoting Intel Corp. v. Qualcomm Inc., 21 F.4th 784, 799–800 (Fed. Cir. 2021) (“If there’s a known technique to address a known problem using ‘prior art elements according to their established functions,’ then there is a motivation to combine.”). Here, as discussed above, the record shows that top view rounding was a known technique to eliminate corners, and that corners were a known problem (e.g., corners tend to reach undesirable higher peak electric field leading to premature breakdown voltage). See, e.g., Ex. 1003 ¶¶ 37, 39, 42– 44, 55–57, 122, 133, 135–141; Ex. 1005, 7:57–8:4; Ex. 1006, 1:18–21, 2:19–39, 5:3–17, Figs. 6A–8B; Ex. 1011, 1:29–41; Ex. 1012; PO Resp. 13, 46 (citing Ex. 1011, 1:34–40); Ex. 2021 ¶ 87. Furthermore, there is no dispute that modifying Kobayashi to eliminate corners via top view rounding was anything more than a “minor and commonplace modification” of cell shape within the skill of an ordinary artisan, or that top view rounding would change Kobayashi’s established function. Pet. 60; Ex. 2021 ¶ 86.” slip op. at 30

  • Obviousness (§103) › KSR rationalesMotivation foundUnpatentable

    “We agree that Kobayashi’ s Figure 5A solely cannot be relied upon as disclosing the claimed diameter. See Hockerson-Halbertstadt, Inc. v. Avia Group Int'l, 222 F.3d 951, 956 (Fed. Cir. 2000) (patent drawings not designated as being drawn to scale cannot be relied upon to define precise proportions of elements if the specification is completely silent on the issue). However, we do not agree that Petitioner failed to show Kobayashi suggests the recited diameter. We disagree with Patent Owner’s assertion that Dr. Liu’s “vague, purported ‘design considerations’” are “unsupported.” PO Resp. 43. Although Kobayashi is silent on the width/diameter of the trench contact in Figure 5A, Kobayashi discloses trenched gates having dimensions below 0.5 μm, which demonstrates that it was known in the art, and required no more than an exercise of ordinary skill in the art, to create trenched features of widths well below 1 μm. Kobayashi also discloses that the width of each trench, and the distance between the adjacent trenches (which includes the trench contact), must be selected to optimum sizes . . . [and] these sizes . . . have some degrees of freedom.” Ex. 1005, 7:42–48. This demonstrates a POSITA would seek to optimize trench contact width or diameter. Dr. Liu’s testimony regarding design considerations suggests the desirability of a reduced diameter trench contact, e.g., to minimize the width of the trench contact for purposes of easier filling, to minimize the total width of the unit cell, and to minimize manufacturing time by reducing etch back time. See Ex. 1003 ¶¶ 111–114. As Patent Owner acknowledges, “there is always a motivation to speed up the fabrication process or shrink feature sizes of semiconductors.” PO Resp. 43 (citing 2021 ¶ 131). However, contrary to Patent Owner’s arguments, these are not generic motivations “untethered” from Kobayashi. Id. Indeed, Kobayashi directly addresses the fabrication process (including new techniques to obtain trench widths under 0.5 μm) and the need to optimize the size of trench gates and the space in between (which includes the trench contact). Ex. 1005, 7:43–54, 7:19–9:53. Patent Owner also argues that Petitioner presents no evidence that modifying Kobayashi to have a diameter smaller than 1 μm is predictable. PO Resp. 44. We disagree. As discussed above, Petitioner points to Kobayashi’s teachings that the sizes are to be optimized and that the trench gate width is smaller than 0.5 μm, which suggests making other trench features of that width was within ordinary skill. Ex. 1003 ¶ 112. Furthermore, Kobayashi’s silence as to the dimensions of the trench contact suggests that the trench contact diameter dimension is likely in the ballpark of the other explicitly disclosed trenched feature dimensions and is a matter of routine optimization. In addition, Patent Owner advances no persuasive evidence that the claimed diameter produces unexpected results or is otherwise critical. Patent Owner also argues that reducing trench contact diameter has downsides (i.e., reduced ease of filling for metal plugs and reduced current carrying capacity) not addressed by Petitioner; however, Petitioner is not required to address those tradeoffs in its Petition, and we do not see how those tradeoffs would prevent the proposed combination. PO Resp. 44; see Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006) (“a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.”); Winner Int'l Royalty Corp. v. Wang, 202 F.3d 1340, 1349 n.8 (Fed. Cir. 2000) (“The fact that the motivating benefit comes at the expense of another benefit, however, should not nullify its use as a basis to modify the disclosure of one reference with the teachings of another. Instead, the benefits, both lost and gained, should be weighed against one another.”). Here, Dr. Liu listed numerous benefits of having a reduced diameter, which weigh against the potential downsides raised by Patent Owner. Ex. 1003 ¶¶ 111–114. Moreover, we do not see how the downsides/tradeoffs prevent modifying Kobayashi in the manner suggested when the same tradeoffs appear to be applicable to the ’409 patent. Having considered Patent Owner’s arguments, and taking into” slip op. at 43

  Patent outcomesUS 7,812,409 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,812,409
• Inductev, Inc. v. Witricity CorporationSome claims unpatentable
  PTAB · May 16, 2025 · IPR2024-00140 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1, 7–10, 12–16, 18, and 19 are unpatentable over the stated grounds; claims 4–6 were not shown unpatentable because the proposed multi-coil alignment lacked prior-art support.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person of ordinary skill in the art “would have had . . . a bachelor’s degree in electrical engineering, microelectronics, or equivalent and . . . two to three years of industry or research experience in the field of wireless energy transfer,” and that “a higher level of education or skill might make up for less experience, and vice-versa.” Pet. 6 (citing Ex. 1003 ¶¶ 39–44). Patent Owner does not contest this. See PO Resp. Petitioner’s proposed articulation is supported by testimonial evidence and appears to be consistent with the types of problems and solutions in the ’654 patent. See Ex. 1001, 1:15–28. We adopt it for this decision.” slip op. at 7

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

    “We agree with Petitioner that the evidence does not suggest (and Patent Owner does not explicitly argue) that the terms “transmitting antenna” and “receiving” antenna depart from the ordinary and customary meanings of those terms. Pet. 1–2. However, for the reasons discussed below, the outcome of our decision would be the same whether we adopted Petitioner’s or Patent Owner’s proposed construction. Thus, we need not adopt either party’s proposed construction for this decision. 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 9

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for patent owner

    “spaced configuration are not confined to ferrite cores 32 and 3, and that at least a component of the flux lines will escape the cores. See Ex. 1032 ¶¶ 48–52; Ex. 1038 ¶ 54 Fig. 2. Indeed, the evidence suggests (and Dr. Horenstein acknowledges in his first declaration) that at least a component of flux will escape the core of even a traditional transformer. See Ex. 1032 ¶¶ 45–47; Ex. 1044, 6; Ex. 2001 ¶ 27. In his second declaration, Dr. Horenstein provides contrary testimony that in Odachi’s open configuration during alignment, cores 32 and 3 “act to confine or guide the magnetic flux lines, rather than radiate them into free space,” and “the flux lines would [not] leave the gap area and enter into the space distal to the magnetic circuit.” Ex. 2010 ¶ 69. But in view of Dr. Horenstein’s contrary position in his first declaration, and the lack of supporting evidence in his second, we do not find it credible. 37 C.F.R. § 42.65(a) (2022) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”); Apple Inc. v. MPH Techs. Oy, 28 F.4th 254 (Fed. Cir. 2022).” slip op. at 24

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

    “(4) Analysis We are persuaded by Petitioner’s argument that during the alignment process in Odachi corresponding to claim 13, there is a “spaced distance between the primary inductive coupler [230] and the secondary inductive receptacle 2” which is “reduced gradually and electromagnetic induction occurs between the coupler to the receptacle when the former coupler comes close to the latter receptacle.” Ex. 1005, 6:1–6. Thus, prior to any contact or precise alignment between the two cores, “an electromotive force is induced in the secondary coil 4 and this induced force is increased with the decrease in the spaced distance.” Id. at 6:6–8. At least in that spaced configuration, the evidence of record suggests that primary coil 31 produces a near-field component of flux into free space (the air space between the coils where there is no intervening core material) that is intercepted by secondary coil 4 to effect resonant inductive coupling, and that secondary coil 4 intercepts and receives the near-field component of flux in free space that is generated by primary coil 31 to effect resonant inductive coupling. See Ex. 1032 ¶¶ 48–52, 55. Thus, we find that Odachi discloses a “transmitting antenna” (coil 31) and a “receiving antenna” (coil 4) under Patent Owner’s proposed construction. We would reach the same finding under Petitioner’s proposed broader construction because the evidence suggests that Odachi’s coils 31 and 4 would have been considered “antennas” under the parties’ uncontested definition of that term, which is “a device that radiates and/or receives radio waves.” See id. ¶¶ 43–47, 53–54; Ex. 1032 ¶ 15 (Dr. Allen agreeing with this definition of “antenna”); Ex. 2001 ¶ 25 (Dr. Horenstein agreeing with this definition of “antenna”)). In addition, Petitioner persuasively shows that the free space between Odachi’s coils in the spaced configuration includes the “near-field region,” which includes the induction field around primary coil 31. See Ex. 2006, 498; Ex. 1045, 5:4–7; Ex. 1032 ¶¶ 53–54). Dr. Horenstein’s testimony does not contradict this. Although he points out that there are separate terms for inductive, near, and far fields, he also acknowledges that “[t]he region of space closer to the antenna than the far field is the near-field region.” Ex. 2010 ¶ 37 (citing Ex. 2006, 275).8” slip op. at 22

  Patent outcomesUS 8,466,654 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,466,654

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.