KOM Software Inc. v. NetApp, Inc.

CourtDistrict Court, D. Delaware
DecidedOctober 4, 2023
Docket1:18-cv-00160
StatusUnknown

This text of KOM Software Inc. v. NetApp, Inc. (KOM Software Inc. v. NetApp, Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Delaware primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
KOM Software Inc. v. NetApp, Inc., (D. Del. 2023).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE

KOM SOFTWARE INC., § § Plaintiff, § § v. § Civil Action No. 18-160-WCB § NETAPP, INC., §

§ Defendant. § § §

MEMORANDUM OPINION AND ORDER

In this patent infringement action, defendant NetApp, Inc., has moved for judgment on the pleadings under Federal Rule of Civil Procedure 12(c). Dkt. No. 145. NetApp argues that the patent claims asserted by plaintiff KOM Software Inc. are invalid under 35 U.S.C. § 101 for being directed to patent-ineligible subject matter. For the reasons set forth below, the motion is GRANTED IN PART and DENIED IN PART. I. Background In its first amended complaint, KOM originally asserted claims from seven patents against NetApp and two other defendants who have since been dismissed from the case. Five of those seven patents are no longer asserted in this case. The remaining asserted claims are claims 5, 6, and 9 of U.S. Patent No. 6,654,864 (“the ’864 patent”) and claims 4, 34, 69, and 103 of U.S. Patent No. 9,361,243 (“the ’243 patent”). Both patents are generally directed to restricting access to files contained within a computer data storage medium. As explained in the specification of the ’864 patent, a software application may seek to access and modify various files stored in a storage medium, such as a hard drive or CD-ROM, while the medium is running. ’864 patent, col. 1, ll. 15–41. In many operating systems, including “Windows NT,” the drivers for the storage devices are “hidden from applications by a protected subsystem.” Id. at col. 1, ll. 30–34. That is, the applications and the storage devices do not communicate directly with one another; instead, “[e]ach communicates with the operating system

independently.” Id. at col. 1, ll. 43–47. In a typical operating system, a software application will submit a request to open a file through the application’s protected subsystem. The request is sent to the “IO [input/output] system services,” which in turn direct the “IO Manager” to communicate with the device drivers. Id. at col. 4, ll. 25–42. As the specification of the ’864 patent notes, prior art systems would require the device drivers to “deal[] with file system commands which cannot be completed,” because all access requests were sent through the IO manager to the device drivers. See id. at col. 7, line 53, through col. 8, line 5. The ’864 and ’243 patents disclose implementing a “trap layer” between the application layer and the file system layer of the computer system. See ’864 patent, col. 7, ll. 53–58. The trap

layer prevents invalid requests from being passed to the device drivers. Based on the capabilities of the storage device that is being accessed, the trap layer can block some requests and modify other requests. Id. at col. 7, ll. 60–64. For example, a particular storage device may permit files to be read and written but not deleted. Id. at col. 8, ll. 8–10. In such a device, the trap layer that is disclosed in the asserted patents would “intercept” a request to delete a file and would return an error message to the application that was trying to access the device. Id. at col. 8, ll. 14–21. Similarly, if the device supports “read access” but not “write access,” the trap layer could modify a request to open a file with “read/write access” by converting that request into one seeking “read- only access.” See id. at col. 7, ll. 44–46. Claim 5 of the ’864 patent is generally representative of the asserted claims of the ’864 patent for purposes of the present motion. That claim recites as follows: 5. A method of restricting access by a computer to a storage medium other than a write once medium in communication with the computer, the method comprising the steps of: providing an indication of a data write access privilege for the entire logical storage medium indicating a disabled operation relating to alteration of a portion of each file stored within the logical storage medium, the indication other than a read only indication; and restricting file access to each file within the logical storage medium in accordance with the same indication while allowing access to free space portions of the same logical storage medium. ’864 patent, cl. 5. Claim 66 of the ’243 patent, from which asserted claims 69 and 103 depend, is generally representative of the asserted claims of the ’243 patent for purposes of the present motion. That claim recites as follows: 66. A data processing system configured to apply a computer file system operation access privilege to a computer storage medium, comprises: at least one computer processor configured to associate the computer file system operation access privilege with at least a portion of the computer storage medium; said at least one computer processor configured to intercept, by at least one computer file system trap layer or at least one computer file system filter layer, an attempted operation on said at least a portion of the computer storage medium, wherein said interception occurs regardless of an identity of a user that attempts the attempted operation; said at least one computer processor configured to compare the attempted operation to the computer file system operation access privilege; and said at least one computer processor configured to allow, or deny the attempted operation based on the comparison of the attempted operation to the computer file system operation access privilege. ’243 patent, cl. 66. NetApp contends that all the asserted claims of the ’864 and ’243 patents are invalid under 35 U.S.C. § 101 because, in NetApp’s view, they are directed to an abstract idea and do not contain an inventive concept sufficient to render the claims patent-eligible. II. Legal Standard

Under Federal Rule of Civil Procedure 12(c), “[a]fter the pleadings are closed—but early enough not to delay trial—a party may move for judgment on the pleadings.” A Rule 12(c) motion “will not be granted unless the movant clearly establishes that no material issue of fact remains to be resolved and that [it] is entitled to judgment as a matter of law.” Jablonski v. Pan Am. World Airways, Inc., 863 F.2d 289, 290 (3d Cir. 1988) (internal quotation marks and citation omitted). The standard that applies to a Rule 12(b)(6) motion to dismiss for failure to state a claim also applies to motions brought under Rule 12(c); that is, in the common situation in which the defendant moves to dismiss the complaint, the court “must accept the truth of all factual allegations in the complaint and must draw all reasonable inferences in favor of the non-movant.” Revell v. Port Auth. of New York & New Jersey, 598 F.3d 128, 134 (3d Cir. 2010). More generally, “[t]he

purpose of judgment on the pleadings is to dispose of claims where the material facts are undisputed and judgment can be entered on the competing pleadings and exhibits thereto, and documents incorporated by reference.” Venetec Int’l, Inc. v. Nexus Med., LLC, 541 F. Supp. 2d 612, 617 (D. Del. 2008). Patent eligibility under 35 U.S.C. § 101 is a question of law, based on underlying facts. See Aatrix Software, Inc. v.

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

Related

Revell v. Port Authority of New York & New Jersey
598 F.3d 128 (Third Circuit, 2010)
Le Roy v. Tatham
55 U.S. 156 (Supreme Court, 1853)
Diamond v. Diehr
450 U.S. 175 (Supreme Court, 1981)
Accenture Global Services v. Guidewire Software, Inc.
728 F.3d 1336 (Federal Circuit, 2013)
Venetec International, Inc. v. Nexus Medical, LLC
541 F. Supp. 2d 612 (D. Delaware, 2008)
Planet Bingo, LLC v. Vkgs LLC
576 F. App'x 1005 (Federal Circuit, 2014)
Ddr Holdings, LLC v. hotels.com, L.P.
773 F.3d 1245 (Federal Circuit, 2014)
Ariosa Diagnostics, Inc. v. Sequenom, Inc.
788 F.3d 1371 (Federal Circuit, 2015)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Tli Communications LLC v. Av Automotive, L.L.C.
823 F.3d 607 (Federal Circuit, 2016)
Electric Power Group, LLC v. Alstom S.A.
830 F.3d 1350 (Federal Circuit, 2016)
McRO, Inc. v. Bandai Namco Games America Inc.
837 F.3d 1299 (Federal Circuit, 2016)
Affinity Labs of Texas, LLC v. Directv, LLC
838 F.3d 1253 (Federal Circuit, 2016)
Intellectual Ventures I LLC v. Symantec Corp.
838 F.3d 1307 (Federal Circuit, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
KOM Software Inc. v. NetApp, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/kom-software-inc-v-netapp-inc-ded-2023.