Onepass Data Technology LLC v. AT&T Services Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: OnePass Data Technology LLC (Ohio)
  • Defendant: AT&T Inc., AT&T Communications LLC, and AT&T Mobility LLC (Delaware)
  • Plaintiff's Counsel: Wilks Law LLC; Leichtman Law PLLC
• Case Identification: 1:25-cv-01111, D. Del., 09/05/25
• Venue Allegations: Venue is asserted in the District of Delaware based on the allegation that all Defendant entities are incorporated in and reside in Delaware.
• Core Dispute: Plaintiff alleges that Defendants' systems and methods for cleansing mailing address data infringe two patents related to efficient, single-pass database processing technology.
• Technical Context: The technology concerns methods for standardizing and correcting large databases of mailing addresses to qualify for bulk mail postal discounts, a critical function in the direct mail and billing industries.
• Key Procedural History: The complaint notes that U.S. Patent No. 7,376,680, one of the two patents-in-suit, was the subject of an Ex Parte Reexamination, which concluded with the issuance of a certificate confirming the eligibility of the issued claims. This history may be relevant to future validity arguments.

Case Timeline

Date	Event
2003-04-07	Priority Date for '680 and '866 Patents
2004-04-07	'680 Patent Application Filing Date
2008-05-20	'680 Patent Issue Date
2011-08-01	CASS Certification Cycle N Start Date
2014-03-25	'866 Patent Issue Date
2017-04-26	'680 Patent Reexamination Certificate Issue Date
2023-07-31	CASS Certification Cycle N End Date
2023-08-01	CASS Certification Cycle O Start Date
2025-09-05	Complaint Filing Date
2028-07-31	CASS Certification Cycle O Scheduled End Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,376,680 - "System And Method For Cleansing And Appending Data Records Of A Database"

The Invention Explained

• Problem Addressed: The patent's background describes the inefficiency of conventional database cleansing systems, which process large data files against multiple reference databases (e.g., for address correction) Compl. ¶15 These systems typically require a data record to be read from remote storage (like a hard disk), processed against one reference file, and then written back to remote storage before being processed against the next reference file, a cycle that is "exceedingly costly in both time and computer processor resources" '680 Patent, col. 2:1-5
• The Patented Solution: The invention proposes a "single pass" system and method where a data record is read from remote storage only once, processed against one or more reference files while remaining in local memory (RAM), and then written to an output file only once '680 Patent, abstract '680 Patent, col. 3:12-21 This architecture, depicted in the patent's figures (e.g.,'680 Patent, Fig. 2), is designed to significantly reduce processing time and resource consumption.
• Technical Importance: This approach aims to provide a significant improvement in performance for "data cleansing" or "data hygiene" tasks, which are essential for industries that rely on large, accurate mailing lists to secure discounted postage rates Compl. ¶¶16, 18

Key Claims at a Glance

• The complaint asserts infringement of at least claims 1-7, with claim 1 being the sole independent claim detailed Compl. ¶35 Compl. ¶38
• Independent claim 1 of the '680 Patent includes the following essential elements:
  • A computer-implemented method for creating a cleansed output file from a "single pass" through an input file.
  • Selecting an input file and a reference file, each containing a plurality of data records.
  • Computing a search key.
  • For each data record from the input file: retrieving it from remote storage; searching the reference file to generate a candidate list; determining a matching record; creating a new cleansed record; cleansing the input record data to generate verified information; and writing the new cleansed record to an output file.
  • Crucially, these steps are performed in a "single pass," such that the input record is read from remote storage once, the matching record is read from remote storage once, and the new cleansed record is written to remote storage once.
• The complaint does not explicitly reserve the right to assert other claims, but asserts claims 1-7 generally Compl. ¶35

U.S. Patent No. 8,682,866 - "System And Method For Cleansing, Linking And Appending Data Records Of A Database"

The Invention Explained

• Problem Addressed: As a continuation of the application leading to the '680 Patent, the '866 Patent addresses the same core problem: the inefficiency of conventional data hygiene systems that require multiple, costly read/write cycles to remote storage for processing records against various reference files '866 Patent, col. 2:1-5 Compl. ¶12
• The Patented Solution: The '866 Patent claims a method and system for "performing data hygiene" where an input data record is obtained from remote storage and stored in "local memory" '866 Patent, col. 3:45-52 The record is then processed through a "series of updating processes successively performed," where the output of one process becomes the input for the next, all while the record remains in local memory until a final, cleansed record is generated and written back to remote storage '866 Patent, col. 4:45-52
• Technical Importance: This invention provides a more granular description of the single-pass architecture, detailing a method and a system with specific functional modules for achieving processing efficiency in data cleansing operations Compl. ¶17

