US 7856233

I'll search for authoritative information on US 7856233, including any 2026 CAFC docket activity.

Let me check for litigation, PTAB proceedings, and any 2026 Federal Circuit activity involving this patent.

Important lead: a 2026 Federal Circuit decision in Lemko Corp. v. Microsoft (No. 2024-2336). Let me pin down which patent(s) it involved and whether 7856233 is among them.

US Patent 7,856,233 — Analyst Summary

Bottom line up front: I could not find any 2026 CAFC docket naming U.S. Patent 7,856,233. The only 2026 Lemko–Microsoft Federal Circuit activity I located is Appeal No. 2024-2336, decided April 10, 2026, and it arises from IPR2023-00531, which involves a different patent (U.S. 7,855,988) — not the '233 patent. I flag this because a Law360 headline describes 2024-2336 as involving "a distributed mobile architecture patent," which can easily be misread as the '233 patent. Details below.

1. Bibliographic data (per Google Patents family record and USPTO/PTAB filings)

2. Abstract (verbatim from the record)

"An authentication, authorization, and accounting module of a first distributed mobile architecture is disclosed and includes a home location register. The home location register provides information associated with one or more mobile subscribers that are registered with the first distributed mobile architecture. Also, the information within the home location register at the first distributed mobile architecture is also provided at a first community location register at a second distributed mobile architecture that is accessible to the first distributed mobile architecture. The module further includes a second community location register that includes information associated with one or more mobile subscribers registered with the second distributed mobile architecture."

3. Overview of the independent claims

Caveat on uncertainty: The full-text record I retrieved includes the specification, figures list, and "Summary of the Disclosure," but not the verbatim numbered claim set. I therefore will not quote claim language. What follows is an overview of the claim families the patent describes, each of which corresponds to a distinct statutory class in the Summary section. Treat the claim numbering as unverified; the technical scope described is well-supported by the specification text.

