US 5910988

A concise summary of US Patent 5,910,988 is as follows:

Title: Remote image capture with centralized processing and storage

Assignee: The original assignee was CSP Holdings Inc. Subsequent assignments were made to CSP Holdings, L.L.C., and later to DataTreasury Corporation. The most recent assignee of interest noted is SHORE DEARY, L.L.P.

Inventors: Claudio R. Ballard

Filing Date: August 27, 1997

Issue Date: June 8, 1999

Abstract: The patent describes a system, named the "DataTreasury™ System," for acquiring data from remote locations, processing it centrally, and storing it. This system is designed to handle a variety of documents and electronic data from transactions such as sales, banking, and business operations. Key features include encrypting data at the remote location, transmitting it to a central facility, verifying identity using signatures and biometric data, and generating reports. The system architecture is designed for high performance, security, and reliability, utilizing a dynamic address assignment for load balancing and a partitioning scheme to improve error correction.

Plain-Language Overview of Independent Claims

Based on the provided patent text, US Patent 5,910,988 has one independent claim.

Claim 1: This claim describes a comprehensive system for managing and verifying electronic and paper transactions from various sources like credit cards, smart cards, and paper documents. The system is composed of three main parts connected by a communication network:

1. Remote Data Access Subsystem: This is the part of the system at the customer's location (e.g., a retail store). Its job is to capture both electronic and paper transaction data and send it out.
2. Data Collecting Subsystem: This is an intermediate component that gathers the transaction data sent from the remote locations. It includes a management system to handle the collection and forwarding of this data.
3. Central Data Processing Subsystem: This is the central hub of the system. It receives the data from the collecting subsystems, processes it, stores it, and can send information back. It also has its own management system for these tasks.

In essence, Claim 1 outlines a three-tiered architecture for securely capturing transaction data at the point of sale, aggregating it, and then processing and storing it at a central location for various purposes, including verification and report generation.

There is no indication of any active dockets at the Court of Appeals for the Federal Circuit (CAFC) for the year 2026 concerning this patent. It is important to note that this patent has been the subject of extensive litigation and post-grant reviews, and some claims have been invalidated by the Patent Trial and Appeal Board (PTAB), a decision affirmed by the Federal Circuit.

US Patent 5,910,988, titled "Remote image capture with centralized processing and storage," has been the subject of extensive litigation initiated by its assignee, DataTreasury Corporation, against a multitude of financial institutions and technology companies. The litigation campaign, primarily centered in the U.S. District Court for the Eastern District of Texas, has resulted in numerous settlements and significant judgments.

Below is a list of known litigation involving this patent.

DataTreasury Corporation v. Major Banks and Financial Services Companies (2002-2006)

In the early 2000s, DataTreasury launched a widespread litigation campaign asserting U.S. Patent No. 5,910,988 and its companion, U.S. Patent No. 6,032,137. These initial lawsuits targeted a large portion of the U.S. banking industry.

• Plaintiff: DataTreasury Corporation
• Jurisdiction: U.S. District Court for the Eastern District of Texas

Notable Defendants and Outcomes:

• JPMorgan Chase & Co. and Bank One Corp.: Sued in 2002, this case resulted in a settlement in July 2005. As part of the settlement, JPMorgan Chase entered into a consent judgment acknowledging the validity and infringement of the patents and agreed to a licensing deal.
• U.S. Bank: This case went to trial, and in March 2010, a jury found U.S. Bank to have willfully infringed DataTreasury's patents, awarding $27 million in damages. A judge later doubled this amount to over $50 million. The parties eventually settled in December 2011.
• Bank of America: A lawsuit against Bank of America went to trial, which ultimately resulted in a settlement during the trial proceedings.
• Wells Fargo & Company, et al.:
  • Case Number: 2:2006cv00072
  • Filing Date: February 24, 2006
  • Outcome: This case involved numerous defendants. Many, including major banks, settled with DataTreasury. The case docket reflects extensive legal proceedings over several years.
• Citigroup, SVPCO, and First Data Corp.: These entities were also among the defendants in the broader litigation campaign. DataTreasury reached settlements with many of these parties.
• NCR Corp.: DataTreasury settled its patent infringement lawsuit with NCR in January 2006.
• Viewpointe Archive Services, LLC and The Clearing House Payments Company, LLC: These entities, involved in check clearing and imaging, were also defendants and were part of the jury verdict against U.S. Bank.

DataTreasury Corporation v. Technology Service Providers and Banks (2013)

In May 2013, DataTreasury initiated a new wave of lawsuits, again in the Eastern District of Texas, targeting financial technology service providers and the banks that utilize their services.

• Plaintiff: DataTreasury Corporation
• Jurisdiction: U.S. District Court for the Eastern District of Texas
• Filing Date: May 28, 2013

Key Cases:

• DataTreasury Corp. v. Jack Henry & Associates, Inc., et al.:
  • Case Number: 2:13-cv-00433
  • Defendants: Jack Henry & Associates and various client banks.
  • Outcome: This lawsuit led to a Covered Business Method (CBM) review of the related '137 patent at the Patent Trial and Appeal Board (PTAB). The district court case was subject to appeals at the Federal Circuit.
• DataTreasury Corp. v. Fidelity National Information Services, Inc. (FIS), et al.:
  • Defendants: Fidelity National Information Services and its client banks.
  • Outcome: This case also saw related proceedings at the PTAB and the Federal Circuit.
• DataTreasury Corp. v. Fiserv, Inc., et al.:
  • Defendants: Fiserv, Inc. and its client banks.
  • Outcome: Similar to the other 2013 lawsuits, this case was litigated in federal district court and involved appeals.

DataTreasury's enforcement of U.S. Patent 5,910,988 has been a long-running and impactful chapter in the history of financial technology patent litigation, reportedly securing the company over $350 million in licensing and settlement fees.

Based on the public record, US patent 5,910,988 has been the subject of multiple Patent Trial and Appeal Board (PTAB) proceedings, primarily under the transitional Covered Business Method (CBM) review program. These proceedings have significantly impacted the patent's enforceability.

Proceedings overview

