US 5825002

I'll search for litigation and docket information, then combine it with the authoritative patent text I already have.

Search results — scope note

I searched for the specific number 5,825,002. Two near-miss results surfaced that are not this patent and must not be conflated:

• The Delaware/Cytek–Beckman Coulter summary-judgment brief that repeatedly refers to "the '582 patent" is referring to U.S. Patent No. 10,330,582 (a flow-cytometer patent), not 5,825,002 — the brief's own abbreviations table confirms the number.
• A N.D. Cal. § 290 notice (OpenAI v. Open Artificial Intelligence, 3:23-cv-3918) lists 5,258,002 — a digit-transposed, different patent.

I found no CAFC 2026 docket, no PTAB/IPR, and no district-court assertion naming 5,825,002. I cannot rule out litigation records that are not indexed in the sources I could reach; treat the "no litigation found" statement as a limitation of the search rather than proof of absence.

---

Bibliographic data for US 5,825,002 A

Two prior-art systems are named in the patent's own Background: Dutch Patent Application No. 9002296 and U.S. Pat. No. 5,468,942 (Oosterveen et al.) — the latter also appears as a cited reference of record.

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."

Independent claims in plain language

Claim 1 — Secure session-upload method (return-then-authenticate). A customer returns the portable scanning terminal to a terminal receiver that identifies the terminal by its unique assigned identifier. The central system receives that identifier. Then the customer enters an authorization code on a data entry device, and the system checks that the code matches the specific terminal that was just returned. The customer's data file is updated with the session record only if the code corresponds to that terminal's identifier. The key ordering point is that the code entry happens after the terminal is returned, and the update is gated on an identifier-to-code match.

Claim 5 — Self-checkout system with secure data collection. An apparatus claim. It requires (a) a data entry device for receiving authorization data; (b) data processing and storage with a first memory holding a user file of authorized customers, a corresponding authorization code for each, and a customer data file for each; and (c) a secondary memory holding the session data record. The system updates the correct customer's data file from the secondary memory only when an authorized customer's code is entered and it corresponds to the previously assigned terminal.

Claim 7 — Customer service facility. A service-desk apparatus with (a) a console having a display and data entry device coupled to the central system, able to retrieve both the stored customer data file and the session record held in the portable terminal; (b) a card reader for the customer's loyalty card; and (c) a receipt printer that prints a receipt of the session record upon entry of the loyalty card and the authorization code. This is the "exception handling" track for customers whose transactions went wrong.

Claim 8 — Temporary-memory holding method. The system stores a customer authorization code; the terminal's session record is downloaded to a temporary memory location (not the customer file); the customer enters the authorization code; and only then is the record uploaded from temporary memory into the customer data file. This is the broadest-sounding formulation of the gating concept — it omits the terminal-return and identifier-matching steps of claim 1.

Claim 9 — Method including payment processing. Combines the secure-update sequence (return terminal to receiver, store customer data file with authorization code, enter the code) with the additional step of processing payment for the session data record, so that both the file update and the payment are conditioned on entry of the stored authorization code.

Claim 10 — Selective activate/deactivate of the terminal. Distinct from the security claims. The terminal has active and inactive modes and only records items in active mode. The authorized customer's identification entry is registered in memory; the terminal is issued in active mode; scanning/entering the customer ID on the terminal's own integrated data entry device toggles it to inactive; re-entering toggles it back to active; this can be repeated during the session. The specification's stated use case is a shopper who wants to leave the scanner unattended (e.g., in a cafeteria or fitting room) without children accidentally adding or deleting items.

Claim 11 depends on claim 10 and specifies that the integrated data entry device is a bar code scanner and the customer identification entry is a bar-coded customer loyalty card.

Notes and uncertainties

• The Google Patents family listing shows priority dates of 1996-09-05 across many descendant applications, which appears to be a display artifact for the family rather than accurate priority dates for each filing. I would verify individual family members before relying on those dates.
• Assignment history recorded: 1996-09-05 assignment to Symbol Technologies, Inc. (assignor Roslak); 2005 security interest to JPMorgan Chase; 2010 release; 2014 security agreement with Morgan Stanley Senior Funding; 2015 change of name to Symbol Technologies, LLC; 2015 release.
• Status "Expired – Lifetime" is Google's characterization, not a legal conclusion; the 20-year term from the 1996-09-05 filing would have run to 2016-09-05 absent any extension or terminal disclaimer.
• I did not find authoritative evidence of any litigation or post-grant proceeding involving this specific patent. If enforcement activity matters to your analysis, a docket-level (PACER/Docket Navigator/Lexis) check should be run rather than relying on the web-indexed sources I used.

I'll research litigation involving US Patent 5825002. Let me run several targeted searches.

Let me search additional litigation databases and the Unified Patents portal for this specific patent.

Summary

Based on my searches, I found no evidence of any litigation (district court, ITC § 337, CAFC, or PTAB) that asserted or involved U.S. Patent 5,825,002. I want to be explicit and honest about this rather than generate plausible-sounding but fabricated case entries.

What I searched and what I found

Cases that came up but are NOT this patent (important not to conflate)

The searches surfaced several Symbol Technologies matters that involve different patent numbers. These are not litigation over 5,825,002:

• Symbol Technologies v. Lemelson Medical, Education & Research Foundation — D. Nev., Nos. CV-S-01-701-PMP(RJJ) to CV-S-01-703-PMP(RJJ) (declaratory judgment on Lemelson patents; patents-in-suit were e.g. 4,338,626; 4,511,918; 4,969,038; etc. — none is 5,825,002).
• Metrologic Instruments v. Symbol Technologies — laser bar-code reader patents (Markman ruling Sept. 29, 2006).
• Symbol Technologies v. Metrologic line (e.g., '297 and '186 patents; historic cases C-84-20051 and 86-8736).
• ITC Inv. No. 337-TA-551, Certain Laser Bar Code Scanners and Scan Engines (Symbol as complainant, 2007) — asserted scanner patents, not 5,825,002.

Important caveats on my confidence

• Search tools, not full dockets: I was working through general web search and the publicly indexed Unified Patents portal; I could not run a direct PACER/CAFC query or RPX/Docket Alarm litigation lookup within my available steps. It is possible a low-profile suit exists that is not well indexed.
• Citing ≠ asserting: I deliberately did not count declaratory-judgment actions, IPRs, or prior-art citations involving other Symbol patents as litigation for this one.
• Patent status context: Per the Google Patents record, US 5,825,002 (filed 1996-09-05, granted 1998-10-20, "Expired – Lifetime," anticipated expiration 2016-09-05) is one of a family with continuations US 5,979,753 and US 6,367,694 bearing the same title. If you are doing a freedom-to-operate or family-level check, those sibling patents should be searched separately, as an assertion could exist on a family member even if 5,825,002 itself was never asserted.

Bottom line

