US 7313580

The first search confirmed the patent record. The CAFC docket search returned nothing. Let me run additional targeted searches to check for USPTO assignment records, litigation, and any CAFC 2026 appeal involving this exact patent.

The CAFC search returned no results. Let me do two more targeted checks: the USPTO assignment database and the Utah case asserting this patent, to see whether any appeal has reached the CAFC.

Summary — US Patent 7,313,580 (US7313580B2)

Bibliographic data

• Title: Systems and methods for sharing information between a user group and associated document
• Patent number: US7313580B2 (application no. US 11/052,198)
• Filing date: February 8, 2005
• Issue date: December 25, 2007
• Inventors: Domenico Vellante; Vittorio Luigi Brioschi
• Original assignee: Individual (the application was filed by the individual inventors; no corporate assignee at filing)
• Current assignee (per Google Patents/assignment records): Ubqs IP LLC (Texas). Assignment chain per recorded legal events: Vellante → Vittorio Luigi Enrico Brioschi (recorded 2025-08-27, Reel/Frame 072126/0009) → UBQS-IP LLC (recorded 2026-01-13, Reel/Frame 073448/0258).
• Legal status: Expired – Lifetime (Google Patents lists adjusted expiration ~2026-03-26; maintenance fees were paid through the 12th year, small entity, May 2019).

Note: My direct query against the USPTO assignment database returned no usable snippet (the search tool returned empty). The assignment chain above comes from the legal-events table in the Google Patents record, which is consistent but not an independent USPTO confirmation.

Abstract (as published)

The invention connects a group of users involved in a common project; project information is stored in an electronic document. Each group member holds an exact copy of the document, and the method ensures the copies remain exact. Each user may incorporate modifications into his or her copy, which are later shared with the rest of the group after a synchronization stage. The sharing stages transfer modifications from a specific user to the rest of the group, avoiding a dedicated client-server structure.

Independent claims — plain-language overview

The patent has 20 claims. Only Claim 1 (method) and Claim 12 (electronic document) are independent. Claims 2–11 depend from Claim 1; Claims 13–20 depend from Claim 12.

Claim 1 (method of sharing information/synchronization): A method for sharing information among a group of users where the shared electronic document is stored in decentralized fashion — each user having his or her own copy and being able to make changes (adding or modifying information). The data-exchange/synchronization process comprises these stages:

1. Saving information to the local storage unit, where the newly added or modified resources are also written into an information "packet" placed in a spooler (outgoing waiting area).
2. Issuing a synchronization order that encodes, packages, and sequences the data so it can be handled by the transport mechanism.
3. Sending all spooled, encoded packets from the computer that issued the synchronization order to each of the other computers on the group's user list.
4. Receiving the packets at the other computers, decoding them back into resource packets, and incorporating them into the recipients' document copies according to the sender's sequence numbers.
5. Generating the resources needed to update the document from the decoded packet.
6. Transferring the updated document to the information manager so that, once every user has synchronized, all users hold an exact copy of the updated document.

Claim 12 (the shared electronic document): The electronic document to be shared according to the method of any preceding claim, containing at least one of:

• a group identifier;
• a list of users making up the group;
• a viewing structure enabling exact reproduction of the document for all users;
• the set of objects contained in the document; and
• storage space.

Litigation / docket search results (as of search date)

• USPTO database: The patent record is confirmed (Google Patents / Justia / FreePatentsOnline all show the same title, dates, and claims). I did not obtain an independent USPTO full-text or assignment-database result directly; the bibliographic data above is from the authoritative Google Patents record supplied in the prompt.
• CAFC 2026 dockets: No CAFC docket entries were found for patent 7313580. Searches for CAFC 2026 appeals involving this number returned no results.
• District court (2026): The patent is currently being asserted by UBQS-IP LLC in district court cases filed April 8, 2026, all under 35 U.S.C. § 271 (patent infringement), with no appellate activity found yet:
  • UBQS-IP, LLC v. Notion Labs, Inc. — SDNY, No. 1:26-cv-02878 (Judge John P. Cronan)
  • UBQS-IP LLC v. Dropbox, Inc. — SDNY, No. 1:26-cv-02875
  • UBQS-IP, LLC v. Atlassian Corporation — SDNY, No. 1:26-cv-02880 (Judge Paul A. Engelmayer)
  • A Utah District Court case, No. 2:26-cv-00251, is also listed on the Google Patents record.

Uncertainties

• I could not verify whether the specific patents asserted in the SDNY complaints include 7313580 (the AO-120 forms list the patents but the docket snippets did not enumerate them; the Google Patents "litigation" links associate 7313580 with these cases).
• I found no CAFC 2026 appeal for this patent; if an appeal exists, it was not indexed in the searches performed.
• Note a date inconsistency in the exercise: my environment states "Current Date: April 26, 2026," yet the retrieved court dockets include filings through June 2026. Per instructions, I treated the live search results as ground truth; if your date context is strict, the May–June 2026 docket entries would be prospective and should be treated cautiously.

Litigation Involving U.S. Patent 7,313,580

Based on searches of Unified Patents litigation data, Justia dockets, UniCourt, Ex Parte (AI-Lab), and the Google Patents record, U.S. Patent 7,313,580 ("the '580 patent") is currently being asserted in at least four district-court actions filed in April 2026 by its current assignee, UBQS-IP LLC (a Texas NPE; per Unified Patents, an entity of Pueblo Nuevo LLC). All identified actions are at the very early stages (service, extension-of-time to answer); none has progressed to a merits decision, and no CAFC appeal exists as of the search date.

Confirmed cases (S.D.N.Y., all filed April 8, 2026)

All three S.D.N.Y. actions plead 35 U.S.C. § 271 patent infringement, Nature of Suit 830. Plaintiff's counsel is the Law Office of David J. Hoffman. Atlassian is represented by Michael Frank Autuoro. The Ex Parte complaint analysis of the Dropbox action expressly identifies U.S. Patent No. 7,313,580 ("Systems and Methods for Sharing Information between a User Group and Associated Document," issued December 25, 2007) as the patent-in-suit, asserting all claims 1–20. The accused instrumentalities are collaborative document-editing systems (e.g., Dropbox's multi-user concurrent editing of a single page/post).

Case associated via the patent record but not independently docket-verified

The Google Patents record for the '580 patent links to a Utah District Court case, No. 2:26-cv-00251, and a June 24, 2026 Unified Patents article states that "UBQS-IP has sued Egnyte, Atlassian, Notion Labs, and Dropbox." That strongly suggests the Utah case is UBQS-IP LLC v. Egnyte, Inc. (or similar), but I could not independently confirm the defendant, judge, or docket for 2:26-cv-00251 in the searches I ran. Treat the defendant name as unverified.

Related non-court activity

• Unified Patents (June 24, 2026): announced that it is preparing a validity challenge (likely ex parte reexamination) against a UBQS-IP patent "generally related to a decentralized system allowing multiple users to edit the same document," in light of the suits against Egnyte, Atlassian, Notion Labs, and Dropbox. The article does not print the patent number, but the description and timing match the '580 patent. No PTAB/reexamination filing was found in my searches.
• No appellate activity: No CAFC docket entries for the '580 patent were found. Given the April 2026 filing dates and pending answers, an appeal is not yet possible.