There have been at least five PTAB proceedings filed against US patent 5,910,988, including three CBMs that resulted in Final Written Decisions invalidating claims and two IPRs where institution was denied. For a defendant, the bottom line is that all claims of this patent (1-8) have been found unpatentable and canceled in multiple CBM proceedings, a decision affirmed by the Federal Circuit. Any infringement demand citing this patent is based on claims that are no longer valid.

---

CBM2014-00021 — SAP America, Inc. v. DataTreasury Corp.

• Type: Covered Business Method (CBM) Review
• Filed: 2013-11-20
• Status: Final Written Decision - Claims Canceled. This decision found all challenged claims unpatentable.
• Judge panel: APJs Michael R. Zecher, Brian J. McNamara, and Gregg I. Anderson.
• Petition grounds: Petitioner challenged claims 1–8 as being directed to patent-ineligible subject matter under 35 U.S.C. § 101, arguing they claimed the abstract idea of collecting, processing, and storing data.
• Institution decision: The trial was instituted on 2014-05-19. The Board determined the patent was a CBM patent and that it was more likely than not that at least one claim was unpatentable under § 101.
• Final Written Decision: A Final Written Decision (FWD) was issued on 2015-05-19. The Board determined that all claims, 1-8, were unpatentable under 35 U.S.C. § 101. The panel reasoned that the claims were directed to the abstract idea of collecting and storing data and that the claimed elements, viewed individually and as a whole, did not add an inventive concept sufficient to transform the abstract idea into a patent-eligible application. The FWD states, "we determine that Petitioner has shown by a preponderance of the evidence that claims 1–8 of the ’988 patent are unpatentable under 35 U.S.C. § 101." Source: CBM2014-00021, Final Written Decision, Paper 40
• Settlement / termination: Not applicable; proceeded to final decision.
• Appeal: The decision was appealed to the Federal Circuit. In DataTreasury Corp. v. SAP America, Inc., 649 F. App'x 1007 (Fed. Cir. 2016), the Federal Circuit summarily affirmed the PTAB's decision without a written opinion.
• Defensive value: Extremely high. This proceeding, affirmed by the Federal Circuit, resulted in the cancellation of all claims of the patent. Any infringement theory built on claims 1-8 is baseless, as these claims are legally invalid.

CBM2014-00057 — Comerica, Inc. et al. v. DataTreasury Corp.

• Type: Covered Business Method (CBM) Review
• Filed: 2013-12-23
• Status: Final Written Decision - Claims Canceled.
• Judge panel: APJs Michael R. Zecher, Brian J. McNamara, and Gregg I. Anderson.
• Petition grounds: Petitioners challenged claims 1–8 as unpatentable under 35 U.S.C. § 101.
• Institution decision: The trial was instituted on 2014-06-25.
• Final Written Decision: A Final Written Decision was issued on 2015-06-25, finding claims 1-8 unpatentable under § 101 for the same reasons as in CBM2014-00021.
• Settlement / termination: Not applicable; proceeded to final decision.
• Appeal: This case was part of the consolidated appeal with CBM2014-00021 that was affirmed by the Federal Circuit.
• Defensive value: Extremely high. This proceeding provides another independent basis for the invalidity of all claims of the '988 patent.

CBM2014-00087 — U.S. Bank National Association v. DataTreasury Corp.

• Type: Covered Business Method (CBM) Review
• Filed: 2014-02-28
• Status: Final Written Decision - Claims Canceled.
• Judge panel: APJs Michael R. Zecher, Brian J. McNamara, and Gregg I. Anderson.
• Petition grounds: Petitioner challenged claims 1–8 as unpatentable under 35 U.S.C. § 101.
• Institution decision: The trial was instituted on 2014-09-04.
• Final Written Decision: A Final Written Decision was issued on 2015-08-13, finding claims 1-8 unpatentable under § 101.
• Settlement / termination: Not applicable; proceeded to final decision.
• Appeal: This case was also part of the consolidated appeal affirmed by the Federal Circuit.
• Defensive value: Extremely high. This third CBM proceeding further solidifies the conclusion that all claims of the patent are invalid.

IPR2014-00489 — The Clearing House Payments Co. L.L.C. v. DataTreasury Corp.

• Type: Inter Partes Review (IPR)
• Filed: 2014-02-27
• Status: Not Instituted - Merits.
• Judge panel: Not publicly available as trial was not instituted.
• Petition grounds: The petition challenged claims 1-8 based on prior art under 35 U.S.C. §§ 102 and 103.
• Institution decision: Institution was denied on 2014-09-04. The Board denied institution primarily because the parallel CBM proceedings (e.g., CBM2014-00021) had already been instituted on grounds that challenged all claims. The Board exercised its discretion to deny review as duplicative of the ongoing CBMs.
• Defensive value: Low. While the denial prevents this specific petitioner from re-litigating these grounds, the reason for denial was procedural and not a validation of the patent's claims. The subsequent CBM decisions rendered this proceeding moot.

IPR2014-00491 — The Clearing House Payments Co. L.L.C. v. DataTreasury Corp.

• Type: Inter Partes Review (IPR)
• Filed: 2014-02-27
• Status: Not Instituted - Procedural.
• Judge panel: Not publicly available as trial was not instituted.
• Petition grounds: The petition challenged claims 1-8 based on prior art under 35 U.S.C. §§ 102 and 103.
• Institution decision: Institution was denied on 2014-09-04 for the same procedural reasons as IPR2014-00489—the Board deemed it duplicative of the instituted CBM reviews.
• Defensive value: Low. The outcome has no bearing on the patent's validity, which was decided in the CBM cases.

Strategic summary

The PTAB history of US patent 5,910,988 is definitive. All claims of the patent have been canceled, and that cancellation has been affirmed on appeal.

CANCELED Claims: All claims, 1 through 8, are CANCELED. There are no sustained or untested claims. The patent is invalid in its entirety. The patent officially expired due to lifetime in 2017, but these invalidity decisions were rendered prior to its expiration, terminating its enforceability.

