Kaufman v. Microsoft Corporation

District Court, S.D. New York·Decided January 22, 2020·No. 1:16-cv-02880·Unknown

Opinion

DOCUMENT ELECTRONICALLY FILED UNITED STATES DISTRICT COURT DOC #: SOUTHERN DISTRICT OF NEW YORK , — et pe = □□ RS SSA DATE FILED: | /2 2. /Z262¢ MICHAEL PHILIP KAUFMAN, : ORDER GRANTING IN PART : AND DENYING IN PART Plaintiff, : MOTION FOR SUMMARY : JUDGMENT -against- : 16 Civ. 2880 (AKH) MICROSOFT CORPORATION, Defendant. i

neem enna naan nanan □□□ nene n-ne non-=====-- X ALVIN K. HELLERSTEIN, U.S.D.J.: This is an action brought by the owner of U.S. Patent No. 7,885,981 (the “’981 Patent”), Michael Kaufman (“Plaintiff”’ or “Kaufman”). Plaintiff alleges that Defendant Microsoft Corporation’s (“Defendant” or “Microsoft”) software infringes the ’981 Patent. Defendant moves for summary judgment. J held oral argument on Defendant’s motion on January 16, 2020. For the reasons stated at oral argument and for the reasons that follow, Defendant’s motion is granted in part and denied in part. BACKGROUND The ’981 patent was filed on October 26, 2007 and issued on February 8, 2011. Plaintiff's Rule 56.1 Statement in Opposition to Microsoft’s Motion for Summary Judgment, ECF No. 127 (“Pl’s 56.1”) | 2.1 The invention described in the ’981 Patent relates to the field of data processing, and more specifically to relational computer databases. The object of the invention is, among other things, “to provide a complete and fully functional user interface (UJ)

! Facts are taken from Defendant’s Rule 56.1 Statement of Undisputed Material Facts in Support of Microsoft’s Motion for Summary Judgment, ECF No. 114; Plaintiff’s Rule 56.1 Statement in Opposition to Microsoft’s Motion for Summary Judgment, ECF No. 127; and supporting materials referenced therein. Citations to Pl’s 56.1 can be considered to incorporate both Defendant’s statements of fact and Plaintiff's responses.