Caveats

• Date discrepancy: My instructions set "Current Date: April 26, 2026," but live docket results include entries through June 2026 (e.g., the Notion extension order dated 5/19/2026 and the Unified Patents article dated 6/24/2026). Per the operating rules I treated the live search results as ground truth; the May–June 2026 entries would be prospective relative to April 26, 2026.
• Patent identification: All case identifiers above were matched literally to patent 7,313,580 via the Ex Parte complaint analysis and the Google Patents litigation links. One search result for "7313580" returned an unrelated French patent (FR7313580) and was disregarded.
• I was unable to retrieve the AO-120 forms for the S.D.N.Y. cases to enumerate all patents-in-suit, but the Dropbox complaint analysis independently confirms the '580 patent and claims 1–20.

Proceedings overview

Zero AIA trial proceedings exist on U.S. Patent 7,313,580. The USPTO Open Data Portal's PTAB trial list (the canonical source for this prompt) contains no IPR, PGR, or CBM involving the '580 patent, and web searches confirm no AIA trial has ever been filed — no petitions, no institution decisions, no Final Written Decisions, no settlements, no CAFC appeals from the Board. The breakdown is: 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denied. The defensive posture for a defendant is a clean slate on the PTAB side: every claim (1–20) is PTAB-untested, no IPR estoppel exists against any would-be petitioner, and the § 315(b) one-year bar clock has only just started running from the April 2026 complaints — meaning an IPR window is still open for the S.D.N.Y./Utah defendants (subject to the patent's March 2026 expiry, which limits but does not eliminate IPR utility and damages exposure). Separately, defensive-aggregator Unified Patents publicly announced (2026-06-24) a forthcoming validity challenge against a UBQS-IP patent matching this one — but as an ex parte reexamination, not an AIA trial — and no such filing had been docketed as of the search date.

Proceedings

There are no AIA trial proceedings to report. Nothing was found in the USPTO ODP structured data, PTAB E2E/P-TACTS results, or web sources under any variant of the patent number, the inventor names (Vellante/Brioschi), the current assignee (UBQS-IP LLC / Pueblo Nuevo LLC), or the asserted family (US20080040429A1, US20080098096A1, EP1854056A1, WO2006085214A1).

The closest public activity — which is not an AIA trial and must not be confused with one — is:

• Unified Patents, "UBQS-IP patent validity challenge coming soon" (2026-06-24): Unified announced it is using its Pearl prior-art tool to chart art against a UBQS-IP patent "generally related to a decentralized system allowing multiple users to edit the same document," in the wake of UBQS-IP's suits against Egnyte, Atlassian, Notion Labs, and Dropbox. Unified describes itself as "the top requester of ex parte reexaminations in recent years," and its UBQS-IP article does not print the '580 patent number or a reexamination control number. No ex parte reexamination filing (e.g., a Control No. 90/xxx,xxx) was located for the '580 patent in any search performed. URL: https://www.unifiedpatents.com/insights/2026/6/24/ubqs-ip-patent-validity-challenge-coming-soon

Strategic summary

Claim-level status. All 20 claims of the '580 patent — independent method claim 1, independent document claim 12, and dependents 2–11 and 13–20 — are UNTESTED before the PTAB. No claim has been canceled, no claim has been sustained, and no FWD exists. The only invalidity context to date is the district-court pleadings: the Dropbox complaint analysis (Ex Parte, 1:26-cv-02875) confirms UBQS-IP asserts claims 1–20 of the '580 patent, and the accused instrumentalities are multi-user concurrent document-editing systems. Because no AIA petition has been filed, there is no § 315(e)(2) estoppel binding anyone — no ground has been raised or "reasonably could have been raised" in any trial, so every § 102/§ 103/§ 112 ground remains available to any defendant.

Estoppel and timing landscape for today's defendants. For the four companies sued in April 2026 (Dropbox, Notion Labs, Atlassian in S.D.N.Y.; a fourth defendant in D. Utah No. 2:26-cv-00251, likely Egnyte per Unified's article), the § 315(b) one-year IPR bar runs from service of the respective complaints (service dates 2026-04-30 to 2026-05-04 in the S.D.N.Y. cases), so petitions would be timely if filed by roughly April–May 2027. Critical wrinkle: Google Patents lists the '580 patent as Expired – Lifetime with an adjusted expiration of 2026-03-26 (maintenance fees paid through the 12th year in 2019, but no 15th-year fee — i.e., the patent lapsed for non-payment before the April 2026 suits). An expired patent can still be challenged by IPR, but the practical stakes shift: no injunctive relief and damages only for pre-expiration conduct; the Board also has discretion in such circumstances, and petitioners should confirm whether the patent term expired before the accused conduct or whether the complaints plead pre-expiration infringement. Given the expiry, ex parte reexamination (Unified's announced route) and § 101/§ 112 district-court challenges are likely to be the more common levers than IPR.

Pattern signals. There is no pattern of repeat IPR petitioners — the patent has simply never been taken to the Board. The owner-side signal to note is the assignment-and-assertion chain: individual inventors → Vittorio Luigi Enrico Brioschi (2025-08-27) → UBQS-IP LLC, a Texas NPE entity of Pueblo Nuevo LLC (2026-01-13), which filed four coordinated district-court actions in April 2026 through the Law Office of David J. Hoffman. The presence of Unified Patents publicly flagging the patent for a reexamination-style challenge is the classic precursor to defensive-aggregator activity; a defendant should expect Unified (or another entity) to file the reexam imminently and should monitor the CRU docket rather than the PTAB trial docket.

Recommended next steps

1. If you are a defendant served in the 2026 actions: there is no PTAB FWD to cite because none exists. Do not let an adversary or a marketing memo tell you the patent is "IPR-hardened" — it is entirely untested, and the district-court complaints assert all claims 1–20 with no claim charting beyond the independent claim. Confirm whether the accused products and the alleged infringement period fall within the patent's enforceable life (expired/lapsed for non-payment as of 2026-03-26 per the assignment/legal-events record; note the record shows maintenance fees paid through the 12th year only). If all accused conduct post-dates lapse, that is a dispositive non-infringement/immunity argument independent of validity.
2. Monitor, don't file blind: watch the Unified Patents portal (https://portal.unifiedpatents.com) and the CRU for a reexamination control number matching the '580 patent; if Unified files, a defendant sued on the same patent can request parallel treatment or stay consideration. If you prefer an AIA trial, the § 315(b) clock runs from service (2026-04-30 through 2026-05-04 in S.D.N.Y.), so an IPR petition remains timely through roughly April–May 2027 — but weigh the cost/benefit against an expired patent, where a reexam or a district-court § 101/§ 112 motion may be faster and cheaper.
3. Verify the docket-verification gap: the D. Utah case (2:26-cv-00251) and the specific patents-in-suit in each S.D.N.Y. AO-120 form were not fully docket-verified in this analysis; before relying on any single case for estoppel or co-pendency analysis, pull the AO-120s and the Utah complaint to confirm the '580 patent (and which claims) are actually asserted in each action.

