US 7310734

I'll search for this specific patent number and any litigation/docket references.

Let me run a few more targeted searches.

Let me check for any litigation involving the patent's technology/assignee and any post-issuance proceedings.

Search scope and result

Searches run (web-based, not direct USPTO/PACER API queries):

• US patent 7310734
• "7310734" patent litigation CAFC docket 2026
• "US7310734" / "US 7,310,734" litigation district court
• CAFC 2026 docket "7,310,734" appeal
• USPTO Patent Center 09/775,205 7310734 status

Litigation finding: I found no district-court, PTAB, or CAFC docket naming U.S. Patent No. 7,310,734. The only web hits containing that digit string were unrelated: keyword/query logs embedded in IPR petition exhibits from Roku Inc. v. IOENGINE LLC (PTAB IPR2022‑01552 and IPR2022‑01257), where "7310734" appears merely as a search-string term inside a file-wrapper document for a different patent (U.S. 10,972,584 / 10,447,819). All other "734 patent" hits concern entirely different patents (e.g., 5,371,734; 6,928,734; 9,752,734; 8,684,734).

Caveat: I did not have direct authenticated access to USPTO Patent Center, PACER, or the CAFC docket. Two follow-up queries (targeting "7,310,734" + 3M litigation, and PTAB IPR/CBM petitions) were cut off by a tool limit and did not return results. So my "no litigation found" statement is based on open-web searching only and should be verified against USPTO Patent Center and PACER/CAFC dockets before being relied upon. I have no authoritative information about any 2026 CAFC appeal involving this patent.

Bibliographic summary (per the authoritative full text supplied)

Abstract (verbatim)

"An improved computer network security system and a personal identifier device used for controlling network with real time authentication of both a person's identity and presence at a computer workstation is provided. A new user is registered to a portable personal digital identifier device and, within the portable personal digital identifier device, an input biometric of the user is received and a master template is derived therefrom and securely maintained in storage. A private key and public key encryption system is utilized to authenticate a user registered to the portable personal digital identifier device. The personal digital identifier device verifies the origin of a digitally signed challenge message from the network security manager component. A digitally and biometrically signed challenge response message is produced and transmitted by the personal digital identifier device in response to the verified challenge message."

Plain-language overview of the independent claims

Claim 1 — The personal digital identifier (PDI) device itself

A lightweight, wearable/carryable portable device for controlling network access, used in a network where each workstation has a base unit doing wireless (e.g., IR) communications, and where a central server runs a "security manager" and has network storage.

The device must have:

• (a) a wireless transceiver to talk to the base unit;
• (b) a biometric capture component (fingerprint transducer in the preferred version);
• (c) a processor that (i) checks whether a live-derived biometric template matches a stored master template and emits a "match" signal; (ii) generates its own private key and matching public key and transmits the public key out; (iii) creates digital signatures with that private key; and (iv) verifies, using the security manager's public key, that an encrypted message really came from the security manager (anti-spoofing);
• (d) secure storage holding the master template, the device's private key, and the security manager's public key;
• (e) a power source; and
• (f) a housing.

The device signs and returns a challenge-response message with its private key, but only after the biometric match signal, and it is configured never to transmit the master template or the private key. Critically, claim 1 also recites a network-level behavior: during an active logged-in session, a policy manager component causes a workstation screen to blank out when a second PDI enters the detection envelope, staying blanked until the second device's registered user is biometrically shown to have permission to view the logged-in session's data.

(Analyst note: the screen-blanking limitation is written into the device claim even though it is performed by the workstation/policy manager — an unusual claim-drafting choice worth noting for any claim-construction or infringement analysis.)

Claim 9 — The overall security system

A system for controlling network access at a workstation access point, comprising three cooperating parts:

• A. the PDI described in claim 1 (same transceiver, biometric component, and processor functions — match signal, key-pair generation, signing, security-manager verification — plus secure storage, and prohibition on transmitting the template or private key);
• B. a base unit attached to the workstation that initiates and maintains wireless communications confined to an "envelope" around the workstation (the envelope is sized/shaped to cover anyone close enough to read the screen); and the same screen-blanking rule: during a user's logged-in session, the policy manager directs the workstation to blank the screen when a second PDI is detected within the envelope, until the second user is biometrically identified; and
• C. a central server with access to network storage that uses the security manager and PDI to authenticate the user, where network storage holds the public key corresponding to the PDI's private key.

Claim 17 — The method

A method of controlling network access, where each workstation has a base unit for wireless "envelope-limited" communications with a portable PDI:

• (a) Registration: inside the PDI itself — capture the user's biometric, derive and securely store a master template, generate and securely store a private key, generate the public key and provide it to network storage, and receive/store the security manager's public key.
• (b) Proximity handshake: the base unit transmits a first signal; the PDI automatically responds when inside the envelope, establishing communications.
• (c) Mutual authentication (inbound): the PDI receives a digitally signed challenge ostensibly from the security manager and verifies the origin using the security manager's public key.
• (d)–(e) Local biometric check: the PDI captures a live biometric, derives a template, and locally compares it to the stored master template, emitting a match signal.
• (f) Response: the PDI uses its private key to produce a digitally signed challenge response (after the match) and sends it to the security manager to authenticate the user.
• (g) The authenticated user is permitted network access via the workstation.
• (h) Envelope monitoring / privacy: during the logged-in session, the policy manager blanks the workstation screen when a second PDI enters the envelope, and keeps it blank until the second user is biometrically confirmed to have permission to view the current session's data.

Dependent claims of note (for completeness, not independent): solid-state fingerprint sensor (cl. 3); optical and RF transceivers (cl. 4–5); automatic response signalling (cl. 6); all secure-storage data is by itself non-identifying of the user (cl. 7); a cradle/device holder with a communications connector for tethered (USB) direct connection to a workstation (cl. 8); envelope shaped to cover would-be readers (cl. 16, 18); polling signal (cl. 19); display of identifying user data (cl. 20); and registration of a new user by a registrar in the presence of a guarantor, both biometrically authenticated and all present within the envelope (cl. 21).

Uncertainty / things I could not confirm

1. Docket confirmation is incomplete. No CAFC 2026 (or any) appeal, district-court suit, or PTAB proceeding on U.S. 7,310,734 was surfaced, but two targeted searches were blocked by a step limit and my access was open-web, not the official USPTO/PACER/CAFC systems. Treat "no litigation found" as provisional.
2. Legal status. The only status data I have is the Google Patents field ("Expired – Fee Related," adjusted expiration 2023‑03‑02), which expressly disclaims being a legal conclusion. I could not independently confirm maintenance-fee status in Patent Center. Because the patent appears to have expired, any 2026 CAFC activity would most likely relate to a pre-expiration damages/lookback dispute or a still-running appeal rather than to prospective injunctive relief.
3. Inventor/assignee accuracy rests on the supplied authoritative text and the Golden wiki corroboration; I did not verify the assignment chain in USPTO's Assignment Search.
4. I did not auto-correct any identifier: the patent was analyzed strictly as 7,310,734, application 09/775,205, and the near-miss "734" patents encountered (5,371,734, 6,928,734, 8,684,734, 9,752,734, and the "10,972,584 / 10,447,819" file-wrapper exhibits) were excluded as different patents.