I cannot identify any plaintiff, defendant, jurisdiction, case number, filing date, or outcome for litigation involving U.S. Patent 5,825,002, because no such litigation appears in the sources I was able to search. If you need a definitive negative, I'd recommend a direct PACER/CAFC Docket search and a Lex Machina/Docket Alarm (RPX) query keyed to the exact number 5,825,002 and its two same-title family members, 5,979,753 and 6,367,694. I'd be glad to walk through those specific queries if you can share portal access.

PTAB / AIA Trial Proceedings — US 5,825,002 ("Device and method for secure data updates in a self-checkout system")

Analyst note on sourcing: The structured "PTAB proceedings on file" block states the USPTO ODP API returns no AIA trial proceedings for this patent, and directs me to treat "no PTAB activity on file" as the default while flagging anything web search surfaces. I ran targeted searches (Unified Patents portal, PTAB petition PDFs, CourtListener, Google Patents, general IPR/PGR/CBM queries). No AIA trial proceeding (IPR, PGR, or CBM) naming US 5,825,002 as the challenged patent surfaced. I did not invent any numbers. The one recurring hit — "US 5,825,002 A … Roslak" — appears only as a cited prior-art reference inside other parties' IPR petitions (e.g., petitions concerning Walmart's self-checkout patents such as US 10,121,133 and US 11,853,988). The "'582 patent" discussions in Intellectual Ventures petitions are a different patent and must not be conflated with 5,825,002.

---

Proceedings overview

Total AIA trial proceedings on US 5,825,002: 0 (0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denied). There are no IPRs, PGRs, or CBM reviews to report. The defensively relevant fact is not a PTAB outcome but the patent's legal status: per the authoritative record, 5,825,002 has an anticipated expiration of 2016-09-05 and carries the legal status "Expired - Lifetime." That expiration — not any trial result — is the bottom-line driver of a defendant's posture today.

---

Per-proceeding detail

There are no proceedings to detail. No {PROCEEDING_NUMBER} entries can be listed because none exists on the record, and I will not fabricate one. To be explicit about the categories the task asks for:

