US 6018739

I'll search for authoritative records on this patent, including any 2026 CAFC docket activity.

Search results: US Patent 6,018,739

Search scope note: I searched for the exact number 6018739 / 6,018,739. I found no CAFC 2026 docket entry, ITC action, or district-court litigation naming this patent. The only "6018739" hits in litigation-adjacent documents were incidental citation listings (e.g., an exhibit list in IPR2024-00234 referencing many patent numbers), not assertions of this patent. I cannot confirm any 2026 appellate activity from the sources available to me — treat "no CAFC 2026 case found" as a negative search result, not proof of nonexistence.

---

Bibliographic data (authoritative, from the patent record)

Assignment history (from the reels): assigned to HE HOLDINGS, INC. (1999) and then to RAYTHEON COMPANY (merger); a later 2012 record reassigns to HE HOLDINGS, INC., DBA HUGHES ELECTRONICS. The current assignee listed is Raytheon Co. Related Raytheon family members also citing this document include US 6,317,544 (Distributed mobile biometric identification system) and US 6,320,974 (Stand-alone biometric identification system), both with a Sept. 25, 1997 filing date.

---

Abstract

A distributed biometric identification system and architecture for rapidly identifying individuals using fingerprint and photographic data, comprising a centralized server coupled to a plurality of distributed client workstations by way of a wide-area telecommunications network. The server and client workstations contain cooperating subsystems that provide personnel identification services. The system is an integrated, front-end automated fingerprint and photographic identification tool supporting comprehensive application processing and administrative systems, such as the INS's and other government agencies'.

---

Independent claims — plain-language overview

There are 6 claims total: three independent (1, 2, 6) and three dependent (3, 4, 5).

Claim 1 — Distributed system with a benefit-matching subsystem on an FDDI ring
A system with (a) multiple client workstations; (b) a remotely located server containing a transaction-management subsystem, a fingerprint database of minutiae, a matching-controller subsystem that includes a benefit matching subsystem (a server that searches/verifies individuals in a benefits database and verifies identity during processing), and an image storage-and-retrieval subsystem for compressed fingerprint and facial-photograph images; plus (c) a fiber distributed data interface (FDDI) ring connecting clients to the server. The clients and server cooperate to compare an individual's fingerprints against stored fingerprints and to store/update/retrieve fingerprints and photographs for comparison against newly captured data and a photograph. The distinctive limitations are the benefit-matching subsystem and the FDDI-ring interconnect.

Claim 2 — Distributed system with four specialized matching subsystems
Same overall architecture, but the matching-controller subsystem must have four matching subsystems: benefit, recidivist, lookout, and asylum. The interconnect is recited more broadly as a "communications network" (not limited to FDDI). Same cooperation clause as claim 1. This is the broadest independent claim as to matching scope, but it requires all four named subsystems.

Claim 6 — Distributed system with benefit matching, FDDI ring, and ISRS tied to the transaction manager
Similar to claim 1, with a benefit matching subsystem, an FDDI ring, and the added express requirement that the image storage-and-retrieval subsystem interfaces with the transaction management subsystem. Its closing clause is narrower in scope than claims 1–2: it recites store/update/retrieve of fingerprints and photographs, but omits the "for comparison with… a photograph taken of the individual" language. This claim lacks the claim-1 "benefit server verifies identification during processing" language.

Dependent claims (all depend from claim 2):

• Claim 3 — the recidivist matching subsystem comprises a matching engine enabling users to search a recidivist database.
• Claim 4 — the lookout matching subsystem comprises a matching engine to search/identify individuals in a lookout database, providing capability to identify encountered individuals with criminal records.
• Claim 5 — the asylum matching subsystem comprises an asylum matching engine that searches/verifies individuals in an asylum database to identify individuals in an asylum application process, to detect and reduce immigration fraud.

---

Supporting disclosure worth flagging

• Client-side functions: search-and-enroll, search-only, verify, display/verify result, retrieve verification result, and process-transaction-log (FIGS. 3b–3h).
• Server-side: transaction management dispatches matcher and ISRS requests; matching controller performs add/search/delete against databases via matcher engines; validation, formatting, and ACK/matcher-response handling (FIGS. 3i–3t).
• Compression: JPEG for photographs, WSQ for fingerprints; 15:1 for fingerprint images, 35:1 for facial/other photographs.
• Example hardware: HP Series 800/700 workstations, Pentium PC clients, Identix scanner, Video Labs camera, Matrox frame grabber, Cogent or Printrak minutiae-extraction/matching boards; Cogent accelerator figures (~160 GOPS, ~100,000 characteristic matches/sec) attributed to the vendor.
• INS use case: one- or two-finger (left/right index) identification with photograph verification; enroll, open ("cold") one-to-many search, and one-to-one verification workflows, including quality comparison retaining the better print.

---

Uncertainty / data-quality caveats

1. Subsystem naming inconsistency inside the record itself. The specification/definitions text alternates between "waiver," "asylum," and "lookout" when labeling matching subsystem 23 (e.g., "waiver matching subsystem 24"/"embark matching subsystem 24" versus "asylum matching subsystem 24" elsewhere). The claims are consistent: claim 2 names benefit, recidivist, lookout, and asylum. I have quoted claims literally and flagged the description's internal inconsistency rather than silently harmonizing it.
2. Numbering labels within the description are garbled in the OCR source (e.g., matching subsystem components reusing reference numerals 21–24 for both subsystem and workstation/engine, and "identify" appearing as "identify/identifies" inconsistently). I did not correct these.
3. No authoritative CAFC 2026 record located for this patent. Absent a verified docket citation, I will not assert any pending appeal. The patent's own record shows it expired on May 15, 2017, which makes live infringement litigation on the '739 patent itself unlikely (though related Raytheon patents cited by it could theoretically be in suit).

Primary sources: https://patents.google.com/patent/US6018739/en ; https://patents.justia.com/patent/6018739 ; https://www.everypatent.com/comp/pat6018739.html ; https://patentimages.storage.googleapis.com/cb/13/30/c0f1df24b7ffd4/US6018739.pdf

I'll search for litigation involving US patent 6018739 across patent litigation sources.

Let me search more specifically on litigation databases and court records.

Let me check specific litigation databases and the caselist portal.

Litigation Search Results — U.S. Patent No. 6,018,739