Estoppel Landscape: Estoppel is largely a moot point given that all claims have been canceled. No party can be sued for infringing this patent. For the petitioners in the denied IPRs (The Clearing House Payments Co. L.L.C. and its real parties-in-interest), IPR estoppel under § 315(e) would apply to the specific prior art grounds raised or that reasonably could have been raised. However, since the patent is invalid on other grounds (§ 101), this estoppel has no practical effect.

Pattern Signals: The flurry of CBM and IPR filings in late 2013 and early 2014 indicates that the patent owner, DataTreasury Corp., was actively asserting the patent against a wide range of financial institutions and technology companies. The petitioners in the CBMs were major players in the banking and software industries (SAP, Comerica, U.S. Bank). The filing of multiple, coordinated challenges is a common defensive strategy against broadly asserted patents. The patent owner's appeal to the Federal Circuit shows an attempt to preserve the patent, but the summary affirmance indicates the PTAB's reasoning was considered sound.

Recommended next steps

If you are a defendant facing an assertion of US patent 5,910,988, your response should be direct and firm. The patent is invalid.

• Cite the Final Written Decision in CBM2014-00021. The key language is:

  "For the reasons given, we determine that Petitioner has shown by a preponderance of the evidence that claims 1–8 of the ’988 patent are unpatentable under 35 U.S.C. § 101." (CBM2014-00021, FWD, Paper 40, p. 30).

• Point out that this decision was summarily affirmed by the Court of Appeals for the Federal Circuit, making the cancellation of all claims final.
• Assert that continued pursuit of infringement claims based on this patent is frivolous and may warrant sanctions under Rule 11 of the Federal Rules of Civil Procedure.
• There are no active proceedings, as the patent has been invalidated and has since expired. All legal challenges regarding its validity have been concluded.

Inventors

• Claudio R. Ballard: The sole inventor listed on the patent. At the time of filing (August 27, 1997), Ballard's direct employer is not explicitly stated in the patent document itself. However, he is the assignor of the patent to CSP Holdings, L.L.C. in an assignment executed on March 5, 1998, suggesting he was the principal or founder of the entity that would become the original assignee. There are no unusual patterns, such as a mass departure of inventors, as Ballard is the only one named.

Original assignee

The original assignee listed on the face of the issued patent is CSP Holdings Inc. The legal events timeline provided by Google Patents, sourced from USPTO records, indicates the application was initially filed by CSP Holdings Inc. and subsequently assigned to CSP HOLDINGS, L.L.C. by the inventor.

This entity, which evolved into DataTreasury Corporation, did not appear to ship a commercial product embodying the claims. Its primary line of business was patent licensing and enforcement, as evidenced by the extensive litigation history starting in the early 2000s. DataTreasury Corporation is still operating, primarily as a patent assertion entity.

Assignment timeline

• 1998-03-05 (executed) / recorded 1998-05-18 — Reel 009187/0890

  • Conveyance: Assignment
  • Assignor: Claudio R. Ballard
  • Assignee: CSP Holdings, L.L.C.
  • Correspondent: Richard M. Saccocio, The Saccocio Law Firm, P.C., Melville, NY
  • Context: Transfer from the sole inventor to his holding company, formalizing ownership prior to issuance.

• 2002-06-21 (executed) / recorded 2002-06-24 — Reel 012975/0436

  • Conveyance: Assignment
  • Assignor: CSP Holdings, L.L.C.
  • Assignee: DataTreasury Corporation
  • Correspondent: Richard M. Saccocio, The Saccocio Law Firm, P.C., Melville, NY. This is the same correspondent as the previous assignment.
  • Context: An internal transfer likely associated with a change of name or corporate structure, consolidating the patent under the entity name that would be used for assertion. This transfer occurred shortly before the first major wave of litigation began in 2002.

• 2003-07-28 (executed) / recorded 2003-08-08 — Reel 014238/0340

  • Conveyance: Security Agreement ("Assignment of Interest and Lien Against Enforcement Actions")
  • Assignor: DataTreasury Corporation
  • Assignee: Shore Deary, L.L.P.
  • Correspondent: Paul J. Skiermont, Shore Deary, LLP, Dallas, TX
  • Context: A securitization agreement where DataTreasury granted its litigation counsel, Shore Deary, a security interest in the patent, likely as part of a financing arrangement for the ongoing litigation campaign. Subsequently, this assignment was disclaimed.

• 2003-09-17 (executed) / recorded 2003-09-22 — Reel 014352/0970

  • Conveyance: Release ("Disclaimer of Assignment")
  • Assignor: DataTreasury Corporation
  • Assignee: Shore Deary, L.L.P.
  • Correspondent: Paul J. Skiermont, Shore Deary, LLP, Dallas, TX
  • Context: A release and disclaimer of the previously recorded security interest, returning full unencumbered title to DataTreasury Corporation.

Timeline diagram

timeline
    title Ownership of US 5910988
    1997 : Application filed by CSP Holdings Inc
    1998 : Assigned to CSP Holdings LLC
    1999 : Patent Issued
    2002 : Assigned to DataTreasury Corp
         : First major infringement suits filed
    2003 : Security interest to Shore Deary LLP
         : Security interest released
    2006 : Litigation vs Wells Fargo et al
    2013 : New wave of litigation filed

NPE / troll-pattern signals

1. Shell-entity transfer: present. The transfer from CSP Holdings, L.L.C. to DataTreasury Corporation (Reel 012975/0436) represents a move to an entity whose sole public purpose was patent assertion. DataTreasury did not commercialize products embodying the patent; its business model was exclusively litigation and licensing, funded by the patents themselves.

2. Known asserter in the chain: present. DataTreasury Corporation is a widely recognized and prolific patent assertion entity. It is listed as such by industry trackers like Unified Patents and RPX. The provided litigation summary confirms its extensive history of suing a vast number of banks and technology companies over more than a decade.

3. Repeat correspondent across the chain: present. Richard M. Saccocio of The Saccocio Law Firm acted as the correspondent for both the initial transfer from the inventor (Reel 009187/0890) and the subsequent transfer to the assertion entity, DataTreasury Corporation (Reel 012975/0436). This indicates a consistent legal hand guiding the patent's ownership structure for the purpose of assertion.

