US 6571218

I'll verify the patent's current status and check for any 2026 CAFC activity before summarizing.

US Patent 6,571,218 — Verification Note

I ran searches against Google Patents, FreePatentsOnline, Justia, and uspto.report for the exact number 6,571,218, plus targeted searches for any CAFC 2026 docket activity. I did not find any Federal Circuit or district-court docket entry referencing this patent in 2026, which is consistent with its expired status. The full patent text supplied in your message is treated as authoritative and is the basis for the summary below.

⚠️ One caveat on the record: a body of CAFC 2026 summaries surfaced in the searches (e.g., Teva v. Lilly, No. 2024-1094 (Fed. Cir. Apr. 16, 2026); LKQ v. GM, 102 F.4d 1280), but none involve '218. I found no authoritative evidence of '218 litigation, so I cannot represent that none exists — only that my searches did not surface any.

Bibliographic Data

Uncertainty flag: Google Patents explicitly labels the assignee/priority/legal-status fields as assumptions, not legal conclusions. The "NCR Voyix Corp" designation reflects a corporate name change plus a recorded security interest, not a verified assignment chain.

Abstract (as issued)

"In a system for processing store interventions in a network of self-checkout terminals, self-checkout terminals monitor the self-checkout activities performed to determine whether an issue has arisen requiring intervention by store personnel. Detected issues are prioritized and placed into an issues log. A remote authorization station connected into the network accesses the issues log to review and resolve the issues that have arisen in priority order. Further, where it is determined that an issue has arisen at a self-checkout terminal that cannot be resolved at that terminal, the transaction is suspended and then resumed at a personnel-operated terminal."

Plain-Language Overview of the Independent Claims

Claim 1 — System claim

A retail transaction system with two cooperating pieces:

1. A network of self-checkout terminals where customers scan and pay themselves. Each terminal watches its own checkout activity to detect when an issue has arisen that needs a store employee to intervene, and drops each detected issue into an issues log.
2. A remote authorization station connected into that same network. It reads the issues log and lets store personnel review and resolve the pending issues in priority order.

The key structural point: the issues log sits between the terminals and the authorizer, so one remote operator handles many lanes — and the claimed system does not require the terminal to halt while the issue is pending.

Claim 15 — Method claim

The corresponding process, in five steps:

• (a) Monitor customer activity at the self-checkout terminals.
• (b) Determine whether any issue has arisen at any terminal that requires store-personnel intervention.
• (c) Store any such issues in an issues log.
• (d) Determine whether the transaction is done at a terminal and whether issues remain to be resolved at the remote authorization station.
• (e) If both are true, access the issues log from the remote authorization station and resolve the issues remotely.

Note the temporal gating in step (d): remote resolution is triggered after the transaction is "done" (specification says this is normally a tender or a critical device error).

Dependent Claims — Grouped Themes

Parallel / non-blocking processing (claims 2, 7, 8): Issues are resolved remotely in parallel with the customer continuing additional (or ongoing) self-checkout activity at the same lane; data is exchanged between the station and the terminal over an interprocess communication (IPC) mechanism (spec: shared memory or named pipes).

Operator interface (claims 3–6): A display lists the issues across lanes; each networked terminal gets a graphical representation, carrying a graphical indication of whether an issue exists plus a numerical priority indicator; the display is a touchscreen with buttons for resolving issues. (Spec: tri-color red/yellow/green light bars, FIFO priority numbering, max 12 lanes, 800×600 resolution.)

Suspension and lane handoff (claims 9–14): The terminal suspends a transaction for an issue unresolvable there; the lane is then freed for the next customer; a personnel-operated checkout terminal continues the suspended transaction; the self-checkout terminal prints a bar-coded receipt; the staffed terminal scans that receipt and resumes the transaction. (Spec: the customer may then tender by check, food stamps, coupons, etc.)

Method dependents (16–18): Step (c) includes prioritizing the log so (e) resolves in priority order; post-step-(e) suspension at the self-checkout lane plus continuation at a staffed terminal; and the bar-code print/scan mechanism for doing so.

Technical Context Worth Noting

• Architecture: Windows-based PC remote station; communication between the Remote Approval Program (RAP) and self-checkout software via Microsoft DCOM and ActiveX — a detail that dates the disclosure and bears on any modern claim-construction or § 101 analysis.
• Stated motivation over prior art: the specification distinguishes itself from a prior remote-approval system in which "each situation is handled at the time the issue is created," and emphasizes separating self-checkout-specific approvals from the store's general business algorithms.
• Cited prior art of record (4): JPS55119772A (Tokyo Electric Co.); US 5,937,386 (Frantz); US 6,032,128 and US 6,167,381 (both NCR). Two non-patent citations reference pscnet.com self-checkout pages.
• Notable forward citations: US 7,558,742 (Fujitsu, multi-device supervisor support for self-checkout, 2001 priority) and US 10,121,133 (Walmart Apollo, self-checkout with a mobile device) both cite '218.

Confidence Statement

High confidence on all bibliographic fields, the abstract, claim text, and dependent-claim themes — these come from the full patent document you supplied. Moderate confidence on current ownership, since the Google Patents assignee list is expressly flagged as non-authoritative. Low confidence / no evidence found regarding any 2026 CAFC docket for this patent; because the patent expired 2019-04-14, active enforcement in 2026 would be unusual, but I cannot affirmatively rule out post-expiration proceedings (e.g., an IPR or a damages-phase case on pre-expiration conduct) on the basis of the searches performed.

I'll search for litigation involving US patent 6571218 across patent litigation resources.

Let me search more specifically on litigation databases and PACER-type sources.

Summary of Findings — U.S. Patent No. 6,571,218

Bottom line: I could not identify any known litigation involving U.S. Patent No. 6,571,218.

Despite searching for the exact number 6571218 / 6,571,218 in connection with patent litigation databases and general web sources, no district court action, ITC investigation, PTAB proceeding, or CAFC appeal naming this patent as the patent-in-suit was found.

Supporting details

Patent identity (confirmed):