I'll research litigation involving US Patent 7,310,734. Let me run several searches.

Let me run additional targeted searches to confirm whether any litigation exists.

Summary: No litigation found involving U.S. Patent 7,310,734

Based on the searches I was able to complete, I did not find any record of litigation (district court, ITC, PTAB, or CAFC) involving U.S. Patent No. 7,310,734. I am reporting this as "none known," not as a definitive negative, because my search was limited (I hit a tool-call limit before exhausting all databases). Details below.

About the patent

• Patent: U.S. 7,310,734 B2 — "Method and system for securing a computer network and personal identification device used therein for controlling access to network components"
• Application: US 09/775,205; filed Feb. 1, 2001; granted Dec. 18, 2007
• Original assignee: AIT Advanced Information Technologies Corp. → Current assignee: 3M Innovative Properties Co.
• Status: Expired – Fee Related (adjusted expiration Mar. 2, 2023)
• Inventors: Alan Boate, Brian Reed

Cases found — none

What the "7310734" hits actually were

Every search hit containing the string "7310734" was not a lawsuit about this patent. They were:

1. Prior-art search-string excerpts in other patents' prosecution file wrappers, surfaced through PTAB exhibit PDFs — e.g., Roku Inc. v. IOENGINE LLC, IPR2022-01552 and Roku Inc., IPR2022-01257 / IPR2022-01258 (the number appears merely as a search term ("7310734").PN. in an examiner's EAST/PatBase query list). These are unrelated to the '734 patent's use.

2. Unrelated patents ending in "734" that the searches returned as noise, including:

   • U.S. 7,804,734 (Samsung v. NVIDIA, IPR2015-01068) — memory strobe buffer
   • U.S. 6,655,733 (Lear Corp. v. NHK, No. 2:13-cv-12937, E.D. Mich.)
   • U.S. 7,741,734 (WiTricity/MIT v. Momentum Dynamics, D. Del.)
   • U.S. 5,243,734 (Hoover v. Bissell) — vacuum cleaner '734
   • U.S. 12,133,734 (Bardy Diagnostics v. iRhythm) and others.

   These are all different patents; per your instruction I did not attribute any of them to U.S. 7,310,734.

Confidence and caveats

• Confidence that no litigation has been publicly reported: Moderate-to-high. The patent is a 3M-held, fee-expired asset, and it did not appear as an asserted patent in any district court, ITC, or PTAB proceeding in the results.
• Caveats: (a) My searches were cut off by a step limit before I could fully query PACER, the CAFC opinion database, or the Unified Patents litigation portal directly; (b) litigation databases are not always complete or indexed for a given patent number; (c) a declaratory-judgment or licensing action that is not docketed under this patent number could exist.
• I am not aware, from training data, of any litigation involving U.S. 7,310,734. If you want a higher-confidence negative, the recommended next step is a direct PACER/Unified Patents/Docket Navigator query by patent number plus a name search for "AIT Advanced Information Technologies" and "3M Innovative Properties."

Bottom line: No known litigation involves U.S. Patent 7,310,734. If you require a certified "no cases" determination, that must be confirmed against PACER and the Unified Patents litigation portal directly rather than inferred from the above.

I'll verify the ODP result with independent searches before concluding.

Let me run a couple more targeted checks to be thorough.

One final check on the CBM/post-grant side and any party-page listing.

Proceedings overview

Total AIA trial proceedings on file for US 7,310,734: zero. The canonical USPTO Open Data Portal list returns no IPR, PGR, or CBM proceeding, and independent web searches for a petition, institution decision, Final Written Decision, or appeal naming this patent returned nothing — so the breakdown is 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denials; the bottom line for a defendant is that no PTAB panel has ever touched this patent, so there is no invalidation record to lean on — but the patent expired on or about 2023-03-02, which is a far better defense than any IPR outcome would be.

Proceedings

No proceedings to enumerate. There is no {PROCEEDING_NUMBER} to report for US 7,310,734.

Verification trail (what I checked and what I found):

⚠️ False-positive warning. Searches for the string 7310734 return several other matters that are not proceedings on this patent — e.g., a Roku, Inc. IPR exhibit file wrapper for US 10,972,584 that merely cites US 7,310,734 in a prior-art reference list. Likewise US 7,253,731, US 8,684,734, US 7,312,734 (McNeill), and US 8,845,731 are different patents that appear in the search results. Do not confuse any of these with a proceeding on US 7,310,734.

Strategic summary

Claim status: all 21 claims are UNTESTED. Claims 1, 9, and 17 are the independent claims (claim 8 is a device-holder combination claim referencing claim 1; claims 2–7 depend from claim 1, 10–16 from claim 9, and 18–21 from claim 17). None has been canceled, confirmed, or even challenged at the PTAB. There is no narrowing certificate, no FWD, and no adverse judgment to work from. The only claim-level changes on record are prosecution-side: as issued, claim 1 and claim 9 both carry the "policy manager component … blank out a respective screen when a second personal digital identifier device is detected at a location within an envelope" limitation, which reads like a late-stage amendment to overcome art — worth pulling the file wrapper to confirm, but it is not a PTAB outcome and I am not asserting it as one.

Estoppel landscape: clean, and irrelevant. Because there is no IPR/PGR/CBM, no § 315(e)(2) estoppel attaches to anyone. No petitioner is barred from raising anything, and no defendant inherits a narrow "could have raised" record. Practically, this cuts both ways: there is also no SAS-era ground that a prior petitioner already litigated and lost, so you cannot piggyback on someone else's work product or a Board's claim construction. Any invalidity theory you build would be first-instance, from scratch. Note also that a PGR is statutorily unavailable here — the '734 patent has a 2001-02-01 priority date, far before the 2013-03-16 AIA cutoff — and CBM review required claims directed to a financial product or service (and its petition window sunset in 2020), so IPR is the only realistic AIA vehicle for this patent.

Pattern signals: none to read. There is no repeat petitioner, no Unified Patents or other defensive-aggregator filing, and no evidence the patent owner litigated or appealed anything at the Board. The absence is meaningful: well-asserted patents of this vintage (a 2001-filed biometric/PKI network-access patent, in the crosshairs of the entire 2010s authentication industry) almost invariably attract at least one IPR. That none exists suggests US 7,310,734 was never meaningfully asserted in a campaign. Combined with the recorded status — "Expired - Fee Related," adjusted expiration 2023-03-02 (per Google Patents, which expressly labels its legal-status and expiration data as assumptions and not legal conclusions) — the likely explanation is simple: the patent lapsed without a monetization effort.

