US 7548763

The initial searches returned no results. Let me refine with different query formulations.

Summary of U.S. Patent No. 7,548,763 (US7548763B2)

Based on the authoritative Google Patents record (fetched 2026-09-01, supplied in full with your query) and the corroborating USPTO/PTAB search results, here is the summary. Note: the CAFC 2026 docket searches I ran returned no results specific to this patent number, so I cannot confirm or describe any CAFC 2026 proceeding from authoritative sources; the litigation data below comes from the Google Patents record.

Bibliographic data

• Patent number: US 7,548,763 B2 (application no. 11/105,173)
• Title: "System, method, and device for providing communications using a distributed mobile architecture"
• Inventor: ShaoWei Pan (also rendered Shao-Wei Pan / Shaowei Pan; USPTO records corrected the assignor name to "SHAOWEI PAN" in a 2009 re-record)
• Assignee: Lemko Corporation (later records show Lemko Corporation, Itasca, IL; the patent is currently held under a 2025-03-25 patent security agreement to Piccadilly Patent Funding LLC, and a 2012 covenant not to sue was granted to Motorola Solutions, Inc.)
• Filing date: April 13, 2005
• Issue date: June 16, 2009
• Status: Active; adjusted expiration listed as 2026-12-29 (Google Patents legal-status notation)

Abstract (verbatim from record)

"A method of providing telephone communication is disclosed and includes allowing a group call between four or more participants. Each participant calls from a separate telephone device that communicates with a base transceiver station that is coupled to a distributed mobile architecture server. The method also includes providing full duplex calling capability between all participants via one or more of the distributed mobile architecture servers. One or more participants can disconnect from the group call without effecting other participants remaining on the group call. Further, one or more added participants can connect to the group call."

Claim structure

The patent has 18 claims. Only claim 1 is an independent claim; claims 2–18 are all dependent on claim 1.

Plain-language overview of the independent claim (claim 1)

Claim 1 is a system claim covering two interconnected "distributed mobile architecture" (DMA) servers:

• First DMA server, comprising: a computer-readable medium; an embedded mobile switching center (MSC) module; an embedded base station controller (BSC) module; and an embedded call detail record (CDR) generation program. The first server is in direct physical connection with a first wireless transceiver (e.g., a BTS/antenna).
• Second DMA server, similarly comprising: its own computer-readable medium, embedded MSC module, embedded BSC module, and embedded CDR generation program — plus a program (embedded in its medium) to allow a group call among four or more mobile communication devices. The second server is in direct physical connection with a second wireless transceiver.
• Interconnection: Telephony traffic received at the first wireless transceiver is transmitted from the first DMA server to the second DMA server via a peer-to-peer connection.

In plain terms: the claim protects a distributed cellular system made of self-contained, software-based "server" units (each combining MSC + BSC + billing/CDR functions and directly wired to its own base-station radio) that link to each other peer-to-peer, where at least one of the units is programmed to support a 4+ party full-duplex group call.

Dependent-claim highlights (claims 2–18)

• Claims 2–3: peer-to-peer traffic transmission while one or both DMA servers are moving (mobile/deployable servers).
• Claims 4–7: each server further includes home location register (HLR) and visitor location register (VLR) modules (claims 4, 6), and OAMP, AAA, PDSN gateway, and GGSN modules (claims 5, 7).
• Claim 8: first server in a city area, second server in an urban fringe area (rural-coverage extension scenario).
• Claims 9–14: first server holds subscriber administrative information; and further gateways — PSTN gateway (claim 10), media gateway (claim 11), Internet phone gateway (claim 12), SS7 gateway (claim 13), SIP gateway (claim 14).
• Claims 15–18: the first server's BSC module comprises a cellular radio network controller (claim 15), a cellular selection/distribution unit (claim 16), and a call protocol controller (claim 17) that communicates with the first wireless transceiver (claim 18).

Litigation / PTAB context (from the Google Patents record)

• IPR2023-00530 filed against this patent — noted as "Not Instituted – Merits" (petitioner: Unified Patents; per docketalarm/PTAB-linked records).
• District court case in the Texas Northern District Court, case 3:22-cv-00363.
• Related Lemko patents in the same family include US 7,486,967, US 7,539,158, US 7,653,414, US 7,855,988, US 8,224,322, and US 8,310,990 (which the search results confirm is a continuation-family patent also involved in PTAB IPR2023-00529/00531 proceedings, including a Federal Circuit appeal, Lemko Corp. v. Microsoft et al., No. 24-2336).
• Continuation child: US 7,840,230 (application 12/471,253, filed 2009-05-22).

Uncertainty notes

• I could not verify any CAFC 2026 docket entry for this specific patent number via web search (the queries returned no results). Do not assume a pending CAFC case exists based on my search.
• The Google Patents "priority date" field shows 2005-04-13 for the US application, while the family's PCT (WO2006052342) and related foreign filings list a priority date of 2004-11-08; the relationship between those dates is not fully clarified by the record shown, so treat the 2004-11-08 date as a family priority reference rather than this application's filing date.

Based on the search results and the Google Patents record for US 7,548,763 (which you provided), the following litigation is identifiable. I'm flagging where the available snippets did not let me fully confirm party names or status.

Known proceedings involving US Patent 7,548,763

1. PTAB inter partes review — IPR2023-00530

• Patent at issue: US 7,548,763 (challenged claims 1, 4, 6, 9, and 15 per the PTAB record)
• Patent owner: Lemko Corporation
• Petitioner: The PTAB docket is part of the same Lemko IPR campaign as IPR2023-00529 (Microsoft Corporation and Affirmed Networks, Inc. v. Lemko Corp., U.S. Patent 7,653,414), and IPR2023-00530 is the companion proceeding directed to the '763 patent. The retrieved snippets do not expressly reproduce the IPR2023-00530 caption/petitioner name, so I cannot state with 100% confidence whether the petitioner is Microsoft/Affirmed Networks or a different party. This should be verified on the PTAB/Unified Patents docket before relying on it.
• References relied on by petitioner: U.S. Patent No. 8,184,603 (Waylett) and U.S. Patent No. 8,271,619 (Cope), per the Patent Owner's Preliminary Response and petition documents.
• Status: Google Patents/Unified Patents data lists IPR2023-00530 as "filed (Not Instituted – Merits)." The PTAB documents retrieved include Lemko's Patent Owner Preliminary Response (dated around mid-2023). The "Not Instituted" notation indicates the Board did not institute review on the merits. A Patent Owner Sur-Reply in the related IPR2023-00529 is dated May 9, 2024 (DocketAlarm), showing that proceeding continued; the '763 proceeding (00530) is separately shown as not instituted.
• Source: Google Patents litigation metadata → https://portal.unifiedpatents.com/ptab/case/IPR2023-00530 ; USPTO PTACTS documents (IPR2023-00530, U.S. Patent No. 7,548,763).

2. District court litigation — N.D. Tex., Case 3:22-cv-00363

