US 8243723

I'll search for authoritative information on US 8,243,723, including any recent CAFC docket activity.

Let me dig deeper on the specific claims and any 2026 Federal Circuit activity.

Let me confirm the actual claim text and check for any 2026 appellate activity.

US 8,243,723 B2 — Analyst Summary

Sourcing note: The bibliographic data and specification below come from the authoritative full text supplied for this patent (Google Patents, fetched 2026‑09‑29). The claims section was not included in that supplied text, so the independent‑claim description below is grounded in the PTAB's institution decision in IPR2017‑00222 (Paper 7, May 25, 2017) and related record excerpts. Patent numbers are reproduced literally as found.

1. Bibliographic data (literal)

Recorded assignments of interest: Ayalogic Inc → Empire IP LLC (2013‑07‑31); → Uniloc Luxembourg S.A. (2016‑06‑10); security interest to Fortress Credit Co LLC (2016‑06‑27); → Uniloc 2017 LLC (2018‑07‑12).

Representative classifications: H04L51/04 (real‑time/IM), H04L65/40 (real‑time app support), H04M3/533 and H04M3/53366 (voice mail / message disposing & creating), H04M7/006 (VoIP interconnection), H04M2203/4536 (voicemail combined with text‑based messaging).

2. Abstract (verbatim)

"There is provided an instant voice messaging system (and method) for delivering instant messages over a packet-switched network, the system comprising: a client connected to the network, the client selecting one or more recipients, generating an instant voice message therefor, and transmitting the selected recipients and the instant voice message therefor over the network; and a server connected to the network, the server receiving the selected recipients and the instant voice message therefor, and delivering the instant voice message to the selected recipients over the network, the selected recipients being enabled to audibly play the instant voice message."

3. Independent claim — plain-language overview

Per the PTAB institution decision in IPR2017‑00222, the '723 patent's challenged set spans claims 1–8, and claim 1 is the sole independent claim (claims 2–8 depend directly or indirectly from it). Claim 1 is a method claim, and the Board quoted it (slightly truncated in the available excerpt) as follows:

"1. A method for instant voice messaging over a packet-switched network, the method comprising:
monitoring a connectivity status of nodes within the packet-switched network, said connectivity status being available and unavailable;
recording the connectivity status for each of the nodes;
associating a sub‑set of the nodes with a client;
transmitting a signal to a client including a list of the recorded connectivity status for each of the nodes in the sub‑set corresponding to the client;
receiving an instant voice message having one or more recipients;
delivering the instant voice message to the one or more recipients over a packet‑switched network…"

Plain-language breakdown:

