US 8073911

I'll search for litigation and docket information on this specific patent, then compile the summary.

Let me check for CAFC 2026 activity and the district court litigation.

US Patent 8,073,911 — Summary

Note on scope of this report: All identifiers below are given literally as they appear in the record I retrieved. Where a source conflicts with the authoritative patent text, I say so explicitly.

Bibliographic data

Assignment history (per Google Patents): Bluespace Group Ltd. (2005) → Bluespace Software Corp. (2006) → security agreement to Silicon Valley Bank (2008) → Sterling Computers Corporation (2014, from Bluespace Federal Corp. and Bluespace Software Corp.).

Caution on title: One third-party litigation-analysis page (exparte.com) renders the title as "System and Method for Enforcing Compliance on Electronic Messages." That is not the title of record. The patent document itself and Google Patents both give "Enforcing compliance policies in a messaging system." I am treating the patent text as authoritative here.

Abstract (as issued)

A messaging system enforces compliance policies for electronic messages. A set of related messages (e.g., an email string between two or more people) is treated as a message container (200) with relational references to one or more submessages (210, 212, 214). A messaging server (112) stores the messages and submessages as discrete message components in a message database (416) and stores one or more compliance policies. A compliance policy describes the rules applicable to message components during their lifecycles and is defined in terms of a population structure, a set of rules, and a set of jobcodes. When an action occurs involving a piece of content, the system identifies the relevant compliance policy in the governance policy database (424) and applies rules applicable given the population structure and jobcode.

Independent claims — plain-language overview

The patent has 29 claims. Four are independent: claims 1, 10, 13, and 27.

Claim 1 — Computerized messaging server (system claim)
A messaging server with two core modules:

• a messaging module controlling a message database that stores messages sent among users. At least one stored message is a container with relational references pointing to multiple sent submessages stored externally to the container in the database; at least one submessage is a reply to or forward of other submessages of that message.
• a governance module controlling a governance policy database that stores a compliance policy describing rules applicable to the sent submessages. The governance module determines which rules apply to which submessages, and importantly, different rules can apply to different submessages within the same container.
• The system is used by entities in a population structure, and a rule includes a rule element indicating applicability, drawn from at least one of: a source element (the population entity that is the source of the submessage), a target element (the population entity that is a recipient), and a rank (ordering relative to other rules).

Claim 10 — Computer program product (non-transitory CRM)
Substantively the same elements as claim 1, but framed as program code on a non-transitory computer-readable medium (i.e., a software-product claim rather than a server claim).

Claim 13 — Computer-implemented method
A method of managing messages, comprising: (a) defining a compliance policy describing rules applicable to sent submessages; (b) receiving a sent message from one end user to at least one other end user, the message being a container with relational references to a plurality of sent submessages (including a first and second submessage) stored externally to the container, at least one being a reply to or forward of another; and (c) selectively applying the compliance policy's rules to the sent submessages. Same population-structure and source/target/rank rule-element limitation as claim 1.

Claim 27 — Computerized messaging server (email-specific variant)
A server claim framed around an email database storing emails sent among users, where sent emails comprise an email container with relational references to sent submessages stored externally to the container, at least one being a reply or forward. Based on the IPR petition record, this claim additionally recites that each of the sent submessages is stored exactly once within the email database (a de-duplication limitation).

⚠️ Uncertainty: The claim text supplied in my source is truncated mid-word at "…being one of a reply to and a forw[ard]". I therefore cannot reproduce claim 27 verbatim, and the "stored exactly once" language above is drawn from the IPR2025-00270 petition summary rather than from the claim document itself. Treat claim 27's full text as unverified.

Selected dependent claims (for context, not exhaustive)

• 2–4: Compliance policy describes the population structure, jobcodes, and rules; a jobcode carries a rule set applicable to all submessages classified with it; the messaging module receives a jobcode indication from an end-user and associates it with a submessage.
• 5, 9, 11, 18: Rule types — communication rules, readership rules, action rules (including DRM-type actions such as printing/saving/offline/copying/replying), and search rules.
• 6, 12: Validity rules (time period of usability) and retention rules (time period after which content should be deleted).
• 7–8, 26: Temporal policy snapshots — each submessage is associated with the compliance policy active when its content was created. A single message can therefore have a first submessage governed by an older policy and a second submessage governed by a newer one, with each policy applied separately at action time.
• 17, 20: DRM action rules; action budgeting (a permitted action limited to a number of times within a time period).
• 23–24: Recording a prohibited attempted action in a compliance log; logging interactions in an audit log.
• 25: Determining a rule applies/does not apply to first vs. second submessage based on the rule's source and/or target element.

Litigation and post-grant activity (as of the search date)

• District court: Sterling Computers Corporation v. Microsoft Corporation, No. 1:24-cv-00406, U.S. District Court for the Western District of Texas, filed April 17, 2024, before Judge Robert Pitman (source: Justia dockets; Stanford NPE Litigation Database). Asserted independent claims identified as claims 1 and 10. Accused product: Microsoft Exchange Online, with the infringement theory mapping "conversations"/Message-ID threading to the claimed message-container relational references, and "mail flow rules" to the claimed governance module. Microsoft filed a Rule 12(b)(6) motion to dismiss on § 101 (Alice) grounds on June 13, 2024; the court's February 12, 2025 order (Dkt. 48) discusses the Alice two-step framework.

• PTAB: IPR2025-00270, Microsoft Corporation v. Sterling Computers Corporation, petition filed January 17, 2025, challenging claims 1–13, 15, 18, 20–21, and 27. Grounds: (1) obviousness over Rohall (App. 2003/0163537) in view of Schiavone (App. 2002/0120600); (2) obviousness over Rohall + Schiavone + Gomes (US 8,375,008) for claims 9 and 27. A Google Patents litigation entry lists the case as "Pending – Instituted," and an amended scheduling order dated March 10, 2026 appears in the PTAB docket. Google Patents also lists a related Texas Western District case at 1:24-cv-00406.

• CAFC 2026: I searched specifically for Federal Circuit activity in 2026 involving this patent number and found no results. I cannot affirm that no appeal exists — the absence may reflect indexing lag or non-publication rather than the absence of a docket. This is an explicit uncertainty, not a negative finding.

Reliability caveats