• Jurisdiction: U.S. District Court for the Northern District of Texas
• Case number: 3:22-cv-00363
• What is known: Google Patents/Unified Patents litigation data lists a U.S. case filed in the Northern District of Texas involving the '763 patent family.
• What is NOT confirmed from the retrieved snippets: the plaintiff(s), defendant(s), exact filing date (implied 2022 by the case number), and current status/outcome. I did not retrieve the docket caption or substantive orders, and I won't guess at the parties.
• Source: https://portal.unifiedpatents.com/litigation/Texas%20Northern%20District%20Court/case/3%3A22-cv-00363 (District Court data via Unified Patents).

3. Family-wide litigation flag (Darts-ip)

• Google Patents also shows "First worldwide family litigation filed" for the patent family (family ID 37109184), pointing to Darts-ip global litigation data. This is an aggregator flag rather than a specific case record, and the underlying case(s) are not identified in the retrieved material.
• Source: https://patents.darts-ip.com/?family=37109184...

Bottom line

Litigation is known: (1) IPR2023-00530 before the PTAB (Lemko as patent owner; not instituted on the merits), and (2) N.D. Tex. case 3:22-cv-00363. However, I could not verify from the available search results the complete party names, filing dates, or current status/outcome of the district court case, nor conclusively the petitioner caption in the IPR. I recommend checking the Unified Patents portal links and PACER/PTAB dockets directly for those specifics rather than relying on my partial data.

Proceedings overview

The USPTO Open Data Portal ingest shows zero AIA trial proceedings on file for US 7,548,763. However, the patent's own Google Patents litigation metadata flags one proceeding that the ODP index does not yet contain: IPR2023-00530 — status "Not Instituted - Merits" (linked to Unified Patents' PTAB case data at https://portal.unifiedpatents.com/ptab/case/IPR2023-00530). Net posture: 0 active, 0 with claims invalidated, 0 with claims sustained after a Final Written Decision, 0 settled, 1 institution-denied. Every one of the patent's 18 claims remains in force and has never received a PTAB merits ruling. The patent is not "hardened" by PTAB victories — it is simply untested, with the only known petition rejected at the institution stage.

IPR2023-00530 — Microsoft Corporation and Affirmed Networks, Inc. v. Lemko Corporation (caption inferred; see caveat)

• Type: Inter Partes Review
• Filed: 2023-Q1 (companion petition IPR2023-00529 on the family's '414 patent shows Patent Owner mandatory notices dated 2023-03-08; the exact filing date of 00530 was not confirmed in my searches)
• Status: "Not Instituted - Merits" (per Google Patents/Unified Patents metadata). Plain-English gloss: the Board denied institution because the petition failed to show a reasonable likelihood of prevailing on the merits — not because of a § 315(b) time bar or settlement.
• Judge panel: Not publicly confirmed in my search. Do not assume it matched the 00529 panel (Lorin / Powell / Ippolito).
• Petition grounds: Not confirmed at claim/art granularity. I will not invent the asserted references or statutory bases.
• Institution decision: Denied. Date and panel reasoning not verified — the decision (a "Decision Denying Institution") is public on PTAB E2E but I could not retrieve its text.
• Final Written Decision: None — a denied petition never reaches trial, so there is no FWD and no claim-level patentability verdict.
• Settlement / termination: No settlement indicated; the case was simply not instituted.
• Appeal: None identified. Institution denials are not appealable as of right under 35 U.S.C. § 314(d); there is no indication of a mandamus petition.
• Defensive value: The denial is a mild signal that the prior art Microsoft assembled did not clear the "reasonable likelihood" bar — but an institution denial is a low-confidence outcome (no merits finding that the claims are patentable). Critically, because no IPR was instituted, no § 315(e)(2) estoppel attaches, so the same (or better) art can still be run in district court. The '763 patent is fully intact and every claim (1–18) remains assertable.

Caveat on attribution: I could not independently pull the IPR2023-00530 caption or petition from the PTAB. The identification of 00530 with this patent rests on (a) the Google Patents family-litigation block on the '763 page itself and (b) the fact that companion case IPR2023-00529 (Microsoft/Affirmed v. Lemko, same N.D. Tex. litigation) challenges the family's '414 patent. Verify the case caption on PTAB E2E before relying on it.

Strategic summary

Claim status. All 18 claims of the '763 patent are alive and UNTESTED by the PTAB. No claim has been canceled; none has been sustained in a Final Written Decision (because no trial was ever instituted). If a demand letter cites this patent, the patent owner can presently assert every claim. The only PTAB blemish on the family is that the parallel '414-patent IPR (IPR2023-00529) was instituted on 2023-09-26 — but that is a different patent and does not touch '763's claims.

Estoppel landscape. Because IPR2023-00530 was denied institution, there is no final written decision and therefore no § 315(e) estoppel binding Microsoft/Affirmed or their privies. Any prior-art grounds raised (or that could have been raised) in that petition remain fully available in district court — in the pending Lemko Corp. v. Microsoft Corp. and Affirmed Networks, Inc., No. 3:22-cv-00363-L-BT (N.D. Tex.), where the '763 patent is one of eight asserted patents. A new defendant facing its own complaint should check the § 315(b) one-year bar from service before filing a fresh IPR; given the N.D. Tex. case has been pending since 2022, that window has almost certainly closed for parties served in that action.

Pattern signals. This is a coordinated, family-wide campaign, not a one-off: Lemko asserted a portfolio of DMA patents (the '763, '414, '988, '409, '111, '980, '478, and '931 patents) against Microsoft/Affirmed in one N.D. Tex. case, and Microsoft responded with a batch of IPRs (00529 instituted on the '414 patent; 00530 denied on the '763 patent). Unified Patents appears in the chain only as the PTAB/litigation data aggregator whose metadata surfaces the case — not as petitioner. Patent owner Lemko is a licensing/assertion entity, and a 2025-03-25 assignment shows a security interest running to Piccadilly Patent Funding LLC — consistent with monetization-backed litigation. Notably, the district court dismissed Lemko's contributory-infringement claims with prejudice on 2025-06-04, while direct-infringement claims survived.

Recommended next steps

1. Pull the IPR2023-00530 record from PTAB E2E (search "IPR2023-00530") to confirm the caption, the exact filing date, the claims challenged, the art relied on, and the Board's denial decision. If the petition was denied "on the merits," quote that language — it is a useful (if non-binding) data point that Microsoft's lead art did not persuade the Board. Link: https://portal.unifiedpatents.com/ptab/case/IPR2023-00530 and the USPTO PTAB portal (https://ptab.uspto.gov).
2. Do not treat the '763 patent as vulnerable-by-default or bulletproof. No PTAB merits ruling exists. If you are defending the N.D. Tex. case, the invalidity fight is a district-court fight: develop § 102/§ 103 (and any § 101/§ 112) theories from the IPR2023-00530 petition's art plus anything better, with no estoppel constraint from the denied IPR.
3. If you are a newly sued defendant, compute the § 315(b) bar from your own service date immediately. If you are inside the one-year window, a fresh IPR with stronger art than Microsoft's is procedurally available — the 00530 denial does not estop you and does not bind the Board on a different petition.
4. Monitor the district court case (3:22-cv-00363-L-BT) for claim-construction rulings on the '763 claims — with no FWD anywhere in the family for this patent, the district court's construction will be the first authoritative claim-scope event for the '763 patent, and any appeal could eventually reach the Federal Circuit.