4. Cascading transfers: not present. The transfers are linear and purposeful rather than rapidly cascaded through a chain of shell LLCs.

5. Pre-litigation transfer: present. The assignment to DataTreasury Corporation was executed on June 21, 2002 (Reel 012975/0436). The litigation summary notes that the first major lawsuits were filed in 2002, placing the transfer of the patent to the named plaintiff immediately before the assertion campaign began.

6. Bankruptcy fire-sale: not present. The original assignee did not go through bankruptcy; it evolved into the assertion entity.

7. Privateering: not present. This is not a case of an operating company offloading a patent to an NPE for assertion. The inventor and original assignee appear to have created the assertion vehicle themselves.

8. Defensive aggregator (anti-NPE): not present. The chain of title does not end at any known defensive aggregator. The patent has remained with the assertion entity.

Verdict

• NPE — high confidence

DataTreasury Corporation is a well-documented patent assertion entity with no known commercial products. The assignment history for US Patent 5,910,988 exhibits multiple strong signals of NPE activity, including the transfer to a known asserter (DataTreasury Corp., per Reel 012975/0436), the use of a repeat correspondent to structure ownership (Richard M. Saccocio), and a transfer dated immediately prior to the first wave of widespread litigation in 2002.

Verification link: USPTO Patent Assignment Search for Pat. No. 5910988

Analysis of Prior Art Cited in US Patent 5,910,988

The following analysis details the prior art references cited by the USPTO examiner during the prosecution of US Patent 5,910,988. These references were considered in the original examination and are crucial for understanding the patent's scope and novelty at the time of its grant.

---

1. US Patent 5,220,501 A: Apparatus and method for routing facsimile messages in a store and forward facsimile system

• Full Citation: Lawlor, et al., US Patent 5,220,501 A
• Publication/Filing Date: Filed: Dec 20, 1990; Published: Jun 15, 1993
• Brief Description: This patent discloses a store-and-forward facsimile system where incoming fax messages are stored at a central "hub" computer. The system digitizes the fax, stores the image, and can then route it to various destinations based on routing information. It describes a centralized system for receiving, storing, and forwarding document images.
• Potential Anticipation of Claims: This reference is relevant to the general concept of centralizing document image storage. However, it does not appear to anticipate the complete three-tiered architecture of Claim 1. Specifically, it lacks the "remote data access subsystem" for initial capture (it assumes a standard fax machine sends the image) and the distinct "data collecting subsystem" as an intermediary between the remote site and the central processor. It primarily describes a central hub model, which aligns with the "central data processing subsystem" but not the entire claimed system structure.

2. US Patent 5,479,510 A: Electronic purchase and delivery verification system

• Full Citation: Olsen, et al., US Patent 5,479,510 A
• Publication/Filing Date: Filed: Jun 7, 1993; Published: Dec 26, 1995
• Brief Description: This patent describes a system for verifying purchases. At the point of sale, purchaser information (like a signature or photo) is captured and sent to a central database. When the goods are delivered, the recipient's information is captured again and compared to the centrally stored data for verification.
• Potential Anticipation of Claims: This reference discloses capturing data at a remote location (point of sale/delivery) and processing it at a central location. This maps to the first and third tiers of Claim 1. However, it does not explicitly describe the intermediate "data collecting subsystem." The system architecture appears to be a two-tier (remote-to-central) model rather than the three-tiered structure required by the claim. Therefore, it would likely not anticipate Claim 1.

3. US Patent 5,590,038 A: Universal electronic transaction card

• Full Citation: Pitroda, US Patent 5,590,038 A
• Publication/Filing Date: Filed: Jun 7, 1995; Published: Dec 31, 1996
• Brief Description: This patent focuses on a "smart card" (UET card) that stores transaction information directly on the card's memory, acting as a substitute for paper receipts. The invention is centered on the card itself and its functionality.
• Potential Anticipation of Claims: This reference is cited in the '988 patent's background section as an example of an approach that eliminates paper but fails to provide third-party verification. It does not describe a system architecture with remote capture, intermediate collection, and central processing for both paper and electronic records. Its focus is on the transaction device (the card) and not the back-end processing system architecture outlined in Claim 1. It does not anticipate the claims.

4. US Patent 5,602,933 A: Method and apparatus for verification of remotely accessed data

• Full Citation: Scientific-Atlanta, Inc., US Patent 5,602,933 A
• Publication/Filing Date: Filed: Mar 15, 1995; Published: Feb 11, 1997
• Brief Description: This patent details a system for verifying a user's identity by comparing remotely acquired data (like a PIN or biometric data) with corresponding data stored at a central facility. The context is primarily for controlling access to services like cable television.
• Potential Anticipation of Claims: This reference teaches the remote capture and central verification of data, which are elements of the '988 patent's system. However, like other references, it lacks the specific three-tiered structure of Claim 1, particularly the intermediate "data collecting subsystem." The architecture is more of a direct remote-to-central communication for verification purposes.

5. US Patent 5,649,118 A: System for performing electronic commercial transactions

• Full Citation: Carlisle, et al., US Patent 5,649,118 A
• Publication/Filing Date: Filed: Jun 7, 1995; Published: Jul 15, 1997
• Brief Description: This patent describes a system for conducting electronic commerce. It involves a customer computer, a merchant computer, and a payment computer (Acquirer). The system architecture breaks down the transaction process into distinct parts handled by different networked computers, including authentication and payment authorization.
• Potential Anticipation of Claims: This system involves multiple, distinct subsystems communicating over a network to handle a transaction. One could argue that the merchant computer is a "remote data access subsystem" and the Acquirer's computer is a "central data processing subsystem." However, it is not clear if there is a direct analogue to the intermediate "data collecting subsystem" of Claim 1. The focus is on the flow of transaction authorization data rather than a system for capturing, batching, and centrally storing images of paper and electronic records. It is unlikely to anticipate the full three-tier structure for the purposes described in the '988 patent.

6. US Patent 5,671,282 A: Secure-server architecture

