Speed Track, Inc. v. Amazon.com, Inc.

Background

SpeedTrack alleged that Amazon.com, Inc. and other defendants infringed United States Patent No. 5,544,360, the ’360 Patent. The patent concerns a system and method for accessing computer files through user-defined category descriptions rather than relying only on traditional hierarchical folders. The court conducted a technology tutorial and briefing before a claim-construction hearing. Claim construction is the court’s process for deciding the meaning and scope of patent claim terms.

Judge Hamilton had previously construed several terms in an earlier related proceeding involving the same patent. The Federal Circuit had affirmed the earlier construction of “category description.” Judge White treated that construction as controlling for that term and considered the other earlier constructions for their persuasive value while making an independent decision in this case.

Rulings on disputed terms

“Category descriptions having no predefined hierarchical relationship”

The court adopted the earlier construction:

“The category descriptions have no predefined hierarchical relationship. A hierarchical relationship is a relationship that pertains to a hierarchy. A hierarchy is a structure in which components are ranked into levels of subordination; each component has zero, one, or more subordinates; and no component has more than one subordinate component.”

The court explained that the limitation addresses both the relationship between a category-description list and its category descriptions and the relationships among the category descriptions themselves. The court relied on the patent’s description of ordinary tree-like directories, in which each component has only one parent, and contrasted that structure with the patent’s “hybrid folders,” which may belong to multiple parent directories. The court also relied on statements SpeedTrack made during patent examination to distinguish an earlier reference called Schwartz.

The court rejected the defendants’ proposal to add field-and-value language. It concluded that the proposal would introduce terms not used in the patent, could confuse the jury, was broader than the disclaimer shown by the prosecution history, and omitted a useful definition of “hierarchy.”

“File”

The court construed “file” as:

“Any collection of data or information stored on a computer system.”

The court further explained that “collection of data or information” means a set of data or information that the operating system recognizes as a unit. The data or information must already exist as a collection when stored, but it need not be stored in one physical location. The court therefore distinguished an already stored file from disparate data that is collected into a unit only when retrieved.

“File location information”

The court construed this term as:

“Information that is sufficient to locate a file.”

The court found that the claims require the information to be sufficient to access the selected file. It declined to require a fully qualified file path or an alias record because the patent describes those as examples rather than mandatory limitations and contemplates different kinds of storage systems.

“File name” or “name of each file”

The court construed these terms as:

“A name used to identify a file.”

The court concluded that the claims and specification did not require the more specific operating-system directory limitations proposed by the defendants.

Search-filter guarantee

The disputed claim language required that, for each category description in a search filter, there be at least one matching file in the file information directory. The court construed the language to mean:

“Wherein for each category description in the search filter there is always at least one file in the file information directory having a set of category descriptions matching the set of category descriptions of the search filter.”

The defendants argued that this was a step-plus-function limitation under 35 U.S.C. § 112(f) and that the patent was invalid because its specification did not disclose the required algorithm. The court rejected that argument. It concluded that the claim did not indicate an intent to use a step-plus-function limitation and that “creating in the computer system a search filter” described a concrete act rather than an abstract step lacking supporting acts.

Stipulated constructions and case management

The court noted the parties’ stipulated constructions. “Search filter” means a set of one or more category descriptions, with at least one logical operator if more than one category description is included, used to search. “Category description table” means at least one list or array containing multiple category descriptions.

Disposition

Judge Jeffrey White adopted the constructions stated in the order. The court set a further case-management conference for December 6, 2019, and ordered the parties to submit a joint case-management report by November 29, 2019. The order construed disputed patent terms and did not determine infringement or validity beyond rejecting the defendants’ claim-construction argument concerning Section 112(f).