US 7840230

I'll verify the litigation/assignment posture with targeted searches before summarizing.

Let me check the litigation posture more precisely, including any 2026 Federal Circuit activity.

US 7,840,230 — Verification Summary

Important scope note up front: I was able to confirm bibliographic data and litigation references for the '230 patent, but I did not find any Court of Appeals for the Federal Circuit 2026 docket that involves the '230 patent. The only Lemko-related CAFC activity dated 2026 that surfaced was a Rule 36 affirmance on April 10, 2026 in Lemko Corp. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), Affirmed Networks, Inc., No. 2024‑2336, which is an appeal from IPR2023‑00531 — U.S. Patent 7,855,988, a sibling Lemko DMA patent, not the '230 patent. Reporting (Law360, Apr. 10, 2026) describes it generically as "a distributed mobile architecture patent," which is how the confusion likely arises. Do not attribute that affirmance to the '230 patent.

Bibliographic data (as listed on Google Patents, cross-checked against Unified Patents and Justia)

Discrepancy flag: The day-level differences above (April 12 vs. 13; May 21 vs. 22; Nov. 22 vs. 23) are inconsistent across sources. I am treating the Google Patents figures as authoritative per my operating rules, but the exact dates should be confirmed against the USPTO PatentCenter record if precision matters.

Assignment / ownership chain

• 2009‑05‑22 — Assignment of interest recorded to Lemko Corporation (assignor: Pan, ShaoWei).
• 2012‑02‑21 — Motorola Solutions, Inc. recorded a Covenant Not to Sue (assignor: Lemko Corporation). Note: this is a covenant, not an ownership transfer.
• 2025‑03‑25 — Piccadilly Patent Funding LLC, as security holder — patent security agreement (assignor: Lemko Corporation). Again, this is a security interest, not a sale.

Priority / family

The specification states the application is a continuation of Ser. No. 11/105,173, filed April 13, 2005, titled "System, method, and device for providing communications using a distributed mobile architecture" (which issued as US 7,548,763). Google Patents' "Related Parent Applications" table shows a priority date of 2004‑11‑08 for that parent, which conflicts with the claimed April 13, 2005 filing date; this appears to be a data artifact in the Google listing (there is a co‑family patent, US 7,489,667, in the same family). Treat the priority chain with mild caution and verify against the printed patent's (63) continuation data.

Abstract (verbatim substance)

A method includes receiving telephony data from four or more mobile communication devices at a communication apparatus. The apparatus includes a wireless transceiver and a computer readable storage medium. A mobile switching center (MSC) module is embedded in the storage medium, and the MSC module includes an authentication, authorization, and accounting (AAA) module configured to support generation of call detail records at the apparatus. A base station controller (BSC) module and a group call program are also embedded in the storage medium. The method also includes providing, via the group call program, a group call between the four or more mobile communication devices.

Plain‑language overview of the three independent claims

A caveat worth stating plainly: the issued claims are materially narrower than the abstract and summary section. The claims recite HLR and VLR modules embedded in the same computer readable storage medium, and they require that telephony data for the group call traverse a second communication apparatus having its own full embedded module set. The abstract says nothing about HLR/VLR or the second apparatus. Anyone reading only the abstract will over‑estimate claim scope.

Claim 1 — Method (the flagship claim)

1. A DMA "communication apparatus" receives a request to establish a group call among four or more mobile devices.
2. The apparatus must contain, all embedded in its computer readable storage medium: (a) an HLR module, (b) a VLR module, (c) an MSC module that itself includes an AAA module configured to support generation of a first set of call detail records at that apparatus, (d) a BSC module, and (e) a group call program. It also needs a wireless transceiver.
3. The group call program then provides the group call among the four‑or‑more devices.
4. Critically, telephony data for the group call must be communicated to at least one of those devices via a second communication apparatus, and that second apparatus must independently have: a transceiver, storage medium, its own HLR, its own VLR, its own MSC including an AAA module generating a second set of call detail records at the second apparatus, and its own BSC module.

In short: a distributed two‑node cellular core where call‑detail‑record generation is locally distributed rather than centralized.

Claim 8 — Communication apparatus (same invention, device framing)
The apparatus itself: wireless transceiver; storage medium embedding an HLR module, a VLR module, an MSC module with an AAA module configured to support CDR generation at the apparatus, a BSC module, and a group call program. The group call program provides a group call among four or more mobile devices in response to receiving a request to establish the group call, and the telephony data path runs through the identically‑equipped second apparatus described above.

Claim 13 — Communication system (two‑node framing)
A first apparatus and a second apparatus, where each independently comprises: a transceiver; a storage medium with embedded HLR module, VLR module, MSC module (with AAA module supporting generation of its own set of call detail records at that apparatus), BSC module, and a group call program. The first provides a first group call among a first set of four‑or‑more devices; the second provides a second group call among a second set of four‑or‑more devices.

Dependent claims (for context, not independent scope):

• 2–6 (method): full‑duplex calling among all four‑or‑more devices; allowing a first set of participants to disconnect without affecting the remaining set; maintaining full duplex among those remaining; adding an additional device and giving it full duplex with the remaining set.
• 7 (method): receiving telephony data from a plurality of additional devices and connecting them to the group call.
• 9–11 (apparatus): mirror claims 2–4 (full duplex; drop‑out tolerance; full duplex for remaining participants).
• 12 (apparatus): "wherein the wireless transceiver includes at least one base transceiver station (BTS)."
• 14–18 (system): IP packet data over a peer‑to‑peer IP connection; portability of the first apparatus; and transmitting IP packet data over a peer‑to‑peer IP connection while the apparatus is in motion (claims 16–18), including when both apparatuses are in motion.

Litigation / PTAB posture (as of the current date)

• Lemko Corp. v. AT&T — Google Patents links a US case in the Texas Eastern District Court, No. 2:25‑cv‑00305. A PTAB petition document filed in a related Lemko IPR includes a complaint excerpt dated March 17, 2025 in which AT&T is alleged to directly infringe at least exemplary Claim 8 of the '230 Patent under 35 U.S.C. § 271(a). The '230 patent is identified in that document as one of the "Asserted Patents" alongside the '066, '322, '990, '667, '029, and '020 patents.
• PTAB: The 2025–2026 Lemko IPR activity I located (IPR2025‑01142) targets the '990 patent, not the '230 patent. I found no instituted IPR naming the '230 patent.
• CAFC 2026: As noted, the April 10, 2026 Rule 36 judgment (No. 2024‑2336) concerns U.S. 7,855,988 via IPR2023‑00531 — not the '230 patent.

Explicit uncertainty: The litigation details above are drawn from Google Patents' litigation links and from a third‑party PTAB petition exhibit, not from a direct USPTO or court docket query. I cannot confirm the current status of EDTX 2:25‑cv‑00305 (e.g., whether claims were narrowed, stayed, transferred, or dismissed), nor whether the '230 patent remains asserted in that action as of today. I also cannot rule out an unreported or recently docketed CAFC appeal involving the '230 patent; based on the sources available to me, none exists.

Key prior art cited on the face of the patent