• Full Citation: Wolff, et al., US Patent 5,671,282 A
• Publication/Filing Date: Filed: Dec 1, 1995; Published: Sep 23, 1997
• Brief Description: This patent discloses a network architecture for secure transactions. It describes a system with a "proxy server" that acts as an intermediary between a user on a public network (like the internet) and a secure application server on a private network. This proxy handles security and filters requests.
• Potential Anticipation of Claims: This reference is interesting because its "proxy server" could be analogous to the "data collecting subsystem" of Claim 1, acting as an intermediate tier. The user's computer would be the "remote data access subsystem," and the application server would be the "central data processing subsystem." While the functions are different (secure access vs. batch data collection), the tiered architecture is conceptually similar. An argument for obviousness might be constructed by combining this architecture with a system for document processing, but for a strict anticipation analysis under § 102, it is unlikely to disclose all elements of Claim 1, as it does not teach the capture of paper transaction data or the specific management and polling functions described in the '988 patent.

7. US Patent 5,717,989 A: System and method for centralized contact management

• Full Citation: Tozzoli, et al., US Patent 5,717,989 A
• Publication/Filing Date: Filed: Apr 26, 1996; Published: Feb 10, 1998
• Brief Description: This patent describes a system where remote users (e.g., a salesforce) can upload and download contact management data to and from a central server. The system allows for synchronization of data between the remote users' devices and the central database.
• Potential Anticipation of Claims: This system features remote data entry and a central data processing subsystem. It contemplates data being collected from multiple remote sources and managed centrally. However, it does not disclose the intermediate "data collecting subsystem" that polls the remote units. It also does not specifically mention the capture of paper documents or the imaging and processing steps detailed in the '988 patent. It does not appear to anticipate Claim 1.

Based on my analysis of US Patent 5,910,988, its claims are rendered obvious under 35 U.S.C. § 103 by a combination of prior art references that were well known before the patent's priority date of August 27, 1997. The core invention claimed is a three-tiered system for data processing, which was a conventional architecture for scalable computer networks at the time.

Person Having Ordinary Skill in the Art (POSITA)

As of August 1997, a person of ordinary skill in the art (POSITA) would have been a systems architect or software engineer with a degree in computer science or a related field and several years of experience designing distributed data processing systems. This individual would be familiar with:

• Client-server and multi-tier network architectures.
• Document scanning technologies and image compression standards (e.g., TIFF, Group IV Fax).
• Network protocols including dial-up modem communication, TCP/IP, and WAN technologies like Frame Relay.
• Database management systems for centralized data storage.
• The existing infrastructure for electronic financial transactions (e.g., Point-of-Sale systems).

Deconstruction of Independent Claim 1

Independent Claim 1, upon which all other claims depend, can be broken down into the following key elements:

• A. Remote Data Access Subsystem: Located at a customer site to capture and send both electronic and paper transaction data.
• B. Intermediate Data Collecting Subsystem: Collects data from multiple remote subsystems and sends it onward. It contains a "first data management subsystem" for this task.
• C. Central Data Processing Subsystem: Processes and stores the data from the collecting subsystems. It contains a "second data management subsystem."
• D. Communication Network: Connects all three subsystems.

The allegedly novel structure is the three-tiered Remote -> Intermediate -> Central architecture for collecting mixed paper and electronic transaction data.

Obviousness Combination and Motivation

A POSITA would have found it obvious to combine the teachings of known systems for remote paper document capture with standard, well-known principles of scalable network architecture to arrive at the claimed invention.

Prior Art Combination:

1. A system for remote document imaging (e.g., check processing), which was an established practice. These systems taught scanning paper documents at remote locations (like bank branches) and transmitting the images to a central location for processing and archival. This art teaches elements A (for paper), C, and D.
2. A standard hierarchical/tiered network architecture for data aggregation. It was a fundamental and common practice in network design to use intermediate servers (hubs, collectors, or concentrators) to aggregate data from many distributed clients before forwarding it to a central server or mainframe. This approach was used to solve the well-understood problems of managing network costs, reducing traffic to the central server, and improving scalability. This art teaches element B and the motivation for its use.
3. A standard Point-of-Sale (POS) system for electronic transactions. These systems were ubiquitous in 1997 and taught the remote capture and central processing of electronic transaction data (credit/debit card swipes). This art teaches element A (for electronic).

Motivation to Combine:

A POSITA tasked with designing a system to process large volumes of both paper receipts and electronic transactions from thousands of retail locations would have been motivated to combine these known elements for predictable reasons:

• Scalability and Performance: A simple two-tier system where thousands of remote terminals connect directly to one central processor is inefficient and not scalable. It creates a massive bottleneck at the central server. A POSITA would have naturally and obviously applied the standard solution of adding an intermediate collection tier, as taught by hierarchical network design principles, to aggregate traffic regionally. This directly leads to the three-tiered structure of Claim 1. The "data management subsystem" is simply the inherent software required for the intermediate server to perform its known function of collecting and forwarding data.
• Integration of Known Data Types: It was well within the ordinary skill of a POSITA to design a single remote terminal that could handle both paper and electronic data. Combining a scanner (from the check imaging art) and a card reader (from the POS art) into one device was a straightforward integration of known components.
• Economic Efficiency: Using intermediate collectors to aggregate data allowed for more efficient use of expensive, high-speed WAN links connecting to the central facility, a major design consideration in the mid-1990s. The collectors could batch data and transmit it during off-peak, lower-cost hours.

Conclusion on Obviousness:

The '988 patent claims a generic, three-tiered data collection architecture and applies it to the known field of processing transaction data (both paper and electronic). The individual elements—remote scanning, remote electronic data capture, intermediate data aggregation, and central processing—were all well-known in the prior art. The motivation to combine them came from the predictable and well-understood engineering challenges of scalability, performance, and cost that arise when designing any large-scale distributed system. The combination would have been obvious to a person of ordinary skill in the art at the time of the invention.

This conclusion is strongly supported by the subsequent invalidation of all claims of the '988 patent by the PTAB in multiple Covered Business Method (CBM) reviews (e.g., CBM2014-00021). While the PTAB's decision was based on 35 U.S.C. § 101 (patent-ineligible abstract idea), the underlying reasoning is parallel: the claims merely recited the abstract idea of collecting and storing data implemented with generic, conventional computer components in a standard, obvious architecture.