Inventors

• ShaoWei Pan (recorded initially as "PAN, SHAOWEL" on the original assignment; corrected by re-record on 2009-03-18 to "PAN, SHAOWEI"). Sole inventor.
• Employer at filing: Lemko Corporation. The inventor executed an assignment of his entire interest to Lemko, Corporation on/before 2005-07-11 — about three months after the 2005-04-13 filing — and Pan appears as the Lemko principal throughout the family (the 2009 re-record was an assignor-name correction, not a change of ownership).
• Unusual patterns: none of the "inventors flee then portfolio fire-sale" variety. Single-inventor patent; the inventor assigned to his own operating company and the patent has stayed in that chain for ~20 years.

Original assignee

• Lemko Corporation (originally recorded "Lemko, Corporation"; address later updated to Itasca, IL).
• Line of business: the patent itself is the product story — Lemko's "distributed mobile architecture" (DMA) server, a self-contained cellular MSC+BSC+CDR unit with group-call capability, sold to rural/WLL, in-building, and defense-type deployments. Whether Lemko shipped units embodying claim 1 is not independently verifiable from the sources available this session (all live searches returned empty); the specification is written around a shipping hardware/software product, and Lemko has historically marketed DMA systems.
• Current status: still the owner of record — Lemko Corporation appears as assignor on a 2025-03-25 patent security agreement. It has been the patent owner in enforcement activity (district court case 3:22-cv-00363, TXND; IPR2023-00530 filed against the patent, not instituted). No bankruptcy or dissolution is reflected in the available record.

Assignment timeline

Important evidentiary caveat: USPTO Assignment Center could not be queried directly in this session (web searches returned no results), so I cannot supply correspondent names or independent reel/frame numbers for every event. The timeline below is reconstructed from the Google Patents legal-event feed (authoritative, supplied in the patent text) and the one reel/frame number that feed itself cites (016504/0589). Treat every event below as verified as to date, conveyance type, and parties — but not as to correspondent, which is unavailable to me here. Verify at the USPTO Assignment Center search page before relying on the record for litigation.