Representative references include US 5,623,495 (Eng et al., portable base station architecture for an ad‑hoc ATM LAN), US 6,411,825 (Samsung, distributed BTS architecture), US 6,539,237 / 6,807,431 (Cisco, integrated wireless communications in private and public network environments), US 6,801,432 / 2002/0045444 (Inmarsat, mobile cellular radio), US 6,760,227? — caution: the cited list includes US 6,763,226 (Computer Science Central, multifunctional world wide walkie talkie), and US 2003/0153343 (Qualcomm, communication device for initiating a group call in a group communication network). Note also US 2006/0046760 (Qualcomm, optimistic talk‑permit reliability in a push‑to‑talk system) and US 2006/0063544 (RIM). The group‑call claim element interacts most directly with the Qualcomm group‑call and push‑to‑talk references.

Practical takeaway

US 7,840,230 is a Lemko DMA‑family continuation that issued in 2010 and expired in April 2025. Its surviving record value is historical and defensive rather than as an enforcement asset. Its independent claims are narrowly built around a two‑apparatus architecture with locally embedded HLR, VLR, MSC+AAA (per‑node CDR generation), BSC, and group‑call programs — a narrower picture than the abstract suggests. If you are assessing it for validity, infringement, or IPR purposes, I would work from the printed claim set and confirm the prosecution history (particularly any HLR/VLR‑related amendments) rather than from the abstract or the summary of the disclosure.

I'll search for litigation involving US patent 7840230 across patent litigation databases.

Let me dig deeper into the specific cases and PTAB proceedings involving this patent.

Litigation Involving U.S. Patent No. 7,840,230