• Type / Filed / Status / Judge panel / Petition grounds / Institution decision / FWD / Settlement / Appeal — not applicable; no proceeding on file.
• Family companions: the same-family continuation patents US 5,979,753 (filed 1998-09-15) and US 6,367,694 (filed 1999-11-09) also show status "Expired - Lifetime" in the record and likewise surfaced no AIA trial activity. (Source: Google Patents family table, https://patents.google.com/patent/US5825002/en.)

---

Strategic summary

Claim status — none canceled, none sustained through PTAB, all "untested" at the Board. Because no AIA trial was ever filed, no claim of 5,825,002 has been canceled or affirmed by the PTAB. Claims 1–11 (the only independent claims being 1, 5, 7, 8, 9, and 10, with dependents 2–4, 6, and 11) carry only their original, unadjudicated scope. The absence of PTAB narrowing means there is no "surviving claims" list to build around and no FWD to quote — the claim set is whatever the face of the patent says. The strongest structural attack on the patent is not a PTAB record but the calendar: the patent expired 2016-09-05.

Estoppel landscape is empty — and moot. With no IPR/PGR/CBM, there is no § 315(e)(2) or § 325(e)(2) estoppel against anyone. A defendant is therefore not barred from raising any prior-art ground in district court — but this is a hollow benefit, because the expiration date dominates. Infringement requires acts during the patent term (before 2016-09-05); combined with the 6-year damages lookback from today (2026-10-01), the practical window for past damages has closed. Any assertion today would have to rest on pre-2016 conduct and would face a laches/SOL problem in addition to invalidity. Note the pre-AIA landscape: this patent predates the AIA, so any challenge posture is governed by pre-AIA § 102/§ 103 and the familiar § 282 burden framework.

Pattern signals — none of the usual ones. No serial petitioner (no petitioner filed even once, let alone multiple times). No patent-owner PTAB appeal activity, because there was never a decision to appeal. No Federal Circuit appeal. No defensive aggregator (e.g., Unified Patents) appears as a petitioner against this patent — a Unified Patents portal page exists for the patent, but that is an informational page, not evidence of a filed challenge. It is worth stating plainly: well-asserted patents eventually attract IPRs; this one never did, which — combined with its 2016 expiration — is consistent with a patent that was not a live monetization target during the IPR era.

---

Recommended next steps

• If you are a defendant receiving a demand letter citing US 5,825,002: lead with expiration. The patent's term ended 2016-09-05 (anticipated expiration, "Expired - Lifetime"). An expired patent cannot support ongoing or prospective infringement relief; you are at most facing a pre-2016 past-damages theory, which collides with the 6-year limitations period. Demand the plaintiff identify the specific pre-2016 accused acts and the damages period it claims.
• Confirm no PTAB activity independently before relying on this memo. The authoritative source for AIA proceedings is the USPTO PTAB E2E / Patent Trial and Appeal Board End-to-End system (https://ptacts.uspto.gov/) and the Open Data Portal (https://developer.uspto.gov/api-catalog). Where I cite an opinion, the neutral research repositories are the PTAB Decisions site and CourtListener (https://www.courtlistener.com/). Per the instructions, the ODP block is canonical, and it returned zero proceedings; my web search corroborates but is not a substitute.
• Check the family before responding. The same-family continuations US 5,979,753 and US 6,367,694 appear to share the 1996-09-05 priority and show "Expired - Lifetime" status in the record. Because a demand letter may cite these siblings instead, verify each one's status and expiration (they should share the ~2016 term) before drafting a response. Also verify whether any later, unexpired patent claims priority to this family — that, and not 5,825,002 itself, would be the only live exposure.
• If an active proceeding ever appears (it has not, on this record): the statutory milestones to diary are institution decision (~6 months from petition), oral hearing, and FWD within one year of institution (extendable to 18 months for good cause). None of these are live here.

Bottom line: There is no PTAB activity on US 5,825,002. The patent is expired (2016-09-05), its family continuations also appear expired, and the absence of any IPR — while often a signal that a patent is a soft target — is secondary here to the expiration date. A demand letter citing claims 1–11 of this patent should be answered first on term/laches grounds, with a merits-based invalidity fallback built on the pre-AIA prior art (e.g., the references already cited on the face of the patent: NL 9002296, Oosterveen US 5,468,942, and the self-checkout art cited by the examiner).

Caveat on confidence: I am highly confident there is no AIA trial proceeding of record, based on the canonical ODP block plus corroborating searches. I could not verify internal (non-public) settlement discussions, pre-AIA inter partes reexaminations, or district-court/ITC litigation history from the sources searched; if your matter turns on those, pull the full litigation and reexam histories directly before relying on this summary.

I'll research the assignment chain for this patent, starting with the legal events I have and then searching for USPTO Assignment Center records.

Let me search for more specific assignment record details.

Let me look for the specific assignment records and the 2014 securitization.

I've gathered what I can. Note upfront: my tool access yielded the Google Patents legal-events record and two PLANsite assignment-index hits, but not the Assignment Center/Assignment Search record detail (reel/frame numbers and correspondent-of-record). I will not fabricate those fields. Everything below is grounded in the legal-events block of the authoritative patent text plus the PLANsite hits; where a field is unavailable I say so plainly.

Inventors

Unusual-pattern check: No evidence of inventors departing within 12 months of filing. This was a standard employee assignment-of-interest recorded the same day the application was filed (1996-09-05) — the normal in-house pattern for a large corporate filer. No fire-sale precursor signal.

Original assignee

Symbol Technologies, Inc. (Holtsville, New York 11742-1300), per the assignment record and the patent face.

• Line of business: automatic identification and data capture — hand-held bar code scanners, mobile data terminals, RFID, and wireless LAN equipment. This is exactly the product line the patent's claims describe (portable bar code terminal issued at a self-checkout dispenser), so the original assignee was an operating company that shipped products in the claimed technology space.
• Status: acquired by Motorola (2006/2007) and folded into Motorola Solutions; Motorola Solutions' Enterprise business (including Symbol) was acquired by Zebra Technologies for ~$3.45B, completed October 2014. Symbol Technologies today survives as Symbol Technologies, LLC, a wholly owned Zebra Technologies subsidiary. It is not dissolved, and it is not in bankruptcy.

Assignment timeline

The following is every recorded ownership/security event shown in the patent's legal-events record. Caveat: the Google Patents legal-events feed gives a single date per event and the conveyance type, but does not expose reel/frame numbers, execution-vs-recording dates, or the correspondent of record. Those fields require the Assignment Center record itself, which I could not retrieve. Dates below are the dates reported by Google Patents (most likely recording dates).

• 1996-09-05 (recorded as of filing) — Reel not retrieved

  • Conveyance: Assignment of assignors' interest
  • Assignor: Thomas Roslak
  • Assignee: Symbol Technologies, Inc.
  • Correspondent: not retrieved (no correspondent data surfaced)
  • Context: standard inventor-to-employer assignment executed at filing.

• 2005-01-05 — Reel not retrieved

  • Conveyance: Security Interest
  • Assignor: Symbol Technologies, Inc.
  • Assignee: JPMorgan Chase Bank, N.A. (as secured party)
  • Correspondent: not retrieved
  • Context: securitization — the patent pledged as collateral under a Symbol credit facility. Not a transfer of ownership.

• 2010-12-03 — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: JPMorgan Chase Bank, N.A.
  • Assignee: Symbol Technologies, Inc.
  • Correspondent: not retrieved
  • Context: release — the 2005 JPMorgan security interest was discharged; ownership returns to Symbol/Symbol's successor unencumbered by that lien.

• 2014-10-31 — 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 tied to Zebra Technologies' acquisition financing of the Motorola Enterprise business. All four grantors are Zebra-family entities; this is a corporate-family collateral pledge, not a transfer to an asserter. Confirmed as a PLANsite-indexed assignment (assignment id 7725435, "Patent Assignment from Zih Corporation; Laser Band, LLC; Zebra Enterprise Solutions Corporation; and Symbol Technologies, Inc. to Morgan Stanley Senior Funding, Inc.").

• 2015-07-08 — Reel not retrieved

  • Conveyance: Change of Name
  • Assignor: Symbol Technologies, Inc.
  • Assignee: Symbol Technologies, LLC
  • Correspondent: not retrieved
  • Context: change of name / internal reorganization only — same corporate family (Zebra), no change in beneficial ownership. Confirmed as a PLANsite-indexed assignment (assignment id 6805875, "Patent Assignment from Symbol Technologies, Inc. to Symbol Technologies, LLC").

• 2015-08-17 — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Morgan Stanley Senior Funding, Inc.
  • Assignee: Symbol Technologies, Inc.
  • Correspondent: not retrieved
  • Context: release — the 2014 Morgan Stanley security agreement was discharged.

Current owner of record: Symbol Technologies, LLC (per Google Patents "Current Assignee"). No assignment to any third party, NPE, or licensing entity appears anywhere in the chain. The patent reached its anticipated expiration on 2016-09-05 and its legal status is Expired – Lifetime — i.e., the corporate chain is the entire ownership history.

Timeline diagram

timeline
    title Ownership of US 5825002
    1996 : Filed and assigned to Symbol Technologies Inc
    2005 : Security interest to JPMorgan Chase
    2007 : Symbol acquired by Motorola
    2010 : JPMorgan security interest released
    2014 : Security agreement with Morgan Stanley
         : Zebra acquires Motorola enterprise unit
    2015 : Change of name to Symbol Technologies LLC
         : Morgan Stanley security interest released
    2016 : Patent anticipated to expire

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. The only entity-name change is Symbol Technologies, Inc. → Symbol Technologies, LLC (2015-07-08), a Change of Name conveyance, not a sale. No "IP / Licensing / Holdings / Ventures" shell appears anywhere in the recorded chain. (Note: the "LLC" suffix here is a corporate conversion within Zebra, not an anonymous single-purpose vehicle.)

2. Known asserter in the chain — Not present. No assignee in the chain matches any published NPE list (Acacia, Marathon, IV, Wi-LAN, Conversant, Vringo, Pendrell, Round Rock, etc.). The secured parties (JPMorgan Chase, Morgan Stanley Senior Funding) are lenders perfecting liens, not asserters.

3. Repeat correspondent across the chain — Unclear / not retrievable. The Assignment Center correspondent-of-record was not exposed in the sources I could reach. I will not infer intent from this field absent the actual records. A single recurring recorder would be expected here given all six events were filed by/for one corporate family, but I cannot cite reel/frame to confirm it.

4. Cascading transfers — Not present. Assignments are 1996 → 2005 → 2010 → 2014 → 2015 → 2015, spaced across two decades and all internal or lender-related. No rapid chained-LLC sequence.

5. Pre-litigation transfer — Not present. The earlier litigation review found no infringement suit naming US 5,825,002, so there is no suit date against which to measure a transfer window.

6. Bankruptcy fire-sale — Not present. No Symbol/Motorola/Zebra Chapter 7 or 11 sale of this patent; the 2014 event is acquisition financing, not a distress sale.

7. Privateering — Not present. No transfer from an operating company to an NPE asserting on its behalf. Zebra/Symbol retained the asset and later let it lapse.

8. Defensive aggregator — Not present. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. It terminates at an operating-company subsidiary (Zebra).

Verdict

Operating-company assertion — with an explicit caveat: only the operating-company prong is documented; no suit enforcing this patent was found, so the "is suing actual competitors" element of the label is unmet. This is most accurately a non-NPE, operating-company-held patent, and if the menu permitted a sixth option I would call it "operating-company holding, non-asserted."

Justification: every recorded event is internal or lender-related — the 1996-09-05 inventor-to-employer assignment, the 2005-01-05 JPMorgan security interest and its 2010-12-03 release, the 2014-10-31 Morgan Stanley security agreement (Zebra-family grantors; PLANsite id 7725435) and its 2015-08-17 release, and the 2015-07-08 Change of Name to Symbol Technologies, LLC (PLANsite id 6805875). The current assignee is a wholly owned subsidiary of Zebra Technologies, an operating company that ships bar code scanners and mobile computers embodying this claim space. Zero NPE signals are present, and the earlier litigation review independently found no assertion of this patent. This finding is consistent with — and does not contradict — the prior litigation summary.

Verification: USPTO Assignment Search — https://assignment.uspto.gov/patent/index.html (search by patent number 5825002), and the Assignment Center at https://assignmentcenter.uspto.gov/. I was unable to pull the reel/frame and correspondent fields directly; those should be read off the Assignment Center record for the six events dated 1996-09-05, 2005-01-05, 2010-12-03, 2014-10-31, 2015-07-08, and 2015-08-17 to complete the record. Google Patents legal-events source: https://patents.google.com/patent/US5825002/en.

Flagged gap (not a contradiction): the two sibling family members named in the prior section — US 5,979,753 and US 6,367,694 — carry the same title and should be assignment-searched separately; their chains could differ from this one.

I'll ground this analysis in the patent's own citation-of-record list (which I have in full from the authoritative text), then verify the most important references via search.

Let me verify a few more of the citation-of-record references.

Prior-Art Analysis — U.S. Patent No. 5,825,002

Tool note / scope limitation: My search session hit its step limit before I could full‑text‑read every one of the 40 references. I verified the full text of the most material references (US 5,468,942; US 5,397,882; US 5,637,847; US 5,424,524; NL 9002296/NL 191499 and the related Heijn EP 0 681 273 family). For the remainder, descriptions are drawn from the citation‑of‑record list in the authoritative patent text plus my background knowledge, and are flagged accordingly. Treat every "potentially anticipates" statement as a candidate that must be confirmed against the reference's full text before it is relied on.

---

1. Confirming the patent being analyzed (literal‑ID discipline)

The record retrieved is US 5,825,002 A — "Device and method for secure data updates in a self‑checkout system," App. No. 08/706,579, filed 1996‑09‑05, granted 1998‑10‑20, sole inventor Thomas Roslak, original assignee Symbol Technologies, Inc. (now Symbol Technologies LLC), status Expired – Lifetime.

Because the instruction is to return results for this exact number only, I explicitly do not fold in these near‑miss identifiers that surfaced and are different patents:

• US 5,258,002 — digit‑transposed; appears in an unrelated N.D. Cal. § 290 notice.
• US 10,330,582 — "the '582 patent" in a Cytek/Beckman‑Coulter brief; a flow‑cytometer patent.
• US 5,825,002's own same‑title family members US 5,979,753 and US 6,367,694 (continuations) — same disclosure, but different numbers; not prior art to themselves.

---

2. Critical framing: two different "citation" sets, only one of which is prior art

The Google Patents record contains two things that are easily confused:

The task asks for "each patent citation for 5825002," so the analysis below is keyed to the 40 cited references. I flag two additional non‑patent items named in the applicant's own Background — Dutch Patent Application No. 9002296 (which is in the 40) and U.S. Pat. No. 5,468,942 (Oosterveen) (which is also in the 40 as US 5,468,942). A separate "Family Cites Families (14)" list appears in the record but is a Google‑Patents display construct of family/related art and is not part of this patent's § 102 citation set.

Pre‑AIA § 102 baseline (filing 1996‑09‑05, so AIA §§ 102/103 do not apply):

• § 102(b) — published > 1 year before filing → published before 1995‑09‑05.
• § 102(a) — published before the invention date but not more than 1 year before filing (roughly 1995‑09‑05 to 1996‑09‑05).
• § 102(e) — described in a U.S. patent granted on an application filed before the invention date (this can rescue a reference published after 1996‑09‑05, e.g., US 5,637,847 published 1997‑06‑10).
• Foreign patents/specifications (NL, JP, WO, DE) qualify only under § 102(a)/(b) by their publication date — they get no § 102(e) benefit.

---

3. Tier 1 — The closest art (self‑checkout + portable scanner + customer authentication)

These are the references against which the independent claims are actually tested.

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

• Full citation: Netherlands Patent Application 9002296 A; granted as NL 191499 B/C. Title: "Self‑service bar‑code reader and totaliser — uses added customer identification card with reliability coding."
• Dates: Priority/filed 1990‑10‑22; published 1992‑05‑18 (NL 9002296 A); granted 1995‑04‑03 / 1995‑08‑04 (NL 191499).
• § 102 basis: Published before 1995‑09‑05 → § 102(b) statutory bar (and § 102(a)).
• Description: Portable bar‑code reader issued to a shopper who presents a customer identification card carrying "reliability coding"; shopper self‑scans items into the reader's memory; the reader is read out at the exit and the total computed, with reliability/spot‑check controls.
• Claim(s) potentially anticipated: Claim 1 (issuance to an identified customer; readout of the terminal; verification of the customer credential), Claim 5 (customer file + corresponding authorization credential), Claim 8 (stored customer code; download session record; verify before updating), Claim 9 (return/readout + identification before the transaction is completed). This is the single most pertinent § 102 reference on file and is named in the patent's own Background, i.e., an admitted prior design.

3.2 — US 5,468,942 A (Oosterveen et al.; Ahold Retail Services AG) — "the Oosterveen Patent"

• Full citation: U.S. Patent 5,468,942, "Dispensing device for hand scanners accessible from two sides."
• Dates: Priority 1994‑04‑18; published 1995‑11‑21.
• § 102 basis: Published 1995‑11‑21 (after 1995‑09‑05, before filing) → § 102(a); also a U.S. patent so § 102(e) as of its 1994‑04‑18 filing.
• Description (verified full text): A rack/dispenser with a plurality of holders for hand scanners, accessible from two sides, that both dispenses and receives scanners. It includes an identification device 15 that determines the customer's identity and clears one of the scanning devices for that customer, implemented as a card reader 17 for a card‑shaped pass plus an optional keyboard 17′ for a PIN code and a display 18. After use, the scanner is placed back in the dispenser and read out.
• Claim(s) potentially anticipated: Claim 1 steps (a)–(b) (return to a receiver that identifies the terminal), Claim 5 (system issuing a terminal to an identified authorized customer), Claim 6 (a terminal receiver holding the returned scanner — the holder/cavity structure maps to "locking means" only if the reference's holder physically retains the unit; this element needs full‑text confirmation). The card‑reader‑plus‑PIN identification device maps to claim 5(b)'s "authorization code for each authorized customer."
• Admitted prior art: Named in the applicant's Background.

3.3 — US 5,397,882 A (Van Solt; Ahold Retail Services AG)

• Full citation: U.S. Patent 5,397,882, "Method for spot checking a client in a self‑service store."
• Dates: Priority 1993‑05‑14 (app. Ser. No. 08/063,581); published 1995‑03‑14.
• § 102 basis: Published before 1995‑09‑05 → § 102(b).
• Description (verified full text): Scanner is issued to a client only after the client presents a customer pass that is automatically read/recognized; at the exit the scanner is coupled to the readout station and the customer pass is identified at the same time, whereupon a check parameter stored on the pass (or in the computer) governs whether a spot check occurs.
• Claim(s) potentially anticipated: Claim 1 element (e) (the system identifies the customer at the point of readout/return, i.e., matches a customer credential to the scanner being returned) and Claim 8 (a stored customer credential consulted before the session record is finalized). Note: US 5,397,882 is the parent incorporated by reference into US 5,637,846/Heijn‑type filings, so its disclosure carries forward.
• Assessment: Strongest cited art on the "identify the customer at the readout station" concept, but its stated purpose is check selection, not authorization to update the data file. As a clean § 102 anticipation of claim 1 it is arguable; as § 103 art it is powerful.

3.4 — US 5,637,847 A (Watanabe; Mitsubishi Denki K.K.)

• Full citation: U.S. Patent 5,637,847, "Automated shopping basket system with accounting and article tracking functions."
• Dates: Appl. No. 400,853 filed 1995‑03‑08; priority listed 1994‑03‑10; published 1997‑06‑10.
• § 102 basis: Published after the 1996‑09‑05 filing, so it is not a § 102(a)/(b) reference; it qualifies only as § 102(e) based on its 1995‑03‑08 U.S. filing date. (This distinction matters — an examiner citing a 1997 publication must rely on the § 102(e) filing date.)
• Description (verified): Cart/basket‑mounted article registering unit, calculator, display, alarm, transmitter/receiver, and an external memory storing program/sale data received from a host computer; a card reader at the accounting unit allows settlement by credit or bank card; accounting data is transmitted to the accounting unit at the counter.
• Claim(s) potentially anticipated: Claim 5(c) (secondary/external memory holding the session record before settling), Claim 8 (temporary memory holding the record prior to posting to a customer file), Claim 9 (payment processing conditioned on the account settlement step). Not a good fit for the portable‑scanner‑returned‑to‑dispenser architecture of claims 1/6.

3.5 — US 5,424,524 A (Ruppert et al.)

• Full citation: U.S. Patent 5,424,524, "Personal scanner/computer for displaying shopping lists and scanning barcodes to aid shoppers."
• Dates: Priority 1993‑06‑24; published 1995‑06‑13.
• § 102 basis: § 102(b) (published before 1995‑09‑05).
• Description (verified): Handheld CCD bar‑code scanner with microprocessor, memory, display/touchscreen, and a bidirectional communication port / IR LAN interface; scans as the shopper shops, keeps a running total, downloads a store price list, and uploads scanned data to the store computer over a hardwired or infrared link; includes a credit‑card facility whose stored card information is downloaded to the store computer for payment.
• Claim(s) potentially anticipated: Claim 5 (handheld scanner + central processing/storage + separate memory), Claim 8 (scanned record held locally then uploaded; a customer credential — credit card — entered before the transaction is completed), Claim 9 (payment processing tied to the entered card data). Directly parallels the upload‑and‑pay architecture, though without the return‑to‑dispenser + identifier‑match gating.

3.6 — US 5,345,071 A (Dumont) and US 5,457,307 A (Dumont)

• Citations: U.S. Patent 5,345,071, "Shopper's purchase monitoring device" (priority 1992‑04‑27; pub. 1994‑09‑06, § 102(b)); U.S. Patent 5,457,307, "Portable self‑service bar code marker and reader for purchase monitoring" (priority 1992‑04‑27; pub. 1995‑10‑10, § 102(a)/(e)).
• Description: Portable handheld bar‑code reader/marker carried by the shopper to register selected items, with an erase/"minus" function for items put back.
• Claim(s) potentially anticipated: Claim 5 (portable data‑collecting terminal architecture), Claim 10 (portable terminal recording/deleting items during a session — the add/remove mechanic is shared, though the reference does not disclose toggling the terminal between active/inactive via the customer's own ID entry).

---

4. Tier 2 — Self‑checkout / portable‑terminal field art (enabling / § 103 background)

None of these is a clean § 102 anticipation of an independent claim; they are field‑establishing / § 103 references showing that portable scanners issued to customers, downloaded to a central system, and paid for at checkout were well known by 1996.

---

5. Tier 3 — Coupon / customer‑history / marketing art (least relevant to the data‑security claims)

These appear on the citation list primarily because the challenged claims recite a "customer data file," a "loyalty card," and "authorization code." They disclose customer‑profile databases and loyalty identification, but not secure gating of a session‑record upload. They are at most § 103 art for the "customer data file / customer card" recitations.

---

6. Tier 4 — Peripheral / non‑analogous references

---

7. Claim‑by‑claim § 102 posture for the strongest candidates

Bottom line on § 102: taken as a set, the 40 cited references supply the field (self‑checkout, portable scanning, customer cards, temporary storage of a session record, card‑based payment) but do not, on the record I could verify, anticipate independent claims 1, 5, 8, 9, or 10 in full. The strongest single § 102 arguments are against claims 6 and 8; the rest of the citation list reads as § 103 (obviousness) and background art, which is consistent with the patent having issued over it.

---

8. What the cited art does not teach (the point of novelty)

Across all 40 references, no single reference is shown to disclose the ordered combination: (i) returning the specific terminal to a receiver that reads its unique assigned identifier, (ii) then entering a customer authorization code, (iii) confirming that code corresponds to that terminal's identifier, and (iv) only then updating the customer file (and/or processing payment). The two concepts most heavily leaned on by the cited art — identify the customer (NL 9002296, US 5,468,942, US 5,397,882) and stage the session record in a temporary/secondary memory (US 5,424,524, US 5,637,847) — are separated in the prior art and joined and gated in the claims. Likewise, the active/inactive toggle by customer card of claims 10–11 appears to be without a cited counterpart.

---

9. Honest gaps and recommended verification steps

1. Filing‑date vs priority‑date: The Google table lists priority dates, not always the underlying U.S. filing dates. For § 102(e) references (US 5,637,847; US 5,621,812; US 5,572,653; US 5,478,989; US 5,489,773; US 5,468,948; US 5,457,307), the actual application filing date must be confirmed from the front page, because that is what sets the § 102(e) date.
2. Foreign‑reference dates: NL 9002296 / NL 191499, JPH 03249003, and the two WO references must be dated by publication, not filing; only NL 9002296 (pub. 1992‑05‑18) is comfortably a § 102(b) bar.
3. Unverified descriptions: I full‑text‑verified only six references. The remaining descriptions in Tiers 2–4 are title‑derived and should be spot‑checked, particularly the two WO references and US 5,418,713 / JPH 03249003, which appear non‑analogous.
4. Citations of record ≠ rejections of record: The 40‑reference list reflects examiner consideration, not necessarily an anticipation rejection. The prosecution history (file wrapper / IFW) would show which of these were used under § 102 versus § 103, and should be pulled before any validity opinion is finalized.
5. I could not complete a PACER/PTAB docket pull for this patent within the available steps (consistent with the earlier "no litigation found" limitation).

If you want, I can next (a) rank these 40 by strength as § 103 art rather than by § 102 candidacy, or (b) build an element‑by‑element claim chart for claims 1 and 5 against US 5,468,942 and US 5,397,882, flagged for full‑text confirmation.

I'll ground the obviousness analysis in the actual cited prior art by checking a few key references, then build the § 103 combinations.

Let me verify a few more of the cited references that are central to the claim charts.

Obviousness Analysis — U.S. Patent No. 5,825,002 (35 U.S.C. § 103)

Building on the prior sections: The summary section established the claim set (independents 1, 5, 7, 8, 9, 10; dependents 2–4, 6, 11), the 1996-09-05 priority date, and the two background-named references (NL 9002296 and U.S. 5,468,942). The litigation section found no assertion/PTAB history — which matters here because it means there is no record evidence of secondary considerations (commercial success with nexus, unexpected results, licensing, praise, failure of others) to rebut a prima facie § 103 case. I do not repeat those sections; the analysis below uses the Prior Art / Citations (38) listing of the patent record.

Throughout, numbers are interpreted literally and I do not silently correct identifiers. Where I rely on a family member of a cited reference, I say so and flag the date.

---

0. Framework and ground rules

The governing test is Graham v. John Deere Co., 383 U.S. 1 (1966), as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007): (1) scope/content of the prior art; (2) differences between the art and the claims; (3) level of ordinary skill; (4) secondary considerations. A combination is obvious where the references disclose the claimed elements, the art is from the same field (or a field of endeavor with a known problem to which the references are directed), and a POSITA would have had a reason to combine with a reasonable expectation of success — KSR; In re Keller, 642 F.2d 413 (CCPA 1981) (test the combined teachings, not each reference in isolation).

Level of ordinary skill (proposed): A bachelor's degree in electrical/computer engineering (or equivalent), plus ~2 years' experience in retail point-of-sale / self-scanning systems; or a lower formal degree with more field experience. This is the level the references themselves target — NL 9002296, the '942 patent, and the '882 patent are all supermarket self-scanning systems.

Applicant-Admitted Prior Art (AAPA) — an important § 103 hook. The specification's Background expressly names NL 9002296 and U.S. 5,468,942 (Oosterveen et al.) as disclosing the entire self-checkout architecture (issue scanner to identified customer → accumulate item list in scanner memory → download at dispenser → print receipt → pay at register). It then frames the invention's problem as securing returns and updates. Statements in the specification describing the prior art as teaching those features are admissions that may be used as prior art in a § 103 rejection. See MPEP § 2129. So the only genuinely open question for most claims is the gating/security layer, not the self-checkout framework.

References that qualify as prior art (representative dates):

All are in the same field of endeavor (self-service/portable data collection and checkout) or are analogous arts of generic transaction-authorization, so they are proper prior art for combination.

---

1. Claim 1 — return → identify → authenticate → update

Elements: (a) return terminal to receiver; (b) communicate the terminal's unique assigned identifier to the central system; (c) enter auth code after return; (d) communicate the code; (e) confirm code corresponds to the assigned identifier; (f) update the customer file only if they correspond.

Primary combination: NL 9002296 (or its U.S./EP family equivalent) + U.S. 5,468,942 + U.S. 5,397,882.

• NL 9002296 teaches issuing a portable scanner to a customer whose customer pass is read/recognized; the pass may be "encoded electronically and/or magnetically, which makes automatic identification possible"; the scanner stores scanned item codes in memory; the customer hands the scanner in at a readout station which reads the memory. It also teaches the "reliability coding" check concept.
• U.S. 5,468,942 teaches (i) an identification device (card reader 17 with PIN keypad 17′) at the dispenser; (ii) that the identification device "determines the identity of a customer and subsequently clear[s] one of the scanning devices … for use by that customer" — i.e., a specific terminal is bound to a specific identified customer; and (iii) that the rack "can serve not only as a dispensing device … but also as a receiving device for used hand scanners." That supplies elements (a) and the assigned-identifier ↔ customer linkage.
• U.S. 5,397,882 teaches that at the readout station "the scanner is coupled with the readout device and at the same time the customer pass is identified … the check parameter is determined," and that the check parameter may be "stored in the memory of the computer with the name of the client." That supplies elements (b)/(e) (the system compares the identified pass with the scanner record just read) and (f) (a per-client computer record).

Reason to combine / motivation: Every reference is directed to the same problem — preventing fraud and mis-association in self-registration. The '882 patent's whole object is verifying that "the information stored in the memory is correct" and deterring cheating via a per-client check parameter; the '942 patent explicitly notes it can be monitored "whether a scanner is handed in again." A POSITA implementing those incentives would naturally (i) read the returned scanner's identifier together with the presenting customer's card at the readout, and (ii) refuse to post the session to the customer's account unless the two match — because that is precisely what "the customer pass is identified … at the same time" in '882 already achieves. Ordering the code entry after return (elements c–d) is the inherent dataflow of an at-readout verification station.

Expected success: High — the references already perform card reading at the dispenser and at the readout; the only added step is a comparison of two already-available data items.

Note on the "corresponds to the assigned identifier" limitation: A tight reading requires a code↔terminal-ID match, not merely code↔customer. The references satisfy this because the dispenser assigned the specific scanner to the specific card (’942: "clear one of the scanning devices … for use by that customer"; the system "can be monitored whether a scanner is handed in again"). Thus the post-return pass read inherently confirms the presented code against the identifier of the terminal that was issued to that customer.

---

2. Claim 2 — communicate the receiver's location address

Combination: U.S. 5,468,942 + NL 9002296.

• '942 discloses the rack divided into sections "provided with an identifying mark at a properly visible place" (top pieces 12′ marked "A, B, C"), and a computer 32 connected to the dispensing device. The rack knows which holder released which scanner.
• Communicating that slot/section designation to the central system alongside the terminal identifier is a predictable design choice (KSR: combination of known elements according to known methods) that enables the central processor to track dispenser inventory and slot occupancy — exactly the rationale the '002 specification itself gives ("the electronic marking is … a means for identifying the location of the bar code reader by the central processor").

This is the easiest dependent claim to knock out under § 103.

---

3. Claim 3 — lock the terminal in the receiver after return, before code entry

Combination: U.S. 5,468,942 (alone or + '882).

• '942 claim 4 expressly recites that "each accommodating cavity comprises controllable locking means for locking or selectively releasing a hand scanner," and the spec describes a locking member 44 lockable/unlockable by an electromagnet 43. That is the claimed locking mechanism structurally.
• The ordering limitation (lock after return, before auth-code entry) is the natural, inherent sequence of a "receive-then-verify" station: detaining the device until verification is the stated security purpose ("If the bar code reader 40 was returned by someone who stole … the bar code reader 40 is kept in the system until it is released by the authorized person" — the '002 spec, but the same deterrent logic is why the '942 rack locks on return).

Motivation: theft and mis-return prevention — a recognized problem in the same field. High expectation of success. This claim is strongly obvious, bordering on anticipation of the locking structure by '942.

---

4. Claim 4 — alert at the service facility on code mismatch

Combination: U.S. 5,397,882 + U.S. 4,929,819 (+ '942 display 18 / enquiry counter 31).

• '882 discloses "an automatically operating device … which, depending on the check parameter determined, generates a signal indicating whether a check should take place" — i.e., a signal to store personnel when a client's data fails verification.
• '929,819 discloses that error records generated during scanning "aid" the cashier. '942 discloses a display 18 at the identification device.
• Motivation: notifying an attendant of misuse is the routine automation of the '882 "signal" concept and of a store's existing exception-handling at the enquiry counter.

One caveat: claim 4 recites the alert is generated when the code does not match a recognized code, whereas '882's signal is generated when the check parameter triggers a spot check. The two are closely analogous (both are "verification failed → alert operator"), and KSR permits combining familiar elements for their known purpose; but if a challenger wants a cleaner read, the mismatch-alert feature can also be sourced from the generic exception-handling of '542/'942. Rate claim 4 obvious but slightly less airtight than claims 2–3, 6.

---

5. Claim 5 — the system (apparatus) claim

Elements: (a) data entry device; (b) data processing/storage with a user file of authorized customers + a corresponding authorization code for each + a customer data file for each; (c) secondary memory storing the session record; update on entry of an authorized customer's code corresponding to the previously assigned terminal.

Combination: NL 9002296 / U.S. 5,397,882 (primary system) + U.S. 5,468,942 (assignment & locking) + U.S. 5,334,821 or U.S. 5,354,974 (data-entry device / authorization-gated account record).

• '882 supplies (b): a per-client computer record ("parameter … stored in the memory of the computer with the name of the client") and the readout station that reads the scanner memory into the computer (c).
• '942 supplies the customer-identification data-entry device (card reader 17/keypad 17′) and the assignment of a specific terminal to a specific customer, satisfying the "previously assigned portable data collecting terminal" clause.
• For the "user file with an authorization code per authorized customer," the cleanest secondary source is the U.S. 5,334,821 (Telxon portable POS) and/or U.S. 5,354,974 (Base 10 ATM), both of which embody the well-known paradigm of a customer file/personal-identification-code (PIN) that gates access to or modification of a stored account record. This is a famously familiar element (the ATM/PIN model) and KSR instructs that combining a known technique to improve a similar device in the same way is obvious.

Motivation: security of the customer data file (the '002 spec itself notes the importance "that individual customer data files be secure"); using a stored code per customer to gate an account-file write is the standard, predictable solution. "Secondary memory" for temporary staging (scanner memory / readout buffer before posting) is inherent to the '882/'296 readout architecture.

Strength: Moderate-to-strong; the "authorization code stored per customer in a user file" element is the piece a challenger must source from a second reference (Telxon/Base 10), but that is exactly the kind of predictable combination KSR endorses.

---

6. Claim 6 — terminal receiver with locking means for the portable terminal

Combination: U.S. 5,468,942 (directly), optionally + NL 9002296.

• '942 claim 4 / '942 claim 1(c)–(d) recite accommodating elements in a rack with controllable locking means for locking/releasing hand scanners, the rack acting as both dispenser and receiver. This discloses claim 6's "terminal receiver … having locking means … upon the return of the portable data collecting terminal after the generation of the session data record" essentially verbatim.

This is the strongest § 103 (and arguably § 102) position in the patent. If '942 alone does not literally reach it, it does so in view of the '002 Background's admission that '942 is the dispenser/receiver art.

---

7. Claim 7 — customer service facility (console + card reader + receipt printer)

Combination: U.S. 5,397,882 + U.S. 4,929,819 + U.S. 5,468,942.

• '882: the readout station prints a receipt after reading the scanner; the computer holds the client record; the enquiry counter/exception flow is the service-desk function.
• '929,819: a point-of-sale terminal 82 with keyboard 84, display monitor 86, and printer 88, coupled to data processing means, used to retrieve/verify scanner data and print a transaction record — i.e., a console with display + data entry + printer coupled to the central system.
• '942: the customer card reader and the enquiry counter 31 adjacent to the rack; "the receipt printer, if desired, could be arranged next to the rack as a separate unit."

Motivation: to handle exceptions (customer questions, illegible/missing receipt, errors) — a recognized need expressly noted in the '002 spec ("In the event a customer should lose a printed receipt or receive an illegible copy … a customer receipt printer is also provided"). Combining a loyalty-card reader (’942), a display/keypad console (’929,819), and a receipt printer (’882/’942) at a service station is the predictable assembly of known components for their known functions.

Strength: Moderate. The single distinguishing nuance is that claim 7 couples the session record held in the portable terminal to the service console for retrieval — but '929,819 already couples the removed module to the checkstand's data processing means and printer, so the combination covers it.

---

8. Claim 8 — temporary-memory staging method (the broadest claim)

Elements: store auth code; download the session record to a temporary memory location; enter the code; upload from temporary memory to the customer data file upon entry of the code.

Combination: NL 9002296 / U.S. 5,397,882 + U.S. 5,334,821 or U.S. 5,434,394.

• '882 / '296: the scanner's stored session is read into the store computer at the readout station — necessarily into some memory location before it becomes part of the permanent client record.
• The "temporary memory then commit-on-authorization" pattern is a generic, well-known data-processing technique (transaction staging/commitment), the same paradigm found in ATM/authorization systems (Base 10 '974) and order/account systems (Tandy '394).

Motivation / KSR: Using a staging buffer and committing the record only after authorization is a predictable, conventional software design choice to preserve data integrity and avoid posting unverified sessions — a design incentive identified in the field (fraud/error prevention).

Strength: Moderate. Because claim 8 deliberately omits the return step and the identifier-matching of claim 1, it is the broadest claim; that breadth cuts against non-obviousness (fewer limitations to distinguish over the art), but it also means the "temporary memory" limitation carries the weight. Expect a challenger to argue that reading scanner memory into a conventional readout buffer (’882/'296) meets "temporary memory," and that committing to the customer file only on code entry is the '882 per-client verification in its simplest form. Expect the patentee to argue "temporary memory location" is a distinct structural feature; that argument is weakened by the absence of any special structure recited.

---

9. Claim 9 — secure update plus payment processing

Elements: return terminal to receiver; store customer data file with an authorization code; enter the authorization code on a data entry device; update the file AND process payment for the session upon entry of the code.

Combination (near-anticipatory): NL 9002296 + U.S. 5,397,882 + U.S. 5,468,942, with the electronic-payment/passage feature supplied by the Ahold paying-device family (NL 9400743 / EP 0 681 273) or by U.S. 5,334,821 (Telxon POS) / U.S. 5,354,974 (Base 10) for PIN-gated payment.

• The Ahold paying-device disclosure (found in the search record as EP 0 681 273 A1, which is the European counterpart of the NL 9400743 "self-registration … electronic payment" application that itself cites NL 9002296) states: "a scanner is issued to the client upon his presenting his identity card … after the scanner has been read out, the client pays electronically without intervention of store personnel upon presenting his payment card … After electronic payment the store arrangement automatically grants the client passage." That is secure update + payment conditioned on card/PIN entry.
• U.S. 5,468,942 supplies the card-reader + PIN keypad; '882 supplies the client record.

Motivation: combining payment at the readout/exit with the same pass that authorized issuance is the evident, stated goal of the Ahold system (reduce queues, allow exit without personnel intervention). KSR: predictable combination of the '882/'296 identification + the payment station.

Date caveat (important): EP 0 681 273 / NL 9400743 sit close to the one-year § 102(b) line relative to the 1996-09-05 filing and are not in the '002 front-page citation list. I therefore rest claim 9's payment element primarily on the cited references (Telxon '821 / Base 10 '974 for PIN-gated payment coupled to an account record) and treat the Ahold paying-device art as corroborating. Do not rely on the uncited EP document without confirming its exact publication date.

Strength: Moderate-to-strong for claim 9 provided the payment element is read as conventional PIN-gated electronic payment (which the cited Telxon/Base 10 references support).

---

10. Claim 10 — selectively activate/deactivate the portable terminal via the customer's ID

Elements: active/inactive modes; register the customer ID entry in memory; issue terminal in active mode; toggle to inactive by entering the customer ID on the terminal's own integrated data entry device; toggle back on re-entry; repeat.

Combination: U.S. 4,071,740 (Gogulski) + NL 9002296 / U.S. 5,468,942 (customer ID card).

• Gogulski '740 discloses a portable scanner/control-panel with "an on-off switch 36 to activate or deactivate control panel 12," a "ready light which indicates that items can be entered into the cart," a "travel button light to indicate that the cart is in movement and not able to accept entries," and logic whereby "an unauthorized entry will cause the shopping cart to cease operating." That is the active/inactive, record-only-when-active functionality of claim 10.
• NL 9002296 / '942 supply the customer identification card and its reading at the terminal.
• Motivation: substituting the card/ID entry for Gogulski's manual on/off button is an obvious ergonomic/security choice (the customer is already carrying the card; the card identifies who is toggling), and the specification's own stated purpose — preventing accidental scans "by children" while the device is unattended — is a familiar concern addressed in Gogulski by its entry-control lights/buttons.

Strength: Weakest of the independents for a § 103 attack. The combination is defensible on motivation, but a patentee can argue that Gogulski's mode switching is cart-based and button-actuated, and that no reference suggests the same customer-identification entry serving as the toggle. This claim is where a challenger should expect the most resistance and where a well-crafted secondary-considerations story (if one existed) would have the most traction — but per the litigation section, no such record evidence has been located.

---

11. Claim 11 — bar-coded scanner + bar-coded loyalty card

Combination: NL 9002296 + U.S. 5,468,942 (directly).

• Both teach a bar-code/optical scanner and a customer pass/loyalty card used to identify and clear the terminal; '942 expressly contemplates a "card-shaped pass … electronically and/or magnetically recognize[d]," and the '296 system uses bar-code scanning throughout. Making the identification entry a bar-coded loyalty card read by the scanner is the natural, predictable implementation given both references.

Strength: Strong. Merely obvious.

---

12. Cross-cutting § 103 rationales (KSR)

Across all claims, the same four rationales recur:

1. Same field / same problem. All primary references are self-scanning supermarket systems addressing fraud, mis-association, and throughput. Combining references from the same field with a common problem is presumptively obvious.
2. Predictable combination of known elements. Identification card + assigned terminal + readout station + authorization code + account record are each known; the claimed gating is their arrangement for their known purposes.
3. Design incentive / market pressure. "Known technique to improve similar devices in the same way" — KSR; the field was actively racing to make self-scanning fraud-resistant (the '882 check-parameter, the '942 monitoring, the Ahold electronic payment) as of 1996.
4. Obvious to try with a finite, predictable set of solutions. Given NL 9002296 / '942 / '882, the POSITA had a small, identified set of options (verify at readout, gate the file write on a PIN/card, lock the returned device) and predictable success.

No teaching away is apparent in any cited reference; none disparages code-gated updates or locking-on-return.

---

13. Overall assessment and defensive notes

Strong § 103 positions (likely defensible rejections):

• Claim 6 — locking receiver: '942 essentially anticipates; obvious even if not.
• Claim 3 — lock-on-return before code entry: '942 locking structure + inherent ordering.
• Claim 2 — location address: '942 sections + computer; design choice.
• Claim 1 — return→identify→verify→update: '296/'882 + '942.
• Claim 11 — bar-coded card: '296 + '942.

Moderate positions (combination-dependent):

• Claim 5 — needs the "stored authorization code per customer" element from a secondary reference (Telxon '821 / Base 10 '974).
• Claim 7 — service-desk console: '929,819 + '882 + '942.
• Claim 8 — temporary-memory staging: broadest claim; turns on whether a conventional readout buffer reads on the limitation.
• Claim 9 — payment + update: moderate-to-strong; the payment element must come from cited art (Telxon/Base 10) or, if used, the uncited Ahold EP document (date-verify first).

Weakest position:

• Claim 10 — ID-based toggle: Gogulski gives mode switching but by button; motivation exists, suggestion is the weak link.

Secondary considerations: None evidenced. The prior-section finding that the patent was never asserted and has no located post-grant proceedings means there is no litigation or licensing record to support an objective-indicia argument. If a patentee later proffers commercial success (Symbol's system) or industry praise, look for the nexus to the gated-update/locking features (not to self-checkout generally, which is concededly old), and to whether the success post-dates the 1995–96 prior art.

Caveats on this analysis:

• I worked from the patent's own citation list plus verification searches; I did not run a full reexamination/§ 102(b) date audit for every reference. The '942 and the Ahold paying-device family members warrant exact date confirmation (one is § 102(a)/(e) rather than § 102(b); one is uncited and near the one-year line).
• I did not locate any express prior-art "statement of motivation" beyond what the references themselves state; the motivations above are reasoned from the references' stated purposes and the field's common problems, consistent with KSR's instruction to consider "the background knowledge possessed by a person having ordinary skill in the art."
• Whether any specific claim is ultimately invalid depends on claim construction (especially "temporary memory," "corresponds to the assigned identifier," and "secondary memory"), which I have flagged rather than resolved.