• Juniper Networks, Inc. v. Portsmouth Network Corp.All claims unpatentable
  PTAB · Dec 9, 2025 · IPR2024-00893 · APJ Justin T Arbes · IPR · Final written decision

  Claims 3, 8, 11, 12, 15, 20, 23, and 24 are unpatentable as obvious over Gai and IEEE 1999.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that at the time of the application for the ’986 patent (January 2002), a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering or a related field, plus at least two years of industry experience or graduate-level academic experience with computer networking.” Pet. 20. In the Decision on Institution, the Board agreed with and applied Petitioner’s proposed definition, removing the phrase “at least” to avoid unnecessary ambiguity. Dec. on Inst. 18–19. Patent Owner uses Petitioner’s proposed definition for its Response. PO Resp. 5. Neither party made any further argument regarding the level of ordinary skill in the art in its papers during trial. In the Cisco IPR, we adopted a similar definition, determining that a person of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, electrical engineering, or in an equivalent field, or approximately two years of experience working in the field of information technology and networking,” where “[l]ack of professional experience can be substituted by additional education, and vice versa.” IPR2024-00505, Paper 29 at 10–11 (alteration in original); see Dec. on Inst. 19 n.7 (noting the proposed definition in the Cisco IPR). Based on the full record developed during trial, including our review of the ’986 patent and the types of problems and solutions described in the ’986 patent and cited prior art, we adopt the same definition of the level of ordinary skill in the art as the Cisco IPR and apply it for purposes of this Petitioner’s similar proposed definition in this proceeding.” slip op. at 12

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Gai discloses entering an Enable_Uplinkfast command at an access switch (e.g., access switch 114) to block a failed port (e.g., the root port) and configure the access switch to send dummy traffic upstream through a new active port. . . . When modified in view of IEEE 1999’s disclosure that self-healing network traffic can advantageously be sent both upstream and downstream, the command would be entered at a backbone switch (e.g., backbone switch 122) to block a failed port (e.g., a designated port connected to access switch 114) and configure the backbone switch to send dummy traffic downstream to an access switch (e.g. access switch 114) through a new active port. While Gai uses its protocol signaling command, Enable_Uplinkfast, to send dummy traffic through a new root port, [a person of ordinary skill in the art] would deem it an obvious implementation detail to modify the parameters of the port on a backbone switch. See Ex. 1003 ¶ 139 (citing Ex. 1005, col. 6, ll. 39–46).” slip op. at 34

  • Prior constructionPrior construction adoptedDecided for petitioner

    “In the Cisco IPR, we addressed four claim terms in the final written decision: “access switch” and “edge switch,” which appear in independent claims 1 and 13 and various dependent claims, and “downstream” and “upstream,” which appear in claims 11, 12, 23, and 24. IPR2024-00505, Paper 29 at 11–14. We interpreted “access switch” to mean “a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems,” interpreted “edge switch” to mean “a core switch that is directly connected to an access switch,” interpreted “downstream” to mean “away from the root switch,” and interpreted “upstream” to mean “toward the root switch.” Id. As noted above, Patent Owner did not appeal that decision. We incorporate herein our previous analysis in the Cisco IPR, but note that none of the analysis of the disputed issues below depends on such determine whether Petitioner has met its burden to prove unpatentability of the challenged claims. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe [a particular claim limitation] where the construction is not ‘material to the . . . dispute.’” (emphasis added) (citation omitted)).” slip op. at 13

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

    “1999, supported by the testimony of Mr. McNair, which we credit, is persuasive. See Pet. 25–30, 40–46; Ex. 1003 ¶¶ 132–145, 165–174. Based on the full trial record, we find that Gai and IEEE 1999 teach limitation [1E] and that a person of ordinary skill in the art would have been motivated to combine their teachings in the manner described by Petitioner. Based on all of the evidence of record, we determine that Petitioner has proven, by a preponderance of the evidence, that claim 3 would have been obvious over Gai and IEEE 1999 under 35 U.S.C. § 103(a). 4. Claims 8, 15, and 20 Claim 8 depends indirectly from independent claim 1. Claims 15 and 20 depend indirectly from independent claim 13, which is similar to claim 1 but recites a network switching device rather than a method. As to independent claim 13, Patent Owner refers to its earlier arguments regarding claim 1, asserting that limitation [13C] is “substantially similar” to limitation [1E]. PO Resp. 14–15. We disagree with Patent Owner’s arguments for the reasons explained above. See supra Section II.D.3.b. Patent Owner does not argue dependent claims 8, 15, and 20 separately from their respective parent claims 1 and 13. See PO Resp. 19. We have reviewed Petitioner’s contentions and supporting evidence, including the testimony of Mr. McNair, and are persuaded that Petitioner has proven, by a preponderance of the evidence, that claims 8, 15, and 20 would have been obvious based on Gai and IEEE 1999 under 35 U.S.C. § 103(a), for the reasons stated by Petitioner. See Pet. 21–46, 48–52, 55–59; Ex. 1003 ¶¶ 113–175, 179–185, 194–203.” slip op. at 41

  Patent outcomesUS 6,917,986 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,917,986
• Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00503 · APJ Charles J Boudreau · IPR · Final written decision

  Claims 1–18 were not shown unpatentable because the asserted obviousness combinations did not cure the failure to show the claimed request and routing steps.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art in the field of the ’279 patent in January 2001 “would have had a working knowledge of the network communication technologies that are pertinent to the ’279 patent, including network flow allocation in a ring topology.” Pet. 12. More specifically, Petitioner argues, a person of ordinary skill in the art “would have had a master’s degree in computer science, computer engineering, or an equivalent, and two years of professional experience relating to network communications and resource allocations,” where “[a]dditional work experience can substitute for specific educational background, and vice versa.” Id. (citing Ex. 1003 ¶ 20). Patent Owner represents that it “does not dispute Petitioner’s definition” for the purposes of its Response. PO Resp. 5. We find Petitioner’s proposal is consistent with the evidence of record, including the asserted prior art and the ’279 patent, and, therefore, we likewise adopt Petitioner’s proposed definition of the level of ordinary skill in the art for purposes of this Decision.” slip op. at 11

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

    “Neither party contends that any formal claim construction is necessary. See Pet. 12 (“Petitioner submits that, for the purposes of this proceeding and the grounds presented herein, no claim term requires express construction.”); PO Resp. 4 (“Here, at this stage in the proceeding, Patent Owner will apply the ordinary and customary meaning to the ’279 Patent’s claim terms.”). Patent Owner notes, however, that Petitioner had asserted specific constructions in the Cisco litigation for the term “predetermined,” as recited in claims 1, 10, 14–16, and 18, and for the term “quantum.” PO Resp. 4. Specifically, according to Patent Owner, Petitioner proposed that “predetermined” be construed as “determined before the data flow request” and that “quantum” be construed as “an amount of a requested resource by which to increase or decrease.” Id. (citing Ex. 2007). Patent Owner contends asserted prior art combinations disclose or render obvious the challenged claims under these constructions. Id. Because our conclusion that Petitioner has not demonstrated that any of the challenged claims are unpatentable does not turn on the construction of either “predetermined” or “quantum,” there is no need for us to construe those terms. See Realtime Data, 912 F.3d at 1375.” slip op. at 12

  • Strike new argumentNew argument disregardedDecided for patent owner

    “We again are not persuaded by Petitioner’s argument. As an initial matter, we find no argument with respect to “best effort data traffic” or dropped packets in the Petition. See Tr. 12:10–21 (conceding that “the phrase ‘best effort’ was not in the Petition” but arguing that it was raised in response to the Patent Owner Response). Moreover, we are unable to identify any argument in the Patent Owner Response to which this line of argument is properly responsive, and Petitioner does not identify any such line of argument. Instead, Petitioner’s argument appears to advance belatedly a new theory. See 37 C.F.R. § 42.23(b); Patent Trial and Appeal Board Consolidated Trial Practice Guide (Nov. 2019), 73–74, available at” slip op. at 43

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedMixed

    “We credit the supporting testimony of Dr. Olivier on the points discussed above, as it is explained sufficiently and consistent with the testimony simply mirrors the Petition and does not explain sufficiently why a person of ordinary skill in the art would have understood Kovvali in the manner Petitioner asserts. See Pet. 35; Reply 17–18; Ex. 1003 ¶ 83.” slip op. at 44

  Patent outcomesUS 7,035,279 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,035,279
• Cisco Systems, Inc. v. Portsmouth Network Corp.Some claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00505 · APJ Justin T Arbes · IPR · Final written decision

  Claims 1, 2, 4–7, 9, 10, 13, 14, 16–19, 21, and 22 are unpatentable as obvious over Gai under theory 1B; claims 11, 12, 23, and 24 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “patent, we look to “1) the types of problems encountered in the art; 2) the prior art solutions to those problems; 3) the rapidity with which innovations are made; 4) the sophistication of the technology; and 5) the educational level of active workers in the field.” Ruiz v. A.B. Chance Co., 234 F.3d 654, 666–67 (Fed. Cir. 2000). “Not all such factors may be present in every case, and one or more of them may predominate.” Id. at 667.” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningOther

    “The most common type of MAC bridge is a switch, which has multiple ports connecting it to LANs, other switches, host computing systems, or other network elements. Switches can be roughly classified as access switches or core switches. An access switch has ports that connect to LANs and/or to other network endpoints, such as user computer systems. Core switches interconnect the access switches into a Wide Area Network (WAN), by direct connection between the core switch and access switches and/or by connection to other core switches. Core switches that are directly connected to access switches are referred to herein as edge switches. Ex. 1001, col. 1, ll. 27–38. Both parties refer to this disclosure when arguing whether particular switches in the asserted prior art (Gai) qualify as an “access switch” or “edge switch.” See Pet. 5, 22, 27–28 (“edge switches are ‘[c]ore switches that are directly connected to access switches’”), 71; PO Resp. 31–32 (“The ’986 patent discloses that ‘[a]n access switch has ports that connect to LANs and/or to other network endpoints.’ . . . The ’986 patent also discloses that edge switches are ‘[c]ore switches that are directly connected to access switches.’”); Reply 20, 22. Dr. Houh and Dr. Olivier do so as well. See Ex. 1003 ¶¶ 39, 66–67, 82–83, 166, 171, 193; Ex. 2001 ¶ 80. Based on the full trial record, we agree and conclude that the descriptions of “access switch” and “edge switch” in the ’986 patent reflect what was understood to be the plain and ordinary meanings of these terms at the time of the invention. Accordingly, we interpret “access switch” to mean a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems, and interpret “edge switch” to mean a core switch that is directly connected to an access switch.” slip op. at 12

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

    “and conclude that Petitioner has not shown sufficiently that a person of ordinary skill in the art would have been motivated to designate switch 117 as the root switch when implementing the network reconfiguration method of Gai. The only mention of an access switch connected to port 7 of switch 114 is at column 13, lines 59–63 of Gai. While that sentence establishes that such an access switch may exist in the network, it does not state or imply that it would be the root switch. Instead, when discussing the operation of the Figure 1 network, Gai only identifies switches 120 and 121 as the root switch. See Ex. 1005, col. 10, ll. 37–41, col. 11, ll. 60–64, col. 14, ll. 16–20, col. 15, ll. 27–29, 38–51, col. 16, ll. 42–45. To be sure, Gai does disclose that “execution of the spanning tree algorithm causes the switches to elect a single switch, among all the switches within each network, to be the ‘root’ switch,” where “[e]ach switch has a unique numerical identifier (switch ID) and the root is the switch having the lowest switch ID numeric value,” such that an access switch can be the root switch if it has the lowest switch ID. See Ex. 1005, col. 2, ll. 42–47, col. 10, ll. 29–36. As Patent Owner and Dr. Olivier explain in detail, though, Gai expressly cautions against doing so. Gai discloses that [d]epending on the configuration of a given network, the location of the root can significantly affect the distance that messages must travel. For example, many networks include a plurality of switches designated as access switches that provide connectivity to LANs, end stations, etc., and a plurality of backbone switches that, in turn, interconnect the various access switches. If the root is located at an access switch and the principal server utilized by the end stations (i.e., clients) is coupled to a backbone switch, the average distance between end stations and the primary server may be quite high, resulting in inefficient network operation. In addition, the backbone switches may become partitioned as ports between them are blocked. Id. at col. 3, ll. 17–29; see also id. at col. 10, ll. 26–29 (the “location of the root may affect the average distance (i.e., the average number of hops) a message travels and/or cause undesirable partitioning of backbone switches”). Thus, the location of the root is not an unimportant consideration—it affects the distance messages must travel and can cause backbone switches to be partitioned. See id. Gai, therefore, discloses that “[t]o reduce the average distance and avoid partitioning of the backbone switches, it is desirable to locate the root at a backbone switch.”10 Id. at col. 3, ll. 29–31 (emphasis added). Switch 117 in Petitioner’s modified Figure 1 is an access switch, not a backbone switch. See id. at col. 6, ll. 10–12 (“Access switches are preferably coupled to entities (e.g., LANs, end stations, etc.) whereas backbone switches provide the interconnections between access switches.”).” slip op. at 44

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

    “We agree with Petitioner. For purposes of claim 1, which does not recite “downstream” communication of dummy traffic (unlike claims 11, 12, 23, and 24), the only modification to Figure 1 is the addition of switch 117 and server 112e—otherwise, in Petitioner’s analysis, Gai’s method operates exactly as described when a failure occurs at root port 3 of switch 114. See Pet. 69–73, 81–85; Tr. 47:20–48:2. That modification is expressly supported by Gai, which discloses the following: Rapid reconfiguration entity 234 similarly generates one or more separate multicast messages 400 for each remaining entity directly coupled to access switch 114 (i.e., entities or end stations on LANs 102–104). In each message 400, entity 234 loads SA field 414 with the address of the corresponding entity. Each of these messages are similarly forwarded by access switch 114 through the new forwarding port (i.e., port number four). In addition, entity 234 generates and transmits one or more multicast messages 400 for entities reachable through switch 114 on ports other than its root port. For example, if port number seven at switch 114 were coupled to another access switch, entity 234 would transmit multicast messages 400 carrying the source address of entities directly coupled to this additional access switch as well. Thus, at least one multicast message 400 is generated and transmitted for each entity directly coupled to or downstream of access switch 114 (relative to the root). As set forth above, upon receipt of these multicast messages 400, the other devices within network 100 update their corresponding filtering databases with the new destination ports, as necessary. Ex. 1005, col. 13, l. 50–col. 14, l. 3 (emphasis added). Gai thus expressly contemplates the addition of “another access switch” coupled to port 7 of switch 114. Switch 117 in the modified Figure 1 is such a switch. See PO Resp. 30 (Patent Owner arguing that “a [person of ordinary skill in the art] would understand that switch 117 is an access switch”); Ex. 1018, 84:14–85:9 (Dr. Olivier agreeing that switch 117 is an “access switch”). And because an “access switch” has “ports that connect to LANs and/or to other network endpoints, such as user computer systems,” and the above disclosure mentions “entities directly coupled to th[e] additional access switch,” switch 117 would be directly connected to a device like server 112e as well. See Ex. 1001, col. 1, ll. 31–33; Ex. 1005, col. 13, ll. 59–63; supra Section II.B. We credit Dr. Houh’s testimony that Gai in its written description expressly discloses the particular “variation of the topology” of Figure 1 that Petitioner asserts. See Ex. 1003 ¶ 165. Third, Patent Owner argues that Petitioner has not established that a person of ordinary skill in the art “would have had a reasonable expectation of success in modifying Gai to meet the claims.” PO Resp. 14–16 (citing Ex. 2001 ¶¶ 47–49). Patent Owner’s arguments are primarily directed to Petitioner’s asserted modification for its “1A” theory. See id. To the extent Patent Owner’s arguments apply to claim 1 and “1B,” we disagree, as Gai expressly describes the asserted modification to Figure 1 (i.e., adding an access switch connected to port 7 of switch 114). Thus, we are persuaded that a person of ordinary skill in the art would have had a reasonable expectation of success in achieving the method of claim 1 based on Gai’s full disclosure.” slip op. at 33

  Patent outcomesUS 6,917,986 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,917,986