• U.S. Patent No. 6,571,218 B1 — "Remote approval system and methods for use in network of retail checkout terminals"
• Inventor: Robert F. Sadler; Original assignee: NCR Corporation; Current assignee (per Google Patents): NCR Voyix Corp
• Appl. No. 09/291,708; filed 1999-04-14; granted 2003-05-27
• Legal status: Expired – Lifetime; anticipated expiration 2019-04-14 (i.e., the patent term has already ended). Source: https://patents.google.com/patent/[US6571218B1](/patent/US6571218B1)/en

Why the number-6571218 hits I found are NOT litigation involving this patent:
The exact-number matches returned by search were all false positives — occurrences of "6571218" as an unrelated identifier, not as the asserted patent:

• A Kansas personal-injury docket (De Macias Gonzalez v. Haulster Transport, Ltd., 6:25-cv-01015) — "6571218" appears only as a PACER receipt number for a filing fee.
• A Brazilian court administrative order (PORTARIA Nº 9865/2022) — "6571218" is a case-document/attachment ID.
• A French health-insurance payment table — "6571218" is a compensation accounting code.
• A federal highway-safety regulation excerpt — "§571.218" (49 CFR) mis-matched by the numeral string.

The one patent-prosecution context where the patent number appears: 6571218 shows up merely as one entry in a list of patent numbers in a search query recorded in the file history of a different patent (a petitioner's exhibit filed in PTAB IPR2022-01471, BJ's Wholesale Club Holdings, Inc. v. Walmart Apollo, LLC). Being cited in a novelty search string is not evidence of litigation — it confirms only that the patent exists and was searched against.

Caveats on this answer (important)

I want to be explicit about the limits of what I checked, per the instruction not to fabricate:

• My tools returned web-search results only. I was not able to directly load a live query on the Unified Patents litigation portal (https://portal.unifiedpatents.com/litigation/caselist), PACER, or Docket Alarm's patent-litigation page for this specific number. Those databases may contain records not surfaced by general web search.
• Given the patent expired on 2019-04-14, it is an unlikely target for infringement assertion in recent years, which is consistent with finding no active litigation.
• I found no evidence of any case — active or terminated — naming US 6,571,218 as a patent-in-suit. But "no evidence found" is not the same as "definitively none exists."

Recommended next steps to confirm

If you need a definitive negative:

1. Run the number directly in the Unified Patents litigation portal and Docket Alarm's patent page.
2. Run a PACER case-search / CourtListener RECAP search on the patent number.
3. Check the USPTO Patent Center "Litigation" / assignment tab and the USPTO Assignment records for this patent (which show only security-interest reassignments to JPMorgan Chase and Bank of America, and the NCR→NCR Voyix change of name — no litigation-related records).

If you'd like, I can re-run the search specifically against the Unified Patents portal URL and CourtListener for this exact number so we can close the gap in coverage.

I'll start by checking for any PTAB proceedings, Federal Circuit appeals, or CBM reviews involving this patent.

No PTAB hits so far. Let me run targeted follow-ups against PTAB-specific sources, CBM review (this is a G06Q business-method patent), and any district-court assertion that could have spawned a challenge.

PTAB Proceedings — US 6,571,218 B1

"Remote approval system and methods for use in network of retail checkout terminals"
Inventor: Robert F. Sadler · Original assignee: NCR Corporation · Current assignee: NCR Voyix Corporation
Priority/filing: 1999-04-14 · Granted: 2003-05-27 · Claims: 1–18 (independent claims 1 and 15) · Legal status: Expired – Lifetime (anticipated expiration 2019-04-14)

Proceedings overview

Total AIA trial proceedings on file: zero (0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials). The USPTO Open Data Portal returns no AIA trial proceedings for US 6,571,218, and my independent web checks surfaced no IPR, PGR, or CBM petition, no PTAB Final Written Decision, and no Federal Circuit appeal arising from this patent — so the defensive posture for a defendant is not "hardened by prior IPR" or "claims canceled," but rather an untested, un-narrowed patent that is also past the end of its statutory term and outside the § 286 damages lookback, which makes PTAB practice largely beside the point.

Verification note: The canonical source is the structured "PTAB proceedings on file" block, which reports no proceedings from the ODP as of the most recent ingest. Search-engine results were noisy and did not surface any proceeding number tied to this patent. I could not independently query PTAB E2E / PTACTS directly within this run, so I flag the absence as well-supported but not guaranteed — confirm with a docket-number search at PTAB E2E and a party search at CourtListener before filing anything that depends on it. I do not have reliable web evidence of any district-court assertion of this specific patent either.

Proceedings

None to report. There is no proceeding number to list, no petitioner, no panel, no institution decision, and no FWD. Per the operating instructions, the default for this patent is "no PTAB activity on file," and nothing found contradicts it. I will not manufacture a proceeding number, panel, or claim-level disposition.

Strategic summary

Claim status: all of claims 1–18 are UNTESTED. No claim of US 6,571,218 has ever been canceled, confirmed, or construed by the PTAB. Claim 1 (a system comprising a network of self-checkout terminals that monitor activity, detect "issues" requiring store intervention, and place them into an issues log, plus a remote authorization station that resolves those issues "in priority order") and claim 15 (the corresponding method) stand exactly as issued in 2003. The dependent claims — 2–14 (parallel resolution, display of a lane list, per-terminal graphical representations with numerical priority indicators, touchscreen buttons, IPC-based data sharing, transaction suspension, freeing the lane, bar-coded receipt printing/scanning at a personnel-operated terminal) and 16–18 (prioritization, suspension, and the bar-code resume flow) — are likewise un-adjudicated. Because nothing was ever narrowed, the full scope of the originally granted claims is the operative claim scope, subject only to whatever a district court does with them.

Estoppel landscape: effectively empty. Section 315(e)(2) estoppel is petitioner-specific; with no petitioner, no IPR/PGR/CBM was ever filed, and no third party is statutorily barred from raising § 102/§ 103 art it "raised or reasonably could have raised." A defendant today is free to run any prior-art ground it can find — including the references already on the face of the patent (JPS55119772A; US 5,937,386 to Frantz; US 6,032,128 and US 6,167,381, both NCR) and the examiner-cited non-patent literature (the pscnet.com self-checkout pages), none of which has been tested in a contested proceeding. Beyond the four of-record references, the self-checkout art from 1997–1999 is deep (note, e.g., NCR's own US 6,408,279 on remote-supervisor intervention — a same-assignee sibling — and IBM's later US 2005/0283402 application on remote attendant intervention), which historically made this a patent vulnerable to § 103 attack. That vulnerability was simply never converted into a PTAB challenge.

Pattern signals: none of the usual ones. There is no repeat petitioner, no defensive aggregator (no Unified Patents or similar) in the chain, no patent-owner appeal history, and no multi-petition campaign — because there was no proceeding at all. The assignee chain is an operating company throughout (NCR Corp → JPMorgan security interests → NCR Voyix Corp, with a 2023-10-25 Bank of America security interest), not an NPE. That profile is consistent with a patent NCR never needed to litigate or defend: it is prior-art-adjacent to NCR's own commercial self-checkout line and was cited against later third-party applications (e.g., it appears as prior art in IBM's Chinese patent CN 103593926 B), which signals it is regarded in the art as background rather than as a crown-jewel assertion asset.

