US 5979753

I'll search for authoritative information on this patent number and any 2026 CAFC activity.

Let me run additional targeted searches for litigation and any 2026 CAFC activity.

US Patent 5,979,753 — Verified Summary

Source of record: Google Patents full text (https://patents.google.com/patent/[US5979753](/patent/US5979753)/en), FreePatentsOnline (https://FreePatentsOnline.com/5979753.html), Justia (https://patents.justia.com/patent/5979753). These agree with each other on every bibliographic field below.

Bibliographic data (literal)

Family / continuity: This is a continuation of U.S. application Ser. No. 08/706,579, filed Sep. 5, 1996, now U.S. Pat. No. 5,825,002. A further continuation, Ser. No. 09/436,170, issued as U.S. Pat. No. 6,367,694 B1. (Note: the specification as published on Google Patents renders the parent number literally as "08706,579" — an OCR artifact; I am flagging it rather than silently correcting it.)

Representative cited prior art: Dutch Patent Application No. 9002296 and U.S. Pat. No. 5,468,942 to Oosterveen et al. (both discussed in the Background); also U.S. Pat. Nos. 4,929,819; 5,393,965; 5,417,354; 5,457,307; 5,637,847; 4,923,308; and 4,723,212, among ~42–44 references.

Abstract (as issued)

"The present invention relates to a data processing and retrieval system for use in a self-checkout system utilized in a retail facility. A plurality of customers are provided with a portable data collecting terminal having a bar code reader. Once the data is collected using the portable terminal, a record of the session is uploaded to a customer's data file upon the entry of an authorization code. In the event errors occur during data entry or in the entry of the authorization codes, a customer service desk is provided which assists the customer in completing the transaction."

Plain-language overview of the independent claims

Claim 1 — Secure data capture system (authorization-gated file update).
A system for updating a customer's data file with the session/payment record that the customer generated using a handheld bar-code reader terminal. It recites (i) a memory holding an authorization code for that customer and recording the session data record, and (ii) a data processor coupled to the customer data entry device and the memory that compares the authorization data entered on the entry device against the stored authorization code and updates the customer data file with the session data only if they match. The final limitation requires that the authorization code be received from an external electronic fund transfer (EFT) system — i.e., the gate is not merely a local PIN check but an external EFT-sourced authorization.
Claim-drafting flag: as printed on both Google Patents and FreePatentsOnline, claim 1 begins at element "b)" and refers to "said customer data entry device" without ever introducing it — element "a)" appears to be omitted from the published text. I therefore cannot state the full literal scope of claim 1 with confidence. This is a text-integrity issue in the published record, not an interpretation I am asserting.

Claim 3 — Combined self-checkout + cash-register system with comparative reporting.
A system spanning two shopping modes: (a) customer portable terminals coupled to an automated self-checkout system; (b) a store computer holding product information for selectable goods; (c) cash registers coupled to that store computer; (d) a customer database that records sales made both through the portable terminals and at the cash registers; and (e) an automated report printing system that prints purchasing-history summary reports for both populations, so that comparative analyses of purchasing histories, sales trends, and system resource usage can be drawn as between self-scanner customers and cash-register customers.

Claim 4 — Secure data capture system with automatic payment.
A system for building a customer record for a shopping session and allowing automatic payment: a portable terminal with an integrated machine code reader generates at least part of the record; a central memory (one or more modules, in communication with the terminal) stores a customer history for each of multiple customers; and a data processor concatenates the customer's session record onto their stored shopping-history record and obtains an authorization code from a remote facility authorizing payment via an electronic payment system, then records that payment information and authorization code into the central memory. Dependent claims narrow this: code stored with the history (5); debit from a debit account (6); credit from a credit card account (7); handheld bar-code reader terminal (8).

Practical core: the patent's commercial thrust is that a self-scanning shopper's session is not allowed to mutate the central customer file, and payment is not accepted, until an externally-sourced authorization code matches; the return cradle (dispenser) both locks the terminal in and withholds/detains it when no valid authorization is presented.

CAFC 2026 docket check

I ran searches for CAFC 2026 dockets and litigation tied to patent 5,979,753. I found no 2026 CAFC docket entry, no IPR/PTAB proceeding, and no active litigation naming this patent. My CAFC-specific query returned zero results, and the only "597"-adjacent hits were unrelated matters (e.g., a Wilus Institute v. HP Inc. E.D. Tex. motion referencing U.S. Pat. No. 11,700,597 — a different patent number, which I am deliberately not conflating).

Explicit uncertainty: I do not have direct docket-database access in this session, so absence of results is not affirmative proof that no 2026 appellate activity exists. I can state with confidence only that (a) no search result surfaced such a proceeding, and (b) the patent is recorded as expired since 2016‑09‑05, which makes live 2026 CAFC enforcement appeal activity unlikely for this number. Assignments of record show only security-interest/name-change transactions (JPMorgan Chase 2005, released 2010; Morgan Stanley Senior Funding collateral agreement 2014, released 2015; change of name to Symbol Technologies, LLC in 2015) — none of which is litigation.

Note on related but distinct numbers

Searches repeatedly surface 5,979,753 as a cited reference inside later patents (e.g., Hand Held Products/Metrologic imaging patents, Quickvault POS-processing patents). Those are citations to this patent, not records of this patent, and should not be mistaken for its own prosecution or litigation history.

I'll research litigation involving US patent 5979753 (the "Device and method for secure data updates in a self-checkout system" patent).

Let me refine my searches, because the results so far are returning different patents that also happen to be nicknamed "'753" (e.g., Biosig's heart-rate monitor patent, Ferring's pharmaceutical patent) — not US 5,979,753.

Answer: No confirmed litigation found for US 5,979,753

Important framing note: I was unable to identify any litigation asserting or involving US 5,979,753 specifically. My searches were also run to their limit, and — critically — the web results were heavily polluted by other, unrelated patents that are also colloquially called "the '753 patent." I want to flag those false positives so you can see I did not mistakenly attribute their litigation to your patent:

None of these concern the patent at issue here.

What I could verify about US 5,979,753 itself

From the authoritative full text (Google Patents, fetched 2026-09-17):

• Title: "Device and method for secure data updates in a self-checkout system"
• Inventor: Thomas Roslak
• Assignee: Symbol Technologies, LLC (originally Symbol Technologies, Inc.)
• Priority date: 1996‑09‑05; Filed: 1998‑09‑15; Granted/Published: 1999‑11‑09
• Application number: US09/153,832 (a continuation of US08/706,579, now US 5,825,002)
• Related family members: US 5,825,002 (parent) and US 6,367,694 B1 (continuation, app. US09/436,170)
• Legal status: Expired – Lifetime; anticipated expiration 2016‑09‑05

The Google Patents page shows no litigation ("Litigation") section with any case entries, which is consistent with the absence of results.

Conclusion

Based on the available sources, I found no known litigation involving US 5,979,753. I cannot provide plaintiff, defendant, jurisdiction, case number, filing date, or outcome because no such case was located.

Two caveats you should weigh:

1. Confidence level: I am not asserting with high confidence that the patent was never litigated. My searches may simply not have surfaced it. Sources like the Unified Patents litigation portal (https://portal.unifiedpatents.com/litigation), PacerMonitor, CourtListener/RECAP, and Docket Navigator are the correct places to run a definitive owner/patent-number query, and I was unable to complete a targeted pull from those before hitting my search limit. A proper next step is a direct docket-number/patent-number search in Docket Navigator or Lex Machina, which index by patent number and are not dependent on informal web references.
2. Practical significance: The patent expired on 2016‑09‑05 (its 20‑year term from the 1996 priority date is reflected as "anticipated expiration"). An expired patent cannot be asserted for prospective relief, so any active assertion today would be unusual. If you are doing a validity, damages, or freedom‑to‑operate analysis (e.g., regarding the sibling US 5,825,002 / US 6,367,694), let me know and I can focus the search on those specific numbers instead — noting that those are different patents and must be searched separately.

If you'd like, I can attempt another round of targeted queries against specific litigation databases for the exact string 5,979,753 combined with "complaint," "Docket Navigator," and each family member (US 5,825,002 and US 6,367,694).

I'll verify the ODP "no proceedings" default against live sources before writing the section.

The ODP block says no proceedings; let me stress-test that against a few more angles (family members, petitioner names) before finalizing.

PTAB / AIA Trial Proceedings — US 5,979,753

Verification basis for this section. (1) The structured "PTAB proceedings on file" block — the canonical USPTO Open Data Portal feed included in this prompt — returns no AIA trial proceedings for US 5,979,753. (2) I ran supplementary web searches for 5,979,753 + IPR/PTAB/CBM, for AIA-trial records naming the patent, and for the two sibling patents in the family (US 5,825,002; US 6,367,694 B1). All of those returned zero proceedings naming this patent; the hits were either generic PTAB-practice commentary or unrelated patents colloquially called "the '753 patent." (3) This is consistent with the earlier sections of this analysis, which found no litigation and no CAFC docket activity for this number.

Proceedings overview

Total AIA trial proceedings on file for US 5,979,753: zero — 0 active, 0 resulting in claims invalidated, 0 resulting in claims sustained, 0 settled, 0 institution decisions denied.

Bottom-line defensive posture: this is not a "hardened" patent in the IPR sense — it is a completely untested one. No independent claim (1, 3, 4) and no dependent claim (2, 5, 6, 7, 8) has ever been construed, instituted against, or canceled at the PTAB, so there is no § 315(e)(2) estoppel to exploit and no FWD to cite. The meaningful defense here is not a PTAB record; it is the statutory one — the patent's recorded legal status is Expired – Lifetime, anticipated expiration 2016-09-05 (20 years from the 1996-09-05 priority date, per Google Patents). Any 2026 assertion can only reach pre‑expiration past damages, and those are themselves cut off by the six‑year lookback of 35 U.S.C. § 286 measured backward from the complaint date.

No proceedings to report

There are no proceedings to render in the per-proceeding format (proceeding number, panel, institution decision, FWD, appeal), because none exists. I am deliberately not generating placeholder numbers, panels, or dispositions. Zero PTAB filings were located on:

• US 5,979,753 (this patent)
• US 5,825,002 (parent; app. 08/706,579) — checked because challengers often attack the family, not just the asserted member
• US 6,367,694 B1 (continuation; app. 09/436,170) — same

Channels that were structurally unavailable when the patent was live — worth knowing if a demand letter arrives today:

Screened and rejected as false positives (different patents, do not conflate):

Confidence statement (required by the constraints): I can state with confidence that the USPTO ODP feed contains no proceedings for this patent and that no search result surfaced one. I cannot state with absolute certainty that no petition was ever filed and denied/terminated, because I lack direct authenticated access to PTAB E2E / P-TACTS in this session. The definitive check is a patent-number query at https://ptab.uspto.gov/ (PTAB E2E) or the ODP trials endpoint at https://data.uspto.gov/ptab/trials/proceedings, plus a CourtListener/RECAP query at https://www.courtlistener.com/.

Strategic summary

Claim status. All eight claims of US 5,979,753 — independent claims 1, 3, and 4 and dependent claims 2, 5, 6, 7, and 8 — stand exactly as issued on 1999-11-09. None is canceled, none is narrowed by certificate, none has been adjudicated. In PTAB-vernacular terms, every claim is UNTESTED, not SUSTAINED. That distinction matters: a patent that has never been IPR'd is neither fortified nor weakened by the Board, and a defendant cannot point to any administrative record as "the patent office already looked at this and got it right." Conversely, a defendant also cannot point to canceled claims as a kill-shot against a demand letter.

Estoppel landscape. § 315(e)(2) is inapplicable — there is no FWD to trigger it. No petitioner, and no privy of any petitioner, is estopped from raising any § 102/§ 103 ground. Every prior-art ground, including the references the examiner already considered during prosecution (Dutch App. 9002296; U.S. 5,468,942 to Oosterveen; U.S. 4,929,819; 5,393,965; 5,417,354; 5,457,307; 5,637,847) and any art not cited at all, is fully available in district court. That said, the same is true in reverse: because no IPR exists, there is also no § 315(e)(1) bar and no estoppel risk for a defendant who wishes to pursue both a district-court invalidity case and a parallel PTAB or reexam challenge — subject only to the separate estoppel and forum-preclusion effects the USPTO is currently proposing to impose at the institution stage (see below).

Pattern signals. There is no petitioner at all, so no serial-filing or joinder pattern to analyze, and no defensive aggregator (Unified Patents or similar) in the chain. The assignment record shows only financing and corporate-housekeeping transactions — JPMorgan Chase security interest (2005-01-05, released 2010-12-03), an inventor-to-Symbol assignment (2012-05-29), a Morgan Stanley Senior Funding collateral agreement (2014-10-31, released 2015-08-17), and the change of name to Symbol Technologies, LLC (2015-07-08). Nothing in that history signals a litigation-driven campaign, and the companion sections of this analysis found no litigation and no CAFC appeal. The absence of any IPR is itself a signal here: a self-checkout patent with a 1999-2016 enforcement life that attracted no PTAB petition, no CBM, and no reported suit was, on the available record, essentially never asserted as a standalone revenue patent.

One live procedural hazard to weigh. As of 2026 the USPTO has sharply curtailed IPR access — Director Squires assumed personal control of all institution decisions effective 2025-10-20, institution rates collapsed to roughly 4% through early December 2025, and proposed amendments to 37 C.F.R. § 42.108 would make denial mandatory where claims were previously upheld or a parallel case will decide validity first (see https://www.kingandwood.com/cn/en/insights/latest-thinking/a-new-era-at-the-uspto-director-Squires-implements-major-restrictions-on-iprs.html and https://www.unifiedpatents.com/insights/2026/1/13/patent-dispute-report-2025-in-review). For an aged, never-challenged patent, the "settled expectations"/prior-knowledge factors now cut against institution. The practical consequence is that an IPR against this patent today is unlikely to be instituted even if it were worth filing — which makes district-court invalidity, or delegated ex parte reexamination, the realistic administrative path. Note the text-integrity issue flagged in the earlier summary: claim 1 as published opens at element "b)" and references "said customer data entry device" without introducing any element "a)." A § 112(b) indefiniteness theory built on that omission cannot be heard in an IPR (IPR is limited to § 102/§ 103) and can no longer be heard in a CBM (sunset 2020-09-16). It has to be raised in district court.

Recommended next steps

1. Treat the "no PTAB activity" finding as a confirmed negative, not a merely empty result. Re-run the patent-number query directly at https://ptab.uspto.gov/ (PTAB E2E) and at the ODP endpoint https://data.uspto.gov/ptab/trials/proceedings before finalizing any opinion or memo, since these index by patent number rather than by informal web reference. Also query the two family members separately — US 5,825,002 and US 6,367,694 B1 — because a challenger sometimes petitions against a sibling rather than the asserted member. This analysis found none for any of the three.

2. Do not build a defense on a canceled claim — because there is none to build on. Since no FWD exists, there is no disposition to quote or link. If a demand letter cites claims 1, 2, 3, 4, 5, 6, 7, or 8 of US 5,979,753, every one of those claims is legally live and must be addressed on the merits.

3. Attack on the timeline, not the validity. The pivot point for a 2026 defendant is the recorded expiry of 2016-09-05. Confirm that date against the USPTO Patent Center maintenance-fee and expiration record, then compute the § 286 six-year damages lookback from the actual complaint or demand date. Depending on when suit is filed, the recoverable window may be vanishingly small or nonexistent.

4. If you want an administrative record, ex parte reexamination is the residual tool — it is not an AIA trial, it survives patent expiration, it is far cheaper than an IPR, and reexam filings are at an all-time high (726 requests in 2025, up 66.1% year over year, per Unified Patents). It also carries no § 315(b) time bar and no estoppel exposure, though cancellation rates are materially lower than in IPR.

5. Preserve the § 112(b) argument for district court. Because the published claim 1 appears to be missing introductory element "a)," parallelism exists between § 112 indefiniteness and the printed claim text — but no PTAB channel can hear it. Document the published-text discrepancy now, before any claim-construction fight.

6. No trial-stage milestone tracking is required. There is no institution decision deadline, no oral hearing date, and no one-year FWD due date to monitor, because no petition is on file.

I'll pursue the assignment record directly — reel/frame numbers and correspondents are the specific deliverables here.

I hit my search-step limit before I could pull reel/frame-level data from the Assignment Center, so what follows is built entirely on the Google Patents legal-events record in the authoritative full text plus the related-patent evidence I did retrieve. I flag the gaps explicitly rather than filling them.

Critical sourcing caveat up front: I could not retrieve reel/frame numbers or assignment correspondents for any event. Two targeted queries ("5979753" assignment "reel" "frame" Symbol Technologies and "REEL/FRAME" "Roslak" assignment Symbol Technologies) returned empty result sets, and the Morgan Stanley/Zebra reel query was cut off by the step limit. I will not invent reel/frame numbers or correspondent names. The only dates I have are the dates displayed in Google Patents' "Assigned to" legal events, which are recording-style dates, not necessarily execution dates — the one exception being the anticipated-expiration date. Treat every date below as "recorded on," pending Assignment Center verification.

Inventors

Thomas Roslak — sole named inventor; no co-inventors on the face of US 5,979,753.

Observation (not a finding): a system-scope patent covering an entire self-checkout architecture — entrance unit, dispenser, locking, EFT authorization gate, service desk — naming a single inventor is atypical. I have no evidence of omitted inventorship; I note it only because single-inventor system patents are the kind of thing that later gets a confirmatory re-assignment, which is exactly what happened in 2012.

Original assignee

Symbol Technologies, Inc. (Holtsville, NY) — this is the entity on the issued patent, and it is also the original assignee per the legal events. Note a minor inconsistency in the record itself: the Google Patents header block lists "Original Assignee: Symbol Technologies LLC," while the legal events show a Change of Name from Symbol Technologies, Inc. → Symbol Technologies, LLC recorded 2015-07-08. The header is a present-tenant summary; the legal events are the chronological truth. This does not contradict the previously generated summary table (which correctly listed Inc. as original, LLC as current), but the header line is misleading if read alone.

Assignment timeline

Six recorded events. No reel/frame numbers or correspondents retrieved — see caveat above. All six are either security interests, releases of security interests, or a corporate name change; there is no third-party ownership transfer, and the only inventor-side conveyance is a late confirmatory assignment back to the original employer.

2005-01-05 (recorded) — Reel not retrieved

• Conveyance: Security Interest (Google Patents label: "SECURITY INTEREST (SEE DOCUMENT FOR DETAILS)")
• Assignor: Symbol Technologies, Inc.
• Assignee: JPMorgan Chase Bank, N.A.
• Correspondent: not retrieved. Cannot flag recurrence.
• Context: securitization — a lender taking a collateral lien over Symbol IP, not a transfer of ownership.

2010-12-03 (recorded) — Reel not retrieved

• Conveyance: Release by Secured Party ("RELEASE BY SECURED PARTY")
• Assignor: JPMorgan Chase Bank, N.A. (rendered "JPMORGANCHASE BANK, N.A." in the record)
• Assignee: Symbol Technologies, Inc.
• Correspondent: not retrieved.
• Context: release of the 2005 securitization lien — extinguishment of the lender's interest; Symbol's ownership was never divested.

2012-05-29 (recorded) — Reel not retrieved

• Conveyance: Assignment of Assignors Interest (inventor→company)
• Assignor: Roslak, Thomas (the inventor)
• Assignee: Symbol Technologies, Inc.
• Correspondent: not retrieved.
• Context: title-cure / confirmatory assignment. This is the most analytically interesting entry in the chain: the inventor executed a formal assignment to his own employer ~16 years after filing and ~13 years after issuance. Where the file already contained an employment/obligation-to-assign basis, a late-recorded confirmatory assignment typically appears when a portfolio is being diligenced for a transaction or a chain-of-title defect is discovered. I have no evidence of what prompted it — the 2012 date does not map cleanly onto the 2007 Motorola acquisition or the 2014 Zebra acquisition, so I am not attributing a cause.

2014-10-31 (recorded) — Reel not retrieved

• Conveyance: Security Agreement
• Assignors: Laser Band, LLC; Symbol Technologies, Inc.; Zebra Enterprise Solutions Corp.; ZIH Corp.
• Assignee: Morgan Stanley Senior Funding, Inc., as the Collateral Agent
• Correspondent: not retrieved.
• Context: securitization — a portfolio-wide blanket lien over the Zebra corporate family's IP. The presence of four unrelated Zebra-family assignors on one recording confirms this is not a patent-specific transaction; US 5,979,753 is simply swept into the collateral pool by its Symbol-chain ownership. Consistent with Zebra's 2014 debt financing tied to its acquisition of Motorola Solutions' Enterprise business — stated as correlation, not as a verified causal link.

2015-07-08 (recorded) — Reel not retrieved

• Conveyance: Change of Name
• Assignor: Symbol Technologies, Inc.
• Assignee: Symbol Technologies, LLC
• Correspondent: not retrieved.
• Context: change of name only — same corporate person, new suffix. No change in beneficial ownership.

2015-08-17 (recorded) — Reel not retrieved

• Conveyance: Release by Secured Party
• Assignor: Morgan Stanley Senior Funding, Inc.
• Assignee: Symbol Technologies, Inc.
• Correspondent: not retrieved.
• Context: release of the 2014 collateral security agreement — the lien was satisfied or refinanced roughly ten months after recording.

Post-chain: anticipated expiration 2016-09-05; legal status Expired – Lifetime.

Timeline diagram

timeline
    title Ownership of US 5979753
    1999 : Patent issues to Symbol Technologies Inc
    2005 : Security interest to JPMorgan Chase
    2010 : JPMorgan security interest released
    2012 : Roslak confirms assignment to Symbol
    2014 : Morgan Stanley security agreement
         : Zebra family entities as co assignors
    2015 : Name change to Symbol Technologies LLC
         : Morgan Stanley security released
    2016 : Patent term expires

NPE / troll-pattern signals

Additional neutral observation: the patent is Expired – Lifetime with anticipated expiration 2016-09-05. Whatever residual value the family has is in US 5,825,002 (parent) and US 6,367,694 B1 (continuation), which are separate numbers requiring separate title searches — a point also flagged in the prior litigation section.

Verdict

Insufficient data — and specifically, insufficient evidence of any NPE pattern, rather than insufficient evidence of ownership.

Justification: the recorded chain is six events over 2005–2015, and it contains zero ownership transfers out of the original corporate family — a 2005-01-05 JPMorgan Chase security interest released 2010-12-03, a 2014-10-31 Morgan Stanley Senior Funding collateral security agreement (naming Lens Band, Symbol, Zebra Enterprise Solutions, and ZIH as co-assignors) released 2015-08-17, a 2015-07-08 change of name from Symbol Technologies, Inc. to Symbol Technologies, LLC, and a single inventor confirmatory assignment from Roslak to Symbol Technologies, Inc. recorded 2012-05-29 — so all eight NPE signals are not present or unclear for lack of correspondent data, and the patent has been expired since 2016-09-05. I choose "Insufficient data" rather than "Operating-company assertion" because Symbol/Zebra, though an operating manufacturer squarely in the claimed device class, is not shown to be asserting this patent, and rather than any NPE category because no asserter, shell LLC, or pre-suit transfer appears anywhere in the record.

Two honest limits on this verdict: (1) I could not retrieve reel/frame numbers or assignment correspondents, so signal 3 is genuinely untested — if a single repeat attorney appears across the 2012/2014/2015 recordings, that would need to be checked directly; and (2) my searches were step-limited and the Google Patents legal-events list is a summary, not the full Assignment Center abstract of title.

Verify at: https://assignmentcenter.uspto.gov/ (search by patent number 5979753; the mirrored index at https://assignment.uspto.gov/patent/index.html surfaces the same records). Pull the reel/frame and the "correspondent" field for each of the six entries above, then compare against https://portal.unifiedpatents.com/patents/patent/US-[5825002](/patent/5825002)-A and the sibling US 6,367,694 B1 to confirm whether any counterpart record exists.

I'll verify the patent record and research the cited prior-art references.

Let me research the key cited references individually to give accurate descriptions.

Let me verify the USPTO record and gather details on a few more key references.

Prior-Art Analysis — US 5,979,753

Note on scope. I verified the number 5979753 and only that number. I did not substitute US 6,367,694, US 5,825,002, Biosig's "'753," Supernus's "'753," or any other similar-numbered patent. Where a different number appears below (e.g., the parent/child family members), it is labelled as such and is not being presented as this patent.

1. Identity confirmation (USPTO / Google Patents record)

Sources agree on all bibliographic fields: Google Patents (https://patents.google.com/patent/US5979753/en), FreePatentsOnline (https://FreePatentsOnline.com/5979753.html), Justia (https://patents.justia.com/patent/5979753), SumoBrain (https://www.sumobrain.com/patents/us/Device-method-secure-data-updates/5979753.html).

Critical date. Because the earliest priority is 1996‑09‑05, only art with a date before that — or US patents/applications qualifying under pre‑AIA §102(e) — is prior art. This matters for two entries below.

2. The reference list of record (44 items)

The face of the patent carries 44 cited references. Google Patents renders them in two overlapping tables: "Citations (42)" and "Patent Citations (44)"; the difference is the two Videocart patents (US 5,295,064 and US 5,287,266), which appear only in the 44‑item table. All entries in the fetched rendering carry the "*" flag that Google Patents' legend assigns to examiner‑cited references (* Cited by examiner, † Cited by third party). I flag that the rendering may not cleanly separate examiner from applicant citations, so I do not assert that every item was an examiner citation.

Two foreign/domestic references are expressly discussed by the applicant in the Background itself and are therefore the applicant-acknowledged closest art:

1. Dutch Patent Application No. 9002296 ("the '296 Application") — Albert Heijn B.V.
2. U.S. Pat. No. 5,468,942 to Oosterveen et al. ("the Oosterveen Patent") — Ahold Retail Services AG

3. Tier 1 — Applicant‑acknowledged background art (most relevant)

3.1 NL 9002296 A — Albert Heijn B.V. ("Heijn Bv Albert")

• Title (as indexed): "Self-service bar-code reader and totaliser — uses added customer identification card with reliability coding"
• Priority date: 1990‑10‑22 · Publication date: 1992‑05‑18
• Description: Self-scanning system in which a customer is issued a hand‑held bar‑code reader, scans merchandise into the reader's memory, and the reader's memory is read out at settlement; the system adds a customer identification card with reliability coding to gate the transaction.
• §102 exposure: Claim 1 — this is the single closest reference to claim 1's core (issued handheld bar‑code terminal; stored per‑customer authorization data; comparison before the session is honoured). Claim 2 — because claim 2 recites authorization data "stored on a bar coded identification card," and the '296 Application is described in this very specification as using an added customer identification card. This reference was almost certainly the reason claim 1's final limitation was drafted to require the authorization code to come from an external EFT system rather than from a card.

3.2 US 5,468,942 A — Oosterveen et al., Ahold Retail Services AG

• Title: "Dispensing device for hand scanners accessible from two sides"
• Filed: 1994‑04‑18 · Issued: 1995‑11‑21
• Description: A rack/dispenser (reference numeral 2) holding hand scanners in accommodating cavities (10), each with controllable locking means (electromagnetic 43, locking member 44) that selectively release a scanner. It includes an identification device 15 with a card reader 17 and card insertion slot 16, a keyboard 17' for PIN entry, and a display 18, and clears a specific scanner for use by the identified customer. Contacts 42 read out the scanner's memory and charge its battery on return.
• §102 exposure: Claim 1 — the "customer data entry device" that claim 1 refers to as "said" (see the omission flag in the previously generated summary) is structurally supplied by this reference (card reader 17 + PIN keypad 17'), and the memory/processor comparison is mirrored by the identification device 15 that "determines the identity of a customer and subsequently clear[s] one of the scanning devices." Claim 2 — card‑based authorization data. This reference also underlies the specification's locking/dispenser passages.

4. Tier 2 — Strongest remaining §102 candidates

4.1 US 5,535,407 A — Oki Electric Industry Co., Ltd.

• Title: "Data processing system for locally updating customer data distributed by a host computer to a remote facility and for returning the updated customer data to the host computer"
• Priority date: 1989‑05‑30 · Issued: 1996‑07‑09
• Discrepancy flag: the granted text states it "is a continuation of application Ser. No. 07/530,185, filed May 29, 1990," while Google Patents lists the priority date as 1989‑05‑30. I record both rather than reconciling them.
• Description: A host computer (1) holds a ledger file (6) of customer data (credit/debit balances, black‑list information). Customer data is distributed in batch to a store controller (20) at a remote facility, which builds a sub‑ledger file. On each transaction the controller searches the sub‑ledger, tests black‑list status, credit balance, and an allowable transaction amount, then either concludes the transaction locally and updates the sub‑ledger (step S11), or routes a transaction message to the host to update the ledger file, or records it in a risk file; the sub‑ledger is later returned to the host in batch.
• §102 exposure: Claim 4 — this is the closest structural analogue of claim 4's "central memory … storing a customer history … and a data processor for concatenating the customer record onto the customer shopping history record … and … recording the payment information … onto said central memory." Claim 1 — memory storing authorization/credit data for an authorized customer plus a processor comparing entered data against stored data before updating the customer data file. Strongest single anticipatory candidate for the claim 4 family (with dependent claims 5–6).

4.2 US 4,929,819 A — NCR Corporation

• Title: "Method and apparatus for customer performed article scanning in self-service shopping"
• Filed: 1988‑12‑12 · Issued: 1990‑05‑29
• Description: Foundational self‑scanning checkout in which the customer performs article scanning.
• §102 exposure: Claim 1 preamble (portable terminal used by an authorized customer to generate a session record) and claim 4 (portable terminal generating at least a portion of the customer record). Alone it lacks an authorization‑code comparison, so it is a preamble/§103 reference rather than a full anticipator.

4.3 US 5,354,974 A — Eisenberg, Base 10 Systems, Inc.

• Title: "Automatic teller system and method of operating same"
• Filed: 1992‑11‑24 · Issued: 1994‑10‑11
• Description: Automatic teller / electronic funds transfer architecture.
• §102 exposure: Claim 1, final limitation — "wherein the authorization code is received from an external electronic fund transfer system." This reference and US 5,072,380 (below) are the natural §102/§103 supports for that narrowing limitation, and their presence on the face of the patent is consistent with the examiner using them against an earlier, broader claim 1.

4.4 US 5,072,380 A — Exxon Research and Engineering Company

• Title: "Automatic vehicle recognition and customer billing system"
• Filed: 1990‑06‑12 · Issued: 1991‑12‑10
• Description: Automatic identification of a customer (vehicle) and automatic billing to that customer's account — an external authorisation-and-settlement model.
• §102 exposure: Claim 1 (external‑system authorization code gating a customer data update) and claim 4/6/7 (automatic payment from a customer account).

4.5 US 5,397,882 A — Van Solt, Ahold Retail Services AG

• Title: "Method for spot checking a client in a self-service store"
• Filed: 1993‑05‑14 · Issued: 1995‑03‑14
• §102 exposure: Claim 1 and claim 3 — a self‑service store in which a client is identified and checked. Relevant to the audit/authorization aspect of claim 1 and the "authorized customer" concept across claims 1, 3, 4.

5. Tier 3 — Remaining references of record, with likely §102 target claim

Dates are given as priority date / issue date. "Primary target" is my reasoned mapping of which claim the reference most plausibly bears on under §102; the great majority of these were almost certainly applied under §103 or merely listed, not as anticipators.

5(a) Self-checkout, portable-terminal and dispenser art

5(b) Access control, network-interface and peripheral art

5(c) Coupon / loyalty / customer‑history database art

These are the references that most plausibly bear on claim 3(d) ("a customer database … for recording the sale of goods selected by customers using the plurality of customer portable terminals and of sales of goods at the cash registers") and claim 3(e) (automated report printing of purchasing histories), and on the specification's "purchase histories 174" field.

6. References on the face of the patent that are NOT §102 prior art

US 5,804,807 A — Symbol Technologies, Inc. — "Scan-ahead system for processing merchandise at a checkout register."

• Priority/filing: 1996‑09‑12 · Issued 1998‑09‑08.
• Its effective date (1996‑09‑12) is seven days after this patent's earliest priority date (1996‑09‑05), so it cannot be §102(a) or §102(b) prior art against the claims here, and it does not qualify as §102(e) art because its filing postdates the priority date. Its presence in the list is most likely an artifact of common assignment to Symbol Technologies. Do not treat it as an anticipator.

US 5,778,348 (Pitney Bowes) — its 1991‑12‑24 priority/filing date does precede 1996‑09‑05, so it can qualify as §102(e) art, but it is remote from the self‑checkout subject matter and is best treated as an obviousness/remote‑authorization reference rather than an anticipator.

7. Family‑level citations (separate list — do not conflate with the 44)

Google Patents also lists "Family Cites Families (10)", i.e. documents cited in the prosecution of related family members. These are not citations against US 5,979,753 itself:

JPS 55‑153068 A (Toshiba, "User transaction unit"), US 5,478,989 (Shepley, nutritional information system for shoppers), US 6,144,848 (Weiss, handheld remote computer control / secured interactive telecommunications), US 5,689,650 (McClelland), JP H09‑8440 A (Toshiba), JP 3264193 B2 (Murata), JP 3131724 B2 (Toto Kogyo), US 5,825,002 (the parent, listed reflexively), CN 1235446 A (Matsushita), JP 2001‑125965 A (Rooson).

8. Bottom line — ranked most‑relevant prior art

1. NL 9002296 A (Albert Heijn) — applicant‑acknowledged; closest to claim 1 and claim 2.
2. US 5,468,942 A (Oosterveen, Ahold) — applicant‑acknowledged; supplies the dispenser, locking means, card reader and PIN keypad elements of claim 1/claim 2.
3. US 5,535,407 A (Oki Electric) — closest to claim 4's customer‑history concatenation and to claim 1's update‑on‑comparison architecture.
4. US 4,929,819 A (NCR) — self‑scanning preamble of claims 1, 3, 4.
5. US 5,397,882 A (Ahold, Van Solt) — spot‑checking/authorization of an identified client in a self‑service store; claims 1, 3.
6. US 5,354,974 A (Base 10) + US 5,072,380 A (Exxon) — the external EFT/automatic‑billing limitation of claim 1 and the automatic‑payment limitations of claims 4, 6, 7.
7. US 5,334,821 / US 5,489,773 / US 5,468,948 / US 5,424,524 / US 5,457,307 / US 5,335,071 — portable handheld bar‑code POS terminal art; claim 4 and claim 8.
8. US 5,621,812 / US 5,237,620 / Catalina group (US 4,723,212; 4,910,672; 5,173,851; WO 92/20030; WO 94/09440) / US 4,833,308 / US 4,949,256 / US 5,380,991 — customer purchasing‑history database and POS data reporting; claim 3(d)–(e).

9. Explicit limitations on this analysis

• I cannot state how the examiner actually applied any reference. The face of the patent records that these documents were cited; it does not record the rejection grounds. Everything in the "Primary target" columns is my reasoned mapping from each reference's disclosed subject matter to the claim language, not a quotation from the file wrapper.
• Claim 1 is not fully analysable on the printed text. As flagged in the previously generated summary, the published claim 1 begins at element "b)" and refers to "said customer data entry device" without an antecedent "a)" in the record. A complete §102 element‑by‑element analysis of claim 1 is therefore impossible from the published sources; the missing element "a)" would, on the specification's own narrative, recite the data entry device (card reader/keypad) that the Tier‑1 references supply. This is a text‑integrity problem in the published record, not an interpretation I am advancing.
• No live docket/full‑text USPTO verification was completed in this pass. My attempt to reach the USPTO PatentCenter record directly was cut off at the search limit; the bibliographic and citation data above come from the Google Patents full text fetched 2026‑09‑17, cross‑checked against FreePatentsOnline, Justia and SumoBrain, which agree.
• "Cited by" is not prior art. The ~33 (rendered) / 113 (aggregate) forward citations to US 5,979,753 — e.g., Hand Held Products/Metrologic imaging‑reader patents and the Quickvault POS‑processing patents — are later documents that cite this patent. They are not prior art against it and are excluded from the analysis above.

I'll ground the § 103 analysis in the actual cited prior art by verifying key references' content and dates.

Good grounding. Now let me verify the remaining key references I plan to rely on.

Obviousness Analysis of U.S. Pat. No. 5,979,753 under 35 U.S.C. § 103

Building on the earlier sections (bibliographic verification, claim overview, and the litigation/CAFC finding of no live litigation). I do not repeat that material; where it is relevant I cross-reference it.

I. Framework, assumptions, and critical dates

Legal standard. Obviousness is assessed under Graham v. John Deere Co., 383 U.S. 1 (1966) (scope and content of the prior art; differences between the prior art and the claims; level of ordinary skill; secondary considerations), as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). Under KSR, a combination is obvious where the prior art elements are known and combined according to known methods to yield predictable results; where a known technique is applied to a known device ready for improvement; or where the combination is "obvious to try" from a finite number of identified, predictable solutions. It is not necessary that the references expressly suggest the combination — an articulated reasoning with a rational underpinning suffices (In re Kahn, 441 F.3d 977 (Fed. Cir. 2006); MPEP § 2143).

Effective date. The claims take the earliest priority date of September 5, 1996 (this patent is a continuation of Ser. No. 08/706,579, per the "Related Applications" paragraph). All analysis below uses that date.

Critical first observation. The specification's own Background identifies Dutch Patent Application No. 9002296 ("the '296 Application") and U.S. Pat. No. 5,468,942 to Oosterveen et al. as the starting-point self-checkout systems, describing them as: issuing an authorized customer a terminal with an integrated bar-code scanner; maintaining the merchandise list in the scanner's internal memory; downloading that memory through a communication port at a terminal dispenser; printing a receipt; and tendering payment at a checkout register — with occasional auditing for system integrity. That is an applicant admission that most of the claim 1, 3, and 4 environment predates the invention. The listed "Prior art keywords" on the patent's own Google Patents record — customer; data; bar code; code reader; authorization — are essentially the keywords of the claims themselves.

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

A POSITA here is a retail-systems / point-of-sale engineer (B.S. in electrical engineering, computer engineering, or computer science, or equivalent experience) with roughly 2–4 years of experience designing automated checkout, portable data-collection, and POS/host transaction systems, and familiarity with bar-code scanning, card-reader/PIN authorization, and store-host or EFT network interfaces. This is not a highly unpredictable art; it is systems integration of known components (readers, memory, host, printers, payment networks).

III. The prior-art record actually available (and one accuracy flag)

From the "Patent Citations (44)" listing on the patent's own page. The most probative references, with the basis on which they qualify:

⚠️ Flag (do not treat as prior art). The listing includes U.S. 5,804,807 (Symbol, "Scan-ahead system," priority 1996‑09‑12, issued 1998‑09‑08). Its earliest date is seven days after the '753 priority date, and it is commonly owned — it is therefore not available as § 102/§ 103 art against this patent. Likewise the entries under "Family Cites Families" (US 6,144,848; CN 1235446A, 1998; JP 2001125965A, 1999) are later documents citing this family, not prior art. Any obviousness case built on these would be defective.

Evidence limitation: I verified the content of U.S. 5,468,942, 5,072,380, 5,535,407, and 4,929,819 directly in this session. I hit the tool-call limit before pulling full text for NL 9002296, U.S. 5,393,965, and U.S. 5,637,847, so for those I rely on the titles/abstracts as recorded on the patent's prior-art listing — treat those specific characterizations as lower-confidence.

IV. Claim-by-claim obviousness

Claim 1 — authorization-gated update of the customer data file, code from an external EFT system

Preliminary § 112(b) flag (carried from the earlier section, not repeated in full): as printed, claim 1 begins at element "b)" and never introduces element "a)"; element c) refers to "said customer data entry device." I construe the claim two ways (assume "a)" is a customer data entry device; or read the entry device as implicit) because the missing element narrows nothing but makes the metes-and-bounds unclear.

Combination A (primary): NL 9002296 + U.S. 5,468,942 + U.S. 5,535,407 + U.S. 5,072,380

Motivation (KSR rationales 1, 3, 4, 6). Both NL 9002296 and Oosterveen '942 exist to solve the same problem the '753 patent addresses — preventing a scanner from being used to charge purchases to someone other than the customer to whom it was issued — and Oosterveen '942 explicitly adds the identification device and PIN keypad for that purpose. Adding a host-side authorization comparison and EFT-sourced authorization is (i) combination of prior-art elements according to known methods yielding predictable results, (ii) application of a known technique (card/PIN + remote host authorization, as in Oki and Exxon) to a known self-checkout device ready for improvement, and (iii) driven by the recognized market/security incentive (reducing shrink and misuse in unattended scanning). The KSR "finite number of predictable solutions" rationale applies squarely: the designer of a self-scanner system in 1996 had a small menu — local PIN, card swipe, or remote/EFT authorization — and each was known.

Claim 2 — the data entry device is the integrated bar-code reader; authorization data on a bar-coded identification card

Combination B: Combination A + card-based authorization teachings.

• NL 9002296 already uses a customer identification card with reliability coding; Oosterveen '942 uses a card-shaped pass read by card reader 17; U.S. 5,457,307 (Dumont) and U.S. 5,380,991 (Valencia) use customer cards in the self-service redemption/authorization context; U.S. 5,393,965 and 5,412,193 (Symbol, commonly owned) teach mobile supermarket checkout with bar-code handling.
• Motivation: the portable terminal already contains a bar-code reader; using that same reader to read a bar-coded loyalty/authorization card eliminates a separate card-reader component (known design incentive — integration and cost reduction, expressly discussed in this patent's own specification). This is the classic "use of a known technique to improve similar devices in the same way." Claim 2 adds essentially no structural weight.

Claim 3 — combined self-checkout + cash-register system with comparative purchase-history reporting

Combination C: U.S. 4,929,819 (NCR) + U.S. 5,637,847 (Mitsubishi) + U.S. 4,723,212/4,910,672/5,173,851 (Catalina) + U.S. 4,833,308 (Advance Promotion) + U.S. 5,621,812 (Credit Verification) + U.S. 5,572,653 (Rest Mfg.)

Motivation. Retailers had a direct, articulated commercial reason to measure and compare the two customer cohorts: U.S. 4,833,308 and 4,723,212 exist precisely to leverage POS purchase data for targeted promotion; U.S. 5,621,812 is directed to building a database for use with selective incentive marketing in response to customer shopping histories. Once both channels write into one customer database, generating the comparison is an expected, routine use of a general-purpose printer and reporting function — i.e., the improvement is predictable, and the "rational underpinning" is the ordinary desire to evaluate whether the self-scanning investment pays for itself.

Additional § 103 point (printed-matter/non-functional content). To the extent claim 3's only differentiator is the content of what is printed ("comparative analyses… purchasing histories and sales trends… system resource usage"), the printed matter doctrine (MPEP § 2111.05; In re Gulack, 703 F.2d 1381 (Fed. Cir. 1983)) means the informational content is not given patentable weight unless functionally related to the structure. A report-printer printing store reports was known; only the report's subject matter is new, and that does not patentably distinguish.

Claim 4 — session record concatenated onto customer history; authorization code obtained from a remote facility for automatic electronic payment

Combination D: Oosterveen '942 / NL 9002296 + U.S. 5,535,407 (Oki) + U.S. 5,072,380 (Exxon) [or U.S. 5,354,974] + U.S. 5,489,773 (Khyber) / U.S. 5,334,821 (Telxon) / U.S. 4,634,845 (NCR)

Claims 5–8. Dependent claims 5 ("authorization code stored with the customer history") and 6–7 (debit / credit account) are directly met: U.S. 5,072,380 discloses credit/debit-card-based billing stored in the customer's accounting file, and the code-storage limitation is a trivial data-placement choice. Claim 8 (hand-held device having a bar-code reader) is met by Oosterveen '942's hand scanner, NL 9002296's reader, and U.S. 5,468,948 (Norand hand-held data terminal). Dependent claims of this character, adding no new structural cooperation, are obvious for the same reasons as the independent claim.

V. Consolidated motivation-to-combine (KSR rationales, with citations)

1. Combination of known elements according to known methods, predictable results. Self-checkout scanners (NL 9002296; '942), host customer-data files (Oki '407; Exxon '380), EFT authorization (Exxon '380; Base 10 '974), and POS report printers (NCR '819; Exxon '380 claims 15–18) each do what they were designed to do when assembled.
2. Known technique applied to a known device ready for improvement. Card + PIN authorization and host authorization were standard in POS/ATM systems by 1990 (Oki '407; Base 10 '974; NCR '4,634,845); applying them to a self-scanning terminal was the obvious fix for the misuse problem that NL 9002296's "reliability coding" and the '753 specification's "account clear field" were both aimed at.
3. Design incentive / market forces. The court in KSR endorsed exactly this kind of reasoning; here the incentive (shrink control, customer trust, faster checkout, cost of a separate card reader) is articulated in the '753 specification itself and in Oosterveen '942's stated object.
4. "Obvious to try" over a finite, enumerated set. The authorization channel options in 1996 were local PIN, scanned card, and remote/EFT authorization; the patent claims the third.
5. Predictable use of a general-purpose reporting/printer resource for a desired informational output (claim 3), which is additionally weak under the printed-matter doctrine.

VI. What would defeat obviousness (and why I do not see it in this record)

• Teaching away. No reference teaches away from authenticating the returning customer. Oosterveen '942 and NL 9002296 push toward it. This is fatal to a teaching-away rebuttal.
• Unexpected results. No evidence in the specification of a result that was unexpected relative to the references; the spec's benefits (security, reduced misuse) are the very benefits the references pursue.
• Secondary considerations. No commercial-success, long-felt-need, or licensing record appears on the face of the patent; and any commercial success of Symbol's self-scanning product line would require a nexus to the specific claimed limitations (particularly the "external EFT system" code source), not merely to self-checkout generally.
• Only genuinely arguable nonobviousness hook: the claim 1 limitation that the authorization code is received from an external electronic fund transfer system, and claim 4's "remote facility" code source. An applicant could argue that prior-art self-checkout systems perform authorization locally (card/PIN at the dispenser) and that sourcing the authorization code itself from an EFT network is a distinct architecture. That argument is weak given the cited record: U.S. 5,535,407 (Oki) expressly discloses transmitting a transaction to a host computer for authorization and returning the result to the remote facility, and U.S. 5,072,380 (Exxon) expressly discloses credit/debit card billing with host-side "authorized to purchase" determination. The strongest rebuttal would have to distinguish merchant-host authorization from interbank EFT-network authorization — a distinction the claim language ("received from an external electronic fund transfer system") arguably draws but never defines in the specification.

VII. Conclusion, confidence, and flagged contradictions

Conclusion. On the face of the examiner's own cited art, claims 1–8 of U.S. 5,979,753 would very likely be held obvious under § 103. The strongest case is claim 1, over NL 9002296 + U.S. 5,468,942 + U.S. 5,535,407 + U.S. 5,072,380 (or U.S. 5,354,974); claim 4 over the same set with U.S. 5,489,773/5,334,821 for the integrated hand-held reader; claim 3 over U.S. 4,929,819 + U.S. 5,637,847 + U.S. 4,833,308 + U.S. 5,621,812 + U.S. 5,072,380. Claim 3 is additionally vulnerable because its differentiating content is informational (the subject of the printed reports) and therefore entitled to little or no patentable weight. The only limitation with real (but, on this record, still surmountable) nonobviousness potential is the external-EFT/remote-facility source of the authorization code, and that is met by Oki '407 and Exxon '380.

Confidence levels.

• High: that the cited record supplies every structural element of claims 1, 4, and 8 (Oosterveen '942, Oki '407, Exxon '380, NCR '819 verified directly in this session).
• Medium: for claim 3's database-and-reporting sub-combination, because my characterization of U.S. 5,393,965 and U.S. 5,637,847 rests on their recorded titles/abstracts rather than full text (I hit the tool-call limit).
• Low/uncertain: any assertion about what NL 9002296's full text says beyond the abstract-level description recorded on this patent's own prior-art listing.

Flagged items pertinent to this § 103 analysis (not restatements of earlier sections):

1. Claim 1's missing element "a)" is a § 112(b) problem independent of § 103 and limits the precision of any obviousness chart; the chart above analyzes both plausible constructions.
2. U.S. 5,804,807 and the "Family Cites Families" documents are not prior art to the 1996‑09‑05 priority date and must be excluded from any § 103 combination, notwithstanding their appearance in the citation listing.
3. Contradiction check against the earlier sections: nothing in this analysis contradicts the bibliographic verification or the "no confirmed litigation" finding. Note, however, that those earlier sections correctly emphasized that this patent expired 2016‑09‑05; a § 103 invalidity analysis is therefore only relevant retrospectively (e.g., pre-expiration damages exposure) or as a validity proxy for the sibling patents U.S. 5,825,002 and U.S. 6,367,694 B1, which are different patent numbers and would each need their own analysis even though they share this specification.