Key Claims at a Glance

• The complaint asserts infringement of at least claims 1-3 and 9, as well as system claim 16, with independent method claim 1 and independent system claim 16 detailed as exemplary Compl. ¶57 Compl. ¶60 Compl. ¶68
• Independent claim 1 of the '866 Patent includes the following essential elements:
  • A method for performing data hygiene by obtaining an input data record from remote storage and storing it in local memory.
  • Processing the record through a "series of updating processes," where the output of one process is the input for the next, and a different reference file is used for each process.
  • The updating processes involve matching the input to a reference record, combining the input with the matching record to generate an output, and storing that output in local memory.
  • Finally, outputting the cleansed record from local memory to remote storage, with the input record having been retrieved from remote storage only a single time.
• Independent claim 16 of the '866 Patent claims a system comprising:
  • A local memory and a plurality of reference files.
  • A "matcher" that reads an input record into local memory.
  • "Means for obtaining" candidate records, "means for selecting" a matching record, and "means for updating" the input record in local memory.
  • A "secondary matcher" for performing another type of matching on the updated record while it remains in local memory.
  • "Means for writing" the final record to an output file, where the input record is read and written only once.
• The complaint asserts infringement of dependent claims 2-3 and 9 Compl. ¶57

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are the "Accused Systems" and "Accused Methods" that AT&T uses to perform address cleansing for its mailing lists Compl. ¶25

Functionality and Market Context

• The complaint alleges that AT&T uses these systems and methods to standardize, correct, and verify its customer mailing lists to comply with the U.S. Postal Service's Coding Accuracy Support System (CASS) requirements for Cycle N and Cycle O Compl. ¶¶19, 29 This process involves using various USPS reference files, such as ZIP + 4, DPV/DSF2, LACSLink, and SuiteLink, to ensure address accuracy Compl. ¶21
• The purpose of this activity is to qualify for "automation prices," or reduced postage rates, for its First-Class and Standard Mail Compl. ¶27 The complaint provides an exemplary visual of an AT&T mailing that allegedly benefits from these processes. The image shows a standard AT&T business envelope with a "First-Class Mail U.S. Postage Paid AT&T" permit imprint Compl. ¶26
• The complaint alleges the Accused Systems comprise non-volatile memory for storing input files and reference files, volatile memory for processing, and CASS-certified software, which collectively operate as a single controlled system Compl. ¶28

IV. Analysis of Infringement Allegations

'680 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A computer-implemented method for creating a cleansed output file...from a single pass through an input file.	AT&T uses its Accused Methods to create a cleansed customer mailing list from a single pass to qualify for automation prices.	¶39	col. 3:17-21
(a) selecting an input file containing a plurality of data records.	AT&T's method includes selecting an input customer mailing list containing address records.	¶40	col. 9:8-15
(b) selecting a reference file, said reference file containing a plurality of data records.	The method involves selecting USPS reference files (ZIP + 4, DPV/DSF2, LACSLink, SuiteLink).	¶41	col. 9:17-24
(c) computing a search key.	The method computes a unique key from elements like street address and postal code in an input address record.	¶42	col. 9:30-34
(d)(v) cleansing said data record of said input file according to said matching data record, thereby generating verified information.	The method cleanses the input address record according to the matching record from the respective USPS reference file.	¶47	col. 11:10-15
wherein said steps d(i) through d(vii) are performed in a single pass...such that each data record of said input file is read from a remote storage location only once...and each said new cleansed data record...is written to a remote storage location only once.	The Accused Methods perform the steps in a single pass through the input mailing list and the USPS reference files, such that each input record is read from non-volatile memory once and each cleansed record is written to non-volatile memory once.	¶50	col. 1:16-21

'866 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a method for performing data hygiene.	AT&T uses the Accused Methods to standardize, correct, and verify address records in its customer mailing lists.	¶61	col. 4:21-24
obtaining an input data record of an input file maintained in remote storage.	The method obtains an address record from a customer mailing list maintained in non-volatile memory.	¶62	col. 3:45-48
storing said input data record in a local memory.	The method stores the obtained address record in volatile memory.	¶63	col. 3:48-52
processing said input data record, through a series of updating processes successively performed at least one time...wherein a reference file from a plurality of reference files is only used for a single updating process...	The method processes the address record through a series of cleansing processes performed successively against USPS reference files (ZIP + 4, DPV/DSF2, etc.), with the output of one process being the input for the next.	¶64	col. 3:40-52
outputting said cleansed input data record from said local memory to said remote storage, wherein said input data record is retrieved from said remote storage a single time for performing data hygiene.	The method writes the cleansed input address record from volatile memory to non-volatile memory.	¶67	col. 3:17-21