• Qualcomm Incorporated v. Network System Technologies, LLCAll claims unpatentable
  PTAB · Jun 13, 2025 · IPR2024-00343 · APJ Charles J Boudreau · IPR · Final written decision

  Claims 1–7 are unpatentable as obvious over Rădulescu2004 and OCP; the Board did not reach the Weber-based grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “include (1) the educational level of the inventor; (2) the type of problems encountered in the art; (3) prior-art solutions to those problems; (4) the rapidity with which innovations are made; (5) the sophistication of the technology; and (6) the educational level of workers active in the field. Envtl. Designs, Ltd. v. Union Oil Co., 713 F.2d 693, 696–97 (Fed. Cir. 1983). Not all factors may exist in every case, and one or more of these or other factors may predominate in a particular case. Id. These factors are not exhaustive, but merely a guide to determining the level of ordinary skill in the art. Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). Moreover, the prior art itself may reflect an appropriate skill level. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 13

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

    “35 U.S.C. § 112 ¶ 6 (2006). “[T]he use of the word ‘means’ in a claim element creates a rebuttable presumption that § 112, para. 6 applies.” Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1348 (Fed. Cir. 2015) (en banc in relevant part); Personalized Media Commc’ns, LLC v. Int’l Trade Comm’n, 161 F.3d 696, 703–04 (Fed. Cir. 1998). “[This] presumption may be rebutted if the properly construed claim limitation itself recites sufficiently definite structure to perform the claimed function.” Kemco Sales, Inc. v. Control Papers Co., 208 F.3d 1352, 1361 (Fed. Cir. 2000).” slip op. at 16

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Term construed patent owner constructionDecided for patent owner

    “Ex. 1001, 4:46–50. This passage indicates that the interconnect can be a network on a chip and the network on a chip can include wires and buses. That does not necessarily mean that the interconnect can be just wires or buses; rather, it discloses that the interconnect can include wires and buses. In context, the disclosure regarding wires and buses does not support construing the corresponding structure broadly enough to encompass just wires and buses. The networks that constitute the corresponding structure, however, could include networks with wires and buses. Therefore, we agree with Patent Owner that the corresponding structure for the interconnect means should not include a mere bus, switch, and point-to-point wire and instead find that the corresponding structure under 35 U.S.C. § 112 ¶ 6 is a network, which the ’052 patent describes as a multi-hop interconnection between modules separated by one or more network nodes. See Ex. 1001, 2:33–37. Because this structure corresponds to the construction of “interconnect means” proposed by Patent Owner and adopted by the district courts in the TI and Qualcomm litigations (see supra Section III.C.3.b), and we do not rely in our analysis below on a recourse to “equivalents thereto” as permitted by § 112 ¶ 6, we note that our ultimate conclusions on the unpatentability of the challenged claims would be the same if § 112 ¶ 6 did not apply. iii. Conclusion For the reasons stated above, we construe “interconnect means” to cover the structure described in the Specification corresponding to the specified functions of “coupling said plurality of processing modules (M, S)” in the context of claim 6 and “coupling said plurality of processing modules (M, S)” and “enabling a connection-based communication having a set of connection properties” in the context of claims 1 and 7—i.e., a “multi-hop interconnection between modules separated by one or more network nodes”—and equivalents thereof.” slip op. at 28

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

    “standard as would be used by a district court to construe a claim in a civil action involving the validity or infringement of a patent. 37 C.F.R. § 42.100(b). Under that standard, claim terms are given their ordinary and customary meaning, as would have been understood by a person of ordinary skill in the art at the time of the invention, in light of the language of the claims, the specification, and the prosecution history of record. Id.; Phillips v. AWH Corp., 415 F.3d 1303, 1312–19 (Fed. Cir. 2005) (en banc); Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365–66 (Fed. Cir. 2012). “The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (quoting Vivid Techs., Inc. v. Am. Sci. Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 15

  Patent outcomesUS 7,594,052 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,594,052
• Xu Peicheng (Hong Kong) Optoelectronic Technology Co., Limited v. Semisilicon Technology Corp.Some claims unpatentable
  PTAB · May 14, 2025 · IPR2024-00156 · APJ Sheila F Mcshane · IPR · Final written decision

  Claims 1–3 and 8 are unpatentable over the stated obviousness grounds; claims 4–6 were not shown unpatentable because Hiroyuki does not teach the claimed terminal pins.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the Schubert Declaration, Petitioner proposes that a person of ordinary skill in the art “would have had a bachelor’s degree in electrical engineering, physics, materials science, or a related discipline, and 6 years of 1 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112–29, 125 Stat. 284 (Sept. 16, 2011), includes amendments to Section 103 that became effective on March 16, 2013. Because the challenged claims issued from an application filed before March 16, 2013, we apply pre-AIA law. See Pet. 2; Ex. 1001, codes (22), (30). 2 US 2009/0021955 A1, published January 22, 2009 (Ex. 1004, codes (10), (43)) (“Kuang”). Petitioner contends that Kuang is prior art to the ’546 patent at least under pre-AIA 35 U.S.C. § 102(b). Pet. 2. 3 US 2012/0050606 A1, published March 1, 2012 (Ex. 1005, codes (10), (43)) (“Debevec”). Petitioner asserts that “[b]ecause Debevec was filed prior to the priority date of the ’546 patent, it qualifies as prior art at least under pre-AIA 35 U.S.C. § 102(e).” Pet. 2. 4 US 6,774,584 B2, issued August 10, 2004 (Ex. 1008, codes (10), (45)) (“Lys”). Petitioner contends that Lys is prior art to the ’546 patent at least under pre-AIA 35 U.S.C. § 102(b). Pet. 2–3. 5 JP2006-228529, published August 31, 2006 (Ex. 1006, code (43)) (“Hiroyuki”). We refer herein to the certified English translation filed as Exhibit 1007. Petitioner contends that Hiroyuki is prior art to the ’546 patent at least under pre-AIA 35 U.S.C. § 102(b). Pet. 2. practical experience in designing or fabricating LED lighting systems, including controlling and driving LEDs,” or “[a]lternatively . . . would have had a master’s degree and four years of experience, or a Ph.D. degree and two years of experience.” Pet. 5 (citing Ex. 1003 ¶ 31). Patent Owner applies Petitioner’s asserted level of ordinary skill in the art. PO Resp. 7–8. For the purposes of this Decision, we adopt the assessment offered by Petitioner as it is consistent with the ’546 patent and the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 16

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

    “The parties also dispute the interpretation of the term “synchronous signals” recited in claim 1, with the parties proposing these respective constructions: Petitioner’s Proposed Patent Owner’s Proposed Construction Construction “signals that are sent to the slave “signals related to activities governed by synchronized timing” nodes to control their corresponding LED strings at the same time.”” slip op. at 20

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

    “The “context” is typically evaluated by reviewing the intrinsic record. See e.g., Regeneron, 130 F.4th at 1380–84. Here, as discussed above, the ’546 patent has multiple disclosures where a curtain lamp has a single light-emitting diode in one light-emitting diode string. See Ex. 1001, 1:33–36, 6:15–20, 6:27–40, 8:25–45. In particular, the ’546 patent similarly discloses a first curtain lamp with one LED in one light string, as well as a second curtain lamp, which provides further support for Petitioner’s proposed interpretation. Id. at 8:25–45. Although Patent Owner argues that Figures 7 and 8 disclose multiple LEDs and light strings in curtain lamps, other embodiments and claims explicitly indicate single components in a “curtain lamp.” “[T]here is a strong presumption against a claim construction that excludes a disclosed embodiment.” See In re Katz Interactive Call Processing Patent Litig., 639 F.3d 1303, 1324 (Fed. Cir. 2011). Given that certain embodiments and claim 8 disclose a curtain lamp with one light string with one LED, we decline to interpret the claim to prohibit Petitioner’s interpretation. Additionally, we do not find that Petitioner’s claim interpretation renders the claim terms nonsensical or illogical. See Becton, 616 F.3d at 1255. Patent Owner asserts otherwise, arguing that Petitioner’s interpretation is based upon a “nonsensical” or “absurd[]” argument, there is no reason to have both a master and slave control unit to operate a single LED, and the interpretation renders most of the components superfluous. See PO Sur-reply 12; PO Resp. Supp. Br. 5. As discussed above, however, although the ’546 patent does not appear to provide any explanation for why there are master and slave control units to operate a single LED, the patent nevertheless discloses that in embodiments. This situation is also distinguishable from Becton, where “unequivocal language” of the claim recited “spring means ‘connected to’ the hinged arm,” such that interpreting the spring means and the hinged arm as the same structure would have rendered the claim nonsensical. Becton, 616 F.3d at 1254–55. Becton further found that interpreting the spring means and hinged arm as the same structure would be inconsistent with descriptions of the elements in the specification. Id. Here, in contrast, the ’546 patent Specification is replete with disclosures of a curtain lamp having one light string with one LED, and claim 8 is directed to the same. Accordingly, we adopt Petitioner’s interpretation of these claim elements.” slip op. at 36

  • Strike new argumentNew argument consideredDecided for petitioner

    “Although Patent Owner argues that Petitioner’s arguments in the Reply on “light strings” and “curtain lamp” as they relate to a single LED are improper, we do not agree. As Patent Owner acknowledges, the Petition and Dr. Schubert’s original declaration stated that a “curtain lamp” is “commonly understood to be one or more light strings.” See PO Sur-reply 12; see also Pet. 8; Ex. 1003 ¶ 37. Patent Owner did not contest Petitioner’s interpretation in its Response. See PO Resp. 15. Patent Owner did, however, argue that Kuang did not teach or suggest “light strings” in any form and therefore did not teach a “curtain lamp” under Petitioner’s definition of the same. PO Resp. 15–17. A petitioner reply may respond to arguments raised in a patent owner’s response under 35 U.S.C. § 42.23(b), and here Petitioner’s argument that a light string may have a single LED is properly presented in its Reply in response to Patent Owner’s arguments. Further, Patent Owner was not only aware that Petitioner had taken the position that a “curtain lamp” could be a single “light string,” but Patent Owner also did not dispute Petitioner’s interpretation.8 Our view, therefore, is that Petitioner’s argument that a curtain lamp may be a single LED is proper because it is corollary to Petitioner’s reply arguments on light strings. That is, Petitioner’s assertion follows from the reply arguments on light strings and the unopposed interpretation of curtain lamp as a single light string. Additionally, to the extent there could be any prejudice to Patent Owner by these light string and curtain lamp arguments, Patent Owner has had opportunities to address them by supplemental briefing.” slip op. at 32

  Patent outcomesUS 8,884,546 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,884,546
• Juniper Networks, Inc. v. Monarch Networking Solutions LLCSome claims unpatentable
  PTAB · May 5, 2025 · IPR2024-00175 · APJ Norman H Beamer · IPR · Final written decision

  Claims 7, 9–11, 13, 14, 16, and 17 are unpatentable as obvious over Biswas and Kumar; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Pet. 14 (citing Ex. 1003 ¶¶ 62–64). Patent Owner does not dispute Petitioner’s proposal. PO Resp. 8–9. Petitioner’s proposal is consistent with the level of ordinary skill in the art as reflected by the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); GPAC, 57 F.3d at 1579. On this record, the level of ordinary skill is neither in dispute nor dispositive of any challenge. For purposes of this Decision, we apply Petitioner’s articulation.” slip op. at 10

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

    “Claim terms need only be construed to the extent necessary to resolve the controversy. Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017). The parties submit that no claim construction is necessary. Pet. 14; PO Resp. 15. We have not been presented with the need to construe any claim terms for this Decision. D.” slip op. at 11

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

    “We determine that Petitioner has provided sufficiently articulated reasoning with rational underpinnings for the proffered combined teachings of Biswas and Kumar. We are persuaded by Petitioner’s declarant’s testimony that one of ordinary skill would have known to use the masking techniques exemplified by Kumar to implement the disclosed operation in Biswas of edge routers providing hosts with port number ranges. Ex. 1003 ¶¶ 77, 97–101. Accordingly, we determine that Petitioner has proved by a preponderance of the evidence that one of ordinary skill in the art would have been motivated to combine Biswas and Kumar.” slip op. at 13

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

    “This disclosure is inconsistent with any suggestion that the Fangman system, when routing a telephone call to its destination, identifies the private IP address of the destination telephone by determining the port range to which the port number of the destination telephone belongs. When Fangman describes the NAPPT process, it does not indicate that port ranges are used, but rather repeatedly states that port numbers are used: The [service gateway] receives a data packet from the IP device, including a public destination IP address . . . a destination port number . . . and source information, NAPPTs the data packet, using the [public destination IP address] and the [destination port number] to identify the [IP telephone] . . . . Ex. 1024, code (57). Performing NAPPT on the data packet received from the destination may include using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to a private source IP address of the IP telephone while leaving the destination port number unchanged. Ex. 1024, 4:28–33. The SG 170 may maintain a table of semi-permanent mappings of the external IP address and ports to the internal hosts and ports. Ex. 1024, 8:49–51.” slip op. at 33

  Patent outcomesUS 8,693,369 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,693,369