for any arbitrarily complex or large database schema, without any custom software programming.” Pl’s 56.1 § 3; see also ECF No. 40-6 (together with ECF No. 40-7, the “’981 Patent”) at col. 3:8-12. A key feature of the invention is the automated nature of certain steps. See Pl’s 56.1 { 7. The term “automatically generating” appears in the preamble to each of the independent claims. Pl’s 56.1 f 4-6; see also ’981 Patent at col. 377:3, 377:46-57, 378:23-24. Of most relevance to Defendant’s argument here, the act of “scan[ning] [a] database,” described in limitation (b) of each of the independent claims, occurs “automatically.” Pl’s 56.1 4-7; see also ’981 Patent at col. 377:2-37, 377:46-378:54. Each independent claim requires “a user interface paradigm comprising a set of modes for interacting with a given database table, said modes comprising create, retrieve, update and delete, and a corresponding display format for each mode.” Pl’s 56.1 □□ 4-6; see also ’981 Patent at col. 377:14-19, 377:58-378:4, 378:32-36. Furthermore, the invention “integrates into each said mode display processes for representing, navigating, and managing said relationships across tables.” Pl’s 56.1 4-6; see also °981 Patent at col. 377:25-38, 378:9-21, 378:41-54. In summary, three functions (i.e., representing, navigating, and managing) are integrated into four mode displays (i.e., create, retrieve, update, and delete). The 981 Patent states, “The preferred embodiment of the invention . . . corresponds in most respects to an implementation of the invention being developed under the trademark SCHEMALIVE™ which is herein referred to as the ‘reference implementation.’” °981 Patent at col. 4:34-38. The complete source code for that reference implementation (the “Schemalive Reference Implementation’) is reproduced in the ’981 Patent. Pl’s 56.1931. The ’981 Patent

ial nein diode incre Fores a claim construction order. ECF No. 69. The portions of the claims requiring construction, where used here, have the definitions assigned in the claim construction order.

also includes figures depicting the Schemalive Reference Implementation’s mode displays. Pl’s 56.1 32. The source code for the Schemalive Reference Implementation does not perform the delete functionality, and the figures do not show a delete mode display, as Kaufman had not yet incorporated the delete functionality in the Schemalive Reference Implementation. Pl’s 56.1 32, 34. The ’981 Patent does, however, include instructions on how to add a delete mode to the Schemalive Reference Implementation. Pl’s 56.1 § 32. Plaintiff alleges that Microsoft’s Dynamic Data infringes the °981 Patent. Pl’s 56.1 { 14. Microsoft actively developed Dynamic Data between 2007 and 2009. Pl’s 56.1 4 15. A user creates the Dynamic Data application from a tool called Visual Studio. Pl’s 56.1417. To scana database, the user must invoke Object Relational Modeler and click through a series of prompts and windows, essentially telling the software which database to scan. Pl’s 56.1 Jf 19-20. Defendant contends, and Plaintiff contests, that additional manual steps are necessary at the end of the scanning process. Pl’s 56.1 § 21. The parties agree that some allegedly infringing user interfaces in Dynamic Data do not integrate all three claimed processes (representing, navigating, and managing). Pl’s 56.1 24, 26-27. For example, Dynamic Data’s purported retrieve mode does not have a process for managing. Rather, Plaintiff alleges, each allegedly infringing display integrates at least one of the three claimed processes. Pl’s 56.1 24. The instant suit is not the first time Microsoft has come across Kaufman’s work. First, in 2006, the United States Patent and Trademark Office (“USPTO”) cited one of Kaufman’s patent applications when it rejected a Microsoft patent application. Pl’s 56.1 | 38; Declaration of Leah J. Edelman in Support of Microsoft’s Motion for Summary Judgment, ECF No. 113 (“Edelman Decl.”), Ex. J at 32. The cited Kaufman application, which Kaufman calls the “parent to the

Patent,” did not have the same claims as the ’981 Patent. Pl’s 56.1 438. Second, when European authorities rejected a Microsoft patent application in 2009, they cited a 2002 Patent Cooperation Treaty application made by Kaufman. P1’s 56.1 4 39; Edelman Decl., Ex. L. The cited Kaufman application again did not have the issued claims of ’981 Patent, but Kaufman contends they were substantively similar. Pl’s 56.1 § 39. Third, in 2011, Microsoft cited the application for the ’981 patent (the “’981 Patent Application”) in an information disclosure statement submitted to the USPTO. Pl’s 56.1 4 40; Edelman Decl., Ex. J at 30-31. Kaufman says the claims in the Patent Application were nearly identical to those issued in the ’981 Patent. Pl’s 56.1 4 40. Fourth, in 2014, the USPTO cited the ’981 Patent Application when it rejected a Microsoft patent application. Pl’s 56.1 40; Edelman Decl, Ex. J at 31. Outside counsel handled Microsoft’s communications with the USPTO. Pl’s 56.1 441. None of the aforementioned Microsoft patent applications concerned Dynamic Data. On April 18, 2016, Plaintiff filed the instant suit, bringing claims for direct infringement, inducing infringement, contributory infringement, and willful infringement. DISCUSSION Summary judgment should be granted where “the movant shows that there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law.” Fed. R. Civ. P. 56(a). A genuine issue of material fact exists “if the evidence is such that a reasonable jury could return a verdict for the nonmoving party.” Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 248 (1986). In ruling on a motion for summary judgment, the Court “is... required to view the evidence in the light most favorable to the party opposing summary judgment, to draw all reasonable inferences in favor of that party, and to eschew credibility assessments.” Amnesty Am. v.

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

Kaufman v. Microsoft Corporation, (S.D.N.Y. 2020).

Kaufman v. Microsoft Corporation (Kaufman v. Microsoft Corporation) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related