The real defensive point is the calendar, not the PTAB. The patent's legal status is Expired – Lifetime, with an anticipated expiration of 2019-04-14 (20 years from the 1999-04-14 filing; no patent term adjustment is reflected in the status data). If that date holds, two things follow: (1) there is no injunction exposure and no ongoing-infringement theory — only pre-expiration damages under 35 U.S.C. § 284; and (2) the § 286 six-year lookback means the last actionable pre-expiration conduct (2019-04-14) had to be sued on by roughly 2025-04-14, which has now passed as of today (2026-09-27). Caveat: Google Patents' "anticipated expiration" is a computed assumption, not a USPTO certificate; I have not verified whether a terminal disclaimer, PTA award, or a continuing/continuation-in-part family member extends or re-covers this subject matter. Treat the expiration date as highly likely but confirm it against the USPTO Patent Center before relying on it to defeat a demand.

Recommended next steps

1. Confirm the absence of PTAB activity and the expiration date directly. Run the patent number through PTAB E2E and the USPTO Open Data Portal, and pull the Patent Center file wrapper to (a) confirm no Certificate of Correction, PTA award, or post-issuance challenge, and (b) confirm the expiration/reinstatement calculation and any terminal disclaimer. The absence of IPR activity here is a weak signal on its own — the patent is from 1999 and expired in 2019, so it aged out of the AIA trial window rather than "surviving" challenges.

2. If a demand letter cites claim 1 or claim 15, attack the damages theory first, not validity. Note that the patent has no PTAB record, so there is no FWD to link to and no cancellation to quote — do not let opposing counsel imply otherwise. The dispositive issue is whether any accused conduct occurred on or before the expiration date and within the six-year lookback of § 286.

3. Preserve prior-art defenses even though no IPR exists. Because no proceeding was ever filed, there is no § 315(e) estoppel, so a full slate of § 102/§ 103 grounds remains available in litigation or in a new IPR — but note that IPR of an expired patent is of limited practical utility (no amendment, and the value is retrospective). If you need a claim-construction or invalidity ruling for a past-damages defense, that fight belongs in district court on the issued claim text.

4. Check for family members and related NCR patents before assuming you are clear. Same-assignee relatives such as US 6,408,279 (remote supervisor terminal with transaction suspension) cover overlapping functionality and may have different, later expiration dates. A demand built on "the self-checkout remote-approval family" rather than on the '218 patent number alone would need a separate freedom-to-operate pass.

Nothing in this report should be read as a finding that any claim of US 6,571,218 is valid, invalid, infringed, or not infringed — no tribunal has ever decided any of those questions for this patent.

I'll reconstruct the assignment chain from the authoritative patent text you supplied, then verify against USPTO Assignment Center and related sources.

Let me try to pin down specific reel/frame records and check the asserter/NPE directories.

Let me check the asserter directories and try once more for the specific reel/frame records.

⚠️ Data-access caveat up front: The USPTO Assignment Center record pages for this patent were not retrievable in my search session, so I could not verify reel/frame numbers, execution dates, or the correspondence-of-record fields for this specific patent. What I can reconstruct with confidence is the ownership chain as reported in the Google Patents legal-events tab of the document you supplied (which mirrors the same underlying USPTO assignment records but omits reel/frame). Where I am inferring rather than confirming, I say so. Do not treat any reel/frame as verified — none are reproduced below because none were confirmed.

Inventors

Pattern check — no departure signal. Sadler's inventor profile (Patent Leaderboard, keyed to NCR) shows 15 granted US patents spanning 1994–2024, i.e. continuous NCR-lineage inventorship well past this patent. That is the opposite of the "all inventors gone within 12 months → portfolio fire-sale" pattern. There is no evidence of inventor exit preceding a transfer, and the sole inventor never appears as an assignor to anyone other than NCR. (patentleaderboard.com/ncr/robert-sadler/677360)

Original assignee

NCR Corporation (now NCR Voyix Corporation), Atlanta, GA.

• Primary line of business: point-of-sale, self-checkout, ATM hardware/software and retail banking technology. NCR is the company that commercialized the cash register (1884, National Cash Register Co.) and is a direct lineage entity.
• Did it ship a product embodying the claims? Yes — NCR's SelfServ / FastLane self-checkout line is the commercial embodiment of a multi-lane self-checkout network with a supervising attendant station, which is exactly the claimed subject matter. The specification's own architecture (network of self-checkout lanes + a remote approval station + a staffed terminal) describes NCR's own self-checkout product family.
• Current status: Operating. NCR split on 2023-10-16 into NCR Voyix (digital commerce / self-checkout, NYSE: VYX, ticker changed 2023-10-17) and NCR Atleos (ATM network business). The NCR Corporation → NCR Voyix transition was effected as a name change, consistent with the Google Patents legal event. (britannica.com/money/NCR-Voyix-Corporation; ncratleos.com news release)

Assignment timeline

Reconstructed from the Google Patents legal-events tab of the authoritative document. Reel/frame not available — see caveat.

