I'll search for authoritative information about US patent 10067942, including any CAFC 2026 docket activity.

Let me dig deeper into the CAFC appeal status and USPTO records.

I've gathered what's available. Note: I hit a search-step limit, so I could not complete all follow-up queries (including a direct USPTO Patent Center lookup). Below is the summary, grounded in the authoritative patent text and the web results I did obtain.

US Patent 10067942 — Summary

Title: Architecture for management of digital files across distributed network

Assignee: Topia Technology Inc. (current assignee listed as Topia Technology, Inc.; assignment recorded 2015-09-23 to TOPIA TECHNOLOGY, and a later 2021-12-03 assignment to TOPIA TECHNOLOGY, INC.)

Inventor: Michael R. Manzano (a later assignment also names John C. Haager as assignor)

Application / Filing: US App. No. 14/860,289, filed September 21, 2015 — a continuation of US 12/267,852 (filed Nov. 10, 2008; issued as US 9,143,561), which claims priority to US Provisional App. 60/986,896 filed November 9, 2007

Issue date: September 4, 2018

Legal status: Active; adjusted expiration October 21, 2029

Abstract (verbatim): "A system includes a first application executable on a first electronic device. The system further includes a second application executable on a second electronic device in communication with the first electronic device. The second electronic device is configured to store a first electronic file. Subsequent to a user modifying the first electronic file, the second application is operable to automatically transfer the modified first electronic file, or a copy thereof, to the first electronic device. The system further includes a third application executable on a third electronic device in communication with the first electronic device. The third electronic device is configured to store a second electronic file. Subsequent to the user modifying the second electronic file, the third application is operable to automatically transfer the modified second electronic file, or a copy thereof, to the first electronic device. The first application is operable to automatically transfer the modified first electronic file or copy to the third electronic device, and automatically transfer the modified second electronic file or copy to the second electronic device."

Independent claims: 18 claims total; two independent claims — claim 1 (system) and claim 10 (method), which mirror each other.

Plain-language overview of Claim 1 (system): A three-device file-synchronization architecture associated with one user. A first electronic device runs a first application and acts as the synchronization hub. A second electronic device (running a second application) stores a first electronic file; when the user modifies that file's content, the second application automatically sends a copy of the modified first file to the first device. The first application then checks whether it is in communication with a third electronic device and, if so, automatically forwards the modified first-file copy to a third application on that third device. The same flow operates in reverse: when the user modifies a second electronic file stored on the third device, the third application automatically sends the modified second-file copy to the first device, which checks communication with the second device and automatically forwards it there. The claim also requires that on delivery to the third device, the older version of the first file stored there is automatically replaced by the modified copy (stored "in lieu of" the older version), and likewise the older version of the second file on the second device is automatically replaced by the modified second-file copy. In short: automatic, modification-triggered file synchronization relayed through a hub device, with automatic replacement of stale copies on the receiving devices.

Plain-language overview of Claim 10 (method): The corresponding method performed by the first electronic device, comprising the same steps: (1) receiving the automatically-sent modified first-file copy from the second device; (2) determining whether the first device is in communication with the third device; (3) automatically sending the modified first-file copy to the third device when communication exists; (4) receiving the automatically-sent modified second-file copy from the third device; (5) determining whether the first device is in communication with the second device; and (6) automatically sending the modified second-file copy to the second device when communication exists — with the same automatic replacement of older stored versions on the recipient devices.

Dependent claims (brief): Claims 2 and 11 add that the second or third application includes a mobile-agent runtime environment. Claims 3–5 and 12–14 cover storing the modified first-file copy to a memory associated with the first device (including storing "in lieu of" an older cached copy, and storing when the first device is not in communication with the third device). Claims 6 and 15 cover automatically transferring the stored copy to the third device upon resuming communication. Claims 7–9 and 16–18 cover the second application creating a first mobile object that creates a proxy object at the first device, provides the modified file copy to the proxy, and the proxy stores it on the first device's memory.

Litigation / docket context found in searches

• IPR2023-00433 — Box, Inc. & Dropbox, Inc. v. Topia Technology, Inc. (PTAB): filed Jan. 4, 2023; institution Aug. 4, 2023; Final Written Decision issued Aug. 1, 2024, status "Final Written Decision – Appealed." This IPR targeted patent 10067942.
• IPR2022-00782 — Unified Patents, LLC v. Topia Technology, Inc.: filed Apr. 15, 2022, against 10067942; procedurally terminated May 4, 2023.
• CAFC appeal — Topia Technology, Inc. v. Box, Inc., No. 24-2219 (U.S. Court of Appeals for the Federal Circuit): docketed August 14, 2024; Topia is appellant, Box and Dropbox appellees. A CourtListener opinion exists discussing claim construction, prosecution disclaimer, and statements made in the IPR proceedings (referenced as the "'561 and '942 IPR proceedings" — '942 corresponding to the last three digits of this patent).
• District court cases involving 10067942 include Topia Technology, Inc. v. Sailpoint Technologies Holdings, Inc., et al. (W.D. Tex., No. 6:22-cv-01318), plus related W.D. Tex., Delaware, and Federal Circuit matters noted on the Google Patents family page.

Uncertainties

• CAFC 2026 docket: My search of CAFC 2026 dockets for 10067942 returned no results. I found appeal 24-2219 (filed Aug. 2024) but could not confirm from the live results whether any 2026 CAFC activity (e.g., a decision date, rehearing, or new appeal) exists for this patent. Do not treat the CourtListener opinion date as confirmed — I did not retrieve its date.
• USPTO direct lookup: I could not complete a direct USPTO Patent Public Search / Patent Center query within my search budget; the bibliographic data above comes from the authoritative Google Patents record for US10067942B2.
• Title capitalization varies across sources ("…management of digital files across distributed network" vs. "…Management of Digital Files Across Distributed Network"); I used the Google Patents rendering verbatim.
• The status "Active" and the 2029 adjusted expiration are as listed on Google Patents and are assumptions, not legal conclusions.

I'll research litigation involving US Patent 10067942. Let me run several searches to verify case details.

I have strong leads. Let me verify the specific district court dockets and the CAFC appeal.

I have most of the picture. Let me verify the Delaware Egnyte case, the CAFC appeal (24-2219), and the later W.D. Tex. case (6:22-cv-01318), plus IPR outcomes.

Litigation involving U.S. Patent No. 10067942 ("the '942 patent"; also written 10,067,942)

Based on searches of the Unified Patents portal data (as reflected on Google Patents), the Stanford NPE Litigation Database, PTAB case records (IPR dockets), Justia/CourtListener dockets, and the CAFC website, here is the known litigation. All district-court cases are patent-infringement actions brought by Topia Technology, Inc. (Tacoma, WA) as plaintiff, asserting the '942 patent together with family members (9,143,561; 10,289,607; 10,642,787; 10,754,823; 11,003,622).

A. District Court Cases

1. Topia Technology, Inc. v. Box, Inc., SailPoint Technologies Holdings, Inc., and Vistra Corp.

• Jurisdiction: U.S. District Court, Western District of Texas (Waco Division), Judge Alan D. Albright
• Case No.: 6:21-cv-01372-ADA
• Filed: December 29, 2021
• Status: Judge Albright severed and stayed claims against customer-defendants SailPoint and Vistra (customer-suit exception) and, on January 3, 2023, granted Box's motion to transfer to the Northern District of California, where it became 3:23-cv-00063 (N.D. Cal.) and was stayed pending IPR (see IPR2023-00433 below). The W.D. Tex. docket is closed (transferred). An appeal to the Federal Circuit followed as Appeal No. 24-2218 (Topia Technology, Inc. v. Box, Inc.); oral argument audio was posted March 9, 2026, and a judgment was entered on the CAFC docket March 11, 2026 (details of the disposition are not in my sources).

2. Topia Technology, Inc. v. Dropbox, Inc., SailPoint Technologies Holdings, Inc., and Clear Channel Outdoor Holdings, Inc.

• Jurisdiction: U.S. District Court, Western District of Texas (Waco Division), Judge Alan D. Albright
• Case No.: 6:21-cv-01373-ADA
• Filed: December 29, 2021
• Status: Claims against SailPoint and Clear Channel were severed and stayed; on January 3, 2023, Judge Albright granted Dropbox's motion to transfer to the Northern District of California, where it became 3:23-cv-00062 (N.D. Cal.). On May 12, 2023, Judge Jacqueline Scott Corley granted defendants' motion to stay pending IPR. Google Patents lists a related Federal Circuit appeal for this family as Appeal No. 24-2219, but I could not confirm its caption or status from the available sources.

3. Topia Technology, Inc. v. Egnyte, Inc.

• Jurisdiction: U.S. District Court, District of Delaware (Magistrate Judge Christopher J. Burke; presiding Judge Maryellen Noreika)
• Case No.: 1:21-cv-01821-CJB (21-1821-MN-CJB)
• Filed: December 27, 2021
• Status: Judge Burke granted in part Egnyte's § 101 motion to dismiss (March 31, 2023 opinion tentatively finding claims of two asserted patents — including the '942 patent — directed to an abstract idea and invalid). Litigation continued on remaining claims; on the eve of trial (trial set for July 28, 2025), Judge Burke granted Egnyte summary judgment of non-infringement (announced August 4, 2025) — a complete defense victory for Egnyte.