Two background facts a defendant should confirm independently: (1) ownership moved from AIT Advanced Information Technologies Corporation to 3M Innovative Properties Company by assignment recorded 2003-06-04, so any demand letter should be traced to the current owner of record; and (2) the patent's term is a live question — 20 years from the 2001-02-01 filing plus any PTA. The listed 2023-03-02 adjusted expiration implies roughly two years of adjustment, but that figure is a third-party estimate. Verify the expiration date against the face of the patent and the ODP assignment/transaction history before relying on it.

Recommended next steps

1. Lead with expiration, not with invalidity. There is no PTAB record to cite — you cannot point a court to a FWD canceling claims 1–9, because none exists. Your strongest, cheapest dispositive argument is that US 7,310,734 is expired and its claims cannot be infringed by post-expiration conduct (damages, if any, are confined to the pre-expiration window). Confirm the exact expiration date from the printed patent's PTA notice and the ODP legal-status record — the Google Patents page lists "Adjusted expiration 2023-03-02" but flags it as an assumption.

2. If you need an invalidity posture in parallel, treat it as a first-instance IPR. No estoppel exists, no ground has been beaten to death, and IPR is your only AIA option (PGR unavailable; CBM program closed). The pre-AIA § 102/§ 103 art of record is substantial — the patent cited 55 references, including US 5,229,764 (Matchett, "Continuous biometric authentication matrix"), US 6,088,450 (Intel, challenge/response authentication), US 6,016,476 (IBM, portable biometric + digital certificate), US 5,623,552 (Cardguard, self-authenticating fingerprint card), and US 6,357,889 / WO 1999/056429 (Identix). Whether the "envelope"-based screen-blanking limitation added to claims 1, 9, and 17 gives the claims a meaningful distinguishing feature is the key § 103 question.

3. Periodically re-run the ODP check. There is no institution deadline, no oral hearing, and no statutory FWD due date to track, because there is no proceeding. But if the patent is being asserted against you now — a $10M+ damages demand would make a resurrected assertion rational — watch for an IPR filed by a co-defendant or by a defensive aggregator. Pull the file wrapper at USPTO PatentCenter for Appl. No. 09/775,205 to see whether the claim 1 / claim 9 blank-out language was a prosecution amendment or a post-issuance certificate, and to confirm no ex parte reexamination decision lurks in the record (I found none, but the ODP block covers AIA trials only and would not surface a reexam).

4. Confirm current ownership before responding to any demand. Assignment history in the record shows AIT → 3M (2003-06-04). If your demand letter comes from a non-3M entity, verify the chain of title through the USPTO Assignment database before conceding standing or negotiating.

Sources: Google Patents US7310734B2 · USPTO PTAB E2E · PTAB Decisions · USPTO PatentCenter · USPTO Assignment Search

Limitations of this report: The ODP ingest is authoritative for AIA trials and returned an empty set. Web searches surfaced no additional or recently-filed proceeding, but absence of evidence in a search is not proof of non-existence — a very recently filed petition may not yet be indexed. I did not locate any CourtListener or CAFC docket entry for this patent, and I am not fabricating one. If you need certainty, run a party-name query in PTAB E2E for "3M Innovative Properties Company" and check the printed patent's file wrapper directly.

I'll start by cross-checking the assignment record against multiple sources, since Google Patents' legal-events view is often incomplete.

Good — one lead already: the patent appears in the "3M-AiT" portfolio profile. Let me dig into the corporate chain and look for any litigation or later transfers.

Ownership Reconstruction — US 7,310,734 B2

Data caveat up front (important): I was unable to retrieve reel/frame numbers or recorded correspondents for this patent. The USPTO Assignment Center and the legacy assignment portal are JavaScript/database applications that are not exposed to web crawling, and the USPTO's legacy PDF archive (legacy-assignments.uspto.gov) did not surface this patent in my searches. What I can verify is the Google Patents legal-events record (which is derived from the same assignment data), plus the public corporate history of the parties. Where I do not have a value I say so rather than guessing. Every reel/frame field below is therefore marked not retrieved — verify directly at https://assignmentcenter.uspto.gov/ (search by patent number 7310734) or https://assignment.uspto.gov/patent/index.html.

Inventors

Notes on pattern:

• Both named inventors executed an assignment of their rights to AIT Advanced Information Technologies Corporation on 2001-02-01, the same date the application was filed — i.e., a standard, contemporaneous employee invention assignment. There is no evidence of inventors departing within 12 months of filing, and no re-assignment of inventor-held rights.
• This is not a case of an independent-inventor patent later sold to a monetizer. The inventors were employees of an operating security-document company.
• (I could not independently confirm job titles; "employer" is inferred from the assignment instrument cited in the Google Patents legal-events table.)

Original assignee

As printed on the issued patent (18 Dec 2007): 3M Innovative Properties Company, a Delaware corporation and wholly-owned IP-holding subsidiary of 3M Company, 3M Center, St. Paul, Minnesota.

