Tecsec, Inc. v. Adobe Systems Incorporated
658 F. App'x 570
Fed. Cir.2016Background
- TecSec sued Adobe for infringing four "Distributed Cryptographic Object Method (DCOM)" patents covering multi-level encryption and use of "labels" attached to encrypted objects; district court granted summary judgment of non-infringement to Adobe.
- Representative method claim requires: access an object-oriented key manager; select an object; select a label; select an encryption algorithm; encrypt; label the encrypted object; read the object label; determine access authorization based on label; decrypt if authorized.
- Adobe Acrobat encrypts PDFs via password or digital-certificate security, stores encryption-related data in an "encryption dictionary," and supports nesting encrypted PDFs (PDF envelopes) that can be separately encrypted.
- At summary judgment the district court sua sponte construed “selecting a label” to require choosing a pre-existing label and construed "label" narrowly from the specification; it then held Acrobat non-infringing because the encryption dictionary is created on save and (for password security) does not identify particular persons.
- The Fourth Circuit vacated and remanded: it rejected the district court’s “pre-existing” requirement for "selecting a label," affirmed the district court’s express definition of "label," found Acrobat’s password/key structure can meet that definition, modified the "object-oriented key manager" construction to include object-oriented functionality, and rejected Adobe’s alternative grounds for affirmance.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Proper construction of “selecting a label” | Plain meaning; no pre-existing-label requirement; may include selecting components | Selecting implies choosing a pre-existing item; one cannot select what does not exist | "Selecting a label" given plain meaning; district court erred imposing a pre-existing requirement; vacated summary judgment |
| Construction of “label” and whether Acrobat’s encryption dictionary is a label | "Label" = identifier associated with an object; Acrobat’s encryption dictionary qualifies (includes user/owner keys) | Specification defines label narrowly; encryption dictionary (esp. with password security) doesn’t identify persons | Court affirmed district court‘s definitional construction (express definition in spec) but held Acrobat’s password/keys can satisfy it (identifying classes such as user vs owner) |
| Scope of “object-oriented key manager” and whether Acrobat meets it | Broader: software controlling access to algorithm; Acrobat’s security handler performs required functions | Key manager must manage keys (generate, store, distribute, etc.); Acrobat doesn’t store/distribute keys (re-derives key from password) | Modified construction: software component that manages encryption of an object by performing one or more key-management functions; factual disputes preclude summary judgment for Adobe |
| Multi-level security (preamble) — does Acrobat infringe? | Nesting encrypted PDFs across sessions satisfies multi-level encryption | Acrobat cannot provide multiple nested layers within a single session; thus allegedly fails | Multi-level security can be met by nesting via multiple sessions; genuine factual disputes exist; summary judgment denied on this ground |
Key Cases Cited
- O2 Micro Int’l Ltd. v. Beyond Innovation Tech. Co., 521 F.3d 1351 (Fed. Cir.) (district court duty to resolve claim construction disputes)
- Teva Pharm. USA, Inc. v. Sandoz, Inc., 135 S. Ct. 831 (2015) (deference standard for factual findings in claim construction)
- Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir.) (use of specification and ordinary meaning in claim construction)
- Jack Guttman, Inc. v. Kopykake Enters., Inc., 302 F.3d 1352 (Fed. Cir.) (patentee’s express definition in specification is dispositive)
- United States v. Guglielmi, 929 F.2d 1001 (4th Cir.) (factors governing reassignment to a different judge)