Fujitsu Ltd. v. Tellabs Operations, Inc.

782 F. Supp. 2d 635, 2011 WL 1303358, 2011 U.S. Dist. LEXIS 35286
CourtDistrict Court, N.D. Illinois
DecidedMarch 31, 2011
Docket08 C 3379, 09 C 4530
StatusPublished
Cited by2 cases

This text of 782 F. Supp. 2d 635 (Fujitsu Ltd. v. Tellabs Operations, Inc.) is published on Counsel Stack Legal Research, covering District Court, N.D. Illinois primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Fujitsu Ltd. v. Tellabs Operations, Inc., 782 F. Supp. 2d 635, 2011 WL 1303358, 2011 U.S. Dist. LEXIS 35286 (N.D. Ill. 2011).

Opinion

MEMORANDUM OPINION AND ORDER

JAMES F. HOLDERMAN, Chief Judge.

On January 29, 2008, Fujitsu Limited filed a complaint against Tellabs, Inc. and Tellabs Operations, Inc. in the United States District Court for the Eastern Dis *637 trict of Texas (“Texas Action”) alleging infringement of U.S. Patent Nos. 5,526,163 (“'163 Patent”); 5,521,737 (“'737 Patent”); 5,386,418 (“'418 Patent”); and 6,487,686 (“'686 Patent”). 1 (Case No. 09-4530, Dkt. No. 1, Fujitsu’s Compl. ¶¶ 1, 12-35.) Tel-labs Operations, Inc. then filed suit against Fujitsu Limited and Fujitsu Network Communications, Inc. (collectively “Fujitsu”) in the United States District Court for the Northern District of Illinois (“Illinois Action”) on June 11, 2008, alleging infringement of U.S. Patent No. 7,369,772 (“'772 Patent”). (Case No. 08-3379, Dkt. No. 1, Tellabs’s Compl. ¶ 1.) Both Fujitsu Limited and Fujitsu Network Communications, Inc. filed their amended answers, affirmative defenses, and counterclaims in the Illinois Action on April 1, 2009. (Dkt. Nos. 119,120.) In its counterclaims, Fujitsu Limited alleged that Tellabs Operations, Inc., Tellabs, Inc., and Tellabs North America (collectively “Tellabs”) infringed two additional patents assigned to Fujitsu Limited: U.S. Patent Nos. 7,227,681 (“'681 Patent”) and 5,533,006 (“'006 Patent”). (Dkt. No. 119.)

On May 13, 2009, 2009 WL 1329153, this court issued its preliminary claim constructions of certain disputed claim terms in the '772, '681, and '006 Patents. The Texas Action subsequently was transferred to the Northern District of Illinois on July 29, 2009, and the two cases were consolidated for purposes of discovery. (Case No. 08-3379, Dkt. No. 202.) After the cases were consolidated, this court held a technology tutorial related to the general technology underlying the six patents-in-suit, including the '006 Patent.

The parties identified additional claim terms for the court to construe and filed briefs related to those proposed constructions. Tellabs also filed two motions for summary judgment: Tellabs’s “Motion for Summary Judgment of Invalidity Based on Indefiniteness of All Asserted Claims (1 and 6-9) of U.S. Patent No. 5,386,418” (Case No. 09-4530, Dkt. No. 165) and its “Motion for Summary Judgment of Invalidity Based on Indefiniteness of All Claims of U.S. Patent 5,533,006” (Case No. 08-3379, Dkt. No. 305). Fujitsu then filed its “Motion for Summary Judgment for Judicial Correction of ‘And’ to ‘A’ in Claim 1 of U.S. Patent 5,386,418” (Case No. 09-4530, Dkt. No. 202). On November 30 and December 1, 2, 3, and 7, 2010, the court held a Markman hearing, during which the parties’ counsel addressed the respective claim construction positions as well as the pending motions for summary judgment.

For the reasons explained below, Tel-labs’s “Motion for Summary Judgment of Invalidity Based on Indefiniteness of All Claims of U.S. Patent 5,533,006” (Case No. 08-3379, Dkt. No. 305), is granted. In a separate opinion issue today, this court has denied Tellabs’s “Motion for Summary Judgment of Invalidity Based on Indefiniteness of All Asserted Claims (1 and 6-9) of U.S. Patent No. 5,386,418,” and granted Fujitsu’s “Motion for Summary Judgment for Judicial Correction of ‘And’ to ‘A’ in Claim 1 of U.S. Patent 5,386,418.” The claim constructions for the '418, '163, '737, '681, and '772 Patents remain under advisement.

BACKGROUND

I. '006 Patent

The application for the '006 Patent was filed with the U.S. Patent and Trademark Office (“PTO”) on February 14, 1994, and claims priority from a related foreign application filed on September 13, 1993. The patent issued to Fujitsu Limited on July 2, 1996, and is titled “Control System for a *638 Ring Type Network System.” The '006 Patent discloses a method for arranging a synchronous optical network, i.e., a SON-ET network, that allows the network to transmit data to users despite a problem in the network. (See '006 Patent, col. 1 11.5— 15; col. 211.45-61.)

In a SONET network, nodes drop and pass-through signals to other nodes within the network. (Id. at col. 1 11.13-45.) Prior art nodes in the SONET network would transmit data on a first optical fiber and also send a redundant copy of that data on a second optical fiber. (See 2/23/10 Tutorial Hr’g Tr. 352:20-353:14 (“So node C is receiving, in principle, two copies of the same signal, and the point is to select one.”).) If the first optical fiber is cut or otherwise interrupted, an alarm signal (“AI signal”) is generated. ('006 Patent, col. 1 1.60-col. 2 1.4.) The controlling unit for the node receiving the data detects the AI signal and “switches the connection of the reception path R to the normally functioning side ... opposite to the side ... from which the AI signal is received.” (Id. at col. 1 11.60-64.) Consequently, despite a failure in the network, a data recipient can still receive the data from the second optical fiber carrying the redundant data. (Id. at col. 211.2-4.)

SONET networks use time division multiplexing (“TDM”) to place multiple data paths on a single optical fiber. (2/23/10 Tutorial Hr’g Tr. 313:25-316:18.) In the SONET network, the TDM multiplexer organizes customer data into frames; each frame is a matrix having exactly 810 elements arranged in 90 columns and 9 rows. (Id. at 315:11-25; 330:17-22.) The first three columns of each SONET frame contain “overhead” which includes “framing bytes” used to manage the network. (Id. at 329:18-25); Fujitsu’s Tutorial Slides at 15-18 (attached as Ex. C-l to Case No. 08-3379, Dkt. No. 327 (“Fujitsu’s Opp.”).) The remaining 87 columns are referred to as the “synchronous payload envelop” and consist of an additional column of overhead (“path overhead”) and up to 86 columns of data for the customer. (2/23/10 Tutorial Hr’g Tr. 332:24-333:2.)

As was known in the prior art, human technicians program the nodes in the SONET network to perform cross connections to forward incoming signals to the correct outputs. (Id. at 353:24-354:16.) For those paths in the network that are intentionally not being used to transmit customer data, the node transmits an unequipped code signal, i.e., SONET’s standardized UNEQ signal, to indicate that the path is unused. ('006 Patent, col. 2 11.5-8.) Based on SONET standards, the UNEQ signal is always contained in the C2 byte of the frame, which is the third byte of the path overhead. (2/23/10 Tutorial Hr’g Tr. 333:2-11.) An UNEQ signal is transmitted when the C2 byte contains the value “00000000.” (Id.)

Human technicians can incorrectly program the cross connections in the node to designate a certain path as being intentionally unused even though the path actually is carrying customer data. (Id. at 354:17-24; '006 Patent, col. 2 11.15-27.) In that situation, the downstream .node receives the UNEQ signal and treats the path as an intentionally unused path, forwarding the UNEQ signal but not any customer data carried on the path. ('006 Patent, col. 2 11.15-27.) The receiving node, therefore, does not receive the data. (Id.)

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

Related

Fujitsu Ltd. v. TELLABS OPERATIONS, INC.
821 F. Supp. 2d 1009 (N.D. Illinois, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
782 F. Supp. 2d 635, 2011 WL 1303358, 2011 U.S. Dist. LEXIS 35286, Counsel Stack Legal Research, https://law.counselstack.com/opinion/fujitsu-ltd-v-tellabs-operations-inc-ilnd-2011.