Predecessor/owner at filing: AIT Advanced Information Technologies Corporation (Ottawa, Ontario) — a TSX-listed reporting issuer that designed, developed and marketed issuance systems for secure ID and travel documents (passports, visas, driver's licences) and border/immigration inspection systems, including the "VeriMe" product line. It was an operating company, not an IP shell.

• Did AiT ship a product embodying the claims? It shipped secure-document issuance and border-control systems. The claimed subject matter (wireless personal digital identifier device + biometric + PKI network access control) is plausibly within AiT's development roadmap (the application is a PCT/CA2002/000106 filing), but I have no evidence of a commercial product reading on the specific claims — I will not assert that.
• AiT's status: acquired via merger by 3M Canada Company, effective 19 July 2002; shareholders received C$2.88/share, aggregate consideration ≈ C$42 million; AiT became a wholly-owned subsidiary operating as 3M-AiT Ltd., and is today described in a Canadian regulatory record as "AiT Advanced Information Technologies Inc. (now 3M Canada Company)." Pre-merger AiT had recorded a significant loss for FY ended 30 Sep 2001 and had retained an M&A advisor to find a strategic buyer — a solvent strategic sale, not a bankruptcy.
• 3M / 3M Innovative Properties Company status: operating; 3M remains a large NYSE-listed diversified manufacturer (Security Systems / Identification & Authentication business; later added SPSL (2006), Rochford Thompson (2007), Cogent Systems (2010)). The asserted patent expired 2 Mar 2023 for failure to pay maintenance fees ("Expired – Fee Related").

Assignment timeline

Reel/frame and correspondent could not be retrieved for any entry. Dates and parties below are from the Google Patents legal-events table, which mirrors USPTO assignment data. Do not treat any reel/frame number as verified — none is asserted.

• 2001-02-01 (executed) / recorded 2001-02-01 — Reel not retrieved / not retrieved

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: Alan Boate; Brian Reed
  • Assignee: AIT Advanced Information Technologies Corporation
  • Correspondent: not retrieved
  • Context: contemporaneous inventor-to-employer assignment at filing (original ownership).

• 2003-06-04 (recorded) — Reel not retrieved / not retrieved

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: "American Electronic Sign Company"; "ATT Advanced Information Technologies Corporation" [sic — the Google Patents record renders the AiT name this way; it almost certainly denotes AIT/AiT Advanced Information Technologies Corporation]
  • Assignee: 3M Innovative Properties Company
  • Correspondent: not retrieved (3M typically records correspondent as its own IP department at 3M Center, St. Paul, MN; a trademark-side 3M merger assignment, reel 2502/0547, lists correspondent James F. Voegeli, 3M Center, Bldg. 220-11W-01, St. Paul MN — noted only as an adjacent data point, not as this patent's correspondent)
  • Context: post-merger consolidation — the 19 Jul 2002 3M–AiT merger ($42M) flowed the AiT portfolio into 3M's IP-holding subsidiary; recording lagged the closing by ~11 months.

• 2007-12-18 — patent granted/issued (not an assignment).

• 2023-03-02 — adjusted expiration; patent lapsed for non-payment of maintenance fees (not an assignment).

No assignment after issuance. There are no post-grant transfers, no security agreements, no release, and no recorded change-of-name on this patent in the sources available to me.

Timeline diagram

timeline
    title Ownership of US 7310734
    2001 : Application filed 01 Feb
         : Inventors assign rights to AiT of Ottawa
    2002 : 3M Canada acquires AiT in merger
    2003 : Assignment recorded to 3M Innovative Properties
    2007 : Patent issues on 18 Dec
    2023 : Patent expires for unpaid maintenance fees

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The chain moves operating company → operating company (AiT → 3M, both product businesses). No "IP / Holdings / Ventures"-style single-purpose assignee appears; the assignee of record is 3M Innovative Properties Company, a long-established captive IP subsidiary of a Fortune-500 operating company, not a revenue-less licensing shell.

2. Known asserter in the chain — not present. Neither AiT nor 3M matches any entity on the standard NPE lists (Acacia, Marathon, IV, IPNav, Wi-LAN, Conversant/Mosaid, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, etc.). 3M is an operating company that does assert patents (e.g., 3M's plasma-fluorination litigation against TransWeb, discussed in Fed. Cir. appeals), but as a competitor suit, not an NPE campaign, and not on this patent.

3. Repeat correspondent across the chain — unclear / not determinable. I could not retrieve the correspondent of record for either event, so I cannot assess recurrence. I explicitly decline to call this on naming alone. (Action item for a manual Assignment Center pull: confirm whether both recordings name 3M's own St. Paul IP department — if they do, that is normal captive-IP-house practice, not an NPE tell.)

4. Cascading transfers — not present. Only two recorded events, ~16 months apart (2001-02-01 and 2003-06-04), and the second is a single merger-step consolidation — not a rapid chain of LLC-to-LLC hops.

5. Pre-litigation transfer — not present. I found no infringement litigation naming US 7,310,734 in any source. With no suit, there is no transfer "arranged to enable assertion."

6. Bankruptcy fire-sale — not present. AiT was acquired in a negotiated, solvent all-cash merger (~C$42M) after a loss-making year — a strategic sale, not a Chapter 7/11 asset sale.

7. Privateering — not present. No evidence of 3M transferring the patent to an affiliate-NPE to assert on 3M's behalf; the patent simply remained with 3M and lapsed.

8. Defensive aggregator (anti-NPE) — not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN; it terminates at an operating company and then lapses.

Verdict

Insufficient data.

The complete ownership record shows only two events: the inventors' 2001-02-01 assignment to AIT Advanced Information Technologies Corporation, and a 2003-06-04 assignment of the AiT portfolio to 3M Innovative Properties Company following the 19 July 2002 3M–AiT merger (C$42M). There are no post-issuance assignments, no NPE-list assignee, no litigation, and no assertion activity, and the patent lapsed 2023-03-02 for unpaid maintenance fees. Because no NPE signal is present but I could not verify reel/frame or correspondent fields against the Assignment Center, the only honest call is Insufficient data — this is the inverse of an NPE finding: a straightforward operating-company (inventor → AiT → 3M) chain with no monetization layer ever attached. If any category were available for "operating-company-owned, non-asserting, expired," that would be the more precise label.

Verify at: https://assignmentcenter.uspto.gov/ (search patent 7310734) — the reel/frame numbers and correspondents I could not retrieve (and which would be needed to fully clear signal #3) are exposed there.

I'll analyze the prior art citations for US 7,310,734. Let me first verify the patent record and then research the key cited references.

Let me research additional key references, especially those relating to proximity-based display control and wireless authentication.

Prior Art Analysis — U.S. Patent No. 7,310,734 B2

0. Scope, method, and a required caveat

Patent verified. US 7,310,734 B2, "Method and system for securing a computer network and personal identification device used therein for controlling access to network components"; application US 09/775,205; filed 2001‑02‑01; granted 2007‑12‑18; applicants/inventors Alan Boate and Brian Reed; original assignee AIT Advanced Information Technologies Corp., current assignee 3M Innovative Properties Co. (Google Patents record: https://patents.google.com/patent/US7310734/en; also uspto.report/patent/grant/7310734). The number was searched literally as 7310734; results for other "…734" patents (e.g., 7,804,734; 5,243,734) are NOT this patent and are excluded.

Source of the reference list. The authoritative full text you supplied contains the patent's own bibliography — "Citations (55)" — i.e., the references of record cited against this patent. I analyzed that list (52 entries are actually enumerated in the supplied text; the fetch appears to have truncated the final entry, so the list below is the 52 I can read, and I flag where the count is short of the stated 55). Because the reference list is a prosecution artifact, note two things:

• §102 vs §103 caution (important and honest): A reference anticipates a claim under 35 U.S.C. §102 only if it discloses every element of that claim in a single document. As shown below, no single cited reference discloses the full combination recited in independent claims 1, 9 and 17 — namely (i) an on-board biometric with the master template stored on the portable device, (ii) the portable device itself generating its own public/private key pair, (iii) mutual challenge/response authentication of both the device and the security manager, (iv) a proximity detection envelope sized to viewing range, and (v) a policy-manager-driven screen blank when a second device is detected. Consequently most of these citations function as §103 obviousness references (alone or in combination), and I say so per reference. Where the user asks "which claim(s) it potentially anticipates under §102," I answer with the claim(s) most exposed to that reference, and I state the §102/§103 basis explicitly.
• Not prior art: the Google Patents "Definitions" box ("the PDI 10 is able to verify a user… wholly on‑board the PDI 10") is Google's own claim‑charting extract from this patent's description, not a prior‑art reference. It is excluded.

Search limitation: I reached the tool‑call limit before I could run the full USPTO PatentCenter/Public‑PAIR citation listing and confirm the last 3 references of record (52 read vs. 55 stated). References below the 52nd entry may therefore be missing from this analysis; flagging per your "if you don't know, say so" rule.

TIER 1 — Most relevant references (closest to the claimed combination)

1. US 6,088,450 A — Intel Corp. ("Davis")

• Citation: US 6,088,450 A; priority/filed 1996‑04‑17; published (granted) 2000‑07‑11; inventor/assignee Intel Corp.; "Authentication system based on periodic challenge/response protocol."
• Description (verified): A wireless authentication system that keeps a node (PC) in an operational state only when a user-borne token is within a predetermined distance of the node. The security device issues a Challenge message to the token; the token returns a Response message only if it is within range; a time-out counter disables the node when no authentic reply arrives; the challenge/response is re-issued periodically to confirm the user is still present. Challenge/response may use public-key (RSA) or symmetric algorithms. (Google Patents: https://patents.google.com/patent/[US6088450A](/patent/US6088450A))
• Potential §102 exposure: Claims 1, 6, 9, 12, 13, 17, 19 — specifically the wireless challenge/response architecture, the automatic response signal when in proximity (claim 6/12), periodic polling to confirm continued presence (claim 13/19), and proximity-gated operational state of the workstation. This is the single closest reference on the proximity + challenge/response + node-state axis. However, Davis lacks the biometric acquisition/on-board template match and the on-board key-pair generation, so it is best characterized as a §103 backbone reference for the authentication architecture rather than a full §102 anticipation of the independent claims.

2. US 6,594,762 B1 — Ericsson ("display based on separation")

• Citation: US 6,594,762 B1; priority/filed 1999‑05‑05; granted 2003‑07‑15; assignee Ericsson Inc.; "Methods and devices enabling displays of electronic devices based on separation thereof." (Google Patents: https://patents.google.com/patent/US6594762)
• Description (verified): An electronic device (100) and a remote device (110) cooperate so the display is enabled only when the two are within an adjustable transmit range (e.g., 4 ft.) and is automatically disabled (blanked) when the remote device moves beyond that range; reception of an authentication code / pseudo-random code distinguishes the authorized remote device. The stated purpose is to protect displayed data from unauthorized viewers.
• Potential §102 exposure: The "envelope"/proximity‑controlled display elements of claims 1(h)/1, 9(B), 16, 17(h), 18 and the auto‑response/regular‑signal elements of claims 6, 12. Ericsson's stated rationale (protecting the screen from unauthorized viewers by range) maps very closely onto the envelope concept. Difference: Ericsson disables the display when the authorized user's own remote device leaves; claim 1 requires blanking when a second, different user's device enters. That distinction is the likely point of novelty, so treat as a strong §103 reference, not clean §102 anticipation.

3. US 6,016,476 A — International Business Machines ("Maes et al.")

• Citation: US 6,016,476 A; priority/filed 1997‑08‑11; granted 2000‑01‑18; assignee IBM; "Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security." (Google Patents: https://patents.google.com/patent/[US6016476A](/patent/US6016476A); family EP 1004099 B1.)
• Description (verified): A portable device (PDA) with a local CPU that performs biometric verification (voice/fingerprint) on the device, stores a master biometric reference, and downloads/holds a temporary digital certificate from a central server; the certificate must be present to release stored data. Supports wireless (RF/IR) communication.
• Potential §102 exposure: Claims 1, 2, 7, 9, 10, 14 — portable device with on-board biometric verification and digital-certificate/crypto security, plus the "non‑identifiable data on the device / identity held centrally" theme of claims 7/14. Difference: IBM issues a certificate from a server rather than having the device generate its own key pair (claim 1(c)(ii)), and lacks the proximity-envelope and second-device blanking. §103 reference.

4. US 5,623,552 A — CardGuard International ("Lane")

• Citation: US 5,623,552 A; filed 1995‑08‑15 (continuation of 1994‑01‑21); granted 1997‑04‑22; assignee CardGuard International; "Self-authenticating identification card with fingerprint identification." (Google Patents: https://patents.google.com/patent/[US5623552A](/patent/US5623552A))
• Description (verified): A self-authenticating ID card with an on‑card fingerprint sensor, an on‑card memory that permanently stores the user's fingerprint ("master"), and an on‑card authenticator that compares a freshly sensed fingerprint with the stored one and produces an authentication signal on match. Emitted authentication/verification via display/audio. It is one of the seminal "biometric-on-a-token" references (also cited as "X" art in the ISR of WO 02/075665, confirming its core status).
• Potential §102 exposure: Claims 1(b), 1(c)(i), 1(d), 2, 3, 7 — on-board biometric transducer, on-board master template storage, and on-board matching signal. Difference: no wireless transceiver, no key-pair generation, no challenge/response, no envelope. §102/§103 reference for the biometric sub-elements only.

5. US 4,582,985 A — Loefberg ("Data carrier")

• Citation: US 4,582,985 A; priority 1981‑03‑18; granted 1986‑04‑15; inventor Bo Loefberg; "Data carrier." (Family EP 0085680, WO 82/03286.)
• Description: Earliest cited reference; a portable data carrier that stores biometric (fingerprint) data for verifying the bearer — the foundational "biometric token" concept. Also cited as "X" art in the WO 02/075665 ISR (claims 1,3,11,12,14 of that case).
• Potential §102 exposure: Claims 1, 2, 3 (biometric-bearing portable carrier). Antedates everything else; background/§103 reference for the biometric-carrier concept.

TIER 2 — Portable biometric identification devices and methods

TIER 3 — Wireless / proximity / RFID / token communication

TIER 4 — Data/key security, PKI, and secure transactions (crypto sub-elements)

TIER 5 — Healthcare / medical-records context (the patent's stated field of use)

Completeness note: the patent's bibliography header reads "Citations (55)," but the supplied text enumerates only the 52 entries above (the 52nd, US 6,607,136 B1, is cut off mid-citation). The remaining ~3 references of record were not readable in the supplied text and I could not retrieve them before the tool limit; I flag this rather than guess.

5. Bottom line for §102 purposes

• No cited reference, standing alone, anticipates independent claims 1, 9, or 17. Each independent claim requires a concurrent combination of (a) on‑board biometric template storage + live match, (b) device‑generated key pair, (c) mutual security‑manager/device challenge‑response with signed messages, (d) a proximity envelope sized to viewing range, and (e) policy‑manager blanking on detection of a second device. The cited art supplies these elements only piecemeal.
• Strongest single-reference §102 candidates for dependent/sub-elements:
  • US 5,623,552 (CardGuard) → claims 1(b), 1(c)(i), 1(d), 2, 3, 7 (on‑board biometric transducer + stored master + matching signal).
  • US 6,088,450 (Intel/Davis) → claims 1, 6, 9, 12, 13, 17, 19 (wireless proximity challenge/response, auto‑response, periodic polling) — but missing biometric/key‑generation, hence realistically §103.
  • US 6,594,762 (Ericsson) → claims 1(h), 9(B), 16, 18 (automatic display disable based on device separation) — but keyed to the authorized device leaving, not a second device entering.
  • US 6,016,476 (IBM/Maes) → claims 1, 2, 7, 9, 10, 14 (portable on‑board biometric + certificate security; non‑identifiable data on device).
• Most likely §103 combinations the examiner would (and effectively did) rely on: Davis (US 6,088,450) + CardGuard (US 5,623,552) + IBM (US 6,016,476) for the device/system claims; Ericsson (US 6,594,762) or Davis for the proximity-blank/envelope claims; and any of Lucent US 6,577,734 / N‑Able US 6,092,202 / Palage US 6,018,801 for the key-management/signature claims.

If you want, I can (1) re‑run the search to retrieve the final ~3 truncated references of record, and (2) produce claim‑element‑by‑claim‑element §102/§103 charts against the Tier 1 references.

I'll ground my obviousness analysis by verifying the disclosures of the key examiner-cited references in the patent's Prior Art section.

Obviousness Analysis — U.S. Patent No. 7,310,734 under 35 U.S.C. § 103

Patent under analysis: U.S. 7,310,734 B2 ("Method and system for securing a computer network and personal identification device used therein for controlling access to network components"), App. No. 09/775,205, filed Feb. 1, 2001, granted Dec. 18, 2007; inventors Alan Boate and Brian Reed; original assignee AIT Advanced Information Technologies Corp., current assignee 3M Innovative Properties Co.

Note on prior sections: Per the litigation summary previously generated, no litigation (district court, ITC, PTAB, or CAFC) was identified involving this patent, and it is Expired – Fee Related with adjusted expiration Mar. 2, 2023. I build on that here only in the "Secondary Considerations" section and do not repeat it.

Sources used: The patent text and the Prior Art sections of the Google Patents page (the 55-item "Citations" list, plus background/cited-by material). I verified the disclosures of five of the most load-bearing references by live search (US 6,016,476; US 6,088,450; US 6,594,762; US 6,353,889; US 5,960,085 family). Mappings for references I could not pull full text for are marked [provisional]. Because the task instructs me to use the Prior Art section, I do not introduce art outside it.

I. Legal framework and assumptions

1. Statute. The application has a U.S. filing/priority date of Feb. 1, 2001, so pre-AIA § 103(a) governs. A reference is § 102(b) art if patented/published before Feb. 1, 2000; a U.S. patent granted on a U.S. application filed before Feb. 1, 2001 is § 102(e)(2) art regardless of its grant date.
2. Standard. Graham v. John Deere, 383 U.S. 1 (1966); KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). The obviousness inquiry asks whether the claimed subject matter as a whole would have been obvious to a PHOSITA at the time of the invention, with a reasoned articulation of why the references would have been combined (MPEP §§ 2141–2144, exemplary rationales (A)–(G)).
3. PHOSITA (circa Feb. 2001). A person with a bachelor's degree in electrical engineering or computer science and 2–3 years of experience in network access control, cryptography, and biometric authentication, or equivalent experience. This is a mature, highly interdisciplinary art — evidenced by the patent's own classification set (H04L 63/0861 biometric authentication; H04L 63/0853 additional device/smartcard; H04W 12/065 continuous authentication; G16H 10/60 patient records).
4. Claim construction of the pivotal terms (construed in light of the specification and its Google Patents "Definitions" entry):
   • "personal digital identifier device" (PDI) — a lightweight, wearable/carryable token with a transceiver, biometric sensor, processor, secure storage, power source, and housing.
   • "secure storage" — storage for the master template, the generated private key, and the security manager's public key; the device must prevent transmission of the template and private key (claim 1, final clause).
   • "envelope" — the spatial region of base-unit/PDI wireless communication, configured to approximate "the ability of the human eye to read the display screen."
   • "security manager component" / "policy manager component" — server-side functional modules; these are labels for functions and do not by themselves add patentable weight, but the substantive acts they perform (mutual authentication; permission-gated screen blanking) do.
5. The patent's own admission. The Background expressly concedes that (i) password-only systems are vulnerable, (ii) token/smart-card systems "do[] not guarantee that the authorized user is actually present," and (iii) any use of a central server to validate a presented biometric introduces a security weakness because the biometric must be transported. This is a judicial-admission-style roadmap that frames the invention as an improvement/combination of known elements rather than a new principle, which materially strengthens a § 103 case.

II. Prior-art qualification of the cited references

Caveat: Each reference must be independently date-qualified. Publications appearing only in the "Cited By (56)" and "Families Citing this family (169)" lists carry priority dates after Feb. 1, 2001 and are therefore not available for a § 103 rejection (e.g., the Privaris, Proxense, and JPMorgan documents). Only the 55 "Citations" are presumptively prior art.

III. The claimed subject matter, element by element

Claim 1 (the PDI) — mapping

Claim 9 (system) — additional elements

Claim 17 (method) — additional elements

Claim 21 (registration protocol) — additional elements

IV. Grounds of rejection

Because the independent device, system, and method claims recite the same core combination, the grounds below are stated once and applied to the corresponding claims.

Ground 1 — the principal combination

Claims 1–7 and 9–16 would have been obvious over Maes (US 6,016,476) in view of Davis (US 6,088,450), further in view of de la Huerga (US 5,960,085), and further in view of Linge (US 6,594,762).

• Maes supplies the portable device with on-board biometric verification and public/private-key ("digital certificate") security, a memory storing the user's biometric/personal data, and RF/IR wireless capability.
• Davis supplies the wireless, worn/carried token that authenticates by a periodic challenge/response with the node, the operational/non-operational control based on proximity, and — critically — claims 6, 23, and 28 already recite a biometric master-template comparison performed in the token. Davis therefore supplies the "challenge message → signed challenge response → access" spine of claim 1 nearly verbatim, plus the "envelope"/proximity concept ("predetermined distance").
• de la Huerga supplies the missing security-critical refinements that the '734 patent itself treats as the point of novelty, namely (i) the PDI verifying the origin of the challenge using the security manager's public key before responding, and (ii) never transmitting the biometric template or private key off the device.
• Linge supplies the automatic display disable/enable based on an authenticated proximity reply signal with an adjustable range, which corresponds to the "envelope"-triggered blanking of claim 1's final "wherein" clause and claim 9's and 17(h)'s blanking limitations.

Result: every element of claim 1 (and the parallel elements of claims 9 and 17) is disclosed or suggested, and the remaining differences (e.g., calling the server modules "security manager" and "policy manager," or calling the proximity region an "envelope") are naming/architectural choices that do not distinguish over the art.

Ground 2 — secondary combination (avoids over-reliance on any one reference for the blanking clause)

Claims 1, 9 and 17 would have been obvious over de la Huerga (US 5,960,085) in view of Maes (US 6,016,476) and Linge (US 6,594,762). Here de la Huerga is the primary reference for the badge/PDI, the on-badge biometric, the private-key-never-transmitted rule, the mutual authentication, and the polling/blanking behavior; Maes supplies the digital-certificate/key architecture and the "non-identifiable data on the device" design; Linge supplies the proximity-triggered display control and the adjustable envelope.

Ground 3 — dependent-claim grounds

• Claims 2, 10 (transducer): US 6,353,889; US 4,582,985; US 5,623,552.
• Claim 3 (solid-state fingerprint sensor): US 5,623,552 / US 4,582,985; US 6,353,889 [provisional as to "solid-state non-optical"].
• Claim 4 (optical/IR transceiver): US 6,016,476; US 5,960,085 (IrDA); US 6,353,889.
• Claim 5 (RF transceiver): US 6,088,450 (radio-frequency format); US 6,353,889.
• Claim 6 and 12 (automatic response to a base-unit signal): US 6,088,450; US 6,594,762 ("transmitting a second signal from the remote device responsive to receiving the first signal").
• Claims 7 and 14 (all stored data non-identifiable): US 5,960,085 (personal biometric indicia never "given up" to an external system).
• Claim 8 (device holder/cradle with a communications connector): US 6,016,476 (serial/parallel port peripheral coupling); US 4,816,653 / 4,816,654 (card reader/writer) [provisional].
• Claim 11 (workstation is a PC): US 6,088,450 (node = computer).
• Claim 13 (plurality of PDIs/BUs with polling): US 6,088,450 (periodic re-issuance of challenges); US 5,960,085 (periodic recommitment polling).
• Claim 15 and 20 (display user-identifiable data upon detection/identification): US 5,960,085; US 6,040,783 [provisional].
• Claims 16 and 18 (envelope shaped to encompass the observer's reading range): US 6,594,762 (adjustable transmit range) + the admitted problem of unauthorized observers in the '734 Background; design choice under In re Kuhle / MPEP 2144.03.
• Claim 19 (polling signal to confirm continued presence): US 6,088,450; US 5,960,085.
• Claim 21 (registrar + guarantor, biometrically signed voucher, all within the envelope): US 5,960,085 + US 6,040,783 + WO 1999013415 A1 (see § VI).

V. Why a PHOSITA would have combined these references (KSR rationales)

1. Same field of endeavor and common problem (MPEP 2141.01(a)). All of Maes, Davis, de la Huerga, Linge, and Mytec are directed to authenticating a human being to a machine or network using possession-plus-identity credentials. They are combinable because they address the same deficiency the '734 Background admits: passwords can be stolen, tokens can be lost or stolen, and central-server biometric validation is insecure because the template must travel.

2. Predictable combination of known elements (KSR; MPEP 2144(A)). Combining (i) a portable token with a wireless transceiver (Davis, Mytec, de la Huerga), (ii) an on-device biometric sensor with a device-resident master template (Maes, Mytec, de la Huerga, Cardguard, Loefberg), and (iii) public/private-key challenge/response (Maes, Davis, de la Huerga) yields nothing more than the expected result: the user must both possess the device and be the enrolled person. Davis had already claimed the biometric-plus-token combination (claims 6, 23, 28), which is powerful evidence that the combination was within the ordinary skill level and not the product of hindsight. No unexpected result is recited; the patent claims no surprising performance data.

3. Design incentive expressly stated in the references (MPEP 2144(F)). Davis's own background recites the problem that "the user accesses his or her personal computer and leaves the personal computer unattended … without removing the card," and the solution of "a wireless authentication system to control an operating state of a first node based on the proximity of an authorized user." De la Huerga's background recites the identical loss/theft problem and expressly proposes a fingerprint-enabled badge to solve it. A PHOSITA reading these side-by-side would have been led, not diverted.

4. Known technique to improve a similar device in the same way (MPEP 2144(C)). Linge's proximity-triggered display enable/disable is a known technique for protecting displayed data from unauthorized viewers; applying it to the workstation of Davis's proximity-authenticated token to blank the screen when a second token enters the detection region is the use of a known technique to improve a similar device in the same way.

5. Substitution of one known credential-carrying form for another (MPEP 2144(B)). The '734 claim's "lightweight, wearable and/or carried" PDI is met interchangeably by Davis's token, Mytec's battery-powered fingerprint access device, and de la Huerga's badge. Substituting one portable-wireless-biometric form factor for another is a predictable design choice.

6. "Obvious to try" in a finite, predictable design space (KSR). Given a known need for two-factor (possession + inherence) authentication and a finite set of known architectures (add a fingerprint sensor and a local template to the token, or add PKI to the badge), the claimed arrangement is one of a small number of predictable solutions with a reasonable expectation of success. The '734 specification itself states that "the individual electronic and processing functions … are, individually, well understood by those skilled in the art."

7. No teaching away. None of the references criticizes on-device template comparison, mutual authentication, or proximity-based display control; to the contrary, each advocates at least one of them. There is no asserted criticality of the specific "envelope = human reading range" geometry; it is presented as a configurable, "hardware and software" variable ("The shape and size of the detection envelope are controllable and may be varied").

8. Avoiding hindsight is not a problem here because the motivation is drawn from the references themselves (Davis's and de la Huerga's stated problems, Linge's stated purpose of protecting displayed data), not merely from the '734 disclosure.

VI. Nonobviousness counterarguments and residual risk

These are the limitations I would expect a patent owner to emphasize, ranked by strength.

1. The final "wherein" clause of claim 1 (and claim 9 / claim 17(h)): policy-manager-directed blanking when a second PDI enters the envelope, held blank until that second user is biometrically identified as having permission. This is the most defensible limitation. Linge teaches departure-based blanking (the authorized user leaves); the '734 claim is arrival-based blanking with a permission-determination substep. De la Huerga's family material (see caveat below) describes blanking the screen when another device is detected and restoring it after the newcomer is biometrically authenticated and authorized, which is close; but if that passage is held to reside only in the post-2001 CIP, a patent owner would argue the arrival-plus-permission-gating combination was not squarely disclosed. Assessment: still likely obvious over de la Huerga '085 + Linge + a permission-gating reference (US 6,148,342; WO 2000026823), but this is the limitation where the § 103 case is least airtight.

2. The "envelope" defined by human reading range. The claim does not recite numerical bounds; it recites a purpose-oriented configuration. A patent owner would argue this is a "result" limitation. Assessment: weak — the specification says the envelope is controllable/variable, and Linge expressly discloses an adjustable transmit range.

3. On-device generation of the key pair (claim 1(c)(ii)). Maes describes a certificate downloaded from the service provider. A patent owner could argue that generating the key pair inside the PDI (so the private key never exists outside it) is the distinguishing security insight. Assessment: moderately weak to a PHOSITA — key-pair generation inside constrained tokens was a known engineering choice (US RE36,946 E; US 6,577,734; Mytec's biometric-controlled key generation [provisional]), and the claim recites no algorithm or hardware that would make the generation non-routine. This is nonetheless the element for which the cited-art mapping rests most heavily on [provisional] references, and a fuller record would be needed to lock it down.

4. Claim 21's registrar-plus-guarantor, biometrically signed, in-envelope registration. Nothing in the verified core references (Maes, Davis, de la Huerga, Linge, Mytec) squarely recites a guarantor providing a biometrically digitally signed voucher. The best fits are US 5,960,085's multi-party signed-transaction/audit-trail disclosure, US 6,040,783 [provisional], and WO 1999013415 A1 [provisional]. Assessment: claim 21 is the strongest candidate to survive a § 103 challenge on the present record. If the goal is to invalidate the patent, I would expect claim 21 (and possibly claim 8's cradle) to be the hold-out claims.

5. "Policy manager determines whether a user's access … is to be limited." As a functional label this adds little; but the dependent concept of granular, role-based access filtering is squarely taught by US 6,148,342 (separately encrypted identifier/access request), WO 2000026823, and US 6,092,202 [provisional], so this alone does not save the claims.

VII. Secondary considerations / objective evidence

• No commercial-success, licensing, or copying evidence was identified. Per the previously generated litigation summary, no litigation was found involving this patent and the patent is Expired – Fee Related. The absence of litigation is not evidence of nonobviousness (no nexus is established to any objective indicator).
• Long-felt need / failure of others is not established by the record here; moreover, any such argument would be undercut by the patent's own admission that the individual components were "well understood by those skilled in the art," and by the fact that both Davis and de la Huerga were confronting and solving the same lost-token problem before 2001.
• Unexpected results: none claimed. The specification asserts no performance metrics that would rebut a KSR prima facie case.
• Caveat on inferences: the prior section's "no litigation" finding is reported as none known (moderate-to-high confidence), not a certified negative. It should not be used as a proxy for patent strength or weakness.

VIII. Caveats, confidence, and contradiction flags

1. Verification scope. I verified the disclosure/claims of US 6,016,476, US 6,088,450, US 6,594,762, US 6,353,889, and the US 5,960,085 family by live search. Mappings for the remaining cited references are marked [provisional] and are based on their titles, classifications, and dates as they appear in the Prior Art section. Before these grounds were asserted in a petition or an invalidity contention, each [provisional] reference should be pulled in full and pin-cited.

2. Date qualification is dispositive for several entries. The "Cited By (56)" and "Families Citing this family (169)" lists are not prior art to a Feb. 1, 2001 priority date. In particular, US 2005/0091338 A1 (de la Huerga, filed 2004) and the Privaris/Proxense/JPMorgan documents post-date the priority date and may only be used, if at all, as background evidence of the state of the art.

3. Contradiction flag / attribution caution for US 5,960,085. My search for "US5960085" returned a long specification that in fact appears to be the de la Huerga continuation-in-part, US 2005/0091338 A1 (a CIP of the '085 patent). That CIP contains the most explicit passage I found on blanking a terminal display when a second badge is detected. The original US 5,960,085 undisputedly discloses the wearable CVD/badge, proximity interrogation, public-key cryptography with the badge verifying the source of the interrogation before re-encrypting with its own key, the "private keys are never transmitted" rule, the optional fingerprint sensor, and periodic recommitment polling. Whether the arrival-based blanking passage is original to the '085 patent or was added in the 2004 CIP, I could not confirm with high confidence from the available search results (my estimate is that it is more likely than not original, roughly 70%). Ground 1 is therefore drafted so that the blanking clause is also supported by US 6,594,762 (which is unambiguously pre-2001 art), so the rejection does not depend solely on that attribution.

4. Contradiction flag / source priority. Per the operating rules, where live search results conflict with training data I have followed the search results. Two examples: (i) the US 6,016,476 record shows a U.S. filing date of Jan. 16, 1998 (App. No. 09/008,122) alongside a 1997-08-11 priority date in the Google Patents table — both are before Feb. 1, 2001, so the discrepancy does not affect prior-art status; (ii) the '085 CIP text I retrieved describes features ("trusted computer system identifier," "neighborhood roam," watermark signatures) that go beyond the 1999 patent — I have attributed only the badge/proximity/PKI/polling features to the '085 patent itself.

5. Overall confidence.

   • That claims 1, 9, and 17 (and dependent claims 2–20) are invalid under § 103 over the Maes/Davis/de la Huerga/Linge combination: high (roughly 80–85%), with the principal residual uncertainty being the arrival-plus-permission blanking clause.
   • That claim 21 is invalid on the present record: moderate-to-low (roughly 40–50%); it is the most likely claim to survive and would require a tighter mapping to a pre-2001 guarantor/identity-proofing reference.
   • That claim 8 (device holder/tethered mode) is invalid: moderate; would benefit from a fuller reading of US 4,816,653/4,816,654.

Bottom line. U.S. 7,310,734 sits at the confluence of three well-developed 1990s art streams — portable biometric tokens (Maes, Mytec, Loefberg, Cardguard), wireless proximity challenge/response (Davis, Linge), and on-badge PKI with no template/private-key export (de la Huerga). Every element of independent claims 1, 9, and 17 appears in the examiner-cited art, and the references themselves supply the motivation to combine (the shared lost/stolen-token problem and the shared observer/privacy problem). The strongest § 103 case is Maes + Davis + de la Huerga + Linge against claims 1–20, with claim 21 (registrar/guarantor registration) the most defensible and the "policy-manager blanking on detection of a second PDI" clause the limitation most worth developing with additional pin cites.