• 1999-04-14 (executed) / same-date recording — Reel not verified

  • Conveyance: Assignment of assignors' interest ("see document for details")
  • Assignor: Robert F. Sadler (inventor)
  • Assignee: NCR Corporation
  • Correspondent: not verified (typical for a 1999 inventor-to-corporate assignment; NCR's portfolio prosecution counsel of record is Schwegman, Lundberg & Woessner, P.A., Minneapolis — but I could not confirm that firm on this record)
  • Context: initial corporate ownership — standard inventor assignment on filing.

• 2014-01-15 (recorded) — Reel not verified

  • Conveyance: Security Agreement
  • Assignor: NCR Corporation and NCR International, Inc.
  • Assignee: JPMorgan Chase Bank, N.A., as Administrative Agent
  • Correspondent: not verified
  • Context: securitization — blanket collateral grant of the NCR patent portfolio to a lender syndicate; no transfer of beneficial ownership.

• 2016-04-18 (recorded) — Reel not verified

  • Conveyance: Security Agreement
  • Assignor: NCR Corporation and NCR International, Inc.
  • Assignee: JPMorgan Chase Bank, N.A.
  • Correspondent: not verified
  • Context: securitization — amendment/restatement of the 2014 collateral grant.

• 2023-10-25 (recorded) — Reel not verified

  • Conveyance: Release of Patent Security Interest
  • Assignor: JPMorgan Chase Bank, N.A., as Administrative Agent
  • Assignee: NCR Voyix Corporation
  • Correspondent: not verified
  • Context: release of the 2014/2016 lien contemporaneously with the NCR split.

• 2023-10-25 (recorded) — Reel not verified

  • Conveyance: Security Interest
  • Assignor: NCR Voyix Corporation
  • Assignee: Bank of America, N.A., as Administrative Agent
  • Correspondent: not verified
  • Context: re-securitization — new lender group takes a collateral position over the same portfolio post-spin.

• 2023-12-07 (recorded) — Reel not verified

  • Conveyance: Change of Name
  • Assignor: NCR Corporation
  • Assignee: NCR Voyix Corporation
  • Correspondent: not verified for '218. Nearest confirmed comparator: a separate, same-type NCR → NCR Voyix Change of Name recording (USPTO assignment 69419/561, executed 2023-10-13, recorded 2024-11-27) carries correspondent Schwegman, Lundberg & Woessner, P.A., Minneapolis. That firm is NCR's long-running prosecution/assignment counsel, not an NPE-side agent. Flagging only as a lead — I have not confirmed it appears on '218's own record. (plainsite.org assignment id 12087437)
  • Context: change of name only — the substantive beneficial owner did not change; the same entity was renamed.

Net substantive finding: across 24 years there is no third-party transfer of ownership. Every post-1999 entry is either a bank collateral grant/release or the corporate name change. Ownership has remained continuously with NCR Corporation / NCR Voyix Corporation.

Timeline diagram

timeline
    title Ownership of US 6571218
    1999 : App filed by NCR Corporation
         : Inventor assignment to NCR
    2003 : Patent issued
    2014 : Security agreement to JPMorgan Chase
    2016 : Second security agreement to JPMorgan Chase
    2019 : Anticipated expiration
    2023 : JPMorgan Chase release
         : Security interest to Bank of America
         : Name change to NCR Voyix Corporation

NPE / troll-pattern signals

1. Shell-entity transfer — not present. No assignee carries an "IP / Patents / Licensing / Holdings / Ventures" suffix; no registered-agent service address appears; no single-member Delaware/Texas LLC anywhere in the chain. The only non-NCR names are JPMorgan Chase Bank, N.A. and Bank of America, N.A. as collateral agents (2014-01-15, 2016-04-18, 2023-10-25), which is lender securitization, not a licensing vehicle.

2. Known asserter in the chain — not present. None of Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN/Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, or Spangenberg entities appears. Current assignee NCR Voyix is an operating company with $2.54B revenue and a live product line.

3. Repeat correspondent across the chain — unclear / no evidence. I could not retrieve the correspondent field for '218. The one correspondent I did surface (Schwegman, Lundberg & Woessner on a separate NCR→Voyix Change of Name record) is an operating-company prosecution firm, not an NPE-side recording agent. Per the task's own rule, a single appearance is not a finding, and here the appearance isn't even on '218's record. Calling this not present on the evidence available.

4. Cascading transfers — not present. Six recordings over 24 years, all corporate housekeeping/securitization; no chained LLCs, no <24-month clustered transfers, no shared-principal addresses.

5. Pre-litigation transfer — not present. I found no infringement suit naming '218 (Google Patents shows no "Litigation" events; searches of Justia/RPX/Unified surfaced none). The last assignment of any kind is the 2023-12-07 name change. With no suit, the pre-litigation-transfer test cannot be triggered.

6. Bankruptcy fire-sale — not present. NCR did not file Chapter 7/11. Its 2023 event was a voluntary corporate separation (spin-off), not insolvency; the '218 asset simply rode along with the renamed parent under a new lien.

7. Privateering — not present. No operating-to-NPE transfer; no SEC disclosure or Patent Progress/EFF coverage linking '218 to an assertion entity.

8. Defensive aggregator — not present. Chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN.

Relevant adjacent (non-'218) note: NCR has been sued (KT Group jury verdict, S.D.N.Y., Jan 2019; Lemelson Foundation litigation over bar-code patents) — i.e. NCR has been a defendant, never an asserter of '218. (kioskindustry.org)

Verdict

Insufficient data — but with a clear non-NPE read from the available record.

Justification: The chain contains no assertion event and no NPE signal. Substantive ownership never left the original assignee — the post-1999 entries are two JPMorgan Chase security agreements (2014-01-15, 2016-04-18), their 2023-10-25 release, a same-day Bank of America replacement lien (2023-10-25), and a pure Change of Name (2023-12-07) to NCR Voyix. Effectively, "only the original assignment" changed beneficial ownership, which is the literal trigger for the Insufficient-data verdict. I am not returning "Operating-company assertion" because NCR Voyix is not suing competitors on '218, and not any NPE category because zero of the eight signals are present on the evidence. The one hard limitation is procedural: I could not retrieve reel/frame numbers or correspondence-of-record for '218 in this session, so the entries above should be re-verified at the Assignment Center before being relied on in a filing.

Verify at: USPTO Assignment Center — search patent 6571218: https://assignmentcenter.uspto.gov/ (mirror: https://assignment.uspto.gov/patent/index.html)

I'll search for the patent and each cited reference.

Let me check the non-patent citations and the second independent claim's prior art relationship.

Scope and method

I searched for the literal number 6571218 and verified the record against a USPTO-mirror page (uspto.report), the Google Patents page, and the granted-PDF front page. No near-number substitutions were used. The results confirm the identity already established in the prior sections (US 6,571,218 B1, App. 09/291,708, filed 1999‑04‑14, granted 2003‑05‑27, Robert F. Sadler, NCR). Sources: https://uspto.report/patent/grant/[6571218](/patent/6571218) ; https://patents.google.com/patent/[US6571218B1](/patent/US6571218B1)/en ; https://patentimages.storage.googleapis.com/31/b1/0b/88edbf900798eb/US6571218.pdf

The patent's face lists four patent citations and two non‑patent citations. I treat those as the prior art of record and analyze each below. I am building on — not repeating — the bibliographic and claim‑theming content already generated.

⚠️ Two record-keeping points I want to be explicit about:

1. I do not have the file wrapper for '218 (the examiner's PTO‑892s, Office Actions, or the specific rejections/combinations). The four references below come from the face of the granted patent, which tells me they were cited/considered, not how the examiner used them. My § 102 mapping is my own independent analysis, not a reproduction of the examiner's rejection.
2. Three of the four cited U.S. references issued after the '218 filing date (1999‑04‑14): US 5,937,386 (1999‑08‑10), US 6,032,128 (2000‑02‑29), US 6,167,381 (2000‑12‑26). Their prior-art effect therefore rests on their earlier filing/priority dates under pre‑AIA 35 U.S.C. § 102(e), not on their issue dates. Only the Japanese reference predates '218 as a printed publication.

1. The four patent citations at a glance

Sources: https://patents.google.com/patent/JPS55119772A/en ; https://patents.google.com/patent/[US5937386A](/patent/US5937386A)/en ; https://patents.google.com/patent/US6032128 ; https://ie.espacenet.com/publicationDetails/biblio?...NR=[6167381A](/patent/6167381A) ; https://patentimages.storage.googleapis.com/93/72/e0/e82dd2d888c6eb/US6032128.pdf ; https://patentimages.storage.googleapis.com/24/3d/cc/050cf36ef9eb71/US6167381.pdf

2. Reference‑by‑reference analysis

A. JPS 55‑119772 A — Tokyo Electric Co., "Processing system for commodity sales data"

Full citation: Japanese unexamined patent application JPS 55‑119772 A (JP App. No. 2737679), filed 1979‑03‑09, published 1980‑09‑13, applicant Tokyo Electric Co., Ltd.

Description: A two‑station checkout architecture. A checker machine 11 (data‑input unit) and a separate cashier machine 12 (money‑processing unit) are linked. The checker has basket counters/keyboard; the cashier has a customer memory 39 storing the checker's sales data together with basket‑number data, plus a buffer memory and accumulation memory. A central control unit detects the end of the data‑input operation and, on a key depression, displays and prints the basket number with the corresponding data. The stated purpose is to preserve the correspondence between commodity, receipt and customer "even if customer is changed between the data input section and money processing section."

§ 102 mapping to '218:

• This is the only cited reference that speaks to splitting a checkout between a data‑entry stage and a separate payment station, with an identifier that keeps a customer's partial transaction correlated as the customer moves between stations. That concept is conceptually adjacent to '218's "extended transaction" (spec: suspend at the self‑checkout lane → print a bar‑coded receipt → resume at a personnel‑operated terminal) and to claims 11–14 and 17–18.
• However, it discloses no self‑checkout terminal, no network of self‑checkout terminals, no remote authorization station, no priority‑ordered issues log, and no bar‑coded receipt/suspend‑and‑resume mechanism.

Verdict: Does not anticipate any of claims 1–18. It is at most background/support showing that correlating an in‑progress customer transaction across two checkout stations was old; it supplies none of the independent‑claim elements (issues log; remote authorization station resolving in priority order).

B. US 5,937,386 A — Frantz, quick‑service restaurant order fulfillment

Full citation: U.S. Patent 5,937,386 A, Howard J. Frantz, filed 1996‑12‑09, issued 1999‑08‑10.

Description: A drive‑thru/QSR order‑accuracy system. A POS register enters the order; a computer (12) computes a target weight and acceptance range for the bagged order; the bag is weighed and the actual weight compared against "acceptable / borderline / unacceptable" ranges. The result is signalled on a monitor by text or a colored light — green (acceptable), yellow (borderline, check it), red (recheck, do not hand out) — and logged in a "Compile Order Accuracy Status Program," which compiles statistics.

§ 102 mapping to '218:

• The green/yellow/red status‑indication scheme and an accompanying status log are the only substantive overlaps. '218's spec uses an essentially identical logic (green = normal, yellow = "intervention may soon be necessary," red = "intervention is currently necessary"). This is the type of reference an examiner would pair against the graphical‑indication limitations of claim 5 (and arguably the "issues log" of claim 1/15(c)).
• But '218's claim 5 requires a numerical indication of the priority of the issue; Frantz's lights carry no per‑lane priority number. And Frantz is not a self‑checkout environment at all — no customer‑operated terminal, no remote authorization station, no priority ordering among lanes.

Verdict: Does not anticipate any of claims 1–18. It is best characterized as a § 103‑type secondary reference for the tri‑color graphical status indication of claim 5 (and, loosely, the logging concept of claim 15(c)) if combined with a networked self‑checkout system.

C. US 6,032,128 A — Lutz & Morrison (NCR), self‑service checkout security monitoring

Full citation: U.S. Patent 6,032,128 A, Dusty L. Lutz and James Morrison, filed 1997‑12‑15, issued 2000‑02‑29, assigned to NCR Corporation. (Note a naming nuance: the '218 face page lists this reference as "Morrison et al.," while its true inventive entity is Lutz & Morrison. Not a contradiction — just the face‑page attribution.)

Description: Weight‑scale‑based security for a self‑service checkout terminal (customer operates the terminal without a clerk). Scales under the bagging/post‑scan areas detect voids and item placement/removal; the processing unit generates a "wrong‑item‑removed control signal." Notably:

• Claim 17: "means for updating an electronic log value in response to generation of said wrong‑item‑removed control signal; and means for comparing said electronic log value to a log threshold and generating a personnel signal."
• Claim 19: "means for generating a personnel control signal … and means for suspending operation of said terminal in response to generation of said personnel control signal."
• Claim 12: generating a "personnel control signal" upon a wrong‑item‑removed detection.

§ 102 mapping to '218:

• This is the closest of the four references. It discloses a self‑service/self‑checkout terminal that monitors its own customer activity, detects a condition requiring store‑personnel attention, writes it to an electronic log, and can suspend the terminal's operation. That bears directly on: claim 1 (first clause: self‑checkout terminal monitoring and placing issues in a log), claim 9 (suspending a transaction when an issue arises), and claim 15 steps (a)–(c).
• It does not disclose a remote authorization station, let alone one that "accesses the issues log to review and resolve the issues … in priority order." Its electronic log is local and threshold‑based; its suspension is local. This is precisely the element '218's specification identifies as the inventive departure from prior remote systems ("each situation is handled at the time the issue is created").

Verdict: Does not anticipate any entire claim — every one of '218's claims (including the dependents) incorporates the remote‑authorization‑station/priority‑resolution element, which US 6,032,128 lacks. It is the best anticipation‑style reference against the individual limitations of claims 1, 9, 15(b) and 15(c), and the natural primary reference in a § 103 combination against claim 1.

D. US 6,167,381 A — Swaine, Vassigh & Paton (NCR), self‑service checkout terminal

Full citation: U.S. Patent 6,167,381 A, Stephen W. Swaine, Ali M. Vassigh, and Grant C. Paton, filed 1998‑02‑06, claiming benefit of U.S. Provisionals 60/037,725 and 60/037,726 (both filed 1997‑02‑07); issued 2000‑12‑26; assigned to NCR Corporation.

Description: A self‑service checkout terminal hardware/architecture disclosure: a base with a bagwell, a first counter carrying a scanner at one end and an automated teller machine (ATM) at the other, and an arcuate second counter. It cross‑references a copending application, "Method for Enhancing Security and Providing Assistance in the Operation of a Self‑Service Checkout Terminal."

§ 102 mapping to '218:

• Overlaps with the hardware context of '218 Figure 1: '218's self‑checkout terminal includes a touchscreen display 16, a scanner 18, an ATM/cash acceptor 20, and a printer 22. US 6,167,381 shows a self‑service checkout terminal combining a scanner and an ATM, and stresses customer self‑operation without a clerk.
• It supplies nothing on the issues log, remote authorization station, priority resolution, parallel non‑blocking approval, IPC data exchange, or bar‑coded‑receipt suspend/resume. It also does not disclose a network of self‑checkout terminals feeding a central authorizer.

Verdict: Does not anticipate any of claims 1–18. Cited as an example of the state of self‑service checkout terminal design (and, via its cross‑referenced sibling application, of NCR's own work on self‑checkout supervision/assistance).

3. The two non‑patent citations

Assessment (with a timing caveat):

• "pscnet.com" is the domain associated with PSC Inc.'s U‑Scan self‑checkout product line, so these two entries are most plausibly product/brochure web pages describing a commercially available self‑checkout system, cited to show that self‑checkout systems (and their supervisor‑assistance features) were known.
• Timing matters under § 102. '218 was filed 1999‑04‑14. The dated page is from 1998 — less than one year before filing, so it is not § 102(b) (¶"printed publication … more than one year prior"). It would only work under § 102(a) (known/used by others before the invention) or as § 103 evidence of the general state of the art — a materially weaker posture than the Japanese publication.
• The "provided in SN 09/340,523" notation points to a different NCR application's file, indicating the examiner obtained the document from a related case rather than the '218 paper file. I have not independently verified the contents of these pages (my searches for the pscnet.com pages returned nothing retrievable), so I cannot testify to their specific disclosures. I flag this as an evidence gap rather than assert content.

Verdict: On the record I have, these NPL items do not anticipate any claim of '218; they are background/state‑of‑the‑art citations.

4. Aggregate § 102 conclusion

No single one of the six cited references anticipates any of claims 1–18 of US 6,571,218 in its entirety. The reason is structural and holds across all four patent references: every claim of '218 (including each dependent, because each depends on claim 1 or claim 15) requires a remote authorization station that accesses the issues log and resolves issues in priority order, and none of the cited references discloses that element. What the references do supply, limitation by limitation:

• US 6,032,128 — self‑checkout terminal that monitors activity, detects a personnel‑requiring condition, writes an electronic log value, and can suspend the terminal → claim 1 (first clause), claim 9, claim 15(b)/(c). Strongest reference.
• US 5,937,386 — green/yellow/red transaction‑status indication plus a status log → claim 5 (graphical indication) and loosely the logging concept of claim 15(c). Secondary/obviousness reference.
• US 6,167,381 — self‑service checkout terminal hardware (scanner + ATM) → context for claim 1's "self‑checkout terminals" and the scanner/printer setting of claims 12–14.
• JPS 55‑119772 — split data‑input/money‑processing checkout with customer/basket correlation → loose background for the "extended transaction"/handoff concepts of claims 11–14, 17–18.
• The two pscnet.com pages — background on commercial self‑checkout; weak § 102(a)/§ 103 posture given the pre‑filing timing.

Most likely examiner usage: because no single reference anticipates claim 1 or claim 15, the references were almost certainly deployed as (i) § 102 citations against individual limitations and/or (ii) a § 103 combination (most plausibly US 6,032,128 as primary, with a remote/networked‑authorization teaching — possibly the NPL or US 6,167,381 — supplying the remote element).

5. Confidence and gaps

• High confidence in the identity and dates of all four patent citations and in the two NPL citations as listed on the patent's face — they come from the authoritative patent text plus corroborating Google Patents/Espacenet/FreePatentsOnline records.
• Moderate confidence in the substantive descriptions (drawn from the references' own abstracts/claims via Google Patents, Espacenet and FPO).
• Low confidence / evidence gap: I could not retrieve the actual Officer‑cited rejections for '218 (no PTO‑892 or Office Action was located), and I could not retrieve the pscnet.com pages themselves. Therefore the § 102 mapping above is my independent limitation‑by‑limitation assessment, and I cannot state how the examiner actually combined these references at any given point in prosecution. If you want the examiner's exact theory, the next step is to pull the '218 file wrapper (Public PAIR / Patent Center) for the PTO‑892s and Office Actions.
• One minor formatting wrinkle worth noting for completeness: the '218 face page credits the US 6,032,128 citation to "Morrison et al.," whereas the reference's actual inventive entity is Lutz and Morrison — an attribution nuance, not a substantive conflict with any prior section.

I'll ground this analysis in the actual prior-art references of record before building the obviousness case.

Obviousness Analysis — U.S. Patent No. 6,571,218 Under 35 U.S.C. § 103

Built on the prior "Patent summary" and "Litigation summary" sections above. Claim language and specification quotes are taken from the authoritative full text supplied; reference content is taken from the cited-art records as fetched (URLs inline). Identifiers are reproduced literally.

1. Governing framework and the POSITA

The application was filed 1999-04-14, so pre-AIA § 103 governs throughout, including pre-AIA § 103(c) as it read before the CREATE Act amendments of Nov. 29, 1999 (a point that matters — see § 9).

Person of ordinary skill (POSITA): a software/systems engineer with ~2–4 years of experience in retail point-of-sale (POS) and self-service checkout systems, familiar with: (a) weight-based security monitoring of self-checkout lanes, (b) store LAN topologies connecting POS terminals, (c) standard graphical/touchscreen operator interfaces, and (d) conventional queue and priority scheduling. This is a systems-integration field, not a field of unpredictable science — which materially lowers the § 103 bar under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007).

2. Prior-art qualification of the references of record

⚠️ Verification caveat: I retrieved the full text of US 6,032,128's claims and US 6,167,381's abstract/background, and descriptive text for US 5,937,386 and JPS 55119772 A. For US 6,167,381 I have not reviewed its complete specification and all 18 claims; for JPS 55119772 A I have only the JPO English abstract (the original is Japanese). A litigation- or IPR-grade mapping requires the complete documents. Statements below about unviewed portions are flagged as inference.

3. The structural problem for the patentee: applicant-admitted prior art (AAP)

The '218 specification itself makes two concessions that do most of the § 103 work:

1. "Certain current self-checkout systems require the retail customer to summon a store employee to the self-checkout terminal when an approval situation arises."
2. *"One current self-checkout system allows a store employee to perform the approval function remotely, but in that system, each situation is handled at the time the issue is created."*

Concession (2) is an admission that a remote authorization station resolving self-checkout approval issues over a network is prior art. The only differences the '218 asserts are (i) timing — queue/"just in time" processing rather than issue-by-issue at creation — and (ii) software separation of self-checkout approvals from the store's general business algorithms. Neither is a claimed structural limitation; (ii) is an architectural preference with no claim counterpart at all. Applicant-admitted prior art is routinely usable in § 103 analysis and in IPR.

4. Combination I — the primary obviousness case

4.1 Claim 1

The one genuine gap a patentee would press: US 6,032,128's "electronic log value" is a numeric counter compared to a threshold, not a queue of discrete, individually-prioritized issues. That mapping gap is real. It is bridged by (a) the AAP remote-approval system, which necessarily had to serialize multiple pending approvals somehow, (b) US 6,167,381's log/paging paradigm, and (c) the ordinary skill of queue-and-priority scheduling. But it is the softest joint in the case, and a petitioner should expect to litigate it.

4.2 Claim 15

Steps (a)–(c) track US 6,032,128/6,167,381 monitoring plus logging. Step (e) (remote resolution after the transaction is "done" — keyed in the spec to "a tender or a critical device error") tracks US 6,032,128 claim 19's suspension-on-personnel-signal and US 6,167,381's post-itemization tender/finalization steps. Step (d)'s "transaction is done and issues remain" is a straightforward gating condition — a design choice within the ordinary skill of a POSITA seeking to avoid interrupting a customer mid-scan, and it was already the operative logic of the AAP system (which handled issues "at the time the issue is created," i.e., adversarially, not gated at completion).

4.3 Motivation to combine (KSR factors)

1. Same field, same problem, same solution type. All four principal references address supervision/security of unattended or lightly-attended retail checkout. KSR factor: combination of references in the same field of endeavor.
2. The references themselves supply the motivation. US 6,167,381 expressly recites the need for a terminal that "assists or otherwise supervises a customer"; US 6,032,128 expressly motivates remote personnel notification for security; the pscnet.com/U-Scan NPL and the 1998 Albertsons reporting show a single attendant supervising multiple lanes. The '218's own stated objectives — "remote approval of multiple lanes in disparate locations by a single store employee" and freeing a lane for the next customer — are the very economic pressures the prior art was already responding to (labor cost reduction, throughput). That is KSR's "design incentive ... market demand."
3. Predictable combination of known techniques. Networked terminals + a central supervisor terminal + a log/queue + priority scheduling are each individually known and combine with predictable results. Per KSR, "if a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious."
4. Common inventorship/assignee. US 6,032,128 and US 6,167,381 are both NCR Corporation refs; the '218 is NCR. Common assignee is probative of what the POSITA (the same engineering organization) would have known and been motivated to combine. But see § 9 for the pre-AIA § 103(c) wrinkle.
5. Weak nexus for any objective indicia. Commercial success of self-checkout generally (U-Scan, NCR FastLane) is driven by the self-checkout concept, not by the claimed remote-approval/priority-log feature; the nexus needed under WBIP is absent on this record.

5. Dependent claims 2–14: mapping to additional art

Non-cash tender rationale. The 1998 reporting on U-Scan states an attendant is assigned "to help enter produce codes, accept coupons, check ID for alcohol purchases or ring up noncash payments." That is contemporaneous, non-record evidence that the "extended transaction" concept (unattended lane hands off unsupported tender to a staffed station) was known and commercially practiced before the '218 filing date.

6. Alternative combinations (for fallback and for art not of record)

Combination II — Frantz-led. US 5,937,386 (three-tier automated acceptability determination + remote monitor alerting) as the primary, in view of US 6,167,381 (self-service checkout terminal hardware and personnel-summons-on-log-threshold). Motivation: Frantz's explicit "borderline / must be checked before release" tiering is a teaching to escalate progressively to a human decision-maker — i.e., a priority scheme. Weakness: Frantz is a quick-service-restaurant bag-weight system, so a patentee will argue different field of endeavor; that argument is weak post-KSR given the shared problem (order-accuracy/security at an unattended handoff).

Combination III — JP-led. JPS 55119772 A as the base for the split-station suspend/resume architecture, in view of US 6,032,128/US 6,167,381 for the self-checkout and monitoring/logging elements. This is the cleanest route to claims 9–14 and 17–18, because the Japanese reference is squarely about completing a transaction at a second station when the customer has moved, using a machine-readable correlation token. Claims 12–14 (bar code) are then a straight substitution argument.

Combination IV — concurrent NCR application. US 6,167,381 cross-references Ser. No. 09/020,057, "Method for Enhancing Security and Providing Assistance in the Operation of a Self-Service Checkout Terminal" (Vassigh/Walter), filed 1998-02-06. That application is not among the four references of record on the '218 face, and its content (which I have not retrieved) plausibly addresses personnel assistance/summons logic directly. A petitioner should pull Ser. No. 09/020,057 in full — it is the single most promising unconsidered-art lead produced by this record.

7. Where the claims plausibly survive § 103

I should be candid rather than one-sided:

• The "issues log as a queue of discrete issues" vs. a numeric log counter. US 6,032,128's log is a counter compared to a threshold. If the patentee successfully construes "issues log" to require discrete per-issue entries, the primary mapping needs the AAP or US 6,167,381's log to carry that weight, and US 6,167,381's full disclosure is unverified here.
• "in priority order" as a claim limitation, not a preference. The '218 recites priority in claim 1 and again in claim 16. If the prior art's ordering is severity-based (Frantz) or threshold-based (6,032,128) rather than a FIFO numbered queue, there is room to argue the specific ordering scheme is not taught — though the motivation to use FIFO is trivially supplied by fairness/throughput.
• "cannot be resolved at that terminal" (claim 9) as a predicate for suspension. JPS 55119772 A discloses a station designed for split processing rather than one that conditionally suspends on an unresolvable issue. The conditional-suspension logic is closer to US 6,032,128 claim 19, which is triggered by a security/personnel signal rather than by tender-type unsupported-ness. A petitioner will need to argue that conditioning suspension on the type of issue is an obvious design choice; that is a reasonable but not automatic argument.
• Claim 6's touchscreen + claim 5's numerical priority indicator are conventional operator-interface choices; expect a strong obviousness case but note that KSR does not excuse a petitioner from identifying where each element appears.

8. § 112 / § 101 side notes (relevant to, but outside, § 103)

The asserted scope of claim 1 is functional and largely result-oriented ("accessing the issues log to review and resolve the issues ... in priority order") with no structural limitation tying the remote station to the terminal. That breadth cuts against the patentee on § 103 (little structure to distinguish) while creating Alice/§ 112(f) exposure — the EPO/Google class notes at https://patents.google.com/patent/[US6571218B1](/patent/US6571218B1)/en place the claims in G06Q 20/20 (a § 101-art unit). A § 103 invalidity finding would moot it, but a petitioner should plead both.

9. Procedural flags a careful analyst must raise

1. The examiner already considered all four patent references and both NPLs (they are marked as cited by the examiner on the face of the '218). Any § 103 attack built solely on these references must explain why it succeeds where examination did not — typically by supplying a new motivation-to-combine rationale (KSR-style articulated reasoning), by new claim construction, or by adding art not of record (Ser. No. 09/020,057; the U-Scan PSC/Optimal product literature; the 1998 Albertsons/Spokesman reporting).
2. Pre-AIA § 103(c) timing nuance. US 6,032,128 and US 6,167,381 both qualified only as § 102(e) art and were commonly owned by NCR with the '218. The CREATE Act (Nov. 29, 1999) amended § 103(c) to disqualify commonly-owned § 102(e) art from § 103 combinations prospectively — i.e., for applications filed on or after that date. The '218 was filed 1999-04-14, before CREATE. On the face of the statute as it then read (§ 103(c) covering only § 102(f)/(g) subject matter), the § 102(e) NCR references were not excluded from § 103. I flag this because it is outcome-determinative and fact-dependent (it turns on invention date and ownership at that date), and because I am a technical analyst, not counsel — this needs patent-attorney confirmation.
3. Full-text verification required for US 6,167,381 (all claims/spec), JPS 55119772 A (Japanese original), the pscnet.com pages (archived), and US 5,937,386. My mappings above for unviewed passages are inferences, labeled as such.

10. Bottom line

On this record, a strong prima facie § 103 case exists against claims 1, 2, 7, 8, 9, 10, 11, 15, 16, and 17, built primarily on the combination of US 6,032,128 + US 6,167,381 + the U-Scan/pscnet NPL, with the applicant's own admission of a prior remote self-checkout approval system supplying the core of claim 1 and the priority-order/queue features coming from US 5,937,386 and routine scheduling practice. The suspend-print-barcode-resume family (claims 11–14, 18) is most cleanly attacked with JPS 55119772 A as the structural primary reference. The operator-interface claims (3–6) are met by conventional touchscreen dashboard design plus US 5,937,386's graded status indication.

The two limitations that will decide the case are (a) whether "issues log" requires a queue of discrete prioritized issues (versus a threshold counter), and (b) whether conditional suspension on unsupported-tender type is taught or obvious. Those are the points on which a patentee would focus, and the points on which a petitioner should obtain the full text of US 6,167,381 and Ser. No. 09/020,057 before finalizing an invalidity contention.

Confidence: high on the claim text, the reference qualifications/dates, and the substantive content of US 6,032,128 and JPS 55119772 A; moderate on US 6,167,381 and the pscnet.com NPL (partial text only); low/unverified on pre-CREATE § 103(c) application to this specific fact pattern — flagged rather than asserted.