Sequoia Technology, LLC v. Dell, Inc.

• Court: District Court, D. Delaware
• Decided: May 20, 2021
• Docket: 1:18-cv-01127
• Status: Unknown

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE

SEQUOIA TECHNOLOGY, LLC, Plaintiff, : Vv. : C.A. No. 18-1127-LPS-CJB : (CONSOLIDATED) DELL INC., DELL TECHNOLOGIES : INC. and its subsidiary EMC : CORPORATION (AKA DELL EMC), : Defendants. :

RED HAT, INC., : Plaintiff, :

v. : C.A. No. 18-2027-LPS-CJB SEQUOIA TECHNOLOGY, LLC and : ELECTRONICS AND : TELECOMMUNICATIONS RESEARCH : INSTITUTE, : Defendants. :

SEQUOIA TECHNOLOGY, LLC, : Counterclaim Plaintiff, : Vv. : RED HAT, INC. and INTERNATIONAL : BUSINESS MACHINES CORPORATION, : Counterclaim Defendants. :

MEMORANDUM ORDER WHEREAS, Magistrate Judge Burke issued a 33-page Report and Recommendation (“Report”) (D.I. 231)' on October 1, 2020, recommending that the Court adopt certain claim constructions for disputed terms in U.S. Patent No. 6,718,436 (the 436 patent”); WHEREAS, on October 29, 2020, Sequoia Technology, LLC and Electronics and Telecommunications Research Institute (“ETRI” and, together with Sequoia Technology, LLC, “Sequoia”) objected to the Report (“Objections”) (D.I. 247), asserting that it incorrectly construed the terms “extent allocation table . . . used or not used,” “disk partition,” and “computer-readable recording medium storing . . .”; WHEREAS, on December 1, 2020, Red Hat, Inc. (“Red Hat’’) responded to the Objections (“Response”) (D.I. 251); WHEREAS, the Court has considered the parties’ objections and responses de novo, see St. Clair Intell. Prop. Consultants, Inc. v. Matsushita Elec. Indus. Co., Lid., 691 F. Supp. 2d 538, 541-42 (D. Del. 2010); 28 U.S.C. § 636(b)(); Fed. R. Civ. P. 72(b)(3); NOW, THEREFORE, IT IS HEREBY ORDERED that the Objections (D.I. 247) to Judge Burke’s constructions of “extent allocation table .. . used or not used,” “disk partition,” and “computer-readable recording medium storing . . .” ace OVERRULED and the constructions set forth in the Report are ADOPTED. 1, Sequoia objects to the recommended construction of “extent allocation table for indicating whether each extent in the disk partition is used or not used” as meaning “extent allocation table for indicating whether each extent in a disk partition is or is not storing

1 All references to the docket index (D.I.) are to the lead case, C.A, No. 18-1127.