1. Claim 27 is truncated in my source document; its full text is unverified.
2. The title discrepancy noted above is resolved in favor of the issued patent's own text.
3. The legal status ("Active," "expires 2028-10-27") is Google Patents' stated assumption, which it expressly disclaims as a legal conclusion — I am not vouching for it either.
4. The IPR petition analysis and complaint analysis I relied on come from third-party aggregators (exparte.com, ai-lab-cl-prod), not from PTAB or PACER originals. The docket entries from Justia and CourtListener are closer to primary sources.
5. The CROSS-REFERENCE section of the patent lists provisional applications 60/570,848 and 60/570,861 (both May 12, 2004) and related applications 10/789,461 and 10/977,354, plus an application titled "Tamper-Proof Electronic Messaging" filed May 12, 2005 — the latter is listed without a serial number in the text I retrieved.

I'll research litigation involving US patent 8073911. Let me start with the sources you mentioned plus general litigation databases.

Let me dig deeper into the specific cases and search for any other litigation.

Litigation Involving US Patent 8,073,911

I located two active proceedings involving US 8,073,911 (both listed on the patent's Google Patents page and confirmed by other sources). Here is what the search results establish:

1. District Court Infringement Action

Sources: Stanford NPE Litigation Database (https://npe.law.stanford.edu/patent/8073911 and https://npe.law.stanford.edu/case/[286221](/patent/286221)); the court's Feb. 12, 2025 order (Dkt. 48) at https://storage.courtlistener.com/recap/gov.uscourts.txwd.1172783609/gov.uscourts.txwd.1172783609.48.0.pdf; Google Patents family/litigation panel (case link to Texas Western District Court, 1:24-cv-00406).

2. PTAB Inter Partes Review

Sources: Docket Alarm (https://www.docketalarm.com – Microsoft Corporation v. Sterling Computers Corporation, Docket IPR2025-00270, PTAB, Jan. 17, 2025); Google Patents PTAB case link (https://portal.unifiedpatents.com/ptab/case/IPR2025-00270).

Additional Note

Google Patents also flags "First worldwide family litigation filed" via the Darts‑ip family record (family no. 34969166), consistent with the U.S. cases above. No other district-court suits, ITC actions, or CAFC appeals specifically naming US 8,073,911 appeared in the results I reviewed.

Caveats and Confidence

• High confidence on the identity, parties, forums, case numbers, and filing dates of the two proceedings above (both are corroborated across multiple sources).
• Lower confidence / unresolved: (a) the precise current docket status of 1:24-cv-00406 — one source says "Closed" while the most recent court order I could retrieve (Feb. 2025) shows the case continuing; and (b) the current posture of IPR2025-00270 beyond institution (e.g., whether a final written decision or termination has since issued).
• The earlier owner, Bluespace Software Corp., is the original assignee of the patent; I could not confirm any pre-2024 assertion campaign by Bluespace involving this specific patent from the available results, so I do not assert one exists.
• I did not independently query PACER or the CAFC docket directly (tool limits); the above is based on aggregator and court-document sources. If you need docket-level confirmation (e.g., exact PACER entries, appeal status), I'd recommend pulling the W.D. Tex. and PTAB dockets directly and re-checking the Stanford NPE entry, which is the source for the "Closed" status discrepancy.

I'll reconcile the structured block (which says "no AIA trial proceedings on file") against the patent page itself, which flags an instituted IPR. Let me search.

PTAB Proceedings — US 8,073,911 ("Enforcing compliance policies in a messaging system")

Data-integrity flag before anything else. The structured "PTAB proceedings on file" block says the USPTO ODP API returns no AIA trial proceedings for this patent. That is wrong as of today. The patent's own Google Patents record is annotated "PTAB case IPR2025-00270 filed (Pending - Instituted)," and document-level PTAB records (institution decision, referral notice, amended scheduling order) are publicly retrievable. I treat the ODP block as a stale index and the live record as controlling. Second flag: Google Patents attributes the PTAB data feed to "Unified Patents PTAB Data" — Unified Patents is the data aggregator here, not the petitioner/serials. The petitioner is Microsoft Corporation. Do not put Unified in the chain based on that attribution; I found no evidence Unified filed or funded anything on this patent.

Proceedings overview

One AIA proceeding on file: IPR2025-00270, [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) v. Sterling Computers Corp., instituted 2025-09-23 and currently active (no Final Written Decision yet as of 2026-09-15). No claims have been canceled, no claims have been sustained, nothing settled, no institution denied, no appeal. The defensive posture is therefore unresolved and live, not hardened — a defendant cannot yet point to a canceled claim, but the patent has been through only one institution-stage pass on a subset of claims, the Board has not ruled on the merits, and the challenged claims (including independent claim 1) are under real § 103 pressure from a three-reference combination anchored on Rohall. Plan for a merits outcome on or about 2026-09-23, not for a settled narrative.

IPR2025-00270 — Microsoft Corporation v. Sterling Computers Corporation

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)
• Filed: 2025-01-17 (filing date accorded 2025-03-25, Paper 7)
• Status: Pending – Instituted. Institution Decision Grant (Paper 12) entered 2025-09-23. Amended Scheduling Order (Paper 19) entered 2026-03-10. No Final Written Decision, no termination, no settlement.
• Judge panel: Administrative Patent Judges KARL D. EASTHOM, AMBER L. HAGY, and BACH V. HOANG. APJ Hoang authored the amended scheduling order; APJ Easthom is the same name flagged in third-party PTAB docket filters for this case. Panel composition is confirmed on the face of Paper 19.
• Petition grounds (per the petition record; § 103 only — no § 102 or § 112 grounds surfaced):
  • Ground 1 — § 103 obviousness over Rohall (US 2003/0163537) in view of Schiavone (US 2002/0120600): claims 1–8, 10–13, 15, 18, and 20–21. Petitioner mapped Rohall's "shadow documents"/parent-child message hierarchy and Mail Agent to the claim 1 "message container … relational references pointing to a plurality of sent submessages," and mapped Schiavone's rule-base/"recipient compliance engine" applying rules by sender, recipient, and content to the "governance module"/"governance policy database"/"compliance policy" limitations.
  • Ground 2 — § 103 obviousness over Rohall, Schiavone, and Gomes (US 8,375,008): claims 9 and 27. Gomes's de-duplication engine was cited for claim 27's "stored exactly once within the email database"; Gomes's repository access rules were cited for claim 9's "search rules."
  • Challenged claims overall: 1–13, 15, 18, 20–21, and 27. Notably not challenged: 14, 16, 17, 19, 22–26, 28, and 29.
• Institution decision: Instituted on 2025-09-23 (Paper 12, "Decision Granting Institution of Inter Partes Review"). Procedural path worth knowing: on 2025-05-28 the case was referred to a Board panel under the 2025-03-26 "Interim Processes for PTAB Workload Management" memo (Paper 8, before Chief Clerk Erica Swift) because Patent Owner filed no brief requesting discretionary denial — so the referral went straight to merits and non-discretionary considerations. Caveat: I could not retrieve the body of Paper 12, so I cannot quote the panel's institution reasoning or confirm whether the Board instituted on all claims/grounds the petition advanced, or only a subset. The grounds above come from the petition side of the record, not from the Board's own words — do not cite them as the Board's holdings.
• Final Written Decision: None issued. Statutory deadline under § 316(a)(11) runs one year from institution, i.e. on or about 2026-09-23 — about a week from today. Watch for it; it has not appeared in the records I retrieved.
• Settlement / termination: None. The parties are litigating (see below), and Patent Owner engaged the merits by filing no discretionary-denial brief.
• Appeal: None. Not appealable until an FWD issues.
• Trial-stage milestones (from Amended Due Date Appendix, Paper 19):
  • Due Date 1 — 2025-12-16: Patent Owner response; Patent Owner motion to amend. (A PO motion to amend was contemplated by the schedule — whether one was actually filed is not confirmed in what I retrieved.)
  • Due Date 2 — 2026-03-10: Petitioner reply; Petitioner opposition to MTA.
  • Due Date 3 — 2026-04-21: Patent Owner sur-reply; PO reply to MTA opposition (or revised MTA).
  • Due Date 4 — 2026-05-12: request for oral argument (non-extendable by stipulation).
  • Due Date 5 — 2026-06-02: Petitioner sur-reply to MTA reply; motion to exclude.
  • Due Date 6 — 2026-06-09: opposition to motion to exclude; prehearing conference request.
  • Due Date 7 — 2026-06-16: reply to opposition to motion to exclude.
  • Due Date 8 — 2026-07-16: oral argument (moved from 2026-06-24 at Patent Owner's request, unopposed by Petitioner). So argument has already occurred; the case is post-hearing and awaiting FWD.
• Counsel: Petitioner — Scott Border, Tathagata Goswami, Joe Netikosol (Winston & Strawn LLP). Patent Owner — Devan Padmanabhan, Michelle Dawson (Padmanabhan & Dawson, PLLC).
• Parallel litigation: Sterling Computers Corporation v. Microsoft Corporation, No. 1:24-cv-00406 (W.D. Tex.) — Sterling is the plaintiff/asserting party; Microsoft filed the IPR roughly a year into the case. The Google Patents record also flags "First worldwide family litigation filed" via Darts-IP, and the Stanford NPE Litigation Database lists this single case for the patent (categorizing Sterling as a "product company" asserter rather than a classic NPE).
• Defensive value: Nothing is dead yet, so the honest read is "watch the FWD, don't file on the assumption of invalidity." If the Board cancels claim 1 (or 1–13/15/18/20–21/27), the patent collapses to a narrow dependent-claim set and any demand letter invoking claim 1 becomes untenable. If the Board upholds claim 1, Microsoft's Rohall/Schiavone theory is now the best-tested art on the patent — useful to you, but you'd be litigating against a survivorship finding rather than a clean kill.

Strategic summary

Claim status. Nothing is canceled and nothing is sustained — the merits record is empty. What exists is a scope map: claims 1–13, 15, 18, 20–21, and 27 are under review (claim 1 as the flagship independent, claim 13 as the method independent, claim 27 as the email-embodiment server claim). Claims 14, 16, 17, 19, 22–26, 28, and 29 were not challenged. Untested claims are the ones a plaintiff will retreat to if the Board invalidates the independent claims — expect a contingent assertion strategy built on the dependents (e.g., claim 16's "approval" element, claim 17's DRM-action element, claim 19's encryption-rules element, claim 20's action-budgeting element) if the FWD goes against Patent Owner on the independents. Note also the patent's adjusted expiration of 2028-10-27 — under three years of runway, which materially changes the economics of fighting versus paying.

Estoppel landscape. No estoppel has attached yet. Microsoft's § 315(e)(2) estoppel arises only on FWD or termination, and it will cover only grounds it raised or reasonably could have raised — i.e., Rohall, Schiavone, and Gomes in the two combinations asserted. For a defendant being asserted today, that leaves the following available (subject to the usual § 325(d)/§ 315(b) and Fintiv-era considerations): any § 102 anticipation art; any § 112 written-description/enablement attack; § 103 combinations built on art other than Rohall/Schiavone/Gomes; and — importantly — any ground at all against claims 14, 16, 17, 19, 22–26, 28, and 29, because claims that were not challenged in IPR2025-00270 fall outside the estoppel's scope for grounds unique to them. Also available: prior-art systems and printed publications that were not "reasonably could have been raised" in the IPR, if you can build a genuine non-overlap story. If you are a Microsoft privy, your art options are effectively closed on the challenged claims the moment the FWD lands.

Pattern signals. No multi-petition pattern: one petitioner (Microsoft), one IPR, one institution-stage victory for Petitioner. No evidence of a defensive aggregator (Unified Patents appears only as a data-feed attribution on Google Patents, not as petitioner or real party in interest — that is worth confirming in the petition's mandatory notices, which I did not retrieve). Patent Owner has not pursued any PTAB appeal because no appealable decision exists; it also declined the discretionary-denial fight at the referral stage, choosing to litigate the merits directly. Petitioner's counsel is a large national firm with a dedicated PTAB practice, and the three-reference § 103 combination with an explicit de-duplication exhibit suggests a fairly well-funded challenge rather than a defensive placeholder. Expect a keep-going posture rather than settlement, since the FWD is imminent and Microsoft has an active W.D. Tex. defense riding on it.

Recommended next steps

1. Get the FWD within days. Statutory deadline is on or about 2026-09-23 (one year from the 2025-09-23 institution). Retrieve Paper 12 and the forthcoming FWD from PTAB E2E / USPTO PatentCenter at https://ptab.uspto.gov/ and verify at claim-level granularity — do not rely on this memo's petition-side claim lists for the disposition.
2. Pull the full IPR2025-00270 file. Docket page: https://www.docketalarm.com/cases/PTAB/IPR2025-00270/Microsoft_Corporation_v._Sterling_Computers_Corporation/ — the amended scheduling order is at https://www.docketalarm.com/cases/PTAB/IPR2025-00270/Microsoft_Corporation_v._Sterling_Computers_Corporation/03-10-2026-Board/Order__Other-19-AMENDED_SCHEDULING_ORDER/ and the 2025-05-28 referral notice at https://www.docketalarm.com/cases/PTAB/IPR2025-00270/Microsoft_Corporation_v._Sterling_Computers_Corporation/05-28-2025-Board/Notice__Other-8-Notice__Referral_to_Board_Panel/. Confirm whether an MTA was actually filed (the schedule reserved the right) — an MTA plus a permissive FWD could leave you facing substitute claims that were never part of the original challenge.
3. Track the W.D. Tex. case for collateral estoppel and stay practice. Sterling Computers Corp. v. Microsoft Corp., No. 1:24-cv-00406 (W.D. Tex.) — check whether a stay was entered pending IPR and whether Microsoft has raised IPR-related invalidity contentions. Federal Circuit activity, if any, will show up on CourtListener: https://www.courtlistener.com/?q=%22IPR2025-00270%22 — no CAFC appeal exists today; an appeal of an adverse FWD would be filed within 63 days of the decision, so that window would open in late 2026.
4. If you are a defendant now, do not send a demand posture premised on this patent being "hardened" or "dead." Neither is supported. Quote nothing from this memo as the Board's holding — the Board has not ruled. Build your § 282 invalidity case on art outside Rohall/Schiavone/Gomes, and target the unchallenged dependents (14, 16, 17, 19, 22–26, 28, 29) as well as claim 1, since that is where a post-IPR Patent Owner will go.
5. Confirm the RPI/privy chain. Verify from the petition's mandatory notices (37 C.F.R. § 42.8) whether any party other than Microsoft is a real party in interest — this drives § 315(e)(2) estoppel scope for anyone contemplating a follow-on petition.

Confidence and gaps — stated plainly: I confirmed the proceeding number, parties, filing date, institution date, panel, grounds, counsel, and all scheduling dates from public document-level records. I did not retrieve the text of the institution decision (Paper 12) or any Patent Owner response/MTA, so I cannot tell you the Board's institution reasoning, whether institution was partial, or what Patent Owner's merits arguments are. I found no second IPR, no PGR, no CBM, no FWD, no settlement, and no Federal Circuit appeal. I cannot rule out a second, later-filed petition on this patent that simply did not surface in the searches I ran — verify directly against the PTAB E2E docket before relying on the count of one.

I'll research the assignment record for US 8073911, starting with the patent's legal events and then cross-referencing USPTO assignment data.

Good leads. Let me dig into the inventors, the Bluespace entity history, and the assignment records.

Assignment & Ownership Analysis — US 8073911 ("Enforcing compliance policies in a messaging system")

Data caveat up front: In this session I was able to retrieve the patent's full text and its legal-events/ownership chain via Google Patents (which mirrors USPTO assignment data), plus litigation and third-party NPE-database records. I was not able to open the Assignment Center record itself, so I could not verify reel/frame numbers or the correspondent of record. Per your instructions I will not fabricate those fields; wherever they are unknown I say so explicitly. The dates and conveyance types below are from Google Patents legal events and should be re-verified at the Assignment Center (search page: https://assignmentcenter.uspto.gov/ ; mirrored at https://assignment.uspto.gov/patent/index.html).

Inventors

Pattern notes: Both named inventors appear to be the founding team, and both are listed as assignors on the 2005 Bluespace Group Ltd. assignment — so there is no evidence of a "founders bail out within 12 months" fire-sale trigger. Bluespace continued as an entity (including a "Bluespace Federal Corp." affiliate) until the 2014 asset transfer. Note: the sibling patent US 7,716,217 (same priority family, asserted in the same campaign) adds Paul Marston as an inventor; the '911 names only Justin Marston and Andrew Stuart Hatch.

Not determinable: Whether either inventor was still affiliated with Bluespace at the 2014 transfer. No departure record was found.

Original assignee

Bluespace Software Corp. (Google Patents "Original Assignee"), with an earlier UK-related parent, Bluespace Group Ltd. (domesticated into the US corp in 2006).

• Product embodying the claims: Yes — Bluespace shipped enterprise messaging for regulated environments. Its one-time CEO Pat Motola described it as a "[s]oftware company selling multi-level applications and messaging solutions to the Defense and Intelligence community" (Mondaq). This is consistent with the patent's secure/auditable messaging theme.
• Primary line of business: Secure/compliance-oriented electronic messaging software for government and regulated customers.
• Current status: Wound down / no longer operating as a patent-holding concern. Its patent assets were transferred to Sterling Computers Corporation in 2014 (which the Mondaq piece describes as a 4-patent transfer). I found no bankruptcy filing for Bluespace; the 2014 event is better characterized as a portfolio sale of a defunct/legacy company's assets than a proven Chapter 7/11 fire-sale. (This is one of the fields I could not fully verify.)

Assignment timeline

Execution dates vs. recording dates: Google Patents legal events show the recording/effective event date. Where only that date is available, I mark the execution date as "unknown." Reel/frame and correspondent are unverified in this session.

• 2005-05-12 (filed) — Application 11/129,212 filed; assignee of record Bluespace Software Corp.

  • Conveyance: (original filing — not a recorded assignment)
  • Assignor: n/a
  • Assignee: Bluespace Software Corp.
  • Correspondent: unknown
  • Context: original filing; priority date claimed to 2004-05-12 (provisionals 60/570,848 and 60/570,861).

• 2005-09-09 (recorded) — Reel unverified

  • Conveyance: Assignment of interest
  • Assignor: Marston, Justin; Hatch, Andrew S. (the inventors)
  • Assignee: Bluespace Group Ltd.
  • Correspondent: unknown — could not retrieve (this is the key field to pull from Assignment Center; see "Repeat correspondent" signal below).
  • Context: internal reorg / entity formation — inventors assign rights up to the group parent entity.

• 2006-07-20 (recorded) — Reel unverified

  • Conveyance: Certificate of Domestication (essentially a name/entity change)
  • Assignor: Bluespace Group Ltd.
  • Assignee: Bluespace Software Corp.
  • Correspondent: unknown
  • Context: change-of-name / domestication only — not an ownership sale.

• 2008-09-16 (recorded) — Reel unverified

  • Conveyance: Security Agreement
  • Assignor: Bluespace Software Corp.
  • Assignee: Silicon Valley Bank
  • Correspondent: unknown
  • Context: securitization — a collateral lien in favor of the company's lender, not a transfer of ownership. (SVB's interest is subordinate to ownership and is not a link in the title chain to Sterling.)

• 2014-10-28 (recorded) — Reel unverified

  • Conveyance: Assignment of interest
  • Assignor: Bluespace Federal Corp.; Bluespace Software Corp.
  • Assignee: Sterling Computers Corporation
  • Correspondent: unknown — could not retrieve
  • Context: asset/portfolio acquisition — the Mondaq report states this 2014 transfer conveyed four issued US patents, including US 8,073,911 and the sibling US 7,716,217. Sterling is the current assignee.

No post-2014 assignments were found. So the chain terminates at Sterling Computers Corporation (which is consistent with Sterling being the named plaintiff in the 2024 suit).

Timeline diagram

timeline
    title Ownership of US 8073911
    2004 : Provisional priority filing
    2005 : Application 11129212 filed
         : Inventors assign to Bluespace Group Ltd
    2006 : Domesticated to Bluespace Software Corp
    2008 : Security agreement to Silicon Valley Bank
    2011 : Patent 8073911 issues
    2014 : Bluespace assets sold to Sterling Computers
    2024 : Sterling sues Microsoft in W D Texas
    2025 : Microsoft IPR instituted at PTAB

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The 2014 transfer (Google Patents legal events, 2014-10-28) moved the patent from Bluespace Software Corp. to Sterling Computers Corporation, which is an operating IT company — not a "IP/Holdings/Ventures" single-purpose Delaware/Texas LLC. The Stanford NPE Litigation Database classifies Sterling as a "Product company" / "Practicing Entity." No registered-agent-service address or single-member shell was identified.

2. Known asserter in the chain — unclear. Sterling does not match any of the enumerated classic NPEs (Acacia, Marathon, IV, IPNav, Wi-LAN/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Erich Spangenberg entities). However, Sterling does appear as a patent asserter in Stanford's NPE Litigation Database (case 1:24-cv-00406) and, per Mondaq, "currently available USPTO records suggest Sterling holds about a dozen patent assets" — i.e., a small accumulation of asserted assets rather than organic R&D output. That is suggestive but not a match to a published high-frequency-plaintiff list.

3. Repeat correspondent across the chain — unclear / not determinable. I could not retrieve the correspondent of record for any recording. This is the single most valuable field to pull directly from Assignment Center, because the 2005, 2006, 2008, and 2014 recordings may share a firm; recurring counsel across those links (especially the 2014 transfer and any later confirmatory/name recordings) would materially upgrade this signal. As of now I make no finding.

4. Cascading transfers — not present. There is only one post-issuance ownership transfer (2014-10-28). The 2005 and 2006 events are intra-Bluespace (formation + domestication), and the 2008 event is a lien. No chained LLC-to-LLC conveyor and no sub-24-month cascade.

5. Pre-litigation transfer — not present. The operative assignment is 2014-10-28; the first infringement suit naming this patent (Sterling Computers Corp. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), 1:24-cv-00406, W.D. Tex.) was filed 2024-04-17 — roughly a nine-and-a-half-year gap, the opposite of a venue/standing-driven pre-suit transfer.

6. Bankruptcy fire-sale — unclear. No bankruptcy record for Bluespace was located. The 2014 transfer reads as a portfolio sale of a wound-down company's assets (four patents), but I could not confirm a Chapter 7/11 proceeding. Treat as unproven.

7. Privateering — not present (no evidence). There is no indication that an operating company transferred these patents to an NPE to assert on the operating company's behalf. Sterling bought the assets outright and asserts in its own name. Note the accused party, Microsoft, is a large incumbent tech company, not a competitor of Bluespace.

8. Defensive aggregator — not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. If anything, the opposite: Unified Patents filed an IPR against this family (IPR2025-00270, instituted), meaning Unified is challenging the patent rather than neutralizing it by acquisition.

Verdict

NPE — moderate confidence.

Justification: The ownership chain terminates not at a product-practicing developer but at Sterling Computers Corporation, which acquired the patent (with three others) on 2014-10-28 from the wound-down original assignee Bluespace Software Corp. and then asserted it against Microsoft in 1:24-cv-00406 (W.D. Tex., filed 2024-04-17) — an acquisition-then-assertion model rather than organic product enforcement, and Sterling appears in Stanford's NPE litigation database as an asserter with roughly a dozen held assets (Mondaq). I deliberately stop short of "high confidence" because the strongest tell — a shell-LLC conveyor — is absent (Sterling is a real operating company that Stanford categorizes as a "Product company"), and I could not verify reel/frame or correspondent, so signals 2/3 remain unresolved. To move this to a firm call, pull the correspondent of record for the 2005, 2006, and 2014 recordings at the Assignment Center; recurrence of one attorney/firm across those links would be the decisive datum.

Verification links:

• USPTO Assignment Center search: https://assignmentcenter.uspto.gov/ (mirror: https://assignment.uspto.gov/patent/index.html)
• Google Patents legal events: https://patents.google.com/patent/US8073911/en
• Sterling v. Microsoft docket (1:24-cv-00406, W.D. Tex.): https://dockets.justia.com/docket/texas/txwdce/1:2024cv00406/1172783609
• Stanford NPE Litigation Database — patent page: https://npe.law.stanford.edu/patent/[8073911](/patent/8073911)
• PTAB IPR2025-00270 (Unified Patents): https://portal.unifiedpatents.com/ptab/case/IPR2025-00270
• Mondaq — Turn Of Sterling Computers To Patent Litigation No Fluke: https://www.mondaq.com/unitedstates/patent/[1493784](/patent/1493784)/turn-of-sterling-computers-to-patent-litigation-no-fluke

I'll research US patent 8073911 and its cited prior art. Let me run several searches.

Let me pull the actual citation lists from Justia and Google Patents.

Prior-Art Analysis — US Patent 8,073,911

1. Patent Identification (verified)

Note: the parallel PTAB proceeding (IPR2025‑00270) captions the same patent (8,073,911) under the title "System and Method for Enforcing Compliance on Electronic Messages." Same patent number, different caption — I am reporting it literally, not correcting it.

2. Important scope limitation on this research

I could not retrieve the complete "References Cited" list as it exists on the USPTO face of the patent. USPTO PatentCenter/Assignment pages were not returned by the searches available; I am working from:

• the authoritative full text at https://patents.google.com/patent/US8073911/en (provided in the prompt), which does not enumerate the citation list in the excerpt;
• the Justia mirror (https://patents.justia.com/patent/8073911), which exposed the non‑patent‑literature list and a first U.S. patent citation (US 6,249,807, Shaw et al., June 19, 2001) plus EP 0739115;
• the IPR2025‑00270 record, which identifies the references the Petitioner actually relies on.

I could not enumerate every U.S. patent document cited on the face of 8,073,911. Patent face-citations for this family typically include dozens of "References Cited" U.S. patents and I do not have that verified list. I am flagging this rather than fabricating entries. Anything below not directly retrieved is marked accordingly.

3. References cited on/against the patent (verified)

3.1 U.S. and foreign patent documents

Caveat: Neither of the above was retrieved with its full disclosure text, so I cannot represent that either discloses every limitation of any claim. §102 anticipation requires a single reference to disclose all limitations; on the available evidence these are at most §103 references.

3.2 Non‑patent literature cited (from Justia's reproduction of the patent's NPL list)

3.3 Related applications named in the patent (family, not prior art)

US provisional 60/570,848 and 60/570,861 (both 2004‑05‑12); US utility 10/789,461 (2004‑02‑26) and 10/977,354 (2004‑10‑28). These are incorporated‑by‑reference family members and should not be double‑counted as prior art.

4. Prior art actually asserted: IPR2025‑00270 ([Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) v. Sterling Computers Corp.)

This is the most probative, currently‑live anticipation/obviousness record against 8,073,911. Challenged claims: 1‑13, 15, 18, 20‑21, and 27.

Grounds as pleaded:

• Ground 1 — claims 1‑8, 10‑13, 15, 18, 20‑21 obvious over Rohall in view of Schiavone.
• Ground 2 — claims 9 and 27 obvious over Rohall + Schiavone + Gomes.

Note the Petitioner framed these as §103 obviousness, not §102 anticipation — an important signal that no single reference was viewed as disclosing every limitation of a claim.

5. Anticipation assessment (§102) — honest bottom line

On the record I could verify:

• No single verified reference appears to anticipate an independent claim (1, 10, 13, or 27). The two‑part architecture the claims require — (a) a message container with relational references to stored submessages, plus (b) a governance module/governance‑policy database applying different rules to different submessages with source/target/rank elements — is split across references (Rohall for (a); Schiavone for (b); Gomes for the de‑duplication/search‑rule limitations).
• Closest to a §102 candidate on the structural limitations alone: the Montage multimedia mail system (Edwards, 1991) for the separately‑referenceable message‑part concept, and Rohall (2003/0163537) for the pointer‑based thread container. Each is a candidate against the structural limitations of claims 1/10/13/27, not the full claims.
• Claims 7, 8 and 26 (associating each submessage with the compliance policy active at the time its content was created, including mixed‑policy containers) are the narrowest, most patentable points and were not addressed by any verified reference; they are the least likely to be anticipated.
• Claim 27 ("stored exactly once") is specifically targeted by Gomes (US 8,375,008) — the strongest single‑reference §102‑style mapping in the IPR, though still pleaded as §103.

Confidence levels

• High confidence: patent identification, dates, assignees, claim set, the IPR grounds and reference identifiers (Rohall 2003/0163537; Schiavone 2002/0120600; Gomes 8,375,008), the NPL list.
• Low / unverified: the full U.S. patent face‑citation list; the title and disclosure of US 6,249,807 (Shaw et al.); the specific content of EP 0 739 115. I did not retrieve these documents and will not characterize their disclosures further.

If you need the exhaustive face‑of‑patent citation list (all U.S. patent documents), that must be pulled directly from USPTO PatentCenter/Global Dossier for application 11/129,212 — the searches I could run returned derivative sources (Google Patents, Justia, IPR records) rather than the complete official list, and I have not filled the gap by inference.

I'll research the prior art landscape for this patent, including the pending IPR and the referenced applications, before building the § 103 analysis.

I found the pending IPR. Let me pull the full petition analysis and the specific prior-art references to ground the § 103 analysis.

Let me pull the details on the secondary references and the institution decision.

Obviousness Analysis — U.S. Patent No. 8,073,911

0. Scope, governing law, and evidentiary posture

The patent. U.S. 8,073,911 B2, "Enforcing compliance policies in a messaging system," inventors Justin Marston and Andrew Stuart Hatch, original assignee Bluespace Software Corp., current assignee Sterling Computers Corp. Application 11/129,212 filed 2005‑05‑12; priority to provisionals 60/570,848 and 60/570,861, both filed 2004‑05‑12. 29 claims (3–29 include 3 independent claims: claim 1 (server), claim 10 (computer program product), claim 13 (computer‑implemented method), plus claim 27 (a second server claim)).

Governing law. Because the application was filed before 16 March 2013, pre‑AIA 35 U.S.C. § 103(a) applies: the invention is unpatentable if "the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art." The controlling framework is Graham v. John Deere Co., 383 U.S. 1 (1966), as refined by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). Asserted invalidity must be proven by clear and convincing evidence, and the claims are presumed valid.

Posture. This is not a hypothetical. The page itself flags "Family has litigation — PTAB case IPR2025-00270 filed (Pending - Instituted)" (https://patents.google.com/patent/[US8073911](/patent/US8073911)/en). That petition, [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) v. Sterling Computers Corp., IPR2025‑00270, was filed 2025‑01‑17 and instituted on 2025‑09‑23 (Paper 12), with an amended scheduling order entered 2026‑03‑10. Challenged claims: 1–13, 15, 18, 20–21, and 27. The grounds and prior-art combinations below are drawn from the petition record as reported at https://ai-lab.exparte.com/case/ptab/IPR2025-00270/doc/summary/1 and https://ai-lab.exparte.com/case/ptab/IPR2025-00270/doc/1016. Institution is not a merits ruling and no final written decision has issued.

Note on the title discrepancy. The same petition summary identifies the '911 title as "System and Method for Enforcing Compliance on Electronic Messages," whereas the patent document at https://patents.google.com/patent/US8073911/en is titled "Enforcing compliance policies in a messaging system." I report both as found and do not reconcile them.

1. The prior art references relied upon

§ 102(b) status. Rohall (2003‑08‑28) and Schiavone (2002‑08‑29) each published more than one year before the 2004‑05‑12 priority date, so both are prior art under pre‑AIA § 102(b) regardless of the provisional/non‑provisional date question. I could not verify Gomes's effective filing date in the available search results; Gomes's status as § 102(b) or § 102(e) art is a genuine open issue that the Patent Owner could contest. This is an express caveat, not a finding.

The patent's own "Prior art keywords" field (Google Patents) is itself informative about the art: sent / rules / submessage / submessages / compliance policy — i.e., the document's own indexing concedes that the intersection of "submessages" and "compliance policy rules" was the relevant prior-art space. The Background section likewise frames the problem as one already recognized in the art: "there are few, if any, ways to automate the process of filtering and storing business-related e-mails" and heavy email "makes it extremely difficult for a company or other enterprise to store the message content or to determine how the messages have transited the messaging system."

2. Independent claim 1 — element-by-element mapping

Claim 1 has three substantive clusters: (a) the container/submessage architecture; (b) the governance module and per-submessage rule determination; (c) the population structure and the source/target/rank rule elements.

Applicability of each independent claim. Claim 10 (computer program product) recites the identical functional architecture over a "non-transitory computer-readable medium," and claim 13 (method) recites defining the policy, receiving the container‑referenced message with first and second submessages, and "selectively applying rules." All three rise and fall with the same Rohall+Schiavone mapping.

3. The combinations, and the articulated reasons to combine

Under KSR and MPEP 2143, the Petitioner must articulate a reason beyond mere proximity of references. Four independent rationales are available here, and the petition record supports at least the first three:

(1) Combination of prior art elements according to known methods, yielding predictable results.
Email‑server architecture (Rohall) and rule‑based message policy engines (Schiavone) were both mature, both "designed to run on general‑purpose computers without specialized hardware," and both used conventional database and pointer structures. Integrating a rule engine behind an existing message store is the paradigm of a predictable combination — no new hardware, no new protocol, no unexpected result. See KSR, 550 U.S. at 416–17.

(2) Use of a known technique (Schiavone's rule base) to improve a similar device (Rohall's mail system) in the same way.
Both references address the same problem family — managing, filtering, and controlling large volumes of email. Rohall's stated motivations are thread integrity, "efficiently stored in memory," and reconstructing threads after deletion; Schiavone's are filtering, routing, and compliance. Adding Schiavone's compliance engine to Rohall's server‑side architecture improves exactly the functions Rohall already cares about, in the way Schiavone already teaches.

(3) Design incentive / market and regulatory pressure.
Both the '911 Background and Schiavone's specification independently identify the same external driver — a "patchwork of local, federal and international laws, regulations and best practices" that must be enforced on email (Schiavone [0006]; '911 Background). When the prior art itself names the problem the patent claims to solve, that is strong evidence of a design incentive. The '911 specification confirms this framing in its own summary: "An enterprise can thus bring its electronic messaging system into compliance with internal or government‑mandated regulations."

(4) The "obvious to try" / finite‑number‑of‑predictable‑solutions rationale.
Once the decision is made to attach policy rules to messages stored as discrete, individually addressable objects, the choice of what a rule may be keyed to (source, target, rank) is not a novel insight — it is the ordinary content of a rule schema. Schiavone enumerates sender, receiver, and content as rule inputs; ordering rules by rank to resolve conflicts is a conventional database/expert‑system practice.

4. The dependent claims

4.1 Ground 1 — Rohall + Schiavone

Claims 2–4 (population structure, jobcodes, jobcode‑to‑submessage association).
Claim 2 adds "a population structure of end‑users … a set of jobcodes with which the sent submessages can be classified, and a set of rules applicable to the population structure, jobcodes, and sent submessages." Claim 3 makes a jobcode carry "a set of jobcode rules applicable to all sent submessages classified with the jobcode." Claim 4 requires receiving a jobcode indication from an end‑user and associating it with the submessage. Schiavone's system expressly teaches a sender‑specified "mail‑type specifier" where "the rule may be associated with messages by default, in an automated fashion, or as the result of a sender's specification, e.g., by including a mail‑type specifier in the message," and its claim 1 recites "identifying a mail type specifier … referencing a data store … [and] processing said electronic mail message as a function of said mail type specifier and data retrieved from said data store." That is materially the jobcode concept: a user‑selected classifier that selects the governing rule set. The motivation is a straight substitution of nomenclature for a known mechanism.

Claim 5 (communication rules and readership rules). Schiavone's rules operate on "the specific sender, receiver and content"; routing/filtering to and from designated parties is communication‑rule functionality, and controlling whether a party may read forwarded content is the readership analogue. The '911 specification itself calls readership rules "important when an end‑user replies or forwards submessages as part of new messages" — a scenario Rohall is expressly built around.

Claims 6, 20 (validity/retention rules; action budgeting). Claim 6 adds validity rules ("time period for which a sent submessage or entity … is useable") and retention rules ("time period after which … should be deleted"). Claim 20 adds "a number of times within a given time period that the entity can perform a specified action." Automated record retention schedules and rate limits are ordinary data‑lifecycle administration; the motivation is the compliance/records‑management driver both references name. (Confidence note: I did not locate a specific passage in the search results where Schiavone or Rohall recites retention periods or action budgets. A retention‑schedule reference such as an email‑archiving product/specification may be needed to close claims 6 and 20 cleanly. That is a gap in what I could verify, and I flag it rather than assert disclosure.)

Claim 7 (prior compliance policy; policy fixed at content creation time). This is a versioning limitation: the governance policy database stores "at least one prior compliance policy active at a time prior to" the current one, and each submessage is associated with "a compliance policy that was active at a time that content of the sent submessages was created." The motivation is unusually strong and legally cognizable: a record‑retention regime that retroactively changed the rules for existing records would defeat its own purpose, and Schiavone's rules already carry association with messages at send time. Making policy applicability date‑stamped at creation is the natural, indeed necessary, implementation for a compliance system.

Claim 8 (different submessages governed by different policies within one message). This is the direct consequence of combining Rohall's discrete per‑document shadow‑document objects with Schiavone's per‑message rule evaluation. Because Rohall stores each reply as its own document with its own metadata, and Schiavone evaluates rules against each message, assigning different policies to different submessages of one container is a mere application of both teachings — the very "different rules … applicable to different ones" concept already present in claim 1.

Claims 11, 12, 18 (rule‑type enumerations). Claim 11 lists communication, readership, action, and search rules; claim 18 the same set for the method claim; claim 12 lists validity and retention. Claim 18's action rules ("actions a population structure entity can perform on a sent submessage") map to Schiavone's modification/processing logic and to Rohall's forwarding/deletion actions.

Claim 15 (group defined by position in a hierarchy). Rohall's parent/child conversation tree plus Schiavone's profile stores make hierarchy‑derived grouping a routine configuration.

Claim 21, 22 (groups and group rules; geographic groups). Rohall's thread tree plus Schiavone's "geographical" concept — Schiavone's stated rationale is "Compliance with local laws" and "a patchwork of applicable laws" with "limited regional application." Grouping users by geography and applying group rules to their messages is the direct implementation of Schiavone's own stated purpose.

Claim 23 (prohibited action recorded in a compliance log) and claim 24 (audit log). Logging rejected/denied actions is inherent in any compliance enforcement system and is the standard implementation of Schiavone's compliance determination; the '911 specification describes the compliance log as merely conventional ("the governance policy module 422 records such communication attempts in the compliance log").

Claim 25 (rule applicability determined by source/target elements for one submessage but not another). Rohall's structure (each submessage has its own sender/recipient metadata — "header information, such as sender, receiver … ") combined with Schiavone's sender/receiver‑keyed rules makes this a direct and predictable result.

Claim 26 (temporal policy versioning applied per submessage on an action against the container). Same rationale as claim 7, applied at the per‑submessage granularity that Rohall's discrete objects provide.

4.2 Ground 2 — Rohall + Schiavone + Gomes

Claim 9 (search rules). "Search rules describing which population structure entities can view which sent submessages when searching the sent submessages stored by the messaging system." Rohall+Schiavone may not squarely reach search access control, because the '911 specification itself distinguishes search rules from readership rules: readership governs content "the target received … directly," while "in the case of search rules, the target need not have received the content as part of a message." This is the strongest non‑obviousness foothold in the challenged set. Gomes supplies it: a repository with defined search criteria and rules that "allow authorized users access" to repository data. Motivation: (i) the de‑duplication/central‑repository architecture of Gomes simultaneously addresses Rohall's express concern with storing threads "efficiently in memory"; (ii) enterprise search over a centralized message store is a natural extension of a compliance system, because a retention/access policy that cannot be enforced during search is only half‑implemented.

Claim 27 (email database; each submessage "stored exactly once"). Gomes's de‑duplication teaching — "only one copy of the content is in the database regardless of the location of the file" — maps directly. Motivation: the '911 specification itself states the problem in terms identical to Gomes's solution: "This results in many copies of the same, user‑authored, message in different, unrelated, mail 'snapshots.' Storing multiple copies of the same messages is inefficient and undesirable." When the challenged patent's own Background articulates the problem that the secondary reference solves, the KSR "design incentive" and "known work prompting variations" rationales apply with unusual force.

5. Claims not challenged in IPR2025‑00270

Claims 14, 16, 17, 19, 22, 23, 24, 25, 26, 28, and 29 were not included in the Microsoft petition (the challenged set is 1–13, 15, 18, 20–21, 27). For a complete § 103 picture:

• Claim 14 (team entity; action by one member reflected across the team) — needs an additional reference teaching shared/aggregate state across a user group (e.g., group mailboxes/team folders).
• Claim 16 (allow/deny subject to approval) — Schiavone teaches conditional delivery keyed to recipient profile data; adding an approver step is a routine administrative workflow. Moderate strength.
• Claim 17 (DRM actions: print, save, take offline, copy, reply) — this is the classic least‑argument‑for‑obviousness limitation. Prior‑art DRM/rights‑management references of the 1999–2003 vintage (e.g., "trusted system"/persistent‑protection art) plus Schiavone's rule engine make it a predictable combination, but I have not verified a specific reference in this record.
• Claim 19 (encryption rules) — conventional; the '911 specification itself treats encryption (AES, 128–4096‑bit keys) as off‑the‑shelf, which weakens any nexus argument.
• Claim 22 (geographic groups), 23, 24 (logs), 25, 26 (source/target and temporal versioning) — addressed above under Ground 1.

Related proceeding lead (unverified): IPR2025‑01248 concerns Sterling's U.S. 7,716,217 and asserts grounds over Dumais, Marston (note: the same surname as the '911 inventor, Justin Marston — likely a separate Marston publication), and Kircher/Krug. These references, and Kircher/Krug in particular, are candidates for the DRM/action‑rule and group‑rule dependent claims not challenged here. I flag this as a lead only; I did not verify the identity, dates, or content of those references.

6. Patent Owner's likely rebuttals, and how they fare

7. Bottom line

1. Claims 1–8, 10–13, 15, 18, and 20–21 are more likely than not obvious under pre‑AIA § 103(a) over Rohall (US 2003/0163537) in view of Schiavone (US 2002/0120600). Rohall supplies the container/relational‑reference/thread architecture; Schiavone supplies the rule base, compliance checking keyed to sender/receiver/content, rule precedence, and user profile structure. The KSR rationales — predictable combination of known elements, known technique improving a similar device, and regulatory/market design incentive expressly named in the prior art — are all available and, on the record summarized above, the PTAB found the petition strong enough to institute.

2. Claim 9 (search rules) and claim 27 (single‑instance storage) are obvious over Rohall + Schiavone + Gomes if Gomes qualifies as prior art — the de‑duplication and repository‑access teachings map directly, and the '911 Background's own statement of the redundant‑copy problem supplies the motivation. Verification of Gomes's effective filing date is the pivotal open question for these two claims.

3. Claims 6 and 20 are the weakest links in the Ground 1 chain on the record I could search, because I found no verified disclosure of retention periods or action budgeting in Rohall or Schiavone. The compliance/records‑management motivation is strong, but a specific retention‑policy reference would strengthen the mapping.

4. Claims 14, 16, 17, and 19 were not challenged and would need additional references (team/aggregate state; approval workflows; persistent DRM; encryption policy) — none of which appears technically difficult given the state of the art, but all of which require an evidentiary showing I could not make from the sources available here.

Confidence levels. High confidence in the Rohall/Schiavone disclosure characterizations and in the § 102(b) publication dates of both (verified at https://patents.google.com/patent/US20030163537A1/en, https://FreePatentsOnline.com/y2003/0101065.html, and https://patents.google.com/patent/US20020120600A1). Moderate confidence in the Ground 1/Ground 2 structure as summarized at https://ai-lab.exparte.com/case/ptab/IPR2025-00270/doc/summary/1. Low confidence on Gomes's identity, dates, and content, and on any reference supporting claims 14, 16, 17, and 19 — I was unable to verify these and have said so rather than infer them.