• Whatfix Inc. v. Walkme Ltd.Some claims unpatentable
  PTAB · Mar 18, 2025 · IPR2023-01368 · APJ Kara L Szpondowski · IPR · Final written decision

  Claims 1–8, 12, 13, 16, 19–23, 26, 29, and 31 are unpatentable over Symons and Williams; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Petitioner proposes that a person of ordinary skill in the art (“POSITA”) “would have a bachelor’s degree in engineering or computer science and two years of experience working on NLP [natural language processing] and automation processes. Alternatively, a POSITA would have five to six years of experience working on NLP and automation processes.” Pet. 5–6 (citing Ex. 1003 ¶¶ 50–52). We adopted Petitioner’s proposal for purposes of the Decision on Institution, explaining that it appeared to be consistent with the evidence of record, including the asserted prior art and the ’664 patent. Dec. 12.” slip op. at 14

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Plain and ordinary meaningDecided for petitioner

    “We interpret claims using the same claim construction standard that would be used to construe the claims in a civil action under 35 U.S.C. § 282(b). 37 C.F.R. § 42.100(b). Under that standard, words of a claim are generally given their ordinary and customary meaning as understood by a person of ordinary skill in the art at the time of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc). However, “the specification may reveal a special definition given to a claim term by the patentee that differs from the meaning it would otherwise possess, and “[i]n such cases, the inventor’s lexicography governs.” Id. at 1316. A patentee may “choose to be his or her own lexicographer by clearly setting forth an explicit definition for a claim term that could differ in scope from that which would be afforded by its ordinary meaning.” Rexnord Corp. v. Laitram Corp., 274 F.3d 1336, 1342 (Fed. Cir. 2001). We only need to construe the claims to the extent necessary to resolve the parties’ disputes. See Realtime Data, LLC. v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019).” slip op. at 18

  • ExcludeGranted in part

    “Exhibits 2015–2017 are three comments made on the Internet in association with the Symons Article. These comments are also shown in Exhibit 2005. According to our rules, “[s]upplemental evidence is not filed at the time of the objection, but simply served, and is filed only in support of an opposition to a motion to exclude.” CTPG14 79 (citing 37 C.F.R. §§ 42.64(a), 42.64(b)(2)). Because no motion to exclude was filed by Petitioner, we agree with Petitioner that Patent Owner improperly filed Exhibits 2014–2017. However, as described above, the comments in Exhibit 2015–2017 are already part of the record in Exhibit 2005, and Petitioner has not filed a motion to expunge Exhibit 2005. Therefore, we are not aware of any harm to Petitioner by leaving these Exhibits in the record, as the information is 14 PTAB Consolidated Trial Practice Guide, November 2019 (the “CTPG”), available at: https://www.uspto.gov/sites/default/files/documents/tpgnov.pdf. already there. See Tr. 100:8–14. Moreover, retaining these Exhibits in the record will avoid confusion in the record and serve the public interest in a full and complete record. Accordingly, we will expunge only Exhibit 2018, as agreed by the parties, and waive the requirements of 37 C.F.R. § 42.64(b)(2) to the extent necessary to retain entry of Exhibits 2014–2017.” slip op. at 27

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

    “We need not determine whether Symons alone teaches this limitation, because we are persuaded that Petitioner has sufficiently shown that the combination of Symons and Williams teaches this limitation. We agree with Petitioner that, by disclosing that “chatbots can engage in natural language dialog with the caller and discern, through a series of interactions, the nature of the call[,] . . .capture information required to further handle the request . . [and] then trigger a robot, passing the required information to the robot to complete the request,” Williams teaches “determining . . . an automation process,” as recited in limitation 1[c]. See Pet. 19 (citing Ex. 1011, 3) (some emphasis omitted); see Ex. 1003 ¶ 95. We disagree with Patent Owner’s arguments that the combination is “ill-defined.” Sur-reply 8–9. Petitioner argues that the combination of Symons and Williams “results in a chatbot-RPA bot system capable of handling a user request for automated email signature generation along with other requests, such as automated generation of an electronic letterhead or an electronic invoice.” Pet. 20 (citing Ex. 1003 ¶ 98). In other words, in addition to the capability of handling the automated email signature generation (as taught in Symons), the combined chatbot-RPA bot system can handle other requests as well (as taught in Williams). Further, we agree with Petitioner that “[t]he ability to handle multiple requests would expand the capabilities and flexibilities of the chatbot-RPA bot” as well as “improv[e] costs, time, and capabilities.” Id. at 19–20 (citing Ex. 1003 ¶¶ 95, 96, 99). Both Symons and Williams support this argument. Ex. 1011, 2 (stating that RPA “support[s] repetitive, labor-intensive and transactional business processes,” that “software robots [are] an attractive way to drive operational cost reduction,” and that “[a]utomation through RPA can offer a return on investment (ROI) often ranging between 30 and 50 percent”); id. at 5 (stating that “[d]eployment of these cognitive tools promises new levels of productivity and innovation–freeing human workers to focus on higher-value activities and bringing industrial-level quality, consistency and auditability to business processes”); Ex. 1004, 2 (stating that “combining [RPA bots and chatbots] to automate processes can tremendously boost productivity in multiple organizations” and that “[RPA bots] reduce[] costs and human efforts”). Patent Owner’s argument that “[n]either Symons nor Williams suggest using a single chatbot-RPA to handle multiple requests at once in the same conversation thread” (PO Resp. 38) is not commensurate with the claim language, which does not require a single automation process (e.g., chatbot-RPA) to handle multiple inputs (e.g., multiple requests in the same conversation thread). See Reply 9–10. Regardless, however, we are not persuaded that Williams does not suggest using a single chatbot-RPA to handle multiple requests, as argued by Patent Owner. Sur-reply 9; see Ex. 1011, 2 (stating, for example, that “[t]he most common processes enabled by RPA today include back-office administrative processes and workflow within IT, finance, procurement, and human resources functions” and that “RPA enlists software robots to perform complex, nested routines that cut across multiple applications and interact with these systems”); id. at 3 (“Through several scripted questions, the virtual agent can surmise that the supplier is asking for status on their payment and, thus, trigger an RPA robot to access the appropriate enterprise resource planning (ERP) backend system, validate the caller’s details, retrieve necessary information, and provide status back in real-time to the supplier.”).” slip op. at 35

  Patent outcomesUS 10,819,664 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,819,664
