Invalidity dossier

US 5490216

Added 5/10/2026, 9:37:21 PM

Got a demand letter citing US 5490216?

Paste the full letter into the analyzer. We extract every asserted patent (this one and any others), characterize the asserter, flag validity vulnerabilities, and draft a sample response letter your attorney can adapt.

Analyze a letter →

Generic sample response letter (PDF)

Generates a draft reply letter to a generic infringement claim citing this patent, using the analysis below. For a response tailored to a specific letter you received, use the demand letter analyzer instead. Sample only — not legal advice. Do not send without review by a licensed patent attorney.

Download sample PDF →

Watchlist

Get alerted when this patent moves.

Email-only, free, anonymous. We'll notify you when US 5490216 gets a new lawsuit, a new PTAB proceeding, or a new dossier section. One-click unsubscribe from any alert.

Active provider: Google · gemini-2.5-pro

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

Patent Summary: US 5,490,216

A search of USPTO and CAFC databases for 2026 activity regarding patent 5490216 reveals no new dockets or filings. This is consistent with the patent's claims having been canceled, rendering it unenforceable. The following summary is based on the authoritative patent text.

Title System for software registration
Inventor Frederic B. Richardson, III
Original Assignee Uniloc Singapore Pte Ltd
Current Assignee Uniloc Luxembourg SA
Filing Date September 21, 1993
Issue Date February 6, 1996
Legal Status Expired / Claims Canceled
Abstract A registration system allows digital data or software to run in a use mode on a platform if and only if an appropriate licensing procedure has been followed. Preferably, the system detects when part of the platform on which the digital data has been loaded has changed... The system relies on a portion of digital data or code which is integral to the digital data to be protected... This integral portion... may include an algorithm that generates a registration number unique to an intending licensee... based on information supplied by the licensee... The algorithm in the code portion is duplicated at a remote location on a platform under the control of the licensor... communication between the intending licensee and the licensor... is required so that a matching registration number can be generated at the remote location for subsequent communication to the intending licensee as a permit to licensed operation...

Plain-Language Overview of Independent Claims

The invention describes a system and method to prevent software piracy by tying the software's use to a specific user and/or their machine through a remote registration process. The core concept is that the software on the user's computer and a remote server under the software vendor's control both run an identical algorithm to generate a unique key. The software will only switch from a limited "demonstration mode" to a fully functional "use mode" when the keys match.

Independent Claim 1: The System
This claim describes the overall architecture. It requires a system for licensing software that includes two key components: a "local" ID generator on the user's computer and a "remote" ID generator at the vendor's end. The software has a "mode switching" function that keeps it in a limited state until the unique ID created by the user's machine matches the unique ID created by the vendor's remote system. This match confirms that the user is licensed.

Independent Claim 11: The Security Routine
This claim focuses on the software component that can be attached to a program to protect it. It describes a "registration means" that generates a security key based on information the user provides, which should uniquely identify them. This allows the software to be registered to a specific user on the computer where it is installed.

Independent Claim 17: The Method
This claim outlines the process of controlling software distribution. The method involves:

  1. Providing software that can switch between a limited "demonstration mode" and a "fully enabled mode."
  2. Using a key generator within the software to create a secret "registration key" based on the user's unique information.
  3. The user contacts a third party (the vendor) who operates a duplicate key generator to get an "enabling key."
  4. The software only switches to its fully enabled mode if the enabling key entered by the user is an identical match to the secret registration key the software generated internally.

Independent Claim 20: The Digital Product
This claim describes the end product itself: a piece of software or digital data that has the registration and mode-switching code built into it. This integrated code is what manages the switch between the demonstration and full-use modes, based on the successful completion of the registration process described in the other claims.

Generated 5/11/2026, 12:05:52 AM