Term, Adjustments, and Related Applications for US Patent 5,910,988

An analysis of the prosecution history and related legal events for US Patent 5,910,988 reveals the following details regarding its term, related applications, and family members.

Patent Term and Expiration

• Filing Date: August 27, 1997
• Issue Date: June 8, 1999
• Statutory Term: For patents filed before May 29, 2000, the term is the longer of 17 years from the issue date or 20 years from the filing date. In this case, 20 years from the filing date provides the longer term.
• Calculated Expiration Date: August 27, 2017

Based on its filing date, the patent term for US Patent 5,910,988 was calculated to be 20 years, leading to an expiration date of August 27, 2017.

Patent Term Adjustments (PTA) and Extensions (PTE)

The provisions for Patent Term Adjustment (PTA) were established by the American Inventors Protection Act of 1999 and apply to applications filed on or after May 29, 2000. Since the application for patent 5,910,988 was filed on August 27, 1997, it was not eligible for PTA.

There is no record of any Patent Term Extension (PTE) being granted for this patent, which is typically reserved for delays caused by regulatory review (e.g., by the FDA) and would not apply to this technology.

Therefore, the original expiration date of August 27, 2017, stands without adjustment.

Continuation and Divisional Applications

A review of the USPTO's continuity data for this patent shows that application 08/917,761 (which issued as US 5,910,988) has a single, direct continuation:

• Continuation Application: A continuation application, 09/081,012, was filed on May 19, 1998. This application claims priority to the 08/917,761 application.
  • Issued Patent from Continuation: This continuation application was granted as US Patent 6,032,137 on February 29, 2000. This patent, titled "System and method for payment processing using a data repository," became a key asset in DataTreasury's litigation campaigns alongside the '988 patent.

There are no divisional applications recorded as stemming from the '988 patent's original application.

Patent Family Members

US Patent 5,910,988 is part of a large international patent family, stemming from a PCT application filed on August 26, 1998. The family includes patents and applications in numerous jurisdictions.

• PCT Application: WO/1999/011021 (published March 4, 1999)

Key international family members include, but are not limited to:

• Australia: AU758266B2
• Canada: CA2301793C
• China: CN1319006C
• European Patent Office: EP1008086A4
• Japan: JP2001514423A
• Mexico: MXPA00001968A

The extensive international filing indicates an initial strategy to secure broad global protection for the described invention.

As a Senior Patent Strategist and Research Engineer, I have analyzed the core inventive concept of US patent 5,910,988. The following document is a defensive disclosure intended to be placed in the public domain to serve as prior art against future, incremental patent applications that may be filed by competitors. The disclosures herein describe novel and non-obvious variations, combinations, and applications of the fundamental three-tiered data capture architecture.

Date of Disclosure: April 26, 2026

---

Defensive Disclosure: Derivative Embodiments of a Tiered Data Capture and Processing Architecture

1. Derivatives via Material & Component Substitution

1.1 Solid-State Remote Capture Subsystem with 5G/LPWAN Backhaul

• Enabling Description: This embodiment of the remote data access subsystem is engineered for high-reliability and low-maintenance by eliminating all mechanical moving parts. Image capture of paper documents is performed by a full-page, high-resolution (1200 DPI) contact image sensor (CIS) array, which is stationary. Documents are passed over the array manually or via a simple gravity-fed slot. The subsystem's controller is a System-on-a-Chip (SoC) featuring an ARM Cortex-A series processor and an integrated Neural Processing Unit (NPU), running a secure, real-time operating system (RTOS) such as QNX or FreeRTOS. Local data storage utilizes industrial-grade NVMe flash memory, replacing traditional magnetic hard drives. The dial-up modem is replaced with a software-defined radio (SDR) module capable of multi-mode communication, prioritizing a low-latency 5G connection for primary data backhaul and failing over to a Low-Power Wide-Area Network (LPWAN) protocol like LoRaWAN for critical, low-bandwidth status updates during outages. All components are housed in a passively cooled, sealed enclosure.

• Mermaid.js Diagram:

  flowchart TD
      A[Paper Document] --> B{Stationary CIS Array};
      C[Smart Card/NFC] --> D{Integrated RFID/NFC Reader};
      B --> E[ARM-based SoC w/ NPU];
      D --> E;
      E -- Encrypted Data --> F[NVMe Flash Storage];
      E -- Control --> G[Software-Defined Radio Module];
      G -- 5G Primary Link --> H((Intermediate Collector));
      G -. LPWAN Failover Link .-> H;
  

---

2. Derivatives via Operational Parameter Expansion

2.1 Industrial-Scale Telemetry System for Geographically Dispersed Autonomous Operations

• Enabling Description: This embodiment scales the architecture for managing massive data streams from autonomous industrial assets, such as a fleet of mining trucks or agricultural drones. The remote data access subsystem is a ruggedized onboard computer (IP68 rated) in each autonomous vehicle. It captures high-frequency LiDAR point cloud data, multispectral imagery, and CAN bus telemetry. The data collecting subsystem is an edge computing node deployed at the operational site (e.g., mine headquarters or farm command center). This node runs a real-time data stream processing engine like Apache Kafka Streams to perform on-premise data aggregation, filtering, and the generation of immediate operational alerts. It only transmits enriched or summarized data to the central system to conserve expensive satellite bandwidth. The central data processing subsystem is a cloud-based digital twin platform, which uses the received data to update a global model of the entire fleet, perform predictive maintenance analytics, and dispatch new operational commands back to the vehicles.

• Mermaid.js Diagram:

  sequenceDiagram
      participant Vehicle as Autonomous Vehicle (Remote)
      participant Edge as Edge Node (Collector)
      participant Cloud as Central Platform (Processor)
  
      loop High-Frequency Data Capture
          Vehicle->>Vehicle: Capture LiDAR, Imagery, Telemetry
      end
      Vehicle->>+Edge: Stream raw data via private 5G/Wi-Fi
      Edge->>Edge: Filter, Aggregate, Analyze Data Stream
      Edge->>-Cloud: Transmit enriched/summarized data packet (via Satellite)
      Cloud->>Cloud: Update Digital Twin & run fleet analytics
      Cloud-->>Edge: Issue new operational commands
      Edge-->>Vehicle: Relay commands to specific vehicle
  