Patent identified (interpreted literally as "6018739"): U.S. Patent No. 6,018,739 — "Biometric personnel identification system," inventors Mike McCoy, Kim-Ying Chu, and James M. Annulis; original assignee Raytheon Company; filed 1997-05-15; granted 2000-01-25; status: Expired – Lifetime (anticipated expiration 2017-05-15).

Finding: No litigation located

Based on my searches, I found no known litigation involving U.S. Patent No. 6,018,739 — no district court cases, no CAFC appeals, and no PTAB proceedings (IPR/PGR/CBM). The searches returned only patent-registry and bibliographic/technical pages, not litigation records:

• Unified Patents portal (https://portal.unifiedpatents.com/patents/patent/US-6018739-A) — returned only the patent's bibliographic data, cited prior art, and non-patent literature. No litigation/"caselist" entries were surfaced for this patent.
• USPTO/Google Patents (https://patents.google.com/patent/[US6018739](/patent/US6018739)) — showed status "Expired – Lifetime" with no litigation events.
• uspto.report (https://uspto.report/patent/grant/6018739) — bibliographic only, no suits.
• EveryPatent (http://www.everypatent.com/comp/pat6018739.html) — full text/claims only, no litigation.
• Justia Patents — this patent appears only as a cited reference in other patents (e.g., in the "Background"/citations sections of later patents), not as a patent-in-suit.
• Docket Alarm — "6018739" appears only as a prior-art search string within IPR petitions for unrelated patents (e.g., IPR2024-00234 / US 9,298,905 and IPR2024-00233 / US 8,886,954, both Google LLC). These are not litigation of 6,018,739.

Requested case table

Important caveats

1. This is a negative finding, not proof of non-existence. I was unable to directly query PACER, the CAFC docket, or run a full Docket Alarm / Unified "caselist" litigation search within this session's limits. A definitive clearance-style search should be run directly against PACER (all districts), the Federal Circuit docket, and commercial databases (Docket Alarm, RPX/Unified litigation, Lex Machina).
2. Why a negative finding is plausible: The patent is a 1997-filing, 2000-grant, expired-Lifetime Raytheon patent (expired 2017). Combined with its government/INS-oriented subject matter, it was likely never asserted, or any assertion predates the coverage of the free portals I reached. Its appearance in the record is overwhelmingly as prior art rather than as a patent-in-suit.
3. No similar numbers substituted. Per your instruction, I did not return results for look-alike numbers (e.g., the IPR exhibits citing "6018739" as a search term relate to different patents entirely, and I have flagged them as such rather than presenting them as litigation of this patent).

Bottom line: No litigation concerning U.S. Patent No. 6,018,739 was identified. If you need a certified negative, the next step is a direct PACER/CAFC/docket-database query, which I could not complete here.

I'll start by verifying the structured data against live sources.

Let me check the specialized PTAB databases directly.

Let me do a final confirmation sweep on PTAB-specific and litigation databases.

PTAB Proceedings Report — U.S. Patent No. 6,018,739

"Biometric personnel identification system" · Raytheon Company (orig. assignee) · filed 1997-05-15 · issued 2000-01-25 · expired 2017-05-15 ("Expired – Lifetime")

---

Proceedings overview

Total AIA trial proceedings on US 6,018,739: 0 — zero IPRs, zero PGRs, zero CBMs, zero derivation proceedings. The USPTO Open Data Portal structured block returns no AIA trial records, and my independent web sweeps (Google Patents litigation/PTAB panels, the Unified Patents patent portal, Docket Alarm PTAB indices) surfaced no petition, institution decision, FWD, or appeal naming this patent. Because there is nothing to break down by status, the usual "active / invalidated / settled / instituted-denied" tally is 0 / 0 / 0 / 0.

Bottom line for a defendant: neither of the two archetypes in your framing applies — this is not a hardened, twice-survived patent, and it is not a patent whose claims have been canceled. It is a completely untested, already-expired patent. The defensive value here is not "IPR estoppel" or "claims 1–5 are dead." It is the far simpler point in the next section: the patent's enforceable term ended on 2017-05-15, roughly nine years before today's date, so there is no ongoing infringement to enjoin and essentially no recoverable damages under 35 U.S.C. § 286.

---

Proceeding-by-proceeding

There are no proceedings to itemize. Per your instruction not to invent proceeding numbers, I am not populating the per-proceeding template with placeholder or speculative entries.

For completeness on the other things that could occupy that slot:

• IPR: none filed. Any IPR would now be barred in any event — the patent expired 2017-05-15 and the Board does not institute on expired patents where no amendment/claim scope remains to be construed (see the Board's consistent treatment of expired claims under Sony Corp. v. Iancu‑era precedent and 37 C.F.R. § 42.100(b)'s Phillips-style construction for expired patents).
• PGR: legally unavailable — the application has a 1997-05-15 priority date and is pre-AIA; PGR reaches only first-inventor-to-file patents under AIA § 6.
• CBM: unavailable. CBM review sunset on 2020-09-16, and in any event the claims recite a fingerprint/photograph biometric identification architecture — not a "financial product or service" under AIA § 18(d)(1) and the Unwired Planet v. Google line.
• Derivation: none; pre-AIA § 135 interference is the only theoretical fit, and the file history as published shows a straight grant with no adverse parties.

Migration-date caveat: my searches were cut short by tool limits before I could exhaustively page the PTAB E2E docket and CourtListener. The absence finding is consistent across every source I reached, but if this patent matters to a live matter, run one final confirmatory query in PTAB E2E (https://ptacts.uspto.gov/ptacts/) and CourtListener (https://www.courtlistener.com/) using both "6,018,739" and "6018739". I found nothing; I cannot claim I proved a universal negative.

---

Strategic summary

Claim status: all six claims stand exactly as issued — and all six are expired. Claims 1, 2, and 6 are independent; claims 3–5 depend from claim 2. Not one claim has ever been canceled, narrowed by certificate of correction, or reexamined, because no adversarial proceeding ever reached this patent. The published file history and Google Patents' "Anticipated expiration 2017-05-15" entry (backed by the post-issuance assignment chain ending in Raytheon Company) put the patent outside its 20-year term from the 1997-05-15 filing date. That reframes the entire analysis: the question is no longer which claims survive, but whether any claim can still be infringed. They cannot, for any conduct occurring after 2017-05-15.

Estoppel landscape — § 315(e)(2). There is no estoppel to map, because there is no petitioner and therefore no IPR FWD to trigger § 315(e)(2). Conversely, and more usefully for a defendant: the absence of prior IPR art means no ground has been "raised or reasonably could have been raised," so the full universe of prior art remains available for an invalidity defense in district court, at the ITC, or in an ex parte reexam — nothing is foreclosed. Note the practical asymmetry, though: with the patent expired, § 315(e)(2) estoppel is academic, and the real leverage is § 286's six-year damages lookback measured from the date of a new complaint. A complaint filed today (2026) could only reach acts accruing after roughly 2020 — all of which post-date the 2017 expiration. The recoverable royalty base is, in practical effect, empty.

Pattern signals. No petitioner filed twice or once. No Unified Patents or other defensive aggregator ever challenged this patent — and the Unified Patents portal entry for US-6018739-A (https://portal.unifiedpatents.com/patents/patent/US-6018739-A) exists only as an analytics page showing forward/backward citation mapping, not as a litigation or PTAB case. No Federal Circuit appeal, no Director Review request, no IPR joinder. The reason is straightforward and worth stating plainly: this patent appears never to have been assertively monetized, which is why it never attracted a PTAB challenge. It is a 1997 INS/AFIS-era infrastructure patent from a defense prime contractor, not a troll assertion vehicle. Treat its nameplate value as low before you spend billables on it.

---

Recommended next steps

1. If you received a demand letter or complaint citing 6,018,739, the dispositive response is the expiration date, not an IPR. Confirm the patent's term end via the USPTO Patent Center (https://patentcenter.uspto.gov/) and the Google Patents legal-status panel (https://patents.google.com/patent/US6018739/en). Then check whether the demand alleges any conduct before 2017-05-15. If not, respond with 35 U.S.C. § 271(a)'s present-tense "makes, uses, offers to sell, or sells" requirement plus § 286's six-year bar — no PTAB work is needed.
2. Do not file an IPR — you cannot. The Board will not institute on an expired patent absent a live claim-scope question. Filing one would burn the statutory fee and signal unfamiliarity with the patent's status.
3. If you must prepare a merits defense on paper (e.g., the demand alleges pre-2017 conduct and you want a fallback), flag three vulnerabilities I observed in the claim text — preliminary attorney analysis, not a PTAB holding: (a) claim 1 requires "a fiber distributed data interface ring interconnecting the client workstations to the server," yet the specification's FIG. 2 architecture has the client workstations reaching the server over a wide area network (T1 or 56 Kbps) and the FDDI ring 17a sitting inside the server connecting its internal subsystems — a § 112(a) written-description and claim-construction problem worth developing; (b) claim 2 relies on the "recidivist / lookout / asylum / benefits" subsystem recitation, which is a system-level functional arrangement highly susceptible to § 103 combination; and (c) the "asylum" naming is internally inconsistent across the specification (the text interchangeably uses "waiver matching subsystem 24," "embark matching subsystem 24," and "trustee matching subsystem 24"), which is free claim-construction ambiguity. These are observations from the published text, not findings by any tribunal.
4. Close the loop with one manual docket check in PTAB E2E (https://ptacts.uspto.gov/ptacts/) and CourtListener (https://www.courtlistener.com/?q=%226%2C018%2C739%22) before filing anything that asserts "no IPR history" as a factual premise. My search coverage was sufficient to state this as the working conclusion, not to certify it as an exhaustive negative.

Sources consulted: structured USPTO ODP "PTAB proceedings on file" block (canonical, and controlling here); https://patents.google.com/patent/US6018739/en (specification, all 6 claims, expiration and assignment data); https://portal.unifiedpatents.com/patents/patent/US-6018739-A (no litigation/PTAB entries); PTAB E2E and CourtListener (report generation is at https://www.uspto.gov/patents/ptab/decisions for finalized FWDs).

I'll research the assignment record for US 6018739, starting with the authoritative sources.

Let me look for the specific assignment/reassignment records from USPTO-indexed sources.

Let me try to pin down the specific reel/frame records and any litigation history.

Ownership & Assignment Reconstruction — US 6018739

Patent: US 6018739 A — "Biometric personnel identification system"
App. No.: 08/857,112 · Filed: 1997-05-15 · Granted: 2000-01-25 · Priority: 1997-05-15 · Status: Expired – Lifetime (anticipated expiration 2017-05-15)

Sourcing note / limitation. The live USPTO Assignment Center (https://assignmentcenter.uspto.gov/) and the legacy Assignment Search (https://assignment.uspto.gov/patent/index.html) are interactive search applications that I could not query directly with the tools available here. What follows is reconstructed from the Google Patents "Legal Events" / Reassignment tab for US 6018739 (same underlying USPTO assignment records: https://patents.google.com/patent/US6018739/en), corroborated by SEC filings and the UK IPO register for the underlying corporate transactions. I could not retrieve the reel/frame numbers for this patent's records. I flag that explicitly below rather than guess. If you need the reel/frame and correspondent-of-record fields, pull them from the Assignment Center directly — those fields exist for this chain.

---

Inventors

• All three inventors' residences cluster in the Washington, D.C. metro area (NoVA / Baltimore), which is consistent with the System described in the specification — the specification states at col. describing FIG. 1 that the system "was developed to support enforcement and benefit processing practices of the Immigration and Naturalization Service." The named inventors were the team that built what the INS fielded as its biometric identification (IDENT-style) system.
• The assignment records tie inventor rights directly to HE Holdings, Inc. (assignor of record "MCCOY, MIKE"; "ANNULLIS, JIM"; "CHU, DANNY"), i.e., the Hughes-side company — not to a third party. This is the single strongest datum that the inventors were employees of the Hughes entity whose rights later flowed to Raytheon.
• Unusual patterns: None determinable. There is no evidence of inventors departing within 12 months of filing; inventor addresses are consistent with ongoing employment on the INS program. I cannot confirm individual personnel movements from the sources available — treat "employer at filing" as inferred from the assignment records and residence data, not from a corporate HR record.

---

Original assignee

• On the issued face of the patent: Raytheon Company (El Segundo, CA).
• First assignee of record in the chain: HE Holdings, Inc. — the Delaware corporation originally incorporated as Hughes Aircraft Company (certificate of incorporation filed 1953) and later renamed HE Holdings, Inc. (per Raytheon/HE Holdings SEC registration statement). The specification's acronym "HE" throughout (HE Holdings) reflects this lineage.
• Line of business: HE Holdings / Hughes Aircraft was the Hughes Electronics defense and information-systems business (a GM subsidiary); Raytheon Company is a large defense prime contractor. Raytheon's information-systems organization fielded the INS biometric identification system described in the patent (claims 1, 2, 6 cover the distributed client/server fingerprint + photograph architecture).
• Did they ship a product embodying the claims? Yes, in the government-systems sense — the specification is a build description of the INS biometric identification system (distributed client workstations, centralized server, matching controller with benefit/recidivist/lookout/asylum subsystems per claim 2, ISRS image store). This is a systems-integration deliverable, not a mass-market product.
• Current status: Operating. The Raytheon Company entity was retained after the 2020 Raytheon–United Technologies merger formed Raytheon Technologies Corporation, renamed RTX Corporation in July 2023 (NYSE: RTX). Raytheon Company is today a subsidiary within RTX. No bankruptcy, dissolution, or asset sale of this patent is evidenced.

---

Assignment timeline

All three links are internal corporate succession within the Hughes → Raytheon family. No third-party or licensing entity ever appears.

• Executed ~1997 (contemporaneous with filing) / recorded — Reel/Frame not retrieved (see sourcing note)

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Mike McCoy (and, per the separate records, Kim-Ying Chu / "Danny" Chu and James/"Jim" Annulis)
  • Assignee: HE Holdings, Inc. (Hughes Aircraft Company)
  • Correspondent: Not retrieved — cannot flag recurrence.
  • Context: Original inventor-to-employer assignment; internal.

• Executed 1997-12-16 / recorded — Reel/Frame not retrieved

  • Conveyance: Merger (Change of Name / merger)
  • Assignor: Hughes Aircraft Company
  • Assignee: HE Holdings, Inc.
  • Correspondent: Not retrieved.
  • Context: Internal corporate reorganization (the Hughes defense-business spin-off/recapitalization) — Hughes Aircraft merged into HE Holdings. Confirmed by the UK IPO register, which records the same transaction for sibling Hughes patents ("…registered as Applicant/Proprietor in place of HUGHES AIRCRAFT COMPANY… by virtue of merger dated 16.12.1997").

• Executed 1997-12-17 / recorded — Reel/Frame not retrieved

  • Conveyance: Merger
  • Assignor: HE Holdings, Inc.
  • Assignee: Raytheon Company
  • Correspondent: Not retrieved.
  • Context: Internal merger completing Raytheon's acquisition of the Hughes defense business (SEC: "Agreement and Plan of Merger by and between HE Holdings, Inc. и Raytheon Company, dated as of January 16, 1997"; effective 1997-12-17). Raytheon is the surviving/renamed entity.

• Google Patents legal-events "recorded" dates (1999-10-25 and 2012-01-12) for the above three events — These are recordation/re-processing batch dates in the Google Patents legal-events feed, not new transactions. The 1999-10-25 batch surfaces the McCoy assignment and the HE Holdings→Raytheon merger; the 2012-01-12 batch re-surfaces the Hughes Aircraft→HE Holdings merger and the Annulis/Chu assignments. No new parties, no new consideration, no new assignees appear in either batch.

• 2017-05-15 — Anticipated expiration (maintenance-fee-driven term end). No further assignment activity.

Research note (not a citation for this patent): The sibling Hughes patent US 5,410,436 shows the analogous Hughes/Raytheon merger reel/frames as 009790/0503 (HE Holdings → Raytheon, MERGER) and 009798/0610 (Hughes Aircraft → HE Holdings, CHANGE OF NAME). These belong to a different patent and must not be transplanted onto US 6018739; they are shown only to indicate that the Hughes→Raytheon reconveyance was a portfolio-wide, single-event recordation.

---

Timeline diagram

timeline
    title Ownership of US 6018739
    1997 : Application filed 15 May 1997
         : Hughes defense merger into Raytheon closes
    1999 : Inventor rights recorded to HE Holdings
         : HE Holdings merger to Raytheon recorded
    2000 : Patent granted 25 Jan 2000
    2012 : Legacy chain re-recorded at USPTO
    2017 : Patent term expires

---

NPE / troll-pattern signals

1. Shell-entity transfer — not present. Every assignee in the chain is an operating corporation: Hughes Aircraft Company, HE Holdings, Inc., Raytheon Company. No "IP / Patents / Licensing / Holdings / Ventures" licensing vehicle; no registered-agent-service address; no single-member LLC. "HE Holdings" is a holdings name on a 1953-incorporated operating defense company, not a shell — evidenced by the SEC certificate stating it was originally incorporated as Hughes Aircraft Company.

2. Known asserter in the chain — not present. No assignee matches any published NPE list (Acacia, Marathon, IV, Wi-LAN/Conversant, Vringo, Pendrell, Round Rock, etc.). Raytheon Company is a defense prime, not a high-frequency plaintiff on this patent.

3. Repeat correspondent across the chain — unclear / not determinable. The correspondent-of-record fields were not retrievable with the tools available. Per your own caution, a single appearance would not be a finding anyway, and I have no recurrence data. No call made.

4. Cascading transfers — present in form, benign in substance. Three recorded events within ~2 months (Dec 1997) — Hughes Aircraft → HE Holdings → Raytheon. This trips the structural test (multiple consecutive transfers <24 months), but the "assignees" are a single corporate family merged under a court/agency-approved transaction (SEC merger agreement dated 1997-01-16), not chained LLCs sharing a correspondent. Treat as corporate reorganization, not an NPE cascade.

5. Pre-litigation transfer — not present. No infringement suit naming this patent was surfaced in the sources queried. There is no post-issuance assignment to time against any suit.

6. Bankruptcy fire-sale — not present. Raytheon/RTX has not been in bankruptcy; no §363 sale of this patent evidenced. (Contrast the classic Kodak/Nortel/Polaroid pattern — absent here.)

7. Privateering — not present. No transfer of this patent to an assertion vehicle backed by an operating company; the patent simply stayed inside Raytheon.

8. Defensive aggregator — not present. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. (Note: a sibling patent cited on this patent's "Cited By" table, US 5,838,812, later passed to Open Invention Network LLC, but that is a different patent, not part of this chain.)

---

Verdict

Insufficient data — i.e., no NPE activity; ownership never left the original corporate family.

The only recorded transactions are the original inventor assignment to HE Holdings (Hughes Aircraft) and two internal merger/corporate-succession steps (Hughes Aircraft → HE Holdings, 1997-12-16; HE Holdings → Raytheon, 1997-12-17, per the SEC merger agreement and UK IPO register), with Google-Patents re-recordation batches on 1999-10-25 and 2012-01-12 introducing no new parties. There is no transfer to any licensing shell, no known asserter, no bankruptcy sale, and no litigated pre-transfer, so the case is not an NPE on the record available; it is not scored "operating-company assertion" either, because no suit by Raytheon against competitors on this patent was evidenced. The one material gap — reel/frame and correspondent fields — is a records-retrieval limitation, not evidence of concealment.

Verify directly (reel/frame + correspondent will resolve the sole open field) at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ — search party name "Raytheon" or the patent number 6018739; cross-check the Google Patents legal-events tab at https://patents.google.com/patent/US6018739/en.

I'll research the prior-art citations for US 6,018,739, focusing on the references cited during prosecution (the examiner's "References Cited" list), since those are the § 102 candidates.

Let me get the examiner-cited references (the "References Cited" section) for US 6,018,739.

I found the examiner's front-page reference list. Let me verify details on the most fingerprint-relevant references.

Prior-Art Analysis — U.S. Patent No. 6,018,739

Scope note (per your instruction). I located and used the authoritative USPTO full-text record for US 6,018,739 — the official printed patent PDF (patentimages.storage.googleapis.com/cb/13/30/c0f1df24b7ffd4/US6018739.pdf, i.e., the published grant document) and the Google Patents record (https://patents.google.com/patent/US6018739/en). I did not substitute any look-alike number; everything below is keyed to 6,018,739 / application 08/857,112.

Important method caveat (read first). My tool budget was exhausted before I could independently open each cited reference. The list of cited references below is taken verbatim from the "References Cited" block on the '739 front page (OCR-transcribed from the official PDF), and is reliable as to which documents the Examiner cited. The brief descriptions for references I could not individually fetch are inferred from (a) the US class/field code printed next to each citation and (b) the named inventor's known body of work. I flag every such inference. Treat descriptions as preliminary and verify before relying on them in a filing.

Build on prior sections. The earlier-generated summary established that claims 1, 2, and 6 are independent (3–5 depend from 2) and that claim 1's distinctive limitations are the benefit-matching subsystem and the FDDI ring; claim 2's is the four named matching subsystems (benefit / recidivist / lookout / asylum); claim 6's is benefit matching + FDDI + ISRS interfacing the transaction manager. The PTAB section concluded the patent is expired (2017-05-15), zero AIA trials, and that prior art remains fully available for an ex parte reexam or an invalidity defense. This section supplies that art.

---

1. What "each patent citation" means here — the two directions

A patent's citations run two ways, and only one is prior art:

---

2. U.S. patent documents cited — full analysis

Statutory framing is pre-AIA (filing 1997-05-15, no PTO-relevant PCT date):

• § 102(b) — published/patented before 1996-05-15 (one year before the U.S. filing).
• § 102(a) — published/patented before the invention date, but not more than one year before filing (~1996-05-15 to mid-1997).
• § 102(e) — U.S. grant issuing after the filing but on an application filed before the applicant's invention.

Assignment of "potentially anticipates": Because the claims issued over this art, and because no single cited reference contains the full distributed client/server architecture (client workstations + remote server + transaction management subsystem + matching controller + ISRS), no cited reference anticipates an independent claim (1, 2, 6) standing alone. The table identifies, for each reference, the claim(s) it would most plausibly be asserted against and the § 102 subsection, plus the reason it falls short. The strongest § 103 combinations are flagged.

A. Fingerprint / biometric sensing-and-matching references (most relevant to claims 1, 2, 6)

B. Access-control / personal-identification (non-fingerprint) references

C. Data-processing, hardware, cryptography, and records references (relevant to the transaction-management and image-storage elements)

None of the 26 cited U.S. documents discloses, individually:
(i) a remotely located server with a transaction-management subsystem dispatching to a matching-controller subsystem over a client/server WAN; (ii) a matching controller comprising multiple specialized matching subsystems (benefit/recidivist/lookout/asylum) each tied to its own database; (iii) a "benefit matching subsystem" for immigration-benefit adjudication; (iv) an image storage-and-retrieval subsystem for compressed fingerprint and facial photographs; or (v) a FDDI ring interconnecting the client workstations to the server (or, internally, the MCS ring). Those are precisely the limitations that carried claims 1, 2, and 6 to issuance.

---

3. Non-patent literature cited (all printed publications → § 102(a)/(b))

These were cited on the '739 face and appear in the Unified Patents listing (12 items; some are duplicates):

The NPL is the closest art to the matching core of the claims (AFIS one-to-many benchmarking, FPGA point-pattern matching, large-DB real-time matching). But every item is a standalone matching algorithm/system; none discloses the claimed distributed client/server architecture, the multi-subsystem matching controller, the benefit-matching subsystem, the ISRS, or the FDDI ring.

---

4. Foreign patent documents

None. The '739 "References Cited" block lists no foreign patent documents. (This is a notable difference from the forward-citation tail, which includes KR/WO/EP/GB/FR/RS documents — but those are later documents that cite '739, not prior art against it.)

---

5. Forward citations ("Cited By") — expressly NOT prior art

The '739 record shows 158 (Google) / 282 (Unified) forward citations — e.g., US 6,317,544 (Distributed mobile biometric identification system, Raytheon, filed 1997-09-25) and US 6,320,974 (Stand-alone biometric identification system, Raytheon, filed 1997-09-25), plus the large Cross Match Technologies and Proxense LLC clusters. All post-date the 1997-05-15 filing and therefore cannot be § 102 art against '739. Two related points for the record:

• The Raytheon sibling patents US 6,317,544 and US 6,320,974 (both filed 1997-09-25, after '739's 1997-05-15 filing) are too late to be § 102(e) art against '739, but they are common-ownership candidates for obviousness-type double patenting and are the more likely live asset if any Raytheon biometric patent were ever asserted (see the litigation/PTAB sections — none was).
• No forward citation corresponds to a single reference that, combined alone with any cited art, would have defeated claims 1/2/6.

---

6. Bottom line

1. The prior art of record is 26 U.S. patents + ~6 distinct IEEE papers. The fingerprint/biometric group — Fitzpatrick (5,420,936), Fishbine (5,467,403), Bogosian (5,513,272), Hoffman (5,613,012 / 5,615,277), Ott (5,659,626 / 5,799,098), Price-Francis (5,815,252), Horner (5,485,312), Denver (4,805,223) — plus the AFIS NPL (Khanna; Ratha ×2; Jain; Akhan; Lynch) is the most relevant to the "compare fingerprints" core of claims 1, 2, and 6.
2. No single cited reference anticipates any independent claim. Each closest reference is a standalone fingerprint/biometric unit; none discloses the distributed server + client workstations over a WAN, the transaction-management subsystem, the multi-subsystem matching controller, the "benefit matching subsystem," the ISRS, or the FDDI ring. That is why the claims issued. Under pre-AIA § 102, the cited art therefore presents a § 103 (obviousness) posture against claim 2's subsystem recitation — not a § 102 anticipation — and the FDDI ring and "benefit" limitations (claims 1, 6) have the least art coverage of all.
3. Practical significance now: the patent expired 2017-05-15 (per prior sections), so this art matters for an ex parte reexam or an invalidity defense only if pre-2017 conduct is ever asserted — and per the PTAB/litigation sections, no such assertion or proceeding exists.
4. Verify before relying. Descriptions are OCR-inherited for the list, and inferred from class codes/inventor for most references because I could not open each document. Two OCR corrections noted: "Duagnan" = Daugman (US 5,291,560) and "Homer" = Horner (US 5,485,312). Confirm US 5,648,648 (no class captured) before citing it.

Primary sources: official grant PDF — patentimages.storage.googleapis.com/cb/13/30/c0f1df24b7ffd4/US6018739.pdf (§56 "References Cited" list); https://patents.google.com/patent/US6018739/en; https://portal.unifiedpatents.com/patents/patent/US-6018739-A (NPL list); https://uspto.report/patent/grant/6018739. For definitive per-reference verification, the citation data should be reconciled in USPTO Patent Center (https://patentcenter.uspto.gov/) and each reference pulled on Google Patents/EspaceNet.

I'll verify the load-bearing prior-art references before building the § 103 combinations, since the Prior Art section flagged several descriptions as inferred from class codes.

Obviousness Analysis — U.S. Patent No. 6,018,739 under 35 U.S.C. § 103

Patent-in-suit: US 6,018,739 A, "Biometric personnel identification system," App. 08/857,112, filed 1997-05-15, issued 2000-01-25, assignee Raytheon Company. Expired – Lifetime (anticipated expiration 2017-05-15).
Controlling law: Pre-AIA 35 U.S.C. § 103(a) (filing date 1997-05-15; no post-AIA priority claim). Graham v. John Deere Co., 383 U.S. 1 (1966); KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); MPEP § 2143.

How this builds on the earlier sections. The Patent Summary established that claims 1, 2, and 6 are independent and 3–5 depend from claim 2; that claim 1's distinctive limitations are the benefit-matching subsystem and the FDDI ring; claim 2's is the four named matching subsystems; and claim 6 adds that the ISRS interfaces the transaction-management subsystem. The Prior Art section supplied the 26 U.S. references + NPL and concluded (correctly) that no single reference anticipates an independent claim. This section supplies the § 103 combination theory — and flags one material correction to the Prior Art section's reference characterization (see § 3).

---

1. The legal framework applied

Because the claims "as a whole" must be compared to the prior art, the question is not whether each cited reference was designed to do what the '739 claims recite, but whether the differences between the claims and the prior art are such that the subject matter as a whole would have been obvious at the time of invention to a POSITA. The following MPEP § 2143 rationales do the work here:

• (A) Combining prior-art elements according to known methods to yield predictable results;
• (B) Simple substitution of one known element for another to obtain predictable results;
• (C) Use of a known technique to improve similar devices in the same way;
• (D) Applying a known technique to a known device ready for improvement;
• (E) "Obvious to try" — a finite number of identified, predictable solutions;
• (F) Design incentives and market forces (a demand known in the field);
• (G) Some teaching, suggestion, or motivation in the references (the classic KSR-approved TSM).

Under KSR, the TSM need not be explicit in the references; it may come from "the interrelated teachings of multiple patents," "the effects of demands known to the design community," or the "background knowledge, creativity, and common sense" of the artisan. Critically, KSR rejects requiring "bodily incorporation" of one reference into another — a predictable arrangement of old elements, each performing the function it was known to perform, is obvious.

Anticipation vs. obviousness. I agree with the Prior Art section: no single reference discloses the full-distributed, multi-subsystem architecture, so there is no § 102 anticipation of claims 1, 2, or 6. The claims are, however, in a classic § 103 combination posture.

---

2. Person of ordinary skill in the art (POSITA)

At the May 1997 effective date, a POSITA would have a bachelor's degree in electrical engineering or computer science (or equivalent), and approximately 2–4 years of experience in one or more of: fingerprint image processing / minutiae matching; automated fingerprint identification systems (AFIS); and multi-user database and client/server networking. This is consistent with:

• the specification's own reliance on off-the-shelf componentry — HP 800/700/9000 UNIX workstations, Pentium PC clients, Oracle Forms/SQL, Identix scanners, Video Labs cameras, Matrox frame grabbers, Cogent/Printrak matcher boards — i.e., an ordinary systems integrator's toolkit, not a research breakthrough; and
• the specification's admission that the communication architecture and protocols "are conventional" (TCP/IP, Ethernet, token ring, 10Base-T) and that FDDI is "defined by ANSI and OSI standards" — an express admission that the network fabric was known art.

That admission matters for § 103: the patent's own specification concedes that its most network-specific limitation (claim 1/6's FDDI ring) is a standardized, known technology.

---

3. Reference availability and one material correction to the Prior Art section

⚠️ Contradiction flagged — Fishbine 5,467,403 is not a "single-node/standalone" reference

The Prior Art section characterized Fishbine 5,467,403 as a "portable/self-contained … single-node/standalone" system and listed its gap as "no distributed client/server." Verified primary text contradicts that characterization. The Fishbine '403 abstract and specification state that the apparatus captures a fingerprint image and a photograph ("mug shot") in the field and transmits the images "to a central location for the purpose of providing immediate identity and background checks," expressly contemplating "wireless transmission of fingerprint images captured in the field to a central facility for identity verification using an automated fingerprint identification system" (naming the FBI National Crime Information Center Network), and that images "can be compressed and sent to the police station for comparison against existing mug shot and fingerprint images." Its FIG. 1 architecture is a field image-collection unit → base unit (in a patrol car) → central facility. (Sources: USPTO.report 5,467,403; RPX Insight US5467403A; grant PDF.)

That is, in substance, a distributed biometric capture-at-the-edge / match-at-the-center architecture combining fingerprint and photograph — five months before the '739 filing was even conceived, and more than a year before the filing (i.e., § 102(b) art). This materially strengthens the § 103 case and supersedes the prior section's gap assessment for Fishbine. (Fishbine's own "References Cited" list also contains US 4,843,377 Fuller et al., corroborating the Fuller reference's identity and its pertinence to personal identification/monitoring.)

I still treat Seth 5,566,327 as unverified — a follow-up search returned no content, so I do not rely on it as the sole teaching of the "transaction management subsystem." That element is independently established as old (see § 5).

---

4. Claim-element map (the inventive "gist")

Claim 1 decomposes into:

Claim 2 = (a)–(g) + (i) with (e) expanded to benefit + recidivist + lookout + asylum subsystems, and (h) generalized to "communications network."
Claim 6 = (a)–(h) with (g) expressly "interfacing with the transaction management subsystem," and the (i) clause narrowed to storage/retrieval (omitting the comparison language).

There is no element of claims 1, 2, or 6 that is not, standing alone, a known building block. The only question is whether their arrangement was nonobvious.

---

5. Combination A — Claims 1 and 6 (base distributed architecture)

Proposed combination: Fishbine '403 (primary) + Ott '626 (secondary) + [Seth '327 or the admitted-conventional client/server DB art] + FDDI-as-a-known-standard.

What each reference contributes:

• Fishbine '403 teaches elements (a), (b), (g), and the substance of (i): field capture of fingerprint and photograph, compression, transmission to a central facility for identity verification using an AFIS, and comparison against stored mug shot and fingerprint images. Fishbine is § 102(b) art.
• Ott '626 teaches (d) and (e): minutiae detection (Gabor/Minutia filter pair), automatic classification, a "Products File" repository of fingerprint records, and expressly "records of all fingerprints on file are available for immediate comparison with new (Search Candidate) fingerprints." That is a stored-minutiae database plus a matching engine — the exact "matching controller … for matching fingerprints of individuals to fingerprints stored in the fingerprint database." (https://uspto.report/patent/grant/5,659,626; https://insight.rpxcorp.com/patent/US5659626A.)
• Seth '327 (or, independently, the admitted-conventional DB art) supplies (c): the central facility's records/transaction management.
• FDDI ring (h): a known ANSI/OSI 100 Mbps token-ring LAN — the '739 specification itself says so.

Motivation (TSM and KSR):

1. Express motivation from Fishbine itself. Fishbine identifies the precise problem the '739 patent claims to solve — field personnel need immediate identity/background checks on encountered individuals — and points to central-facility AFIS verification as the solution. A POSITA implementing Fishbine's central AFIS would naturally reach for a known AFIS matcher + minutiae repository to perform the comparison; Ott '626 is that component. The combination is a straightforward "apply a known technique (Ott's matcher) to a known system ready for improvement (Fishbine's central verify)" — MPEP 2143(D).
2. Known methods → predictable results. Building a client/server system in which an edge device captures data and a remote server matches it against a searchable database is the archetypal predictable combination — MPEP 2143(A). Nothing in the claims recites an unexpected result; the asserted benefits (speed, dispersal of capture) are exactly the benefits Fishbine was already pursuing.
3. Design incentive / market force. The specification itself concedes the driving demand: the INS "interacts with and is required to identify millions of persons each year … under severe time constraints." That is MPEP 2143(F).
4. FDDI ring — substitution of a known equivalent (MPEP 2143(B)/(D)). The claim recites a standardized LAN. Where a reference discloses communicating captured biometric images to a central server (Fishbine's wireless/tether link) and the POSITA needs greater bandwidth to move image data (Fishbine itself teaches compression precisely because bandwidth is limited), selecting a known 100 Mbps FDDI ring is a predictable substitution of one known network for another — and the specification admits FDDI is an ANSI/OSI standard. KSR ("a court must ask whether the improvement is more than the predictable use of prior art elements according to their established functions") squarely covers this. Practical note: the '739 specification's own FIG. 2 places clients on a WAN (T1/56 Kbps) and the FDDI ring inside the server — so the claim-1/6 FDDI limitation arguably has weak written-description support (a § 112 issue flagged in the PTAB section). For § 103 purposes this cuts against patentability: the limitation either (i) reads on an admitted standard network technology, or (ii) is indefinite — neither helps the patent owner.
5. Secondary references reinforce (g): compression of fingerprint and photo images is disclosed by Fishbine, and JPEG (1992) and the FBI's WSQ (1993) were established standards; the spec's 15:1 / 35:1 ratios are routine design choices not recited in the claims.

Result: The subject matter of claims 1 and 6 — a predicable arrangement of known elements each performing its known function — is rendered obvious by Fishbine + Ott + known database management + a known standard LAN. Claim 6 is, if anything, more vulnerable: it adds only the express ISRS-to-transaction-manager interface (routine client/server coupling) and drops the comparison clause. Under § 103 these claims "come down to" the predictable combination the Supreme Court addressed in KSR.

---

6. Combination B — Claim 2 (and its dependents 3–5)

Proposed combination: Combination A + Fuller '377 + Gokcebay '329/'043 + Daugman '560 (and/or Hoffman '012/'277).

Claim 2 requires the matching controller to comprise four named subsystems — benefit, recidivist, lookout, and asylum — each presumably tied to its own database. This is a system-level functional arrangement, and the motivation to build it is strong:

1. Benefit — verifying identity of benefit applicants to prevent fraud. Daugman '560 (biometric personal-identification) and Hoffman '012/'277 (biometric personal identification/verification) disclose biometric-based identity verification against stored references; Fuller '377 discloses personal identification/monitoring of subject individuals. Applying known biometric verification as an eligibility gate for a government benefit program is a known, predictable use — MPEP 2143(F).
2. Recidivist — identifying repeat offenders. Fuller '377 (personal identification & monitoring) and the long-standing law-enforcement practice of maintaining separate criminal-history databases keyed to fingerprint identification supply the teaching. Partitioning a master fingerprint repository into a repeat-offender file is a routine database-design step (MPEP 2143(A)).
3. Lookout — individuals with criminal records / warrants. Gokcebay '329/'043 (access control) plus Fishbine's "background checks" via the FBI/NCIC network establish the concept of checking an encounter against a "wanted/lookout" file; claim 4's added recitation ("provides the capability to identify encountered individuals with criminal records") is literally what Fishbine's NCIC background check does.
4. Asylum — verifying identity of asylum applicants to detect fraud. This is the same generic biometric-verification function as the benefit subsystem applied to a different government program, plus Daugman/Hoffman. (Caveat below on the "asylum" label.)

Motivation to combine the four: they are not alternative designs but coexisting agency functions — an immigration/biometric ID system serving enforcement and benefits must, by the field's known practice, check an encounter against multiple authoritative files (criminal, repeat-offender, benefits, application). Running a plurality of specialized matchers, each against its own database, under one controller is the well-understood way to do that (parallel/partitioned search). The '739 specification's own description confirms this is just four instances of the same subsystem ("the lookout workstation 23 and its software and functionality are substantially identical to the recidivist workstation 22"). An arrangement of four structurally identical functional blocks is the paradigm of an obvious combination. MPEP 2143(A), (C).

Result: Claim 2 is the most vulnerable independent claim — it drops the FDDI limitation (reciting only a generic "communications network," which the spec admits is conventional) and adds only additional instances of the already-known matching-subsystem element.

---

7. Dependent claims 3–5 (all depend from claim 2)

Dependent claims add only the nature of the database being searched, not new structure:

Because each dependent claim adds nothing beyond an application-domain label to an element that claim 2 already recites structurally, each is obvious for the same reasons claim 2 is.

---

8. Backup / alternative combinations (redundancy for the invalidity case)

• Swap the primary matcher: substitute Fitzpatrick '936 or Bogosian '272 (fingerprint identification) or the Ratha NPL (FPGA point-pattern minutiae matcher; large-DB real-time matching) for Ott '626 as the "matching" element. The NPL is particularly useful: Khanna (AFIS benchmarking, 1994) and Ratha (real-time matching for large fingerprint databases, 1996) establish that one-to-many AFIS matching against large databases was an identified, predictable solution — MPEP 2143(E). Jain (on-line verification, 1996) supplies the one-to-one "verify" mode recited in the cooperation clauses.
• Swap the architecture reference: Fishbine is the strongest, but Pare '789 (biometric capture/verify) or Price-Francis '252 can carry the capture/storage elements if a tribunal finds any defect in Fishbine.
• Double-patenting, not § 103: the Raytheon siblings US 6,317,544 and US 6,320,974 (both filed 1997-09-25 — after '739's 1997-05-15 filing) are not § 102(e) art against '739, but they are common-ownership candidates for obviousness-type double patenting. Per the earlier sections, neither is in suit.

---

9. Counterarguments a patent owner would raise — and responses

Where the § 103 case is weakest (candid assessment): (i) the "benefit"/"asylum" domain-specific databases — no reference names an immigration-benefits or asylum database, so that element rests on the generalization that labeling a known biometric-verification subsystem by application domain is obvious; and (ii) the exact claim-1/6 FDDI-to-client-workstations topology — no single reference shows FDDI bridging WAN clients to a server (the '739 spec actually shows clients on a WAN and FDDI internal to the server). Both are strong KSR arguments but are the points a patent owner would litigate.

---

10. Bottom line

Summary: No combination of record anticipates claims 1, 2, or 6, but each independent claim — and every dependent claim — recites a predictable arrangement of known elements, and the strongest combinations are motivated by the same problem the patent itself articulates (rapid, dispersed biometric identification with photo verification) that Fishbine '403 (a § 102(b) reference) had already framed. The distinctive "system" features (multi-database matching controller; ISRS; FDDI) are the known, standardized, and admitted-conventional tools of 1997 systems integration. Under KSR and MPEP § 2143(A)–(G), claims 1, 2, and 6, and dependents 3–5, would likely be held obvious.

Confidence and caveats (per the operating rules):

1. Descriptions of Seth '327, Crumpler '207, Price-Francis '252, Fitzpatrick '936, Bogosian '272, Fuller '377, Gokcebay '329/'043, Daugman '560, Hoffman '012/'277, Pare '789 remain inferred from class codes / inventor bodies of work in the Prior Art section and were not individually re-verified here. The load-bearing references — Ott '626 and Fishbine '403 — were verified from primary text, and the Fishbine verification contradicts the prior section's "standalone" characterization (flagged in § 3).
2. The "asylum" element is internally inconsistent in the '739 specification (which also uses "waiver"/"embark"/"trustee" for subsystem 24); that is a § 112 defect that narrows—or voids—claim 5's scope, and it should be pleaded in the alternative, not conflated with the § 103 case.
3. This is attorney analysis, not a tribunal holding. Because the patent expired 2017-05-15 with no litigation or PTAB history (per the earlier sections), this § 103 record is realistically useful only for an ex parte reexam or an invalidity defense if pre-2017 conduct is ever asserted.

Sources: https://patents.google.com/patent/US6018739/en (specification, all 6 claims, legal status); https://uspto.report/patent/grant/5,467,403, https://insight.rpxcorp.com/patent/US5467403A, https://patentimages.storage.googleapis.com/f2/af/b8/5da17ac99cdafd/US5467403.pdf (Fishbine '403 verified text); https://uspto.report/patent/grant/5,659,626, https://insight.rpxcorp.com/patent/US5659626A (Ott '626 verified text).