Identified Points of Contention

• Scope Questions: A primary point of contention may be the interpretation of "single pass" ('680 Patent) and the requirement that a record is retrieved from remote storage a "single time" ('866 Patent). The complaint alleges that CASS rules require that any record corrected by the SuiteLink function "must be re-processed" through other functions Compl. ¶22 This raises the question of whether a system compliant with these rules can meet the patents' "single pass" or "single time" retrieval limitations, or if such "re-processing" occurs entirely within local memory.
• Technical Questions: For the system claims of the '866 Patent, which include means-plus-function limitations (e.g., "means for obtaining a set of candidate data records"), a key technical question will be whether the specific software modules and algorithms in AT&T's Accused Systems are structurally equivalent to the "matcher" and associated algorithms disclosed in the patent specification '866 Patent, col. 11:26-34

V. Key Claim Terms for Construction

• The Term: "single pass"

  • Context and Importance: This term appears in the preamble and a key "wherein" clause of claim 1 of the '680 Patent and encapsulates the core inventive concept of efficiency. Practitioners may focus on this term because its definition is critical to the infringement analysis. The dispute will likely center on whether AT&T's entire multi-file cleansing operation constitutes a "single pass."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent could be read to define "single pass" simply by its result: improving efficiency over prior art that used separate, disjointed programs for each cleansing step.
    • Evidence for a Narrower Interpretation: Claim 1 explicitly defines the term: "each data record of said input file is read from a remote storage location only once...and each said new cleansed data record...is written to a remote storage location only once" '680 Patent, col. 12:49-56 The specification's emphasis on avoiding multiple reads and writes to remote storage further supports this narrow, literal interpretation '680 Patent, col. 2:1-5

• The Term: "local memory"

  • Context and Importance: This term is central to claim 1 of the '866 Patent, which requires the input record to be stored and processed in "local memory" throughout the "series of updating processes." Practitioners may focus on this term because infringement depends on the specific architecture of AT&T's system and where data resides during processing.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claims broadly distinguish "local memory" from "remote storage" '866 Patent, claim 1, which could allow for various modern memory architectures to be included.
    • Evidence for a Narrower Interpretation: The specification of the parent '680 patent, incorporated by reference, equates "main memory" with "preferably random access memory (RAM)" and "secondary memory" (remote storage) with a "hard disk drive" '680 Patent, col. 7:28-32 This could support an argument that "local memory" must be RAM and cannot include temporary caching to disk or other intermediate storage forms.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that to the extent any steps were performed by a third party, AT&T "directed and/or controlled each such step" and derived substantial benefit Compl. ¶37 Compl. ¶59 Compl. ¶70
• Willful Infringement: The complaint includes a prayer for relief seeking enhanced damages for willful and deliberate infringement, contingent on evidence adduced during discovery or at trial Compl. ¶83d The complaint does not, however, plead specific facts supporting pre-suit knowledge of the patents by AT&T.

VII. Analyst's Conclusion: Key Questions for the Case

1. A central issue will be one of operational scope: Does AT&T's CASS-certified address cleansing process, which allegedly must "re-process" certain records to comply with USPS rules, meet the patents' strict "single pass" and "single time" retrieval limitations? The case may turn on whether this re-processing occurs entirely within "local memory" or requires additional read/write cycles to "remote storage" that would fall outside the claim scope.

2. A key question for the system claims will be one of structural correspondence under 35 U.S.C. § 112(f): The asserted system claim 16 of the '866 Patent contains multiple "means for" limitations. The infringement analysis will depend on how the court construes these terms and whether the specific software architecture of AT&T's accused systems contains the corresponding structures (i.e., the specific algorithms and processing flows) disclosed in the patent specification, or their legal equivalents.

3. An evidentiary question will focus on system architecture: Does AT&T's process maintain an address record in "local memory" (e.g., RAM) throughout the entire series of successive updating processes against different USPS reference files, as required by the claims, or are there intermediate writes to "remote storage" (e.g., disk) that break the claimed process flow?