• Peloton Interactive, Inc. v. NEC CorporationAll claims unpatentable
  PTAB · Feb 5, 2025 · IPR2023-01241 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 10–13, 19, 21, 23, and 33 are unpatentable as obvious over Ueda, the SIP Standard, and the SDP Standard, with Cohee added for claims 11, 13, 19, and 23.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “Petitioner argues that a person of ordinary skill in the art “would have had a bachelor’s degree, or equivalent, in electrical engineering, computer science, or a related field, and 2–3 years of experience researching, designing, or developing content delivery systems and related hardware, software, and firmware, or equivalent experience.” Pet. 4 (citing Ex. 1008 ¶¶ 36–40). Patent Owner does not dispute this. See PO Resp. 3 (citing Ex. 2001 ¶ 22). Because it is uncontested, supported by testimonial evidence, and appears consistent with the types of problems and solutions in the ’427 patent, we adopt the above articulation of the level of ordinary skill for this decision.” slip op. at 12

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

    “We agree with Patent Owner that the term should be construed according to its ordinary and customary meaning, and that we need not construe the term explicitly because the meaning of the term is not relevant to the contested issues in the proceeding. 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 13

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference is prior artDecided for petitioner

    “Having considered all the evidence of record relating to Mr. Taniguchi’s activities during the relevant time frame, we find that Patent Owner has not produced sufficient corroborating evidence to show that Mr. Taniguchi’s work on reducing to practice the claimed invention was reasonably continuous during the critical period between September 19, 2008 (the filing date of Ueda), and November 18, 2008 (the filing date of the Japanese patent application). Although there is corroborating evidence of diligence beginning on November 6, 2008, when Mr. Taniguchi transmitted a draft application to the Baba law firm, there is no evidence of any diligence prior to that date, other than Mr. Taniguchi’s own testimony. We do not agree with Patent Owner that the evidence of Mr. Taniguchi’s other activities for NEC, or research relating to IPTV, corroborate Mr. Taniguchi’s reduction to practice of the claimed invention. Although these activities may have something to do with the general subject matter of IPTV, Patent Owner has not shown any nexus between these activities and the challenged claims. See Naber, 567 F.2d at 385 (“It is well settled that, to satisfy the ‘reasonable diligence’ requirement . . . , the work relied on must ordinarily be directly related to reduction to practice of the invention . . . in issue.” (citing cases)). Although Mr. Taniguchi doubtlessly spent substantial time preparing the application he completed on November 6, 2008 (see Ex. 2017), there is no corroborating evidence that this work was reasonably continuous during the critical period. As far as the corroborating evidence attests, Mr. Taniguchi could have done no work on the draft until early November, or he could have worked on the draft briefly in August and put it aside until early November. Considering all the evidence as to Mr. Taniguchi’s activities, we find that Patent Owner has not met its burden of producing corroborating evidence that the named inventors of the ’427 patent exercised reasonably continuous diligence during the critical period when Ueda was filed until the constructive reduction to practice that occurred on November 18, 2008. Therefore, we determine, by a preponderance of the evidence, that Ueda is prior art to the challenged claims.” slip op. at 24

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

    “In general, we disagree with Patent Owner that, in showing a reason to incorporate the SIP Standard’s teachings about proxy servers, Petitioner must necessarily show that Ueda’s system was deficient or inferior. A patent challenger “does not need to show that there was a known problem with the prior art system in order to articulate the required rational underpinning for the proposed combination.” Unwired Planet, LLC v. Google Inc., 841 F.3d 995, 1002–03 (Fed. Cir. 2016). Also, “when a patent claims a structure already known in the prior art that is altered by the mere substitution of one element for another known in the field, the combination must do more than yield a predictable result.” KSR, 550 U.S. at 416. For this reason and the specific reasons discussed below, we find Patent Owner’s arguments unpersuasive. The evidence of record suggests that it would have been within the ordinary skill in the art to modify Ueda’s system by replacing direct communication between content-providing device 150 and servers 191 or 192 with an indirect connection in the form of proxy servers using well-known, predictable techniques as described in the SIP Standard.” slip op. at 33

  Patent outcomesUS 9,769,427 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,769,427
