Indacon, Inc. v. Facebook, Inc.
824 F.3d 1352
Fed. Cir.2016Background
- Indacon owns U.S. Patent No. 6,834,276, claiming a system that inserts automatically generated hyperlinks/links into searchable databases and indexes.
- Indacon sued Facebook for patent infringement; after the district court’s claim construction order the parties stipulated to noninfringement and judgment was entered for Facebook.
- On appeal Indacon challenged the district court’s constructions of four claim terms: “alias” (and “alias term”), “custom link,” “custom linking relationship,” and “link term.”
- The district court had construed “term” as a textual expression (e.g., words, numbers, spaces), and defined “alias” accordingly; it also construed the link-related terms to require that each instance of a defined term be identifiable and displayable as a link to a user-selected file.
- The Federal Circuit reviewed claim construction de novo (district court relied on intrinsic evidence only) and assessed specification and prosecution-history language to interpret disputed terms.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Whether “alias” can be graphical (not just textual) | Indacon: “alias” may be graphical (or textual) based on file formats referenced in the spec. | Facebook: specification defines “term” as textual; no intrinsic support for graphical aliases. | Court: “alias” limited to textual expression (adopts district court). |
| Whether an “alias” is itself a hyperlink | Indacon: an alias can be a textual or graphical hyperlink. | Facebook: the spec shows links are established to aliases, but alias is not the link itself. | Court: alias is a user-defined textual name/label, not the hyperlink. |
| Whether “custom link / custom linking relationship / link term” can apply to only some instances of a term | Indacon: terms can be linked selectively; constructions should allow linking less than all instances. | Facebook: spec and prosecution history describe associating every/all instances with a file; no plain art meaning expands scope. | Court: terms are limited to allowing each/all instances of a defined term to be identified and displayed as links. |
| Whether claim differentiation prevents the above limitation | Indacon: other claims distinguish between linking instances vs. all instances, so limitation shouldn’t be read into all claims. | Facebook: claims cited are independent and differ in scope; claim differentiation not controlling here. | Court: claim differentiation doesn’t overcome specification/prosecution-history support for limiting language. |
Key Cases Cited
- Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir.) (specification is primary guide to claim meaning)
- Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576 (Fed. Cir.) (use of intrinsic evidence in claim construction)
- Teva Pharm. USA, Inc. v. Sandoz, Inc., 135 S. Ct. 831 (2015) (review standards for claim construction; factual findings reviewed for clear error)
- Info-Hold, Inc. v. Applied Media Techs. Corp., 783 F.3d 1262 (Fed. Cir.) (claim construction reviewed de novo)
- Irdeto Access, Inc. v. Echostar Satellite Corp., 383 F.3d 1295 (Fed. Cir.) (absent an art-accepted meaning, construe terms by the patent disclosure)
- Fenner Invs., Ltd. v. Cellco P’ship, 778 F.3d 1320 (Fed. Cir.) (public may rely on patentees’ prosecution statements)