US 8572182

I'll search for authoritative information on US 8572182, including any 2026 litigation activity.

Let me search for more specific litigation history and any 2026 activity.

Let me check for any 2026 Federal Circuit activity and the disposition of the Twitter case.

US Patent 8,572,182 — Analyst Summary

Important method note: I was able to retrieve the authoritative full text of US 8,572,182 (Google Patents) plus litigation-related secondary sources (Docket Alarm, Law360 case summaries, Unified Patents, Justia). I could not execute a direct USPTO PatentCenter / CAFC docket query, so my statements about pending 2026 CAFC activity carry lower confidence and are flagged explicitly below.

1. Bibliographic data (from the patent record)

Note the assignment history recorded: RESEARCH IN MOTION LIMITED → BLACKBERRY LIMITED (2013 change of name) → OT PATENT ESCROW, LLC (2023) → MALIKIE INNOVATIONS LIMITED (2023, with corrective assignments recorded Sept. 2023).

2. Abstract (verbatim)

"To reduce the communications in an IM conversation between two devices, two or more IM events of the conversation at the first device are confirmed by sending to the second device a single IM communication that confirms the most recent of the events. In order that the user of the second device not experience undue delay in receiving the confirmation, the method may be applied where the time interval between any two consecutive ones of the events is less than a predetermined time."

3. Plain-language overview of the claims

The patent has 15 claims: three independent claims (1, 4, 5) plus dependent claims covering the type of status.

Independent Claim 1 — Method (sending device). In a first device, during an IM conversation with a second device:

• send several instant messages to the second device;
• afterward, receive at least a status notification for only one particular message — importantly, received without having previously received a status notification for any of the earlier messages in that group; and
• in response, use a processor to update an internal record to reflect the status of that particular message and to reflect an inferred status for all earlier messages in the conversation sent before it.

The inventive thrust: a single status notification (e.g., for the most recent message) implicitly confirms the status of the earlier ones, saving bandwidth.

Independent Claim 4 — Non-transitory computer-readable medium. Substantively the same send/receive/infer-and-update logic as Claim 1, expressed as computer-executable instructions (a "CRM" claim).

Independent Claim 5 — Communication device. A device with processor, display, keyboard, communication interface (network-capable), and memory, where the memory's instructions cause the device to perform the same three-step send/receive/infer-and-update sequence as Claim 1.

Dependent claims (all of them narrow the status type only — no additional structure):

• Claim 2 / 8 / 12: status is message delivered
• Claim 3 / 9 / 13: status is message read
• Claim 6 / 10 / 14: status is typing started
• Claim 7 / 11 / 15: status is typing stopped

So the independent claims are broad, and the dependent claims simply enumerate the four notification categories the specification discusses (Message_Delivered, Message_Read, Typing_Started, Typing_Stopped).

4. Litigation / docket status

Known district court matter (2019): US 8,572,182 was one of the patents asserted in BlackBerry Limited v. Twitter, Inc., No. 2:19-cv-01444 (C.D. Cal.), filed 2019-02-27 and assigned to Judge George H. Wu (case transferred from Judge Fitzgerald per C.D. Cal. General Order 19-03, related to 2:18-cv-01844 and 2:18-cv-02693). Google Patents' litigation overlay also lists California Central District Court case 2:19-cv-01444 as a family litigation. The complaint's description of the messaging patents matches this patent's subject matter ("improved techniques for determining whether a recipient has read messages in a conversation by inferring the status of one or more of the messages, thereby reducing data transmissions").

Disposition (per Law360 case summaries, medium confidence as to which claims):

• Oct. 2, 2019 — the California federal judge "declared claims from six BlackBerry patents invalid under ... Alice," affecting BlackBerry's cases against Facebook, Twitter, and Snap.
• Nov. 1, 2019 — BlackBerry "voluntarily dropped infringement allegations against Twitter ... involving three of its targeted ad and mobile messaging patents."
• I could not confirm from the retrieved sources whether the '182 patent's claims were among the six invalidated, the three voluntarily dropped, or neither. Treat any specific outcome for the '182 patent as unverified.

Family litigation (Darts-IP) is also flagged on the Google Patents page, consistent with the Twitter action.

5. 2026 CAFC docket search — uncertainty flagged

• I searched for a Federal Circuit appeal specifically involving 8,572,182 and found no 2026 CAFC docket, opinion, or oral-argument entry tied to this patent number.
• My searches surfaced only unrelated 2026 CAFC activity (e.g., FedEx v. Qualcomm, Netlist appeals, Contour IP v. GoPro), none of which mentions the '182 patent.
• The current patent owner entity, Malikie Innovations Ltd., is actively litigating in 2026 (e.g., cases against Hyundai, Honda, MARA Holdings, Core Scientific, and an IPR involving US 11,119,756), and its portfolio includes BlackBerry-origin assets — but none of the 2026 dockets I retrieved name the '182 patent.

Bottom line on 2026: I have no authoritative evidence of a 2026 CAFC docket for 8,572,182. This is a negative finding from limited sources, not a certified absence. If you need a definitive answer, a direct PACER/CAFC CM/ECF docket query on the patent number (and on Malikie Innovations as appellant/appellee) would be required; I do not want to represent that the docket is clean when I could not query it directly.

I'll research litigation involving US Patent 8572182 specifically.

Let me gather case-specific details.

Let me verify the disposition of the Twitter case and check for any other cases.

Litigation Involving U.S. Patent No. 8,572,182

Patent identified: US 8,572,182 B2, "Handling notifications in instant messaging systems," filed July 21, 2006, issued October 29, 2013, appl. no. 11/459,047, inventor Gerhard Dietrich Klassen, originally assigned to Research In Motion Limited (later BlackBerry Limited), currently shown as Malikie Innovations Limited (via OT Patent Escrow, LLC).

Bottom line: exactly one U.S. district court case is known to have asserted the '182 patent — BlackBerry Limited v. Twitter, Inc., No. 2:19-cv-01444 (C.D. Cal.). It was settled and dismissed with prejudice in January 2020. I found no other litigation asserting this specific patent (including none by Malikie Innovations).

1. BlackBerry Limited v. Twitter, Inc.

Procedural history relevant to the '182 patent:

• Oct. 1–2, 2019 — Final Ruling on Twitter's Rule 12(b)(6) motion to dismiss (Dkt. 51). The court held Claims 1 and 4 of the '182 patent drawn to an abstract idea under Alice/Mayo Step One, with no well-pled allegations of an inventive concept, and granted Twitter's motion as to those claims. The court characterized Claims 1 and 4 of the '182 patent as "highly reminiscent of claims in one of BlackBerry's other patents" it had already found ineligible. The court concurrently dismissed claims on the '929, '351 and '777 patents; claims on the '120, '089 and '059 patents survived in whole or in part.
• Oct. 2019 — BlackBerry filed a Notice of Voluntary Dismissal Without Prejudice (Dkt. 55) of the remaining '120, '089 and '059 claims under FRCP 41(a)(1).
• Dec. 24, 2019 — The parties filed a Joint Stipulation to Vacate Order and Dismiss With Prejudice All Claims and Counterclaims, stating they had "reached a settlement to dismiss the entirety of this action with prejudice," with each side bearing its own costs and attorneys' fees.
• Jan. 2, 2020 — The court entered the Order Granting Joint Stipulation (Dkt. 59), which (1) vacated the Dkt. 51 order "invalidating patent claims of and dismissing infringement claims related to U.S. Patent Nos. 8,676,929, 8,296,351, 8,572,182, and 8,825,777," and (2) dismissed all claims and counterclaims with prejudice. The AO 120 report filed with the USPTO (Jan. 3, 2020) records the patents including 8,572,182 (dated 10/29/2013) and the decision as "Order of Dismissal."

