Tomtom, Inc. v. AOT Systems GMBH
56 F. Supp. 3d 767
E.D. Va.2014Background
- TomTom sued for a declaratory judgment seeking a ruling that U.S. Patent No. 6,356,836 (the '836 patent) is invalid and not infringed; Dr. Michael Adolph (patent owner) counterclaimed for infringement. AOT (licensee) was dismissed for lack of jurisdiction.
- The '836 patent claims a method for mobile units (GPS) to generate, store, and update traveled-distance and section data representing real routes and traffic conditions; claims 1 (independent) and 22 (dependent) are in dispute.
- Parties disputed nine claim terms/phrases: node/coordinates, absolute coordinates, preamble phrases (“generating and updating data for use in…”, “destination tracking system of at least one mobile unit”), “section data” and how nodes are selected, and multiple uses of “storage device” and whether that term is indefinite.
- Prosecution history: examiner initially rejected claims as anticipated by Saito and Thad; Adolph distinguished the prior art by emphasizing (a) storage of contiguous section data including direction, distance and time relationships, and (b) ability to start collecting data without a preloaded road database. These prosecution statements were central to construction.
- The court applied the Phillips/Vitronics framework: start with claim language, then specification and prosecution history (intrinsic evidence); use extrinsic evidence (dictionaries, experts) only when intrinsic is silent or ambiguous.
Issues
| Issue | TomTom (Plaintiff) Argument | Adolph (Defendant) Argument | Held |
|---|---|---|---|
| Meaning of “node” | Should mean a road-network intersection | Plain and ordinary meaning (location reading) | Construed as: intersection, origin, destination, or point where vehicle changes direction > predetermined value in a grid/road network |
| “geographical coordinates x¡ and y¡” & “absolute coordinates” | Geographic coords = Cartesian x,y (not lat/long); absolute coords = latitude/longitude | Plain and ordinary meaning suffices | Both given plain and ordinary meaning: coordinates that locate a node geographically; absolute coords = coordinates locating the mobile unit (not limited to lat/long) |
| Preamble: “generating and updating data for use in …” | Means data generated/updated by mobile unit is used by that same unit | Preamble not limiting / need not be construed | Preamble is limiting (antecedent basis to “said mobile unit”); construed to require that data generated/updated by the mobile unit is used by that unit |
| Preamble: “destination tracking system of at least one mobile unit” | Means portable navigation device that does not contain initial road network info | Preamble not limiting | Constrained by prosecution disclaimer: construed as a destination-tracking system of at least one mobile unit that does not contain initial information relating to existing road networks |
| “section data” | Should be defined as data showing nodes Pj and Pk are connected, direction from Pj to Pk, and distance between them | Plain and ordinary meaning suffices | Construed per prosecution statement as: data from traveled-distance data reflecting (a) nodes Pj and Pk are connected, (b) direction Pj→Pk, (c) distance traveled |
| “selecting… nodes Pj and Pk which define contiguous sections Pj Pk” | Must mean selecting the most characteristic nodes of a road segment and dropping intermediates so sections are contiguous | Plain meaning | Construed: select nodes most characteristic of a segment, drop intermediate nodes, such that end of one section is start of next (contiguous) |
| “storing traveled distance data in at least one storage device” | Storage must be non‑volatile and retain entire trip data to generate sections | Plain and ordinary meaning sufficient | Plain meaning governs: “device used for storing data” (dictionary-supported). No non‑volatile limitation imposed |
| “storing section data” and “storing the section data file in the storage device” (antecedent/indefiniteness) | Terms indefinite for lack of explicit antecedent; or must require separate non‑volatile storage devices for each data type | Plain meaning / not indefinite | Not indefinite; specification shows separate storage units (trip storage, section data storage unit, section data file storage unit). Court construed each to require storage in a separate storage device than traveled-distance data; no non‑volatile requirement imposed |
Key Cases Cited
- Phillips v. AWH Corp., 415 F.3d 1303 (en banc) (claim construction must begin with intrinsic evidence and ordinary skill in the art)
- Vitronics Corp. v. Conceptronic, 90 F.3d 1576 (1996) (court may rely on claim language, specification, and prosecution history; extrinsic evidence is secondary)
- O2 Micro Int’l Ltd. v. Beyond Innovation Tech. Co., 521 F.3d 1351 (2008) (court must construe disputed claim terms when parties present a fundamental dispute regarding scope)
- Innova/Pure Water, Inc. v. Safari Water Filtration Sys., 381 F.3d 1111 (2004) (ordinary meaning to a person of ordinary skill at time of invention)
- Comark Communications, Inc. v. Harris Corp., 156 F.3d 1182 (1998) (doctrine of claim differentiation as a guide)
- Chimie v. PPG Industries, 402 F.3d 1371 (2005) (prosecution history can create disavowal narrowing claim scope)