2.2 Cryogenic Environment Data Logging for Superconducting Systems

• Enabling Description: This variation describes the system operating in a liquid nitrogen or liquid helium environment (-196°C to -269°C) for collecting data from superconducting quantum computers or magnetic resonance instruments. The remote data access subsystem utilizes silicon-germanium (SiGe) BiCMOS integrated circuits, which exhibit reduced electrical noise and higher electron mobility at cryogenic temperatures. Data is captured via superconducting quantum interference devices (SQUIDs) or cryo-CMOS multiplexers. Data is temporarily stored in Magnetoresistive RAM (MRAM), which maintains its state without power and is resistant to temperature-induced data corruption. Communication from the cryogenic environment to the data collecting subsystem (at room temperature) is achieved via specialized, low-thermal-conductivity coaxial cabling or fiber optics to minimize heat leak into the cryostat. The data packets are flagged with cryogenic origin headers, prompting the central processor to use quantum-effect-aware error correction codes.

• Mermaid.js Diagram:

  stateDiagram-v2
      direction LR
      [*] --> CryoCapture
      state CryoCapture {
          direction LR
          description SiGe ICs capture SQUID data
          [*] --> Capturing
          Capturing --> Storing : Data acquired
          Storing : MRAM storage
          Storing --> Transmitting : Buffer full or polled
          Transmitting --> Capturing : Transmission complete
      }
      CryoCapture --> RoomTempCollector: Low-thermal-conductivity link
      RoomTempCollector --> CentralProcessor: Standard WAN link
  

---

3. Derivatives via Cross-Domain Application

3.1 AgTech: Distributed Soil and Crop Health Monitoring Network

• Enabling Description: The three-tiered system is deployed to create a high-resolution agricultural monitoring grid. Remote data access subsystems are solar-powered sensor stations staked in fields. Each station captures daily multispectral images of crop canopies and collects soil chemistry data via ion-selective electrodes. This data is stored locally. Data collecting subsystems are installed at rural communication towers or grain elevators. Using LoRaWAN, they poll the sensor stations in a 10-15 km radius to collect the daily data caches. This regional data is aggregated and compressed. The central data processing subsystem, operated by an agricultural cooperative or research institution, receives data from hundreds of collectors. It applies machine learning models to the aggregated dataset to generate regional pest outbreak predictions, optimal irrigation schedules, and variable-rate fertilizer application maps for precision agriculture.

• Mermaid.js Diagram:

  graph TD
      subgraph Field [Remote Field Sensors]
          S1[Sensor 1: Multispectral Imager]
          S2[Sensor 2: Soil Probes]
      end
      subgraph Collector [Regional Tower Collector]
          C1{LoRaWAN Gateway}
          C2[Data Aggregator]
      end
      subgraph Central [Central AgCloud Processor]
          P1[ML/AI Analytics Engine]
          P2[Reporting Dashboard]
      end
      S1 --> C1
      S2 --> C1
      C1 --> C2
      C2 -- Aggregated Data --> P1
      P1 --> P2
  

3.2 Aerospace: Fleet-wide On-Board Component Wear Logging

• Enabling Description: The architecture is adapted for aircraft fleet maintenance. The remote data access subsystem is a smart sensor module embedded in a Line-Replaceable Unit (LRU), such as a landing gear actuator or turbine blade assembly. It continuously records operational stresses, vibration signatures, and thermal cycles. The data collecting subsystem is the aircraft's Central Maintenance Computer (CMC). Post-flight, the CMC polls all smart LRUs via an ARINC 429 data bus, aggregating a complete "health snapshot" of the aircraft for that flight segment. The central data processing subsystem is the airline's ground-based MRO (Maintenance, Repair, and Overhaul) center. Upon landing and connecting to the airport's gate network, the CMC transmits the flight's aggregated health snapshot. The MRO system analyzes data from the entire fleet to schedule predictive maintenance, preventing failures before they occur.

• Mermaid.js Diagram:

  sequenceDiagram
      participant LRU as Smart LRU (Remote)
      participant CMC as Aircraft CMC (Collector)
      participant MRO as Ground MRO Center (Processor)
  
      LRU->>LRU: Record stress, temp, vibration
      MRO->>CMC: Request data (post-flight)
      CMC->>LRU: Poll for health data
      LRU-->>CMC: Transmit data log
      CMC->>CMC: Aggregate all LRU logs
      CMC->>MRO: Transmit flight health snapshot
  

3.3 Genomics: Distributed Field Sequencing Data Pipeline

• Enabling Description: The system is applied to manage data from genomic sequencing in remote locations for epidemiology or biodiversity studies. The remote data access subsystem is a portable DNA sequencer (e.g., Oxford Nanopore MinION) connected to a ruggedized laptop. It generates large (multi-gigabyte) raw signal data files. The data collecting subsystem is a mobile, containerized HPC node that can be deployed to a regional hub. Researchers bring their sequencers to this hub, which ingests the raw data and performs the computationally intensive basecalling and sequence alignment steps, converting raw signals into standardized FASTQ/BAM formats. The central data processing subsystem is a national or international genomic data archive (e.g., NCBI GenBank) that receives the processed, smaller BAM files for long-term storage, public access, and large-scale comparative analysis.