Important nuance: Because the Dkt. 51 order was vacated as part of the settlement, the district court's § 101 invalidity holding as to the '182 patent no longer stands. No merits judgment on validity or infringement of the '182 patent was entered, and there was no appeal. The dismissal with prejudice is a final, non-appealable resolution between those two parties only.

Primary sources:

• Joint stipulation (Dec. 24, 2019): https://www.docketalarm.com/cases/California_Central_District_Court/2--19-cv-01444/BlackBerry_Limited_v._Twitter_Inc/docs/58.pdf?download=true
• Vacatur/dismissal order (Jan. 2, 2020): https://storage.courtlistener.com/recap/gov.uscourts.cacd.[738215](/patent/738215)/gov.uscourts.cacd.738215.59.0.pdf
• MTD ruling (Dkt. 51), discussing the '182 patent: https://www.docketalarm.com/cases/California_Central_District_Court/2--19-cv-01444/BlackBerry_Limited_v._Twitter_Inc/docs/51.pdf?download=true
• AO 120 report listing 8,572,182: https://www.docketalarm.com/cases/California_Central_District_Court/2--19-cv-01444/BlackBerry_Limited_v._Twitter_Inc/docs/60.pdf?download=true
• Unified Patents case page (the litigation link carried on the Google Patents record): https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/2%3A19-cv-01444
• RPX Insight docket summary: https://insight.rpxcorp.com/litigation/cacdce-738215-blackberry-v-twitter

2. Related cases that did NOT assert the '182 patent

These are worth distinguishing, because they are frequently conflated with the Twitter case:

• BlackBerry Limited v. Facebook, Inc.; WhatsApp, Inc.; Instagram, Inc.; Instagram, LLC, No. 2:18-cv-01844-GW-KSx (C.D. Cal.) — the lead consolidated "Facebook Case." BlackBerry asserted nine patents; the final election of asserted claims lists the '961, '634, '713, '173, '236, '250, '120, '351 and '929 patents — the '182 patent is not among them. Settled and dismissed (stipulation dated Feb. 13, 2021). Source: BlackBerry's Final Election of Asserted Claims.
• BlackBerry Limited v. Snap Inc., No. 2:18-cv-02693-GW-KSx (C.D. Cal.) — related case; no indication the '182 patent was asserted.
• BlackBerry v. Avaya Inc., No. 3:16-cv-2185 (N.D. Tex., July 27, 2016) and BlackBerry v. BLU Products, No. 1:16-cv-23535 (S.D. Fla., Aug. 16, 2016) — BlackBerry enforcement campaigns, but the patents identified in the record I reviewed are the '961 and '713 (continuation) patents, not the '182 patent. I did not find the '182 patent in either case, but I have not independently verified the full infringement contentions in those two matters.

IPR/PTAB: Twitter filed inter partes reviews against several BlackBerry patents in the same campaign (e.g., IPR2019-01511 on the '929 patent; IPR2019-00923 on the '961 patent), and those were terminated following the settlement. I did not locate any IPR or other post-grant proceeding challenging U.S. 8,572,182. Treat that as a negative finding from my searches rather than a verified absence — the PTAB record would need to be checked directly (I could not complete that check here).

Foreign litigation: The Google Patents record flags the family (Darts-ip family 39050777) as having "first worldwide family litigation," and the family includes Canadian counterpart CA 2,594,817 (granted as CA2594817C). That flag may reflect foreign counterpart proceedings; I was not able to identify any specific non-U.S. case involving the '182 patent itself.

Caveats

1. Literal identification. All results above are for U.S. Patent No. 8,572,182 specifically. Several superficially similar identifiers appear in the search results and must not be confused with it — e.g., U.S. Patent No. 9,539,218 (Bayer/Janssen rivaroxaban ANDA litigation in D. Del.), U.S. Reissue Patent RE47,218 (Masimo v. Sotera), and IPR petitions referencing "the '218 Patent" in the Comcast/Rovi context. None of those concern US 8,572,182.
2. Family patents. The '182 patent's own family includes continuations US 9,219,703 (from application 13/238,839, a division) and US 9,264,386 (from application 14/045,039, a continuation). Litigation naming those sibling patents would not constitute litigation of the '182 patent, and I found none.
3. Post-2023 ownership. The '182 patent was transferred to OT Patent Escrow, LLC (effective March 20, 2023) and then to Malikie Innovations Limited (effective May 11, 2023). My searches returned no assertion of the '182 patent by Malikie in any district court. Malikie has been an active filer on other portfolios, so if you need certainty, a fresh PACER docket search on the patent number and on Malikie Innovations as plaintiff would be prudent.
4. Source reliability. The strongest evidence above comes from the actual court filings (stipulation, vacatur order, MTD ruling, AO 120 form) and the parties' own briefs. Secondary aggregators (Unified Patents, RPX Insight, Docket Alarm, UniCourt) were used to corroborate case metadata. I have not done a manual PACER pull, so a small risk remains that an additional short-lived or sealed case exists that is not reflected in these sources.

Answer to your direct question: Yes, at least one litigation is known. Only one — BlackBerry Limited v. Twitter, Inc., No. 2:19-cv-01444-GW-KSx (C.D. Cal., filed Feb. 27, 2019) — and it ended in a January 2, 2020 settlement dismissal with prejudice, with the court's § 101 invalidity ruling on the '182 patent vacated as part of that settlement.

I'll start by verifying the canonical "no PTAB proceedings" finding against public sources, and check for any IPR/PGR/CBM tied to this patent number or its family.

Searches returned unrelated hits (mostly a different patent, 9,858,218). Let me refine to this patent number and its owner/petitioners.

I have enough to answer. Note: I received a system notice that I've reached the search-step limit, so the below rests on the canonical structured data in the prompt plus the searches already executed. I flag the one place where my search surfaced something material.

Proceedings overview

Total AIA trial proceedings on US 8,572,182: 0. The structured "PTAB proceedings on file" block (USPTO Open Data Portal) returns no IPR, PGR, or CBM proceeding naming this patent as the subject patent, and my independent searches on the patent number, its title, and its owners (BlackBerry / Malikie) surfaced no petition, institution decision, FWD, or appeal naming the '182 — so the breakdown is 0 active / 0 claims invalidated by the Board / 0 sustained / 0 settled / 0 institution-denied. The defensive posture this yields is neither "hardened by surviving IPRs" nor "claims canceled": the patent has simply never been challenged at the PTAB, so the Board has never adjudicated any of claims 1–15, and there is no PTAB-based invalidity record to lean on or to fear. All of the invalidity traction on this patent to date comes from a district court § 101 ruling, not from an AIA trial — see the "Related matters" section below.

Per-proceeding detail

None. There is no proceeding to report against 8,572,182. Rather than fabricate docket entries, here is what I verified and what I could not verify.

No IPR / PGR / CBM — verification notes