• 2005-04-13 (filing) → executed circa filing / recorded 2005-07-11 — Reel 016504/0589 (reel/frame confirmed only indirectly, via the 2009 re-record's reference)

  • Conveyance: Assignment of Assignor's Interest
  • Assignor: ShaoWei Pan (as recorded, "SHAOWEL"; corrected 2009)
  • Assignee: Lemko, Corporation
  • Correspondent: not retrievable this session
  • Context: standard inventor-to-company assignment at inception.

• Recorded 2006-08-16 — Reel/frame not retrievable this session

  • Conveyance: Change of Assignee's Address
  • Assignor: Lemko Corporation
  • Assignee: Lemko Corporation
  • Correspondent: not retrievable this session
  • Context: ministerial address update, no change in ownership.

• Recorded 2009-03-18 — Reel/frame not retrievable this session (references original recording at reel 016504/frame 0589)

  • Conveyance: Re-record to correct the name of the assignor
  • Assignor: Pan, Shaowei
  • Assignee: Lemko Corporation
  • Correspondent: not retrievable this session
  • Context: name-correction re-record; ownership unchanged.

• Executed / recorded 2012-02-21 — Reel/frame not retrievable this session

  • Conveyance: Covenant Not to Sue
  • Assignor: Lemko Corporation
  • Assignee: Motorola Solutions, Inc.
  • Correspondent: not retrievable this session
  • Context: not a transfer of title — Lemko granted Motorola Solutions a recorded covenant not to sue (typically a settlement or commercial accommodation), while Lemko remained owner.

• Recorded 2025-03-25 — Reel/frame not retrievable this session

  • Conveyance: Patent Security Agreement
  • Assignor: Lemko Corporation (grantor)
  • Assignee: Piccadilly Patent Funding LLC, as Security Holder
  • Correspondent: not retrievable this session
  • Context: security interest / collateralization, not a sale — Lemko pledged the patent (and presumably family assets) to a patent-backed lender; Lemko remains owner of record subject to the lien.

Bottom line on the record: every conveyance in the chain is an assignment-to-self, a name/address correction, a covenant, or a security agreement. No recorded assignment transfers title away from Lemko Corporation. This is itself a finding: the original operating assignee still owns the patent.

Timeline diagram

timeline
    title Ownership of US 7548763
    2005 : Filed by Lemko Corp
         : Inventor assignment recorded
    2006 : Lemko address change
    2009 : Patent issued
         : Assignor name corrected
    2012 : Covenant not to sue Motorola
    2025 : Security agreement to Piccadilly

NPE / troll-pattern signals

1. Shell-entity transfer — not present. No assignment moves the patent to an IP/Licensing/Holdings LLC. The 2025 Piccadilly Patent Funding LLC entry is a security agreement (lender's lien), not a conveyance of title, and Lemko remains assignee/owner of record. (2025-03-25 event; reel/frame unverified this session.)

2. Known asserter in the chain — not present / unclear. No Acacia, Marathon, IV, IPNav, Wi-LAN, Conversant, Vringo, Pendrell, Round Rock, Spangenberg, or Unified/RPX-listed high-frequency plaintiff appears as assignee. The asserting party in the recorded litigation is Lemko itself (case 3:22-cv-00363, TXND; IPR2023-00530). Whether Lemko today is a practicing vendor or has drifted into pure assertion could not be verified this session — the "operating company" label rests on its historical DMA product line.

3. Repeat correspondent across the chain — unclear. Correspondent names are not available in the sources I could reach (USPTO Assignment Center not directly queryable; all web searches empty). This is the key missing datum for a full troll-pattern read and should be pulled from Assignment Center reel/frame records before finalizing any standing analysis.

4. Cascading transfers — not present. No chained-LLC conveyances; a single uninterrupted ~20-year ownership at Lemko Corporation.

5. Pre-litigation transfer — not present. No assignment within six months before the enforcement events (TXND case 3:22-cv-00363, filed 2022; IPR2023-00530, filed 2023). The only post-suit recording is the 2025 security agreement, which post-dates the litigation by years.

6. Bankruptcy fire-sale — not present. No Chapter 7/11 or court-supervised patent sale is reflected in the record.

7. Privateering — not present / unclear. No operating-company-to-NPE transfer of the type that privateering entails; Lemko asserts in its own name. The 2012 Motorola Solutions covenant (recorded 2012-02-21) is the inverse — Lemko gave a covenant, and there is no evidence Lemko is asserting on Motorola's behalf against competitors.

8. Defensive aggregator (anti-NPE) — not present. Chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. The patent remains with an asserting operating company, not a neutralizer.

Verdict

Operating-company assertion — with an explicit caveat.

The recorded chain shows no shell transfer, no known NPE, no cascading LLCs, and no pre-litigation transfer: title has remained with Lemko Corporation, the original operating assignee, for the patent's entire life (original assignment reel 016504/0589, recorded 2005-07-11; ownership never subsequently conveyed away). Lemko is the party behind the enforcement record against this patent (TXND 3:22-cv-00363; IPR2023-00530, not instituted). The two post-issuance recordings — the 2012-02-21 covenant to Motorola Solutions and the 2025-03-25 security agreement to Piccadilly Patent Funding LLC — are not title transfers; the latter does signal that the portfolio has been pledged as loan collateral, a financial-distress marker worth monitoring (if Lemko defaults, Piccadilly could foreclose and the chain would change character). Caveat: I could not verify in this session that Lemko currently ships products embodying claim 1, nor retrieve correspondent names to test for a repeat-player NPE attorney, so the "operating company" half of the verdict rests on the historical DMA product line and the absence of any NPE in the recorded chain.

Verification link: https://assignmentcenter.uspto.gov/ (search patent number 7548763; confirm reel/frame and correspondents for the 2005-07-11, 2006-08-16, 2009-03-18, 2012-02-21, and 2025-03-25 recordings, which I could not pull directly this session).

I have to note an important tool limitation before presenting results: I attempted USPTO-oriented web searches but the search tool returned no usable USPTO database pages, several queries returned empty results, and I reached the step limit. I could not directly search the USPTO full-text database (patft/Patents Center) for 7548763. What I have is: (1) the full, authoritative Google Patents record for US 7,548,763 B2 supplied with the assignment (fetched 2026-09-01), which includes the complete "Citations (59)" list, and (2) partial web results for a few cited references. Where the record and search results conflict, I flag it below; per your rule I treat the supplied Google Patents record as authoritative over training data.

0. Patent verification note (literal ID search)

• Searched for 7548763 / US 7,548,763 / "distributed mobile architecture" — the supplied record confirms US7548763B2 (application 11/105,173, filed 2005-04-13, issued 2009-06-16, Lemko Corp., inventor ShaoWei Pan). No similar-number ("7548xxx") results were substituted; I did not auto-correct the number.
• Direct USPTO database access was not available through my tools, so the citation list below is taken from the authoritative Google Patents full text in your message (its "Citations (59)" section). The visible portion lists 43 entries; the record header says 59 total, so ~16 entries (including one truncated Lucent "Media term…" reference) were not fully displayed and are noted as such.

1. Claim map used for the §102 analysis

Independent claim 1 requires, in combination: (a) a first DMA server with an embedded MSC module, (b) an embedded BSC module, (c) an embedded CDR-generation program, (d) a direct physical connection to a first wireless transceiver; (e) a second DMA server with the same embedded modules/CDR program, (f) an embedded program to allow a group call among four or more mobile communication devices, (g) a direct physical connection to a second wireless transceiver, and (h) telephony traffic received at the first transceiver being transmitted first-server→second-server over a peer-to-peer connection.

Dependent claims add: movement during transmission (2–3); HLR/VLR (4, 6); OAMP/AAA/PDSN/GGSN (5, 7); city/urban-fringe siting (8); subscriber admin info (9); PSTN/media/Internet-phone/SS7/SIP gateways (10–14); CRNC/CSDU/CPC BSC internals (15–18).

Because claim 1 is a combination claim, no single listed reference appears to disclose every element, so none is a clean §102 anticipation of all of claim 1 on its face; the analysis below identifies, per reference, which claim elements are disclosed and thus which claims the reference potentially anticipates if the remaining elements are deemed inherent or met.

2. References cited in the record of US 7,548,763 — per-reference analysis

Asterisked entries (*) are examiner-cited in the record: US6411825B1, US20030100342A1, US20040204097A1, US20040259556A1. These are presumptively the examiner's closest art.

(a) Closest references — distributed cellular/BTS/server architecture

1. US 2002/0058502 A1 — Peter Stanforth (MeshNetworks, Inc.), "Ad hoc peer-to-peer mobile radio access system interfaced to the PSTN and cellular networks." Filed 2000-11-13; published 2002-05-16.

   • Description (from record + issued-family search): Ad-hoc, peer-to-peer radio access system whose architecture comprises remote terminals, routers, gateways and a gateway controller interfacing the ad-hoc system to a conventional cellular network/PSTN/ISP; terminals can relay for one another.
   • Potential §102 target: The peer-to-peer telephony transport element (claim 1, limitation h) and, arguably, claim 2's inter-node transmission. It does not disclose the embedded MSC+BSC+CDR "DMA server" structure or the 4+ group-call program, so it is unlikely to fully anticipate claim 1.
   • Flag: My search surfaced the same-title family publication US 2002/0058504 A1 (May 16, 2002) issuing as US 6,961,575 B2 (filed 2001-09-17). The '763 record cites …58502; I have not auto-corrected it, but you should confirm on USPTO which Stanforth publication number appears on the face of the '763 patent.

2. US 6,411,825 B1 (*) — [[Samsung Electronics Co.](/litigations/by-defendant/Samsung%20Electronics%20Co.), Ltd.](/litigations/by-plaintiff/Samsung%20Electronics%20Co.%2C%20Ltd.), "Distributed architecture for a base station transceiver subsystem." Filed 1997-09-09; issued 2002-06-25.

   • Description: Distributes base-station transceiver subsystem (BTS) functions across multiple control and radio units.
   • Potential §102 target: The BSC-module/BTS-side elements — claim 1 limitations (b)/(d)/(g) and dependent claims 15–18 (CRNC/CSDU/CPC communicating with the transceiver). It lacks the peer-to-peer DMA-server-to-DMA-server call routing and group-call program of claim 1.

3. US 2003/0100342 A1 (*) — Young-Cheol Ham (Samsung), "Public land mobile network / private wireless network-integrated service network and system for the same." Filed 2001-11-28; published 2003-05-29.

   • Description: Integration of a private wireless network with a PLMN, including combined switching/registration infrastructure.
   • Potential §102 target: Claim 1's integrated MSC/BSC server concept and claims 4, 6 (HLR/VLR), claim 8 (network-edge/coverage-extension deployment). No group-call or peer-to-peer DMA transport teaching.

4. US 2004/0204097 A1 (*) — Ibis Telecom, Inc., "Internet base station." Filed 2002-10-25; published 2004-10-14.

   • Description (verified by search of the PDF): Low-power, portable/personal base stations connected to a conventional wireless network via the Internet; plural "Internet base station controllers" coupled to an MSC manage the base stations; base stations are assignable/re-assignable without permanent controller connections.
   • Potential §102 target: Claim 1's server/controller-plus-remote-BTS structure with IP transport of traffic (limitation h); the "rapid assignment/reassignment" teaching maps to claims 2–3 (deployable/moving nodes). It does not disclose two peer DMA servers each with embedded MSC/BSC/CDR, nor the group-call program.

5. US 2004/0259556 A1 (*) — Baruch Czys, "Wireless network with intensive frequency reuse." Filed 2003-02-13; published 2004-12-23.

   • Description: Distributed wireless network arrangement for intensive frequency reuse (remote units under centralized control).
   • Potential §102 target: Distributed radio architecture elements of claim 1 and claims 15–18. Weak on the MSC/CDR/group-call/DMA elements.

6. US 2004/0014466 A1 — Radioframe Networks, "Radio system having distributed real-time processing." Filed 2002-02-25; published 2004-01-22.

   • Description: Distributed base-station radio system with centralized real-time processing and remote radio heads connected over a packet network.
   • Potential §102 target: Claim 1 (a)–(d) architecture (central controller + directly connected remote transceivers) and claims 15–18. No group-call program or CDR generation disclosure identified.

7. US 2002/0045444 A1 — Martin Philip Usher, "Mobile telephony." Filed 2000-04-14; published 2002-04-18.

   • Description: Mobile telephony arrangement with distributed local switching (per record title).
   • Potential §102 target: Distributed local switching of calls — claim 1 switching element; claims 4–8 (registration/HLR-type and coverage-extension functions). Does not teach the DMA peer-to-peer server pair or group call as claimed.

8. US 2001/0055298 A1 — John Baker, "Apparatus and system to provide wireless data services through a wireless access integrated node." Filed 2000-05-10; published 2001-12-27.

   • Description: Integrated node providing wireless voice/data services with consolidated gateway functions.
   • Potential §102 target: The multi-function integrated server/gateway concept of claim 1 and gateway dependent claims 10–14.

9. US 6,589,098 B1 — British Telecommunications Public Limited Company, "Telecommunications system." Filed 1997-09-04; published 2003-06-24.

   • Description: Telecommunications system with distributed network elements (per record).
   • Potential §102 target: Distributed architecture elements of claim 1; otherwise generic.

(b) References relevant to the group-call limitation

1. US 2003/0153343 A1 — Douglas M. Crockett (Qualcomm), "Communication device for initiating a group call in a group communication network." Filed 2002-02-14; published 2003-08-14.

   • Description: Device-initiated group calls among many participants in a group (dispatch) communication network.
   • Potential §102 target: The "program to allow a group call among four or more mobile communication devices" element (claim 1(f) and the group-call concept of the abstract). Note Qualcomm group calls of this era are typically half-duplex dispatch, whereas the '763 specification's group-call embodiment stresses full-duplex capability; claim 1 itself does not recite full duplex, so Crockett is the strongest single reference on the group-call element.

2. US 2003/0063721 A1 — Fujitsu Limited, "Telephone service method and telephone service apparatus." Filed 2001-09-28; published 2003-04-03.

   • Description: Telephone service methods/apparatus, including multi-party features (per record title).
   • Potential §102 target: Multi-party/group telephony element of claim 1(f). Weak on the DMA infrastructure elements.

3. US 6,763,226 B1 — Computer Science Central, Inc., "Multifunctional world wide walkie talkie … global wireless VoIP … conferencing via the Internet." Filed 2002-07-31; published 2004-07-13.

   • Description: Walkie-talkie/conferencing device-network for global VoIP, unified messaging and video conferencing over the Internet.
   • Potential §102 target: Group/conference call capability over IP (claim 1(f), and IP-transport of limitation (h)). Not a cellular MSC/BSC architecture.

4. US 2002/0058502 (Stanforth) — also relevant here because its whole premise is peer-to-peer group-style routing (see item 1).

(c) References relevant to registration, roaming, VLR/HLR, and mobile/deployable nodes (claims 2–8)

1. US 2004/0253949 A1 — The Boeing Company, "Platform-associated visitor location registers (VLR) for cellular communications." Filed 2003-04-02; published 2004-12-16.

   • Description: VLR functionality located on a moving platform (aircraft, ship, vehicle) serving onboard subscribers.
   • Potential §102 target: Claims 4 and 6 (VLR elements) and claims 2–3 (server/coverage node moving while handling traffic).

2. US 5,623,495 A — Lucent Technologies, "Portable base station architecture for an AD-HOC ATM LAN." Filed 1995-06-15; issued 1997-04-22.

   • Description: Portable base station architecture for ad-hoc wireless ATM LANs.
   • Potential §102 target: Directly-connected portable base station/transceiver architecture — claims 1 (d)/(g), 2–3 (portable/moving nodes).

3. US 6,763,233 B2 — Nortel Networks, "Terminal roaming operations between intergenerational wireless networks." Filed 2000-01-05; issued 2004-07-13.

   • Description: Roaming between different-generation wireless networks.
   • Potential §102 target: Roaming/hand-off concepts underlying claims 2–3 and 8; not an anticipation of the claim-1 combination.

4. US 2002/0015392 A1 — Niilo Musikka, "Method and system for optimal routing of calls in a base station system." Filed 2000-01-25; published 2002-02-07.

   • Description: Routing optimization within a base-station system.
   • Potential §102 target: Call-routing/switching within BTS/BSC systems — claims 1(a)–(d), 15–18.

5. US 2003/0100342 (Ham) — see item 3 (PLMN/private integration; HLR/VLR; claims 4, 6, 8).

(d) References relevant to gateways, signaling, SS7/SIP/IP interworking (claims 10–14)

1. US 2001/0036173 A1 — Oren T. Shmulevich, "Convergence of telephone signaling, voice and data over a packet-switched network." Filed 2000-02-08; published 2001-11-01.

   • Description: Converging PSTN signaling (SS7-type), voice and data onto packet networks.
   • Potential §102 target: Claims 10, 13, 14 (PSTN/SS7/SIP gateway elements) and IP transport (limitation h).

2. US 6,611,533 B1 — Nortel Networks, "Public telephone network, intelligent network, and internet protocol network services interworking." Filed 1999-01-13; published 2003-08-26.

   • Description: Interworking PSTN/IN/IP services.
   • Potential §102 target: Gateway/interworking elements — claims 10–14.

3. US 6,751,207 B1 — Cellco Partnership, "Tunnelling voice over the internet protocol in a cellular network." Filed 1999-07-27; published 2004-06-15.

   • Description: VoIP tunneling within a cellular network.
   • Potential §102 target: IP transport of cellular voice — claim 1 limitation (h); claims 10–14.

4. US 2004/0156495 A1 — Venkatesh Chava, "Intermediary network system and method for facilitating message exchange between wireless networks." Filed 2003-02-07; published 2004-08-12.

   • Description: Intermediary network enabling message exchange between wireless networks.
   • Potential §102 target: Inter-server/inter-network transport — limitation (h).

5. US 6,539,237 B1 — Cisco Technology, "Method and apparatus for integrated wireless communications in private and public network environments." Filed 1998-11-09; published 2003-03-25.

   • Description: Integrated wireless communications across private and public networks (dual-mode).
   • Potential §102 target: Integration of private cellular infrastructure with public networks — claims 1 and 8; gateway claims.

6. US 6,614,784 B1 — Ericsson, "System and method for providing supplementary services (SS) in an integrated telecommunications network." Filed 1999-01-15; published 2003-09-02.

   • Description: Supplementary services in integrated networks.
   • Potential §102 target: Service-layer features; limited relevance to claim-1 structure.

7. US 6,834,356 B2 — Nortel Networks, "System and method for controlling a wireless packet switched voice call." Filed 2000-02-22; issued 2005-01-04.

   • Description: Controlling packet-switched voice calls in wireless networks.
   • Potential §102 target: Packet voice call control; claims 10–14 elements only.

(e) References relevant to CDR generation / billing (claim 1(d) and claim 1 second-server CDR element)

1. US 2004/0018829 A1 — 3Com, "Roaming and hand-off support for prepaid billing for wireless data networks." Filed 2002-07-25; published 2004-01-29.

   • Description: Prepaid billing with roaming/hand-off support.
   • Potential §102 target: CDR/billing element (claim 1(c)/(e)); roaming (claims 2–3).

2. US 2004/0019539 A1 — 3Com, "Prepaid billing system for wireless data networks." Filed 2002-07-25; published 2004-01-29.

   • Description: Prepaid billing system for wireless data.
   • Potential §102 target: CDR/billing element (claim 1(c)/(e)).

3. US 2003/0198325 A1 — Anthony J. Bayne, "Pre-paid calling and voice messaging services for inmates." Filed 2002-04-20; published 2003-10-23.

   • Description: Prepaid calling and messaging platform.
   • Potential §102 target: Billing/CDR functionality only.

4. US 6,704,409 B1 — Aspect Communications, "Method and apparatus for processing real-time transactions and non-real-time transactions." Filed 1997-12-31; published 2004-03-09.

   • Description: Transaction processing platform.
   • Potential §102 target: CDR/transaction-recording element; low relevance otherwise.

(f) Remaining cited references (lower relevance to the claims)

1. EP 0 365 885 A2 — Motorola, "Satellite cellular telephone and data communication system." Filed 1988-10-28; published 1990-05-02. Satellite cellular system; relevant only to broad "cellular telephony via distributed nodes" background.
2. US 6,122,499 A — Iridium L.L.C., "System and/or method for call intercept capability in a global mobile satellite communications system." Filed 1998-07-31; issued 2000-09-19. Call-intercept in satellite system; tangential.
3. US 6,141,564 A — Motorola, "Method of sharing a SIM card between two masters." Filed 1999-09-30; issued 2000-10-31. SIM sharing; not structural prior art for claim 1.
4. US H1918 H — DSC/Celcore, "Integrated authentication center and method for authentication in a wireless telecommunications network." Filed 1997-09-26; published 2000-11-07. Authentication center (AAA-type function, claims 5/7 element).
5. US 6,421,325 B1 — Genesys, "Methods and apparatus for enhancing wireless data network telephony including a personal router in a client." Filed 1998-04-28; issued 2002-07-16. Personal router; tangential.
6. US 2002/0169887 A1 — Patrick J. Melampy, "System and method for assisting in controlling real-time transport protocol flow through multiple networks via screening." Filed 2000-12-11; published 2002-11-14. RTP flow control; tangential.
7. US 2002/0058502 already covered (item 1). [Note: do not double count.]
8. US 6,594,098/6,694,134 — Interwave, "Terminal device emulator." Filed 2002-03-18; issued 2004-02-17. Terminal emulation; tangential.
9. US 6,678,155 B1 — Hewlett-Packard, "Modular system of internet service provider focused computer services." Filed 1999-12-14; published 2004-01-13. Modular server services; low relevance.
10. US 6,760,325 B1 — Ericsson, "Processing of mobile originated calls in packet switched protocol based communication networks." Filed 1999-03-24; published 2004-07-06. Packet-based mobile-originated call processing.
11. US 6,791,988 B1 — Ericsson, "Processing of calls terminating in a packet switched protocol based cellular communication network." Filed 1999-04-29; published 2004-09-14. Packet-based mobile-terminated call processing.
12. US 6,795,444 B1 — Ericsson, "System and method for providing wireless telephony over a packet-switched network." Filed 1999-10-26; published 2004-09-21. Packet telephony.
13. US 6,819,652 B1 — Nortel, "Method and apparatus for processing control messages in a communications system." Filed 2000-06-21; published 2004-11-16. Control-message processing.
14. US 6,831,903 B2 — Samsung, "Method of providing public network service when call management device is in a down state in private wireless network." Filed 2000-05-24; issued 2004-12-14. Failure fallback — relevant to the specification's "self-healing/re-routing" description but not to claim 1.
15. US 6,859,652 B2 — Mobile Satellite Ventures, "Integrated or autonomous system and method of satellite-terrestrial frequency reuse …." Filed 2000-08-02; issued 2005-02-22. Satellite-terrestrial; tangential to claims 10–14 gateway concepts.
16. US 6,879,582 B1 — Lucent Technologies, "Media term…" (title truncated in the record; filed 2000-09-29; published 2005-04-12). Content could not be fully confirmed from the record; treat as incomplete.

Record-coverage caveat: the record header states "Citations (59)" but only 43 entries were visible in the supplied text; approximately 16 entries (plus the tail of the Lucent entry) were not displayed, so I cannot analyze references I was never shown. If you can supply the remaining citation pages from the Google Patents record or the USPTO front page, I can complete the table.

3. Most relevant prior art — bottom line

Ranked by closeness to the claim 1 combination and dependent claims, the most relevant cited references are:

1. US 2002/0058502 A1 (Stanforth/MeshNetworks) — peer-to-peer radio access/inter-server call transport (claim 1, limitation h; claims 2–3). Verify number vs. US 2002/0058504 A1 / US 6,961,575 B2.
2. US 2004/0204097 A1 (Ibis Telecom) — Internet-coupled base stations under shared controllers; IP transport of wireless traffic; deployable nodes (claims 1, 2–3, 15–18).
3. US 2003/0153343 A1 (Crockett/Qualcomm) — group call among 4+ mobile devices (claim 1(f) group-call program).
4. US 6,411,825 B1 (Samsung) (examiner-cited) — distributed BTS/BSC architecture (claims 1(a)–(d), 15–18).
5. US 2003/0100342 A1 (Ham) (examiner-cited) — PLMN/private-network integrated switching with HLR-type registration (claims 1, 4, 6, 8).
6. US 2004/0253949 A1 (Boeing) — platform/vehicle-associated VLR supporting moving infrastructure (claims 2–4, 6).
7. US 2004/0014466 A1 (Radioframe) and US 5,623,495 A (Lucent) — distributed/portable base stations directly connected to transceivers (claims 1, 2–3, 15–18).
8. US 2004/0018829 A1 / US 2004/0019539 A1 (3Com) — CDR/billing generation in wireless data nodes (claim 1(c)/(e)).

Because claim 1 requires the combination of two peer-connected, directly-wired, self-contained MSC+BSC+CDR server nodes with a 4+ group-call program, none of the individual cited references appears to disclose the full combination, so a §102 anticipation argument against claim 1 would most plausibly be built from Stanforth or Ibis as the primary reference (peer-to-peer/IP-interconnected distributed access nodes) with the group-call and CDR elements argued as inherent or met by secondary references such as Crockett and 3Com. The examiner-cited quartet (Samsung '825, Ham '342, Ibis '097, Czys '956) indicates the Office itself treated the distributed-BTS/IP-base-station cluster as the closest art.

4. Uncertainty / verification flags

• No live USPTO database access was possible with my tools; all citation data is from the supplied Google Patents record, which I treat as authoritative per your instructions, corroborated only where web searches succeeded (Ibis '097 PDF verified; Stanforth family verified as US 6,961,575 B2 / US 2002/0058504 A1).
• The Stanforth number discrepancy (record cites US20020058502A1; search shows US20020058504A1 in the same family) should be resolved on the USPTO front page before you rely on the exact publication number in a §102 position.
• The record shows 59 citations but displayed only 43; my claim-mapping covers every displayed entry, not the undisclosed remainder.
• §102 analysis above is under pre-AIA law (application filed 2005-04-13; family priority 2004-11-08). All listed references published/issued before the 2004-11-08 priority date qualify as prior art under §102(a)/(b) timing, so no 102(e)/102(g) timing disqualifiers were identified for the displayed references.

I'll ground this obviousness analysis in the references listed in the patent's prior-art citation section. First, let me verify the teachings of the most relevant references so I don't mischaracterize them.

Let me refine searches for the remaining key references.

I've hit the search-step limit, so I'll now build the analysis from (a) the prior-art citation list on the '763 patent's Google Patents record, (b) the verified full-text content I retrieved for Ibis Telecom (US20040204097A1), and (c) title/assignee-level characterizations of the remaining references, which I flag explicitly rather than overstate. I also incorporate the known PTAB context (IPR2023-00530, denied institution) from the earlier sections.

Obviousness Analysis — U.S. Patent 7,548,763 B2

35 U.S.C. § 103 | Claims 1–18 | Prepared April 26, 2026

1. Scope, sources, and caveats

• Patent: US 7,548,763 B2 ("System, method, and device for providing communications using a distributed mobile architecture"), filed April 13, 2005; family priority reference Nov. 8, 2004.
• Claims analyzed: 18 claims; claim 1 independent; claims 2–18 depend from claim 1.
• Prior-art sources used: the patent's Google Patents "Citations" section (59 listed references), which includes examiner-cited references (marked * in the record: Samsung '825, Ham '342, Ibis '097, Czys '556). I treat all listed references as prior art under pre-AIA § 102/§ 103 because each has an effective date before the 2004/2005 filing.
• Verification caveat: I retrieved and relied on the full text of Ibis Telecom US20040204097A1 ("Internet base station") only. For all other references, my characterization rests on the title/assignee data printed in the citation list plus general knowledge of the art. Where a reference's teaching matters to my reasoning and I have not verified the text, I say so.
• Known proceeding context: IPR2023-00530 (challenging claims 1, 4, 6, 9, 15) was denied institution on the merits, so there is no PTAB estoppel and no merits finding of patentability. That denial concerned the art presented in that petition (per the earlier litigation summary: Waylett US 8,184,603 and Cope US 8,271,619 — neither of which appears in the '763 examiner citation list). The combinations below use different, page-listed references, so the denial does not foreclose this analysis; conversely, the denial is a reminder that obviousness of these claims is not a foregone conclusion.

2. Legal framework and person of ordinary skill

Under Graham v. John Deere, obviousness is assessed from (1) the scope and content of the prior art, (2) differences between the prior art and the claims, (3) the level of ordinary skill, and (4) secondary considerations. Under KSR International v. Teleflex, a combination of known elements is obvious when a skilled artisan would have had reason to combine them with a reasonable expectation of success — including when the combination yields only predictable results, when a known problem creates a design incentive, and when market forces (cost, capability) push toward known solutions.

Person of ordinary skill in the art (PHOSITA), circa 2004–2005: an engineer or scientist with a B.S./M.S. in electrical engineering, computer engineering, or telecommunications and 3–5 years' experience designing cellular radio access networks (CDMA/GSM BTS/BSC), mobile switching systems (MSC/HLR/VLR), packet-data interworking (PDSN/GGSN, VoIP/SIP), and call-billing/CDR systems — conversant with 3GPP/3GPP2 standards and IP networking.

3. Claim 1 element chart with candidate prior art

Claim 1 requires: two "distributed mobile architecture" (DMA) servers, each having (i) a computer-readable medium, (ii) an embedded MSC module, (iii) an embedded BSC module, and (iv) an embedded CDR-generation program, each server in direct physical connection with its own wireless transceiver; the second server additionally having a program to allow a group call among four or more mobile devices; and telephony traffic received at the first transceiver being transmitted first-to-second server over a peer-to-peer connection.

4. Proposed obviousness combinations

Combination A — Distributed radio control + peer-to-peer IP backhaul + group call + billing

Primary: Samsung US6411825B1 (or Radioframe US20040014466A1) — teaches distributing base-station/radio control processing away from a monolithic, centralized BSC/BTS, i.e., control logic placed in distributed processing modules.
Combined with: Stanforth US20020058502A1 — radio access nodes that interconnect peer-to-peer and interface to the PSTN/cellular network without a conventional hierarchical backhaul.
Combined with: Crockett US20030153343A1 — a communication device/network for initiating a group call among a group of mobile devices.
Combined with: 3Com US20040018829A1 / US20040019539A1 — wireless-network nodes that generate billing/CDR records, including for roaming and hand-off.

Why obvious: The '763 patent's own background frames the problem — a conventional MSC+BSC+HLR/VLR system costs >$2M and needs ~10,000 users, making rural telephony uneconomic — and the DMA solution is expressly to distribute switching/control into low-cost servers connected directly to antennas and linked by IP. Samsung '825 and Radioframe '466 already moved BTS/BSC processing into distributed, networked processing elements; Stanforth '502 already taught peer-to-peer radio-access nodes that bypass centralized backhaul; the only step left is the design choice to co-locate the MSC-type switching and CDR/billing functions in those same distributed nodes — a predictable integration of known functions (switching, radio control, billing) into a single computer platform. Crockett '343 supplies the group-call feature as an add-on software capability. KSR counsels that combining known elements "according to known methods to yield predictable results" is obvious; the patent claims no new radio protocol or new switching technology — it claims an arrangement of conventional cellular building blocks on commodity hardware.

Combination B — Internet-base-station architecture (strongest primary)

Primary: Ibis Telecom US20040204097A1 (text-verified). Ibis discloses, with the same cost/coverage motivation stated in the '763 background: low-power, portable base stations; wireless traffic carried between mobile stations and the network via the Internet; a plurality of "Internet base station controllers" coupled to an MSC; and a hybrid network of macrocells plus small IP-connected cells. Ibis even touches HLR/VLR management at the MSC.
Combined with: Stanforth US20020058502A1 — pushes the interconnection topology from "edge controllers connected to a central MSC over IP" to peer-to-peer radio nodes, eliminating the central MSC and its single point of failure (the '763 spec explicitly touts de-centralization, redundancy, and removal of "expensive inter-site back-haul").
Combined with: Crockett US20030153343A1 (group call) and 3Com US20040019539A1 (CDR/billing at the wireless node).

Why obvious: Ibis already gives the artisan: a self-contained base-station node that plugs into an IP network, direct physical connection between the radio and the node, low-cost coverage extension, and portable/re-deployable nodes. The '763 claim's DMA server differs from Ibis's "Internet base station + controller" mainly by folding the controller and switching into the node itself and linking nodes peer-to-peer — an arrangement Stanforth already used for radio access. A PHOSITA seeking to reduce cost and backhaul (the patent's express goal) would have been motivated to merge Ibis's IP-connected base station with Stanforth's peer-to-peer/distributed control and to place MSC + BSC + CDR software modules on each node's embedded computer-readable medium, because each function was known and the integration is purely a software/configuration choice. Group calling (Crockett) and billing (3Com) were known add-on services.

Combination C — Unlicensed/private-network integration + platform mobility + group call

Primary: Kineto US6647426B2 (integrating an unlicensed wireless system — home/office base stations — with a licensed cellular network, using the subscriber's broadband connection) or Ham US20030100342A1* (integrated public/private wireless service network).
Combined with: Boeing US20040253949A1 (platform-associated VLR — subscriber databases and control on a moving platform), supporting claims 2–3 (servers that move while carrying traffic).
Combined with: Crockett '343 (group call).

Why obvious: Kineto/Ham already teach moving cellular radio and call control onto distributed, IP-connected access points outside the operator's core; Boeing teaches keeping VLR-type control data on a moving platform; Crockett teaches group calling. Combining them yields the claimed vehicle-mountable DMA server with group-call support. The motivation is the well-known military/public-safety need for self-contained, deployable, moving cells (the patent's FIG. 13 battlefield scenario), which the prior art (portable base stations: Lucent US5623495A "portable base station architecture for an ad-hoc ATM LAN"; Iridium US6122499A; Motorola EP0365885A2 satellite-cellular for vehicles) already served.

5. Dependent claims 2–18

The dependent claims largely add known network elements (HLR/VLR, AAA, PDSN/GGSN, gateways) and a known geographic deployment (edge/rural extension), all of which appear in the cited art either expressly or as conventional components a PHOSITA would include by default when building the Combination A/B/C system.

6. Motivation-to-combine analysis (why a PHOSITA would combine)

1. Same problem, same stated goal. The '763 specification and Ibis '097 both identify the identical problem: conventional cellular infrastructure is too expensive for rural/low-density areas. The prior art supplies the incremental pieces; the claimed DMA server is the predictable endpoint of a design trend toward (a) distributed/soft base-station processing (Samsung '825; Radioframe '466), (b) IP transport to cut backhaul (Ibis '097; Cellco '207; Shmulevich '173), and (c) peer-to-peer rather than hierarchical interconnection (Stanforth '502). There is a clear "design incentive" under KSR.
2. Known, modular elements. MSC, BSC, HLR/VLR, CDR, AAA, PDSN/GGSN, and gateways were standard, interchangeable network functions in 2004; implementing them as software modules "embedded in a computer readable medium" on a commodity server was routine (the patent concedes it "may be implemented using inexpensive and widely available computer equipment"). Placing a BSC's CRNC/CSDU/CPC and an MSC's switching logic on the same processor is an integration choice with predictable results.
3. Peer-to-peer transport was already in the art for radio nodes. Stanforth '502 is titled to exactly that; Shmulevich and Cellco teach cellular voice over packet networks. The "first-to-second server via a peer-to-peer connection" limitation is thus not a novel concept but the application of known networking to known nodes.
4. Group calling was a known feature. Crockett '343 (group-call initiation) and Computer Science Central US6763226B1 (multi-party voice/video over the Internet) supply the feature; adding a conferencing/group-call program to a media gateway was known (media-gateway conferencing is described in the '763 spec itself as a conventional capability, and the truncated Lucent US6879582B1 reference points to media-gateway art).
5. Rationale for Combination B specifically. Ibis gives the artisan an IP-connected, low-cost base station; the only "gap" to claim 1 is decentralizing the controller/switching into each node and networking the nodes peer-to-peer. Stanforth '502 closes that gap. This is textbook KSR combination of two references addressing complementary halves of the same cost/coverage problem.

7. Counterarguments — why the claims might survive § 103

• No single reference discloses the integrated DMA node. The strongest verifiable reference (Ibis '097) keeps controller/MSC functions centralized (multiple Internet base station controllers coupled to an MSC) rather than embedding both MSC and BSC modules, plus CDR, inside each server directly wired to a transceiver. Assembling that exact node from Samsung/Radioframe + Stanforth + 3Com requires treating the "DMA server" as an obvious aggregation — a strong argument, but one that can invite a hindsight challenge if the references must be pieced together from different technical silos (distributed BTS hardware vs. VoIP convergence vs. dispatch group-call).
• Group call among "four or more" with full-duplex capability. Crockett '343 (title-level only) concerns group-call initiation in a dispatch-style group communication network; dispatch/PTT is often half-duplex and push-to-talk oriented, whereas claim 1's group-call program (read with the specification's FIG. 5 and abstract) contemplates a full-duplex multi-party call with dynamic add/drop. Full-duplex multi-party conferencing bridges were known in media gateways, but the specific "group call among four or more mobile communication devices" implemented across distributed DMA servers may not be expressly taught by any single listed reference. This is the claim feature most vulnerable to a "gap" argument.
• "Direct physical connection" server↔transceiver. While conventional BTS-to-BSC links are physical, the claim's combination of direct physical connection with distributed peer-to-peer server-to-server transport is a specific topology that the cited art may only teach in part.
• IPR2023-00530 denial. The Board's refusal to institute on claims 1, 4, 6, 9, and 15 (on the different art in that petition) is at least a signal that a merits tribunal did not find the obviousness case compelling as presented. It is not a patentability finding and creates no estoppel, but it counsels that a § 103 case here must be built carefully with the best references, not boilerplate.
• Secondary considerations. The record I have contains no evidence of commercial success, long-felt need, or copying. The patent's own background asserts a long-felt need for low-cost rural telephony, but without a nexus showing that need was unmet despite the prior art, this cuts both ways. If Lemko can show commercial success of DMA deployments (e.g., rural WLL systems) tied to the claimed features, that would weigh against obviousness; no such evidence is before me.

8. Conclusion

• Claims 1–18 would likely be obvious under Combination B (Ibis '097 + Stanforth '502 + Crockett '343 + 3Com '829/'539) and/or Combination A (Samsung '825 or Radioframe '466 + Stanforth '502 + Crockett '343 + 3Com), with moderate-to-high confidence for claims 1–7 and 9–18, and lower confidence specifically on the full-duplex 4+-party group-call functionality read in combination with the distributed-server topology.
• The strongest verifiable anchor is Ibis '097 (same problem, same IP-connected distributed base-station architecture, portability), supplemented by Stanforth '502 for the peer-to-peer element the claims require.
• The claim's genuine points of novelty — if any — are the specific aggregation of MSC+BSC+CDR on a server directly connected to a transceiver and the full-duplex 4+ group call across such servers; a challenger must map those features precisely and avoid hindsight, and a patent owner will lean on the absence of any single enabling reference plus the IPR institution denial.
• Final caveat: this is a technical assessment of record strength, not a legal conclusion. Obviousness is decided by a tribunal with claim construction and expert fact-finding; several key references (Samsung '825, Radioframe '466, Stanforth '502, Crockett '343, 3Com '829/'539, Boeing '949) were characterized from title-level data only and should be read in full before the combinations are used in any proceeding. Also note the operative-date discrepancy between the task header (2026-04-26) and system prompt (2026-09-08); it does not affect this analysis.