Juniper Networks, Inc. v. Correct Transmission, LLC

Court of Appeals for the Federal Circuit·Decided July 24, 2024·No. 23-1046·Unpublished

Opinion

NOTE: This disposition is nonprecedential.

United States Court of Appeals for the Federal Circuit

JUNIPER NETWORKS, INC.,

Appellant

v.

CORRECT TRANSMISSION, LLC, Appellee

2023-1046, 2023-1236

Appeals from the United States Patent and Trademark Office, Patent Trial and Appeal Board in Nos. IPR2021- 00469, IPR2021-00682.

Decided: July 24, 2024

R. WILLIAM SIGLER, Fisch Sigler, LLP, Washington, DC, argued for appellant. Also represented by MATTHEW R. BENNER, ALAN M. FISCH, JEFFREY MATTHEW SALTMAN.

JEFFREY A. STEPHENS, Carter Arnett Bennett & Perez, Dallas, TX, argued for appellee. Also represented by JOSHUA BENNETT, BRADLEY D. LIDDLE, MICHAEL CLAYTON POMEROY.

2 JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC

Before DYK, REYNA, and STARK, Circuit Judges.

DYK, Circuit Judge.

Juniper Networks, Inc. (“Juniper”), appeals the Patent Trial and Appeal Board’s (the “Board”) decisions in two inter partes review proceedings in which the Board declined to find claims of U.S. Patent No. 7,283,465 (the “’465 patent ”) (IPR-2021-00682) and U.S. Patent No. 7,983,150 (the “’150 patent”) (IPR-2021-00469) unpatentable as obvious. We affirm.

BACKGROUND

Correct Transmission, LLC, (“Correct Transmission”)

owns the ’465 patent and the ’150 patent, both of which pertain to improvements in communications networks. Specifically, both patents provide mechanisms to protect against failures in communications networks.

I. IPR-2021-00682

The ’465 patent concerns protecting against network failures in virtual private networks (“VPN”), including virtual private local area network services (“VPLS”). A preferred embodiment of the network is shown in Fig. 1 of the patent, reproduced here:

JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC 3

J.A. 103 (Fig. 1). For every primary core node (i.e., data communication device) in the network, the patent describes having “one or more standby core nodes,” where “[e]ach standby core node has the same topological image in the network (i.e., the same connections) as a corresponding primary core node which it protects.” J.A. 107, col. 4, ll. 60–63. “[I]f the primary core node fails, the remaining nodes in the network simply redirect all connections from the failed primary core node to the corresponding standby core node.” Id., col. 4, ll. 64–66. 1 The specification explains that the forwarding tables (i.e., the databases of known addresses for each node) of the primary and standby nodes can be synchronized regularly using “[a] simple communications protocol” to keep the forwarding table of the standby node updated with all the

1 “Every node in a VPLS acts as a virtual bridge,”

which has endpoints or “virtual ports” for the different connections in the VPLS. J.A. 107, col. 3, ll. 19–21. The primary core nodes are thus associated with the primary virtual bridges and the standby core nodes are associated with backup virtual bridges.

4 JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC

addresses in the primary node. J.A. 109, col. 8, ll. 63–67. This way, if the primary core node were to fail, the standby core node would know all the same addresses as the primary core node, except those learned by the primary core node after the last update. Because the standby core nodes have the same connections as their corresponding primary core nodes, the other nodes in the network may seamlessly connect to it without there being a change in the network topology.

Independent claim 1 is representative of the relevant claims in the ’465 patent.

1. A data communication network, comprising:

a plurality of primary virtual bridges, interconnected by primary virtual connections so as to transmit and receive data packets over the network to and from edge devices connected thereto; and a plurality of backup virtual bridges, each such backup virtual bridge being paired with a corresponding one of the primary virtual bridges and connected by secondary virtual connections to the other primary virtual bridges, wherein the primary virtual connections define a respective primary topology image for each of the primary virtual bridges, and wherein each of the backup virtual bridges is connected to the other primary virtual bridges by secondary virtual connections that are identical to the primary virtual connections of the corresponding one of the primary virtual bridges, thus defining a respective secondary topology image that is identical to the respective primary topology

JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC 5

image of the corresponding one of the primary virtual bridges, and wherein each of the primary and backup virtual bridges is adapted to maintain a respective forwarding table, and to forward the data packets in accordance with entries in the respective forwarding table, and wherein each of the backup virtual bridges is adapted to periodically synchronize its forwarding table by copying contents of the forwarding table of the corresponding one of the primary virtual bridges with which it is paired, whereby upon a failure of the corresponding one of the primary virtual bridges, each of the backup virtual bridge forwards and receives the data packets over the network via the secondary virtual connections, in accordance with the synchronized forwarding table, in place of the corresponding one of the primary virtual bridges.

J.A. 111, col. 11, l. 35 – col. 12, l. 3 (emphasis added).

Juniper argued that claims 1–7, 9, 12–16, 27, and 28 of the ’465 patent were unpatentable as obvious over two combinations of prior art: (1) U.S. Patent No. 7,269,132 (“Casey ”) and U.S. Patent No. 7,430,735 (“Balakrishnan”) and (2) U.S. Patent No. 7,209,435 (“Kuo”) and Balakrishnan. Juniper contended that Kuo and Casey, individually, recited every limitation in claim 1, except the limitation of periodically synchronizing the forwarding tables between the primary and backup virtual bridges. Juniper argued that “such periodic synchronization would have been obvious to [the skilled artisan] in view of Balakrishnan’s teachings ” of periodically synchronizing forwarding tables or “in 6 JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC

conjunction with what was generally known in the art.” J.A. 61 (alteration in original); see also J.A. 81–82.

The Board determined that the prior art disclosed the patented features, and that Juniper had provided evidence of a motivation to combine the features. The parties, however , apparently only disputed whether there was a reasonable expectation of success. In that respect, the Board concluded that Juniper had not shown “a reasonable expectation of success in modifying [Casey or] Kuo [with Balakrishnan ] to periodically synchronize forwarding tables.” J.A. 78; see also J.A. 84.

II. IPR-2021-00469

The ’150 patent, like the ’465 patent, relates to communications networks. The ’150 patent specifically pertains to methods and systems for communicating over a bi-directional ring network that includes a VPLS. In a bi-directional ring network, individual nodes (i.e., devices) are organized in a ring, where data can be transferred between any pair of connected nodes in either direction around the ring. Bi-directional ring networks were known in the prior art, but the prior art did not disclose pairing bi-directional ring networks with VPLS. The patent claims that combination , as illustrated in Figure 1 of the patent, reproduced here:

JUNIPER NETWORKS, INC. v. CORRECT TRANSMISSION, LLC 7

Free access — add to your briefcase to read the full text and ask questions with AI

Juniper Networks, Inc. v. Correct Transmission, LLC, (Fed. Cir. 2024).

Juniper Networks, Inc. v. Correct Transmission, LLC (Juniper Networks, Inc. v. Correct Transmission, LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

KSR International Co. v. Teleflex Inc.
550 U.S. 398 (Supreme Court, 2007)
In Re Applied Materials, Inc.
692 F.3d 1289 (Federal Circuit, 2012)
Merck & Cie v. Gnosis S.P.A.
808 F.3d 829 (Federal Circuit, 2015)
Elbit Systems of America, LLC v. Thales Visionix, Inc.
881 F.3d 1354 (Federal Circuit, 2018)
Pfizer, Inc. v. Apotex, Inc.
480 F.3d 1348 (Federal Circuit, 2007)
Elekta Limited v. Zap Surgical Systems, Inc.
81 F.4th 1368 (Federal Circuit, 2023)