• Type: N/A
• Filed: N/A
• Status: No AIA trial proceeding on file (per USPTO ODP structured data; corroborated by web search).
• Judge panel: N/A
• Petition grounds: N/A
• Institution decision: N/A
• Final Written Decision: None — the Board has never issued an FWD on any claim of the '182 patent.
• Settlement / termination: N/A
• Appeal: No PTAB FWD exists to appeal to the Federal Circuit; no CAFC docket tied to this patent's PTAB history.
• Defensive value: Because no IPR was ever filed, no § 315(e)(2) estoppel has attached to any ground, and no claim of the '182 has been canceled by the Board. A defendant cannot point the judge to a PTAB outcome — there isn't one.

Related PTAB matters that do not involve the '182 patent (common mis-attribution risk)

These are worth stating explicitly because the same litigation campaign (BlackBerry's 2018–2019 messaging suits against Facebook and Twitter) generated PTAB work on sibling BlackBerry messaging patents — but the dockets below name different patents, and none of them is 8,572,182:

• IPR2019-01511 — Twitter, Inc. v. BlackBerry Limited — subject patent 8,296,351, not the '182. The petition's exhibit list is dominated by the parallel C.D. Cal. litigation (Facebook/Snap/Twitter complaints, the Facebook #157 Markman order, etc.). Source: https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1528641](/patent/1528641)/ (Twitter v. BlackBerry, IPR2019-01511). Twitter separately petitioned on 8,676,929.
• IPR2019-00899 — Facebook, Inc., Instagram, LLC & WhatsApp Inc. v. BlackBerry Limited — subject patent 8,301,713, not the '182. Source: https://www.docketalarm.com/cases/PTAB/IPR2019-00899/ .
• A PTAB petition document (Paper 1525284) filed in that campaign quotes the C.D. Cal. order on the '182 patent. That document is not a proceeding on the '182 — it merely reproduces the district court's § 101 ruling as litigation background. I cite it only because it is the clearest public quote of the § 101 disposition of this patent's claims.

No CBM review was possible/attempted here in any event: the '182 is a mobile-IM-notification patent, not a "covered business method" under AIA § 18 (financial-products) subject matter.

The invalidity that actually exists on this patent is a district-court § 101 ruling (not PTAB)

This is the single most important thing for a defendant, and it is where my search produced new, claim-specific information relative to the earlier summary:

• In BlackBerry Ltd. v. Twitter, Inc., No. 2:19-cv-01444 (C.D. Cal.) (Google Patents litigation overlay), the court granted Twitter's motion as to this patent. Quoting the order (as reproduced in the PTAB petition document at https://ptacts.uspto.gov/ptacts/public-informations/petitions/1525284/):

"As mentioned, the Court finds Claims 1 and 4 of the '182 Patent highly reminiscent of claims in one of BlackBerry's other patent[s] … Because the Court finds that Claims 1 and 4 of the '182 Patent are drawn to an abstract idea and there are no well-pled factual allegations in the FAC to support an assertion that the claim components, considered individually and as an ordered combination, recite significantly more than routine, conventional, or well-understood material, the Court would GRANT Twitter's motion as to Claims 1 and 4 of the '182 Patent and accordingly find that BlackBerry's infringement claims with respect to the '182 Patent must be dismissed."

Cautions on that quote (do not over-read it):

• It is a § 101 patent-eligibility ruling by a district court, not a PTAB claim cancellation. The claims remain issued; the USPTO has not canceled anything.
• The order addresses claims 1 and 4 only. Independent claim 5 (the device claim) is not named in that passage — so I cannot say claim 5 was adjudicated. Dependent claims 2, 3, 6–15 were likewise not addressed there.
• I could not confirm from the sources retrieved whether this order became final, was entered as a judgment, or was mooted by BlackBerry's later voluntary dismissal of Twitter (Law360 reported on 2019-11-01 that BlackBerry dropped certain Twitter messaging/ad patents; I could not confirm the '182 was among the dropped ones). Treat "claims 1 and 4 of the '182 are dead" as a favorable, non-final district-court ruling in a case that may have settled out, not as a cancellation.
• I also could not confirm whether this § 101 ruling was ever appealed to the Federal Circuit; my earlier 2026 CAFC search found no docket naming the '182.

Strategic summary

Claim status. No claim of US 8,572,182 is canceled (the PTAB has never acted) and no claim is sustained by the Board either. Claims 1 and 4 carry a district-court § 101 invalidity ruling from the Twitter case; claims 2, 3, 5, 6–15 are, as far as I can verify, untested — claim 5 (device) in particular was not in the quoted passage. Practically: any contemporary assertion of this patent would most plausibly rest on claim 5 (the apparatus claim) or the untested dependents, because the two method/CRM independents already have an adverse § 101 ruling on the record from a co-equal district court.

Estoppel landscape. There is no § 315(e)(2) estoppel on any claim, because no IPR/PGR was ever instituted. That cuts both ways: a defendant is not barred from raising any prior-art ground in an IPR or in district court, but also has no prior PTAB narrowing to leverage. Because no petitioner ever ran the IPR gauntlet, all prior art — including the very references an accused infringer would want — remains fully available. Note, however, that the district-court § 101 posture may make an IPR less attractive than a Berkheimer-style eligibility defense, since § 101 is not a ground available in IPR (35 U.S.C. § 311(b) limits IPR to §§ 102/103 on patents and printed publications).

Pattern signals. (1) The same litigation campaign generated multiple IPRs against sibling BlackBerry messaging patents by Twitter (e.g., IPR2019-01511, 8,296,351) and Facebook (IPR2019-00899, 8,301,713) — but not against the '182. That asymmetry suggests the defendants chose to attack the '182 via § 101 in court rather than via the PTAB; it is a strong signal that a § 101 attack is the proven path on this patent. (2) No defensive aggregator has touched this patent: Unified Patents has filed ex parte reexaminations against other Malikie/BlackBerry assets (e.g., US 10,779,156 on 2025-10-03; US 7,372,960; US 12,395,899; US 10,778,989) — none against the '182, and EPRs are not AIA trials regardless. (3) No evidence the patent owner has litigated this patent to a PTAB or CAFC appeal.

Confidence / caveats. The "zero proceedings" finding is well-supported by the canonical ODP block and my searches, but ODP ingest can lag; treat it as a strong negative finding, not a certified absence. A definitive check is a direct PTAB E2E docket query on "8,572,182" and a PACER/CAFC docket query on Malikie Innovations as party.

Recommended next steps

1. If you are a defendant facing assertion of the '182: do not spend IPR money first. The record already contains a district-court § 101 dismissal of claims 1 and 4 (C.D. Cal. 2:19-cv-01444). Pull the actual order (C.D. Cal., Judge George H. Wu) and confirm its finality/procedural posture, then build a § 101 motion on it — especially if the plaintiff asserts claim 1 or 4. Link the ruling and quote the disposition above.
2. If the plaintiff asserts claim 5 or an untested dependent: § 101 precedent from the Twitter order is only persuasive, not dispositive, and claim 5 was not addressed. In that scenario an IPR under §§ 102/103 is available with zero estoppel risk (no prior proceeding), and the full prior-art universe — including the IM-prior-art landscape — is open. Check whether the same prior art was before the examiner (relevant to a discretionary § 325(d) argument the patent owner may raise).
3. Confirm the negative: run PTAB E2E (https://ptacts.uspto.gov/) for "8572182" and CourtListener (https://www.courtlistener.com/) for the C.D. Cal. docket and any CAFC appeal, and pull the docket entry for the § 101 ruling to nail down date, scope (claims 1/4 vs. 5), and finality.
4. Watch the Malikie reexamination campaign: Unified is actively attacking Malikie/BlackBerry-origin assets via EPR. If the '182 is ever asserted by Malikie against a well-resourced target, an EPR or IPR becomes likely — but as of now there is nothing to track.

Bottom line for the report: US 8,572,182 has zero AIA trial history; the "invalidity story" on this patent lives in district court (§ 101, claims 1 and 4), not at the PTAB. Nothing has been canceled, nothing has been sustained, and no estoppel has attached.

I'll research the assignment chain and the entities involved before drafting.

Now let me pin down the correspondent of record and the inventor's status.

Assignment & Ownership Analysis — US 8,572,182

Source note: The reel/frame entries below are drawn from the Google Patents "Legal Events" record for this patent (authoritative for the US assignment chain as indexed). I was unable to run a direct USPTO Assignment Center query in this session, so the USPTO-side correspondent of record field is not captured in my data and is flagged wherever it matters. Everything else (conveyance type, assignor, assignee, execution/recording dates, reel/frame) is taken from the recorded events.

Inventors

Unusual-pattern check: I found no evidence that Klassen departed RIM within 12 months of filing, and I could not verify his later employment history in this session. There is therefore no inventor-departure fire-sale signal here — the patent stayed with the original assignee for ~17 years. (Do not read the absence of evidence as proof of continuing employment; it is simply unverified.)

Original assignee

• At issue: Research In Motion Limited (RIM), Waterloo, Ontario. Renamed BlackBerry Limited by change of name effective 2013-07-09 (Reel 030918/0470). Listed on the patent as assignee at grant = BlackBerry Limited.
• Line of business: RIM/BlackBerry was the operating manufacturer of the BlackBerry smartphone and the BlackBerry Messenger (BBM) IM service. BBM is the product that plausibly embodies the claims: BBM exposed exactly the notification vocabulary this patent discusses — message delivered ("D") and read ("R") indicators and "contact is typing…" status. That is a strong (if not formally proven here) product-embodiment link.
• Current status: Operating company, still public (NYSE/TSX: BB), today focused on cybersecurity/IoT software. It is not dissolved, acquired, or in bankruptcy. It monetized its legacy portfolio as a non-core asset sale (see below), not because of insolvency.

Assignment timeline

All seven recorded events. Dates are executed / recorded as shown in the record.

• 2006-07-20 (executed) / recorded 2006-07-21 — Reel 017974/0051

  • Conveyance: Assignment ("ASSIGNMENT OF ASSIGNORS INTEREST")
  • Assignor: Gerhard Dietrich Klassen
  • Assignee: Research In Motion Limited
  • Correspondent: not exposed in the retrieved record — need USPTO Assignment Center to confirm
  • Context: Employee invention assignment / initial title vesting in the original operating-company assignee.

• 2013-07-09 (executed) / recorded 2013-07-31 — Reel 030918/0470

  • Conveyance: Change of Name
  • Assignor: Research In Motion Limited
  • Assignee: BlackBerry Limited
  • Correspondent: not exposed — confirm via Assignment Center
  • Context: Internal corporate rename only (RIM → BlackBerry); no change in beneficial ownership.

• 2023-03-20 (executed) / recorded 2023-04-27 — Reel 063471/0474

  • Conveyance: Assignment ("ASSIGNMENT OF ASSIGNOR'S INTEREST")
  • Assignor: BlackBerry Limited
  • Assignee: OT Patent Escrow, LLC (Illinois; 200 West Madison, Chicago — later records show Suite 1020 / 37th Floor)
  • Correspondent: not exposed. Lead only (unverified for this patent): a structurally identical HPE→escrow deed in a parallel KPI portfolio lists Joel Lutzker as the OT Patent Escrow signatory — I could not confirm he is the recorded correspondent on this reel/frame.
  • Context: Transfer into an escrow conduit — part of the March 2023 bulk BlackBerry→Malikie/KPI patent sale; escrow entity holds title pending onward assignment to the purchaser.

• 2023-05-11 (executed) / recorded 2023-06-16 — Reel 064015/0001

  • Conveyance: Nunc Pro Tunc Assignment
  • Assignor: OT Patent Escrow, LLC
  • Assignee: Malikie Innovations Limited (Dublin, Ireland)
  • Correspondent: not exposed
  • Context: Escrow release → transfer to the asserting NPE. Retroactive ("nunc pro tunc") to the 2023-05-11 closing.

• 2023-05-11 (executed) / recorded 2023-06-19 — Reel 064066/0001

  • Conveyance: Nunc Pro Tunc Assignment
  • Assignor: BlackBerry Limited (direct)
  • Assignee: Malikie Innovations Limited
  • Correspondent: not exposed
  • Context: Second, redundant chain of title straight from the seller to the purchaser — a belt-and-suspenders standing record alongside the escrow chain.

• 2023-05-11 (executed) / recorded 2023-09-05 — Reel 064807/0001

  • Conveyance: Corrective Assignment (to correct application no. 12,817,157 mistakenly included in Reel 064015/0001)
  • Assignor: OT Patent Escrow, LLC
  • Assignee: Malikie Innovations Limited
  • Correspondent: not exposed
  • Context: Housekeeping/standing cleanup on the escrow→Malikie link.

• 2023-03-20 (executed) / recorded 2023-09-05 — Reel 064806/0669

  • Conveyance: Corrective Assignment (removes app. no. 12,817,157 wrongly listed on the Reel 063471/0474 cover sheet)
  • Assignor: BlackBerry Limited
  • Assignee: OT Patent Escrow, LLC
  • Correspondent: not exposed
  • Context: Housekeeping/standing cleanup on the BlackBerry→escrow link.

Note on the double-chain structure: Malikie took title twice — once via escrow (064015/0001) and once directly from BlackBerry (064066/0001), then filed two corrective deeds in September 2023. This four-instrument re-papering of a single May 2023 closing is characteristic of deals structured for later assertion, where clean, unbroken chain-of-title is a litigation prerequisite.

Timeline diagram

timeline
    title Ownership of US 8572182
    2006 : Filed by Research In Motion
         : Inventor Klassen assigns to RIM
    2013 : Name changed to BlackBerry Limited
    2019 : Asserted against Twitter in California
    2023 : Transferred to OT Patent Escrow LLC
         : Escrow releases to Malikie Innovations
         : Direct BlackBerry to Malikie assignment
         : Two corrective assignments recorded

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT. Operating company BlackBerry Limited assigned the patent to OT Patent Escrow, LLC (Reel 063471/0474, executed 2023-03-20), an escrow/licensing vehicle at a Chicago office-suite address (200 West Madison). Title then passed to Malikie Innovations Limited, a single-purpose Irish company (The Glasshouses GH2, 92 Georges Street Lower, Dun Laoghaire) with no products in commerce (Reels 064015/0001, 064066/0001). Malikie is a plaintiff-only entity; it is described in its own pleadings and by third parties purely as an asserting trustee/successor-in-interest, not a manufacturer.

2. Known asserter in the chain — PRESENT. The current assignee, Malikie Innovations Limited, is expressly characterized by Unified Patents as "an NPE and entity of Key Patent Innovations Limited," and RPX tracks its campaigns (e.g., the Nintendo suit, 2:24-cv-01490). Malikie/KPI is a recognized high-frequency asserting family, even though it is not on the older Acacia/Marathon/IV rosters.

3. Repeat correspondent across the chain — UNCLEAR (flagged). The retrieved record does not expose the correspondent-of-record field, so I cannot state that the same attorney filed all seven reel/frame entries. One concrete lead: a parallel KPI-portfolio escrow deed (HPE→OT Patent Escrow) is signed by Joel Lutzker for OT Patent Escrow, LLC — suggesting a recurring escrow-entity signatory, but this is not confirmed as the recorded correspondent for US 8,572,182's reels. To close this signal, pull the correspondent field for Reels 063471/0474, 064015/0001, 064066/0001, 064806/0669, 064807/0001 in USPTO Assignment Center.

4. Cascading transfers — PRESENT. Four recorded instruments relating to one transaction, spread over ~5.5 months (executions March–May 2023; recordings April–September 2023), routed through a chained escrow LLC: BlackBerry→Escrow→Malikie plus a redundant direct BlackBerry→Malikie deed and two corrective deeds.

5. Pre-litigation transfer — PRESENT (at portfolio level). The controlling transfers (Reels 063471/0474, 064015/0001, 064066/0001) executed 2023-03/05, and Malikie's assertion campaign against wireless/messaging/networking defendants began in 2023–2024 (e.g., notice letters Aug. 2023/Aug. 2024; Nintendo suit Sept. 2024). Caveat: I could not confirm that the '182 patent specifically was asserted post-transfer — the prior analysis section notes the '182 was asserted pre-transfer by BlackBerry v. Twitter, 2:19-cv-01444 (C.D. Cal.), and that the 2019 Alice outcome for this patent is unverified. So the "pre-suit" timing is established for the deal, not for this patent's individual assertion.

6. Bankruptcy fire-sale — NOT PRESENT. BlackBerry's transfer was a solvent, board-approved non-core asset sale, disclosed via press release (2023-03-21) and Form 8-K filed 2023-05-11 ("Item 2.01 Completion of Disposition of Assets"). No Chapter 7/11 proceedings.

7. Privateering — PRESENT. BlackBerry sold ~32,000 non-core patents to Malikie/KPI for consideration up to $900M — $170M at closing (2023-05-11) + $30M by the third anniversary + an 8%–50% share of monetization profits (capped at $700M) — and took a license back. An operating company selling to an NPE while retaining a profit-sharing upside and a license-back is the textbook privateering structure (the seller benefits from the NPE's assertions without itself suing).

8. Defensive aggregator — NOT PRESENT. The chain terminates at Malikie Innovations Limited / Key Patent Innovations Limited (KPI), an asserter — not RPX, AST, LOT, or OIN. The patent has not been neutralized.

(Contextual note: a 2022 predecessor deal to sell the same portfolio to Catapult IP Innovations Inc for $600M reportedly fell through for delay; the March 2023 Malikie/KPI deal replaced it. Direction of travel is unchanged — operating company offloading legacy assets into an enforcement vehicle.)

Verdict

NPE — high confidence.

The record shows an operating company (BlackBerry Limited) conveying the patent through an escrow conduit to a single-purpose Irish asserting entity via Reel 063471/0474 (executed 2023-03-20) and Reels 064015/0001 / 064066/0001 (executed 2023-05-11), followed by corrective reels 064806/0669 and 064807/0001. Two or more strong signals are present simultaneously: a shell/escrow transfer to a no-product licensee, a current assignee that Unified Patents classifies outright as "an NPE," cascading chained-LLC transfers in under 24 months, and a privateering payout structure (BlackBerry retains a license-back plus up to $700M of profit royalties). The one signal I could not substantiate — a recurring correspondent-of-record — is a data gap, not a negative finding, and does not change the verdict.

Verify at: USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search property 8,572,182; mirror index at https://assignment.uspto.gov/patent/index.html). To fully resolve signal #3, capture the correspondent field on Reels 063471/0474, 064015/0001, 064066/0001, 064806/0669, and 064807/0001. Cross-check the privateering terms against BlackBerry's 8-K of 2023-05-11 (SEC EDGAR, CIK 1070235) and the 10-K Exhibit 10.11 Patent Sale Agreement.

Correction/flag for the earlier section: the prior summary listed the current assignee as "Malikie Innovations Ltd (listing)." The assignment record confirms Malikie Innovations Limited is the current owner of record and is wholly owned by Key Patent Innovations Limited, which is in turn owned by New PP Licensing LLC (per Malikie's own corporate disclosure in the Match Group litigation) — with BlackBerry additionally named on a supplemental disclosure list.

I'll analyze the prior-art citations for US 8,572,182. Let me first verify the patent record and gather details on the most relevant cited references.

Good detail on the key IM-focused references. Let me verify the remaining IM-related citations and the non-patent literature.

Prior-Art Analysis for US 8,572,182

A. Verification and method note

Patent verified. US 8,572,182 B2 ("Handling notifications in instant messaging systems"), App. No. 11/459,047, filed/priority 2006-07-21, granted 2013-10-29, inventor Gerhard Dietrich Klassen. Authoritative full text and the complete citation record were retrieved from Google Patents (https://patents.google.com/patent/US8572182/en). I did not run a live USPTO PatentCenter/PAIR query in this pass — the citation list below is the "Patent Citations" and "Non-Patent Citations" record printed on the face of the patent as mirrored by Google Patents. That record is the legally operative prior-art-of-record (26 US patent documents + 4 non-patent items as mirrored; Google's table groups 24 in one block plus two unstarred items).

Rule applied: I interpret every number literally. The family members US 9,219,703 B2 and US 9,264,386 B2 are separate patents and are not treated here as prior art against the '182 patent.

Critical legal framing before the reference-by-reference mapping. Under 35 U.S.C. § 102 a reference anticipates a claim only if it discloses every limitation, arranged as in the claim. Independent claims 1, 4 and 5 all require the same three-step core (per the earlier claim overview): (L1) a first device in an IM conversation; (L2) sending a plurality of instant messages; (L3) thereafter receiving a status notification for only a particular one of those messages without having previously received a status notification for any earlier one; and (L4) in response, updating an internal record to reflect the status of that message and an inferred status for all earlier messages of the conversation. Dependent claims 2–3, 6–7 (etc.) add no structure — they only recite the status type (delivered / read / typing-started / typing-stopped) while incorporating all of claim 1's limitations. Therefore no dependent claim can be anticipated by a reference that does not first anticipate claim 1. This materially narrows what the cited art can actually anticipate, and I flag it throughout.

Prior-art dating. All 26 cited documents carry a filing/priority date before 2006-07-21 and are therefore facially available as § 102(a)/(b) art (if published before the critical date) or § 102(e) art (US patents/applications filed before, published after). Several were published after 2006-07-21 (e.g., all the 2008/2009 US publications) and qualify only as § 102(e) art as of their earlier filing dates.

The patent itself supplies the rationale for the invention: "Notifications sent in an IM system occupy bandwidth that would otherwise be available for other communications."

B. Most relevant prior art (Tier 1 — IM status/notification art)

1. US 2002/0026483 A1 — Isaacs et al. (closest IM delivery-status art)

• Full citation: US 2002/0026483 A1, "System, method and apparatus for communicating via instant messaging," Ellen Isaacs et al.; pub. 2002-02-28; priority 2000-02-22 (parent of US 7,805,487 B2).
• Description: Distributed IM system (PDAs, wireless phones, PCs) using earcons and text IMs. Message status indicators show a message as pending vs received, driven by an acknowledgement (ACK) that carries the unique sequential number of the original message; a "message listing" at the sender is updated on receipt of the ACK, and a listing at the receiver prevents duplicates. (https://patents.google.com/patent/US20020026483)
• Potential § 102 mapping: Implicated mainly for claims 2 / 8 / 12 (status = message delivered) and the L4 "internal record" concept (its "message listing"). It discloses sending multiple IMs and receiving a delivery confirmation, but the confirmation is per-message (indexed by sequence number) — it does not disclose receiving a notification for only a particular message without any prior notification for earlier messages, nor inferring status for all earlier messages. Predictive strength: not a clean § 102 anticipation of claim 1/4/5 (or the dependents, per the rule above); strongest as a § 103 combination reference on the "delivered" aspect.

2. US 2008/0263167 A1 & US 7,975,012 B2 — Jennings et al. (closest IM read-status/inference art)

• Full citation: US 2008/0263167 A1, "Method and apparatus for inferring read status of instant messages," Raymond B. Jennings III et al.; pub. 2008-10-23; filed 2005-02-01 (Ser. No. 11/048,495; continuation filed 2008-06-30); granted as US 7,975,012 B2.
• Description: Analyzes window/focus/user-input criteria on the receiver device to compute a probability/ranking that the IM has been viewed, then sends a message to the sender reporting that view status, without explicit user action. Expressly contrasts itself with prior systems that only confirm "received by the server" or "currently typing." (https://patents.google.com/patent/US20080263167 ; granted text US7975012)
• Potential § 102 mapping: Directly on point for the concept of inference of read status and for the status type in claims 3 / 9 / 13 (message read); also loosely relevant to L4's "inferred status." It does not disclose L3 (status notification for only a particular message, none beforehand for earlier ones) or L4's inference of status for all earlier messages in the conversation — it infers per-message. Predictive strength: highest of the US references as a § 102/§ 103 reference for the "read/inferred status" concept, but it does not anticipate the independent claims; it would not, standing alone, anticipate the dependent claims either.

3. US 2008/0233926 A1 — Eason et al. (closest status-notification-to-sender art)

• Full citation: US 2008/0233926 A1, "Electronic Communications Device Status Determination," Wendy Eason et al.; pub. 2008-09-25; priority 2003-06-20.
• Description: Uses an HLR/status database to track the operational status (on/off, in/out of range) of a receiving wireless device and returns a status message to the calling/sending party (e.g., "called device off"), including visual/tone notification. (https://patents.google.com/patent/US20080233926A1)
• Potential § 102 mapping: Touches L3's "notification of the status" and the system architecture (mobile device, network, status DB) of claim 5, but the "status" is device operational status, not message delivered/read/typing, and there is no inference across a group of earlier messages. Predictive strength: weak for claims 1/4/5; not anticipatory.

4. US 2009/0157816 A1 — Pattan (IM transmission status in a mobile terminal)

• Full citation: US 2009/0157816 A1, "System and method for instant message transmission in mobile communication terminal," Basavaraj Jayawant Pattan; pub. 2009-06-18; priority 2005-04-08.
• Description: IM transmission in a mobile communication terminal, directed to conveying message/transmission status in the mobile environment.
• Potential § 102 mapping: Relevant by subject matter to IM status notification on a mobile device (claim 5 architecture; status types). I could not retrieve the full text in this pass (search budget exhausted), so I flag low confidence on any specific claim mapping. Treat as a § 102(e) reference (filed 2005-04-08) of plausible but unverified relevance.

C. Non-patent literature (Tier 1 — arguably the single most relevant item)

Isomaki & Rosenberg, IETF draft-ietf-simple-messaging-requirements-00 (SIMPLE WG)

• Full citation: M. Isomäki & J. Rosenberg, "Advanced Instant Messaging Requirements for the Session Initiation Protocol (SIP)," IETF Internet-Draft draft-ietf-simple-messaging-requirements-00, June 22/23, 2006 (Expires Dec. 24, 2006). (https://datatracker.ietf.org/doc/html/draft-ietf-simple-messaging-requirements-00)
• Description: Defines requirements for advanced SIP IM, including:
  • "Is-Composing" indicators = typing notifications: REQ-COMP-5 "the sender has begun composing a message" and REQ-COMP-6 "the sender has stopped composing a message" (i.e., Typing_Started / Typing_Stopped);
  • IM Disposition Notifications (IMDN) = delivery/read receipts;
  • REQ-COMP-8 synchronization of the indicator with the message stream; and an open issue on "aggregation" of notifications.
• Potential § 102 mapping (strongest single reference): Directly covers the status types in dependent claims 6/7/10/11/14/15 (typing started / typing stopped) and 2/3/8/9/12/13 (delivered / read). Its discussion of IMDN aggregation and REQ-COMP-8 (indicator synchronized with the message stream so the recipient can tell which came first) is conceptually close to the L3/L4 notion that a later communication can subsume an earlier event. Predictive strength: this is the reference most likely to have driven the examiner's art; as a printed publication dated ~one month before the 2006-07-21 filing it is § 102(a)/(b) art on the notification categories. It is plausible § 102/§ 103 art against the typing/read/delivered dependent claims, but it does not, on the record I retrieved, expressly disclose the "single notification for only a particular message → infer status for all earlier messages" limitation of claim 1.

Other non-patent citations (prosecution documents, not prior art per se):

• CIPO Requisition by the Examiner, CA 2594817, dated 2011-06-01 — a prosecution paper, not anticipatory art.
• EESR for EP 06117626.9, dated 2006-12-28, and Examination Report for EP 06117626.9, dated 2007-06-12 (Strobeck) — European prosecution documents dated after the 2006-07-21 filing; cited on the US face as information, not as anticipatory art.

D. Secondary IM / messaging art (Tier 2)

E. Peripheral / background art (Tier 3 — generally non-anticipatory)

These appear as general background/obviousness-type references. None supplies the L3/L4 combination, so none anticipates any of claims 1–15 standing alone:

• US 6,067,354 A (MCI), "Method and system for processing data records from a telephone data repository…," granted 2000-05-23; priority 1997-07-21.
• US 2001/0054115 A1 (Ferguson), "System and method for bundling information," pub. 2001-12-20; priority 1998-05-29 — "bundling" of communications.
• US 2002/0004820 A1 (Baldwin), "Really simple mail transport protocol," pub. 2002-01-10; priority 2000-01-28.
• US 2003/0212673 A1 (Kadayam), "System and method for retrieving and organizing information from disparate … sources," pub. 2003-11-13; priority 2002-03-01.
• US 2003/0217096 A1 (Mckelvie), "Agent based application using data synchronization," pub. 2003-11-20; priority 2001-12-14.
• US 2004/0205263 A1 (Nokia), "…synchronizing of data providing for the handling of an interrupted synchronization process," pub. 2004-10-14; priority 2002-09-03.
• EP 1 492 033 A2 (Microsoft), "Common query runtime system and application programming interface," pub. 2004-12-29; priority 2003-06-23.
• US 2009/0191864 A1 (RIM), "Seamless Call Switching In A Dual Mode Environment," pub. 2009-07-30; priority 2003-11-20.
• US 7,720,912 B2 (Nokia), "Multimedia message transfer," granted 2010-05-18; priority 2004-02-09.
• US 2006/0274758 A1 (Cim Ltd.), "Adaptive skills-based routing," pub. 2006-12-07; priority 2005-06-01.
• US 2007/0185847 A1 (Intellext), "Methods and apparatus for filtering search results," pub. 2007-08-09; priority 2006-01-31.
• US 2007/0239898 A1 and US 2007/0266107 A1 (John Friend), "System and method for full wireless synchronization of a data processing apparatus with a messaging service / data service," pub. 2007-10-11 / 2007-11-15; priority 2001-08-07.

F. Bottom line

1. No cited reference clearly anticipates independent claims 1, 4 or 5. Each of the independent claims requires the very specific L3+L4 combination — receiving a status notification for only a particular message of a sent plurality, without any prior status notification for earlier messages, and then inferring the status of all earlier messages. Among the references I could examine, Isaacs (per-message ACK/status) and Jennings (per-message inferred read status) operate per message, and Isomaki's SIP draft treats notifications/indicators individually (with "aggregation" still an open issue). None squarely discloses the "one later notification subsumes all earlier messages" inference.

2. Most relevant prior art, ranked:

   • (NPL) Isomaki & Rosenberg, draft-ietf-simple-messaging-requirements-00 (2006-06-23) — the strongest, because it expressly enumerates the exact status categories the dependent claims recite (is-composing = typing started/stopped; IMDN = delivered/read) and addresses synchronization/aggregation. Best § 102/§ 103 reference against dependent claims 2, 3, 6, 7, 8–11, 12–15.
   • (US) US 2002/0026483 A1 (Isaacs) — best US reference on the "message delivered" status aspect and status-indicator/message-listing mechanics.
   • (US) US 2008/0263167 A1 / US 7,975,012 B2 (Jennings) — best US reference on the "message read" inference concept.
   • (US) US 2008/0233926 A1 (Eason) — status-notification-to-sender architecture (§ 102(e) as of 2003-06-20).
   • (US) US 2009/0157816 A1 (Pattan) — mobile IM status; unverified in this pass.

3. Confidence caveats. (a) I relied on the Google Patents full text and secondary sources, not a live USPTO/PatentCenter docket; the citation list is as printed on the patent. (b) I could not retrieve full text for several Tier-2/3 references (Pattan, Malik-forwarding, IBM time-sensitive messages) before exhausting my search budget — their mappings are based on titles/known subject matter and are flagged as lower confidence. (c) The claim-type structure means a reference must anticipate claim 1 before it can anticipate any dependent claim; I have applied that rule strictly rather than loosely labeling per-message art as "anticipatory."

Given the breadth of the independent claims versus the individual-message focus of this art, the record is more consistent with these references having been used for § 102(a)/(b)/(e) rejection of species or § 103 obviousness combinations during prosecution (and in the parallel EP/CA prosecution, e.g., the CIPO requisition of 2011-06-01 and the EESR of 2006-12-28) than with any single anticipatory reference against claim 1.

I'll ground this obviousness analysis in the actual prior art listed on the patent's Google Patents page. Let me verify the content of the key references.

Let me ground the secondary references relevant to the "update internal record" and "delay/aggregate" limitations.

Obviousness Analysis — U.S. Patent No. 8,572,182 under 35 U.S.C. § 103

Patent: US 8,572,182 B2, "Handling notifications in instant messaging systems"
Appl. No.: 11/459,047 | Filed: 2006-07-21 | Granted: 2013-10-29
Inventor: Gerhard Dietrich Klassen | Pre-AIA patent (filed before 2013-03-16, so pre-AIA §§ 102/103 govern)
Claim set: 3 independent claims (1 method, 4 CRM, 5 device) + 12 dependent claims that recite only the status type

0. Method note and reliability grading

Consistent with the prior sections of this analysis, I am working from the prior-art references actually listed on the Google Patents record for the '182 patent (the "Citations (24)", "Family Cites Families (4)", and "Non-Patent Citations (4)" sections). I retrieved and read the substantive text of the most load-bearing references; the rest I am citing by title/abstract only. I grade them below so the reader knows where the confidence sits:

I could not obtain full text for everything on the list, and I say so explicitly rather than filling gaps with assumed content.

1. The legal standard

The '182 patent is pre-AIA, so § 103(a) asks whether the claimed subject matter as a whole would have been obvious at the time of invention to a person having ordinary skill in the art ("POSITA"). Under Graham v. John Deere, I must (1) determine the scope and content of the prior art, (2) ascertain the differences between the prior art and the claims, (3) resolve the level of ordinary skill, and (4) assess objective evidence of non-obviousness. Under KSR Int'l v. Teleflex, a combination is obvious if it is "a combination of familiar elements according to known methods" yielding "predictable results," or if it is "obvious to try" a known design option with a reasonable expectation of success.

A threshold point that governs the whole analysis: the independent claims are extremely broad and recite no structure beyond generic computing hardware. Claim 1 is a three-step data-flow: send N messages → receive status for the last one, with no status for the earlier ones → infer the status of the earlier ones in an internal record. There is no recited timer, no delay mechanism, no specific notification format, and no specific prediction of the predetermined time window that the specification describes. The patentability of the independent claims therefore rises and falls on a single idea: cumulative (a.k.a. "aggregate" or "high-water-mark") status acknowledgment applied to an IM conversation.

2. Level of ordinary skill in the art (POSITA)

A POSITA here is a software/network engineer with (a) a bachelor's degree in CS/EE or equivalent and roughly 2–4 years of experience, or (b) a master's degree with 1–2 years, in the design of messaging clients and real-time communications protocols. She would be familiar with: existing IM notification semantics (Message_Delivered, Message_Read, Typing_Started/Stopped) — a point the patent's own Background concedes as prior art; the SIP/SIMPLE instant-messaging work at the IETF; in-order message sequencing and cumulative acknowledgments (routine in TCP and in the SyncML synchronization framework); and the bandwidth cost of signaling over wireless links. That skill level is modest and is what the references themselves assume.

3. Claim 1 — element-by-element chart

The only genuinely "new" element is the inference in step (E). Everything else is admitted or conventional, and the inference is the well-known high-water-mark/cumulative-acknowledgment concept.

4. The obviousness combinations

Combination 1 (primary): Jennings + Isaacs + Isomäki/RFC 3994

• Jennings (US2008/0263167A1; § 102(e) date 2005-02-01 via parent 11/048,495) supplies the problem the patent claims to solve — the sender cannot tell whether a message was actually read, and commercially available systems only confirm server receipt or that the receiver "is currently typing" (Jennings ¶[0004]). Jennings teaches a device on the receiver side displaying the message and sending a message to the sender indicating the view status (claim 1 of Jennings), where the notification is tied to a specific message. This supplies limitations (A)–(C) in IM context.
• Isaacs (US2002/0026483A1) supplies the mechanism for limitations (B), (E) and the typing status: it assigns each message a unique sequential number, has the receiver return an acknowledgement identifying that number, and has the sender update its local message listing on receipt of the ACK. Isaacs ¶[0055] literally discloses three conversation states — "X is not focused in this window", "X is focused in this window" and "X is typing in this window" — which is a Typing_Started notification.
• Isomäki / RFC 3994 (Jan 2005) supplies the standardized notification taxonomy (delivered / displayed / isComposing active-idle) and the explicit bandwidth rationale: the isComposing indication is "analogous to comfort noise packets … in silence-suppressed interactive voice conversations" and "in most cases, only one message is needed."

A POSITA combining these would arrive at Claim 1 without invention: use Jennings-style read-status signaling (C), number messages in Isaacs-style sequence order (B/E), and rely on the Isaacs/MCI/Nokia convention that a notification identified to a later message supersedes and therefore confirms the earlier ones (D/E).

Combination 2 (alternative/backup): Jennings + Nokia '263 + MCI '354

• Nokia '263 supplies the cumulative-acknowledgment with inferred status of earlier items: it expressly contrasts per-record change-logs (infeasible on a small device) against handling acknowledgments in batch at session boundaries, and its resume logic reconciles the two devices using update identifiers so that everything already covered by a marker is treated as synchronized. That is the claimed inference in (E).
• MCI '354 supplies the internal record: a "message status file" keyed by a per-message "tracking number," updated from a queue response (claims 13–14), with the response indicating "the status of the previously sent message."

This second combination is the more robust one for the negative limitation (D), because Nokia '263 is unambiguous that intermediate per-record acknowledgments are not exchanged when batching is used.

Combination 3 (for the "typing" dependent claims): any of the above + Isomäki/RFC 3994 (+ Isaacs)

RFC 3994 and the Isomäki draft supply isComposing with <state>active</state> and <state>idle</state> — i.e., Typing_Started and Typing_Stopped — and RFC 3994's rule that no idle message is needed if the real message is sent before the idle threshold is exactly the patent's "avoid sending Typing_Stopped if the IM is sent" embodiment (spec: "This may occur, for example, with very short instant messages such as 'OK'"). Isaacs ¶[0055] supplies the typing-start notification independently.

5. Motivation to combine (the KSR prong)

The record supplies an unusually explicit motivation; this is one of the stronger § 103 cases because the references state the reasons themselves:

1. Bandwidth conservation on constrained links. The '182 patent's stated purpose is that "[n]otifications sent in an IM system occupy bandwidth that would otherwise be available for other communications." Nokia '263 says the same thing decades earlier and more forcefully ("the network traffic resulting from the required acknowledgements is not acceptable as it is also expensive and time-intensive in mobile communication environments"). RFC 3994's comfort-noise analogy is an express teaching to suppress redundant signaling. Same field, same problem, same solution → KSR "familiar elements according to known methods."

2. The sender's desire for read/delivery status. Jennings ¶[0004] identifies precisely the unmet need — "there is a need in the art for a method and apparatus for inferring the read status of instant messages." That is the patent's own framing.

3. "Obvious to try" the cumulative-ack design. Cumulative acknowledgment keyed to a monotonically increasing identifier is a well-known technique (TCP; SyncML per Nokia '263; Isaacs' sequence numbers). Given a per-message status signal and a known cost problem, collapsing N notifications into one keyed to the latest message is the predictable, one-directional design choice. There is no teaching away; no reference disparages it.

4. Reasonable expectation of success. The combination uses only known client-side bookkeeping (Isaacs' message listing; MCI's message status file) and known protocol elements (Isomäki/RFC 3994 status types). Nothing unpredictable happens — the specification itself frames the design as a trade-off ("balance between giving the user … enough time to respond and delaying the notifications for too long"), not an unexpected result.

6. Dependent claims 2, 3, 6, 7 (and 8–15)

Because the dependents recite only the status type, they add no structure:

These are the weakest claims in the set; each is met by a single reference plus Combination 1 or 3.

7. Claims 4 and 5

Claim 4 (non-transitory CRM) and Claim 5 (device with processor, display, keyboard, communication interface, memory) are the same three-step logic on generic hardware. Isaacs is implemented as "a computer readable medium having instructions stored thereon" (Isaacs claim 16) and MCI '354 executes on "a data processor" over communications links, so a POSITA would find the CRM and device claims obvious for the same reasons — a general-purpose processor configured to perform the claimed method, with memory storing instructions, adds nothing patentable under Alice/Mayo step two or under § 103.

8. Honest weak points and how they cut

• The negative limitation in (C)/(D) is the hardest to prove with a single reference. The best proof is Nokia '263's batch-acknowledgment/resume model and MCI '354's queue-driven status handling, but a patentee could argue neither discloses the affirmative act of withholding earlier notifications in an IM conversation specifically. That argument is weakened because (i) the patent's Background concedes that per-event notifications were the prior art norm, and (ii) suppressing redundant signaling is the express teaching of RFC 3994.
• No reference I retrieved uses the word "infer" in the cumulative sense for IM status. Jennings uses "infer" but for whether a window was viewed, not for earlier messages. So the strongest formulation is Combination 1/2 rather than a single-reference anticipation. I did not find a clean § 102 anticipation of Claim 1 from the listed art — it is a § 103 case, as instructed.
• § 101 overlay. The prior analysis section noted that the district court in BlackBerry v. Twitter (C.D. Cal. 2:19-cv-01444) held Claims 1 and 4 of the '182 patent ineligible under Alice, but that order (Dkt. 51) was vacated on 2020-01-02 as part of the settlement dismissal with prejudice. That § 101 history does not establish anything under § 103, but it is corroborating evidence that the independent claims are viewed as abstract data-manipulation with conventional hardware. I flag it because a § 103 challenge and a § 101 challenge would likely travel together.
• Forums. The prior analysis flagged that no IPR or other post-grant proceeding against US 8,572,182 was located. An obviousness attack of the kind described here would ordinarily be raised in an IPR, and the PTAB's treatment of "inference/aggregation of status" claims would matter. I could not confirm any such filing, so treat that as a negative finding.

9. Bottom line

On the art listed in the '182 patent's own prior-art section, Claim 1 (and claims 2, 3, 6, 7), Claim 4 (and 8–11), and Claim 5 (and 12–15) would likely have been obvious under § 103 as:

• Primary combination: Jennings (read-status notification for a specific IM, § 102(e) date 2005-02-01) + Isaacs (sequence-numbered messages, ACK keyed to the number, sender-side message-list update, and "X is typing in this window") + Isomäki IETF draft / RFC 3994 (delivered/displayed/isComposing notifications and the express "only one message is needed" bandwidth rationale);
• Alternative/backup combination: Jennings + Nokia '263 (batch acknowledgment with inferred status of earlier records via update identifiers) + MCI '354 (message status file keyed by tracking number and updated from status responses), which more squarely meets the "inferred status for all earlier messages" element and the negative "without having previously received" limitation.

The motivation is stated by the references themselves: bandwidth savings on mobile links (Nokia '263; RFC 3994's comfort-noise analogy), the sender's desire for read/delivery status (Jennings), and the well-known, predictable use of cumulative/high-water-mark acknowledgment. The predictability and lack of any teaching away satisfy the KSR "obvious to try" and "familiar elements, known methods" tests. The dependent claims are the same three-step method restricted to one of four status types, each of which is disclosed in, or obvious from, the same references.

Caveat: I relied on titles/abstracts for the B-grade references (Eason, Glasser, IBM '441, Malik, Chen, AT&T, AOL, Orozco). Those do not change the core combinations — they would be cumulative at best — but a full-text pull of each (especially Eason US2008/0233926A1, "Electronic Communications Device Status Determination," and Glasser US2005/0005008A1, "activity monitoring and reporting in a computer network") could sharpen the negative-limitation argument.