Caveat on the record: no PTAB proceeding, reexam filing, or CAFC appeal for the '580 patent was located as of the search date. The "challenge coming soon" item is a public announcement only; treat the existence of any filed reexam as unconfirmed. If a control number appears after this analysis, the ODP PTAB data and Unified's portal are the authoritative places to verify it.

The first searches didn't surface assignment records directly. Let me try targeted queries on the USPTO assignment database and the parties involved.

The Assignment Center is a JavaScript app that doesn't index well. Let me research the assignee entities and the attorney network behind them.

I've exhausted the search budget for this task, and the two primary sources I need — the USPTO Assignment Center (a JavaScript application that does not render in search) and the assignment record detail pages — did not return correspondent-level data in the retrievable index. Below is the ownership-chain reconstruction based on the records that are confirmed (the Google Patents legal-events table supplied in the patent record, which mirrors the USPTO assignment cover-sheet data), with correspondent names flagged as a verified gap rather than guessed.

Inventors

• Domenico Vellante (inventor 1). Employer at filing: not determinable from public record. The application was filed by the inventors personally ("Original Assignee: Individual" on the Google Patents record), with no corporate assignee of record at filing, so no employer assignment chain exists to trace. The PCT counterpart (WO2006085214A1, filed via IB2006) and the later recorded address of co-inventor Brioschi ("Italy") indicate an Italian origin for the invention.
• Vittorio Luigi Brioschi (inventor 2, full recorded name "VITTORIO LUIGI ENRICO BRIOSCHI, MR., ITALY"). Employer at filing: not determinable. Brioschi is the individual who received Vellante's interest in 2025 and then transferred the entire patent to UBQS-IP LLC in 2026.

Unusual pattern: Both inventors held their rights personally for ~18 years post-issue (2007–2025) with no company ever in the chain, then executed a two-step consolidation-and-exit in under five months (Vellante → Brioschi, Aug 2025; Brioschi → UBQS-IP LLC, Jan 2026). This is not the classic "inventors depart employer, portfolio fire-sale" pattern — there was no original corporate assignee at all — but the sudden late-life consolidation followed by transfer to a litigation LLC is itself the monetization tell.

Original assignee

• Entity on the issued patent: None — "Individual." Per the Google Patents record, the application was filed by the individual inventors (original assignee field: "Individual"), and the patent issued December 25, 2007 with no corporate assignee of record.
• Product / line of business: N/A — the original owners are the two inventors, not an operating company. Neither inventor is shown to have shipped a product embodying the claims.
• Current status of the original owners: Both have now assigned away their entire interest — Vellante to Brioschi (Reel 072126/0009, 2025-08-27) and Brioschi to UBQS-IP LLC (Reel 073448/0258, executed 2026-01-10, recorded 2026-01-13). Neither inventor retains an ownership interest as of the 2026 recording.

Assignment timeline

Two recorded assignments exist for US 7313580. Both are post-2025 and both are part of a single enable-litigation chain. No assignment was recorded at issuance (the patent issued to the inventors personally), and no assignment existed for the first 18 years of the patent's life.

• 2025-08-27 (effective/recorded) — Reel 072126/0009

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (see document for details)
  • Assignor: VELLANTE, DOMENICO, MR.
  • Assignee: BRIOSCHI, VITTORIO LUIGI ENRICO, MR. (Italy)
  • Correspondent: NOT RETRIEVED — the Assignment Center cover-sheet correspondent was not available in any indexed source; verify directly at assignmentcenter.uspto.gov before relying on this record for attorney-pattern analysis.
  • Context: Consolidation of the two inventors' interests into a single owner (co-inventor Brioschi) — the first step of a two-step transfer-to-asserter sequence executed months before litigation.

• 2026-01-10 (executed) / 2026-01-13 (recorded) — Reel 073448/0258

  • Conveyance: ASSIGNMENT OF ASSIGNOR'S INTEREST
  • Assignor: BRIOSCHI, VITTORIO LUIGI ENRICO, MR.
  • Assignee: UBQS-IP LLC (Texas)
  • Correspondent: NOT RETRIEVED — same caveat as above; single recurring-correspondent analysis cannot be completed without the cover-sheet data.
  • Context: Transfer of the entire patent from the individual inventor to a Texas LLC that Unified Patents identifies as an NPE and an entity of Pueblo Nuevo LLC — a transfer-to-asserter executed ~3 months before the first infringement complaints.

Plain-language finding on gaps: I could not confirm whether the Assignment Center shows any additional records (e.g., security interests, name corrections) beyond these two, and I could not retrieve the correspondent-of-record names from either reel because the Assignment Center is not crawlable and the searches returned no cover-sheet data. The two conveyances above are confirmed from the Google Patents legal-events table (reel/frame, parties, dates, conveyance type), which is consistent with — but not an independent copy of — the USPTO cover sheets. Pull reel 072126/0009 and 073448/0258 directly at https://assignmentcenter.uspto.gov/ to complete the correspondent field.

Timeline diagram

timeline
    title Ownership of US 7313580
    2005 : Filed by individual inventors
    2007 : Patent issued
    2025 : Vellante assigns to Brioschi
    2026 : Brioschi assigns to UBQS-IP LLC
         : UBQS-IP sues four tech companies

NPE / troll-pattern signals

1. Shell-entity transfer — present. Reel 073448/0258 (executed 2026-01-10, recorded 2026-01-13) moved the patent from an individual to UBQS-IP LLC, a Texas LLC whose name carries the "IP" suffix and whose only observable activity is litigation. The naming alone is not the finding; the finding is Unified Patents' independent identification of UBQS-IP as "an NPE and entity of Pueblo Nuevo LLC" (June 24, 2026, https://www.unifiedpatents.com/insights/2026/6/24/ubqs-ip-patent-validity-challenge-coming-soon) plus the absence of any product or practicing entity in the chain.

2. Known asserter in the chain — present. The chain terminates at UBQS-IP LLC, which Unified Patents — a defensive-aggregator with plaintiff-tracking data — expressly labels an NPE, and which filed coordinated § 271 suits against Dropbox (S.D.N.Y. 1:26-cv-02875), Notion Labs (1:26-cv-02878), Atlassian (1:26-cv-02880) on 2026-04-08, plus a D. Utah case (2:26-cv-00251). Justia's docket for the Notion action confirms the filings and plaintiff's counsel (David J. Hoffman). Ex Parte's party page lists UBQS IP LLC as a litigant with the '580 patent among its litigated patents.

3. Repeat correspondent across the chain — unclear / not verifiable from retrieved sources. The correspondent names on reels 072126/0009 and 073448/0258 were not retrievable in any indexed source (the Assignment Center is a JavaScript app). This is a flagged data gap, not a negative finding — with only two conveyances and both from individuals, a single-attorney recurrence would be a meaningful signal, but it cannot be confirmed or refuted here. Action item: look up both reel/frames at https://assignmentcenter.uspto.gov/ and compare the correspondent against the Law Office of David J. Hoffman (plaintiff's counsel in the 2026 SDNY suits).

4. Cascading transfers — present (short form). Two assignments executed 2025-08-27 (Reel 072126/0009) and 2026-01-10 (Reel 073448/0258) — under five months apart — consolidated inventor interests and then moved the patent to the asserting LLC. This is not a long multi-LLC daisy chain, but the temporal clustering and single-purpose trajectory (individuals → individual → litigation LLC → four complaints) is functionally a cascade arranged for assertion.

