In re Ricoh Company Ltd. Patent Litigation

Filing 644

REVISED CLAIM CONSTRUCTION AFTER RECONSIDERATION. Signed by Judge James Ware on October 23, 2009. (jwlc1, COURT STAFF) (Filed on 10/23/2009)

Download PDF
1 2 3 4 5 6 7 8 9 10 IN THE UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF CALIFORNIA SAN JOSE DIVISION In re Ricoh Company Ltd. Patent Litigation NO. C 03-02289 JW REVISED CLAIM CONSTRUCTION AFTER RECONSIDERATION / I. INTRODUCTION This is a patent infringement case. Plaintiff is Synopsys, Inc. ("Synopsys"). Defendant is Ricoh Company Ltd. ("Ricoh"). Ricoh is the owner of U.S. Patent No. 4,922,432 ("the `432 Patent"). Ricoh alleges that Synopsys' customers ("Customer Defendants") are infringing certain claims of the `432 Patent. In response, Synopsys asserts that the `432 Patent is invalid, unenforceable, and not infringed by any Synopsys product, and seeks declaratory relief. On January 18, 2005, a different Judge of this Court held a hearing in accordance with Markman v. Westview Instruments, Inc., 517 U.S. 370 (1996), to construe disputed terms and phrases of the asserted claims. The Court's April 7, 2005 Claim Construction Order construed ten disputed terms in Claim 13 of the `432 Patent. (Docket Item No. 226.) On December 14, 2006, the case was stayed pending reexamination of the `432 Patent by the USPTO. (Docket Item No. 542.) On February 15, 2008, the case was reassigned to Judge Ware. (Docket Item No. 544.) On April 7, 2008, the Court conducted a Case Management Conference and on motion by Synopsys, lifted the stay imposed by the previous Judge. (Docket Item No. 548.) The Court set a hearing for cross-motions for summary judgment in an attempt to bring this 2003 case to a close. (Id.) United United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1 2 3 4 5 6 7 8 9 10 A. Based on the construction of a particular phrase in the April 7, 2005 Claim Construction Order, Synopsys filed a Motion for Summary Judgment of Noninfringement of the `432 Patent. (Docket Item No. 571.) In the course of considering the motion, this Court determined to reconsider the April 7, 2005 interpretation of the subject phrase and thus, denied Synopsys' Motion as premature. (Docket Item No. 621.) In this Order, the Court gives a revised construction of words and phrases of the `432 Patent. II. DISCUSSION The `432 Patent The `432 Patent, "Knowledge Based Method and Apparatus for Designing Integrated Circuits Using Functional Specifications," discloses as its invention "a computer-aided design system and method for designing an application specific integrated circuit ("ASIC"). The language under reconsideration is in Claim 13. B. Claim 13 of the `432 Patent Claim 13 provides:1 A computer-aided design process for designing an application specific integrated circuit which will perform a desired function comprising storing2 a set of definitions of architecture independent actions and conditions; storing data describing a set of available integrated circuit hardware cells for performing the actions and conditions defined in the stored set; storing in an expert system knowledge base a set of rules for selecting hardware cells to perform the actions and conditions; describing3 for a proposed application specific integrated circuit a series of architecture independent actions and conditions; specifying for each described action and condition of the series one of said stored definitions which corresponds to the desired action or condition to be performed; and selecting from said stored data for each of the specified definitions a corresponding integrated circuit hardware cell for performing the desired function of the application specific integrated circuit, said step of selecting a hardware cell comprising applying to the specified definition of the action or condition to be performed, a set of cell selection rules stored in said expert system knowledge base and generating for the selected United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1 2 3 Unless otherwise indicated, all bold typeface is added by the Court for emphasis. For ease of reference, the Court will refer to this as the "storing" step. For ease of reference, the Court will refer to this as the "describing" step. 2 1 2 3 4 5 6 7 8 9 10 integrated circuit hardware cells, a netlist defining the hardware cells which are needed to perform the desired function of the integrated circuit and the interconnection requirements therefor. (`432 Patent, Col. 16, l. 34; Col. 13, l. 65.) (emphasis added). C. The Court's Previous Construction of a Phrase used in Claim 13 of the `432 Patent On January 18, 2005, a different Judge of this Court gave the following construction: Disputed Claim Language "architecture independent actions and conditions" Court's Construction "functional or behavioral aspects of a portion of a circuit (or circuit segment) that does not imply a set architecture, structure, or implementing technology, but excludes the use of register-transfer level descriptions as taught in Darringer." United States District Court 11 For the Northern District of California On reconsideration, the parties dispute the appropriateness of including a reference to "register-transfer level descriptions" and to "Darringer" in the construction of the phrase "architecture independent actions and conditions." In construing any particular phrase of a limitation of a claim, the Court begins with a consideration of the `432 Patent as a whole. D. Reconsideration 1. "architecture independent" 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Claim 13 is not the only claim in which the inventors use the phrase "architecture independent" and the phrase "actions and conditions," or some variation of those phrases, in a limitation. When the same words or phrases are used in different claims of the same patent, a court interprets the words and phrases as having the same meaning unless it is clear from the specification and prosecution history that the phrases have different meanings in the different claims. See Phillips v. AWH Corp., 414 F. 3d 1303, 1314 (Fed. Cir. 2005). The phrases "architecture independent" and "actions and conditions" first appear in Claim 1: A computer-aided design system for designing an application specific integrated circuit directly from architecture independent functional specifications for the integrated circuit, comprising a macro library defining a set of architecture independent operations comprised of actions and conditions 3 1 2 3 4 5 6 7 8 9 10 input specification means operable by a user for defining architecture independent functional specifications for the integrated circuit, said functional specifications being comprised of a series of operations comprised of actions and conditions, said input specification means including means to permit the user to specify for each operation a macro selected from said macro library In the Preamble to Claim 1, the inventors use the phrase "architecture independent" to modify "functional specifications." A skilled artisan would understand the Preamble of Claim 1 to recite a system that designs an ASIC from "architecture independent functional specifications." It is necessary therefore, to determine what the inventors meant when they recited that these "functional specifications" are "architecture independent." In the background section of the specification, the inventors recite state of the art computeraided design (CAD) systems and methods for designing an ASIC that require input from highly skilled design engineers: CAD techniques have been used with success in design and verification of integrated circuits, at both the structural level and at the physical layout level. For example, CAD systems have been developed for assisting converting VLSI structural level descriptions of integrated circuits into the physical layout level topological mask data required for actually producing the chip. Although the presently available computedaided design systems greatly facilitate the design process, the current practice still requires highly skilled VLSI design engineers to create the necessary structural level hardware descriptions. (`432 Patent, Col. 1:51-63.) As an improvement over the existing state of the art, the invention is summarized as a computer-aided design system and method that allows a user to define the "functional requirements" for a desired ASIC, using a "sequence of logical operations" independent of the "logic," i.e., hardware structure, that could "carry out those specific functions." (`432 Patent, Col. 2:7-15.) The inventors pointed to a flowchart of logical operations as a preferable example of specifications that are "architecture independent:" The functional architecture independent specifications of the desired ASIC can be defined in a suitable manner, such as in list form or preferably in a flowchart format. The flowchart is a highly effective means of describing a sequence of logical operations, and is well understood by software and hardware designers of varying levels of expertise and training. (`432 Patent, Col. 2:21-29.) United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 4 1 2 3 4 5 6 7 8 9 10 In contrast to specifications that are "architecture independent," the inventors use the phrase "architecture specific" to refer to specifications that include the logic hardware cells that can perform a particular function: From the flowchart (or other functional specifications), the system and method of the present invention translates the functional architecture independent specifications into structural an[d]4 architecture specific level definition of an integrated circuit, which can be used directly to produce the ASIC. The structural level definition includes a list of the integrated circuit hardware cells needed to achieve the functional specifications. The structural level definition includes a list of the integrated circuit hardware cells needed to achieve the functional specifications. These cells are selected from a cell library of previously designed hardware cells of various functions and technical specifications. (`432 Patent Col. 2:34-39.) The inventors' use of the phrase "architecture dependent" to describe specifications for a functional decision tree and "structural and architect specific" to describe specifications that are of implementing logic components is supported by the drawings and the descriptions of the drawings. The inventors label FIG. 1a, "Functional Level:" A flowchart is a graphic representation of an algorithm and consists of two kinds of blocks or states, namely actions and conditions (decisions). Actions are conventionally represented in the flowchart by a rectangle or box, and conditions are represented by a diamond. Transitions between actions and conditions are represented by lines with arrows. (`432 Patent, Col. 3:52-57.) The inventors label FIG. 1b "Structural Level:" FIG. 1b illustrates a structural (or logic) level representation of an integrated circuit. In this representation, blocks are used to represent integrated architecture specific circuit hardware components for performing various function, and the lines interconnecting the blocks represent paths for the flow of data or control signals between the blocks. The blocks may, for example, represent hardware components such as adders, comparators, registers, system controllers, etc. (`432 Patent, Col. 3:59-67.) United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 The Court finds that the article "an" would be understood to be a typographical error and should be read as the conjunction "and." 5 4 1 2 3 4 5 6 7 8 9 10 2. "actions and conditions" In the "input specification means" limitation of Claim 1, the inventors state that "operations and conditions" are a series of logical operations: . . . said functional specifications being comprised5 of a series of operations comprised of actions and conditions. (`423 Patent, Col. 14:43-44.) Consistently throughout the written description, the phrase "actions and conditions" is used to describe the state of the data being controlled by the ASIC, changed in state, and flow of the data based on the state or changes in the state. 3. "a set of definitions" The storing step of Claim 13, recites "storing a set of definitions of architecture independent actions and conditions." In the written description, the inventors variously describe a "data base"6 that contains "design data (flowchart, logic, etc)."7 The flowchart is described as being created by a "Flowchart Editor." In the written description, "macro names and arguments"8 are described as data from which a flowchart would be created. A person of ordinary skill in the art would understand macros and arguments as computer instructions. These macros are stored in a macro library.9 Thus, one skilled in the art would understand "a set of definitions" to mean "a set of computer instructions such as macros and arguments." There is nothing in the `432 Patent documents that indicates that the inventors intended any different meaning of "architecture independent" or of "actions and conditions" in Claim 13. United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 In patent claims, the word "comprising" is open ended; it includes the recited elements and additional elements. AGF Industries, Inc. v. Cardinal IG Company, 239 F.3d 1239, 1250 (Fed. Cir. 2001). 6 7 8 9 5 (`432 Patent, Col. 5:63.) (`432 Patent, Col. 5:65.) (`432 Patent, Col. 7:25-26.) (`432 Patent, Col. 7:28.) 6 1 2 3 4 5 6 7 8 9 10 Accordingly, as used in Claim 13 of the `432 Patent, the Court construes the phrase "storing a set of definitions of architecture independent actions and conditions" to mean: storing a set of instructions of actions or conditions to which a circuit could be subjected that are not dependent on any particular arrangement of hardware cells to perform the actions or create or maintain the conditions. 4. "describing" Claim 13 recites as one of the steps in the method: "describing for a proposed application specific integrated circuit a series of architecture independent actions and conditions." The parties have not requested the Court to determine whether this step is performed by a user or whether it describes a further storing step. Therefore, the Court reserves the construction of the word "describing" as used in this limitation for later consideration. With respect to the phrase "a series of architecture independent actions and conditions," the Court gives to it the same construction as used in the storing step. E. Reference to Register-Transfer Level and Darringer At issue is whether the Court should reconsider the reference to register-transfer level ("RTL") and Darringer in the construction of Claim 13. A clear and unambiguous limitation of the scope of a claim made during prosecution of the claim may be used as a basis to narrow the scope of the claim. Seachange Int'l, Inc. v. C-Cor, Inc., 413 F.3d 1361, 1373 (Fed. Cir. 2005). During the prosecution of the `432 Patent, claims were rejected as obvious based on Darringer, U.S. Patent No. 4,703,435. In response, the inventors distinguished their invention from Darringer and others that required user input at what was referred to as the "register transfer level:" It is respectfully submitted that based upon the Darringer reference, the present invention would not be obvious to one skilled in the art. Although Darringer et al., does disclose a method and system for automatic logic design and it is known in the art of automatic layout to utilize sell libraries of circuit components, Darringer does not teach the present invention. A very clear distinction between Darringer and the present invention is that the input to the Darringer system is in the form of a register transfer level flowchart control language. Darringer et al., U.S. patent No. 4,703,435, column 4, lines 26-32. In order for a designer to utilize the Darringer system, he/she must possess a sophisticated understanding of the complexities of the circuit logic itself and therefore have the specialized expert knowledge of a highly skilled VLSI design engineer. In contrast, the application specific circuit designer utilizing the 7 United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1 2 3 4 5 6 7 8 9 10 present invention need not possess any expertise common among highly skilled VLSI design engineers since input to the present invention is in the form of an architecture independent functional specification. (Declaration of Richard G. Frenkel, Ex. 5, Prosecution History, Docket Item No. 628.) Similar distinctions were made to other prior art references. The Court finds that it is unnecessary to incorporate into its construction of "architecture independent" any reference to "register-transfer level descriptions" or "Darringer." A person of ordinary skill in the art would understand that any system for designing an ASIC that requires the user to input information based on the user having an understanding of the flow of data though registers, logic gates or any other hardware a fortiori would not be "architecture independent." To the extent it can be argued that certain statements in the written description support the conclusion that reference to RTL is necessary, the Court finds it unpersuasive. For example, the written description provides: The cell selector maps the blocks to cells selected from the cell library 34. It selects an optimum cell for a block. This involves the formulation of rules for selecting appropriate cells from the cell library. Four types of information are stored for each cell. These are: (1) functional level information: description of the cell at the register transfer level. (2) logic level information; description in terms of flip-flops and gates. (3) circuit level information: description at the transistor level. (4) Layout level information: geometrical mask level specification. (`432 Patent, Col. 9:21-34.) This reference in the written description to a "register transfer level" describes an embodiment of the operation of the invention relevant to a construction of the "selecting" step of Claim 13, not to the "storing" step or the "describing" step. The claims of the invention do not preclude all use of register-transfer level descriptions or other architecture dependent descriptions. The cited references to RTL are not relevant to construing the "storing" or the "describing" step. III. CONCLUSION The Court has given further consideration to its construction of words and phrases of the `432 Patent. On November 23, 2009 at 10 a.m., the parties shall appear for a Case Management Conference to discuss further proceedings in the case. On or before November 13, 2009, the parties United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 8 1 2 3 4 5 6 7 8 9 10 shall file a Joint Case Management Conference. The Statement shall include, among other things, the parties' proposed schedule for how this case should proceed, and an update on the parties' settlement efforts, if any. Dated: October 23, 2009 JAMES WARE United States District Judge United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 9 1 2 3 4 5 6 7 8 9 10 THIS IS TO CERTIFY THAT COPIES OF THIS ORDER HAVE BEEN DELIVERED TO: Brian A. E. Smith smithbrian@howrey.com Daniel J. Bergeson dbergeson@be-law.com DeAnna Dahlyce Allen allend@dsmo.com Denise M. De Mory demoryd@howrey.com Donald P. Gagliardi dgagliardi@be-law.com Eric Oliver OLIVERE@DSMO.COM Erik Keith Moller invalidaddress@myrealbox.com Ethan B. Andelman ethan.andelman@nxp.com Gary M. Hoffman HoffmanG@dicksteinshapiro.com Henry C. Su suh@howrey.com Hway-Ling Hsu hhsu@be-law.com Jaclyn C. Fink finkj@howrey.com Julie M. Holloway jholloway@wsgr.com Kenneth W. Brothers BrothersK@dicksteinshapiro.com Matthew Greinert greinertm@howrey.com Matthew E. Hocker hockerm@howrey.com Michael A. Berta mberta@wsgr.com Michael A. Berta mberta@wsgr.com Richard Gregory Frenkel rfrenkel@wsgr.com Ron Eleazer Shulman rshulman@wsgr.com Teresa M. Corbin corbint@howrey.com Terrence J.P. Kearney tkearney@wsgr.com Thomas C. Mavrakakis tmavrakakis@mac.com Dated: October 23, 2009 Richard W. Wieking, Clerk By: /s/ JW Chambers Elizabeth Garcia Courtroom Deputy United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?