Bottom line: I identified one active patent-infringement lawsuit that specifically asserts U.S. Patent No. 7,840,230 (Lemko v. AT&T), plus a related ownership/contract dispute (Motorola v. Lemko) that appears to encompass the patent, and a family of PTAB validity proceedings against sibling Lemko patents (none of which appear to target the '230 patent itself).

Verification caveat: My findings below are based on live searches of Unified Patents' portal, Justia, PACERMonitor, Dockets.Justia, CourtListener, the CAFC opinions page, and PTAB filings. I was unable to complete a fully exhaustive multi-source cross-check before reaching my search limit, so treat the details (particularly as to docket-level status and dates) as as-reported rather than verified against primary PACER records.

Case 1 — Lemko Corp. v. AT&T Inc., et al. (CONFIRMED asserting the '230 patent)

Key source URLs:

• PACERMonitor docket: https://www.pacermonitor.com/public/case/57258476/Lemko_Corporation_v_ATT_Inc_et_al
• Justia (Doc. 79, venue order, 03/06/2026): https://law.justia.com/cases/federal/district-courts/texas/txedce/2:2025cv00305/[236690](/patent/236690)/79/
• Complaint analysis (mapping claim 1 of the '230 patent to HLR/VLR/MSC-AAA/BSC/group-call elements): https://ai-lab.exparte.com/case/dct/txed/2:25-cv-00305/doc/analysis/1
• Lemko press release: https://www.lemkocorp.com/lemko-corporation-files-patent-infringement-lawsuit-against-att/

Note on the accused-product theory: The complaint maps the '230 patent's claimed legacy 2G/3G components (HLR module, VLR module, MSC module with AAA, BSC module, group-call program) onto 5G network functions (UDM/UDR, AMF, AUSF, SMF, UPF) and IMS. This is likely to be the central claim-construction battleground.

Litigation financing / ownership note: Per the Google Patents record, on 2025-03-25 the patent was assigned to Piccadilly Patent Funding LLC, as security holder (patent security agreement) — relevant to standing/real-party-in-interest.

Case 2 — Motorola v. Lemko (ownership/contract dispute; likely encompasses the '230 patent)

• Opinion PDF: https://amlawdaily.typepad.com/lemkoopinion.pdf
• Relevance to '230: The '230 patent's parent application (Ser. No. 11/105,173) was filed 04/13/2005 and the continuation (12/471,253) was filed in 2009 — squarely within the 2004–2009 window of the patents Motorola claimed. I could not confirm from the available excerpt that the '230 patent was specifically named among the eight patents at issue; treat this as likely-but-unverified.
• Also relevant: the Google Patents assignment history shows a 2012-02-21 transfer of a "COVENANT NOT TO SUE" to Motorola Solutions, Inc. from Lemko, which is consistent with a resolution of this dispute.

PTAB proceedings (adversarial, but not district-court litigation)

I found no IPR/PGR that specifically challenges U.S. 7,840,230. The identified PTAB proceedings target sibling Lemko patents, and are relevant context because they arise from the same litigation campaigns:

CAFC appeal (sibling patent, not the '230): Lemko Corp. v. Microsoft Corp., Affirmed Networks, Inc., No. 2024-2336 (Fed. Cir.), appeal from IPR2023-00531 ('988 patent). Rule 36 summary affirmance entered April 10, 2026.

• https://www.cafc.uscourts.gov/opinions-orders/24-2336.RULE_36_JUDGMENT.4-10-2026_2674403.pdf

Case 3 — Lemko Corp. v. Microsoft Corp. (N.D. Tex., 2022) — does NOT assert the '230 patent

Important: The '230 patent is not in the eight-patent Microsoft set (source: Mondaq). The Lemko patent families in the two campaigns "intersect," but the asserted patents do not overlap. So the '230 patent has been asserted only against AT&T, not Microsoft.

Unverified / flagged item

A search result surfaced a case captioned Lemko Corp. v. Microsoft Corp., No. 3:26-cv-01876 (N.D. Tex.), listed with a filing date of 06/05/26. I could not verify this docket, the date appears to post-date the current date of record (April 26, 2026), and there is no indication it asserts the '230 patent. I am flagging it as an unconfirmed possible further filing rather than reporting it as established litigation.

Summary table — litigation touching U.S. 7,840,230

Family-litigation flag (independent corroboration): The Google Patents page for US 7,840,230 carries a Darts-IP "First worldwide family litigation filed" link for Family ID 37109184 (https://patents.darts-ip.com/?family=37109184), confirming at least one litigation has been filed against this patent family. The Unified Patents litigation link points to the same Texas Eastern District Court case, 2:25-cv-00305.

What I could not confirm

• Whether Motorola's ownership suit specifically enumerated the '230 patent.
• The full current docket state of 2:25-cv-00305 beyond the 03/2026 venue order (e.g., claim construction, trial date).
• Any ITC Section 337 action, foreign litigation, or additional district-court suits involving the '230 patent. If you need certainty on those, a direct PACER pull and an ITC EDIS search would be the next step.

Proceedings overview

Total AIA trial proceedings on US 7,840,230: 0. The structured "PTAB proceedings on file" block (USPTO ODP) returns no IPR, PGR, or CBM proceeding against this patent, and my web review surfaced no petition, institution decision, or FWD naming 7,840,230 as the challenged patent. Because there are zero proceedings, there is nothing on this list to classify as active / invalidated / sustained / settled / denied. The bottom line for a defendant: all 18 claims of 7,840,230 stand exactly as issued on 2010-11-23, and no IPR estoppel has been generated against anyone. But two caveats dominate any defensive assessment: (1) the patent expired on 2025-04-13 (Google Patents legal status: "Anticipated expiration," "Expired - Lifetime"), so only back damages for pre-expiration conduct are in play; and (2) Microsoft/Affirmed's PTAB campaign against the sibling Lemko patents — which produced an institution denial on the closest sibling ('763) and a claim-cancelling FWD on a later-priority sibling ('988) — tells you both where the art is and why that art may not transfer to '230.

Proceedings on US 7,840,230

None.

No IPR, PGR, or CBM petition has been filed against US 7,840,230 as of 2026-09-29. Note the structural constraints that make future AIA challenges unlikely:

• PGR is time-barred. The patent granted 2010-11-23; the 9-month PGR window under 35 U.S.C. § 321(c) closed in 2011.
• CBM is unavailable. The AIA transitional CBM program sunset on 2020-09-16.
• Only IPR remains, and the patent is expired, so the realistic remedy is a confirmatory invalidity judgment relevant to past damages, not to prospective injunctive relief.
• § 315(b) one-year clock is running for the current defendants. The patent is linked in the ODP record to a Texas Eastern District Court action, Lemko Corp. v. AT&T Inc., No. 2:25-cv-00305-JRG (complaint filed 2025-03-17). I could not confirm from the sources reviewed whether '230 is one of the asserted patents in that case — treat that as an open item to verify against Dkt. No. 1. If '230 was served in that case in mid-2025, the § 315(b) bar date has already passed for AT&T and its privies.

Family-adjacent PTAB activity (NOT proceedings on 7,840,230)

These are included as intelligence only. None of these proceedings challenged 7,840,230, none of them cancel or narrow any claim of 7,840,230, and no estoppel from them attaches to '230. They are listed in descending order of relevance to the group-call subject matter of '230.

IPR2023-00530 — Microsoft Corporation v. Lemko Corporation (U.S. Patent No. 7,548,763)

• Type: Inter Partes Review
• Filed: 2023-02-14 (Petition, Paper 3)
• Status: Institution denied — Decision Denying Institution of Inter Partes Review, Paper 8 (P.T.A.B. 2023-09-25). The denial was not appealed (Lemko's brief in the '988 appeal and its '990 request for discretionary denial both note Microsoft filed no rehearing or Director Review request in -00530).
• Judge panel: Not confirmed from the sources reviewed.
• Petition grounds: § 103 over Waylett (InterWave "network in a box") in view of Cope.
• Institution decision: Denied. The Board found that "Waylett does not necessarily teach a computer readable medium" because "like traditional networks systems, [Waylett's] functions are implemented in hardware." That finding — that hardware-based network appliances do not read on the claimed "computer readable storage medium" limitation — is the single most important takeaway for anyone challenging '230.
• Final Written Decision: None (no institution).
• Appeal: None.
• Why it matters for '230: '763 is the closest sibling to '230 — both claim priority to application 11/105,173 (filed 2005-04-13), and Lemko itself describes '763 as covering "group communications between participants… DMA servers… duplex communications capabilities." '230 claims 1 and 8 recite the same "computer readable storage medium / MSC module / BSC module / group call program" architecture. Lemko has since weaponized the -00530 denial under Advanced Bionics to argue that the same ground cannot be re-run: "the Board already considered and rejected Microsoft's argument that hardware-based network appliances can satisfy the computer-readable-media limitation."

IPR2023-00531 — Microsoft Corporation and Affirmed Networks, Inc. v. Lemko Corporation (U.S. Patent No. 7,855,988)

• Type: Inter Partes Review
• Filed: 2023-02-14 (parallel to -00529 and -00530)
• Status: Final Written Decision — claims cancelled; appealed; affirmed. Terminated at the Board 2024-09-10; DocketAlarm status "Final Written Decision - Appealed."
• Judge panel: Brian D. Range, Frances L. Ippolito, Scott Raevsky (with a panel change order entered 2024-06-17; Hubert Lorin and Neil Powell also appear on the docket). Oral hearing held 2024-07-11, 90 minutes per side across -00529 and -00531.
• Petition grounds: Claims 1, 3-9, and 20 unpatentable under pre-AIA 35 U.S.C. § 102 as anticipated by U.S. Patent Application Publication 2007/0021120 A1 (Flore). 3GPP TS 23.002 v7.1.0 (March 2006) submitted as supporting evidence of GGSN "location register" functionality.
• Institution decision: Instituted (Microsoft also litigated and lost a Director Review request on institution — Board Order Denying Director Review of Institution Decision, 2023-11-17).
• Final Written Decision (2024-09-10, Paper 31): The Board held claims 1, 3-9, and 20 anticipated by Flore. Petitioner's core mapping: Flore's Inter-Access System Anchor = "first DMA gateway"; SGSN = "second DMA gateway"; the Gn interface = the "DMA gateway communications network"; the PDP context = the claimed "communications information"; the Inter-AS Anchor's GGSN emulation = the recited "home location register." The Board declined to construe "distributed" or to narrow "communications information" to require identification of a network, which is precisely what Lemko appealed.
• Settlement / termination: None — case tried to a merits decision.
• Appeal: Yes. Lemko Corp. v. Microsoft Corp., No. 2024-2336 (Fed. Cir.). Notice of appeal 2024-09-16; Lemko's opening brief 2025-01-29; issues on appeal: (1) whether the Board misconstrued "communications information" by reading out express limitations, and (2) whether the Board erred by failing to construe "distributed." Disposition: AFFIRMED by per curiam Rule 36 judgment, 2026-04-10 (Hughes, Stoll, JJ., and Seeborg, C.J.D., sitting by designation). Nonprecedential.
  • Opinion: https://www.cafc.uscourts.gov/opinions-orders/24-2336.RULE_36_JUDGMENT.4-10-2026_2674403.pdf
• Why it matters for '230: The Flore-based anticipation theory that killed '988 is a priority-dated theory. '988 and '990 carry post-2008 effective filing dates; '230 claims priority to 2005-04-13 (and the family record shows a possible earlier benefit date of 2004-11-08). A 2007-published Flore reference is therefore unlikely to be § 102(a)/(e) art against '230. I flag Flore's actual U.S. filing date as unverified in the sources reviewed — confirm it before relying on this point.

IPR2023-00529 — Microsoft Corporation and Affirmed Networks, Inc. v. Lemko Corporation (U.S. Patent No. 7,653,414)

• Type: Inter Partes Review
• Filed: 2023-02-14
• Status: Instituted; oral hearing held jointly with -00531 on 2024-07-11; final outcome not confirmed in the sources reviewed — I will not state a claim-level result I cannot source.
• Judge panel: Range, Ippolito, Raevsky (same panel as -00531).
• Petition grounds: § 103 over Waylett in view of Mauer. The '414 patent is directed to an AAA module with a destination preference register.
• Relevance to '230: The '414 petition targeted the AAA/CDR aspect of the DMA family — an element '230 recites ("AAA module configured to support generation of a first set of call detail records at the communication apparatus"). If the -00529 FWD issued and addressed the "computer readable storage medium" limitation, that reasoning is directly portable to '230.

IPR2025-01142 — Microsoft Corporation and AT&T Services, Inc. v. Lemko Corporation (U.S. Patent No. 8,310,990)

• Type: Inter Partes Review
• Filed: 2025-06-20
• Status: Pending (petition filed; institution not confirmed in the sources reviewed).
• Judge panel: Not yet assigned in the sources reviewed.
• Petition grounds: Claims 1, 3-9 anticipated under § 102 by Flore; Petitioner expressly leans on the '988 FWD as stare decisis-flavored support.
• Key procedural event: Lemko filed a Request for Discretionary Denial under Advanced Bionics, arguing that (a) Factor 5 favors denial because the parties (Lemko, AT&T) are the same as in the E.D. Tex. action, and (b) Factor 6 favors denial because the Board already rejected Microsoft's hardware-vs-software argument in -00530, and Microsoft neither appealed nor sought rehearing of that denial.
• Relevance to '230: This is the template for what a future '230 challenge would look like — and Lemko's playbook is discretionary denial stacked on the -00530 "computer readable medium" finding.

Strategic summary

Claim status on 7,840,230 — CANCELED: none. SUSTAINED: none. UNTESTED: all 18 claims (1-18). This is a critical distinction. The claims have not survived an IPR; they have simply never been through one. Independent claims 1 (method), 8 (apparatus), and 13 (system) each require the same core architecture — a wireless transceiver, a computer readable storage medium, an embedded HLR module, an embedded VLR module, an embedded MSC module with an AAA module supporting CDR generation, an embedded BSC module, and a group-call program serving four or more devices — with claims 13-18 adding peer-to-peer IP transport between two such communication apparatuses, including when one or both are portable and in motion.

Estoppel landscape — there is none against '230. § 315(e)(2) estoppel binds only a petitioner (and its privies/real parties in interest) in an IPR of that patent. Microsoft, Affirmed, and AT&T have never petitioned on '230, so no estoppel, no § 315(b) bar, and no § 325(e) estoppel attaches to '230 for anyone. Conversely, there is no estoppel protecting '230's owner: any defendant can raise any § 102/§ 103 ground based on patents and printed publications in a fresh IPR (subject to the one-year § 315(b) clock and discretionary-denial risk). Prior-art grounds remain fully open, except that any ground a defendant already raised or reasonably could have raised in a district court invalidity case is subject to the separate § 315(e)(1)/Katz estoppel regime — that is a case-specific analysis.

Pattern signals. Microsoft (with Affirmed Networks, and later with AT&T) is a serial, coordinated petitioner against the Lemko DMA portfolio: at least four IPRs across four different Lemko patents, three of them filed on the same day (2023-02-14) targeting the patents Lemko asserted in Lemko Corp. v. Microsoft Corp. and Affirmed Networks, Inc., No. 3:22-cv-00363-L-BT (N.D. Tex.). The results are mixed: win on '988 (claims 1, 3-9, 20 cancelled, affirmed by the Federal Circuit on 2026-04-10), loss on '763 (denied institution), and an escalation to a fifth petition on '990 filed 2025-06-20 alongside a new AT&T suit. Lemko is an aggressive appellant — it appealed the '988 FWD and pressed two claim-construction issues to the Federal Circuit, losing on a Rule 36 affirmance. There is no defensive aggregator in the chain on '230 itself (no Unified Patents or RPX filing found). What is in the chain: a 2012-02-21 recorded covenant not to sue running to Motorola Solutions, Inc. (assignor: Lemko Corporation) and a 2025-03-25 patent security agreement to Piccadilly Patent Funding LLC, as security holder — the latter indicating the patent is now encumbered collateral for a funding entity, consistent with a monetization posture rather than an operating-company posture.

Recommended next steps

1. Do not assume '230 has been invalidated. Nothing has been cancelled. If a demand letter or complaint cites claims 1-18 of 7,840,230, no PTAB estoppel, no FWD, and no cancellation can be cited back at you. Your defense must be built, not borrowed.
2. Exploit the expiration. The patent expired 2025-04-13. Absent pre-expiration willful infringement findings for conduct before that date, injunctive relief is off the table and the exposure is historic damages plus up to six years of back damages under § 286. Any settlement valuation should be capped accordingly, and any request for ongoing royalties should be resisted as inconsistent with an expired patent.
3. Attack the "computer readable storage medium" limitation as your primary IPR theory. The Board in IPR2023-00530 (2023-09-25, Paper 8) already held that a hardware-based network appliance does not read on that limitation. '230 claims 1 and 8 recite the identical limitation. Build any IPR around hardware-implemented MSC/BSC functionality, and anticipate Lemko's Advanced Bionics discretionary-denial response by showing that your primary reference is materially different from Waylett.
4. Verify the § 315(b) clock immediately. Confirm whether '230 is asserted in Lemko Corp. v. AT&T Inc., No. 2:25-cv-00305-JRG (E.D. Tex.) and the exact service date. If service predates 2025-09-29, the one-year bar has run for that defendant and its privies, and IPR is no longer an option for them absent joinder under § 315(c).
5. Pull the recorded covenant not to sue. Retrieve the 2012-02-21 Motorola Solutions assignment/covenant from the USPTO Assignment database and determine its scope and whether it runs to any current accused product or successor. It is the only recorded instrument that could independently immunize a defendant.
6. Check for a reexamination and confirm the '230-specific docket. The ODP block covers AIA trials only. I did not find an ex parte reexamination against '230, but I did not confirm its absence — a reexam certificate or a pending reexam would be a separate validity event. Similarly, confirm via PTAB E2E (https://ptacts.uspto.gov/) and DocketAlarm (https://www.docketalarm.com/cases/PTAB/) that no post-2026-04 '230 petition is pending before relying on the "zero proceedings" conclusion.
7. Watch IPR2025-01142 if you are an AT&T-affiliated or similarly situated defendant: an institution denial there on Factor 5/Factor 6 grounds would confirm that the Board will not entertain repeated Microsoft-family hardware-based attacks on Lemko's DMA claims — which cuts against a future IPR on '230 — while an institution would confirm the Board is willing to re-run the Flore theory on later-priority family members.

Confidence and gaps. High confidence: zero AIA proceedings on 7,840,230 (ODP structured data, corroborated by web review); the '988 FWD (2024-09-10), the CAFC Rule 36 affirmance in No. 2024-2336 (2026-04-10), and the '763 institution denial (2023-09-25). Lower confidence / unverified: Flore's exact U.S. filing date and therefore its status as prior art against '230's 2005-04-13 priority; the final disposition of IPR2023-00529 ('414); the institution status of IPR2025-01142; and whether '230 is among the patents asserted in the AT&T E.D. Tex. action. I have not stated anything about those that I could not source.

I'll research the assignment chain and cross-reference litigation and NPE signals.

Let me dig into the 2025 litigation, Lemko's current status, and the Piccadilly security interest.

Assignment Chain Analysis — US 7,840,230 B2

Report date: 2026-09-29 | Patent: US 7,840,230 B2 ("Communications using a distributed mobile architecture"), App. 12/471,253, filed 2009-05-22, granted 2010-11-23, priority 2005-04-13, expired 2025-04-13 (anticipated).

Source-access caveat up front: USPTO Patent Assignment Search (Assignment Center / assignment.uspto.gov) was not directly reachable during this session, and Google Patents surfaces the legal events without reel/frame numbers. I can therefore reconstruct the sequence, dates, parties, and conveyance types with high confidence from the Google Patents legal-events record and corroborating secondary sources, but I could not verify any reel/frame number, and I will not invent them. Every reel/frame slot below is marked [not retrieved]. The reader should confirm on the Assignment Center search page (https://assignmentcenter.uspto.gov/) before relying on this for standing/chain-of-title work.

Inventors

• Shaowei Pan (ShaoWei Pan) — sole named inventor (confirmed by the litigation press coverage of Lemko's 2025 AT&T campaign: "Shaowei Pan is identified as the patents' sole named inventor").

Employer at time of filing: Lemko Corporation — Pan was a Lemko co-founder and its CTO (later President; he is still identified as the plaintiff's president in the 2025 complaint). Lemko was formed in Illinois on 2002-08-02.

Unusual pattern — flagged: Pan was a Motorola staff engineer (joined Aug 1994; Director of Advanced Technology & Development by ~2000) and left Motorola in late March 2004, roughly one year before this application was filed (2005-04-13). Motorola sued Lemko and 14 individuals in 2008 (Motorola, Inc. v. Lemko Corp., No. 08-cv-05427, N.D. Ill.), seeking a declaratory judgment that Motorola — not Lemko — owned the Lemko patents, on the theory that Pan's signed employee agreement assigned to Motorola every invention related to Motorola's business. The court denied summary judgment to both sides in January 2012. The parties settled on 2012-01-31. This is a title-cloud/ownership dispute, not a fire-sale pattern, but it is unusual and directly relevant to chain-of-title for this patent family. I found no evidence that Pan departed Lemko; he remains the company's principal.

Original assignee

Lemko Corporation (Lemko Corp), an Illinois corporation (incorporated 2002-08-02). Address of record has moved over time: Schaumburg, IL → Itasca, IL.

• Primary line of business: developer of the "Distributed Mobile Architecture" — carrier-grade MSC/BSC functionality virtualized as software on commodity servers at the network edge. It is a commercial network operator/vendor, not a licensing vehicle: it claims to have launched NFV-based networks in 2004, to have run rural wireless broadband in Cairo, Illinois (from ~2016), and to deploy private 4G/5G, IIoT, military and public-safety networks in Alaska, Northern Canada and Africa. It states it holds 50+ patents, 28 covering Mobile Edge Computing.
• Did it ship a product embodying the claims? Lemko asserts it did — its complaints describe "a leading, fully edge-capable mobile network platform and resilient 4G/5G wireless networks," and its own press release claims the DMA software predates the ETSI NFV white paper (Oct 2012) by seven years. The 2012 Motorola opinion records contemporaneous evidence of CASSE/DMA product demos as early as 2004.
• Current status: Operating, and actively litigating as plaintiff. Not dissolved, not in bankruptcy on any record I located. It is however under financial strain signals: as of 2025-03-25 it pledged its patents as collateral to Piccadilly Patent Funding LLC (see timeline).

Assignment timeline

Chronological. Dates are recording-date-derived from Google Patents legal events; execution dates are noted where the underlying instrument date is known. Reel/frame could not be retrieved for any entry.

• 2009-05-22 (executed) / recorded 2009-05-22 — Reel/Frame [not retrieved]

  • Conveyance: Assignment of Assignors Interest
  • Assignor: ShaoWei Pan (individual inventor)
  • Assignee: LEMKO CORPORATION
  • Correspondent: [not retrieved] — note that the prosecution attorney/agent of record on the sibling Lemko applications of this era is Lemko Corporation c/o Cygan Law Offices, P.C., Hoffman Estates, IL. That is prosecution correspondence, not a confirmed assignment-record correspondent.
  • Context: Inventor-to-company assignment, recorded alongside the 2009-05-22 continuation filing; internal, standard original-owner perfection.

• 2012-02-21 / recorded 2012-02-21 — Reel/Frame [not retrieved]

  • Conveyance: Covenant Not to Sue (Google Patents indexes it as "Assigned to MOTOROLA SOLUTIONS, INC." — but the conveyance type is a covenant, not a transfer of title)
  • Assignor: LEMKO CORPORATION
  • Assignee: MOTOROLA SOLUTIONS, INC.
  • Correspondent: [not retrieved]
  • Context: Settlement of Motorola v. Lemko (settlement announced 2012-01-31; recorded 2012-02-21). Lemko granted Motorola a covenant not to sue. Note the discrepancy: the Mondaq litigation commentary attributes the '988 patent covenant to this settlement, yet the same event appears on the '230 Google Patents record — consistent with a portfolio-wide covenant recorded against multiple Lemko patents. Because it is a covenant, no ownership changed hands.

• 2025-03-25 / recorded 2025-03-25 — Reel/Frame [not retrieved]

  • Conveyance: Patent Security Agreement (security interest / lien — not an assignment of title)
  • Assignor: LEMKO CORPORATION (grantor)
  • Assignee: PICCADILLY PATENT FUNDING LLC, AS SECURITY HOLDER
  • Correspondent: [not retrieved]
  • Context: Securitization — Lemko pledged its patent portfolio as collateral for financing from Piccadilly Patent Funding LLC. Under instruments of this type (see the Quest/QPRC form patent security agreements surfaced in search), the grantee takes a first-priority lien and a power of attorney to record a transfer to itself upon an event of default. No default-driven transfer has been recorded as of this report. This is the only post-2012 recording on the '230.

No other recorded assignments exist for this patent. The chain does not terminate in an IP-holding LLC, and no NPE-typical entity appears anywhere in it.

Litigation overlay (for the pre-litigation-transfer test):

• 2025-03-17 — Lemko Corp. v. AT&T Inc., No. 2:25-cv-00305-JRG (E.D. Tex.), Judge Rodney Gilstrap. Asserted patents: 7,840,230; 7,979,066; 8,224,322; 8,310,990; 8,340,667; 8,359,029; 9,198,020. Unified Patents litigation record: https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A25-cv-00305
• Feb 2022 — earlier campaign: Lemko v. Microsoft / Affirmed Networks (N.D. Tex.), asserting a non-overlapping patent set.
• Related PTAB activity: Microsoft Corp. and AT&T Services, Inc. v. Lemko Corp., IPR2025-01142 (U.S. 8,310,990), and the earlier IPR2023-00530, where institution was denied (Paper 8, Sept. 25, 2023).

Timeline diagram

timeline
    title Ownership of US 7840230
    2002 : Lemko founded in Illinois
    2004 : Inventor Pan leaves Motorola
    2005 : Parent application filed Apr 13
    2009 : Continuation filed
         : Assignment recorded to Lemko Corporation
         : Publication of US 2009 0227235
    2010 : Patent issued Nov 23
    2012 : Covenant not to sue recorded to Motorola
         : Motorola Lemko suit settled Jan 31
    2025 : Patent pledged to Piccadilly Patent Funding
         : Lemko sues ATandT in ED Texas
         : Patent reaches anticipated expiration Apr 13

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The patent has been held continuously by Lemko Corporation, the original operating assignee, since the inventor assignment recorded 2009-05-22. There is no "IP / Holdings / Ventures" transferee, no registered-agent address of record, no single-purpose Delaware/Texas LLC in the chain. The only LLC on the record, Piccadilly Patent Funding LLC (2025-03-25), takes as security holder only — a lien, not title.

2. Known asserter in the chain — not present. Lemko Corporation is not Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, or a Spangenberg entity. Lemko is the original operating company asserting its own patents, which it says cover products it built and fielded. Nuance worth recording: Lemko now behaves like a serial plaintiff (Microsoft 2022, AT&T 2025) whose patents are collateralized, so it is trending toward monetization — but the identity test fails.

3. Repeat correspondent across the chain — unclear. I could not retrieve the correspondent of record for any of the three recordings (Google Patents does not expose it and Assignment Center was unreachable). With only one true assignment plus a covenant and a lien, there is no recurrence to test in any event. Not scored as a finding.

4. Cascading transfers — not present. No chained LLCs; no multiple consecutive assignments. The entire chain is two operating-company events plus one lien, spanning 2009 → 2025.

5. Pre-litigation transfer — not present (inverse present). The only recording near the suit is the 2025-03-25 security agreement — recorded eight days after the 2025-03-17 complaint — and it conveys no title. There is no assignment arranged within six months of suit to set venue or manufacture standing; Lemko asserts as the long-standing owner of record.

6. Bankruptcy fire-sale — not present. No Chapter 7/11 record for Lemko located; the company is an active operating plaintiff and was still filing suit in March 2025.

7. Privateering — not present. No operating company handed this patent to a litigating proxy. The party suing AT&T and Microsoft is the same operating company that has held the patent since 2009.

8. Defensive aggregator — not present. Chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. The patent is un-neutralized and in active assertion.

Verdict

Operating-company assertion — with moderate NPE overtones noted below.

Justification: The chain is short and clean. Lemko Corporation took the invention by assignment recorded 2009-05-22, granted Motorola Solutions only a covenant not to sue recorded 2012-02-21 (no title transfer), and remains the owner of record today, with the sole further recording being a patent security agreement to Piccadilly Patent Funding LLC recorded 2025-03-25 (a lien, not an assignment). The asserting party — Lemko, the original assignee, a going concern that says its own DMA software embodies the claims — filed 2:25-cv-00305 (E.D. Tex., 2025-03-17) against AT&T, and previously against Microsoft/Affirmed Networks, i.e., actual competitors in the edge/mobile-core market. None of the eight NPE signals is present.

Caveats that keep this from being a clean bill of health: (a) the collateral pledge to a patent-funding entity plus repeated litigation against deep-pocketed implementers is a monetization pivot worth monitoring; (b) the '230 reached its anticipated expiration on 2025-04-13, roughly one month after suit, so the AT&T campaign is a damages-only, end-of-life assertion; (c) the 2012 covenant not to sue runs to Motorola Solutions and may complicate assertion against parties practicing through Motorola-derived technology.

Verify at: https://assignmentcenter.uspto.gov/ (search by patent number 7,840,230 to retrieve reel/frame and correspondent for the three entries above) — cross-check against RPX Insight and the Unified Patents litigation portal.

I'll verify the patent and its cited prior art against live sources before building the § 102 analysis.

Let me verify the remaining high-relevance references cited on the face of the '230 patent.

Prior-Art Analysis — US 7,840,230 B2

A note on method and on one inconsistency: The task header gives "Current Date: April 26, 2026," while the previously generated section was produced under a date of 2026‑09‑29. I flag this rather than silently reconcile it; nothing in the substantive analysis below depends on which is correct.

What I searched and what I found. I ran targeted searches against the public mirrors of the USPTO record (Google Patents, which reproduces USPTO front‑page citation data; the Unified Patents portal; and PTAB/PTACTS document repositories). I did not retrieve a native USPTO PatentCenter "References Cited" page for 7,840,230 directly, so the citation list below is sourced from the patent's own face (as supplied in the authoritative full text) and cross‑checked where possible against live search results. I verified the following references individually via live search: US 5,623,495; US 2003/0153343 A1; US 2004/0253949 A1; US 6,539,237 B1 (and its continuation US 6,807,431). The remaining references are reproduced from the face‑of‑patent citation list, and I mark them as "not independently re‑verified" where that is the case. I did not auto‑correct any number.

1. The critical framing point before the reference‑by‑reference mapping

A single cited reference must disclose every element of a claim, arranged as the claim requires, to anticipate under 35 U.S.C. § 102. This is a rule that materially affects the answer here, because the independent claims of the '230 patent (claims 1, 8, 13) are narrow combinations:

• a communication apparatus embedding an HLR module and a VLR module and an MSC module that itself includes an AAA module for generating call detail records at that apparatus and a BSC module and a group‑call program (claim 1 elements b–f); and
• a second communication apparatus with an independent, identically complete embedded module set, over which the group‑call telephony data must pass (claim 1 element i).

My conclusion, stated up front and defensible: none of the 48 cited references, taken alone, discloses all elements of claim 1, 8, or 13. The citation set is overwhelmingly a § 103 obviousness set — it supplies the individual building blocks (distributed base stations, per‑node mobility management, HLR/VLR architecture, group calling, AAA/CDR accounting, peer‑to‑peer IP core) but not the claimed combination. Any mapping that described one of these as a § 102 anticipation of the independent claims would be overstating the reference.

There is also a pre‑AIA point: the '230 patent's effective filing chain runs to 2005‑04‑13 (the parent, Ser. No. 11/105,173), i.e., before the AIA's 2013‑03‑16 changeover. So pre‑AIA § 102(a)/(b)/(e) applies, with a critical date of 2005‑04‑13 (or 2004‑11‑08 if the Google "Related Parent Applications" artifact noted in the prior section is correct). All references below predate that date either by publication or by filing (for § 102(e) purposes).

2. Reference table — full citations, dates, descriptions

2a. The references I verified live

2b. References from the face of the patent (not independently re‑verified)

Distributed / embedded base‑station and core‑network architecture

Wireless‑over‑IP / private‑public interworking

Group call / push‑to‑talk / multiparty

Accounting / AAA / billing

Satellite / mobile‑platform cellular

Miscellaneous (data‑connection / network‑maintenance)

Note on two entries I am deliberately not treating as prior art. The citation block also surfaces US 2006/0234747 A1 and US 2006/0234774 A1, both Lemko Corporation, priority 2005‑04‑13 — these are the applicant's own sibling DMA applications published 2006‑10‑19, not third‑party prior art. I flag them because they appear in the same listing and could be mistaken for § 102 references. Likewise the family members US 7,489,667 and US 7,548,763 are the same family, not prior art.

3. Claim‑by‑claim § 102 mapping (the references that get closest)

For each reference I give the strongest claim it could plausibly be argued against, and then state plainly what it lacks.

US 2003/0153343 A1 (Crockett — Qualcomm). Closest to claim element (g)/(h) "receiving a request to establish a group call … providing the group call between four or more mobile communication devices." It expressly discloses group calls among many participants via a member list and a server. What it lacks: the apparatus of claim 1 is a distributed node embedding HLR + VLR + MSC(+AAA generating CDRs locally) + BSC; Qualcomm's architecture routes through a central dispatch application server / MCU, and its disclosure says nothing about an embedded HLR, VLR, BSC, or per‑node call‑detail‑record generation. § 102 result: does not anticipate claims 1, 8, or 13. Strong § 103 material for the group‑call element (2–7). A companion Qualcomm filing, US 2006/0046760 A1 (Bertino, filed 2004‑08‑24, published 2006‑03‑02), is § 102(e) prior art as of its filing date and is similarly relevant only to the group/PTT element.

US 5,623,495 (Eng — Lucent). Closest to claim element (a) + claim 12's "wireless transceiver" and to the § 102 potential for claims 14–18's peer‑to‑peer, in‑motion topology: it discloses per‑node wireless interfaces, distributed control, and a reconfigurable peer backbone among portable nodes. What it lacks: any cellular core — no HLR, VLR, MSC, AAA, CDR generation, or group call program; transport is ATM, not the claimed CDR‑generating MSC apparatus. § 102 result: does not anticipate. Listed here because it is the reference an examiner would most naturally cite for the "portable, peer‑connected node while in motion" idea (claims 15–18).

US 2004/0253949 A1 (Boeing). This is the sharpest single piece of art on the HLR + VLR + MSC + BSC combination (claim 1 elements b–e): it expressly puts an HLR and a per‑platform VLR into the MSC (its claim 8) and a BSC‑type function (ABSC) onto the moving platform (its claim 9), with the platform also carrying user equipment and wireless links. What it lacks: the VLR is defined within the ground MSC, not embedded in the platform's computer readable storage medium; there is no AAA module, no call‑detail‑record generation at the node, and no group call program. § 102 result: does not anticipate claims 1, 8, or 13. It is, however, the most dangerous § 103 reference against the HLR/VLR‑embedded limitation — which matters, because the prior section correctly observes that HLR/VLR were likely added by amendment, making them vulnerable to exactly this kind of reference.

US 6,539,237 B1 (Cisco) / US 6,807,431 B2 (Cisco). The closest art on "MSC‑type and BSC‑type intelligence pushed down into the node." The '431 continuation's claim 1 puts "a processing layer for mobility management and a call control processing layer" contained within the private base transceiver stations, interconnected by a packet data network, with gatekeeper/IWU handling MAP/HLR/VLR interworking. What it lacks: no AAA module generating CDRs at the node, no group‑call program, and the HLR/VLR remain GSM core‑network entities rather than embedded modules of the apparatus. § 102 result: does not anticipate claims 1, 8, or 13. Best § 103 material for the "embedded MSC/BSC in a packet‑interconnected node" concept.

US 7,072,650 (MeshNetworks). Directly relevant to claims 14–18 (peer‑to‑peer IP connection, mobile nodes) — an ad hoc peer‑to‑peer mobile radio access system interfaced to the PSTN and cellular networks. Does not touch the embedded HLR/VLR/MSC‑AAA/BSC apparatus.

US 7,328,268 B1 (Cisco). Relevant only to the AAA element (claim 1 element d: "AAA module … configured to support generation of call detail records at the communication apparatus"). It discloses a common AAA session ID across a network — accounting/AAA in a network, but not AAA as a module embedded in a portable cellular node. Not an anticipation; useful § 103 support for the AAA/CDR element.

US 6,763,226 B1 (Computer Science Central). Multiparty/group communication across cellular‑satellite‑VoIP — relevant to the group‑call element only.

Bottom line of the mapping

4. What I could not verify / caveats

1. I did not obtain a direct USPTO PatentCenter "References Cited" page for 7,840,230. My citation list is from the patent's face (authoritative per the supplied text) plus live cross‑checks. If you need the prosecution‑history citations (i.e., what the examiner actually applied during the 2009–2010 pendency), that requires the file wrapper, which I could not retrieve.
2. Count mismatch to flag: the Unified Patents portal lists "Patent Art (50)" and "Non‑Patent Literature (7)" for this patent, whereas the Google Patents face lists 48 cited references. Seven non‑patent references exist that I have not identified; those NPL items could matter more than several of the patent references and should be pulled from the file wrapper before any validity opinion. I do not know what they are.
3. One apparent reference anomaly in the face list: the supplied text renders a few entries with what look like duplicated or transposed digits (e.g., "US 6,811,652" vs. "US 6,813,652" for the Nortel control‑message patent; "US 6,879,677" appearing twice; "US 6,917,813" vs. the SMS patent). Per my operating rules I have not auto‑corrected these; treat the exact numbers as requiring confirmation against the printed patent.
4. The 2004‑11‑08 vs. 2005‑04‑13 priority artifact flagged in the prior section remains unresolved and directly affects the § 102 critical date; if 2004‑11‑08 governs, US 2006/0046760 (Bertino, filed 2004‑08‑24) and the Qualcomm group‑call family still qualify, but the margin narrows.

Net practical conclusion: for § 102 purposes the '230 citation set yields no clean anticipation of claims 1, 8, or 13; its real force is as a § 103 combination — Boeing '949 (HLR/VLR/MSC/BSC on a moving platform) + Cisco '237/'431 (mobility/call‑control layers inside packet‑interconnected base stations) + Crockett '343 or Bertino '760 (group call) + Cisco '328,268 (AAA/CDR), against the thin, largely conventional HLR/VLR limitation that the prior analysis already identified as the claim's likely point of vulnerability.

I'll ground the obviousness analysis in the actual reference disclosures before constructing combinations.

Let me verify the two references most central to the "integrated MSC+BSC in one node" and "portable/mobile switch" limitations.

Obviousness Analysis — US 7,840,230 under 35 U.S.C. § 103

Prepared: 2026-04-26 (task date). Note on dates: my session environment reports 2026-09-29; the task header says 2026-04-26. Flagging rather than silently resolving. Flag also: this analysis is built on the prior-art citations listed on the face of the '230 patent plus the family-citation list, which is what "the Prior Art section of this page" supplies. Two references central to the strongest combination (US 6,539,237 and US 2006/0046760) could not be full-text-verified before I exhausted my search budget; those characterizations are marked [UNVERIFIED — title/listing only] and should be confirmed against the printed documents before being relied on.

1. Legal frame

The '230 patent is pre-AIA (application Ser. No. 11/105,253 filed 2009‑05‑22, claiming continuation priority to Ser. No. 11/105,173 filed 2005‑04‑13). The controlling test is therefore pre-AIA § 103(a) as construed by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), and MPEP § 2143. Two consequences matter:

1. The 2005‑04‑13 priority date governs the prior-art window, not the 2009 filing date, provided the claims are supported by the '173 disclosure. Google Patents' family table shows a 2004‑11‑08 date for the parent — my earlier section flagged this as a probable data artifact. If 2004‑11‑08 were correct, some art in the window would shift § 102 category (not availability), so this is low-risk for the analysis below.
2. Every reference relied on below pre-dates the priority date. US 2004/0253949 (published 2004‑12‑16, filed 2004‑07‑09) is not § 102(b) art against a 2005‑04‑13 date, but it is available as § 102(e)/§ 102(a) art. US 2003/0153343 (published 2003‑08‑14) is § 102(b). US 5,623,495, US 6,411,825, US 6,539,237, US 7,072,650's parent publication US 2002/0058504 are all § 102(b)/§ 102(e).

The claims were allowed in 2010 and the patent expired 2025‑04‑13. This is a defensive/historical validity question, not an enforcement one — but the § 103 analysis is unaffected by expiry.

2. PHOSITA and the level of ordinary skill

A POSITA here is a cellular network engineer with a B.S. in EE/CS and 3–5 years in wireless core-network design (BSC/MSC, IS‑41/GSM MAP, CDMA/GSM air interfaces), capable of specifying software modules on a general-purpose computer platform. That skill level is important: the '230 claims are software-module-architecture claims ("module embedded in the computer readable storage medium"), and KSR permits combining references plus the knowledge of a POSITA, including the knowledge that HLR/VLR/AAA/MSC/BSC are conventional, decomposable logical functions — a point the prior art itself makes expressly (US 7,072,650: "modern cellular systems are decomposed into logical functional units, with well-defined interfaces between them").

3. Element chart — where each limitation is met

3.1 Claim 1 (method) / claim 8 (apparatus) / claim 13 (system) — shared elements

3.2 Dependents

4. Grounds of rejection

Ground A — Claims 13–18 (the strongest ground)

Combination: Cisco US 6,539,237 (or, alternatively, Samsung US 6,831,903) in view of Crockett US 2003/0153343, further in view of MeshNetworks US 7,072,650, and optionally Boeing US 2004/0253949.

Why each is met: '237/'903 supply the integrated private-network switching node with an on-board control function and a wireless interface; Boeing '949 supplies HLR + VLR co-resident with the MSC in the same node (US 7,359,700 cl. 7) and duplicated equipment sets across plural platforms; Crockett supplies the group-call program and the 4+‑party group call; MeshNetworks supplies the peer-to-peer IP transport between distributed nodes and the express teaching that nodes are replicable, self-routing, and may each act as a base station.

Motivation (KSR factors 1–4 and MPEP 2143.A–D):

• Same field, same problem: both '237/'903 and Crockett address serving wireless subscribers from a locally-controlled switching node; both are in H04M/H04W.
• Known design incentive: removing the central-office backhaul is the stated economic driver of '237, '903, '495 and '650 alike ("significantly less infrastructure is required … much lower building and operating costs").
• Predictable result: bolting a known group-call application onto a known integrated switching node is precisely the "combination of familiar elements according to known methods … predictable results" that KSR holds obvious.
• Market/technical trend: PTT and dispatch (Crockett/Bertino) were migrating from specialized networks onto standard packet/cellular infrastructure; the cited art itself frames cellular functions as "logical units with well-defined interfaces," which is an express invitation to re-partition MSC/BSC/HLR/VLR/AAA.

Claim 14 / 16–18 specifically: US 7,072,650's peer-to-peer IP routing plus US 5,623,495's "portable base station" and US 2004/0253949's airborne, in-motion platform with wireless feeder links make "IP packet data … via a peer-to-peer IP connection when … in motion" a straightforward combination; motion is an expressly contemplated deployment condition in both '495 and '949.

Ground B — Claims 1–8 (same combination, plus the "second apparatus" bridge)

Add to Ground A: US 2004/0253949 for the second apparatus (plural platforms, each with a full on-board BSC equipment set, sharing a core that holds the HLR/VLR) and US 6,831,903 for the motivation to route through a second apparatus (public-network service when the private call-management device is in a down state — i.e., redundancy/failover). The '230 specification itself states this motivation ("self-healing and redundant … if one or more of the DMA servers loses power, fails, or is otherwise inoperable, telephony traffic … can be re-routed").

For the AAA/CDR limitation, add US H1918, US 20040019539, US 6,829,473 and US 7,328,268 — local authentication plus per-node billing-record generation is well-trodden.

For claims 2–7, 9–11, add US 6,781,963 and US 6,873,854 (drop-out tolerance; addition to an active group call), and conference-call art (US 6,839,356; US 7,050,414) for full duplex.

Ground C — Alternative primary reference

US 20040014466 A1 (Radioframe Networks, "Radio system having distributed real-time processing") or US 20010055298 A1 (Baker, "wireless access integrated node") in view of Crockett '343 and MeshNetworks '650. These substitute for '237/'903 on the "integrated node with distributed processing" element. [UNVERIFIED — title/listing only; confirm disclosure before asserting.]

Ground D — Reference-quality caveat

I do not see a viable single-reference § 102 anticipation of claim 1, 8 or 13. The "second communication apparatus with a full duplicate embedded module set, including its own AAA/CDR generation" is not disclosed in any one cited reference I verified. This is a § 103 case that must be built on KSR-style combinations and articulated motivations, not on anticipation.

5. The vulnerabilities in the obviousness case (state them plainly)

1. The "second apparatus" element (claim 1 ¶4, claim 8 ¶4, claims 13–18) is the crux and the weak point. Boeing '949 puts the VLR at the ground MSC, not necessarily at each platform; MeshNetworks '650 is a node-to-node mesh, not two co-equal MSC-bearing cores; Samsung '903 discloses a fallback mode, not two simultaneously served duplicate cores. A patentee would argue that routing group-call telephony data through a second apparatus that independently generates its own set of call detail records is a specific, non-trivial architectural choice (distributed billing/CDR ownership) not suggested by billing art that centralizes CDRs.
2. Half-duplex vs. full duplex. Crockett's system is PTT/dispatch, which is conventionally half-duplex with talk permits. Claim 2/9 (and claims 2–6, 9–11 downstream) require full duplex. The combination must therefore also pull in conference-bridging art, and the patentee will argue PTT art teaches away from full-duplex group calling.
3. "Embedded in the computer readable storage medium." This is a claim-drafting convention, not a technical distinction; it should be given little patentable weight, but expect the patentee to argue it denotes integration rather than mere co-location.
4. Secondary considerations. None are of record here (no evidence of unexpected results, licensing nexus, or long-felt need tied to the claims as issued; the Motorola Solutions entry is a covenant not to sue, and the Piccadilly entry is a security interest — neither is evidence of commercial success or copying). The expired status also forecloses injunctive-relief evidence. I have no evidence either way on nexus, so I would not assert that secondary considerations are absent — only that I found none.

6. Bottom line

The claims are narrower than the abstract and summary (as my earlier section noted): the abstract says nothing about HLR/VLR modules or a second apparatus, yet both are mandatory in every independent claim. Any invalidity position must therefore be argued against the issued claim text — and the "second apparatus" limitation is where the case will be won or lost.

Not a legal opinion or a freedom-to-operate/validity opinion. Reference characterizations marked [UNVERIFIED] rest on titles and citation listings only and must be checked against the full documents. Litigation/IPR status of the '230 patent was not re-verified for this task and remains as stated in my earlier section.