5. Pre-litigation transfer — present. The transfer to UBQS-IP LLC (executed 2026-01-10; recorded 2026-01-13, Reel 073448/0258) occurred under three months before the first infringement complaints naming the '580 patent were filed on 2026-04-08 (S.D.N.Y. 1:26-cv-02875/02878/02880; D. Utah 2:26-cv-00251). This is squarely within the six-month pre-suit window and indicates the chain was arranged to establish standing/venue for assertion.

6. Bankruptcy fire-sale — not present. No corporate bankruptcy is involved; the assignors are the individual inventors, and no Chapter 7/11 proceeding appears anywhere in the chain.

7. Privateering — not present. No operating company transferred the patent to an NPE to sue its competitors, and no SEC filing (10-K/8-K) context exists. The origin is individual inventors, not a practicing company.

8. Defensive aggregator (anti-NPE) — not present. The chain terminates at an asserting NPE, not at RPX, AST, LOT, Unified, or OIN. Inverse signal: Unified Patents is preparing a validity challenge against this UBQS-IP patent (announced 2026-06-24) — i.e., Unified is on the opposing side, and no Unified acquisition/neutralization of the patent exists.

Verdict

NPE — high confidence.

The chain is a textbook late-life monetization: the patent sat unassigned with its individual inventors for 18 years (2007–2025), was consolidated into one inventor (Reel 072126/0009, 2025-08-27), transferred to a Texas LLC that ships no products (Reel 073448/0258, executed 2026-01-10), and was asserted against four tech companies within three months of that transfer (complaints filed 2026-04-08). The decisive evidence is the external identification of UBQS-IP LLC as "an NPE and entity of Pueblo Nuevo LLC" by Unified Patents plus the pre-litigation timing of the transfer-to-LLC — two strong, independently supported signals. Correspondent-level confirmation remains outstanding; pull reels 072126/0009 and 073448/0258 at the USPTO Assignment Center (https://assignmentcenter.uspto.gov/) to complete the attorney-pattern picture.

I'll start by verifying the patent record for 7313580 and then research each of the eight listed citations.

Patent 7313580 confirmed. Now I'll research each of the eight cited references to build accurate profiles.

Now researching the remaining five cited references.

I've reached the search-step budget for this session, so I'll consolidate what was verified with an explicit confidence flag on each reference. I verified the three references that the '580 specification itself discusses (Zaplet, Estrada, IBM) in depth from live sources; the other five are analyzed from the authoritative citation list in the patent record (bibliographic data confirmed), with descriptions flagged as title-level only.

Prior-Art Analysis — U.S. Patent 7,313,580

0. Record confirmation (literal-number check)

US 7,313,580 B2 — "Systems and methods for sharing information between a user group and associated document," application US 11/052,198, filed 2005-02-08, granted 2007-12-25 (inventors Vellante/Brioschi). Confirmed against Google Patents, FreePatentsOnline, and Justia. No similar-number artifacts (e.g., FR7313580 or US 7,313,580's siblings US20080040429A1 / US20080098096A1) are treated as the target.

Governing statute: The '580 application was filed 2005-02-08 — pre‑AIA. Validity is assessed under pre‑AIA 35 U.S.C. § 102. The § 102(b) one-year statutory-bar date is 2004-02-08. References published/patented after that date can still qualify under § 102(a) (if before the invention date) and § 102(e) (US applications/patents by another filed in the US before the invention date). No earlier priority claim exists for the '580 (the PCT/EP/CA counterparts were filed 2006-02-07), so the invention date is presumed on/before 2005-02-08 for this analysis.

Claim map used below (from the granted text):

• Claim 1 (independent method): decentralized copies per user → local save writes changed resources as a packet in a spooler → synchronization order = encode/package/sequence for the transport manager → send all spooled packets from the syncing computer to each listed user's computer → recipients decode and incorporate packets in the sender's sequence into their copies → generate resources to update document → transfer to the information manager → identical copies after everyone syncs.
• Claims 2–3: group created by administrator; administrator grants privileges.
• Claims 4–7: transport agent = e-mail client (4); = OS point-to-point service (5); = daemon/shell (6); = kernel-provided resource (7).
• Claims 8–11: document = desktop (8); markup-language base (9); HTML web page (10); unipersonal use (11).
• Claim 12 (independent document claim): shared electronic document containing at least one of group identifier / user list / viewing structure / object set / storage space.
• Claims 13–20: parent-child objects (13); per-change author+time metadata (14); container objects (15); separate storage space (16); common storage with manager differentiation (17); desktop (18); markup language (19); HTML web page (20).

1. The eight patent citations — full profiles

(a) WO 2001052081 A1 — Zaplet, Inc. — Most relevant; likely the closest single reference to Claim 1's concept

• Full citation: WO 2001052081 A1, "Methods and systems to manage and track the states of electronic media," inventors Miller/Hanson/Axe/Evans, assignee Zaplet, Inc. Priority 1999-08-30 (per the Google Patents citation table; US-family priority traces to Zaplet's 1999–2000 filings, incl. provisional 60/176,230 of 2000-01-14); published 2001-07-19. US family members include US 6,453,337 B2 (2002-09-17) and US 6,871,216 B2 (2005-03-22).
• Verified description (live search): Discloses e-mail-transportable, dynamically updated electronic media ("zaplets") for group collaboration. A server stores the zaplet content and its state; participants open the zaplet from an e-mail message, and dynamic regions are "asynchronously updated in the server"; participants are notified of changes; content is stored in a server database and tracked/managed (restore, archive, supersede). It is the exact system the '580 specification's Background cites as a centralized (server-based) contrast.
• § 102 status: Published 2001-07-19 → squarely § 102(b) prior art (before 2004-02-08), and § 102(a).
• Claims potentially anticipated: Not Claim 1 as a whole — the disclosure is server-centric (single source of truth in a server database; clients retrieve state on "open action"), whereas Claim 1 requires per-user local copies, local save of only-changed resources into packets held in a spooler, and direct dispatch from the syncing computer to each other listed computer; Zaplet does not disclose the spooler/journal packet-sequencing machinery. Strongest § 102 showing is against the electronic document claim 12 (the zaplet is an electronic medium with user/participant addressing — i.e., a user list — plus objects and storage) and the e-mail-transport feature of claim 4. It also colorably reads on claims 2–3's group-of-participants/invitation concepts and claim 10/20's HTML-based content. Zaplet + a packetized-offline-sync reference is a natural § 103 combination against Claim 1.

(b) US 2003/0135565 A1 — Julio Estrada — Most relevant in the e-mail-collaboration field; applicant-cited

• Full citation: US 2003/0135565 A1, "Electronic mail application with integrated collaborative space management," inventor Julio Estrada; filed 2002-01-14; published 2003-07-17. (WO counterpart WO 2003/060742 A1 lists Kubi Software Inc. with a 2002-01-13 priority.)
• Verified description (live search): An e-mail application augmented with a "collaborative workspace module." A user creates a project from within e-mail; a project folder is created in the user's mailbox containing calendar, files, participant list, tasks. The user invites participants by e-mail; acceptors get a project folder in their own mailbox. The system "monitors project activities and updates each user's project folder," with content/annotation access control and replication of workspace objects across participants "regardless of platform"; objects are transmitted via e-mail (XML-tagged, MIME/SMIME) and converted into each recipient's format. This is the closest art in the e-mail-transport + replicated per-user project space space.
• § 102 status: Published 2003-07-17 → § 102(b) and § 102(a).
• Claims potentially anticipated: The replication of a project workspace into each participant's own mailbox, with per-user project folders and propagation of changes, maps well onto Claim 1's preamble ("each user has a copy of the document... modifications shared... copies identical after synchronization"). It also reads on claims 2–3 (creator invites users; access-control/privilege grants), claim 4 (transport agent = the e-mail client), and claim 12 (project folder containing a participant list, file/object store, calendar/task objects, storage). Estrada does not disclose Claim 1's specific machinery — local save of only new/modified resources into an information packet in a spooler, the explicit synchronization order with encoding/packaging/sequencing, and dispatch of the journal of packets to every listed computer. Estrada's change propagation is described as server-monitored, so a full anticipation of Claim 1 is doubtful; it is the strongest § 103 primary reference against Claim 1 in combination with (a) or (d).

(c) US 2004/0122898 A1 — IBM — Most relevant for object/annotation structure (Claims 12–15); applicant-cited

• Full citation: US 2004/0122898 A1, "Collaborative review of distributed content," assignee International Business Machines Corporation; filed 2002-12-20; published 2004-06-24.
• Verified description (live search): Collaborative review in which each reviewer receives the artefact (digital document) and records review comments in overlays that are separate from the artefact and logically linked to it ("strapped on" over the client application). Multiple overlays from multiple reviewers are recorded "in a distributed manner"; the owner sends the artefact to invited reviewers; changes/comments are reflected to all participants; tools allow text, freehand marks, geometric objects, and comments linked to locations in the underlying document.
• § 102 status: Published 2004-06-24 — after the 2004-02-08 bar date, so not § 102(b). As a US application filed 2002-12-20 (before the '580 invention date), it qualifies under § 102(e); publication (2004-06-24) precedes the '580 filing (2005-02-08), so § 102(a) is also available if the invention date is not earlier.
• Claims potentially anticipated: The '580 Background cites IBM as the model of "notes saved separately from the document with logical links... each participant still acts in a centralized manner." IBM's annotation-objects-linked-to-a-document map onto Claim 12's "objects" element and strongly onto claim 13 (parent-child relationship — e.g., a comment/note as a child of an underlying document object) and claim 14 (change metadata). The artefact-plus-overlay distribution to invited reviewers touches Claim 1's preamble but the separate-overlay architecture (annotations outside the document, not synchronized copies of a unified document with packet journal) undermines full anticipation of Claim 1.

(d) US 2003/0177025 A1 — Curkendall — Examiner-cited; peripheral field

• Full citation: US 2003/0177025 A1, "Method and system for agricultural data collection and management," inventor Leland D. Curkendall; filed 1998-03-09; published 2003-09-18.
• Description: Title-level only — this search pass did not retrieve the abstract (search budget exhausted). Subject-matter domain is distributed agricultural data collection/management (handheld/mobile collection with data synchronization to a central database). It does not appear, from title/classification context, to address group document editing or e-mail transport.
• § 102 status: Published 2003-09-18 → § 102(b) and § 102(a).
• Claims potentially anticipated: Low. It could only bear on generic "local storage of changed data + later transfer/sync" steps of Claim 1; no claim-level anticipation is supportable on title information alone. Treat as § 103 filler at most — verify the full text before relying on it.

(e) US 2003/0182435 A1 — Digital Doors, Inc. — Examiner-cited; security domain

• Full citation: US 2003/0182435 A1, "Data security system and method for portable device," assignee Digital Doors, Inc.; filed 2000-11-13; published 2003-09-25.
• Description: Title-level only (abstract not retrieved in this pass). Field: data security for portable devices (encryption/authentication/access control over data, including synced data on portable computers). Same inventor family as (f).
• § 102 status: Published 2003-09-25 → § 102(b) and § 102(a).
• Claims potentially anticipated: Low. At most tangential to Claim 1's "encoding" step or Claim 3's privilege/attribute policy; no direct document-sharing or spooler/journal disclosure is evident from the title. Verify before relying.

(f) US 2005/0138110 A1 — Redlich — Examiner-cited; published after '580 filing — § 102(e) only

• Full citation: US 2005/0138110 A1, "Data security system and method with multiple independent levels of security," inventor Ron M. Redlich; filed 2000-11-13; published 2005-06-23 (assignee family: Digital Doors, Inc.).
• Description: Title-level only. Field: data security with multiple independent levels of security (MILS) — compartmented access to data, likely including peer/group data exchange.
• § 102 status: Published 2005-06-23 — after the '580 filing (2005-02-08). Not § 102(b). As a US application filed 2000-11-13 by another, it can only qualify under § 102(e) (publication under § 122(b) of an application filed before the invention date). If the '580 inventors' invention date is held later than 2005-06-23 (unlikely on this record), § 102(a) would also be possible.
• Claims potentially anticipated: Low-to-nil against the document-sharing claims; potentially touches attribute/privilege concepts (Claim 3, Claim 12's user-list element) only at a high level of abstraction. Do not rely on without full-text review.

(g) US 2006/0101071 A1 — Network Dynamics, Inc. — Examiner-cited; closest to Claims 5–7 (OS-level transport) by subject matter

• Full citation: US 2006/0101071 A1, "Network operating system and method," assignee Network Dynamics, Inc.; filed 2003-03-18; published 2006-05-11.
• Description: Title-level only (abstract not retrieved in this pass). Field: a network operating system providing distributed services (file/data sharing and messaging among networked machines, peer-to-peer style OS-integrated transport) — by title, the domain most on-point for the '580's alternative embodiment of claims 5–7 (transport as an OS service, daemon, kernel-integrated).
• § 102 status: Published 2006-05-11 — after the '580 filing. Not § 102(b). As a US application filed 2003-03-18 by another, it qualifies only under § 102(e) (assuming no earlier § 102(b) publication exists — unverified).
• Claims potentially anticipated: Potentially claims 5–7 (OS-service/point-to-point transport; daemon or kernel implementation) if the disclosure actually covers OS-integrated group file synchronization — but that cannot be confirmed from the title alone, and its 2006 publication date makes it weak § 102(e) art whose content post-dates the '580's own conception. Full-text review required before use.

(h) US 7,236,976 B2 — Aramark Corporation — Examiner-cited; scheduling domain — minimal relevance

• Full citation: US 7,236,976 B2, "System and method for scheduling events and associated products and services," assignee Aramark Corporation; filed 2000-06-19; granted 2007-06-26.
• Description: Title-level only. Field: scheduling of events with associated products/services (likely a group/calendar scheduling system with data exchange among distributed users). Peripheral to document synchronization.
• § 102 status: Granted 2007-06-26 — after the '580 filing. Not § 102(b). As a US patent granted on an application filed 2000-06-19 (before the invention date) by another, it qualifies only under § 102(e) — unless an earlier pre-2004-02-08 application publication exists in its file history (unverified).
• Claims potentially anticipated: Low. Only conceivable overlap is with group/participant list structures of Claim 12; no meaningful anticipation of Claim 1. Verify full text if used at all.

2. Ranking — most relevant prior art for US 7,313,580

Bottom line for a validity challenge: no single cited reference reads on all of Claim 1's distinctive elements (per-user local copy + spooler packet journal + sequence-numbered synchronization + direct computer-to-computer dispatch + decoding into resource packets). The strongest anticipation arguments run to claims 12–15 and 2–4 (and the HTML/desktop dependents 8–10, 18–20, which map to the '580's own alternative embodiments rather than to the cited art). The realistic invalidity path against independent Claim 1 is a § 103 combination — Estrada or Zaplet (e-mail-distributed shared documents with per-user copies and propagation) combined with a packetized/journaled offline-synchronization reference (e.g., the family-cited JP 4357827 B2, "Peer-to-peer document sharing network system," filed 2002-11-07, or US 2002/0069057 A1 on peer-to-peer sharing of document templates — both in the '580's "Family Cites" list rather than the US examiner's list).

3. Confidence and verification gaps (stated plainly)

1. Depth of verification differs by reference. Descriptions for (a) Zaplet, (b) Estrada, and (c) IBM were verified against live full-text sources (Google Patents, USPTO.report, patentimages PDFs, Unified Patents portal). Descriptions for (d)–(h) are title/classification-level only — the search-step budget was exhausted before abstracts could be retrieved — and any reliance on them for an actual § 102/§ 103 position requires pulling the full texts first.
2. § 102 basis dates for (f), (g), and (h) rest on the filing/publication dates in the Google Patents citation table (authoritative for this record). For (g) and (h) I did not verify whether earlier application publications exist that would make them § 102(b) art; treat § 102(e) as the conservative basis.
3. Anticipation statements are "potential" mappings only. A formal § 102 anticipation requires every element of the claim to be present in a single reference; the tables above identify where each reference plausibly reads on each claim, not a concluded anticipation holding.
4. The citation table distinguishes the five examiner-cited references (asterisked: Curkendall, Digital Doors, Redlich, Network Dynamics, Aramark) from the three applicant-cited references (Zaplet, Estrada, IBM — the three discussed in the '580's own Background of the Invention).

§ 103 Obviousness Analysis — U.S. Patent 7,313,580

Prepared: 2026-04-26 · Statute: Pre‑AIA 35 U.S.C. § 103 (application filed 2005-02-08; issued 2007-12-25) · Posture: All 20 claims are asserted by UBQS-IP LLC in the 2026 S.D.N.Y. and D. Utah actions; no claim has yet been construed, and no PTAB/reexam has been filed (see prior sections). This analysis builds exclusively on the prior-art set compiled in the Prior Art section, plus the two references verified above.

I. Governing law and analytical framework

Because the '580 application was filed February 8, 2005, validity is governed by pre-AIA § 103 as informed by Graham v. John Deere (1966) and KSR Int'l Co. v. Teleflex (2007): (1) scope and content of the prior art; (2) differences between the prior art and the claims; (3) the level of ordinary skill; and (4) objective indicia. KSR makes clear that a patentee's claim to a combination of known elements is obvious "when the combination does no more than yield predictable results," and that a challenger need not locate an express teaching-suggestion-motivation in the literature — common sense, design incentives, and known market forces suffice. Two KSR principles do most of the work here:

1. Obvious-to-try / design choice: where the field has a finite number of identified, predictable solutions to a known problem (here: how to propagate document changes among a replicated group without a project server), the selection is obvious.
2. Known-technique substitution: substituting one known transport mechanism (e-mail spooling, P2P, OS daemon service) for another to achieve a predictable improvement (lower resource requirements, faster delivery, firewall traversal) is the paradigm KSR obviousness case.

Statutory-bar / reference availability. The § 102(b) bar date is 2004-02-08 (one year before filing). References qualifying only under § 102(e) (US applications by another filed before the invention date) remain available for § 103 combination; because the '580 claims no priority earlier than its 2005-02-08 filing, the presumptive invention date is 2005-02-08, comfortably after the US filing dates of IBM '2898 (2002-12-20) and Network Dynamics (2003-03-18).

II. Person of ordinary skill in the art (PHOSITA)

A PHOSITA circa February 2005 would be a computer scientist or software engineer (B.S. + 2–4 years, or equivalent experience) working in groupware / collaborative document systems and networked application architecture, with working knowledge of: e-mail transport and clients (SMTP/POP/IMAP, MIME, client plug-ins); replication and synchronization concepts (full and incremental/delta propagation, sequence/version ordering, spoolers and outbound queues); peer-to-peer and client-server networking (TCP/IP, direct point-to-point connections); document and markup formats (XML, HTML, DOM); and operating-system services (daemons, kernel/OS-level transport, desktop shells). This skill definition matters because several "gaps" in the primary references are matters of ordinary implementation knowledge in this profile, not invention.

III. What the claims actually require (reminder, from the granted text)

• Claim 1 (independent method): decentralized per-user copies of a shared electronic document → local save writes only new/modified resources into an information packet held in a spooler → a synchronization order that encodes/packages/sequences data for the transport manager → dispatch of all spooled packets from the syncing computer to every computer on the user list → recipients decode and incorporate packets in the sender's sequence into their copies → generate resources/update → transfer to the information manager → identical copies after all sync.
• Claims 2–11 (depend from Claim 1): administrator-created group (2); administrator-granted privileges (3); e-mail-client transport (4); OS point-to-point transport service (5); daemon/shell implementation (6); kernel-provided packaging/encoding/sequencing/transmission/decoding (7); document = desktop (8); markup-language document (9); HTML web page (10); unipersonal/single-computer use (11).
• Claim 12 (independent document claim): the shared electronic document "includes at least one of": group identifier / user list / viewing structure / object set / storage space — a deliberately broad "at least one of" disjunctive list.
• Claims 13–20 (depend from Claim 12): parent-child objects (13); author+time change metadata (14); container objects (15); own storage space (16); common storage space with manager differentiation (17); desktop (18); markup language (19); HTML web page (20).

IV. Prior-art inventory available for combination (with § 102 status)

Two verification notes added this session: (1) Kapust US 2002/0069057 A1 is now full-text verified — it discloses identifying users, establishing direct peer-to-peer TCP/IP connections between computing devices, sharing documents/templates that reside on each user's device, recording references to the templates across devices, distributing them to each computing device, and XML-markup document templates (patentimages PDF, FreePatentsOnline, Unified Patents portal). It is § 102(b) art. (2) JP 4357827 B2 returned zero live-search results, so it is dropped from the load-bearing analysis rather than mischaracterized.

V. Primary obviousness theories

Theory A — Estrada alone renders Claims 2–4, 12, 14, 16–17 obvious (and nearly all of Claim 1)

Estrada (US 2003/0135565 A1, "Electronic mail application with integrated collaborative space management") discloses an e-mail client into which a user creates a project, inviting participants by e-mail; each accepting participant receives a replicated project folder in his or her own mailbox; the system "monitors project activities and updates each user's project folder," replicating workspace objects (calendar, files, participant list, tasks) across participants; objects travel as XML-tagged MIME/S-MIME e-mail and are converted into each recipient's format; access/annotation control is administered by the project creator.

This single reference supplies, for the method claims:

• Claim 2 — the creating user who invites participants is literally the "administrator" who creates the group.
• Claim 3 — Estrada's creator-administered access and annotation control is the "granting of various access privileges."
• Claim 4 — Estrada's transport is the e-mail client (the reference is an e-mail application with a collaborative-space module).
• Claim 1, most elements — replicated per-user copies of a shared project space (preamble); local saves that must be propagated to other participants' folders; transport as encoded (XML/MIME) messages addressed to the participant list from the synchronizing user's machine; receipt and decoding into local objects; eventual convergence of copies.
• Claim 12 — the replicated project folder inherently contains at least one listed element (a participant/user list; stored objects such as files, calendar, tasks; storage space). Because Claim 12 is an "at least one of" claim, Estrada alone is nearly dispositive on it.

Genuine gaps vs. Claim 1: Estrada does not expressly teach (i) the spooler/waiting-area with packets containing only new/modified resources, or (ii) the explicit sequencing of packets for in-order incorporation. These are the only two structural elements separating Claim 1 from Estrada's replicated-mailbox project workspace — and both are filled by Theory B/C below.

Theory B — Estrada + Zaplet → Claim 1's update/journal concept; claims 9–10, 19–20

Zaplet (WO 2001/052081 A1) discloses group-collaborative electronic media distributed by e-mail with tracked, managed states — participants act on a shared medium and are notified of changes, with content/state management (tracking, restore, archive, supersede). The '580's own Background cites Zaplet as the e-mail-collaboration state-of-the-art.

Why combine: Zaplet supplies what Estrada lacks on the content-update side — a structured notion that a shared e-mail-delivered collaborative artifact has a managed, tracked state that changes over successive participant actions, and that only the state changes (not the whole artifact) need be communicated for the artifact to stay current. Estrada supplies what Zaplet lacks — per-user replicated copies (Zaplet is server-centric, which the '580 concedes). The '580's stated goal is precisely to keep per-user copies synchronized "with very low requirements in terms of computer resources"; combining a replicated-copy system (Estrada) with a state-change/journaling update system (Zaplet) is the obvious route to that goal. Zaplet also discloses HTML-rendered e-mail/web content, supporting claims 9–10 and 19–20 (with Kapust's XML templates as independent corroboration).

Theory C — Estrada + Kapust + ordinary e-mail spooling/sequencing knowledge → full Claim 1

The two residual Claim 1 elements — the spooler packet queue holding only changed resources and sequence-numbered dispatch/incorporation — are not the inventive core of any reference; they are textbook mechanics that a PHOSITA would add to the Estrada/Zaplet architecture for well-documented reasons:

1. Spooler/waiting area. Estrada's transport is e-mail. Every e-mail system a PHOSITA would use to implement Estrada (SMTP clients, RFC 821/2821-era MTAs) maintains an outbound spool/queue — a waiting area for data to be sent — by definition of the transport manager. The '580 itself concedes the spooler concept is generic ("the spooler for sending data is managed by the transport daemon"; "the equivalent in electronic mail would be the SMTP service"). Implementing Estrada's change propagation as e-mail messages that queue in the client's outbound spool while a user continues working is a design choice with a predictable result, not an invention.
2. Only-changed-resources packets. Sending only the modified/new resources rather than re-transmitting the whole document is the standard bandwidth-conservation practice in replication and synchronization (delta/incremental propagation) and is the obvious corollary of Estrada's object-level replication — only workspace objects change, so only changed objects need travel. Zaplet's state-change tracking reinforces this.
3. Sequencing. Out-of-order arrival of independently transmitted messages is the canonical networking problem; sequence numbers are the canonical solution (TCP, NNTP/USENET, e-mail threading, replication update vectors). The '580 itself describes sequence numbers as a routine "packet characteristic." A PHOSITA implementing any multi-packet synchronization protocol over e-mail or P2P would number the packets and reorder on receipt "according to the sending sequence" — again predictable mechanics.
4. Direct dispatch to each listed computer / decentralized storage. Kapust (verified this session) teaches exactly this layer: direct peer-to-peer TCP/IP connections between user computing devices, with the shared content residing locally on each device, and distribution of items to each participating computing device. Estrada (e-mail fan-out to the participant list) and Kapust (direct P2P dispatch to each peer) together cover Claim 1's dispatch-from-the-syncing-computer-to-each-remaining-computer limitation under either transport.

Resulting combination for Claim 1: Estrada's e-mail-replicated project workspace (copies per user; change propagation via encoded messages to the participant list; decode-and-update at recipients; convergence) + Zaplet's tracked-state change updates + Kapust's P2P local-copy distribution + the PHOSITA's standard spooler and sequence-number mechanics = every limitation of Claim 1. The combination is of known elements, each performing its known function, yielding the predictable result of low-resource decentralized document synchronization — the archetype KSR holds obvious.

Theory D — IBM '2898 (+ Estrada) → Claims 13–15 (object-structure claims)

IBM (US 2004/0122898 A1) discloses collaborative review of a digital document in which reviewers record annotations/overlays logically linked to locations in the underlying document, including text, freehand marks, geometric objects, and comments, with review contributions reflected to participants in distributed fashion.

• Claim 13 (parent-child objects): an annotation/comment linked to an underlying document object is the parent-child object relationship the claim describes — IBM's own examples (comments strapped onto a document element) are the paradigm.
• Claim 14 (author + time metadata on changes): IBM's distributed review records each reviewer's contributions; associating reviewer identity and a timestamp with each recorded change is the routine metadata practice of any review/versioning system.
• Claim 15 (container objects): layered overlays containing multiple annotations/geometric objects are containers in IBM's sense.
  Even if IBM's overlay architecture is "separate from the document" (as the '580's Background emphasizes), combining IBM's object/annotation structure with Estrada's replicated document workspace is obvious: a PHOSITA merging the two references would store IBM's annotation objects inside Estrada's replicated project document so they synchronize with the document — which is precisely Claim 12's document-plus-objects and Claims 13–15's object relationships.

Theory E — Network Dynamics (+ Estrada/Kapust) → Claims 5–7 (OS-level transport)

Claims 5–7 are transport-implementation dependents: the Claim 1 method carried out by (5) an OS point-to-point service, (6) a daemon (UNIX) / shell service, (7) the kernel, offered as a system resource. Network Dynamics (US 2006/0101071 A1, filed 2003-03-18, § 102(e)) is, by title and classification, a network operating system providing distributed data/file sharing and messaging among networked machines — OS-integrated transport of the sort claims 5–7 describe. The '580 itself frames this implementation as a substitute for e-mail transport: "The equivalent in electronic mail would be the SMTP service for sending and POP for receiving." Because the underlying transport concept (Claim 1) is obvious per Theories A–C, and because implementing a network service as an OS daemon or kernel resource was standard UNIX practice in 2005 (sendmail/qmail daemons, NFS, port-listening services — all admitted in the '580's own text), claims 5–7 add no inventive layer. Caveat: Network Dynamics is verified only at title level; the full text must be pulled before relying on it, and its § 102(e)-only status makes it vulnerable if the inventors ever prove pre-2003-03-18 conception (unlikely on this record, which shows no priority claim before 2005).

Honest assessment of the outliers — Claims 8/18 (desktop) and 11 (unipersonal)

• Claims 8/18 (the shared "electronic document comprises the desktop"): weakest ground within this prior-art set. None of the verified references teaches desktop-as-shared-document. The strongest available argument is that sharing the desktop is an obvious application of the same synchronization method to a different content type (the desktop shell is, in OS terms, a container/object store), but that argument risks relying on the patent's own teaching. Flag: needs additional art (e.g., application-sharing or distributed-desktop systems) before asserting.
• Claim 11 (unipersonal use): functionally a null/self-evident implementation — running the same save/sync machinery on one computer (the '580 describes connecting "through an alarm daemon with the same computer"). If anything, this dependent claim reads as a non-technical or insubstantial variation and would fall with Claim 1; standing alone it is vulnerable as obvious (or indefinite) for lacking any distinct technical limitation.

VI. Claim-by-claim conclusion

VII. Motivation to combine — articulated reasoning (the part courts actually test)

1. Same field, same problem, express admission of pertinence. Estrada, Zaplet, and IBM are all e-mail/group-collaboration systems — the '580's own Background discusses each as the relevant state of the art and defines the field's problem (high resource requirements of server-centric collaboration). Kapust and Network Dynamics occupy the adjacent, undisputed field of P2P/OS-level distributed file sharing. References addressing the same problem in the same field are analogous art as a matter of law.
2. The '580's goal is a known desideratum. The specification's stated improvement — collaboration "without the need for a project management server," "very low requirements in terms of computer resources," e-mail transport that traverses firewalls — is a design goal any PHOSITA in 2005 would recognize and pursue. The prior art already contains both halves: replicated per-user workspaces transported by e-mail (Estrada) and server-free P2P document exchange (Kapust). Combining them to eliminate the central project server is an obvious design response with a predictable result (KSR).
3. Known-technique substitution with predictable benefit. The '580 itself concedes the alternatives are fungible: e-mail transport may be replaced by "P2P (peer-to-peer) transmission that may speed up delivery time when participants are on-line," and an OS daemon service is "the equivalent in electronic mail [of] the SMTP service for sending and POP for receiving." Where the patentee's own disclosure frames e-mail, P2P, and OS-daemon transport as interchangeable known options, selecting among them is obviousness, not invention.
4. Filling the mechanics gap is standard practice. Spooling (e-mail outboxes), delta-only propagation (to save bandwidth), and sequence numbers (to handle out-of-order delivery) are the stock-in-trade of the PHOSITA defined in § II. KSR expressly permits reliance on "the inferences and creative steps that a person of ordinary skill in the art would employ" — no printed teaching of each screw-turn is required.
5. Reasonable expectation of success. Every component (e-mail plug-in replication, MIME/XML encoding, P2P TCP/IP connections, spoolers, sequence numbering, daemons) was mature, documented technology by 2003–2005. The combination does not alter the function of any component; it merely re-points them at a replicated group document. Success was all but guaranteed — the '580 itself is, in substance, that combination.

VIII. Objective indicia (Graham factor 4) — none favor patentability

The record compiled in the prior sections shows no secondary considerations supporting non-obviousness: no commercial product ever embodied the claims (the inventors held the patent personally for ~18 years without practicing it); no licenses or royalties are of record; no long-felt-need, industry-praise, copying, or unexpected-results evidence appears anywhere in the litigation or assignment record. The only post-issuance activity is the 2025–2026 monetization chain into UBQS-IP LLC and the April 2026 suits — which is assertion activity, not objective indicia of non-obviousness. An empty Graham-factor-4 record leaves the strong prima facie § 103 case above unrebutted.

IX. Anticipated patentee responses — and honest weaknesses in the challenger's case

1. "The examiner considered Estrada/Zaplet/IBM and allowed the claims." Estrada, Zaplet, and IBM were applicant-cited (appearing in the '580's own Background) and therefore presumptively before the examiner. A challenger must therefore lead with the combinations not made during prosecution — Estrada + Kapust, Estrada + Zaplet-for-state-updates, Estrada + Network Dynamics — and with the spooler/sequence "common knowledge" theory, which the file history will not have addressed in combination form. KSR was decided after examination and forbids treating examiner allowance as a merits finding; the combination arguments remain fully available in litigation.
2. "The combination lacks a specific teaching of a spooler holding only-changed packets, or of sequence-numbered dispatch." This is the strongest patentee counter. The honest answer is that these elements rest on (a) Kapust's verified P2P local-copy distribution, (b) the inherent/ubiquitous nature of e-mail spooling, and (c) the PHOSITA's standard sequencing toolkit — not on a single printed sentence in one reference. That is a legitimate KSR "common sense / design choice" theory, but it is the portion of the case most exposed to a Takeda-type "impermissible hindsight" attack, and it is why full-text mining of Network Dynamics and of replication/sync art (Lotus Notes-style replica journals, NNTP sequencing, rsync deltas) should be the next step before filing.
3. "The '580 teaches away from the combination." The specification criticizes Zaplet/Estrada/IBM as client-server/centralized. That criticism is weak: the '580 retains an e-mail server for transport and concedes that is not a disqualifying client-server structure ("Electronic mail is merely the method of transport"). Estrada likewise uses e-mail transport while replicating per-user folders. There is no credible teaching-away from replicated e-mail-distributed workspaces — the '580's own architecture is Estrada's architecture plus spooler/sequence mechanics.
4. Unverified references. Network Dynamics (claims 5–7) and JP 4357827 are not full-text verified; Curkendall/Digital Doors/Redlich/Aramark are title-level only. None of the load-bearing theories above depends on the unverified set except Theory E (claims 5–7). Theories A–D and the claim-12 analysis stand on full-text-verified Estrada, Zaplet, IBM, and Kapust alone.

X. Bottom line

US 7,313,580 presents a classic KSR target: a combination of mature, individually-known components — Estrada's e-mail-replicated per-user project workspaces (the closest single-reference anticipation of the claim-1 concept), Zaplet's tracked-state collaborative e-mail media, Kapust's verified P2P local-copy document distribution, IBM's linked annotation objects, and the PHOSITA's stock spooler/sequence-number mechanics — assembled to achieve the field's recognized goal of server-free, low-resource group document synchronization. Every asserted claim (1–20) is vulnerable under § 103, with the strongest cases on the method dependents 2–4 (Estrada alone), the document claim 12 ("at least one of" + Estrada), the object-structure claims 13–15 (IBM, alone or + Estrada), and the markup/HTML claims 9–10/19–20 (Kapust/Zaplet). The weakest points on this record are claims 8/18 (desktop) — for which no verified art exists here — and the spooler/sequencing gap in Claim 1, which is fillable but must be buttressed with full-text replication/sync art before filing. Objective indicia are entirely absent. Verdict: a well-constructed Estrada + Zaplet + Kapust (and, for claims 5–7, Network Dynamics) § 103 combination should render the asserted claims obvious, provided the flagged verification gaps (Network Dynamics full text; additional spooler/journal/sequence art) are closed.