1. Composition/apparatus claim — the AAA-module family (matches the abstract). A first distributed mobile architecture ("DMA") whose authentication, authorization, and accounting module contains (a) an HLR holding records for subscribers registered with that DMA, where that HLR content is mirrored into a "first community location register" (CLR) at a second DMA, and (b) a second CLR holding records for subscribers registered with that second DMA. Dependent-type features described include a third CLR for a third DMA, a VLR for roaming subscribers temporarily registered with the first DMA, and specific data fields.
2. Method claim — single-DMA local call. Register a first and a second mobile subscriber in the HLR of one DMA; receive a call from the first to the second; locate both subscribers in that same HLR; and connect the call entirely within that DMA (specifically, via one or more local IP addresses inside the DMA) — i.e., no backhaul to an MSC/HLR outside the box.
3. Method claim — call across a peer DMA using replicated data. Receive a call at a first DMA destined for a subscriber whose data resides at a second DMA; locate that subscriber's data in a CLR stored at the first DMA (the replicated copy of the second DMA's HLR); then complete the call across the two DMAs (per the described flowchart, by sending a location update request ("LocUpdate") to the second DMA and receiving an acknowledgement carrying the subscriber's current address).
4. Method claim — location update handling (roaming). A second DMA receives a location update request concerning a mobile subscriber, the request having been sent from a first DMA — i.e., claiming the network side of the peer-DMA location reconciliation mechanism (notably not limited to the roaming-subscriber flow of FIG. 8).
5. Apparatus claim — the DMA as a machine. A distributed mobile architecture comprising a processor, a computer-readable medium accessible to the processor, and an AAA module embedded in that medium, the AAA module including an HLR for subscribers registered with that DMA and a CLR containing information corresponding to the HLR of another DMA.
6. System claim — three-peer mesh. A first, second, and third DMA coupled to each other via an Internet Protocol network, where the first DMA includes an HLR, a second CLR associated with the second DMA, and a third CLR associated with the third DMA — i.e., full data replication across a peer-to-peer IP mesh.

Supporting technical context from the specification (useful for claim construction): the DMA is an integrated MSC-module + BSC-module converged in software on a single board (gatekeeper, circuit gateway to ISDN/PSTN, PDSN/GGSN and SIP gateways, SS7 gateway to ANSI-41/GSM MAP, media gateway, AAA module, CRNC/CSDU/CPC, OAMP), and a peer-to-peer IP interconnect between DMAs so that coverage is "self-healing and redundant" with no single point of failure. The CLR concept — replicating each peer DMA's HLR into the other DMAs' AAA modules — is the core differentiator over a conventional centralized HLR/VLR.

4. Litigation, PTAB, and 2026 CAFC status

No 2026 CAFC docket for 7,856,233 was found. What I did find:

• Fed. Cir. No. 2024-2336, Lemko Corp. v. Microsoft Corporation (and Affirmed Networks, Inc.) — appeal from PTAB IPR2023-00531, decided by Rule 36 summary affirmance on April 10, 2026 (per curiam; Hughes, Stoll, and Chief District Judge Seeborg). Oral argument audio posted April 8, 2026. The patent at issue in IPR2023-00531 is U.S. 7,855,988 (Lemko's "System, method, and device for routing calls using a distributed mobile architecture"), as confirmed by the IPR2023-00531 docket record (Respondent Patent Number: 7855988) and Lemko's own appellate briefs referring to "the '988 Patent." The appeal turned on whether the Board failed to construe the term "distributed" in "distributed mobile architecture," and on an alleged waiver of a "communication information" construction argument. This is not the '233 patent.
• Related Lemko PTAB proceedings involve yet other patents: IPR2023-00529 → U.S. 7,653,414; IPR2025-01142 → U.S. 8,310,990 (Petitioner AT&T, with Lemko seeking discretionary denial under Fintiv / §325(d)).
• District court: Lemko Corp. v. Microsoft Corp. and Affirmed Networks, Inc., N.D. Tex. No. 3:22-cv-00363-L-BT (filed Feb. 14, 2022). On June 4, 2025, Judge Sam A. Lindsay adopted the magistrate's report (Doc. 90) and granted-in-part/denied-in-part the defendants' motion to dismiss (Doc. 85): contributory infringement claims dismissed with prejudice; the motion otherwise denied. A further Lemko–Microsoft case, 3:26-cv-01876 (N.D. Tex.), and Lemko Corp. v. AT&T Inc., 2:25-cv-00305 (E.D. Tex.) also appear in 2025–2026 dockets; the AT&T complaint excerpt I reviewed maps 5G functions (UDM/UDR, AMF, SMF, UPF, AUSF) onto legacy HLR/VLR/BSC/MSC claim terms, but the patents identified in that excerpt are 7,979,066 and related family members — I did not see 7,856,233 asserted in the excerpts retrieved.

5. Explicit uncertainties

• Verbatim claims not verified. I did not retrieve the literal text of claims 1–N. The six independent-claim overviews above are derived from the specification's Summary section and flowcharts, which closely track the claims, but I cannot confirm claim numbering, exact transitional language, or the precise limitations without the claim set.
• Whether 7,856,233 was ever asserted in the Microsoft/Affirmed or AT&T suits is not established by the materials I found. The Darts-ip "family litigation filed" flag on Google Patents is family-level, not patent-level evidence.
• Priority date discrepancy (2006-03-29 vs. 2006-03-30) is unresolved in the record; the assignment was executed 2006-03-29 and the application filed 2006-03-30. Google Patents labels the priority date 2006-03-30, while some aggregators (Unified Patents) list 2006-03-29.
• Assignee chain complexity: the 2012 Motorola Solutions "covenant not to sue" assignment and the 2025 Piccadilly Patent Funding security agreement should be reviewed at the USPTO Assignment database before relying on current ownership; the Google Patents "current assignee" field lists Lemko Corp but expressly disclaims accuracy.
• "Active – Reinstated" status and 2028-10-18 adjusted expiration are as listed by Google Patents and are assumptions, not legal conclusions; the reinstatement event is not explained in the record I retrieved.

Primary sources used: Google Patents US7856233B2 family/bibliographic record and full description text; freepatentsonline.com/7856233.html; CAFC Rule 36 judgment PDF for 2024-2336 (cafc.uscourts.gov/opinions-orders/24-2336.RULE_36_JUDGMENT.4-10-2026_2674403.pdf); CAFC oral argument page for 2024-2336; PTAB/IPR dockets for IPR2023-00529, -00530, -00531 and IPR2025-01142; N.D. Tex. docket and Doc. 94 order in 3:22-cv-00363; Law360 (Apr. 10, 2026) and Lemko Corp. press releases (Apr. 15, 2025; May 5, 2021).

I'll research litigation involving US 7856233 across patent litigation trackers and court sources.

Let me dig deeper into the specific Lemko enforcement campaigns to determine which cases actually name the '233 patent.

Let me search specifically for the '233 patent in litigation and any PTAB or ITC proceedings.

Bottom line

I could not confirm any litigation in which U.S. Patent No. 7,856,233 ("System, method, and device for providing communications using a distributed mobile architecture," inventor ShaoWei Pan, original assignee Lemko Corp., filed March 30, 2006, granted December 21, 2010) is actually asserted as a patent-in-suit.

What exists is a family-level litigation flag. The Google Patents record for US 7,856,233 carries a "Family has litigation / First worldwide family litigation filed" banner linked to Darts-IP (https://patents.darts-ip.com/?family=38559838). Google Patents attaches that banner at the patent-family level, not the individual-patent level, so it does not by itself establish that the '233 patent was ever asserted. I was unable to identify a complaint, claim chart, or docket entry naming 7,856,233/7856233 as an asserted patent, and the number does not appear in the asserted-patent lists of the Lemko campaigns I could verify (below). I may be missing a case — treat this as "none found," not as a definitive negative.

Lemko's verified enforcement campaigns (checked against asserted-patent lists — '233 not included)

Sources: Mondaq case note on the two campaigns (explicitly noting the two asserted sets "do not overlap"), https://webiis08.mondaq.com/unitedstates/patent/1622202/; Lemko press releases https://www.lemkocorp.com/lemko-corporation-files-patent-infringement-lawsuit-against-att/ and https://www.lemkocorp.com/update-lemko-corporation-patent-litigation-against-microsoft-and-affirmed-networks/; Docket 94, Lemko Corp. v. Microsoft Corp., No. 3:22-cv-363-L-BT (N.D. Tex. June 4, 2025); Lemko Corp. v. Microsoft Corp., Nos. 2024-2336 (Fed. Cir. Apr. 10, 2026) (Rule 36 affirmance of IPR2023-00531).

Note the asserted lists. US 7,856,233 is conspicuously absent from both the Microsoft and AT&T asserted sets, even though sibling patents from the same failure/specification chain (e.g., '414, '988, '763, '230, '066, '322, '990, '667, '029, '020) are asserted.

Related proceedings that touch Lemko's DMA portfolio (but not '233)

• PTAB — Microsoft Corp. / Affirmed Networks, Inc. v. Lemko Corp.:
  • IPR2023-00529, U.S. 7,653,414 — instituted; Final Written Decision Aug. 30, 2024: no challenged claims unpatentable (Lemko won).
  • IPR2023-00530, U.S. 7,548,763 — denied institution (Sept. 25, 2023).
  • IPR2023-00531, U.S. 7,855,988 — instituted; Final Written Decision Sept. 10, 2024 (Lemko lost; affirmed by Fed. Cir., No. 2024-2336, Apr. 10, 2026).
  • IPR2023-00570, U.S. 9,191,980 — denied institution (Sept. 26, 2023).
  • None of these involve 7,856,233.
• IPR2025-01142, U.S. 8,310,990 (filed against Lemko; Lemko's Patent Owner Preliminary Response invokes Advanced Bionics and the prior Microsoft IPRs). Not 7,856,233.
• Motorola, Inc. v. Lemko Corp. et al., No. 1:08-cv-05427 (N.D. Ill.) — Motorola's trade-secret/ownership action against Lemko, Shaowei Pan, Nicholas Labun, and others, seeking a declaratory judgment that Motorola owned "eight patents and ten pending patent applications" (the "Lemko patents") conceived during Pan's/Labun's Motorola employment. See the court's summary-judgment opinion at https://amlawdaily.typepad.com/lemkoopinion.pdf and Motorola's complaint at http://ia800901.us.archive.org/35/items/gov.uscourts.ilnd.223965/gov.uscourts.ilnd.223965.473.0.pdf. I could not verify whether the '233 patent (or its application 11/393,993) was among the enumerated patents/applications in that case — the published excerpts do not list the numbers, and the litigation period (2008 filing) overlaps with the '233 application. This is the single most plausible candidate for a case "involving" the '233 patent, so it warrants direct docket/pleading verification before you rely on it.
• Assignment/agreement record on the '233 patent itself: the Google Patents reassignment history for US 7,856,233 shows a February 21, 2012 entry — "MOTOROLA SOLUTIONS, INC. — COVENANT NOT TO SUE — Assignors: LEMKO CORPORATION" (consistent with the Feb. 2012 Lemko/Motorola Solutions resolution). This is a contractual instrument recorded against the patent, not litigation. A 2025-03-25 entry records "PICCADILLY PATENT FUNDING LLC, AS SECURITY HOLDER — PATENT SECURITY AGREEMENT — Assignors: LEMKO CORPORATION." Current legal status per Google Patents: Active – Reinstated, adjusted expiration 2028-10-18. Legal status is an assumption, not a legal conclusion.

Candid caveats

1. No confirmed hit. I searched litigation trackers and general web sources for the exact string 7856233 / 7,856,233 and found no case identifying it as a patent-in-suit. Generic hits on that digit string were unrelated (Brazilian/municipal gazettes, a Korean patent-citation listing, etc.) and are not litigation.
2. Coverage limits. I did not have live access to PACER, Docket Navigator, or the Unified Patents litigation portal (https://portal.unifiedpatents.com/litigation/caselist) filtered on this patent; those are the tools that would give a definitive docket-level answer, including any ITC Section 337 action or older suits.
3. The Darts-IP family flag is not patent-specific. It reflects that some patent in Lemko's 38559838 family was litigated — which is true of the Microsoft and AT&T campaigns — and should not be read as evidence about the '233 patent itself.

Recommended next step for a definitive answer: run 7,856,233 against Docket Navigator or Unified Patents' litigation search (patent-level filter), and pull the Motorola, Inc. v. Lemko Corp. (N.D. Ill. 1:08-cv-05427) amended complaint/Exhibit A to confirm whether application 11/393,993 or the issued '233 patent was enumerated.

I'll verify the PTAB landscape for US 7856233 via live search before reporting.

Let me dig specifically into whether any AIA trial targeted the '233 patent itself.

Let me run targeted checks for any proceeding naming the '233 patent directly, including other petitioners and aggregators.

PTAB Proceedings — US 7,856,233 ("System, method, and device for providing communications using a distributed mobile architecture," Lemko Corp.)

Sourcing note: The canonical structured block supplied with this task ("PTAB proceedings on file") reports no AIA trial proceedings for US 7,856,233 as of the most recent USPTO Open Data Portal ingest. I ran independent web searches against PTAB E2E (ptacts.uspto.gov), Docket Alarm, the Unified Patents PTAB case list, and the Federal Circuit docket and found no IPR, PGR, or CBM naming the '233 patent. Everything below is built accordingly; I have not invented any proceeding numbers.

Proceedings overview

Total proceedings on US 7,856,233: 0 (0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denials) — the '233 patent has never been the subject of an AIA trial petition, so it stands erroneously unchallenged at the PTAB and the bottom-line defensive posture is "the patent is untouched but unhardened: no claim has been canceled, and no estoppel forecloses any invalidity ground." That cuts both ways for a defendant — there is no free kill shot in the form of a canceled claim, but also no adverse PTAB precedent and no § 315(e)(2) estoppel constraining what you can raise.

Caveat on completeness: the ODP ingest is necessarily a snapshot. A very recently filed petition (e.g., a 2025–2026 filing not yet indexed) could exist. My searches surfaced none, and the related Lemko-family campaign I did find (below) conspicuously omits the '233 patent.

Per-proceeding entries

None. There are no proceedings to render in the ### {PROCEEDING_NUMBER} format for this patent. I decline to populate that section with fabricated or analogized case data.

Related Lemko-family proceedings (context only — these are on different patents, NOT on the '233 patent)

This matters because it establishes who has been attacking the Lemko DMA portfolio, with what art, and with what results. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) and Affirmed Networks, Inc. filed a coordinated IPR campaign against Lemko in February 2023 in parallel with Lemko Corp. v. Microsoft Corp., No. 3:22-cv-00363-L-BT (N.D. Tex.):

Sources: Unified Patents PTAB case list (petitioner filter: Affirmed Networks), Docket Alarm dockets for IPR2023-00529/00531, and the CAFC Rule 36 judgment (https://www.cafc.uscourts.gov/opinions-orders/24-2336.RULE_36_JUDGMENT.4-10-2026_2674403.pdf).

Key mechanics worth carrying over: the Board's institution record against these patents is mixed — three petitions never got in (the '763, '980, and one '414-adjacent theory), and on the '988 the Board construed "communications information" against the patent owner and Lemko lost on appeal. Microsoft's Waylett/Cope and Waylett/Mauer art, and the Flore reference used against the '988, are family-adjacent prior art that a '233 challenger would want to evaluate — but they were never applied to the '233 claims, and they are not a substitute for a '233-specific § 102/§ 103 theory.

Strategic summary

Claim status on the '233 patent: nothing is CANCELED, nothing is SUSTAINED, everything is UNTESTED. No claim of US 7,856,233 — independent or dependent — has ever been construed by the PTAB, invalidated, or confirmed in an AIA trial. Because the patent issued 2010-12-21 and its adjusted expiration is 2028-10-18, its entire claim set (including any claims added by the reissue/continuation family, e.g., US 8,359,029, which claims priority to the '233 application under 11/393,993) remains live and un-adjudicated.

Estoppel landscape: clean slate. Because no IPR/PGR was instituted against the '233 patent, no § 315(e)(2) estoppel attaches to any petitioner or privy with respect to it. The estoppel generated by the sibling Microsoft/Affirmed IPRs is confined to the patents actually at issue there (the '414 and '988) and to the grounds raised or reasonably raised in those proceedings; it does not bar invalidity theories against the '233 claims. Practically, a current defendant retains the full universe of § 102/§ 103 art usable under § 311(b) (patents and printed publications only), plus § 112 written-description/enablement theories in district court that an IPR cannot reach. Two timing constraints govern: (i) the § 315(b) one-year bar runs from service of a complaint alleging infringement of the '233 patent, so run the calendar the moment an amended complaint adds it; and (ii) any petition must be filed with enough lead time before the 2028-10-18 expiration to make the proceeding worthwhile.

Pattern signals. Microsoft and Affirmed Networks have been the only sustained PTAB challengers to the Lemko portfolio, and they filed as a bloc in Feb-2023 — but their campaign hit the '414, '763, '988, and '980, not the '233. Lemko litigates its patents and appears to be in a monetization posture: the '233 patent carries a "Family has litigation" flag, was subject to a 2012 covenant not to sue in favor of Motorola Solutions, Inc., and on 2025-03-25 was encumbered by a patent security agreement in favor of Piccadilly Patent Funding LLC, as security holder — a financing structure typical of active assertion programs. No defensive aggregator (e.g., Unified Patents) appears in the chain for this patent. The 2025 IPR on the sibling '990 patent shows the family continues to draw fire; the '233 is simply the member of the family that no one has taken a swing at yet.

Recommended next steps

1. Treat the absence as the headline, not a footnote. Zero PTAB activity on a patent that Lemko has asserted across a multi-patent campaign is a genuine signal: either no accused product has squarely implicated the '233 claims yet, or prior challengers judged the claims harder to invalidate than the '414/'988 claims they did attack. Confirm against the district court docket (N.D. Tex. 3:22-cv-00363-L-BT) whether the '233 patent is actually in suit and which claims are asserted.
2. If you are a defendant and the '233 patent is asserted, there is no FWD to lean on — no claim has been canceled, so you cannot point to a PTAB disposition. Your invalidity case must be built from scratch. Budget for a full prior-art search with the DMA specification family (the '233 shares its Fig. 1–23 disclosure with the '763/'988 lineage) as a starting corpus.
3. Preserve the § 315(b) clock. File any IPR within one year of service of a complaint on the '233 patent. If a co-defendant was served earlier, evaluate RPI/privy exposure that could shorten your window.
4. Test the family art as a starting point, not an answer. The Board's treatment of Waylett (US 8,184,603), Cope (US 8,271,619), Mauer, and Flore in the sibling IPRs is instructive on how the Board reads "distributed mobile architecture" and "computer readable medium," but none of it was applied to the '233 claims. Do not assume the '988 FWD's claim-construction reasoning transfers — it is a different patent with different claims, and Lemko's appeal of that FWD (No. 2024-2336) was affirmed without opinion under Rule 36, so it carries no precedential claim-construction value.
5. Monitor for a late-arriving petition. Given the active '990 IPR (IPR2025-01142) and the parallel N.D. Tex. litigation, check PTAB E2E and the ODP docket quarterly. If a petition on the '233 is filed, the statutory milestones to track are: institution decision within ~6 months of filing (35 U.S.C. § 314(b)), and a Final Written Decision within 12 months of institution (§ 316(a)(11)).
6. Do not cite any proceeding number in a brief or demand-letter response without re-verifying it in PTAB E2E. I have deliberately not created one for the '233 patent, and none of the sibling numbers above support a statement about the '233 claims.

I'll research the assignment record and ownership chain for US 7856233. Let me start with parallel searches.

Good context. Now let me pin down the reel/frame numbers and the 2015/2025 recordings.

Assignment & Ownership Analysis — US 7856233 B2

"System, method, and device for providing communications using a distributed mobile architecture"
Appl. 11/393,993 · filed 2006‑03‑30 · issued 2010‑12‑21 · priority 2006‑03‑30 · status Active – Reinstated, adjusted expiration 2028‑10‑18

Data-limitation note (read first). The five post-filing events below are taken verbatim from the Google Patents legal-events record for this patent (https://patents.google.com/patent/US7856233/en#legalEvents), which mirrors the USPTO assignment index. I was unable to retrieve the Reel/Frame numbers or the correspondent of record for any of the recordings — the Assignment Center pages (https://assignmentcenter.uspto.gov/ ; https://assignment.uspto.gov/patent/index.html) were not reachable/indexed in my searches, and no third-party source reproduced the reel/frame metadata for this specific patent. I have not guessed or reconstructed any reel/frame or attorney name. Every such field is marked below as not retrieved. One near-miss worth flagging so it is not mistaken for data: a PTAB filing chains Reel 035949/Frame 0180 to a signing attorney on 2015‑07‑14, but that reel belongs to an unrelated Rovi/TiVo "episode tracking" patent — it is not part of this chain.

Inventors

• Prior employment: Motorola, Inc., staff engineer (Aug 1994) → Director of Advanced Technology and Development (c. 2000), separated 2004‑03‑31.
• Pattern — "departing inventor," but the inverse of a fire-sale tell: Pan left Motorola in March 2004 and filed Lemko's first application in Nov 2004; this application followed in March 2006. Motorola then sued (N.D. Ill. 1:08‑cv‑05427, plus a W.D. Wash. action), contending the DMA/CASSE inventions were conceived during Motorola employment and seeking an order compelling Pan and co‑founder Nicholas Labun to assign the Lemko patents to Motorola. The inventor did not leave the assignee; he remained a Lemko officer/director. So the "all inventors exit within 12 months" fire-sale precursor is not present here — the anomaly is a title cloud raised by a former employer, which is what the 2015 confirmatory assignment appears to cure.
• Note on co-inventorship: Labun is a co‑inventor on sibling Lemko patents (e.g., the '988 and '990 families) but is not a named inventor on US 7856233; the record shows Pan alone (consistent with contemporaneous coverage: "Shaowei Pan is identified as the patents' sole named inventor").

Original assignee

Lemko Corporation (Illinois corporation; incorporated August 2002, operating from 2004).

• Business: wireless network infrastructure — "Distributed Mobile Architecture" (DMA) software and DMA servers. The patent's own specification frames the DMA as a software substitute for a legacy MSC/BSC that can be deployed on commodity hardware.
• Product practice — yes, with evidence: Lemko shipped Node1 and Node2 product lines and states (in its own IPR briefs) that it "commercialized the claims … in its various patent‑practicing products," marked with its patent numbers. Documented deployments: TelAlaska Cellular (2009), Bristol Bay Cellular Partnership (2005), K‑Net / Dryden Municipal Telephone System in northern Ontario (2009), plus Africa and Southeast Asia.
• Current status: Operating, private (formerly VC‑backed; ~$14.3M raised over 5 rounds; ~25–29 employees; still issuing press releases through 2025). HQ: 935 National Parkway, Schaumburg, IL. Subsidiary TazcaConnects is closed.
• Litigation posture: Lemko has been an active plaintiff — Lemko v. Microsoft & Affirmed Networks (N.D. Tex., filed 2022‑02‑14) and Lemko v. AT&T (E.D. Tex. 2:25‑cv‑00305, ~May 2025) — and a defendant in Motorola v. Lemko (2008). Google Patents carries a "Family has litigation" flag with a Darts‑IP family link (family 38559838).
• Assignee of record today: Lemko Corp (unchanged). No recorded instrument transfers title out of Lemko.

Assignment timeline

*(All five records below appear in the Google Patents legal-events feed. Execution date is shown where the feed exposes it; otherwise the event date is the record date. Reel/Frame and Correspondent: not retrieved — see the data-limitation note above.)*

1. 2006‑03‑29 executed / recorded c. 2006‑03‑30 — Reel not retrieved

   • Conveyance: Assignment of assignors' interest
   • Assignor: Pan, ShaoWei
   • Assignee: Lemko Corporation
   • Correspondent: not retrieved (single occurrence in any event — no recurrence can be established)
   • Context: Standard pre‑filing inventor→company assignment, executed one day before the 2006‑03‑30 filing date.

2. 2006‑08‑16 recorded — Reel not retrieved

   • Conveyance: Change of assignee's address (no transfer of title)
   • Assignor: Lemko Corporation
   • Assignee: Lemko Corporation
   • Correspondent: not retrieved
   • Context: Administrative address update only — not an ownership event. (Do not count this as a link in the chain.)

3. 2012‑02‑21 recorded — Reel not retrieved

   • Conveyance: Covenant not to sue (recorded through the assignment system, hence its appearance as an "assigned to" event)
   • Assignor: Lemko Corporation
   • Assignee/beneficiary: Motorola Solutions, Inc.
   • Correspondent: not retrieved
   • Context: Litigation‑driven defensive carve‑out out of Motorola v. Lemko, not a title transfer — Lemko retained ownership. Coverage of sibling patent US 7,855,988 by a Motorola covenant is separately noted in trade coverage; the Google Patents record shows the same 2012‑02‑21 instrument against this patent as well, indicating a family‑wide covenant.

4. 2015‑05‑13 recorded — Reel not retrieved

   • Conveyance: Assignment of assignors' interest (second, confirmatory)
   • Assignor: Pan, ShaoWei
   • Assignee: Lemko Corporation
   • Correspondent: not retrieved
   • Context: Chain‑of‑title cure/confirmatory assignment by the sole inventor to the entity that already owned the patent — consistent with shoring up record title after the Motorola ownership challenge (Motorola had sought to compel assignment to Motorola; the 2012 summary‑judgment opinion turned on Lemko having recorded its interest first).

5. 2025‑03‑25 recorded — Reel not retrieved

   • Conveyance: Patent security agreement (security interest / lien — not an assignment of title)
   • Assignor (grantor): Lemko Corporation
   • Assignee (secured party): Piccadilly Patent Funding LLC, as security holder
   • Correspondent: not retrieved
   • Context: Patent collateralization / monetization financing — Lemko hypothecated the portfolio to a funding entity. Ownership of record did not move; this is a lien, not a shell‑entity transfer. Timing is notable: recorded ~6 weeks before the AT&T suit surfaced (E.D. Tex. 2:25‑cv‑00305).

No sixth link exists. In particular, there is no recorded transfer of title away from Lemko, and no assignment to any entity on the classic NPE lists.

Timeline diagram

timeline
    title Ownership of US 7856233
    2006 : Pan assigns rights to Lemko Corp
         : Application filed 30 March 2006
         : Lemko address change recorded
    2010 : US 7856233 issues
    2012 : Motorola covenant not to sue recorded
    2015 : Pan confirmatory assignment to Lemko
    2025 : Patent security agreement to Piccadilly

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
Title has never moved to a licensing-only LLC. The only entities on the chain are Lemko Corporation (operating; ships Node1/Node2; ~25–29 employees; real carrier customers in Alaska, Ontario, Africa) and a security holder, Piccadilly Patent Funding LLC (event dated 2025‑03‑25), which holds a lien, not title. A "funding" LLC named on a security agreement is a financing party, and the recording is expressly "as security holder." The related 2012‑02‑21 instrument (Motorola Solutions) is a covenant not to sue, again not a transfer. Naming alone is not treated as a finding here; there is no evidence of a productless successor owner.

2. Known asserter in the chain — NOT PRESENT.
No assignee or predecessor matches Acacia, Marathon, Intellectual Ventures, IPNav, Wi‑LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation, or any Spangenberg entity. Lemko does appear as a plaintiff in RPX Insight litigation documents (e.g., the AT&T complaint hosted at insight.rpxcorp.com) and in Unified Patents' patent pages — but those are litigation-database and patent-record entries, not NPE-list designations. Lemko is the operating company asserting its own operating patents.

3. Repeat correspondent across the chain — UNCLEAR (cannot be evaluated).
The correspondent of record was not retrievable for any of the five recordings, so recurrence cannot be tested. I decline to name any attorney or firm on inference. The one attorney signature that surfaced in adjoining research (a "/Drew J. …" signature dated 2015‑07‑14 chaining Reel 035949/Frame 0180) belongs to an unrelated Rovi/TiVo episode‑tracking patent and is not part of this chain.

4. Cascading transfers through chained LLCs in <24 months — NOT PRESENT.
Five events span 19 years (2006→2025) and only two are ownership events (2006‑03‑29, 2015‑05‑13), both to the same assignee, Lemko. There is no rapid LLC‑to‑LLC ladder, no shared registered‑agent clustering visible, and no common‑principal pattern.

5. Pre-litigation transfer within 6 months of first suit — NOT PRESENT for title; the closest event is a financing.
The assertion campaigns run without any pre‑suit title transfer — Lemko has been the owner of record continuously since 2006 and is the named plaintiff. The 2025‑03‑25 security agreement to Piccadilly is ~6 weeks ahead of the E.D. Tex. AT&T filing, but a security interest does not set standing or venue and is not a transfer of ownership. Flagged as timing‑notable, conveyance‑insufficient.

6. Bankruptcy fire‑sale — NOT PRESENT (on the available record).
No Chapter 7/11, receivership, or ABC sale is evidenced. Lemko is currently described as operating, revenue‑generating and active in 2025–2026. Its 2008–2012 Motorola exposure was a trade‑secret/ownership suit, not a bankruptcy, and it did not result in a sale of the patents.

7. Privateering — NOT PRESENT.
The vector is the opposite of privateering: this is an operating company asserting its own patents in its own name against alleged copiers (Microsoft, Affirmed Networks, AT&T). The 2012 Motorola instrument is a defensive covenant running to a large operating company, i.e., it immunizes Motorola rather than arming a proxy.

8. Defensive aggregator at end of chain — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. The inverse signal (patent neutralized) does not apply. The 2012‑02‑21 Motorola covenant neutralizes the patent only against Motorola Solutions, not industry‑wide.

Additional observation not in the eight categories: the 2025‑03‑25 patent security agreement to Piccadilly Patent Funding LLC is a genuine hall‑mark of patent monetization/litigation financing — a small, formerly VC‑backed operating company collateralizing its portfolio on the eve of a new multi‑defendant campaign. It strengthens the "litigation is now a core revenue line" reading without making Lemko a non‑practicing entity.

Verdict

Operating-company assertion.

The chain is short and clean: inventor Pan → Lemko Corporation (2006‑03‑29) → confirmatory re‑assignment by the same inventor to the same owner (2015‑05‑13), with a defensive Motorola Solutions covenant (2012‑02‑21) and a security interest to Piccadilly Patent Funding LLC (2025‑03‑25) that never moved title. The assignee of record remains Lemko Corp, which demonstrably ships patent‑marked products (Node1/Node2, deployed with TelAlaska, Bristol Bay, K‑Net/DMTS) and is suing actual competitors — Microsoft, Affirmed Networks and AT&T — not downstream end users or anonymous licensees. There is exactly one weak, non‑dispositive indicator (the 2025 collateralization of the portfolio to a litigation‑funding entity); it is a financing tell, not an NPE tell, and cannot carry a "moderate confidence NPE" call on its own.

Verify at: https://assignmentcenter.uspto.gov/ (search patent number 7856233) and https://assignment.uspto.gov/patent/index.html — retrieve the Reel/Frame and Correspondent fields there; those are the two data points I could not confirm, and the Correspondent field is the only remaining way to test signal #3.

I'll research US patent 7856233 and its prior art citations.

Let me look for the specific "References Cited" section on the patent's front page.

Let me try to retrieve the actual front-page references from the patent's Google Patents entry.

Prior-Art Analysis — US Patent 7,856,233 B2

1. Identification of the Patent (as instructed, verbatim)

Important sourcing caveat (stated up front rather than fabricated): The authoritative full text I was given for US 7,856,233 contains the specification, abstract, and classification data, but it does not include the front-page "(56) References Cited" list. I was unable to retrieve the exact examiner-cited reference list printed on the '233 front page within the available search steps. The references enumerated in Section 3 below are drawn from the front pages of the closely related Lemko sibling patents — US 7,653,414 B2 (same inventor, same title, granted 2010‑01‑26) and US 8,310,990 B2 — which share the same specification family, plus references developed in the Lemko IPR/litigation record. Because '233, '414, and '990 are in the same Lemko DMA family with overlapping disclosures, these references are highly relevant to '233, but you should treat this list as "strongly indicative, pending confirmation against the USPTO PatentCenter Image File Wrapper for 11/393,993," not as a verbatim transcription of the '233 front page.

2. The Claims Being Tested

From the specification/abstract of '233, the claims fall into these families:

• Claim 1 (apparatus/module): An AAA module of a first DMA comprising a home location register (info on subscribers registered with the first DMA); the HLR information is also provided at a first community location register at a second DMA accessible to the first DMA; and the module further comprises a second CLR containing information associated with subscribers registered with the second DMA.
• Claims 2–7 (dependents): third CLR associated with a third DMA; HLR contents (IMSI, ESN, MDN, location indicator, TLDN, registration indicator, timer, MSC/ISDN/VoIP preference indicators); CLR contents (IMSI, ESN, MDN); VLR contents.
• Claims 8–10 (methods): registering two subscribers in one DMA HLR and completing a call locally; call setup using a CLR lookup at the first DMA; and receiving a Location Update request at a second DMA sent from a first DMA.
• Claims 11–12 (device/system): DMA = processor + computer-readable medium + embedded AAA module (HLR + CLR of another DMA); system of first/second/third DMAs coupled via an IP network, with the first DMA holding HLR, a second CLR (2nd DMA) and a third CLR (3rd DMA).

The technical core that distinguishes this family is the distributed, replicated subscriber database (HLR at each DMA, with mirrored CLRs propagating HLR contents to peer DMAs over a peer-to-peer IP network).

3. Patent References and § 102 Analysis

A. References confirmed in the Lemko DMA family citation records

US 4,284,848 — Frost, "Mobile Radio Telephone System" — granted 8/1981

• Description: Early cellular/mobile radio telephone architecture with centralized switching coordination.
• § 102 potential: Low. Predates distributed IP-based core and the CLR concept entirely. Anticipates nothing in claim 1. Relevant only as background art.

US 5,590,175 — Gallant et al. — granted 12/1996

• Description: Cellular system with mobility management/home register-type subscriber databases.
• § 102 potential: Low–moderate. Discloses HLR/VLR mobility management but in a centralized core; no disclosure of a CLR replica at a peer node with a distributed AAA embedded in a remote switch. Cannot anticipate claim 1 or 11 singly; relevant to the HLR/VLR-content claims (5, 6, 7) as evidence of conventional subscriber-record fields.

US 6,122,499 — Magnusson — granted 9/2000 (and US 6,141,564 Bruner et al., 10/2000; US 6,160,804 Ahmed et al., 12/2000)

• Description: Cellular mobility/database and roaming-registration art.
• § 102 potential: Low–moderate, same reasoning as Gallant — establishes conventional HLR/VLR practice and roaming registration. Relevant as secondary evidence against the novelty of the record-content dependent claims, not the distributed-CLR independent claims.

US 7,136,651 B2 — Kalavade — granted 11/14/2006 (filed earlier; pre-dates '233 priority)

• Description: A distributed / softswitch-style mobile architecture with call control and subscriber data functions.
• § 102 potential: Moderate. This is the most architecturally comparable of the confirmed references. If Kalavade discloses a distributed switch with replicated/remote subscriber-database access, it is the best candidate under § 102(a)/(e) against claim 11 (DMA = processor + CRM + AAA module) and against claims 8–10 (call-setup and Location-Update methods). Whether it discloses the specific "second community location register storing the HLR of the second DMA" limitation requires element-by-element comparison — I cannot assert it does with high confidence.

US 6,816,706 B1 — Hohnstein — granted 11/2004 and US 6,871,072 B1 — Meche — granted 3/2005

• Description: Wireless/cellular call-routing and gateway art.
• § 102 potential: Low–moderate. Both are cited in the sibling '414 front page. Relevant to routing/method claims (8–10) but unlikely to disclose the CLR replication structure of claim 1.

US 6,760,325 B1 (7/2004); US 6,807,431 B2 — Sayers et al. (10/2004); US 6,515,985 B2 — Shmulevich et al. (2/2003); US 6,411,825 B1 — Csapo et al. (6/2002); US 6,418,838 B1 — Heinonen et al. (7/2002); US 6,421,325 B1 — Kikinis (7/2002); US 6,539,237 B1 — Sayers et al. (3/2003); US 6,542,497 B1 — Curry et al. (4/2003)

• Description: Assorted wireless-switching, IP-telephony gateway, and distributed-network art.
• § 102 potential: Low, individually. These form the general § 103 combination landscape rather than single-reference § 102 art.

Statutory Invention Registration H1918 — Hoffmann et al., "Integrated Authentication Center and Method for Authentication in a Wireless Telecommunications Network" — filed 2/19/1998, published 11/7/2000

• Description: Integrated authentication center for subscriber authentication in a wireless network.
• § 102 potential: Moderate–high for the AAA-module claims. This is a name-matched reference to the authentication, authorization, and accounting concept that claim 1 recites. It is the single best candidate to show that a combined authentication/AAA function in a wireless network was known. However, it does not disclose the distributed CLR replication among peer DMAs, so it cannot anticipate claim 1 as a whole; it is best used in a § 103 combination.

Published applications cited in the family: US 2001/0036173 (Shmulevich et al., 11/2001); US 2001/0055298 (Baker et al., 12/2001); US 2002/0055802 (Sandroffi, 5/2002); US 2003/0153343 (Crockett et al., 8/2003); US 2004/0018829 (Raman et al., 1/2004); US 2007/0202847 A1 (8/30/2007).

• § 102 potential: The pre-2006 publications are § 102(a)/(b) art but individually disclose only pieces (IP-telephony, distributed networking). US 2007/0202847 A1 is post-'233-priority and cannot be § 102 art against '233; it is a § 102(e)/§ 103-type reference only against later Lemko cases. I flag it because it appears in the '414 record — it should not be used as prior art against '233.

B. References developed in the Lemko IPR/litigation record (most probative)

US 7,395,085 B2 — Mauer et al. ("Mauer") — used as Exhibit 1005 in IPR2023‑00529 against US 7,653,414

• Description: Voice-mail / call-routing architecture for wireless networks; cited for the "destination preference register" and "community location register" concepts.
• § 102 potential: High candidate for the CLR-dependent claims (claims 1, 2, 11, 12). In the PTAB proceeding, Petitioner relied on Mauer for the "community location register" element. If Mauer discloses a register (replicated/remote) holding subscriber information for a second network node, it is arguably anticipatory of the CLR-based independent claims — subject to whether its register is at a peer DMA over an IP network.
• Source: https://www.docketalarm.com/cases/PTAB/IPR2023-00529/Microsoft_Corporation_v._Lemko_Corp/docs/07-09-2024-Petitioner/Pet_Reply_to_PO_Resp-37-Petitioners_Reply_to_Patent_Owners_Response.pdf

US 8,184,603 B2 — Waylett et al. ("Waylett," "Network-in-a-Box") — Exhibit 1006 in IPR2023‑00529

• Description: Self-contained / boxed cellular network (MSC/BSC/HLR functions in a single compact unit).
• § 102 potential: The single most relevant structural reference. Waylett's "network-in-a-box" describes integrating core-network functions (including subscriber databases) into a compact, deployable unit — directly material to claim 11 (DMA unit = processor + CRM + embedded AAA/HLR/CLR). Whether Waylett discloses the second and third CLRs at the first DMA mirroring peer DMAs is the dispositive question; the PTAB record shows the parties disputed exactly this. Best used as § 102 art for the DMA-as-a-unit claims and in combination for the distributed-register claims.

US 7,548,763 B2 — (Lemko/Pan family, filed 2005‑04‑12) "Communications Using a Distributed Mobile Architecture"

• Description: Same inventor/assignee, earlier-filed Lemko DMA disclosure.
• § 102 potential: High under § 102(e) as a co-pending/earlier application by the same inventive entity for the claims it supports — it can be prior art against '233 if its disclosure (not merely its claims) support the distributed DMA/AAA/CLR elements. Because it is the same family, it may also be a § 102(b) or § 102(e) reference depending on publication timing. Note the potential § 103(c)/common-ownership complications.

US 2008/0039144 A1 (Lemko, filed 2005‑04‑12) — same family; note that its April 2005 filing predates '233's March 2006 date and may qualify as § 102(e) art against '233.

C. Non-patent literature in the family record (for completeness)

• Hoffpauir et al., Statutory Invention Registration H1918 (1998/2000) — see above.
• B.G. Evans & K. Baughan, "Visions of 4G," Electronics & Communication Engineering Journal, Dec. 2000, pp. 293–303.
• S. Das, A. Nandan & G. Pau, "SPAWN: A Swarming Protocol for Vehicular Ad-Hoc Wireless Networks," VANET '04, Oct. 1, 2004.
• Y.-C. Tseng, C.-C. Shen & W.-T. Chen, "Integrating Mobile IP with Ad Hoc Networks," IEEE Computer, May 2003, pp. 48–55.
• H. Yanikomeroglu, D.D. Falconer & V.M. Steng, "Coverage Enhancement Through Two-Hop Peer…" (IEEE, 2002).
• GSM Networks: Protocols, Terminology, and Implementation, Heine, Artech House, Dec. 1998; Newton's Telecom Dictionary, 20th ed., Mar. 2004 (these last two appear in the IPR exhibit list).

4. Bottom-Line Assessment

1. No single confirmed reference anticipates claim 1 or claim 11 in full. The distinguishing limitation is the distributed, replicated register structure (HLR at DMA‑1 mirrored into CLR‑1 and CLR‑2 at peer DMA‑2/DMA‑3, interconnected by a peer-to-peer IP network). The confirmed pre-2006 references (Frost, Gallant, Magnusson, Bruner, Ahmed, Csapo, Kikinis, etc.) disclose pieces of conventional cellular/HLR/VLR or IP-telephony architecture but were not shown to disclose that replication topology.

2. The best § 102 candidates, in descending order of strength:

   • Waylett (US 8,184,603) — for the "DMA as an integrated unit" claims (claim 11) and possibly the register claims.
   • Mauer (US 7,395,085) — for the "community location register" element of claims 1, 2, 11, 12.
   • Kalavade (US 7,136,651) — for distributed call-control/subscriber-data architecture (claims 8–10, 11).
   • Hoffpauir H1918 — for the "authentication/AAA" limitation of claim 1.
   • US 7,548,763 / US 2008/0039144 A1 (Lemko family, earlier filed) — for § 102(e) treatment of the DMA/AAA disclosure.

3. Most of these references are, in practice, § 103(c) combination art, not § 102 anticipation art. The Lemko IPR record (IPR2023‑00529, ‑00531; the '414 and '988 patents) confirms that the challengers proceeded on obviousness grounds combining Mauer + Waylett, precisely because no single reference disclosed the full distributed-register architecture. This reasoning transfers to '233, whose claims recite the same CLR/HLR/peer-IP structure.

4. Caveats you should carry forward: (a) the exact front-page "(56) References Cited" list for 11/393,993 was not retrievable in this session — confirm against the USPTO PatentCenter IFW before relying on any individual citation here; (b) US 2007/0202847 A1 is post-priority and must not be treated as prior art against '233; (c) dates for the older references were taken from family records and should be verified.

Primary sources:

• https://patents.google.com/patent/US7856233/en
• https://www.freepatentsonline.com/7856233.html
• https://www.sumobrain.com/patents/us/System-method-device-providing-communications/7856233.html
• https://www.docketalarm.com/cases/PTAB/IPR2023-00529/Microsoft_Corporation_v._Lemko_Corp/docs/07-09-2024-Petitioner/Pet_Reply_to_PO_Resp-37-Petitioners_Reply_to_Patent_Owners_Response.pdf
• https://patentimages.storage.googleapis.com/17/d9/dd/e4711745857c86/US8310990.pdf (sibling front-page reference list)

I'll research this patent's prior art landscape before building the §103 analysis.

Let me pull the actual prior-art references cited on the face of this patent and in the related litigation/IPRs.

§103 Obviousness Analysis — US 7,856,233 B2

Patent: US 7,856,233 B2 ("System, method, and device for providing communications using a distributed mobile architecture")
Appl. No.: US 11/393,993 · Filed: 2006-03-30 · Priority: 2006-03-30 · Granted: 2010-12-21
Inventor: ShaoWei Pan · Original/current assignee: Lemko Corp
Source page: https://patents.google.com/patent/US7856233/en

0. Two threshold caveats you should read first

(a) The claim set was truncated in the material provided. The page text supplied to me cuts off inside the FIG. 20 description and never reaches the "Claims" section. My limitation mapping below is therefore reconstructed from (i) the disclosure's own claim-style summary passages and (ii) the claim language that appears in the sibling publication US 2007/0232267 A1 (https://patents.google.com/patent/US20070232267), which recites "at least one community location register, wherein the at least one community location register includes information associated with a home location register of another distributed mobile architecture" and a system claim reciting first/second/third DMAs coupled "via the Internet protocol network," the first DMA comprising a second CLR associated with the second DMA and a third CLR associated with the third DMA. Verify against the granted claims before relying on this.

(b) This patent is pre-AIA. Filed 2006-03-30, so pre-AIA 35 U.S.C. § 103(a) governs, together with pre-AIA §§ 102(e) and 103(c). On the face of the record the "prior art" material the page itself supplies is thin: Google's prior-art keywords are merely dma, dma system, mobile subscriber, mobile, registered, and the classifications are H04W88/02 (terminal devices) and H04W8/02 (processing of mobility data / registration information at HLR or VLR). That H04W8/02 classification is the single most damaging signal on the page: it places the claimed subject matter squarely in the well-trodden HLR/VLR registration art.

I could not retrieve the "References Cited" list printed on the front page of the '233 patent, and I will not invent one. The references analyzed below are the ones actually on the public record: the references asserted against the sibling Lemko patent US 7,653,414 in IPR2023-00529 ([Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) and Affirmed Networks, Inc. v. Lemko Corp.) — i.e., Mauer, US 7,395,085 and Waylett, US 8,184,603 — plus the Flore reference relied on in the related PTAB/monitoring proceeding.

1. The claim architecture to be attacked

Stripping the specification to its inventive core, the claims (as described) require:

Every one of these elements is a conventional mobility-management primitive, recomposed. The novelty, if any, lives in the distribution of the registers across peer nodes and in "pre-fetching" a neighbor's HLR into a local CLR.

2. Ground 1 (primary): Mauer in view of Waylett

Mauer — US 7,395,085 (Ex. 1005 in IPR2023-00529) discloses a system integrating a WWAN and a WLAN, with subscriber databases and an alternative-communication-option trigger when a called party is unreachable.
Waylett — US 8,184,603 (Ex. 1006) discloses a "network in a box": MSC, BSC-style, and core-network functions collapsed into a single integrated appliance.

Why a POSITA would combine them. The '233 patent's own background supplies the motivation verbatim: a legacy MSC + BSC + HLR/VLR deployment "can cost over $2.0 million" and "may require a minimum of ten thousand users in order to be economically viable." Waylett teaches precisely the cost-and-footprint collapse the patent says the market needed; Mauer teaches that cellular and packet networks can be interworked over IP with shared subscriber/register databases. Both are in the same field (wireless network infrastructure), both address the same recognized deficiency (expensive, hardware-heavy core networks), and the combination is a mere predictable, finite-solution arrangement of known elements — the KSR "design need / market pressure / finite number of identified, predictable solutions" rationale.

Where it lands. Claim 1's system claim and the FIG. 6 single-DMA method claim are strongly implicated. The register elements (HLR/VLR, location caching) are the ordinary stock-in-trade of ANSI-41/GSM mobility management, and the patent admits as much by defining its registers purely in terms of IMSI/ESN/MDN/TLDN — standard ANSI-41/GSM fields.

The real fight. This is exactly the fight Lemko won on paper in the sibling IPR: Lemko argued the asserted references "are based on the conventional network approach," that Waylett's Network-in-a-Box is a "hardware-based" appliance rather than software-embedded MSC/BSC functionality in a computer-readable medium, and that Mauer/Waylett supply no rational motivation to combine. Petitioners countered that "distributed mobile architecture" carries only its plain and ordinary meaning and that the Board need not narrow it (https://www.docketalarm.com/cases/PTAB/IPR2023-00529/...). The Federal Circuit appeal materials indicate the Board declined to adopt Lemko's narrow construction of "distributed" and considered the narrow reading "incorrect" (https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1558047](/patent/1558047)/...). Outcome-informing point for the '233 patent: if "distributed mobile architecture" is construed broadly (plain meaning), Mauer+Waylett is a viable §103 ground against the '233 claims. If it is construed to require distributed call-routing functionality and mandatory peer-to-peer connections (as Lemko urged), the same combination fails — because Mauer and Waylett describe centralized/hierarchical core elements.

3. Ground 2: Flore (3G/4G architecture) — anticipation-flavored obviousness

Microsoft relied on Flore as disclosing conventional 3G and 4G networks. I could not confirm the exact Flore patent number from the search results and will not guess at one; treat this as "the Flore reference identified in the IPR2023-00529/related PTAB record."

A 3G/4G network with an HLR/HLR-plus-HSS, a distributed set of RNC/node elements and IP transport between them discloses, or at minimum renders obvious, the '233 system claim if the claims only require multiple architectures coupled by an IP network plus per-node subscriber registers. Lemko's counter — that 3G/4G "rely on centralized hubs for call routing" — is a claim-construction argument, not a technical-identity argument. Under plain meaning, this ground is strong; under Lemko's construction, it collapses.

4. Ground 3: Mauer/Waylett/Flore + a location-register replication reference (for the CLR + LocUpdate limitations)

The CLR/HLR-replication and LocUpdate-request-acknowledgement limitations (FIG. 7 blocks 704, 710-716; FIG. 8 blocks 804-830) are textbook distributed-database replication plus ANSI-41/GSM MAP location updating:

• GSM/ANSI-41 MAP location update (the "Location Update Request → Update Location → acknowledgement with routing/address information" sequence) is the literal ancestor of the claimed LocUpdate flow. The '233 specification itself uses the terms "ANSI-41 interface … can be used for roamer registration" and "GSM Mobile Application Part (MAP)."
• Gateway Location Register (GLR) concepts (3GPP TS 23.119 family) and hierarchical/VLR-HLR caching teach capping or replicating HLR data at intermediate nodes so that a querying node holds a local copy of a visited subscriber's data — functionally the claimed CLR.
• Generic distributed database replication / caching teaches "pre-fetching" a peer's records into a local store.

Motivation: the patent states its own motivation — avoiding expensive centralized infrastructure and enabling self-healing, redundant, de-centralized operation. Any POSITA building a multi-node wireless system on an IP backbone would replicate subscriber location data at peers to (i) cut signaling latency and backhaul cost, (ii) enable local call completion when a node is isolated, and (iii) support roaming. That is a recognized engineering trade-off with predictable results (KSR; Winner Int'l; In re ICON Health), not an inventive leap.

5. Ground 4: Lemko's own earlier filings — a trap with a 103(c) escape hatch

The '233 family sits on top of earlier Lemko/Pan applications that published only after the '233 filing date but were filed well before it:

• US 2006/0098661 A1 — filed 2004-11-08 ("System, method and device for providing communications using a distributed mobile architecture")
• US 2006/0234747 A1 and US 2006/0234774 A1 — filed 2005-04-13
• US 7,653,414 — the sibling asserted in IPR2023-00529

These are facially §102(e) prior art (published application / patent effective as of its filing date). However, pre-AIA §103(c) disqualifies subject matter that is prior art only under §102(e), (f), or (g) where the subject matter and the claimed invention were commonly owned or subject to an obligation of assignment to the same person at the time the invention was made. Lemko owned all of them, and the 2006-03-29 assignment record (Pan → Lemko) is on the face of the '233 page. So a self-collision ground is likely unavailable, and the real exposure there is obviousness-type double patenting, not §103 — unless the earlier applications were directed to a materially different inventive entity (e.g., "Pan et al." vs. "Pan") and ownership could not be traced, which the record does not support.

6. Ground 5: Lemko's own pre-2005 public disclosures (the sleeper §102(b) issue)

The Motorola litigation record (https://amlawdaily.typepad.com/lemkoopinion.pdf) establishes that Lemko circulated CASSE/"distributed architecture" PowerPoints and diagrams in 2002-2004 — e.g., a July 2003 e-mail attaching a PowerPoint "describing CASSE technology, which includes a description of its 'distributed architecture' as well as multiple diagrams and designs," and documents advertising "The Lemko DMA Architecture - Block Diagram" prior to Q2 2004.

Because the '233 critical date is 2005-03-30, any public disclosure of that material before that date is §102(b) prior art or a §102(b) public-use/on-sale issue against the patentee's own application. The same record shows the court found "Motorola has shown that Pan and Labun may have conceived of DMA … while employed by Motorola" — a derivation/inventorship exposure that would sit on top of, and interact with, the §103 analysis. I flag this as investigate, do not assume: I cannot verify from the search results that any particular 2002-2004 document was publicly accessible, and the litigation exhibits are characterized second-hand.

7. Bottom line

1. The §103 case is strong if, and essentially only if, "distributed mobile architecture" gets its plain meaning. Under that construction, Mauer (US 7,395,085) + Waylett (US 8,184,603) — the very combination the Board apparently credited in IPR2023-00529 against sibling US 7,653,414 — maps onto the register-plus-single-appliance-core claims, and a second-layer reference teaching HLR data replication (GSM MAP location updating / GLR-style caching) supplies the CLR and LocUpdate limitations with an obvious latency-, cost- and resilience-based motivation.
2. The patent's entire defensive value is its claim construction of "distributed." Lemko's briefs argue the term requires distributed functionality and peer-to-peer connection; if that construction holds, every one of the grounds above fails at the threshold because Mauer, Waylett, and Flore all describe centralized appliance or hierarchical architectures.
3. Secondary considerations are genuinely in play. Lemko has asserted long-felt need (rural/low-ARPU deployments priced out of $2M MSC/BSC/HLR-VLR builds), commercial success of the Node1 product, and third-party praise (the AT&T "Network Functions Virtualization" whitepaper sequence and Ms. Chiosi's "radical design" characterization). A petitioner must rebut nexus — in the sibling IPR, Petitioners attacked nexus by arguing the commercial-success evidence referred to a 4G Node1 product while the claims read on a 3G product.
4. Self-referential prior art will not work. Lemko's own 2004/2005 applications are trapped by pre-AIA §103(c) common ownership; attack those via double patenting or via §102(b) public disclosures, not §102(e)+§103.

Confidence: high on the legal framework, the claim architecture, and the identity of Mauer/Waylett as the operative record references; medium on the Flore reference's bibliographic details (number unconfirmed) and on the ultimate outcome of IPR2023-00529; low/unverified on the '233 patent's own front-page "References Cited" list, which I was unable to retrieve and have not fabricated.