information.” (id. at 4) The parties dispute what it means for an extent to be “used or not used.” (See D1. 231 at 19) The Report determined that “used or not used” refers to whether the extent “is or is not storing information,” and the Court agrees with the three reasons it gives for this conclusion. (Jd. at 19-21) First, the patent’s specification describes an “extent” as “a minimum unit of space allocation to store information,” directly linking an extent’s purpose to storing information. (See id. at 19-20) (citing °436 patent at 7:2-3) (emphasis added) Second, the patent cites a publication in which its inventors indicate that “an extent is ‘used’ when it is storing information.” (Jd. at 20) Third, the extent allocation map referenced in a preferred embodiment allocates all of a disk partition’s extents to one logical volume. (/d. at 20-21) This map would be superfluous under Sequoia’s view that an extent allocation table shows merely whether an extent has been allocated to a logical volume, and not whether it is actually storing information. (See id.’ While not dispositive, this is “another point in favor of Red Hat’s construction.” (id. at 21) 2. Sequoia objects to the recommended construction of “disk partition” as meaning “section of a disk that is a minimum unit of a logical volume.” (D.1. 247 at 4-9) The Report describes how the °436 patent identifies a hierarchical process for storing information at three levels: at the lowest level is the extent, which is a “minimum unit of space allocation to store information;” at the next level is the disk partition; and at the highest level is the logical volume. (D.I. 231 at 7-8) (citing *436 patent 6:58-59, 65, 7:1-3) Red Hat does not dispute that disk

2 Sequoia insists that the Report incorrectly concludes all extents in a disk partition must be used by a logical volume. (See DL. 247 at 4) Sequoia, however, misconstrues the Report’s conclusion, as Red Hat explains. (See D.J. 251 at 3) The Report simply observed that in the preferred embodiment all the extents in the disk partition are allocated to one logical volume, and Sequoia’s construction would render the extent allocation table in that embodiment nonsensical. (See D.I. 231 at 20)

partitions (and therefore the logical volume) are made up of extents, which are smaller than disk partitions. (See DJ. 251 at 5 n.4) For its part, Sequoia agrees that a disk partition can bea minimum unit of a logical volume; it only disagrees with the Report’s requirement that it must be. (See D.I. 247 at 5-6) The key question is whether a logical volume can be constructed or resized in units less than whole or entire disk partitions. The Report answers this question in the negative. Sequoia opposes this conclusion on three grounds, each of which is unavailing. 3. First, Sequoia contends the Report misconstrues the intrinsic evidence. (See id. at 5-7) The Report notes that the claims suggest a whole or entire disk partition is used to construct

a logical volume, describing “disk partitions forming” and “constructing” the logical volume and explaining that the first step in the method is “creating the logical volume by gathering disk partitions,” (D.1. 231 at 9) (citing 436 patent at 12:20, 24-25, 28-29, 13:19-20, 15:7-8) The Report also points to language in the specification explaining that “[t]he present invention constructs a logical volume by using a disk partition as a volume construction unit,” adding that “t]he disk partition is a minimum unit of the logical volume” and “[t}he logical volume is a union of disk partitions.” (Id. at 9-10) (citing °436 patent at 11:66-67, 6:60-61, 64-65) While Sequoia is correct that several of these statements are directed to a preferred embodiment (see 247 at 6-7), the Report acknowledged this fact (see D.I. 231 at 10 n.3) and went on to explain that “the particular language used by the patentee (‘[t]he disk partition és”)” sounds like a definition and, in any event, supports Red Hat and does not support Sequoia (id. ). Sequoia relatedly argues that the Report “disregards” a portion of the specification describing “an Extent Size 95” as “a minimum space allocation unit of a corresponding volume.” (D.L. 247 at 5) (citing °436 patent at 8:35-36) There is no basis to conclude that Judge Burke disregarded this or any other portion of the record. As importantly, this statement does not

contradict the Report’s conclusion: an extent may be the minimum unit for allocating space on a disk, but it does not follow that it is also the minimum unit for creating or resizing logical volumes (which is the disputed issue). (See D.I. 251 at 5) Rather, the patent claims and specification indicate to a person of ordinary skill in the art (““POSA”) that the disk partition is the minimum unit for that function. Nor is the Court persuaded by Sequoia’s arguments with respect to Figures 5 and 8. Figure 5 shows a field for the “total number of extents in volume” alongside a field for the “total number of disk partitions.” (D.I. 247 at 2-3, 6) In Sequoia’s view, if all the extents in the disk partition must be allocated to the logical volume, then the first field would be easily calculable and, thus, unnecessary. (See id. at 3) The Court agrees, however, with Red Hat that the first field may provide help where, for example, a logical volume comprises many disk partitions, which in turn each comprise a different number of extents. (See D.I. 251 at 5) Figure 8 contains

a mapping map 75, which stores information on the extent numbers, not just the partitions. (See 247 at 6) Sequoia argues that the extent number would be unnecessary if the disk partition were the smallest unit. (fd) The Court agrees with Red Hat that Sequoia is conflating the roles of the extent and the disk partition. (See D.I. 251 at 5-6) 4, Second, Sequoia asserts that the Report’s construction would render logical volume management (“LVM”) essentially useless, as the “purpose of LVM is to allow for logical volumes to be dynamically resized, without any restriction limiting it to whole partitions.” (D.I. 247 at 7) Sequoia argues this notion is supported by statements Red Hat’s expert made after the Markman hearing. (/d.) The statements at issue, however, relate to the accused Red Hat

3 The Report explicitly acknowledges that an extent is a “minimum unit of space allocation to store information.” (D.I. 231 at 7-8) (citing °436 patent at 7:2-3)