1. Presence tracking — the system watches whether nodes on the packet network are "available" or "unavailable."
2. Recording state — it stores that availability status for each node.
3. Grouping — it links a sub‑set of nodes (e.g., a user's contacts) to a particular client.
4. Pushing the presence list — it sends that client a signal containing a "list" of the recorded connectivity status for the nodes in its sub‑set (colloquially, a presence/buddy list showing who's online).
5. Receiving a voice message — it accepts an instant voice message addressed to one or more recipients.
6. Delivering and playing — it delivers the voice message to the recipients over the packet‑switched network, where it can be audibly played back.

Key drafting takeaway: despite the "instant VoIP messaging" title and the abstract's client/server system language, the issued independent claim is directed to a server-side presence‑monitoring method (monitor/record/associate/transmit‑list/receive/deliver). Much of the litigation turned on the word "list" — specifically whether it must include the recorded connectivity status of more than one node (the Board reasoned that "each of the nodes in the sub‑set" implies at least two).

4. Patent family (same specification)

The '723 patent shares a specification with:

• US 7,535,890 B2 (original application 10/740,030)
• US 8,199,747 B2 (12/398,076)
• US 8,724,622 B2 (13/546,673)
• US 8,995,433 B2 (14/224,125)
• US 9,621,490 B2 (14/633,057)

Note the sibling '622 patent carries the system claims (e.g., "message database…database record including a unique identifier," "object field including a digitized audio file," "document handler system") that are frequently — and incorrectly — attributed to the '723 patent. The '723 claims are the presence‑list method claims described above.

5. Litigation, PTAB, and appellate history (as listed)

District court (E.D. Tex., 2016): numerous cases including 2:16‑cv‑00638, ‑00639, ‑00640, ‑00641, ‑00642, ‑00643, ‑00644, ‑00645, ‑00722, ‑00725, ‑00728, ‑00731, ‑00732, ‑00777, ‑00779, ‑00892.

PTAB:

• IPR2017‑00222 — Apple Inc., Snap Inc., Facebook, Inc., WhatsApp, Inc. v. Uniloc 2017 LLC. Challenged claims 1–8; instituted as to claims 1–7 (May 25, 2017). Final Written Decision entered May 23, 2018 finding claim 1 unpatentable over Vuori, and claim 2 unpatentable over Vuori and Malik. Patent Owner's request for rehearing denied (Sept. 6, 2018). Both sides appealed, with Patent Owner filing a Notice of Cross‑Appeal on Nov. 8, 2018.
• IPR2017‑01800 — Samsung (723 patent); instituted on claims 1–3 as obvious over Griffin and Zydney; oral hearing Oct. 30, 2018; listed as settled.
• IPR2017‑01365 — Not Instituted (Merits).
• IPR2017‑01635 — Instituted (listed as pending).

Federal Circuit: appeals 19‑2165 and 19‑2166 (Court of Appeals for the Federal Circuit) are listed. These trace to the IPR2017‑00222 cross‑appeals. Secondary reporting (AppleInsider, May 13, 2021) describes the Federal Circuit declining to overturn the PTAB result in Uniloc's VoIP/FaceTime dispute — i.e., the '723‑family validity loss was effectively affirmed. A related panel decision, Uniloc 2017 LLC v. [Apple] (19‑2162), addressed the '622 patent (claims 3, 4, 5, 24) and the Zydney/"object field" obviousness question.

Post‑grant reexamination: Reexam 90/14,788 ("Reexamination of Patent No. 8,243,723, System and Method for Instant VOIP Messaging"), filed June 29, 2021, examiner Stephen J. Ralis, art unit 3992; status listed as Reexamination Certificate Issued.

Legal status: Expired – Fee Related; adjusted expiration date listed as 2025‑11‑10.

6. CAFC 2026 docket check — result

No 2026 Federal Circuit docket activity for US 8,243,723 was found in the searches performed. The only Federal Circuit matters surfaced (19‑2162, 19‑2165, 19‑2166) are 2019 filings that were resolved around 2021. This is consistent with the patent's listed status: it is expired (fee‑related) with an adjusted expiration of 2025‑11‑10, and its principal validity challenge was finally disposed of on appeal years earlier.

Important caveats / uncertainty:

• The searches returned no live PACER or CAFC docket entry dated 2026 tied to this patent number. A definitive "no 2026 appeal exists" statement would require a direct PACER/CAFC docket query (e.g., by the 19‑2165/19‑2166 appeal numbers or by patent number in the appellate docket system), which was not available here.
• The search results did not return any result for a different number that could be confused with 8,243,723; results referencing 8,724,622 / 8,995,433 / 8,199,747 / 9,621,490 are genuinely related family members, not the same patent.
• The exact full claim set (total claim count and the precise wording of dependent claims 2–8) was not available in the supplied authoritative text; the claim descriptions above are drawn from the PTAB record. I have not fabricated claim language that was not in those sources.

Bottom line: US 8,243,723 is a 2012‑granted Ayalogic/Uniloc patent (application 12/398,063, filed 2009‑03‑04, priority 2003‑12‑18) claiming a server-side method of monitoring and distributing node connectivity/presence lists in an instant voice messaging system. Its single independent claim (claim 1) was held unpatentable in IPR2017‑00222, that outcome was appealed (Fed. Cir. 19‑2165/19‑2166) and effectively sustained, and the patent is now expired. No 2026 CAFC docket activity was located.

I'll research litigation involving US 8,243,723 using the sources you specified. Let me run several targeted searches.

Let me dig into the specific case numbers and PTAB proceedings.

Litigation involving U.S. Patent No. 8,243,723 ("the '723 patent")

Bottom line: Yes — the '723 patent has a substantial litigation history. It was asserted by the Uniloc entities in a 2016 wave of ~20 infringement suits in the Eastern District of Texas, was challenged in multiple AIA post-grant proceedings (including two Apple and Samsung IPRs), and reached the Federal Circuit in 2021. The patent is now owned by Uniloc 2017 LLC and is recorded as Expired – Fee Related (adjusted expiration 2025‑11‑10).

Below I separate what I could verify against primary/portal sources from what is only listed on the patent record.

1. Ownership / status context (relevant to who the "plaintiff" is)

Per the Google Patents record for US 8,243,723 B2 (https://patents.google.com/patent/US8243723/en):

Family members frequently asserted together with the '723 patent: US 7,535,890; US 8,199,747; US 8,724,622; US 8,995,433; US 9,621,490.

2. District court litigation (E.D. Tex., 2016 wave) — plaintiffs Uniloc USA, Inc. and Uniloc Luxembourg S.A.

The Google Patents "family litigation" record lists the following Texas Eastern District Court cases (all filed 2016, all case numbers interpreted literally). Because Google Patents flags this at the family level ("Family has litigation"), some of these may involve sibling patents rather than the '723 patent specifically. Cases I could independently confirm as asserting the '723 patent are marked ✔ confirmed.

Caveat on filing dates: The case numbers indicate a mid‑2016 filing wave, but I was not able to confirm exact filing dates for each docket from a primary source in this session. I am therefore not stating specific filing dates rather than guessing.

Sources: https://patents.google.com/patent/US8243723/en (litigation links to portal.unifiedpatents.com); PatSnap case summaries (Uniloc v. Avaya, 2:16‑cv‑00777; Uniloc v. Sony, 2:16‑cv‑00732); CourtListener docket 4389014 (2:16‑cv‑00642 / ‑00644 dismissal); Stanford NPE database (2:16‑cv‑00638, Apple).

A separate 2017 E.D. Tex. case, Uniloc USA v. Google, Inc., No. 2:17‑cv‑00231, appears in search results but the complaint text I retrieved concerned US 8,724,622; I could not confirm the '723 patent was asserted there, so I do not list it as a '723 case.

3. PTAB (inter partes review) proceedings

Portal links: https://portal.unifiedpatents.com/ptab/case/IPR2017-00222 ; /IPR2017-01800 ; /IPR2017-01365 ; /IPR2017-01635. Institution decision and FWD text retrieved via Docket Alarm.

4. Federal Circuit appeals

• Apple Inc. v. Uniloc 2017 LLC, No. 19‑1151 (Fed. Cir. Feb. 9, 2021) — appeal from IPR2017‑00222, plus Uniloc's cross‑appeal. The court affirmed in all respects: substantial evidence supported the Board's holding that claims 1–2 were obvious over U.S. Pat. App. Pub. 2002/0146097 (Vuori), and the Board correctly found claims 3–8 (representative claim 3, the record/intercom mode distinction) not obvious over U.S. Pat. App. Pub. 2003/0219104 (Malik). Opinion at https://www.courtlistener.com/opinion/[4854957](/patent/4854957)/apple-inc-v-uniloc-2017-llc/.
  • ⚠️ One secondary source (IP Law Daily/VitalLaw) refers to the patent as the "'732 patent" — that appears to be a typographical error for the '723 patent, since the case, the IPR number, and the claims quoted all match US 8,243,723. I flag it rather than silently correct it.
• CAFC Nos. 19‑2165 and 19‑2166 are listed on the '723 patent's litigation record as Federal Circuit cases. I was not able to verify which proceedings/patents these appeals arise from in this session, so I do not attribute them to the '723 patent with confidence.

5. Related (non-infringement) proceeding referencing the '723 patent

• Intel Corporation and Apple Inc. v. Fortress Investment Group LLC, et al., No. 3:19‑cv‑07651‑EMC (N.D. Cal.) — an antitrust/monopolization action. The amended complaint cites the '723 patent (along with the '890, '433, and '622 patents) as an example of a patent whose prior owners (Ayalogic, then Empire IP) never asserted it while Uniloc/Fortress allegedly did, as part of the asserted patent-aggregation scheme. This is not a patent infringement case against the '723 patent, but it is a proceeding in which the '723 patent is discussed.

6. What I could NOT confirm (stated explicitly rather than fabricated)

• Exact filing dates for the individual 2016 E.D. Tex. complaints.
• Defendant identities for cases 2:16‑cv‑00639, ‑00640, ‑00643, ‑00645, ‑00722, ‑00725, ‑00728, ‑00731, ‑00779, and ‑00892, and whether the '723 patent (as opposed to a sibling family patent) was asserted in each.
• Petitioner identities for IPR2017‑01365 and IPR2017‑01635 (and whether IPR2017‑01635 was resolved).
• Whether CAFC Nos. 19‑2165 / 19‑2166 concern the '723 patent.
• District‑court judgments on the merits for the 2016 cases (most were resolved by stipulated dismissal with prejudice, settlement, or were overtaken by PTAB invalidation of related claims); no damages award or infringement verdict involving the '723 patent appeared in my sources.

If you need PACER‑verified filing dates and defendant names for the ten unconfirmed dockets, those would require pulling the individual dockets — I did not want to guess them.

I'll research the PTAB proceedings on US 8,243,723, starting with the specific proceeding numbers that appear in the patent record, since the structured "no PTAB activity" block conflicts with the litigation history already documented.

Strong results — the record clearly documents four AIA proceedings, contradicting the structured block. Let me pin down the two remaining ambiguities: the CAFC 19-2165/19-2166 appeals and the 2017-01365 denial reasoning.

AIA Trial Proceedings — U.S. Patent No. 8,243,723 ("System and method for instant VoIP messaging")

⚠️ Source conflict flagged up front. The structured "PTAB proceedings on file" block for this patent states that the USPTO Open Data Portal returns no AIA trial proceedings. That is wrong for US 8,243,723. The patent's own record (Google Patents litigation links) and the primary documents — the Board's Final Written Decisions themselves, Docket Alarm, RPX Insight, Patexia, and the Federal Circuit's 2021 opinion — establish four AIA proceedings naming this patent. Per the task instruction ("web search may surface older or recently-filed proceedings the ODP hasn't indexed yet — flag any you find"), I treat the four documented proceedings as authoritative and flag the ODP result as a data gap, not a substantive "no PTAB activity" finding. None of the proceeding numbers below were invented; each is sourced to a Primary Board document or an indexed docket.

Proceedings overview

Four AIA proceedings name the '723 patent — zero currently active, one resolved by joinder/merger, one institution-denied, and two reaching Final Written Decisions that invalidated claim 1 (twice) and claims 2 and 3 (once), with claims 3–8 surviving one petitioner's art and claims 4–8 never adjudicated — so the bottom-line defensive posture is that the sole independent claim is dead and affirmed dead by the Federal Circuit, leaving only the never-challenged dependents 4–8 standing on a canceled-claim foundation.

Breakdown by status:

• Claims invalidated (FWD issued): 2 — IPR2017-00222 (claims 1–2), IPR2017-01800 (claims 1–3)
• Claims sustained (FWD issued): 1 — IPR2017-00222 held claims 3–8 not unpatentable over Apple's art
• Institution denied: 1 — IPR2017-01365
• Merged / terminated by joinder: 1 — IPR2017-01635
• Active: 0

IPR2017-00222 — Apple Inc., Facebook, Inc., and WhatsApp, Inc. v. Uniloc Luxembourg S.A. (later Uniloc 2017 LLC)

• Type: Inter Partes Review
• Filed: 2016-11-14 (Google Patents/docket list Nov. 14, 2016)
• Status: Final Written Decision (closed on appeal)
• Judge panel: JENNIFER S. BISK, MIRIAM L. QUINN (opinion author), CHARLES J. BOUDREAU. Docket Alarm also lists Kerry Begley on the panel record.
• Petition grounds: Claims 1–8, all under pre-AIA § 103. Apple asserted: (1) claim 1 obvious over U.S. Pat. App. Pub. 2002/0146097 (Vuori); (2) claims 2–7 obvious over Vuori in view of U.S. Pat. App. Pub. 2003/0219104 (Malik); (3) claim 8 obvious over Vuori + Malik + U.S. Patent 6,192,395 (Lerner).
• Institution decision: Instituted 2017-05-25 as to claims 1–7; trial not instituted as to claim 8. Following SAS Inst. v. Iancu, the panel issued an Order (2018-05-10, Paper 28) modifying institution to add claim 8 and all petitioned grounds; both parties waived further briefing.
• Final Written Decision: 2018-05-23 (Paper 29). Verdict at claim level:
  • Claims 1 and 2 — UNPATENTABLE by a preponderance of the evidence (obvious over Vuori; Vuori+Malik).
  • Claims 3–8 — NOT shown unpatentable. The Board construed the claim-1 term "list" to require the recorded connectivity status of more than one node, reasoning the recitation of "each of the nodes in the sub-set" implies at least two — but held Vuori's buddy-list/presence disclosure nonetheless met that construction. On claim 3 (representative of 4–8), the Board found Vuori and Malik disclosed different methods for sending messages based on connectivity, but not different modes of generating messages as claim 3 requires. On claim 8, the Board found Lerner's buffers buffer packets as received, not "as the instant voice message is recorded."
  • Rehearing requests from both parties were denied 2018-09-06 (Papers 32 and 33); the Patent Owner's due-process/"sua sponte" argument on the "list" construction was rejected.
• Settlement / termination: None — decided on the merits.
• Appeal: Both sides appealed. Federal Circuit No. 19-1151, Apple Inc. v. Uniloc 2017 LLC, decided 2021-02-09 (Lourie, J.), AFFIRMED IN ALL RESPECTS — substantial evidence supported invalidating claims 1–2 over Vuori, and the Board correctly found claim 3 (and thus 4–8) not obvious over Malik. Opinion: http://cafc.uscourts.gov/sites/default/files/opinions-orders/19-1151.OPINION.2-9-2021_1730132.pdf ; https://www.courtlistener.com/opinion/[4854957](/patent/4854957)/apple-inc-v-uniloc-2017-llc/
• Defensive value: Claim 1 — the only independent claim — is canceled and the cancellation is court-affirmed. Any infringement theory built on claim 1 is dead on arrival. A defendant should also know the flip side: Apple's art (Vuori/Malik/Lerner) did not take down claims 3–8, so a defense cannot simply import Apple's grounds for the dependent claims.

Primary FWD: https://www.docketalarm.com/cases/PTAB/IPR2017-00222/Inter_Partes_Review_of_U.S._Pat._8243723/docs/05-23-2018-Board/Final_Decision-29-Termination_Decision_Document.pdf

IPR2017-01800 — [Samsung Electronics America, Inc.](/litigations/by-plaintiff/Samsung%20Electronics%20America%2C%20Inc.) v. Uniloc Luxembourg S.A. / Uniloc 2017 LLC

• Type: Inter Partes Review
• Filed: 2017-07-20
• Status: Final Written Decision (claims invalidated). ⚠️ Note the source conflict: Google Patents labels this proceeding "Settlement," while the Board's own document is a Final Written Decision finding claims unpatentable and Patexia lists status "Final Written Decision." I treat the FWD as controlling and flag the Google Patents label as inconsistent with the record.
• Judge panel: JENNIFER S. BISK, MIRIAM L. QUINN (opinion author), CHARLES J. BOUDREAU.
• Petition grounds: Claims 1–3, obvious under pre-AIA § 103(a) over U.S. Patent No. 8,150,922 (Griffin) and WO 01/11824A2 (Zydney). (Confirmation of instituted grounds: "Claims 1–3 as obvious over Griffin and Zydney.")
• Institution decision: Instituted 2018-02-06, partially — reasonable likelihood as to claims 1 and 3, but not claim 2. Post-SAS, the panel modified institution to add claim 2 and all petitioned grounds (2018).
• Final Written Decision: 2019-01-31 (Paper 34). Verdict:
  • Claims 1, 2, and 3 — UNPATENTABLE by a preponderance of the evidence.
  • The panel did not apply collateral estoppel from IPR2017-00222 to claims 1–2 because that appeal was still pending at the time, expressly noting the unresolved appeal.
• Settlement / termination: No settlement reflected in the FWD; decided on the merits.
• Appeal: Patexia's docket metadata lists Appeal 2019-2165 for this proceeding. The patent record separately lists Federal Circuit Nos. 19-2165 and 19-2166 as CAFC cases on this patent. I could not definitively confirm in this session that 19-2165 is the Samsung/IPR2017-01800 appeal or what 19-2166 corresponds to — I flag this as an open item rather than assert it. (Note: the earlier-generated litigation section attributed 19-2165/19-2166 to the IPR2017-00222 cross-appeals; that attribution is incorrect — the -00222 appeal is 19-1151. This is the contradiction I was asked to flag.)
• Defensive value: This is the second, independent death of claim 1 — on different art (Griffin/Zydney) from different petitioners — and it is the proceeding that also canceled claims 2 and 3. Because claims 4–8 depend (directly or indirectly) from claim 3, this FWD functionally removes the foundation for the entire dependent set.

Primary FWD: https://www.docketalarm.com/cases/PTAB/IPR2017-01800/Inter_Partes_Review_of_U.S._Pat._8243723/docs/01-31-2019-Board/Termination_Decision_Document-34-Termination_Decision_Document.pdf

IPR2017-01365 — Facebook, Inc. and WhatsApp Inc. v. Uniloc USA, Inc. / Uniloc Luxembourg S.A.

• Type: Inter Partes Review
• Filed: 2017-05-03
• Status: Institution Denied
• Judge panel: CHARLES J. BOUDREAU, KERRY BEGLEY, MIRIAM L. QUINN (per docket metadata)
• Petition grounds: Not confirmed in my sources at claim/art granularity. Art unit 2614, Tech Center 2600.
• Institution decision: DENIED — institution decision date 2017-12-04. The panel's specific reasoning was not available in the retrieved sources; I do not fabricate it.
• Final Written Decision: None (never instituted).
• Settlement / termination: None — denied at the threshold.
• Appeal: Institution denials are generally not appealable under § 314(d); no appeal is listed.
• Defensive value: Low on its own, but strategically informative — it shows that the same petitioner family (Facebook/WhatsApp) lost at the institution threshold on the '723 patent, which is why they pivoted to a joinder petition (below) rather than a standalone challenge.

IPR2017-01635 — Facebook, Inc. and WhatsApp Inc. v. Uniloc Luxembourg S.A.

• Type: Inter Partes Review (joinder petition)
• Filed: 2017-06-16
• Status: Instituted / joined and terminated. Docket metadata: Instituted 2017-10-03, Terminated 2017-10-03, last docket entry 2018-04-11.
• Judge panel: CHARLES J. BOUDREAU, KERRY BEGLEY, MIRIAM L. QUINN
• Petition grounds: Filed as a joinder vehicle to IPR2017-00222; on grant of joinder, Facebook, Inc. and WhatsApp, Inc. were joined as Petitioners in IPR2017-00222 (see the FWD's footnote and Paper 12). Substantively identical art to the Apple petition.
• Institution decision: Institution granted as a joinder to IPR2017-00222 on 2017-10-03.
• Final Written Decision: None issued under this number — the merits issued in IPR2017-00222 (Paper 29).
• Settlement / termination: Terminated by joinder into IPR2017-00222; the joined parties are bound as Petitioners to that FWD.
• Appeal: Coextensive with the IPR2017-00222 appeal (19-1151).
• Defensive value: Its relevance is estoppel scope — Facebook and WhatsApp are treated as Petitioners in IPR2017-00222, so § 315(e)(2) estoppel reaches them for everything they raised or reasonably could have raised on claims 1–8.

⚠️ One retrieved petition document referenced "IPR2018-01635 (involving the '723 Patent)" in a list of related matters; RPX and the Board's own records identify the '723 joinder petition as IPR2017-01635 (filed 2017-06-16). I treat the "2018" reference as a typographical error and flag it rather than silently correct it.

Strategic summary

Claim landscape — CANCELED vs. SUSTAINED vs. UNTESTED.

• Claim 1 (sole independent claim): CANCELED. It was held unpatentable in IPR2017-00222 (2018-05-23, over Vuori; Vuori+Malik for claim 2) and again in IPR2017-01800 (2019-01-31, over Griffin+Zydney). The 19-1151 Federal Circuit affirmance (2021-02-09) put the first cancellation beyond dispute.
• Claim 2: CANCELED (both proceedings).
• Claim 3: CANCELED per IPR2017-01800 (Griffin+Zydney) — although note the genuine, art-specific split: the same claim 3 was SUSTAINED in IPR2017-00222 because Apple's Vuori/Malik art failed to show two different modes of generating a message. The Board can (and did) reach opposite results on different records.
• Claims 4–8: NEVER ADJUDICATED. Apple challenged claim 8 (and 4–7) but lost; Samsung challenged only claims 1–3. So no PTAB tribunal ever issued an unpatentability holding on claims 4–8. But they depend directly or indirectly from claim 3 (which depends from claim 1), so once claims 1 and 3 are canceled, claims 4–8 have no valid base to stand on. A defendant's practical posture is therefore: claim 1 gone, dependent set structurally hollowed out, with no formal cancellation certificate for claims 4–8.

Estoppel landscape (§ 315(e)(2)). Apple, Facebook, and WhatsApp (as Petitioners in IPR2017-00222, including via the IPR2017-01635 joinder) and Samsung (IPR2017-01800) are estopped in civil actions from raising any ground they raised or reasonably could have raised on the claims that reached FWD. For a new defendant who was not a petitioner or privy, estoppel does not attach: Vuori, Malik, Lerner, Griffin, and Zydney are all public and remain fair game. However, the most useful defense for a new defendant may be collateral estoppel off the claim-1 invalidity, not a fresh IPR — claim 1 is already dead, and claims 4–8 are the only live drafting surface, untested by any petitioner.

Pattern signals. This was a coordinated, multi-front campaign by the actual accused infringers, not a defensive aggregator. Apple filed a five-petition family sweep (IPR2017-00221/-00222/-00223/-00224/-00225 across the '890/'723/'622/'433 patents); Samsung filed a six-petition sweep (IPR2017-01797/‑01798/‑01799/‑01800/‑01801/‑01802 across the '622/'747/'723/'433/'890 patents); Facebook/WhatsApp filed IPR2017-01365 (denied) and IPR2017-01635 (joinder); Google, LG, and Huawei also filed family IPRs. On the '723 patent specifically, two different petitioners independently killed claim 1 using entirely different art. The patent owner (Uniloc, later Uniloc 2017 LLC) litigated hard — it filed rehearing requests in IPR2017-00222 and filed a Notice of Cross-Appeal on 2018-11-08, appealing the claim 1–2 loss in 19-1151 while Apple cross-appealed the claim 3–8 win. Uniloc did not get the claim 1 invalidation reversed. There is no Unified Patents petition in the '723 chain — the Unified Patents links on the Google Patents page are a litigation-data source, not a petitioner.

Recommended next steps

1. For a defendant facing a demand letter citing claims 1–3: The response writes itself. Link the IPR2017-01800 FWD (2019-01-31) and IPR2017-00222 FWD (2018-05-23), and the Federal Circuit's 19-1151 affirmance (2021-02-09), and quote the disposition verbatim: "Petitioner has shown by a preponderance of the evidence that claims 1 and 2 of the '723 patent are unpatentable" (IPR2017-00222) and "claims 1–3 of the '723 patent are unpatentable" (IPR2017-01800). Asserting canceled claims is sanction-bait.

2. For a defendant facing a theory on claims 4–8: Be precise. Those claims were never adjudicated — do not say they were "invalidated." Instead, argue (a) they depend from canceled claims 1/3 and cannot survive independently, and (b) if the plaintiff insists they are separately patentable, the Apple art was held insufficient but the Griffin/Zydney art was never applied to claims 4–8 — a § 103 theory on claims 4–8 using Griffin/Zydney-plus, or new art, remains available and would not be estopped against a non-petitioner.

3. Trial-stage milestones: There are none to track — every proceeding is closed. IPR2017-01365 died at institution (2017-12-04); IPR2017-01635 merged on 2017-10-03; and both merits proceedings issued FWDs (2018-05-23 and 2019-01-31). The statutory one-year trial clock is moot.

4. Open items to verify on PACER / PTAB E2E before relying on them: (i) the exact disposition and docket correspondence of CAFC Nos. 19-2165 and 19-2166 (I could not confirm which proceeding each arises from — 19-2165 is plausibly the IPR2017-01800/Samsung appeal per Patexia metadata, but I did not verify it); (ii) whether any certificate of cancellation issued for claims 4–8 (the record shows only a fee-related expiration at 2025-11-10, not a claims-cancellation certificate); and (iii) the panel's specific reasoning in the IPR2017-01365 institution denial, which was not retrieved. PTAB E2E: https://ptabe2e.uspto.gov/ ; CAFC docket: https://cafc.uscourts.gov/ .

5. Reexamination note (non-AIA-trial context): The earlier-generated section records ex parte reexam 90/14,788 (filed 2021-06-29, art unit 3992) with a listed status of "Reexamination Certificate Issued." That is a separate post-grant track from the AIA trials above, but if a reexam certificate changed the claim set, it should be pulled directly from the USPTO Patent Public Search / Public PAIR before any reliance on claim numbering.

I'll research the assignment record for US 8,243,723, starting with the USPTO Assignment Center and cross-referencing sources.

Good — I found reel/frame references. Let me dig into the specific assignment documents and correspondents.

Let me get more detail on the intermediate assignment and the correspondents of record.

Assignment Record Reconstruction — US 8,243,723 B2

Methodology and reach caveat (read first): My planned live queries against USPTO Assignment Center (assignmentcenter.uspto.gov) and the indexed mirror (assignment.uspto.gov) could not be completed in this session (search-step limit reached before I could pull the reel/frame detail pages directly). I therefore reconstructed the chain from primary-record excerpts reproduced in PTAB filings — specifically the 37 CFR 3.73(b) chain-of-title statements and assignment exhibits filed in the '723-family IPRs (IPR2017‑00222, IPR2017‑01797, IPR2017‑01798) — and cross-checked them against the Google Patents legal-events record supplied as authoritative. Reel/frame numbers below are taken verbatim from those documents. Where a value (execution date, correspondent) was not in the documents I retrieved, I say so rather than infer it. Confirm every entry at the Assignment Center before relying on it.

Inventors

Notes on patterns:

• Single inventor. The '890/'747/'622/'433/'490/'723 family all trace to one inventor, Michael J. Rojas. There is no multi-inventor team whose departure could signal a fire-sale; the "asset" was always one person's disclosure.
• Rojas is a serial founder, not a one-off. Public records show he co-founded North Coast Logic, Inc. (sold to NEC America, became NEC Integrated Application Division), where he led AIMWorX and was issued ~7 patents, then left NEC in early 2002 to found Ayalogic. The '723 family therefore sits on the second of his venture exits. Source: Ayalogic press release dated Dec. 18, 2003 (ssmp.com/pdfs/PR_a31219_Ayalogic.pdf).
• No inventor-departure signal is determinable for the '723 patent specifically: Ayalogic was a small private startup founded in 2002 by Rojas, and I found no public record of a distinct inventor team leaving. The more probative event on this chain is the company-level exit, not an inventor exit.

Original assignee

Ayalogic, Inc. (Akron, OH; offices also in New York City) — named as assignee on the issued patent and on the parent US 7,535,890.

• Did it ship a product embodying the claims? Yes, on the record. Ayalogic publicly launched Imvox™ — described in its own Dec. 18, 2003 release as "a secure, PC-based instant voice messaging system" — and filed the priority application the same day. Its later enterprise product was Qmunicate™, described as integrating "voice, text, IM, voicemail, email and document transfer." The press release states Imvox "contains the most important features of instant messaging, voice mail and e-mail," which maps onto the specification's record/intercom modes. So this was, at origin, an operating-company patent, not a paper asset.
• Primary line of business: privately held communications/telephony software development (VoIP instant-voice messaging, enterprise unified communications).
• Current status: Ayalogic, Inc. no longer owns the patent and I found no evidence it operates today. It appears to have wound down its patent holdings via the Empire IP transfer. I could not confirm from primary records whether Ayalogic was dissolved, wound up, or acquired; no Chapter 7/11 filing surfaced. Treat the end-state as unconfirmed.
• Original prosecution counsel of record: Scully, Scott, Murphy & Presser, P.C., 400 Garden City Plaza, Suite 300, Garden City, NY 11530 (USPTO Customer No. 23389; filer John Kasha; attorney docket 17188Y). The Ayalogic release notes SSMP also prosecuted Rojas's seven NEC AIMWorX patents — i.e., repeat prosecution counsel across Rojas's successive ventures.

Assignment timeline

The chain documented in the PTAB exhibits is a three-link transfer from inventor to NPE, plus a security interest and a later intra-NPE reassignment. Reel/frame values are verbatim from the filings; execution/recordation dates are given as recorded on Google Patents' legal-events ledger where the document itself did not carry a date.

1. Execution date not confirmed / recorded on the 014,827 reel series — Reel 014827/0059

   • Conveyance: Assignment (inventor → company)
   • Assignor: Michael J. Rojas
   • Assignee: Ayalogic, Inc.
   • Correspondent: Not stated in the excerpt. Prosecution was handled by Scully, Scott, Murphy & Presser, P.C. (400 Garden City Plaza, Suite 300, Garden City, NY 11530; Customer No. 23389; John Kasha). Whether SSMP was the recording correspondent on this instrument is unconfirmed.
   • Context: Founder-to-company transfer at formation of the venture — standard startup capitalization, not a disposal.

2. Executed ~2013‑07 (recorded event dated 2013‑07‑31) — Reel 030922/0335

   • Conveyance: Assignment
   • Assignor: Ayalogic, Inc.
   • Assignee: Empire IP LLC
   • Correspondent: Not captured in the excerpts I retrieved.
   • Context: Portfolio divestiture / transfer-to-asserter — the operating company exits and the patent passes to a licensing entity.

3. Executed ~2016‑06‑10 (recording on the 038,963 reel; the 3.73(b) statement in the record is dated 2016‑09‑15) — Reel 038963/0343

   • Conveyance: Assignment
   • Assignor: Empire IP LLC
   • Assignee: Uniloc Luxembourg S.A.
   • Correspondent: Partially captured. The chain-of-title submission is signed by "Sean D. [surname not legible in the retrieved OCR], IP Counsel for Uniloc Luxembourg S.A." The full name, firm, and address as recorded were not legible in the text I retrieved. Flag: this is a Uniloc in-house IP counsel signing, i.e., the recording was filed through the acquirer's own channel — recurring NPE-side authority, though I could not confirm a second appearance to meet the "recurrence" bar.
   • Context: Transfer-to-asserter, executed four days before the first '723 infringement complaint (see signal 5).

4. Recorded 2016‑06‑27 — Reel/frame not captured

   • Conveyance: Security Agreement / Security Interest
   • Assignor(s): Uniloc Corporation Pty Limited; Uniloc Luxembourg S.A.; Uniloc USA, Inc.
   • Assignee: Fortress Credit Co LLC
   • Correspondent: Not captured.
   • Context: Securitization — the Uniloc patent family is pledged as collateral to a third-party financier (Fortress), the classic Uniloc/Fortress funding structure.

5. Recorded 2018‑07‑12 — Reel/frame not captured

   • Conveyance: Assignment
   • Assignor: Uniloc Luxembourg S.A.
   • Assignee: Uniloc 2017 LLC (current assignee of record)
   • Correspondent: Not captured.
   • Context: Internal reorg / restructuring within the same NPE family (Luxembourg S.A. → Delaware LLC), consistent with the IPR-era re-papering of the Uniloc estate.

What I could not verify: the reel/frame numbers for entries 4 and 5, the correspondent names/firms for entries 2, 4 and 5, and the executed (as opposed to recorded) dates for entries 1 and 2. Those require the Assignment Center detail pages, which I was unable to pull. Do not treat the missing reel/frames as "no assignment" — the Google Patents ledger shows these conveyances were recorded.

Timeline diagram

timeline
    title Ownership of US 8243723
    2003 : Rojas files priority application
         : Rojas assigns to Ayalogic Inc
    2012 : Patent issued to Ayalogic
    2013 : Ayalogic assigns to Empire IP LLC
    2016 : Empire IP assigns to Uniloc Luxembourg
         : First suits filed days later
         : Fortress takes security interest
    2018 : Reassigned to Uniloc 2017 LLC
    2025 : Listed expiration lapses

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT. Patent moves off an operating company onto licensing entities: Ayalogic, Inc. (shipped Imvox/Qmunicate) → Empire IP LLC (reel 030922/0335) → Uniloc Luxembourg S.A. (reel 038963/0343) → Uniloc 2017 LLC. The suffix pattern ("IP LLC," foreign holding S.A., "2017 LLC") is paired with concrete evidence of no-product status for the transferees, not naming alone: the only product evidence in the record (the 2003 Imvox/Qmunicate releases) belongs to the transferor Ayalogic, and no commerce by Empire IP or the Uniloc entities appears anywhere in the file.

2. Known asserter in the chain — PRESENT (strong). Two links independently match public NPE directories:

   • Uniloc (Luxembourg S.A. / Uniloc USA / Uniloc 2017 LLC) — among the most prolific patent plaintiffs of the 2016–2020 period; it drives the E.D. Tex. 2016 wave in which 2:16‑cv‑00638 (Apple) asserted the '723 patent, and it is the named Patent Owner in the IPRs.
   • Empire IP LLC — a known patent-assertion/acquisition entity that acquired the Ayalogic estate.
   • Additionally, the Fortress Credit Co LLC security interest (2016‑06‑27) matches the documented Uniloc–Fortress financing/asserter relationship.

3. Repeat correspondent across the chain — UNCLEAR (partial evidence). I could establish a prosecution-side repeat player — Scully, Scott, Murphy & Presser, P.C. appears as counsel across Rojas's successive ventures (NEC AIMWorX and Ayalogic) — but that is prosecution, not assignment recording. On the assignment side I have only a single legible NPE-side recording signature ("Sean D., IP Counsel for Uniloc Luxembourg S.A.") on the 038963/0343 submission. One appearance is not a recurrence finding, and I could not retrieve the correspondents for the 030922/0335 or 2018 recordings to test for recurrence. Flagged as unclear rather than asserted.

4. Cascading transfers — PRESENT. Three ownership transfers in roughly five years (2013‑07 → 2016‑06 → 2018‑07), with the Empire IP → Uniloc and Fortress security interest legs compressed into the same month (June 2016) and a further same-family reassignment in July 2018. The Common Denominator across the NPE legs is the Uniloc/Fortress correspondence channel, consistent with the pattern described in the Intel/Apple v. Fortress antitrust pleading (N.D. Cal. 3:19‑cv‑07651).

5. Pre-litigation transfer — PRESENT (strongest signal). The Empire IP LLC → Uniloc Luxembourg S.A. assignment is dated ~2016‑06‑10 (reel 038963/0343). The first '723 complaint, Uniloc USA, Inc. & Uniloc Luxembourg, S.A. v. Apple Inc., No. 2:16‑cv‑00638 (E.D. Tex.), was filed 6/14/2016 per the AO‑120 form of record. That is a four-day gap between the enabling assignment and the complaint naming the '723 patent — the chain was papered specifically to vest standing in the plaintiff immediately before assertion.

6. Bankruptcy fire-sale — NOT PRESENT / UNCLEAR. I found no Chapter 7/11 proceeding, 363 sale, or court-supervised patent auction for Ayalogic, Empire IP, or Uniloc in the sources retrieved. The transfer was a private negotiated divestiture, not a bankruptcy disposition.

7. Privateering — NOT PRESENT (as to this chain's mechanics). This was not a case of an operating company transferring to an NPE that asserts on the operating company's behalf against its competitors. Ayalogic exited entirely; the assertion was conducted for the NPE's own account (and its Fortress financier). The structure is outright monetization, not proxy warfare.

8. Defensive aggregator — NOT PRESENT. The chain terminates at Uniloc 2017 LLC, an asserter — the inverse of a defensive neutralization (no RPX / AST / LOT / Unified / OIN involvement anywhere in the recorded chain).

Verdict

NPE — high confidence.

The chain is documented end-to-end from public-record exhibits: Rojas → Ayalogic, Inc. (reel 014827/0059); Ayalogic → Empire IP LLC (reel 030922/0335, recorded 2013‑07‑31); Empire IP LLC → Uniloc Luxembourg S.A. (reel 038963/0343, executed ~2016‑06‑10); security interest to Fortress Credit Co LLC (recorded 2016‑06‑27); reassignment to Uniloc 2017 LLC (recorded 2018‑07‑12). This yields two or more strong signals in combination: a shell/asserter transfer off a genuine product company, a chain populated by a known high-frequency plaintiff (Uniloc) and known acquirer (Empire IP), and — most decisively — a pre-litigation transfer executed four days before the first '723 infringement suit (2:16‑cv‑00638, filed 6/14/2016). The single caveat is evidentiary, not analytical: I could not pull the Assignment Center pages themselves, so reel/frame numbers for the Fortress and Uniloc‑2017 recordings and the correspondents on entries 2, 4, and 5 remain to be confirmed.

Verify at: https://assignmentcenter.uspto.gov/ (search: patent 8243723) — mirror: https://assignment.uspto.gov/patent/index.html

I'll research the prior art cited on US 8,243,723. Let me run several targeted searches.

Let me search for the specific prior-art references cited on the face of the '723 patent and the IPR record.

Let me get the actual front-page "References Cited" list on the '723 patent itself.

Prior Art for U.S. Patent No. 8,243,723 B2 — Analyst Findings

Scope discipline: every identifier below was checked against the literal number 8,243,723. I did not substitute results for the closely-numbered sibling patents US 8,724,622, US 8,199,747, US 7,535,890, US 8,995,433, or US 9,621,490. Where a cited reference is a family member of the '723 patent (same specification, different claims), I say so explicitly rather than presenting it as unrelated art.

1. Sourcing note — what I could and could not retrieve (read first)

The authoritative full text supplied for this patent (Google Patents, fetched 2026‑09‑29) does not include the front‑page "(56) References Cited" block, and my direct attempts to pull the '723 patent's own PTO‑892 / front‑page citation list timed out before returning a clean hit. Therefore:

• Group A (§3 below) — art that is definitively tied to the '723 patent, because it was pleaded and adjudicated in the '723‑specific IPRs and the resulting Federal Circuit appeal. High confidence.
• Group B (§4 below) — the examiner‑cited U.S. patent documents that appear on the front pages of sibling patents sharing the '723 specification (US 7,535,890, US 8,199,747, US 8,724,622). These are candidate '723 citations: they are the same art family the '723 examiner worked with (the '723 patent's own prosecution included an Office Action dated Oct. 18, 2011 in App. Ser. No. 12/398,063), but I could not confirm the '723 patent prints every one of them. Labelled accordingly.

Important § 102 vs. § 103 caveat: the task asks which claims each reference "potentially anticipates under 35 U.S.C. § 102." In this record, almost none of the citations were applied as § 102 anticipators. The '723 patent's own IPRs were obviousness (§ 103) proceedings, and the examiner‑cited documents were cited as background. A reference "potentially anticipates" a claim only if it discloses every limitation of that claim in a single document. I flag which references are genuine § 102 candidates and which are only § 103 combination art — I am not stretching every citation into an anticipation theory.

2. The claim set being measured against (from the Federal Circuit opinion, No. 19‑1151)

Claim 1 is the sole independent claim; claims 2–8 depend from it. Per the CAFC opinion (https://cafc.uscourts.gov/sites/default/files/opinions-orders/19-1151.OPINION.2-9-2021_1730132.pdf):

• Claim 1 — method: monitoring connectivity status of nodes ("available and unavailable"); recording that status for each node; associating a sub‑set of nodes with a client; transmitting a signal to a client including a list of the recorded connectivity status for each of the nodes in the sub‑set; receiving an instant voice message having one or more recipients; delivering it over the packet‑switched network.
• Claim 3 (representative of 4–8) — "controlling a method of generating the instant voice message based upon the connectivity status" of the recipient(s).
• Claim 6/8 — "intercom mode": buffering successive portions of the message and delivering each successive portion as it is recorded.

This matters for anticipation analysis: the presence‑list method of claim 1 is a very different target than the "two modes of generation" limitation of claim 3 or the buffering limitation of claim 8.

3. GROUP A — References definitely applied to US 8,243,723 (IPR + CAFC record)

A‑1. Vuori — the primary reference

A‑2. Malik — the secondary reference

A‑3. Lerner — applied to the buffering claim only

A‑4. Stubbs & Abburi — the alternative § 103 grounds

A‑5. Griffin & Zydney — the Samsung IPR ground (IPR2017‑01800)

A‑6. Non‑patent literature cited for the presence concept

4. GROUP B — Examiner‑cited U.S. patent documents on the shared‑specification family front pages

These are the "(56) References Cited" items printed on the front pages of the sibling patents sharing the '723 specification. They are candidate '723 citations — I could not confirm each one appears on the '723 patent itself. Dates are the publication dates as printed.

⚠️ Date‑law flag: many Group B documents published after Dec. 18, 2003 (the '723 priority date). Under § 102(a)/(e) a reference published after the priority date is not prior art unless it is entitled to an earlier effective filing date. Several of these were plainly cited for the later‑filed '622 patent, not the '723 patent — which is another reason I do not label them § 102 anticipators of '723 claims.

5. Anticipation assessment — bottom line

Net: the single most relevant prior art for US 8,243,723 is the Vuori publication (US 2002/0146097 A1), with Malik (US 2003/0219104 A1) as the key secondary reference and Lerner (US 6,192,395) relevant only to the intercom‑mode buffering claim. The examiner‑cited U.S. documents (Group B) are largely background art and do not individually anticipate any '723 claim.

6. Flags, contradictions, and things I could not verify

1. OCR artifact on the '723 patent's own face. One retrieved OCR excerpt renders the number as "US 3,243,723 B2." That is an OCR misread of the '723 patent's front page (a "7" read as "3"). Per the operating rule, I note it rather than silently correct it — it is not a separate patent.
2. "723" vs "732" mislabel. As previously flagged in the litigation section, IP Law Daily/VitalLaw (Feb. 9, 2021) refers to this patent as the "'732 patent." The case number (19‑1151), the IPR, and the quoted claims all match US 8,243,723; I continue to treat "'732" as a typo but do not alter the source.
3. IPR2017‑01800 status conflict (unresolved). Google Patents labels it "Settlement"; the document text I retrieved is a Final Written Decision holding claims 1–3 unpatentable. Both are stated; I do not resolve the conflict.
4. Not verified: the exact publication numbers and dates for Griffin and Zydney (IPR2017‑01800 ground), and the full front‑page "(56)" block as printed on US 8,243,723 B2 itself. I could not pull these without a paid docket source or the patent PDF's front page, and I have not guessed them.
5. No fabricated references: every document listed above comes from the IPR/CAFC record or from the sibling patents' printed front pages. Where I did not know a title or a date, I said so rather than supplying one.

I'll research the prior art references cited against the '723 patent and its family, then build the § 103 analysis.

Obviousness Analysis — U.S. Patent No. 8,243,723 B2 under 35 U.S.C. § 103

Analysis date: April 26, 2026. Claim text, prior-art disclosures, and procedural history are taken from the supplied authoritative patent text plus the PTAB/CAFC record retrieved for this session. All patent and application numbers are reproduced literally.

0. Sourcing note and one correction to the earlier summaries

The Prior Art section for this page resolves to two distinct pools:

1. References of record on the face of the patent (the 12/398,063 file wrapper references): US 6,763,226 (McZeal); US 2003/0087632 (Sagi); US 2003/0126207 (Creamer); US 2004/0014456 (Vaananen); US 2004/0030046 (Schultes); US 2004/0085456 (Kwag); US 2004/0122906 (Goodman); US 2004/0128356 (Bernstein); US 2004/0179092 (LaPoint); US 2004/0252679 (Williams); US 2005/0053230 (Gierach); US 2005/0105697 (Hollowell); US 2006/0167883 (Boukobza); US 2006/0268750 (Weiner); US 2007/0112925 (Malik); US 2007/0174403 (Barry); US 2010/0070275 (Cast); plus non-patent literature (Cisco CallManager v3.3 data sheet, Nov. 22 2002; Cisco MGX 8000 data sheet; Teliphone 3100-V21P, 2003; "Device Profile: snom 100 VoIP phone," May 15 2002; pingtel Xpressa SIP phone, Dec. 8 2003). (Source: https://www.freepatentsonline.com/8243723.html; corroborated by the OCR of US 8,243,723 B2 front page at docketalarm.)

2. References relied on in the AIA challenges — which are the operative § 103 art: Vuori (US 2002/0146097 A1), Malik (US 2003/0219104 A1), Lerner (US 6,192,395), Griffin, Zydney, Stubbs, and (in the sibling-IPR record) Appelman (US 6,750,881).

Correction to the earlier "Patent summary" section: that section states the '723 claim set was drawn from the IPR2017-00222 institution decision and that full claim text "was not available." The full literal claim text is now available from the Federal Circuit's nonprecedential opinion in Apple Inc. v. Uniloc 2017 LLC, No. 19‑1151 (Fed. Cir. Feb. 9, 2021) (http://cafc.uscourts.gov/sites/default/files/opinions-orders/19-1151.OPINION.2-9-2021_1730132.pdf) and from Apple's petition (https://www.docketalarm.com/cases/PTAB/IPR2017-00222/.../Petition-2-Petition.pdf). This matters because the earlier summary described claim 1 as ending at "delivering … over a packet-switched network…" — the claim actually contains two further limitations (temporary storage and later delivery) that materially change the § 103 mapping. The corrected text appears below.

1. Legal framework applied

• Governing statute: pre-AIA 35 U.S.C. § 103(a), because the application's effective filing date is Dec. 18, 2003 (continuation of Ser. No. 10/740,030). The '723 patent is not a post-AIA first-inventor-to-file patent.
• Test: Graham v. John Deere, 383 U.S. 1 (1966) — scope and content of the prior art, differences between the prior art and the claims, level of ordinary skill, and secondary considerations.
• Combination rationale: KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) — a combination is obvious where the elements were known, the combination was "a predictable variation," the reference taught "design incentives and other market forces," or the technique was "obvious to try" from a finite number of identified, predictable solutions.
• Level of ordinary skill (PHOSITA): a bachelor's degree in computer science/electrical engineering (or equivalent) plus ~2–3 years of experience in IP telephony/packet-switched messaging, or equivalent. The Board's expert testimony in IPR2017-00222 and IPR2017-01800 was framed around a December 2003 timeframe, and I adopt that date.

2. The claims in issue (literal text, as reproduced by the Federal Circuit and the IPR petitions)

Claim 1 (sole independent claim):

"1. A method for instant voice messaging over a packet-switched network, the method comprising:
monitoring a connectivity status of nodes within the packet-switched network, said connectivity status being available and unavailable;
recording the connectivity status for each of the nodes;
associating a sub-set of the nodes with a client;
transmitting a signal to a client including a list of the recorded connectivity status for each of the nodes in the sub-set corresponding to the client;
receiving an instant voice message having one or more recipients;
delivering the instant voice message to the one or more recipients over a packet-switched network;
temporarily storing the instant voice message if a recipient is unavailable; and
delivering the stored instant voice message to the recipient once the recipient becomes available."

Claims 2–8 (as recited in Apple's petition, Grounds 2–3):

• 2. "wherein the instant voice message includes one or more files attached to an audio file."
• 3. "controlling a method of generating the instant voice message based upon the connectivity status of said one or more recipient."
• 4. "wherein said method of generating said instant voice message is selected from a group comprising a record mode and an intercom mode."
• 5. "wherein said record mode is selected as a default when at least one recipients are unavailable."
• 6. "wherein said intercom mode is selected as a default when at least one recipients are available."
• 7. "wherein said record mode comprises the steps of: recording the instant voice message; receiving a stop indicator; and transmitting the recorded instant voice message after the receipt of said stop indicator."
• 8. "wherein said intercom mode comprises the steps of: buffering each of a plurality of successive portions of the instant voice as the instant message is recorded; transmitting from each successive buffered portion; and delivering each successive portion to the recipients wherein the recipients audibly playing each successive portion as it is delivered."

Structural observation that drives the whole analysis: claim 1 is server-side presence distribution + store-and-forward voice delivery. It contains no client-side recording limitation, no attachment limitation, and no mode-selection limitation. Those all live in dependents 2–8. Consequently the § 103 exposure of claim 1 is much higher than that of claim 3.

3. Reference-by-reference disclosure mapping

3.1 Vuori — US 2002/0146097 A1 ("Short Voice Message (SVM) service method, apparatus and system," Nokia; filed Jul. 23, 2001; published Oct. 10, 2002)

Vuori alone maps every limitation of claim 1, which is why both the Board (IPR2017-00222 FWD; IPR2017-01800 FWD) and the Federal Circuit sustained unpatentability of claim 1 over Vuori.

The one contested term — "list." The Board construed "list" as requiring the connectivity status of more than one node ("each of the nodes"), and found Vuori's buddy list satisfied it. The Federal Circuit affirmed on substantial evidence, holding that the Board was "entitled to credit the testimony of one expert over the other." Uniloc's contrary argument — that Vuori's presence information is not transmitted as a single signal from server to client — is the only serious non-obviousness point on claim 1, and it lost.

3.2 Malik — US 2003/0219104 A1 ("Instant voice messaging")

• Discloses a voice instant message (VIM) server that monitors presence information of clients (¶ 25). This is a direct § 103 substitute for the "monitoring/recording/transmitting a list" limitations if Vuori's "list" reading were rejected.
• Discloses client voice-recording generation and transmission to a server (¶ 33).
• Discloses that "if a recipient client is unavailable to receive the message, the message is stored in a queue and delivered when the recipient client connects to the network." This is an exact textual match for claim 1's final two limitations.
• Does not disclose two different generation modes (record vs. intercom) — the Board and Federal Circuit both so found (Fed. Cir. slip op. at 8–10).

Note the § 325(d) overlay: Uniloc argued in its Preliminary Response that Malik is cumulative with US 2007/0112925 (Malik), cited on the face of the parent '890 patent. The Board did not accept that as a basis to deny institution, but it is a real vulnerability for any repeat § 103 challenge built on Malik (§ 325(d) discretion).

3.3 Lerner — US 6,192,395

• Sound control module for multi-participant audio conferences that routes sound between participants using a plurality of buffers.
• Transmit path: a router "breaks a signal in a transmit buffer into packets that are routed to the participants by a server."
• Receive path: "a plurality of receive sound buffers," with packets routed by participant identity.
• Failed as to claim 8 because the Board found Lerner's receive buffers buffer packets as received by the recipient, not as the message is recorded, and Apple never relied on Lerner's transmit buffer (Fed. Cir. slip op. at 10–11). This is a fixable mapping defect, not a substantive absence of disclosure — see Ground C below.

3.4 Griffin

• Speech (voice) chat messages transmitted between subscribing terminals; potential recipients are associated with each subscribing terminal.
• Queuing at a server complex such that the recipient "can request playback within a predetermined period of time."
• Weaknesses: Samsung's own declarant conceded "Griffin does not provide additional details regarding how this is done" (IPR2017-01800, Ex. 1002 ¶ 130). Uniloc also argued Griffin's mobile terminals are not established to be "within the packet-switched network," attacking the "monitoring … nodes within the packet-switched network" limitation. Despite these attacks, IPR2017-01800 held claims 1–3 unpatentable over Griffin + Zydney.

3.5 Zydney

• Distributed voice messaging using a "voice container"; recipient list maintained by the originator; central server stores and delivers; server delivers stored messages once the recipient becomes available; recipients audibly play.
• Supports attachments (MIME multipart; "digitized greeting card" or other data types attached to the voice container) and a "list of voice containers" presented to the recipient.

Weaknesses identified in the family's IPR record: in Zydney the user (or the user's software agent) supplies and maintains the recipient list, rather than receiving it from a server (IPR2017-01257, Paper 8 at 30). That is fatal to using Zydney as the primary reference against claim 1's "transmitting a signal to a client including a list of the recorded connectivity status," unless Zydney is combined with a server-side presence reference (Vuori/Malik/Griffin).

3.6 Stubbs

• Apple pleaded Stubbs as an alternative primary reference alongside Vuori (see Uniloc's Preliminary Response accusing Apple of "vertical redundancy"). I could not retrieve Stubbs's substantive disclosure in this session, so I do not assert what it teaches. It is listed here because it appears in the prior-art record and would need to be evaluated on its face.

4. Grounds of rejection

Ground A — Claim 1 anticipated/obvious over Vuori alone (§ 102/§ 103)

Every limitation of claim 1 is disclosed by Vuori. Even if "list" were construed to require server-side aggregation of multiple statuses, Vuori's presence service is a server-side presence aggregator distributing status to watchers/subscribers (¶ 44). Predicted result: claim 1 unpatentable. Confirmed: IPR2017-00222 FWD (claim 1 unpatentable over Vuori), aff'd, Fed. Cir. 19-1151; IPR2017-01800 FWD (claims 1–3 unpatentable over Griffin + Zydney).

Ground B — Claims 2–7 obvious over Vuori in view of Malik

• Motivation to combine: both references are in the same field (packet-switched/mobile voice messaging), both expressly address presence of the recipient as the trigger for immediate vs. delayed delivery, and both solve the identical problem the '723 patent identifies — the "need … for providing instant VoIP messaging over an IP network." Vuori itself imports the RFC 2778 presence/buddy-list model (¶¶ 44–46), and Malik supplies the server-side presence monitoring that makes the buddy list dynamic. Under KSR, combining a known presence framework with a known voice-messaging transport is a predictable variation with a clear design incentive (giving a voice-messaging user the "who's online" affordance already standard in text IM — a point the '723 specification itself concedes was known: "Instant text messaging is likewise known… The instant text-messaging server presents the user … with a list of persons who are currently 'online'").
• Claim 2 (attached files): IM attachments and MIME multipart messaging were conventional; Zydney (Ground C) supplies express disclosure; Malik ¶ 31–33 plus general IM practice supplies the motivation.
• Claim 3 (controlling the generation method based on connectivity): FAILED. The Board and the Federal Circuit both held that Vuori and Malik describe different methods of sending/delivering based on connectivity status but not different modes of generating the message. The Federal Circuit: "Whether the message is delivered immediately or at a later time, the message is generated in the same manner—by a voice recording." Because claims 4–7 depend from claim 3, they fell with it.
• Predicted result: claim 2 unpatentable; claims 3–7 not established by this combination. Confirmed: IPR2017-00222 FWD; aff'd, Fed. Cir. 19-1151.

Ground C — Claim 8 obvious over Vuori + Malik + Lerner

• Motivation to combine: Lerner is directed to real-time multi-party audio with buffered packet routing — i.e., exactly the "intercom mode" concept (real-time streaming of successive buffered portions as recorded). An artisan seeking to add a real-time mode to a store-and-forward voice-messaging system would look to audio-conference/buffered-packet transport art.
• Why it failed: (i) claim 8 depends from claim 3, which was not established; and (ii) the Board found Lerner's buffers were receive buffers, buffering packets as received, not as the message is recorded.
• How a better-constructed § 103 case would run: map the buffering limitation to Lerner's transmit buffer / router, which does break the signal in a transmit buffer into packets while the participant is speaking. That is "buffering each of a plurality of successive portions … as the … message is recorded" with a straight face. Apple's petition simply failed to rely on that buffer. This is a pleading defect, not a disclosure gap.

Ground D — Claims 1–3 obvious over Griffin in view of Zydney

• Motivation to combine: Griffin discloses the speech-chat voice message and server-side queuing/playback; Zydney supplies the availability/unavailability status model and central-server store-and-forward delivery with playback once the recipient becomes available. Both are in the same field (network voice messaging), and the combination addresses the known problem of delivering voice messages to intermittently connected terminals. KSR design-incentive rationale applies.
• Result: Succeeded. IPR2017-01800 FWD (Jan. 31, 2019): "Petitioner has shown by a preponderance of the evidence that claims 1–3 of the '723 patent are unpatentable." (https://www.docketalarm.com/cases/PTAB/IPR2017-01800/.../Termination_Decision_Document-34-Termination_Decision_Document.pdf)
• ⚠️ Discrepancy to flag: Google Patents lists IPR2017-01800 as "Settlement," while the document docketed at the January 31, 2019 entry is captioned as a Final Written Decision under § 318(a) finding claims 1–3 unpatentable. Both can be true (a FWD followed by settlement before appeal), but the file name "Termination_Decision_Document" and the settlement label conflict with the FWD text. I flag rather than resolve this.
• Patent Owner's counterarguments (recorded, and worth weighing): (a) Griffin's declarant admitted the recipient-association mechanism was undisclosed; (b) Griffin's mobile terminals were not shown to be "within the packet-switched network"; (c) combining Griffin with Zydney would produce "erroneous behavior for text-only buddies" (a text-only contact would be treated as available for voice). Argument (c) is the strongest teaching-away-type point and is the kind of secondary consideration that could be pressed.

Ground E — Stubbs as alternative primary reference (+ Vuori/Malik/Zydney)

Not substantively evaluable here — Stubbs's disclosure was not retrieved. Its significance is procedural: because Apple pleaded Vuori and Stubbs as alternative primaries for the same limitations, Uniloc attacked the petition as vertically redundant, citing Liberty Mutual and Eizo Corp. v. Barco. Any new § 103 challenge should assert a single strongest primary reference to avoid that attack.

Ground F — Zydney as primary reference (+ Appelman / Griffin)

• In the sibling IPRs, Samsung first used Appelman (US 6,750,881) instead of Griffin against the same concepts, then joined with Griffin. Appelman is therefore a viable secondary/primary reference for the presence-buddy-list element.
• Limitation to watch: Zydney's list is originator-supplied, not server-supplied. Against claim 1's "transmitting a signal to a client including a list of the recorded connectivity status," Zydney must be combined with a server-side presence reference. Patent Owner in IPR2017-01257 made exactly this point, and the Board agreed.

Ground G — Claims 3–8: what a successful § 103 case would need

Claims 3–8 survived because the art of record disclosed delivery-mode switching, not generation-mode switching. To reach claim 3, a petitioner needs a reference teaching that the client's recording behavior changes with recipient presence — i.e., real-time streaming while recording vs. complete-file recording then send. Candidate classes of art (I have not verified any of these as prior art of the correct date in this session, and I say so rather than assert it):

1. Push-to-talk / half-duplex voice art — where a talker's transmission is streamed in real time if the listener is present, and otherwise recorded for later. The '723 specification's own "intercom mode" language and dependent claims 4/6/8 (intercom as default when a recipient is available) track PTT practice.
2. Sibling-family prior art already in the record — e.g., the Weiner references (US 2006/0268750; US 8,917,849, "Method and end-user device for messaging," priority lineage to Vimplicity, WO 2004/100581, "Methods and systems for instant voice messaging and instant voice message retrieval"). Caveat: WO 2004/100581 published Nov. 18, 2004, after the Dec. 18, 2003 priority date, so it is not § 102(b) art. It could only be § 102(e) art if the corresponding application is entitled to an earlier effective date and satisfies the pre-AIA § 102(e) conditions (published PCT designating the US, in English, entering the national stage). I have not verified those conditions and do not assert that this art is available.
3. Prosecution-cited art of record — Sagi (US 2003/0087632), Creamer (US 2003/0126207), Goodman (US 2004/0122906), Bernstein (US 2004/0128356), LaPoint (US 2004/0179092), Williams (US 2004/0252679), Hollowell (US 2005/0105697) — most of which are directed to presence-based messaging or endpoint/stream handling. Several of these were cited during prosecution and would face a § 325(d) hurdle, but they are available as evidence of the state of the art.

5. Cross-cutting motivation-to-combine analysis (the KSR rationales that do the work)

6. Limitations on any § 103 conclusion (stated explicitly)

1. Claim 3 is a genuine § 103 obstacle on the art of record. Two tribunals and the Federal Circuit held the record did not show that connectivity status controls the manner of generating the voice message. The Patent Owner's win here is real, not a technicality — the Board found Figure 4 of Malik shows no logical decision regarding generation at the availability-determination step.
2. § 325(d) risk. Malik (2007/0112925) was cited during prosecution; any new challenge centered on Malik risks discretionary denial.
3. Vertical-redundancy risk. Alternative-primary-reference pleadings (Vuori and Stubbs) drew a sustained objection. Use one primary.
4. Claim construction sensitivity. The word "list" (more than one node?) and the term "node" (device vs. person? — litigated in the sibling '747 proceedings) materially change the outcome. "Node" was argued to mean a device within the packet-switched network, which is the reading most protective of the patent against Zydney's list of people's names.
5. Teaching away. The "text-only buddy" argument (inserting Zydney's available/unavailable status into Griffin would mislabel a text-only contact as available for voice) is the best available teaching-away/undesirable-result theme.
6. No damages/secondary-consideration evidence found. No verdict of infringement or damages award involving the '723 patent appeared in the record; the principal district-court cases were resolved by stipulated dismissals with prejudice. There is therefore no commercial-success evidence in the record for me to weigh on the non-obviousness side.
7. Unverified items. I did not retrieve the substantive disclosure of Stubbs, the petition identities behind IPR2017-01365 (listed "Not Instituted – Merits") and IPR2017-01635 (listed "Pending – Instituted"; a Facebook/WhatsApp petition and motion for joinder into IPR2017-00222 was granted, so those entities are joined as Petitioner there), or the date-sufficiency of the Vimplicity/Weiner family art. I flag rather than assert these.

7. Bottom line

• Claim 1 (and claim 2) are clearly obvious over Vuori alone and over Griffin + Zydney. This is not a close call — it was litigated to an FWD twice, appealed, and affirmed in Apple Inc. v. Uniloc 2017 LLC, No. 19-1151 (Fed. Cir. Feb. 9, 2021) (https://www.courtlistener.com/opinion/[4854957](/patent/4854957)/apple-inc-v-uniloc-2017-llc/). Claims 1–3 were also held unpatentable in IPR2017-01800 over Griffin + Zydney.
• Claims 3–8 were not established as obvious on the art of record. The dispositive distinction is generation-mode control versus delivery-mode control. A fresh § 103 attack on those claims would need art expressly teaching that the client's recording mode (streaming while recording vs. complete-file-then-send) is selected based on recipient presence — a category that the record's Vuori/Malik/Lerner combination does not reach, and which I could not verify was satisfied by any reference of record.
• Net: the presence-list/store-and-forward subject matter that defines the '723 patent's independent claim is squarely obvious; the patent's surviving leverage (now moot, given Expired – Fee Related status with an adjusted expiration of 2025-11-10) sat entirely in the dependent mode-switching claims.