• Microsoft Corporation v. Reald Spark, LLCAll claims unpatentable
  PTAB · Nov 19, 2024 · IPR2023-01046 · APJ Jean R Homere · IPR · Final written decision

  Claims 1–14 and 16–19 are unpatentable: claims 1–3, 5, 10, 12–14, and 18 as anticipated by Ganin; the remaining claims as obvious over the stated combinations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not contest Petitioner’s proffered definition of the level of ordinary skill in the art, but offers a definition of its own. PO Resp. 8. Patent Owner contends that a person having ordinary skill in the art at the time of the invention “would have had at least a bachelor’s or master’s degree in electrical engineering, computer engineering, electrical and computer engineering, computer science, or similar educational background; or equivalent on-the-job training, including approximately two to three years of experience in machine learning and/or pattern recognition.” Id. (citing Ex. 2008 ¶ 22). Patent Owner asserts that the “level of skill is approximate and more experience would compensate for less formal education and vice versa.” Id. We note that the differences between the parties’ descriptions are immaterial and find Petitioner’s description to be consistent with the problems and solutions disclosed in the ’985 patent and prior art of record, and adopt it as our own for purposes of this Decision, albeit without the two instances of “at least,” which introduce ambiguity. See, e.g., In re GPAC Inc., 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 15

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

    “Petitioner contends that it “applied plain and ordinary meanings of all terms and no express constructions are required here.” Pet. 5. Patent Owner agrees with Petitioner that there are no claim terms that require construction for purposes of the Board’s final decision. PO. Resp. 8–9. We therefore determine that we do not need to expressly construe any term for purposes of this Decision. See Realtime Data, 912 F.3d at 1375.” slip op. at 17

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Chalom’s large RFC with Aslan’s teacher-student MLA pair would have rendered the ensuing system more complex, and thereby inefficient. As correctly noted by Petitioner, Chalom indicates that the RFC can be embodied in a mobile computing device. Id. at 15 (citing Ex. 1005, 22:33– 37, 19:65–20:6). And Dr. Karam persuasively explains that using the teacher model to train the student model is more efficient because the teacher’s knowledge allows the student model to converge faster. Id. at 17 (citing Ex. 2009, 178:14–24). Accordingly, we find that a POSITA would have found sufficient motivation to replace Chalom’s RFC with Aslan’s teacher-student models to enhance the efficiency of the MLA pair in a mobile computing environment. On this record, we agree with Petitioner that the proposed combination of Chalom and Aslan would predictably result in the teacher MLA generating motion vector fields for user gaze correction (i.e., first reference or editing instructions) that are passed to the student MLA, which subsequently generates motion vector fields (i.e., second reference or editing instructions) for further refining the received first reference data. Id. at 58. Consequently, we reiterate that because the proposed combination involves known elements performing their ordinary functions to produce a predictable result, a POSITA would have appreciated that the proposed combination is proper.4 After considering Patent Owner’s arguments, we find Petitioner has shown by a preponderance of the evidence that the proposed combination of Chalom and Aslan is sufficiently supported by the requisite motivation to teach limitations 1[D] and 1[E].” slip op. at 40

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

    “Because Chalom explicitly indicates that its RFC can be trained using any suitable techniques(s) including compressing the classifier, we agree with Petitioner that a POSITA would have looked to Aslan’s teacher-student architecture that proposes compressing large models such as Chalom’s RFC into smaller models so they can be more readily deployed on computing devices with limited resources. Pet. Reply 11–12. As correctly noted by Petitioner, the experts of the parties agree that both Aslan and Chalom involve classifiers. More particularly, as acknowledged by Patent Owner’s representative during the hearing, compression is desirable for Chalom’s RFC. See Tr. 56:21–57:4. Accordingly, we agree with Petitioner that a POSITA would have looked to a similar compression operation of classifiers in Aslan for training a more compact MLA at runtime or offline. Pet. Reply 11–12. For these same reasons, we find unavailing Patent Owner’s argument that Chalom and Aslan are directed to different objectives or techniques. Further, we do not agree with Patent Owner’s argument that replacing Chalom’s large RFC with Aslan’s teacher-student MLA pair would have rendered the ensuing system more complex, and thereby inefficient. As correctly noted by Petitioner, Chalom indicates that the RFC can be embodied in a mobile computing device. Id. at 15 (citing Ex. 1005, 22:33– 37, 19:65–20:6). And Dr. Karam persuasively explains that using the teacher model to train the student model is more efficient because the teacher’s knowledge allows the student model to converge faster. Id. at 17 (citing Ex. 2009, 178:14–24). Accordingly, we find that a POSITA would have found sufficient” slip op. at 39

  Patent outcomesUS 10,740,985 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Graham
  Patents in suitUS 10,740,985
