US 6223289

I'll run several targeted searches to check for current USPTO status and any CAFC/litigation activity, then summarize.

Let me check for litigation/docket history and pull the claim text.

Let me try to retrieve the actual claim set for US6223289.

US 6,223,289 B1 — Analyst Summary

Note on dates: Your prompt frames the current date as April 26, 2026; my operating instructions give 2026‑09‑29. Either way, the patent below is long expired, so the date difference does not change any status conclusion. I flag it only for transparency.

Note on sourcing: All bibliographic facts below come from the authoritative patent text supplied in my context (Google Patents, https://patents.google.com/patent/US6223289/en) plus corroborating search hits (Unified Patents portal, https://portal.unifiedpatents.com/patents/patent/US-[6223289](/patent/6223289)-B1; the WO/EPO family record for WO9954803, https://patentimages.storage.googleapis.com/54/e0/87/e17e8b15c3751a/WO2002037267A3.pdf). Where I could not verify something, I say so explicitly.

1. Bibliographic data

Note on the assignment record: the 1998‑08‑04 assignment lists the assignor names as "WALL, GERAD A." and "NORHTCUTT, J. DUANE" (apparent typographical variants of Gerard/Northcutt in the USPTO assignment abstract). Per your strict rule, I am reporting those spellings literally rather than correcting them.

2. Abstract (verbatim)

Authentication and session management can be used with a system architecture that partitions functionality between a human interface device (HID) and a computational service provider such as a server. An authentication manager executing on a server interacts with the HID to validate the user when the user connects to the system via the HID. A session manager executing on a server manages services running on computers providing computational services on behalf of the user. The session manager notifies each service in a session that the user is attached to the system using a given HID. A service can direct display output to the HID while the user is attached to the system. When a user detaches from the system, each of the service's executing for the user is notified via the authentication manager and the session manager. Upon notification that the user is detached from the system, a service can continue to execute while stopping its display to the HID.

3. Plain‑language overview of the independent claims

Important honesty caveat. I was not able to retrieve the verbatim claim text of US 6,223,289 from the sources I could reach. The full text supplied to me contains the description but is truncated before the claims, and my searches returned the continuation patent US 6,484,174 rather than the '289 claim set. I therefore will not invent claim language or claim numbers. What follows distinguishes (a) what I can state from the specification/abstract, and (b) what I can state about the family's claim 1, which I do have verbatim.

(a) Subject matter the claims necessarily cover (from abstract + specification, high confidence):

• A human interface device (HID) / "network terminal" paradigm in which display and input are partitioned away from computation and state (FIG. 7, FIG. 8).
• An authentication manager executing on a server that validates a user when the user connects via the HID, using a challenge/response exchange (FIGS. 5A–5B, FIG. 6) that hashes identifier, PIN, secret and challenge values with a function such as hmac_md5 (RFC 2104/RFC 2103 line of art).
• A session manager executing on a server that maintains a session database mapping users → sessions → services, initiates required services, and sends connect/disconnect notifications so that services direct display output to whichever HID the user is currently at.
• Session portability / persistence: services continue executing while the user is detached (e.g., smart card removed), and are redirected to a new terminal when the user re‑attaches.
• One‑way authentication that avoids key exchange and central key lookups (stated in the specification as an advantage).

(b) The family claim 1 (verbatim, from US 6,484,174 B1, the continuation of application 09/063,339, published in the Official Gazette, Issue 1264‑3): This is the closest authoritative claim text I can give you for the '174 continuation — not for the '289 patent itself:

1. A method for interacting with a computer system comprising: accessing a first computer in said computer system using an identifier; authenticating a user on a server in said computer system using said identifier; and directing one or more services to said first computer system, if said user is authenticated on said server; disconnecting from said first computer; continuing to execute said services; re‑connecting on a second computer in said computer system using said identifier; authenticating said user on said server in said computer system using said identifier; and directing said services to said second computer system, if said user is authenticated on said server wherein said services continued to execute when said user was disconnected from said first computer.

The '174 patent reports 24 claims; the '289 patent's claim count and independent-claim structure are unverified in my sources. Structurally, a patent of this era and family typically presents one or more method claims (session management / authentication as above) mirroring this continuation claim, plus apparatus and/or computer program product claims covering the authentication manager + session manager architecture. I am labeling that last sentence as inference, not verified fact.

4. Litigation, PTAB, and CAFC 2026 docket check

• No record found. Targeted searches for "6223289" in combination with Federal Circuit, PTAB, IPR, or district‑court litigation terms returned no case, docket, IPR, or appeal involving US 6,223,289. The only "6223289"‑bearing hit was a stray numeric occurrence on a courtscast.com oral‑argument index page (Cascades Computer Innovation v. RPX Corp.), where the number appears as unrelated page metadata rather than as a patent‑in‑suit identifier. I would not treat that as evidence of litigation over this patent.
• Enforcement context: Even absent a docket hit, the patent's window for infringement suits is effectively closed — it expired 2018‑04‑20 (20 years from the 1998‑04‑20 filing, with no verified terminal disclaimer or extension in my sources). Damages recovery would be limited to the six years before expiration.
• Limits of my check: I could not query PACER, the CAFC CM/ECF docket, or USPTO Patent Center / PTAB APIs directly; my check rests on open‑web search. A negative result here means "not surfaced by search," not a certified clearance opinion. If you need a certified litigation history, pull the Patent Center "Legal Events" tab, PACER Docket Navigator/ Lex Machina, and the CAFC docket for the patent number.

5. Explicit uncertainty list

1. Verbatim claim text and claim count of US 6,223,289 — NOT verified. Do not rely on the claim‑1 description above as the '289 claim; it is the '174 continuation's claim 1.
2. No verified litigation/PTAB/CAFC history. Searches were negative; they are not exhaustive of PACER/ECF.
3. Assignee chain: Original assignee Sun Microsystems, Inc.; current Oracle America, Inc. per recorded reassignment — the Google Patents page itself warns that listed assignees "may be inaccurate" and that it performs no legal analysis.
4. Legal status ("Expired – Lifetime," 2018‑04‑20) is Google Patents' assumption, explicitly not a legal conclusion.

If you want, I can attempt a follow‑up pass aimed specifically at the USPTO full‑text claims view for 6,223,289 so the independent claims can be restated verbatim rather than by family proxy.