product, not the patent, and do not bear on claim construction. (See D.I. 251 at 6; see also id. (“{T'Jhe patent itself — which is the relevant point of reference for claim construction —

exclusively depicts logical volumes that are made up of entire partitions, belying Sequoia’s suggestion that such a system is ‘useless.’”)) By contrast, the statements made by ETRI in successfully opposing institution of an IPR on the ’436 patent — that “extents are added or removed from a logical volume at the level of the disk partitions” — appear to distinguish the patent from prior art describing logical volumes that are formed from subsets of disk partitions. (See D.I, 231 at 11) (citing D.I. 178 Ex. K at 5) These ETRI statements are fully consistent with the Report’s construction. 5. Third, Sequoia contends that Red Hat is judicially estopped from arguing for a

narrower construction than it proposed during the IPR, when it argued that a “portion of a disk”

can form a logical volume. (See D.I. 247 at 8-9) Judicial estoppel is only appropriate when: (1) the party to be estopped is asserting a position that is irreconcilably inconsistent with one she previously asserted; (2) the party changed her position in bad faith, 1e., with an intent to play fast and loose with the court, and (3) the use of judicial estoppel is tailored to address the affront to the court’s authority or integrity and no lesser sanction would adequately remedy the situation. See Montrose Med. Grp. Participating Sav. Plan v. Bulger, 243 F.3d 773, 777-78 (3d Cir. 2001). “[A] party has not displayed bad faith for judicial estoppel purposes if the initial claim was never accepted or adopted by a court or agency.” Jd. at 778. Red Hat argues that judicial estoppel does not apply because the PTAB denied institution of its IPR petition, so Red Hat did not prevail in the prior adjudication. (See D.I. 251 at 7; see also New Hampshire v. Maine, 532 U.S. 742, 749 (2001) (“(Judicial estoppel] generally prevents a party from prevailing in one phase of a case on an argument and then relying on a contradictory

«

argument to prevail in another phase.”) (internal citation and quotation marks omitted)) Sequoia disagrees. (See D.I. 247 at 9) The Court need not resolve this dispute because, even if the Court

were to agree with Sequoia, and were also to find that Red Hat’s position is inconsistent with what it advocated in the IPR, the record is devoid of any indication of bad faith on Red Hat’s part or any affront to the integrity of the courts from permitting Red Hat to press its current position. 6. Finally, Sequoia objects to the recommended construction of “computer-readable recording medium” or “CRM” in the preamble to Claim 8 as meaning “transitory or non- transitory computer-readable recording medium.” The parties dispute whether CRM

encompasses transitory media. Sequoia argues that the patent does not even mention transitory media — yet, as the Report correctly states, it also does not limit a CRM to non-transitory media; instead, the specification describes what a CRM “includes.” (See DJ. 231 at 27-28) (citing □□□□ patent at 11:36-39) (describing “computer readable medium including compact disc read only memory (CDROM), random access memory (RAM), floppy disk, hard disk, and magneto-optical disk”) The Court agrees with the Report that a POSA would read this list as non-exhaustive, as the portion of the specification in which it appears does not purport to limit the term’s scope. Without clear language excluding transitory media, the Report turns to extrinsic evidence, relying on 34 different prior art patents and patent applications from 2000 and 2001,4 discussed in a declaration from Red Hat’s expert, which collectively support the conclusion that

a claim directed to a “computer-readable recording medium” at that time would have been understood to encompass transitory media. (See D.I. 231 at 28) (citing DI. 154 Ex. U) This is persuasive extrinsic evidence, particularly given the lack of any substantive rebuttal from

4 The °436 patent was filed in December 2001.

□

Sequoia’s expert (see id. at 29) and the Report’s observation that other courts examining this issue have reached a similar conclusion (see id. at 28 n.15). 7. In light of the foregoing conclusions, the Court need not address Red Hat’s argument that Sequoia adds substantial new evidence and arguments without good cause,> (See D.I. 251 at 9-10) The Court has considered all of the arguments made and evidence presented by Sequoia.

> [| ~ May 20, 2021 HONO EONARD P. STARK Wilmington, Delaware UNITED STATES DISTRICT JUDGE

5 Red Hat asserts that Sequoia introduced at least the following new evidence and arguments: two new expert declarations; Red Hat documents regarding the accused product; and a new judicial estoppel argument. (See D1. 251 at 9-10)