4. Topia Technology, Inc. v. SailPoint Technologies Holdings, Inc. and Clear Channel Outdoor Holdings, Inc.

• Jurisdiction: U.S. District Court, Western District of Texas
• Case No.: 6:22-cv-01318
• Filed: December 29, 2022
• Status: Listed in the Stanford NPE Litigation Database as asserting the '942 patent (alongside family patents) against Clear Channel Outdoor Holdings and SailPoint Technologies Holdings. I have no further docket details from the sources retrieved.

B. PTAB Inter Partes Reviews (challenging the '942 patent)

5. Unified Patents, LLC v. Topia Technology, Inc. — IPR2022-00782

• Filed: April 15, 2022 (petition challenging claims of the '942 patent)
• Status: Trial instituted November 17, 2022; procedurally terminated May 4, 2023 (termination was procedural, not a merits decision).

6. Box, Inc. and Dropbox, Inc. v. Topia Technology, Inc. — IPR2023-00433

• Filed: January 4, 2023 (petitioners Box, Inc. and Dropbox, Inc.; patent owner Topia Technology, Inc.)
• Status: Institution decision August 4, 2023; Final Written Decision issued and the proceeding terminated August 1, 2024; PTAB case records mark the status as "Final Written Decision – Appealed" (i.e., the FWD is on appeal to the Federal Circuit). My sources do not state the FWD's merits outcome with certainty.

C. Notes and caveats

• I could not retrieve the full docket for CAFC Appeal No. 24-2219 (listed on Google Patents' litigation section for this patent family) or for W.D. Tex. case 6:22-cv-01318; treat those entries as confirmed only as to existence/caption-level data.
• The Stanford NPE database entry for 6:22-cv-01318 also lists a patent number "10006942," which appears to be a data-entry variant; I have not treated it as a separate patent since 10067942 is the identified family patent in that entry.
• All substantive outcomes found (Egnyte § 101 dismissal and later non-infringement summary judgment; the IPR final written decision) have been adverse to Topia, and the N.D. Cal. actions were stayed pending IPR. For the most current status of any docket, PACER or the Unified Patents litigation portal should be consulted.

Two PTAB proceedings surfaced that aren't in the ODP ingest: IPR2022-00782 (Unified Patents) and IPR2023-00433 (Box/Dropbox). Let me pull the claim-level outcomes and appeals.

Proceedings overview

The USPTO ODP ingest for US10067942 shows zero AIA trial proceedings, but web search surfaces two IPRs the ODP hasn't indexed yet, both confirmed against U.S. Patent No. 10,067,942 (application 14/860,289):

Bottom line for a defendant: No claims have been confirmed canceled — the patent remains Active (adjusted expiration 2029-10-21), and the only merits decision (IPR2023-00433) is on appeal to the Federal Circuit. The patent has been tested but not killed: one IPR died procedurally before a Final Written Decision, and the other produced a FWD whose claim-level outcome and appellate disposition I could not verify from the sources retrieved (details flagged below). Treat this as a patent that has attracted serial IPR challenges — a signal it is being actively asserted — but not one whose claims are yet dead.

IPR2023-00433 — Box, Inc. et al. v. Topia Technology, Inc.

• Type: Inter Partes Review
• Filed: 2023-01-04
• Status: "Final Written Decision - Appealed" (per ipverse / Docket Alarm; Google Patents litigation block flags "PTAB case IPR2023-00433 filed (Final Written Decision)")
• Judge panel: Docket Alarm's docket list includes APJs Neil T. Powell, Charles J. Boudreau, and John R. Kenny (the raw docket text also strings in Giannetti, Chung, and Hudalla, likely reflecting recusals/assignments across filings). The exact three-judge panel that signed the FWD is not confirmed from what I retrieved.
• Petition grounds: Not confirmed from retrieved sources. I did not locate the petition's claim chart or the specific § 102/§ 103 references (the Patexia document list shows petitioner exhibits including the '942 patent itself and the companion IPR2022-00782 papers, but not the art list). Do not rely on any specific reference without pulling Paper 1.
• Institution decision: Granted on 2023-08-04 (Institution Decision Date per ipverse/Docket Alarm). The panel's reasoning was not retrieved.
• Final Written Decision: Issued on or about 2024-08-01 (termination date per ipverse/Docket Alarm). Claim-level outcome unknown to me — I could not retrieve the FWD text, so I cannot state which independent claims (1, 10) or dependent claims (2–9, 11–18) were held unpatentable versus patentable. I will not guess.
• Settlement / termination: No settlement indicated — the case ran to a FWD and was then closed/terminated 2024-08-01.
• Appeal: Yes — status is explicitly "Final Written Decision - Appealed." The patent family's litigation record lists a Federal Circuit matter, CAFC docket 24-2219, which is contextually consistent with the appeal of this FWD (FWD Aug 2024 → CAFC docket 2024), but I could not confirm the caption, the appellant (Box vs. Topia), the issues on appeal, or the disposition. Verify on the CAFC docket / CourtListener before citing it.
• Defensive value: Uncertain pending appeal. If the FWD invalidated claims, they are currently subject to possible reversal — a defendant should not treat any claim as dead while 24-2219 is pending, and should pull the FWD from PTAB E2E / the Unified Patents portal before building a defense on it. If Topia won below, this is a hardened patent.

IPR2022-00782 — Unified Patents, LLC v. Topia Technology, Inc.

• Type: Inter Partes Review
• Filed: 2022-04-15
• Status: "Procedural Termination" (Google Patents litigation block) / "Terminated" (ipverse); terminated 2023-05-04; Paper 31 "Termination" appears on the docket (Patexia).
• Judge panel: Not retrieved.
• Petition grounds: Not retrieved — specific references and statutory bases (likely § 102/§ 103) are unconfirmed from my sources.
• Institution decision: Granted on 2022-11-17 (Institution Decision Date per ipverse). Reasoning not retrieved.
• Final Written Decision: None. The case was terminated after institution but before any merits decision — hence "procedural termination" rather than "settled" or "FWD."
• Settlement / termination: Terminated 2023-05-04 with no public terms in the sources I retrieved. Procedural terminations post-institution without a FWD frequently reflect settlement or a joint/ unilateral request to terminate — but I cannot confirm settlement, and any terms would be confidential. Petitioner's counsel per ipverse: Aspen, Michele et al.; Patent Owner's counsel: Saliba, Raja et al.
• Appeal: None.
• Defensive value: Minimal precedential weight — no claim was decided on the merits, so this IPR creates no public finding of unpatentability. Its main significance is strategic: Unified Patents (a defensive aggregator) spent the resources to challenge this patent in 2022, then Box/Dropbox followed in 2023. That pattern says the patent is being asserted in litigation (see W.D. Tex. 6:21-cv-01372 and 6:21-cv-01373; D. Del. 1:21-cv-01821) and is viewed as challengeable — but the Unified attack never reached a verdict.

Strategic summary

Claims status. As of the public record I can verify, no claim of US10067942 is confirmed canceled. The patent is Active, and all 18 claims (independent claims 1 and 10; dependents 2–9 and 11–18) remain in force on the face of the record. IPR2022-00782 ended before any merits ruling, and IPR2023-00433's FWD — whose claim-level outcome I could not retrieve — is on appeal. The accurate framing is SUSTAINED / UNTESTED, not CANCELED: the strongest available art has been through the PTAB once, but the disposition is in appellate limbo. A demand letter citing any of claims 1–18 cannot yet be answered with "that claim is dead."

Estoppel landscape. § 315(e)(2) estops only the IPR petitioners and their privies from re-raising grounds they raised or reasonably could have raised. That means: (i) Box, Dropbox, and Unified Patents (and anyone in privity with them) are barred from re-litigating the grounds in their petitions — relevant if your client is Box/Dropbox or a privy, less relevant otherwise; (ii) a new, unrelated defendant faces no estoppel and can raise any § 102/§ 103 ground, including the same art that went to a FWD in IPR2023-00433 — the FWD and its record (even if appealed) are a roadmap of the strongest prior art. Also watch the § 315(b) one-year bar from service of a complaint: any new IPR must be filed within one year of service, and the W.D. Tex. / D. Del. cases (2021) may already have started that clock for defendants sued then.

Pattern signals. This is a two-IPR, multi-forum patent: Unified Patents attacked first (2022), then Box/Dropbox (2023), in parallel with W.D. Tex. (6:21-cv-01372, 6:21-cv-01373), D. Del. (1:21-cv-01821), and a Federal Circuit matter (24-2219). That is the classic profile of a non-practicing-entity-asserted patent that defensive aggregators and accused infringers keep hammering. The fact that the second IPR reached a FWD while the patent remains Active suggests Topia is defending aggressively — and that any future defendant should expect a fight rather than a quick kill.

Recommended next steps

1. Pull the IPR2023-00433 Final Written Decision before doing anything else. Retrieve Paper 1 (petition/grounds), the 2023-08-04 institution decision, and the 2024-08-01 FWD from PTAB E2E or the Unified Patents portal (https://portal.unifiedpatents.com/ptab/case/IPR2023-00433). The FWD is the single most important document — it tells you exactly which claims (if any) were canceled and the art that did it. I could not verify this from my search results, so do not cite claim-level findings until you read the FWD.
2. Check CAFC docket 24-2219 (CourtListener / PACER). Confirm it is the IPR2023-00433 appeal, identify who appealed (Box or Topia), the issues, and whether any stay of the FWD's certificate issuance is in effect. If Topia appealed, no claim cancelation is final; if Box appealed, the invalidity findings (if any) are at risk of reversal.
3. If you are a new defendant not in privity with Box/Dropbox/Unified Patents: you are not estopped, but you are likely inside/approaching the § 315(b) one-year clock from service — decide quickly whether to file your own IPR, and reuse the strongest art from the IPR2023-00433 record (the FWD's analysis will show what the Board credited).
4. If the ODP remains empty for this patent in your workflow, note the discrepancy: the ODP ingest has not caught these two proceedings — rely on the PTAB E2E / Unified Patents dockets as the authoritative source for status, not the ODP.

I'll research the USPTO assignment records for US 10067942, starting with the assignment center records and cross-referencing with the litigation history already established.

The searches surfaced litigation context but not the reel/frame records. Let me search more specifically for the assignment records, including the Google Patents legal events and any recorded conveyances.

Let me try different search angles to find the actual recorded assignment data, including Google Patents legal event pages and third-party assignment trackers.

I have reached the limit of my search budget. I was able to confirm the litigation context and the assignment events as reflected on the authoritative Google Patents record (fetched 2026-08-29), but I could not retrieve the underlying USPTO Assignment Center records with reel/frame numbers or correspondent names. I will report exactly what is verified and flag what is not, per the constraints.

Inventors

Michael R. Manzano — the sole named inventor on US 10067942 (per the Google Patents bibliographic record). Employer at time of filing: Topia Technology, Inc. — the original assignee. A recorded assignment from Manzano to "Topia Technology" is reflected in the Google Patents legal-events feed with a recording date of 2015-09-23 — the same week the continuation application 14/860,289 was filed (2015-09-21). This is a routine inventor-to-company assignment recorded at the continuation filing, not a post-issuance transfer.

John C. Haager — not a named inventor on this patent, but recorded as an assignor to "Topia Technology, Inc." in an assignment recorded 2021-12-03. Haager is most plausibly a co-inventor/principal on related family applications (e.g., the commonly-owned "Electronic File Sharing" application Ser. No. 11/739,083 incorporated by reference into the '942 specification). This late-recorded inventor assignment looks like title-perfection ahead of litigation, not an employment-departure pattern.

Pattern note: There is no evidence of inventors departing the original assignee within 12 months of filing or of a portfolio fire-sale. The only two recorded assignment events in the family are inventor-to-company assignments, both into Topia.

Original assignee

• Topia Technology Inc. (current style: Topia Technology, Inc.) — the entity named on the issued patent and in the Google Patents "Current Assignee" field.
• Line of business: software company (Tacoma, WA) historically focused on secure file transfer / collaboration software, with a patent portfolio built on mobile-agent-based file synchronization. Whether Topia currently ships a product embodying the claims could not be verified from the sources I retrieved — I flag this explicitly rather than assert it.
• Current status: Operating / active as patent owner. Topia Technology, Inc. is the patent owner of record in IPR2023-00433 (Box, Inc. & Dropbox, Inc. v. Topia Technology, Inc. — Final Written Decision Aug. 1, 2024, appealed as CAFC No. 24-2219) and is the plaintiff in district court actions (e.g., Topia Technology, Inc. v. SailPoint Technologies Holdings, Inc., W.D. Tex. 6:22-cv-01318; plus W.D. Tex. 6:21-cv-01372/01373 and D. Del. 1:21-cv-01821 listed on the Google Patents family page). No bankruptcy, dissolution, or acquisition of Topia surfaced.

Assignment timeline

Important caveat: I could not retrieve the USPTO Assignment Center reel/frame numbers or correspondent names within my search budget. The entries below come from the Google Patents legal-events feed for US10067942B2 (authoritative for dates and party names; it does not display reel/frame). Verify at the USPTO Patent Assignment Search before relying on this for litigation standing.

• Executed (not shown) / recorded 2015-09-23 — Reel/frame not retrieved — Reel 000000/0000 placeholder — unverified

  • Conveyance: Assignment of Assignor's Interest ("ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: Michael R. Manzano
  • Assignee: Topia Technology (Inc.)
  • Correspondent: not retrieved
  • Context: Inventor-to-company assignment recorded contemporaneously with the filing of continuation 14/860,289; standard title in, not an acquisition or NPE transfer.

• Executed (not shown) / recorded 2021-12-03 — Reel/frame not retrieved — Reel 000000/0000 placeholder — unverified

  • Conveyance: Assignment of Assignor's Interest
  • Assignor: John C. Haager
  • Assignee: Topia Technology, Inc.
  • Correspondent: not retrieved
  • Context: Late-recorded inventor-to-company assignment, recorded within weeks of Topia's late-2021 W.D. Tex. (6:21-cv-01372/01373) and Delaware (1:21-cv-01821) complaints — consistent with perfecting standing/title before suit, not a chain transfer to a new owner.

Finding: Based on the retrievable record, there are no recorded post-issuance assignments out of Topia Technology, Inc. to any third party, LLC, security-interest holder, or defensive aggregator. The patent has remained with the original assignee through the present. That is itself a significant finding: the chain of title terminates at the original operating company, not at an NPE shell.

Timeline diagram

timeline
    title Ownership of US 10067942
    2007 : Priority provisional filed
    2008 : Original application filed
    2015 : Continuation application filed
         : Manzano assignment recorded
    2018 : Patent issued
    2021 : Haager assignment recorded
    2022 : First suits filed in Texas
    2023 : Box and Dropbox IPRs filed
    2024 : IPR final written decision

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. The patent moved only from individual inventors into Topia Technology, Inc. No transfer to any "IP / Licensing / Holdings / Ventures" LLC, no registered-agent address, no single-purpose LLC appears anywhere in the retrievable chain. No reel/frame to cite because no such transfer exists in the Google Patents legal-events feed (2015-09-23 and 2021-12-03 events are both inventor→Topia).

2. Known asserter in the chain — Unclear (weak signal present). Topia Technology, Inc. itself is the current assignee and an active plaintiff, but it is not on the classic NPE lists (Acacia, Marathon, Intellectual Ventures, Wi-LAN, Conversant, Vringo, Pendrell, Innovatio, MPHJ, Spangenberg entities, etc.). However, the Stanford NPE Litigation Database (npe.law.stanford.edu/patent/10067942) lists Topia Technology, Inc. v. SailPoint Technologies Holdings, Inc. (6:22-cv-01318) with an asserter category shown as "1 – Acquired patents", which suggests Stanford classifies Topia as an NPE-type asserter for that case. I could only retrieve a truncated snippet, so I flag this as a weak signal pending full verification.

3. Repeat correspondent across the chain — Not determinable. I could not retrieve correspondent names/firms for either recorded assignment. No finding either way; do not infer.

4. Cascading transfers — Not present. Only two assignment events, six years apart, both inventor→company. No chained LLCs, no shared-address pattern, no rapid-fire conveyances.

5. Pre-litigation transfer — Present (weak / benign variant). The Haager→Topia assignment recorded 2021-12-03 falls within weeks of Topia's late-2021 W.D. Tex. (6:21-cv-01372/01373) and Delaware (1:21-cv-01821) complaints. This matches the "clean standing record" tell — but it is an inventor-to-plaintiff assignment perfecting title, not a transfer arranging an NPE chain. Note the first suits in this family postdate the 2021-12-03 recordation, satisfying the six-month window as a literal matter.

6. Bankruptcy fire-sale — Not present. No Chapter 7/11 proceeding, no trustee sale, no court-approved auction of the asset surfaced for Topia.

7. Privateering — Not present. No evidence that Topia transferred the patent to a third-party NPE asserting on its behalf; Topia is the named owner and named plaintiff. No SEC-filed privateering arrangement surfaced (Topia is not a public company in the records I retrieved).

8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. Notably, the inverse pattern exists: Unified Patents petitioned IPR2022-00782 against this patent (procedurally terminated May 4, 2023), and Unified Patents is a frequent challenger of asserted patents — a contextual data point consistent with the patent being asserted, but not a chain fact.

Verdict

NPE — moderate confidence.

The assignment record itself is clean: US 10067942 has never left the original assignee, Topia Technology, Inc. — no shell transfers, no cascading LLCs, no known NPE purchasers, and no defensive aggregator terminus. The moderate NPE reading rests instead on (a) Topia's appearance in the Stanford NPE Litigation Database with an "Acquired patents" asserter category for the SailPoint case (weak signal), (b) a pre-litigation title-perfection assignment recorded 2021-12-03 immediately before the late-2021 W.D. Tex./Delaware complaints (weak signal), and (c) a broad multi-defendant assertion campaign (Box, Dropbox, SailPoint) that drew a Unified Patents IPR. Against that, the counter-evidence is substantial: the patent never left the inventor-founded company, and Box/Dropbox are plausibly direct competitors in the enterprise file-sync space Topia's products historically targeted — which would support an operating-company-assertion reading if current product shipments were verified, which I could not do. Because no single strong signal exists and the strongest indicators are the Stanford classification plus litigation timing, "moderate confidence" is the most defensible call.

Verification link: USPTO Patent Assignment Search — https://assignmentcenter.uspto.gov/ (search by patent number 10067942) and https://assignment.uspto.gov/patent/index.html. If the Assignment Center abstract confirms only the two inventor→Topia conveyances and no third-party transfers, the NPE-moderate reading should be downgraded and the "operating-company assertion / insufficient data" branch reconsidered.

I'll research the prior art citations for US 10067942, starting with the patent's cited references and their specifics.

The patent text is confirmed. Now let me research the most relevant cited prior art references in detail, starting with the strongest file-synchronization candidates.

I have strong details on the FusionOne references. Let me now research the IPR proceedings to see which references were actually asserted against this patent, plus a few more key cited references.

I've reached the search-step limit, so I'll now synthesize the analysis from the authoritative patent text (which contains the full 101-reference citation list) plus the live search results I obtained. I'll flag clearly where verification was and wasn't possible.

Verification notes first (per your strict rules)

• Patent number confirmed: US10067942B2 ("Architecture for management of digital files across distributed network"), Appl. 14/860,289, continuation of US 12/267,852 → US 9,143,561, priority 2007-11-09 (Provisional 60/986,896), granted 2018-09-04. Confirmed via the Google Patents record supplied as authoritative and cross-checked in live results (Justia assignee pages, FreePatentsOnline, Docket Alarm).
• No direct USPTO Patent Public Search/Patent Center query could be completed in my budget; the citation list below comes from the patent's own "Citations (101)" section (authoritative for what the examiner/third parties cited) and live search results for the individual references. If a direct USPTO file-wrapper query is needed to see which references the examiner actually applied to which claims, that remains outstanding.
• IPR context (live search): IPR2023-00433, Box, Inc. et al. v. Topia Technology, Inc., filed 2023-01-04, institution 2023-08-04, Final Written Decision 2024-08-01, status "Final Written Decision – Appealed" (Tech Center 2100, Art Unit 2157; judges Powell, Boudreau, Kenny, Giannetti, Chung, Hudalla). I could not retrieve the petition's asserted-reference list or the FWD's specific findings before hitting the step limit — that document is the single best source for "most relevant prior art" and should be pulled if available to you.

Claim elements used for the anticipation mapping

Claim 1 (independent, system) and Claim 10 (independent, method) require:

1. First electronic device (hub) running a first application;
2. Second device running a second application, storing a first electronic file;
3. User modifies the first file → second application automatically transfers the modified file/copy to the first device;
4. First application determines whether it is in communication with a third device;
5. First application automatically sends the modified first-file copy to a third application on the third device (responsive to both receipt and the communication determination);
6. Mirror-image flow for a second file modified on the third device → first device → second device;
7. On delivery, the older version is automatically replaced "in lieu of" the new copy on the recipient device (both directions).

Dependent claims: 2/11 (mobile-agent runtime environment in second/third application); 3–5/12–14 (storing the modified first-file copy on first-device memory; in lieu of an older cached copy; stored when first device is not in communication with the third device); 6/15 (automatic transfer to the third device on resuming communication); 7–9/16–18 (second application creates a mobile object → proxy object at the first device → proxy receives/stores the copy).

Tier 1 — Closest references (potentially anticipate claims 1 and/or 10)

These are the cited references that most fully disclose multi-device, change-triggered, hub-mediated file synchronization with replacement of stale data. For each: full citation, dates, description, and claim assessment.

1. EP 1130511 A2 — FusionOne, Inc., "Data transfer and synchronization system"

   • Priority: 2000-01-25; published 2001-09-05.
   • Description (verified live via EPO GPI and Google Patents): System with a first sync engine on a first system producing difference information; a network-coupled data store; a second sync engine on a second system receiving the difference information and updating the second system's data; an optional management server; and a plurality of sync engines on a plurality of systems. The disclosed method: determining difference data from changes to a first file on a first system; transmitting to a server; querying from a second system; retrieving; and updating the second file.
   • § 102 mapping: Strongest single-reference candidate for claims 1 and 10 — discloses user-associated devices, change detection, automatic propagation to a central node, and updating (i.e., effectively replacing) the older file content on the receiving device. The explicit "determining whether in communication" and "stored in lieu of the older version" limitations are the main gaps (update-by-difference arguably satisfies "in lieu of" only by argument).

2. US 6,757,696 B2 — FusionOne, Inc., "Management server for synchronization system"

   • Filed 2001-01-02 (continuation of 09/490,550 filed 2000-01-25); granted 2004-06-29. (Priority 2000-01-25 in the citation list.)
   • Description (verified live): A controller/management server with an authentication module identifying the user, and a synchronization manager communicating with at least one interactive agent to control data migration between a first and a second network-coupled device; storage server holding transaction-based user data; both pull and push synchronization flows (Figs. 15–16).
   • § 102 mapping: Potentially anticipates claims 1 and 10 (user-authenticated hub controlling data migration between multiple user devices; push-sync embodiment). Same in-lieu-of/communication-determination gaps as EP 1130511.

3. US 6,611,849 B1 — PalmSource, Inc., "System for synchronizing databases on multiple devices utilizing a home base"

   • Filed 2000-09-29; granted 2003-08-26.
   • Description: Multi-device database synchronization through a "home base" computer; devices sync their databases with the home base when connected, using change logs, so each device converges to the same data.
   • § 102 mapping: Potentially anticipates claims 1, 10, and 6/15 — the home-base hub model maps to the first device, and deferred sync-on-reconnect maps to claim 6/15. Gaps: explicit "responsive to user modification" automatic transfer and the "in lieu of" replacement language.

4. US 6,810,405 B1 — Starfish Software, Inc., "System and methods for synchronizing data between multiple datasets"

   • Filed 1998-08-18; granted 2004-10-26.
   • Description: TrueSync-style synchronization engine that reconciles multiple datasets across devices by exchanging change information; supports bi-directional synchronization among more than two datasets.
   • § 102 mapping: Potentially anticipates claims 1 and 10 for the multi-dataset, multi-device sync core; automatic change-driven transfer is present in the change-information exchange model.

5. US 2007/0014314 A1 — BellSouth Intellectual Property Corporation, "Peer-to-peer synchronization of data between devices"

   • Filed 2005-07-13; published 2007-01-18 (before the 2007-11-09 critical date — true § 102(a)/(b) prior art).
   • Description: Peer-to-peer synchronization of data between devices with detection of data changes on one device and propagation to other devices.
   • § 102 mapping: Potentially anticipates claims 1 and 10; the hub device in the '942 claims can be argued to be the peer coordinating the other two. Published pre-critical-date, so no § 102(e)/103 priority-date complications.

6. US 7,552,166 B2 — Visto Corporation, "System and methods for asynchronous synchronization"

   • Filed 2001-11-15; granted 2010-07-06.
   • Description: Asynchronous synchronization of user data among multiple devices through a server; changes are queued and delivered when devices connect; reconciliation on reconnect.
   • § 102 mapping: Potentially anticipates claims 1, 10, 6, and 15 (asynchronous delivery when the target device becomes reachable is squarely the "resuming communication → transfer" concept).

7. US 7,761,414 B2 — [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.), "Asynchronous data synchronization amongst devices"

   • Filed 2007-01-07 (before the 2007-11-09 critical date; granted 2010-07-20 → § 102(e) prior art).
   • Description: Asynchronous synchronization of data among multiple devices, propagating changes between devices with conflict/change tracking.
   • § 102 mapping: Potentially anticipates claims 1 and 10 as § 102(e) art; publication post-dates the critical date, so effective prior-art date analysis (filing date 2007-01-07) is the linchpin.

8. US 8,370,423 B2 — Microsoft Corporation, "Data synchronization and sharing relationships"

   • Filed 2006-06-16; granted 2013-02-05 (§ 102(e) prior art).
   • Description: Synchronization of data with defined sharing relationships among multiple devices, propagating changes along relationship graphs.
   • § 102 mapping: Potentially anticipates claims 1 and 10, including the three-device relationship topology; the "in lieu of" replacement of stale copies is inherent in sync-along-relationship propagation.

9. US 8,386,558 B2 — Microsoft Corporation, "Cross-pollination synchronization of data"

   • Filed 2004-02-04; granted 2013-02-26 (§ 102(e) prior art).
   • Description: "Cross-pollination" sync in which changes made on one device are propagated to other devices even when the devices use different applications, via a sync service.
   • § 102 mapping: Potentially anticipates claims 1 and 10; automatic propagation of a modified file's copy to other devices is the core disclosure.

10. US 7,340,534 B2 — Sun Microsystems, Inc., "Synchronization of documents between a server and small devices"

    • Filed 2002-03-05; granted 2008-03-04.
    • Description: Synchronization of documents between a server and small (mobile/handheld) devices, including transfer of updated documents to the devices.
    • § 102 mapping: Potentially anticipates claims 1 and 10 for server-mediated document sync; the three-device relay and communication-determination steps are the gaps.

11. US 2002/0087588 A1 — Stephen Larry McBride, "Method and apparatus for automatically synchronizing data from a host computer to two or more backup data storage locations"

    • Filed 1999-04-14; published 2002-07-04.
    • Description: Automatic synchronization of data from a host to two or more backup storage locations, with change detection on the host.
    • § 102 mapping: Potentially anticipates claims 1 and 10 for the host-fan-out topology; the "user modifies file on a non-hub device → hub → other device" directionality differs and is the principal gap.

12. US 6,463,463 B1 — Research In Motion Limited, "System and method for pushing calendar event messages from a host system to a mobile data communication device"

    • Filed 1998-05-29; granted 2002-10-08.
    • Description: Event-driven "push" of data items from a host system to a mobile device when data changes, over a wireless network.
    • § 102 mapping: Potentially anticipates the "automatically transfer responsive to modification" element of claims 1 and 10, and supports the triggering concepts; alone it lacks the full three-device relay.

13. US 6,700,821 B1 — Visto Corporation, "System and method for globally and securely accessing unified information in a computer network"

    • Filed 1996-12-13; granted 2004-03-16.
    • Description: Unified, secure access to a user's information across multiple devices via a network service that maintains a consistent copy.
    • § 102 mapping: Potentially anticipates claims 1 and 10 for the "one user, many devices, consistent copy" model.

14. US 6,505,200 B1 — IBM, "Application-independent data synchronization technique"

    • Filed 2000-07-06; granted 2003-01-07.
    • Description: Application-independent synchronization technique that detects data changes and propagates them between devices without application-specific logic.
    • § 102 mapping: Potentially anticipates claims 1 and 10 for generic file-level change propagation.

15. US 7,269,433 B2 — Microsoft Corporation, "Scheduling of synchronization operation on a mobile device based on predetermined subset of user actions"

    • Filed 2002-11-05; granted 2007-09-11.
    • Description: Sync operations scheduled/triggered by a predetermined subset of user actions (e.g., save/close of a document).
    • § 102 mapping: Most relevant to the "responsive to the user modifying a content of the file" trigger in claims 1 and 10 (the specification's own triggering events — save, elapsed time, session re-initiation — track this reference's teaching).

16. US 7,024,428 B1 — Openwave Systems Inc., "Reliable data synchronization over unreliable networks"

    • Filed 2001-02-23; granted 2006-04-04.
    • Description: Reliable sync with queuing and retry when network connectivity is lost or intermittent.
    • § 102 mapping: Potentially anticipates claims 5–6/14–15 (store locally when not in communication; transfer on resuming communication), in combination with a Tier-1 sync reference; alone it lacks the three-device topology.

17. US 2004/0172424 A1 — Microsoft Corporation, "Method for managing multiple file states for replicated files"

    • Filed 2003-02-28; published 2004-09-02.
    • Description: Managing multiple states of replicated files (e.g., local edits vs. replicated versions) and resolving which version is authoritative.
    • § 102 mapping: Most relevant to the "older version … replaced … in lieu of" limitations of claims 1 and 10 (the replacement-of-stale-replica concept).

18. US 7,584,186 B2 — Microsoft Corporation, "System and method for resolving conflicts detected during a synchronization"

    • Filed 2001-06-27; granted 2009-09-01.
    • Description: Conflict detection and resolution during synchronization of replicated data.
    • § 102 mapping: Supports the replacement-of-stale-version analysis; secondary to the Tier-1 references.

19. US 7,587,446 B1 — FusionOne, Inc., "Acquisition and synchronization of digital media to a personal information space"

    • Filed 2000-11-10; granted 2009-09-08.
    • Description: Synchronization of digital media into a user's personal information space across devices.
    • § 102 mapping: Potentially anticipates claims 1 and 10 for user-centric multi-device sync; same family lineage as EP 1130511/US 6,757,696.

20. US 7,895,334 B1 — FusionOne, Inc., "Remote access communication architecture apparatus and method"

    • Filed 2000-07-19; granted 2011-02-22.
    • Description: Remote access architecture for synchronizing/accessing user data across devices.
    • § 102 mapping: Potentially anticipates claims 1 and 10.

21. US 8,112,549 B2 — Yahoo! Inc., "Alert mechanism for notifying multiple user devices sharing a connected-data-set"

    • Filed 2005-07-14; granted 2012-02-07.
    • Description: Notifying multiple user devices that share a connected data set when the data set changes.
    • § 102 mapping: Relevant to claims 1 and 10 for the multi-device, same-user, change-notification topology.

22. US 2002/0026478 A1 — Edward B. Rodgers, "Method and apparatus for forming linked multi-user groups of shared software applications"

    • Filed 2000-03-14; published 2002-02-28.
    • Description: Linked groups of shared software applications with shared data access among devices.
    • § 102 mapping: Secondary candidate for claims 1 and 10.

23. US 6,829,622 B2 — Siemens, "Apparatus and method for mobile device synchronization" (filed 2001-07-27; granted 2004-12-07); US 6,874,037 B1 — Sony, "Method and apparatus for synchronizing device information" (filed 2000-06-19; granted 2005-03-29); US 2006/0189348 A1 — Memory Matrix, "Automatic synchronization of cellular telephones" (filed 2005-02-23; published 2006-08-24); US 2008/0288578 A1 — Nokia, "Method, a Device, and a System for Enabling Data Synchronization Between Multiple Devices" (filed 2004-04-01; published 2008-11-20); US 2009/0013009 A1 — Nakayama, "Using differential file representing differences…" (filed 2007-07-02; published 2009-01-08).

    • These are mid-tier multi-device/differential sync references; each could contribute to claims 1/10 elements (esp. change detection and differential propagation) but none alone is as complete as the Tier-1 set.

Tier 2 — Relevant to dependent claims

Claims 2/11 and 7–9/16–18 (mobile-agent runtime; mobile object → proxy object):

• US 7,224,973 B2 — NEC Corporation, "Communication agent apparatus" (filed 2004-03-26; granted 2007-05-29) — agent-based communication apparatus; the closest listed citation to the mobile-agent concept, but it does not clearly disclose a mobile object creating a proxy object at the hub that stores the file copy. This is the weakest area of the cited art, which is consistent with these dependent claims being the most robust.
• Note: the specification incorporates by reference Topia's own U.S. Application 11/739,083, "Electronic File Sharing" for the mobile-agent transfer concepts — that is not a § 102 reference against this continuation (same owner/family), but it is where the mobile-object/proxy-object teaching actually lives.

Claims 3–6/12–15 (local caching; offline storage; transfer on reconnect):

• US 7,024,428 B1 (Openwave), US 7,552,166 B2 (Visto), US 6,611,849 B1 (Palm home base), and US 2002/0087588 A1 (McBride) — each discloses storing/queuing updates when a target is unreachable and delivering on reconnect.

Trigger-on-modification element (claims 1/10):

• US 7,269,433 B2 (Microsoft) and US 6,463,463 B1 (RIM push) are the most on-point for "automatically … responsive to the user modifying."

Tier 3 — Cited but lower relevance (listed for completeness)

The remaining citations in the '942 list are primarily background: version-management systems (US 5,600,834 A Mitsubishi, "reconciling different versions of a file"; US 5,806,078 A Softool; US 6,449,624 B1 Fisher-Rosemount), delta/differential update systems (WO 98/56149 A1 Ericsson; US 5,909,581 A Samsung; US 2005/0097225 A1; US 2007/0027936 A1; US 2009/0013009 A1), proxy-client backup (US 6,026,414 A IBM), distributed file systems and clustered filesystems (US 2003/0028514 A1; US 2003/0078946 A1; US 2004/0107225 A1), software updating (US 2003/0028542 A1; US 2004/0158817 A1), P2P file sharing (US 2008/0005114 A1 Microsoft; WO 2007/047302 A2 Qualcomm; US 2005/0091316 A1), media sync (US 2008/0086494 A1 Apple), backup (US 2007/0100913 A1), and user-authentication/security items (US 7,415,615 B2). None of these plausibly anticipates claims 1 or 10 standing alone, and none maps to the mobile-agent dependent claims. The full 101-reference list is in the patent record if you need every entry itemized.

Special note — US 9,143,561 B2 (Topia): Listed as a citation but is the parent of the '942 continuation (same inventor/assignee, same disclosure). It is not § 102 prior art against the '942 claims (not a "prior" patent by a different inventive entity, and the '942 claims are substantively the same as those examined in the parent). It appears in the list for family/continuity reasons only.

Bottom line

• Strongest § 102 anticipation candidates for claims 1 and 10: EP 1130511 A2 (FusionOne), US 6,757,696 B2 (FusionOne), US 6,611,849 B1 (Palm home base), US 6,810,405 B1 (Starfish), US 2007/0014314 A1 (BellSouth), US 7,552,166 B2 (Visto), US 8,370,423 B2 and US 8,386,558 B2 (Microsoft), and US 7,761,414 B2 (Apple, via § 102(e)).
• Best support for the "in lieu of older version" limitation: US 2004/0172424 A1 (Microsoft) and US 7,584,186 B2 (Microsoft).
• Best support for the modification-trigger element: US 7,269,433 B2 (Microsoft) and US 6,463,463 B1 (RIM).
• Best support for offline-store/reconnect-transfer (claims 5–6/14–15): US 7,024,428 B1 (Openwave), US 7,552,166 B2 (Visto), US 6,611,849 B1 (Palm).
• Mobile-agent dependent claims (2, 7–9, 11, 16–18): thinly supported in the cited art; US 7,224,973 B2 (NEC) is the closest listed citation, and the operative teaching is in the incorporated Topia application 11/739,083.

Caveats: (1) This is an analytical mapping to the claim language, not a legal anticipation conclusion — a proper § 102 analysis requires reading each reference's full disclosure against every claim limitation, which I could not do for all 101 references within the search budget. (2) The examiner's actual rejections (which references were applied to which claims) and the IPR2023-00433 Final Written Decision's findings would be the authoritative "most relevant prior art" determinations; I confirmed the IPR's existence and FWD date via live search but could not retrieve the FWD's reference-specific findings. (3) I could not complete a direct USPTO Patent Public Search/Patent Center query, so everything above rests on the Google Patents record and the live secondary sources cited.

Obviousness Analysis — U.S. Patent 10,067,942 (US10067942B2)

Scope and method

This analysis evaluates whether claims 1–18 of US10067942B2 ("the '942 patent") would have been obvious under 35 U.S.C. § 103 to a person having ordinary skill in the art (PHOSITA) as of the relevant time. I rely on (a) the prior art identified in the patent's own Citation/Family-Cites records (the "Prior Art section of this page"), and (b) the actual inter partes review record for this patent and its parent, which — per live search results — is the strongest available evidence of how these claims read on the prior art. Per the operating rules, where search results and my prior knowledge conflicted, I treated the search results as ground truth.

Key procedural context from live search (ground truth):

• IPR2023-00433 — Box, Inc. & Dropbox, Inc. v. Topia Technology, Inc., challenging this exact patent (10067942): filed Jan. 4, 2023; instituted Aug. 4, 2023; Final Written Decision Aug. 1, 2024. Per the CAFC oral-argument transcript in Topia Technology, Inc. v. Box, Inc. (Fed. Cir. No. 24-2219), the Board found "all challenged claims were obvious" under "two independent grounds" and "under both constructions," including on "the Sigurdsson and Chappelle [Shappell] grounds."
• IPR2023-00427 — companion petition against the parent patent (9,143,561), challenging claims 1, 3, 4, 8, 10, 11 on: Ground 1: Sigurdsson (US 2007/0174246 A1) + Shappell (US 2005/0091289 A1) and Ground 2: Brown (US 7,035,847 B2) + Hesselink (US 2005/0120082 A1). The '942 patent's claims 1–18 are continuations of the same disclosure, and the CAFC transcript confirms the same two-ground structure was applied to the '942 patent in IPR2023-00433.
• I could not retrieve the full IPR2023-00433 Final Written Decision text within my search budget; the description of its grounds below is inferred from the companion IPR2023-00427 record and the CAFC transcript and should be verified against the FWD before any legal reliance.

The claimed invention, distilled

Independent claim 1 (system) and claim 10 (method) require a three-device, user-associated synchronization architecture in which:

1. A first electronic device runs a first application (the hub);
2. A second device runs a second application and stores a first file; automatically transmits a copy of the modified file to the first device responsive to the user modifying its content;
3. The first application determines whether it is in communication with a third device and, if so, automatically sends the modified first-file copy to the third device;
4. The identical flow runs in reverse for a second file (third device → first device → second device); and
5. On delivery, the recipient device's older version is automatically replaced so the modified copy is stored "in lieu of" the older version.

Dependent claims add: a mobile-agent runtime environment in the second/third application (claims 2, 11); local storage of the copy on the first device, including storage "in lieu of" an older cached copy and storage while the third device is offline (claims 3–5, 12–14); deferred transfer upon resumption of communication (claims 6, 15); and a mobile object creating a proxy object at the first device that receives and stores the file (claims 7–9, 16–18).

PHOSITA

A PHOSITA would be a designer/engineer with a bachelor's degree in computer science or equivalent, and 2–4 years of experience in distributed systems, file synchronization, client-server architectures, and networked data management, familiar with synchronization protocols (e.g., Palm HotSync, Microsoft ActiveSync, GoodLink, FusionOne-style sync servers) and mobile-agent/proxy design patterns. This profile is consistent with the technical center (TC 2100) and the prior art of record.

Combination 1 — Sigurdsson (US 2007/0174246 A1) in view of Shappell (US 2005/0091289 A1)

This is the primary ground asserted in IPR2023-00427 (parent) and, per the CAFC transcript, one of the two grounds on which the Board found the '942 claims obvious in IPR2023-00433.

What Sigurdsson teaches (claim mapping)

Sigurdsson discloses a client-server system for synchronizing files across a single user's multiple devices — e.g., home computer, work computer, and mobile device. Its server (Server 106) acts as a "drop-box": it receives a modified file pushed from one client device and transfers it to another client device, including storing the file when the destination is offline and delivering it when the destination reconnects — exactly the "determine whether in communication … store … resume communication … transfer" logic of claims 1/10 elements and dependent claims 3–6 and 12–15.

What Shappell adds

Shappell (US 2005/0091289 A1) teaches an "automatic replication" feature in a file-synchronization system: upon receiving notification of a file modification, a receiving machine automatically removes the local, out-of-date copy and obtains/installs the updated version. This maps directly onto the "automatically caused to be replaced … in lieu of the older version" limitation that is the crux of independent claims 1 and 10.

Motivation to combine (KSR)

• Same field, known problem: Both references are in the art of file synchronization among a user's devices. Sigurdsson itself raises the concern of limited memory/data storage on its server; a PHOSITA would look to known techniques for managing outdated file versions on client devices.
• Predictable improvement: Shappell's automatic-replacement technique would predictably prevent accumulation of stale copies on the receiving device and ensure the user always has the latest version — directly serving Sigurdsson's synchronization goal. Combining a known replacement mechanism into a known sync architecture is a textbook "combination of familiar elements according to known methods … yielding predictable results" (KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 416 (2007)).
• Reasonable expectation of success: Implementing Shappell's replacement logic in Sigurdsson's client-server architecture is a straightforward integration of two known components in the same field.
• The PTAB so found: In IPR2023-00427 the Board (per the record) credited essentially this reasoning, and per the CAFC transcript the Board found all challenged '942 claims obvious on the Sigurdsson/Shappell ground under both proposed claim constructions.

Coverage of dependent claims under Combination 1

• Claims 3–5 / 12–14 (local storage at first device, "in lieu of" replacement of a cached copy, offline storage): taught by Sigurdsson's drop-box/offline handling combined with Shappell's replacement teaching.
• Claims 6 / 15 (transfer upon resuming communication): expressly taught by Sigurdsson's store-and-forward when the destination is offline.
• Claims 2 / 11 (mobile-agent runtime) and 7–9 / 16–18 (mobile object → proxy object → storage): see Combination 3 below; these were also the subject of separate analysis in the IPR (challenged claims in the parent included 8 and 11, i.e., the proxy-object and mobile-runtime claims, suggesting the petitioner mapped them onto Sigurdsson/Shappell and/or the secondary references).

Combination 2 — Brown (US 7,035,847 B2) in view of Hesselink (US 2005/0120082 A1)

Second ground asserted against the family; per the CAFC transcript, the Board found all challenged '942 claims obvious on this ground as well.

What Brown teaches

Brown discloses a client-server system that bidirectionally synchronizes files between a user's multiple client devices (e.g., desktop 130 and laptop 135) through a common central server (105), monitoring for file changes to keep files current at each client, and expressly stating that "any scheduling algorithm" can be used to initiate synchronization. Brown's default initiation is periodic or manual — the gap Hesselink fills.

What Hesselink adds

Hesselink teaches a synchronization system that transmits changes "as soon as the update has been performed" — e.g., each time the user saves — so that all connected devices are updated concurrently and immediately. This supplies the claim limitation that the modified-file copy is automatically transferred "responsive to the user modifying a content of the first electronic file" (claims 1/10), and the analogous "responsive to … modifying" triggers throughout.

Motivation to combine

• Brown's own stated goal is "maintaining currency at each client as changes are made," and it expressly leaves the scheduling algorithm open ("any scheduling algorithm"). Substituting Hesselink's event-driven, save-triggered push for periodic polling is a predictable design choice within Brown's own teaching.
• Hesselink provides an express rationale: saving user time and avoiding the problems of stale versions — the same objectives as Brown and the '942 patent's background (which criticizes latency and uncertainty about whether a remotely accessed file is current).
• High expectation of success: the modification is confined to Brown's sync trigger, and Brown already contemplates transferring whole files or deltas.
• The Board (per the companion record and CAFC transcript) found this combination sufficient under both claim constructions.

Combination 3 — Hub-and-spoke synchronization art of record (the patent's own "Prior Art section") + trigger/replacement/proxy references

Even setting aside the IPR-proven combinations, the '942 claims are obvious over the prior art cited on the face of the patent, which documents that every element was well known in the art by 2007.

Primary hub-and-spoke sync references (from the patent's Citations)

• US 6,611,849 B1 (Palm) — "System for synchronizing databases on multiple devices utilizing a home base": a hub ("home base") that synchronizes multiple user devices — the three-device hub architecture of claims 1/10.
• EP 1,130,511 A2 / US 6,757,696 B2 (FusionOne) — "Data transfer and synchronization system" / "Management server for synchronization system": a server that manages synchronization of a user's multiple devices, including storing data for offline devices.
• US 6,810,405 B1 (Starfish) — synchronizing data between multiple datasets.
• US 6,708,221 B1 (Visto) — globally and securely accessing unified information across a user's devices via a network.
• US 6,990,522 B2 (Microsoft) — synchronizing objects between two devices.
• US 2008/0086494 A1 (Apple) and US 7,761,414 B2 (Apple) — transfer/synchronization of media data among a user's devices.
• US 7,243,163 B1 (Good Technology) — full wireless synchronization of a data processing apparatus.
• US 6,671,700 B1 and US 7,155,488 B1 (Palm) — conduit-based and two-handheld synchronization.

These references collectively teach: multiple user-associated devices; a hub/server application that receives modified files and forwards them to other devices; automatic synchronization; and offline store-and-forward. The automatic, modification-triggered push is taught by US 7,269,433 B2 (Microsoft) — "Scheduling of synchronization operation on a mobile device based on predetermined subset of user actions" (sync triggered on user actions such as saving a file) — and by Apple's US 2008/0168526 A1 (prioritized data synchronization with a host device).

Replacement "in lieu of" (the key limitation)

• US 5,600,834 A (Mitsubishi) — reconciling different versions of a file, including replacing an older version with the newer one.
• US 5,806,078 A (Softool) — version management system that maintains and installs current versions.
• US 2004/0172424 A1 (Microsoft) — "Method for managing multiple file states for replicated files" (managing which replicated state is current).
• US 7,584,186 B2 (Microsoft) — resolving conflicts detected during synchronization and updating replicas to the current version.

A PHOSITA combining any of the hub-spoke sync primaries with any of these version-replacement teachings would arrive at the full independent-claim combination with the same motivation articulated in Combination 1: ensure recipients always hold the latest version and avoid stale-copy confusion — the very problem the '942 specification says the prior art suffered from.

Dependent claims — mobile-agent runtime and proxy object (claims 2, 7–9, 11, 16–18)

• Mobile-agent runtime (claims 2, 11): The '942 specification itself concedes these concepts are known ("An embodiment … leverages remote programming concepts by utilizing processes called mobile agents … sometimes referred to as mobile objects or agent objects") and describes the runtime environments as optional ("may, but need not, include"). US 7,224,973 B2 (NEC) — "Communication agent apparatus" — is cited in the patent and teaches mobile-agent runtime environments for networked communication. Mobile-agent platforms (e.g., IBM Aglets, Telescript) were standard by 2007. At minimum, providing the sync client with a known mobile-agent runtime is an obvious design choice.
• Proxy object (claims 7–9, 16–18): US 6,026,414 A (IBM) — "System including a proxy client to backup files in a distributed computing environment" — is cited in the patent and teaches a proxy client that acts on behalf of a remote source to store files on a local machine. That is precisely the claimed proxy-object pattern: a first mobile object creates a proxy object at the first device, the proxy receives the modified file copy, and the proxy stores it on the first device's memory. Using a proxy to decouple a remote agent's execution from local storage was a well-known distributed-systems design pattern.

Claim-by-claim summary table

Motivation-to-combine synthesis

Under KSR's expansive obviousness framework, all three combinations satisfy § 103:

1. Same field / analogous art: All references are in file synchronization, distributed data management, or network file access — the same field as the '942 patent.
2. Known problem, known solution: The '942 patent's own Background identifies the problem (stale/duplicate versions across a user's devices, offline access, latency) and every element of its solution — hub-based sync, modification-triggered push, offline store-and-forward, automatic replacement, proxy/mobile-agent patterns — was individually known and, in most cases, cited by the examiner on the face of the patent.
3. Predictable combination: Combining a trigger mechanism (Hesselink; Microsoft '433) with a hub architecture (Sigurdsson/Brown/Palm/FusionOne) and a replacement mechanism (Shappell; Mitsubishi '834) yields the claimed system without unexpected results.
4. Design incentives: Sigurdsson's own server-storage concern motivates adding Shappell's client-side replacement; Brown's "any scheduling algorithm" invitation motivates adding Hesselink's event-driven trigger.
5. PTAB corroboration: The Board instituted IPR2023-00433 against this patent and, per the CAFC record, issued a Final Written Decision finding all challenged claims obvious under both of the asserted grounds and under both proposed claim constructions. The CAFC appeal (No. 24-2219) was pending as of the search date; the appeal's existence does not undermine — and the oral-argument transcript affirmatively supports — the finding that the claims were shown obvious on the Sigurdsson/Shappell and Brown/Hesselink combinations.

Caveats and uncertainties

• I did not retrieve the full text of the IPR2023-00433 Final Written Decision; the precise grounds and claim scope challenged there are inferred from the companion IPR2023-00427 record (same petitioner, same family, overlapping claims) and the CAFC transcript. Verify against the FWD before legal reliance.
• The CAFC appeal No. 24-2219 had not produced a decision in my available search results; the analysis above addresses obviousness on the merits, not the appellate outcome.
• Secondary considerations (e.g., teaching away, unexpected results, commercial success) were argued by Topia in the IPR and appeal (including expert testimony of Dr. Chenoy); per the CAFC transcript, the Board addressed and rejected those arguments. A complete § 103 analysis for litigation would weigh any such evidence, but nothing in the available record indicates it overcame the strong prima facie case described above.

Bottom line: The independent claims are obvious over Sigurdsson + Shappell and over Brown + Hesselink — combinations the PTAB already found to render the family's claims unpatentable — and independently obvious over the hub-and-spoke, trigger, and version-replacement references cited on the face of the '942 patent. The dependent claims add known mobile-agent, proxy-object, offline-storage, and deferred-transfer features that are taught by the cited art (notably NEC '973 and IBM '414) and, in the case of mobile agents, admitted in the specification to be known.