• Mermaid.js Diagram:

  erDiagram
      REMOTE_SEQUENCER ||--o{ RAW_DATA_FILE : generates
      RAW_DATA_FILE {
          string file_id PK
          blob raw_signal_data
          datetime timestamp
      }
      REGIONAL_HPC_NODE ||--|{ PROCESSED_SEQUENCE_FILE : processes
      RAW_DATA_FILE ||--|| PROCESSED_SEQUENCE_FILE : is_converted_to
      PROCESSED_SEQUENCE_FILE {
          string bam_file_id PK
          string file_id FK
          string alignment_metadata
      }
      CENTRAL_ARCHIVE ||--|{ PROCESSED_SEQUENCE_FILE : archives
  

---

4. Derivatives via Integration with Emerging Technologies

4.1 AI-Driven Predictive Data Triage and Compression

• Enabling Description: This embodiment integrates AI to optimize network usage. The remote data access subsystem includes an Edge AI accelerator (e.g., a Google Coral TPU) that runs a convolutional neural network (CNN) on captured images to classify document type and a time-series model on electronic data to check for anomalies. Based on the classification, it applies a context-aware compression algorithm (e.g., higher compression for low-importance documents). The data collecting subsystem uses a regional AI model to analyze patterns across its nodes, predicting network congestion and data priority. It dynamically re-routes data from low-priority remote systems to off-peak transmission windows. The central data processing subsystem uses the incoming metadata flags from the remote and collector tiers to automatically route data to different storage tiers and processing pipelines without manual intervention.

• Mermaid.js Diagram:

  flowchart TD
      subgraph Remote Tier
          A[Capture Data] --> B{Edge AI Analysis};
          B -- High Priority --> C[Low-Loss Compression];
          B -- Low Priority --> D[High-Lossy Compression];
      end
      subgraph Collector Tier
          E((Network))
          C --> F{Collector AI};
          D --> F;
          F -- Predicts Congestion --> G[Dynamic Scheduler];
      end
      subgraph Central Tier
          H((WAN))
          G --> H
          H --> I[Automated Data Routing];
          I --> J[Hot Storage / Real-time Analytics];
          I --> K[Cold Storage / Batch Processing];
      end
  

4.2 Blockchain-Anchored Data Provenance and Integrity Verification

• Enabling Description: This variation ensures an immutable, auditable trail for all captured data. At the remote data access subsystem, upon capturing a transaction, a SHA-256 hash of the data packet (image and metadata) is generated. This hash is recorded as a transaction on a permissioned blockchain (e.g., Hyperledger Fabric). The data collecting subsystem periodically aggregates the hashes from all its remote nodes into a Merkle Tree and posts the Merkle Root to the same blockchain. This creates a tamper-evident seal for a large batch of transactions with a single on-chain entry. The central data processing subsystem, upon receiving a data packet, can independently verify its integrity by re-computing the hash and validating its inclusion in a Merkle Tree whose root exists on the blockchain, thus providing non-repudiation of data origin and content.

• Mermaid.js Diagram:

  sequenceDiagram
      participant Remote
      participant Collector
      participant Blockchain
      participant Central
  
      Remote->>Remote: Capture Data Packet
      Remote->>Remote: Generate Hash(Data)
      Remote->>Blockchain: Record Transaction(Hash)
      Remote->>Collector: Send Data Packet
      Collector->>Collector: Aggregate Hashes in Merkle Tree
      Collector->>Blockchain: Record Merkle Root
      Collector->>Central: Forward Data Packet
      Central->>Central: Re-compute Hash(Data)
      Central->>Blockchain: Verify Hash against Merkle Root
  

---

5. Derivative via The "Inverse" or Failure Mode

5.1 Graceful Degradation with Mesh Network Store-and-Forward Failover

• Enabling Description: The system is engineered for resilience in environments with unreliable network connectivity. The remote data access subsystem operates in a "connected" or "disconnected" state. In the "connected" state, it transmits data normally. If the primary link to the data collecting subsystem fails, it transitions to a "disconnected" state, encrypting and storing all captured transactions locally in a FIFO queue. It then activates a secondary, low-power mesh networking protocol (e.g., Bluetooth LE Mesh or Zigbee) to discover other nearby remote subsystems. It can forward its queued data to a neighboring node that has connectivity, which will then relay the data to the collector. This creates a store-and-forward mesh network as a fallback. The data collecting subsystem is programmed to accept data packets originating from other remote nodes on behalf of a disconnected node, ensuring eventual data delivery.

• Mermaid.js Diagram:

  stateDiagram-v2
      [*] --> Connected
      Connected: Transmitting data to collector via primary link.
      Connected --> Disconnected: Primary link failure
      Disconnected: Storing data locally. Activating mesh protocol.
      Disconnected --> Connected: Primary link restored
      Disconnected --> Forwarding_via_Peer: Neighbor node found
      Forwarding_via_Peer: Relaying queued data to neighbor.
      Forwarding_via_Peer --> Disconnected: Relay complete
  

---

Combination Prior Art Scenarios

1. Combination with Open Financial Exchange (OFX): The described three-tiered architecture is combined with the OFX standard for banking. The remote data access subsystem (e.g., a bank's remote deposit capture scanner) captures check images and transaction metadata, then formats this data into a valid OFX message packet. The data collecting subsystem acts as a regional OFX server for a group of branches, aggregating these packets and polling the remote scanners. It forwards the batched OFX data to the central data processing subsystem, which is the bank's core processing system that parses the standard OFX messages to clear the checks.

2. Combination with DICOM and PACS: The architecture is used for medical imaging. The remote data access subsystem is an MRI or CT scanner at a clinic, which generates images in the DICOM format. The data collecting subsystem is the hospital's on-premise Picture Archiving and Communication System (PACS) server, which polls the imaging modalities to collect new studies. The central data processing subsystem is a cloud-based, regional Vendor Neutral Archive (VNA) or research repository that periodically ingests DICOM studies from multiple hospital PACS servers for long-term archival and anonymized analysis.

3. Combination with MQTT Protocol: The architecture is implemented using the standard MQTT publish/subscribe protocol for IoT. The remote data access subsystems are configured as MQTT clients, which publish their captured data (e.g., sensor readings or images) to a specific topic (e.g., area_51/device_007/data). The data collecting subsystem is an MQTT broker that subscribes to topics from all clients in its region. It buffers, filters, and logs these messages. The central data processing subsystem is a backend application that subscribes to the broker with a wildcard (e.g., +/+/data), receiving the aggregated data streams for central storage and processing. The polling mechanism of the patent is analogous to the broker managing connections and subscriptions from clients.