Lucent Technologies, Inc. v. Newbridge Networks Corp.

168 F. Supp. 2d 181, 2001 U.S. Dist. LEXIS 23042, 2001 WL 1230763
District Court, D. Delaware·Decided September 21, 2001·No. 97-347-JJF·Published·Cited by 12 cases

Opinion

OPINION

FARNAN, District Judge.

Pending before the Court in this patent infringement action is a Motion For Judgment As A Matter Of Law 1 (D.I. 616) filed by Plaintiff, Lucent Technologies, Inc. (“Lucent”) and a Renewed Motion For Judgment As A Matter Of Law At The Close Of The Evidence (D.I.618) and a Motion For A New Trial On Certain Issues (D.I.617) filed by Defendants, Newbridge Networks Corporation and Newbridge Networks, Inc. (collectively “Newbridge”). 2 By its Motion For Judgment As A Matter Of Law, Lucent requests the Court to enter a judgment of infringement against Newbridge on Claims 1 and 4 of U.S. Patent No. 4,750,-136.

By its Renewed Motion For Judgment As A Matter Of Law, Newbridge requests the Court to enter a judgment of non-infringement as a matter of law with regard to all five of the patents-in-suit. Specifically, Newbridge contends that Lucent failed to establish infringement by a preponderance of the evidence, or in the alternative, that several defenses preclude a finding of infringement against New-bridge. Alternatively, Newbridge seeks a new trial on the questions of infringement and damages, as well as on certain of its defenses, including the validity of the patents and the existence of an implied license to practice the patents. (D.I.617).

For the reasons set forth below, the Court will deny Lucent’s Motion For Judgment As A Matter Of Law, grant in part and deny in part Newbridge’s Renewed Motion For Judgment As A Matter Of Law, and deny Newbridge’s Motion For A New Trial On Certain Issues.

BACKGROUND

1. Procedural Background

Plaintiff Lucent Technologies, Inc. (“Lucent”) filed the instant action against Defendants Newbridge Networks Corporation and Newbridge Networks, Inc. (collectively “Newbridge”) on June 24, 1997 (D.I.l), initially alleging infringement of four patents: (1) U.S. Patent No. 4,769,-810 (the “Eckberg ’810 patent”); (2) U.S. Patent No. 4,769,811 (the “Eckberg ’811 patent”); (3) U.S. Patent No. 4,979,174 (the “Cheng ’174 Patent”); and (4) U.S. Patent No. 4,437,087 (the “Petr ’087 Patent”). On January 13, 1998, Lucent amended its Complaint to add a claim of infringement under a fifth patent, U.S. Patent No. 4,750,136 (the “Arpin ’136 Patent”). (D.I.25, 30).

A three week jury trial was held on all issues presented by the parties, except *189 certain equitable defenses. The jury returned a verdict in favor of Lucent on all issues, except infringement of Claims 1 and 4 of the Arpin patent. Following the trial, the parties filed a stipulation resolving the outstanding equitable issues. (D.I. 683). Accordingly, the only issues remaining for the Court’s consideration are those raised by the parties’ post-trial motions.

II. Technological Background

The patents at issue in this action relate generally to data networking. (D.I.551).

A. Eckberg ’810 Patent and Eck-berg ’811 Patent

The Eckberg ’810 and ’811 patents disclose methods and apparatus for controlling congestion in a packet-switching network. In an end station of a packet-switched network, a data message is broken into shorter pieces called packets, which are then individually transmitted by the end station into the network. Each packet includes a header. The header contains information identifying the destination of the packet, or in some implementations, the connection to which the patent belongs. The nodes of the packet-switched network use the information in the header to route the packet through the network to the intended destination end station. At the destination end station, the packets are reassembled into the original message. (D.I. 551 at 14-15.)

When several users attempt to utilize a network at the same time, congestion can occur. Congestion occurs when a network component, or a portion of a network component, is required to process more packets than it can handle. In addition to long delays in data transmission, congestion can also result in packet loss. As described in the Eckberg patents:

A principal area of packet congestion is in buffers, or queues, in each node, particularly where the buffers become unavailable to store incoming packets. Yet the buffer requirement is closely related to the utilization of processor real time and/or link bandwidth. When the processor real time is exhausting, or when the link bandwidth is not sufficient to handle the packet traffic, queues within the switching node will build up causing a long delay. Finally packet buffers will be exhausted, resulting in the dropping of packets.

(’810 patent, col. 2, 11. 26-35; ’811 patent, col. 2, 11. 25-34). Congestion and the resulting loss of packets, can be prevented and controlled by allocating bandwidth to users’ connections and permitting new connections only when bandwidth is available. Bandwith is the amount of data that can be sent per unit of time. To allocate band-with appropriately in this manner, the network must provide a means for users to select their bandwith needs. Once the network understands the user’s needs, the network creates the appropriate parameters for the user and enforces those parameters for the user. The agreement between the user and the network concerning the user’s bandwith needs is called a traffic contract. Once a traffic contract is established between the user and the network, packets that are transmitted at a rate in excess of the agreed parameters are automatically discarded at the network’s entry point.

Because traffic on the network varies at times, the automatic discarding of packets that exceed a user’s allocation is not efficient. Specifically, there may be times that the network could have handled the excess traffic instead of dropping those excess packets. The Eckberg ’810 and ’811 patents teach a traffic enforcement mechanism that allows excess packets to be marked, instead of automatically discarded. By marking excess patents, *190 the network can decide whether to discard marked excess packets during periods of congestion, or to allow those marked packets to proceed during periods of relative quiet. Generally speaking, the claims of the ’810 patent are directed toward marking excess packets, and the claims of the ’811 patent are directed toward dropping the marked packets during periods of network congestion. (D.I. 551 at 16-18.)

B. Cheng ’17lp Patent

The Cheng ’174 Patent teaches a method of handling random and bursty errors in a data transmission system. A random error is typically caused by noise and generally results in a single bit error. A bursty error is usually more serious and results in multiple bit errors. When a random or bursty error occurs in the header of a packet, that packet may be delivered to an incorrect destination address. (Cheng, col.l, 11.11-23).

Although the prior art in this field taught various techniques for dealing with these types of error, the prior art was not adequate in packet-switching systems involving high transmission speeds.

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

Lucent Technologies, Inc. v. Newbridge Networks Corp., 168 F. Supp. 2d 181, 2001 U.S. Dist. LEXIS 23042, 2001 WL 1230763 (D. Del. 2001).

168 F. Supp. 2d 181 (Lucent Technologies, Inc. v. Newbridge Networks Corp.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Green Mountain Glass LLC v. Saint-Gobain Containers, Inc.
300 F. Supp. 3d 610 (D. Delaware, 2018)
Cif Licensing, LLC v. Agere Systems Inc.
727 F. Supp. 2d 337 (D. Delaware, 2010)
Inline Connection Corp. v. Earthlink, Inc.
684 F. Supp. 2d 496 (D. Delaware, 2010)
Boston Scientific Scimed, Inc. v. Cordis Corp.
434 F. Supp. 2d 308 (D. Delaware, 2006)
Lucent Technologies, Inc. v. Extreme Networks, Inc.
367 F. Supp. 2d 649 (D. Delaware, 2005)
Genzyme Corp. v. ATRIUM MEDICAL CORP.
315 F. Supp. 2d 552 (D. Delaware, 2004)
Air Turbine Technology, Inc. v. Atlas Copco AB
295 F. Supp. 2d 1334 (S.D. Florida, 2003)