• Zoho Corporation / Zoho Corporation PVT., Ltd. v. Meetrix IP, LLCAll claims unpatentable
  PTAB · Jul 16, 2024 · IPR2023-00382 · APJ Karl D Easthom · IPR · Final written decision

  Claims 19–29 are unpatentable as obvious: claims 19–21 and 25–27 over Knappe, Elliott, VPN Textbook, and Hendricks; claims 22–24, 28, and 29 with Drell added.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner “believes a POSITA would have a bachelor’s degree in electrical engineering, computer science, or equivalent with two years or more of experience in computing systems development.” PO Resp. 12 (citing Ex. 2001 ¶ 3). The two proposals largely overlap. Based on a review of the record, we adopt Petitioner’s proposed level of ordinary skill in the art because it is consistent with the evidence of record, including the asserted prior art and ’612 patent specification, except that we delete the qualifier “or more” in the phrase “three or more years” to eliminate vagueness as to the stated amount of professional experience. However, even if we were to adopt Patent Owner’s proposal, we agree with the parties that the outcome would be the same. See Reply 2 (Petitioner arguing that “under either definition the result is the same”); Tr. 49:11–14 (Patent Owner contending that as to defining a “person of ordinary skill in the art,” he “can’t point to a material difference that would change the outcome of this” trial).” slip op. at 8

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

    “In any event, even if Exhibit 2002 includes construction of a claim term at issue here, we determine below that Petitioner shows that the challenged claims would have been obvious under constructions consistent to any such terms proposed by Patent Owner.7 Moreover, as Petitioner argues, “Patent Owner arguments do not actually rely on any of these claim constructions,” and “only a handful of the listed terms actually appear in the claims of the ’612 patent.” Reply 2. In its Sur-reply, Patent Owner does not direct attention to any dispositive issue that turns on the district court claim construction. Sur-reply 2. 7 As discussed below, Patent Owner presents an argument related to the district court claim construction of “VPN ‘tunnel.”’ See Ex. 2002, 13. explicit construction for any claim term is not necessary. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (stating that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 9

  • BurdenUnpatentable

    “reasons supported by the record as summarized above. See Pet. 35–37; Reply 10–13. For example, summarizing the Petition’s showing, Petitioner contends that “[i]t would have been obvious to a POSITA, in view of Elliott’s teachings, to implement Knappe’s transmission of various types of data as collaboration data, because this type of collaboration data would allow a greater variety of information among the participants, improving the experience and enhancing the effectiveness of collaboration in a variety of contexts.” Reply 13 (citing Ex. 1003 ¶ 348); see also Pet. 35–36 (similar showing (citing Ex. 1006, 3:26–29; 5:31–33; Ex. 1003 ¶¶ 342–361, 409)). Therefore, Petitioner also provides articulated rationale with factual underpinnings to show persuasively that it would have been obvious to employ distinct collaboration data (distinct from audio and video data) in Knappe’s system based on the combined teachings of Knappe and Elliott to supplement the audio and video data during a conference. Based on the summary outlined above, Petitioner also shows persuasively that this collaboration data would have improved Knappe’s similar conferencing system, summarizing as follows: [T]he combination of Knappe and Elliott is merely the ordinary use of common techniques (transmitting collaboration web browsing data, application sharing data, and collaboration data per the T.120 standard as Elliott teaches) to improve the similar conferencing system of Knappe in the same way by allowing for enhanced collaboration among participants. Reply 14 (citing Ex. 1003 ¶ 352). Based on the record and foregoing discussion, we find that Petitioner articulates persuasive rationale supported by the record to show that the combined teachings of Knappe and Elliott satisfy steps 19.1.1 and 19.2.1.” slip op. at 32

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

    “reasons supported by the record as summarized above. See Pet. 35–37; Reply 10–13. For example, summarizing the Petition’s showing, Petitioner contends that “[i]t would have been obvious to a POSITA, in view of Elliott’s teachings, to implement Knappe’s transmission of various types of data as collaboration data, because this type of collaboration data would allow a greater variety of information among the participants, improving the experience and enhancing the effectiveness of collaboration in a variety of contexts.” Reply 13 (citing Ex. 1003 ¶ 348); see also Pet. 35–36 (similar showing (citing Ex. 1006, 3:26–29; 5:31–33; Ex. 1003 ¶¶ 342–361, 409)). Therefore, Petitioner also provides articulated rationale with factual underpinnings to show persuasively that it would have been obvious to employ distinct collaboration data (distinct from audio and video data) in Knappe’s system based on the combined teachings of Knappe and Elliott to supplement the audio and video data during a conference. Based on the summary outlined above, Petitioner also shows persuasively that this collaboration data would have improved Knappe’s similar conferencing system, summarizing as follows: [T]he combination of Knappe and Elliott is merely the ordinary use of common techniques (transmitting collaboration web browsing data, application sharing data, and collaboration data per the T.120 standard as Elliott teaches) to improve the similar conferencing system of Knappe in the same way by allowing for enhanced collaboration among participants. Reply 14 (citing Ex. 1003 ¶ 352). Based on the record and foregoing discussion, we find that Petitioner articulates persuasive rationale supported by the record to show that the combined teachings of Knappe and Elliott satisfy steps 19.1.1 and 19.2.1.” slip op. at 32

  Patent outcomesUS 9,843,612 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,843,612

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.