US 7522632

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

Let me dig deeper for any 2026 CAFC or district court activity specific to this patent.

Let me retrieve the actual claim text for this patent and check for any reexamination/PTAB or litigation records.

US Patent 7,522,632 — Analyst Summary

Important scope note: You asked me to search USPTO and CAFC 2026 dockets for this specific number. I searched for U.S. Patent No. 7,522,632 (grant) and found no 2026 Court of Appeals for the Federal Circuit docket, appeal, IPR, or district-court case naming this patent. The 2026 Federal Circuit/docket hits my searches returned (e.g., Contour IP Holding v. GoPro, Fed. Cir. No. 2026-2012; Headwater Research v. Verizon; Nokia v. Acer/D. Del. 25-1106) involve unrelated patents. I am reporting that absence explicitly rather than inferring litigation. Also note: "7522632" also returns an unrelated JP Patent No. 7522632 (a Daikin gas-shielded arc welding patent) and a Lithuanian registry notice number — these are not U.S. 7,522,632 and are excluded.

---

Bibliographic data (US 7,522,632 B2)

Family members (from the same 2001-03-19 priority): EP 1244323 B1, DE 60200415 T2, JP 4076775 B2 (JP 2002-330179 A). The specification also states this application is related to commonly assigned application Ser. No. 09/812,401, titled "Multiple-Protocol Home Location Register and Method of Use," by Penny L. Bright et al., filed the same date. Search results indicate a same-titled sibling patent, US 6,950,876 B2 (Lucent), and publication US 2002/0169883 A1; I did not verify the serial-number-to-patent-number mapping from an authoritative USPTO record, so treat that linkage as likely but not confirmed.

---

Abstract (as granted)

A multiple-protocol home location register (MP HLR) comprises a processor that generates network messages according to two or more network protocols and processes network requests and other messages to obtain information requested by two or more networks supporting those protocols. One embodiment (FIG. 2) uses protocol gateways that interpret network requests and generate, using common control procedures for multiple protocols, queries to a database providing a common source of data. Another embodiment (FIG. 4) uses a mediation device that generates and/or translates network messages across protocols and is coupled to multiple HLRs or home agents, each supporting a different protocol.

---

Plain-language overview of the independent claims

Caveat on confidence: The authoritative full text supplied for this analysis includes the specification, abstract, and figures list, but not the claims section. The following is drawn from the Google Patents claims listing for US 7,522,632 B2 and a machine translation of the JP family member (JP 4076775 B2). I am moderately confident on claim 1's granted language and less certain on the exact boundaries of the other independent claims; the full claim set should be confirmed against the USPTO PatentCenter/PDF.

Claim 1 — the MP HLR apparatus (FIG. 4 embodiment). A "multiple-protocol home location register" comprising:

• a receiver that receives a network request from one of at least two requesting networks, the request conforming to one of at least two network protocols;
• a processor within the MP HLR that processes the request using a common source of data and common control procedures for the multiple protocols to obtain the requested information;
• a transmitter operably coupled to the processor that relays the requested information back to the requesting network;
• a standalone HLR for each wireless network and a server for each wireline network of the requesting networks;
• a provisioning gateway (part of the processor) that distributes user data between the standalone HLR(s) and the server(s) within the MP HLR;
• a mediation device coupled to the provisioning gateway, the standalone HLR, and the server; and
• the mediation device being configured to generate network messages, translate network messages, and/or emulate GMSCs, VMSCs, and message centers.

In short: claim 1 as granted is a unified HLR apparatus that internally houses per-protocol HLRs/servers plus a provisioning gateway and a translating/emulating mediation device, and that answers a multi-protocol network request from shared data using shared control procedures.

Likely additional independent claims (structure inferred, moderate confidence). The specification's summary and the sibling family indicate the patent also covers:

1. A method of operating an MP HLR: receive a network request in a first protocol at a first protocol gateway; that gateway interprets/translates the request into a common control procedure; a processor (database manager coupled to the gateway and the database) applies the common data source and common control procedure to process the request; generate and relay at least one database query; receive the requested information from the database; and relay it back through the appropriate protocol gateway to the requesting network. (This tracks the JP 4076775 B2 translated claim 1.)
2. An MP HLR apparatus comprising a first HLR providing a first protocol and a second HLR providing a second protocol, with a mediation device coupled to both that generates network messages in both protocols, so the MP HLR provides HLR capability to devices using either protocol.
3. A system with a first infrastructure device issuing a query in a first protocol and a second infrastructure device operating in a second protocol, where the MP HLR functions in both protocols so that a call request in the first protocol is completed in the second protocol; profiling data is formatted per the serving network's protocol.
4. A method in which a first infrastructure device generates a first-protocol query and sends it to the MP HLR, which processes it to generate a second-protocol message that is sent to a second infrastructure device.

The remaining claims (numbering toward 20, vs. the sibling's 71) appear to be dependent claims addressing protocol-gateway details, common operations (e.g., Register Terminal, Request Location, Retrieve Profile, Cancel Terminal Registration per TABLE 1), and call/message-flow specifics for GSM, ANSI-41/136, SIP, H.323, AAA, and M-IP.

Practical claim scope, in one sentence: the claims are directed to consolidating mobility management — subscriber location, profile, and authentication data — into one HLR entity that speaks multiple wireless and wireline protocols, either via per-protocol protocol gateways over a shared relational database (FIG. 2) or via a mediation device sitting between discrete GHLRs/servers (FIG. 4).

---

Things I did not find / residual uncertainty

• No 2026 Federal Circuit activity for US 7,522,632 in my searches. If a specific 2026 docket number was expected, I could not confirm it.
• The patent is listed as expired (fee-related; adjusted expiration 2025-02-12), which is consistent with the absence of active enforcement litigation — but Google Patents expressly labels its status/expiration data as an assumption, not a legal conclusion, so verify against USPTO PatentCenter.
• Granted claim 1 appears to have been narrowed relative to the published application (the pre-grant US 2002/0167906 A1 summary describes only a receiver/processor/transmitter), and the 20-claim count contrasts with the sibling's 71 claims — suggesting prosecution-history amendments. I could not retrieve the full prosecution history, so the narrowing rationale is inferred, not verified.

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

Let me search the specific litigation databases directly.

Let me try more targeted searches on litigation databases and patent assertion entities.

Findings: Litigation Involving U.S. Patent No. 7,522,632

Bottom line: My searches did not identify any litigation — past or pending — involving U.S. Patent No. 7,522,632. I must be candid that this is a "no known results" finding rather than a confirmed negative, and explain the limits of what I could verify.

What the patent is (for identification, literal identifiers)

Note: I am treating "7522632" strictly as US 7,522,632. Searches surfaced many unrelated hits on the same digit string — e.g., JP Patent No. 7522632, FR 7522632 (a 1975 bicycle-brake application), a Brazilian company registration, a Chinese trademark opposition, and a PACER receipt number — none of which are this US patent. I have excluded all of those.

Searches performed

• Web searches on the bare number, the comma-formatted number ("7,522,632"), and on variants combined with "litigation," "lawsuit," "complaint," "district court," and "Alcatel-Lucent."
• Attempted targeting of litigation aggregators (Unified Patents portal, RPX Insight, Docket Alarm, CourtListener/RECAP, Justia Dockets).

No source returned a plaintiff, defendant, case number, jurisdiction, or filing date tied to US 7,522,632. The results were almost entirely noise (unrelated patents, other case numbers, the patent's own bibliographic page, and inventor-profile aggregator pages such as PatentLeaderboard).

Case table

Important qualifications (why this is not a definitive "no litigation exists")

1. Search-tool limits. I could not directly query PACER or the Unified Patents litigation caselist with the patent number as a filter; the general web searches did not surface indexed docket records for this specific patent. A patent asserted only in a handful of suits, or in suits that settled early, may simply not be indexed by the sources I could reach.
2. The Unified Patents hit I did get was not a litigation record. One result pointed to portal.unifiedpatents.com/patents/patent/US-10547530-B2, i.e., a different patent (US 10,547,530) whose page happened to reference US 7,522,632 in its "related/cited" material. That is a citation artifact, not evidence that 7,522,632 was used in Unified Patents' litigation tracking.
3. Age and status weigh against recent enforcement. The patent is now "Expired – Fee Related" with an adjusted expiration of 2025-02-12, and its term ran from a 2001 priority date. Any suit would have had to be filed before expiration, and the absence of any indexed activity is at least consistent with the patent never having been asserted.
4. Assignee lineage is a plausible source of suits, but I found none. The patent passed Lucent → Alcatel-Lucent → (listed) Nokia of America. The broader Nokia/Alcatel-Lucent portfolio was asserted in unrelated matters (e.g., Nokia Technologies Oy v. Apple Inc., E.D. Tex. 2:16-cv-01440; Regents of the University of Minnesota v. Cellco Partnership, D. Minn. 0:14-cv-04672), but US 7,522,632 does not appear in those complaints, and I did not find it in any assertion campaign (I found no evidence it was transferred to a patent-assertion entity).

Suggested next steps for a definitive answer

To convert this into a conclusive determination, a manual query should be run against sources I could not fully search here:

1. USPTO Patent Center / Assignment records for Application 09/813,016 — confirm whether any assignment ever transferred enforcement rights to a litigating entity.
2. PACER / CourtListener RECAP full-text docket search for "7,522,632" and "7522632."
3. Unified Patents litigation portal and RPX Insight — search by patent number directly.
4. Lex Machina / Docket Navigator — subscriber databases with reliable per-patent litigation linkage.
5. Cross-check the sibling application 09/812,401 (Bright et al.), since related patents are often asserted together.

If you want, give me the go-ahead and I will run a second, narrower pass against those specific databases, or you can search by patent number directly. As of this moment, I have no litigation to report for US 7,522,632, and I will not manufacture one.

I'll verify the structured data against live sources before writing anything.

No hits yet. Let me try a few more targeted angles, including litigation history and the sibling application.

PTAB proceedings on US 7,522,632 — "Multiple-protocol home location register and method of use"

Proceedings overview

Zero AIA trial proceedings on file. The structured USPTO ODP block supplied in this prompt reports no IPR, PGR, or CBM proceeding against US 7,522,632, and my independent web checks (multiple query formulations against PTAB/E2E-indexed sources, docket aggregators, and third-party patent portals) surfaced no petition, no institution decision, no Final Written Decision, and no Federal Circuit appeal arising from a PTAB trial on this patent. Breakdown by status is therefore trivial: 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denied.

Bottom-line defensive posture: there is no invalidating PTAB record to lean on — but there is also no need for one, because the patent is dead on the register: the Google Patents record for US 7,522,632 carries the legal status "Expired - Fee Related" with an adjusted expiration of 2025-02-12. A patent that has lapsed cannot support an ongoing infringement claim. The far more relevant defensive facts here are the expiration and the pre-expiration damages window — not the (nonexistent) PTAB history. Any demand letter citing this patent today should be met with the expiration status first, before validity is even discussed.

---

Proceedings

None. There is no IPR20XX-XXXXX, PGR20XX-XXXXX, or CBM20XX-XXXXX number to report, and I will not manufacture one. For completeness, here is what the record does show, since it is the reason a defendant should not assume the patent is inconsequential:

(No proceeding) — record of activity relevant to a PTAB analysis

• Type: N/A — no AIA trial petition filed.
• Filed: N/A.
• Status: "No PTAB activity on file" (verbatim framing from the canonical ODP structured block). No PTAB panel has ever construed a claim of this patent, and no claim has ever been tested at the Board.
• Judge panel: None — no panel has been assigned.
• Petition grounds: None asserted. Because no IPR was ever filed, there is no § 315(e)(2) estoppel running against anyone, and equally no adjudicated validity finding in the patent owner's favor.
• Institution decision / Final Written Decision / Settlement / Appeal: Not applicable — none exists.
• Defensive value: Neutral-to-favorable for a defendant, but for a non-PTAB reason. The absence of PTAB activity on a 2001-priority telecom-infrastructure patent is unsurprising: the economics of an IPR rarely make sense against a patent with a 2021–2025 expiration horizon, since the statutory one-year trial clock plus appeal would outlast meaningful remaining term. The doctrine that "well-asserted patents eventually attract IPRs" is true, but it does not bite where the patent has aged out before acquiring assertion value.

---

Strategic summary

Claim status: all claims UNTESTED at the PTAB — and all claims EXPIRED. No claim of 7,522,632 has been canceled, sustained, or even instituted upon. There is no narrowing FWD, and therefore no "surviving claim set" to list. What the file does contain is a terminal status: "Expired - Fee Related," adjusted expiration 2025-02-12 (Google Patents legal-status record). One inconsistency a defendant should have counsel resolve against the USPTO PatentCenter maintenance-fee record: a 20-year term measured from the 2001-03-19 filing date would have run to 2021-03-19 absent patent term adjustment, so the 2025-02-12 figure implies either a substantial PTA award or records a lapse/expiration event rather than the raw term end. Either way, the record's own status field says expired, and that is the controlling defensive fact. Separately, the patent was filed 2001-03-19 (App. No. 09/813,016), granted 2009-04-21, and its claims (a receiver/processor/transmitter architecture for a multi-protocol HLR interacting with GSM and ANSI-41 networks, plus SIP/AAA/H.323 wireline servers) sit squarely in the 2014-era Alice crosshairs if it were ever revived for assertion — but that is a § 101 point for a district court, not a PTAB point, and post-SAS the Board does not decide § 101.

Estoppel landscape: empty. Because no IPR, PGR, or CBM ever reached a Final Written Decision, no petitioner is estopped under 35 U.S.C. § 315(e)(1) or § 315(e)(2), and no privies are captured. Conversely, a defendant cannot ride anyone else's estoppel or borrow anyone else's invalidity record. Every § 102/§ 103 ground remains theoretically "available" in the sense that none has been consumed — but this cuts the other way too: there is no free invalidity ruling, no public FWD to cite, and no prior PTAB claim construction to leverage. A defendant facing assertion must build its invalidity case from scratch in district court, or, more realistically, defeat the claim on expiration and damages-window grounds.

Pattern signals: none on this patent. No repeat petitioner, no serial petitions, no General Plastic / Fintra dynamics, no Director Review, no POP referral, and no defensive aggregator (e.g., Unified Patents) in the chain for the '632 patent specifically. One adjacent signal worth flagging with caution: the sibling patent in this family — the commonly-assigned application Ser. No. 09/812,401 by Penny L. Bright et al., identified in the '632 specification as a related application, which issued as US 6,950,876 ("Multiple-protocol home location register and method of use") — appears in third-party records with WSOU Investments, LLC listed in the agent/ownership field. I could not independently confirm a current WSOU ownership chain for the '632 patent itself from the sources I was able to reach, and the '632 record shows Nokia of America Corp as current assignee with Alcatel-Lucent USA Inc. as original assignee (with a 2013 Credit Suisse security interest later released in 2014). Treat the WSOU-family point as a lead to verify, not a finding. Notably, even that monetization activity has not produced a PTAB filing against '632.

---

Recommended next steps

1. No PTAB activity exists — say it plainly, and do not build a defense around an IPR that never happened. There is no FWD to quote and no disposition to link, because no Final Written Decision was ever issued. If opposing counsel or a demand letter implies the patent is "hardened" by surviving PTAB review, that implication is unsupported: the patent was never tested, so its survival is untested, not earned.

2. Lead with expiration. Confirm the maintenance-fee and expiration status in USPTO PatentCenter (https://patents.google.com/patent/US7522632/en records the status as "Expired - Fee Related"; verify against the primary source at https://patentcenter.uspto.gov). Also reconcile the 2025-02-12 adjusted-expiration entry against the 20-year term from the 2001-03-19 filing date. If the patent lapsed for non-payment of maintenance fees, there is no enforceable claim today.

3. Run the damages clock. Even a pre-lapse cause of action is bounded: 35 U.S.C. § 286 caps recovery at six years before suit — as of 2026-09-20, that reach-back begins around 2020-09-20 — and the patent's own term/status may cut that window shorter still. Any demand premised on post-expiration conduct fails at the outset.

4. Preserve the § 101 and § 112 arguments for district court. Because the Board does not adjudicate § 101 and evaluates § 112 only in a narrow PGR window that closed years ago (PGR was unavailable for this 2001-priority patent), the eligibility and written-description attacks on claims directed to routing/registering messages across GSM and ANSI-41 protocols must be litigated in court. There is no PTAB shortcut here.

5. Monitoring hygiene. If a party is nonetheless contemplating a petition (unlikely given expiration), the statutory gates are now tighter than when this patent's IPRs would have been filed: Director Squires' 2025-10-16 memorandum centralizes institution decisions with the Director, and the 2025-10-15/17 proposed rules to 37 C.F.R. § 42.108 would bar institution where a challenged claim previously survived a § 102/§ 103 challenge in any forum. Neither changes the present answer — the '632 record still shows no PTAB activity.

Caveats on sourcing: The canonical proceeding list in the structured block is authoritative and empty. My web verification was search-based and returned no PTAB filings; I was unable to run a direct PTAB E2E / Docket Alarm party-name query within this session, so a recently filed petition that the ODP ingest has not yet indexed cannot be ruled out with absolute certainty. As of the most recent ingest, the answer is no proceedings — and I flag no older or unindexed proceedings that search surfaced.

I'll research the assignment record for US 7522632 using the available sources.

Let me dig deeper into the Provenance Asset Group lead and the full assignment history.

Let me check whether this patent appears in any litigation, and verify its current ownership record.

Assignment & Ownership Analysis — US 7,522,632 B2

Patent: Multiple-protocol home location register and method of use
Application: US 09/813,016 · filed 2001-03-19 · granted 2009-04-21
Priority: 2001-03-19 · Foreign family: EP1244323B1, DE60200415T2, JP4076775B2 (priority claimed 2002-02-22 / 2002-02-28)
Sibling application cited on the face of the patent: Ser. No. 09/812,401, "Multiple-Protocol Home Location Register and Method of Use," Bright et al., filed the same day (2001-03-19)
Legal status shown on Google Patents: Expired – Fee Related; adjusted expiration 2025-02-12

Sourcing caveat up front. Google Patents' legal-events feed records conveyance type, entity names and dates, but does not expose reel/frame numbers. I was unable to retrieve the reel/frame for the Lucent- and Alcatel-Lucent-era recordings, and USPTO Assignment Center's interactive record pages were not reachable in this session. Where I give a reel/frame I give the source; where I do not, I say so rather than reconstruct it. No reel/frame is invented below.

---

Inventors

Unusual patterns observed: none that I can substantiate. All four inventors assigned to the same operating company on the same recorded date, and the patent stayed in that corporate family for its entire life. There is no evidence of all inventors departing the assignee within 12 months of filing, and no evidence of a post-filing inventor-side transfer. I could not verify individual departure dates from primary records — treat that as unclear, not as a negative finding.

---

Original assignee

Lucent Technologies, Inc. (Murray Hill, NJ) is the entity that took the inventors' assignment in 2001; the issued patent front page names Alcatel-Lucent USA Inc., which is the successor of Lucent Technologies by merger (recorded 2009-02-25).

• Line of business: telecom network infrastructure — switching, mobility, optical, and the Bell Labs research organization. US 7,522,632 is squarely core-product subject matter: a multi-protocol Home Location Register (HLR) supporting GSM/ANSI-41 and wireline (SIP/H.323/RADIUS) mobility management. This was intended to be embodied in commercially shipped MSC/HLR products.
• Shipped a product embodying the claims? The specification describes implementation in the assignee's own HLR/GMSC infrastructure, and the surrounding Alcatel-Lucent portfolio was implemented in its switching products. I did not find a specific accused-product mapping for this patent (it appears in no litigation I could locate), so I state this as likely but unverified rather than as a documented product.
• Current status: Lucent Technologies → Alcatel-Lucent USA Inc. (internal merger recorded 2009-02-25) → part of the Nokia group after Nokia's 2016 acquisition of Alcatel-Lucent. Google Patents lists the current assignee as Nokia of America Corp, consistent with the Alcatel-Lucent USA entity operating under the Nokia US holding structure. Nokia is a going-concern operating company; no bankruptcy, no dissolution.
• Patent's own fate: the record shows Expired – Fee Related — the owner stopped paying maintenance fees, i.e., the asset was allowed to lapse. That is inconsistent with a monetization campaign around this specific patent.

---

Assignment timeline

Only the events below are documented. All are internal corporate events or secured-financing recordings — there is no recorded transfer to a licensing vehicle or asserter for this patent.

• 2001-06-27 (recorded) — Reel/frame not surfaced in the sources reviewed

  • Conveyance: ASSIGNMENT OF ASSIGNORS' INTEREST
  • Assignor: Thomas F. La Porta; Kazutaka Murakami; Krishan Kumar Sabnani; Robert Shaw Sellinger
  • Assignee: Lucent Technologies, Inc.
  • Correspondent: not surfaced — Google Patents' legal-events feed does not publish correspondents. No recurrence assessment possible.
  • Context: original employment assignment (inventors → employer), the standard first link.

• 2009-02-25 (recorded) — Reel/frame not surfaced

  • Conveyance: MERGER
  • Assignor: Lucent Technologies Inc.
  • Assignee: Alcatel-Lucent USA Inc.
  • Correspondent: not surfaced
  • Context: internal reorg / corporate name change flowing from the 2006 Alcatel–Lucent combination. Not an arm's-length sale; no change of beneficial owner.

• 2013-03-07 (recorded) — Reel/frame not surfaced

  • Conveyance: SECURITY INTEREST
  • Assignor: Alcatel-Lucent USA Inc.
  • Assignee: Credit Suisse AG
  • Correspondent: not surfaced
  • Context: securitization / collateral — Credit Suisse acting as collateral agent on Alcatel-Lucent's 2013 secured financing. A lien, not a title transfer.

• 2014-10-09 (recorded) — Reel/frame not surfaced

  • Conveyance: RELEASE BY SECURED PARTY
  • Assignor: Credit Suisse AG
  • Assignee: Alcatel-Lucent USA Inc.
  • Correspondent: not surfaced
  • Context: lien release — the 2013 security interest was discharged. Purely a financing housekeeping step.

Cross-referenced but NOT attributable to this patent (important): The large Nokia → Provenance Asset Group LLC portfolio assignment was recorded 2017-09-13 at Reel 043877 / Frame 0001 (assignors: Nokia Technologies Oy, Nokia Solutions and Networks BV, Alcatel Lucent SAS; assignee Provenance Asset Group LLC, 22 West Avenue, Essex, CT 06426; correspondent Dinsmore & Shohl LLP, 1 South Main St., Ste. 1300, Dayton, OH, per the PTAB petition exhibit reproducing the USPTO abstract of title). A related security interest to Cortland Capital Market Services LLC was recorded 2017-09-13 at Reel 043967 / Frame 0001, and a 2019-02-14 Nokia US Holdings security interest appears at Reel 048370 / Frame 0682.

I could not confirm US 7,522,632 was inside the Provenance Exhibit A schedule. Google Patents shows this patent's current assignee as Nokia of America Corp, not Provenance — if the patent had moved in that 4,000-asset US transfer, the assignment data Google renders would normally show Provenance. On the record available, the Provenance/Dinsmoor & Shohl chain does not touch this patent. I flag it only because it is the nearest large Nokia-portfolio transfer and a reader will reasonably ask.

If Assignment Center shows no further records: that is consistent with what I found — no post-2014 ownership-change recording exists for this patent, which means the Alcatel-Lucent USA / Nokia of America entity still owned it through lapse.

---

Timeline diagram

timeline
    title Ownership of US 7522632
    2001 : Filed by Lucent Technologies
         : Inventors assign rights to Lucent
    2009 : Merged into Alcatel-Lucent USA
    2013 : Credit Suisse security interest
    2014 : Security interest released
    2016 : Nokia acquires Alcatel-Lucent
    2025 : Adjusted expiration recorded

---

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
No recorded conveyance to any entity with an IP / Holdings / Licensing / Ventures suffix. The only assignments on record run inventors → Lucent Technologies, Inc. (2001-06-27) and Lucent Technologies Inc. → Alcatel-Lucent USA Inc. (2009-02-25, merger). The assignee never left the Lucent/Alcatel-Lucent/Nokia operating family. The one "Holdings"-style entity in the vicinity — Provenance Asset Group LLC / Provenance Asset Group Holdings LLC at 22 West Avenue, Essex, CT — is tied to Reel 043877/0001 and 043967/0001 and cannot be linked to this patent on the record I retrieved.

2. Known asserter in the chain — NOT PRESENT.
No assignee in this patent's chain matches Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, or Document Generation Corp. Nokia and Alcatel-Lucent are operating companies. Note for completeness: the Provenance vehicle was formed by Dan McCurdy (ex-AST, ex-RPX), Tim Lynch, and Laura Quatela, and IAM reported its stated model as defensive licensing only — "its business model does not include patent assertion." Even if US 7,522,632 had been in that portfolio, that would not by itself be a strong NPE signal. It isn't in it, so the point is moot here.

3. Repeat correspondent across the chain — UNCLEAR / NOT ASSESSABLE.
This is the one signal I genuinely cannot score. Google Patents' legal-events feed does not expose the correspondent of record, and I could not reach the Assignment Center record pages for the 2001, 2009, 2013 and 2014 recordings. I therefore have zero correspondent data points for this patent's own chain, so I cannot test for recurrence either within the chain or against the Dinsmore & Shohl / NPE-assertion correspondent lists. I decline to name a correspondent I did not observe.

4. Cascading transfers — NOT PRESENT.
Four recorded events over 13 years (2001 → 2014), of which two are a lien and its release. No sequence of back-to-back LLC-to-LLC conveyances inside 24 months. No shared registered-agent addresses, no shared principals.

5. Pre-litigation transfer — NOT PRESENT.
I found no infringement action naming US 7,522,632 by any party. With no assertion, there is no pre-suit transfer window to test. The last ownership-affecting recording (2014-10-09) predates any hypothetical suit by years.

6. Bankruptcy fire-sale — NOT PRESENT.
Lucent, Alcatel-Lucent and Nokia are not bankruptcy estates, and no Chapter 7/11 sale of this patent appears on the record. (Alcatel-Lucent's end was a merger into Nokia, not an insolvency; the Credit Suisse lien and its release are ordinary secured financing, not a distressed sale.)

7. Privateering — NOT PRESENT on this patent's record.
No operating-company-to-NPE conveyance is recorded, and no suit is documented. The nearest thematic match — Nokia's mass divestiture of legacy Alcatel-Lucent assets, some of which did reach assertion-oriented buyers such as WSOU Investments LLC (which litigated Alcatel-Lucent-origin patents in W.D. Tex. and had its standing challenged) — does not include this patent on the record I could retrieve.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents or OIN. It terminates at Nokia of America Corp, an operating company, and the patent was simply allowed to lapse for non-payment of maintenance fees.

---

Verdict

Insufficient data.

The recorded chain for US 7,522,632 is nothing but the original employment assignment to Lucent Technologies, Inc. (2001-06-27), an internal merger into Alcatel-Lucent USA Inc. (2009-02-25), and a Credit Suisse security interest with its 2014-10-09 release — i.e., no ownership change to any third party, no licensing vehicle, and no assertion. The patent is now listed to Nokia of America Corp and has been allowed to expire for fee non-payment, which is the opposite of monetization behavior. I could not score the repeat-correspondent signal at all because reel/frame and correspondent fields were unavailable in the sources I could reach.

What would change the verdict: a recorded assignment of this patent into the Nokia → Provenance Asset Group LLC chain (Reel 043877/0001, recorded 2017-09-13, correspondent Dinsmore & Shohl LLP) or into a WSOU-style assertor. Neither is supported by the record retrieved; I found no such recording and Google Patents shows a non-Provenance current assignee. Do not treat this patent as NPE-controlled without pulling the ribbon copy on the reel/frame directly.

Verify at:

• USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search patent number 7522632)
• USPTO Patent Assignment Search (legacy index) — https://assignment.uspto.gov/patent/index.html
• Google Patents legal events — https://patents.google.com/patent/US7522632/en
• Referenced Ptolemy/PTAB exhibit reproducing the Provenance abstract of title — https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1549234](/patent/1549234)/download-documents

Two open items I could not close and am flagging honestly rather than papering over: (a) reel/frame numbers for the 2001, 2009, 2013 and 2014 recordings; (b) the correspondent of record for each. Both require the Assignment Center record pages, which did not render in this session.

I'll search the USPTO database and other authoritative sources for US Patent 7,522,632's cited prior art.

Let me get the front-page "References Cited" data directly from USPTO/FPO sources.

Let me pull the front-page reference list from Justia and the patent PDF image.

Prior-Art Analysis — US 7,522,632 (La Porta et al.)

0. Scope, method, and an important honest limitation

I ran searches against the Google Patents record, FreePatentsOnline, Justia, uspto.report, RPX Insight, and the USPTO/EPO/WIPO family documents, using the literal identifier "7522632."

The single most important caveat for this section: I was not able to retrieve the face-of-patent "(56) References Cited" list for US 7,522,632 in these searches. The search tool returns snippets, not the patent's front page, and none of the indexed mirrors returned the examiner's cited U.S. patent documents or foreign patent documents for this specific patent. I therefore will not present a fabricated (56) table. Below I give (a) what I did verify, (b) the prior-art references that are documented in this patent's family record, and (c) a clearly-labelled § 102 analysis of those, plus the direct verification path for the full list.

Date discrepancy to flag (per your operating rules): the current task header says April 26, 2026, while the fetched patent record is timestamped 2026-09-17 and the earlier generated sections used 2026-09-20. I'm not silently reconciling these; for a 2001-filed / 2009-granted / now-expired patent the discrepancy does not change the prior-art analysis (all prior art dates are fixed), but it does matter for any "as-of-today" statements. I treat April 26, 2026 as the stated date and note that no 2026 enforcement activity was found in the earlier sections, consistent with the expired status.

---

1. Status update on previously generated sections (not a contradiction — a refinement)

The earlier Patent summary said the authoritative text supplied did not include the claims section and gave a "moderately confident" claim-1 reconstruction. I was able to retrieve reproduced granted claim text this session (RPX Insight, insight.rpxcorp.com/patent/US7522632B2). This confirms the earlier reconstruction rather than contradicting it:

• Claim 1 (apparatus) — confirmed: receiver; processor using "a common source of data and common control procedures"; transmitter; a standalone HLR for each wireless network; a server for each wireline network; the processor comprising a provisioning gateway to distribute user data between the standalone HLR and server; and a mediation device coupled to the provisioning gateway, standalone HLR, and server, "configured to one or more of generate network messages, translate network messages, and emulate one or more of gateway mobile switching centers, visited mobile switching centers, and message centers." — i.e., the earlier description of claim 1 as the FIG. 4 (mediation-device) embodiment is correct.
• Additional independent claims confirmed: claim 3, claim 5, and claim 16 are all method claims (claim 3 = receive/process via provisioning gateway/interpret/generate common command; claim 5 = first standalone HLR receives first-protocol message, mediation device generates a command from the common command set; claim 16 = receive via first standalone HLR, process per procedure common to HLR + mediation device + provisioning gateway, generate/relay database query).
• Claim count = 20 — confirmed, matching the earlier summary.

So the earlier "moderate confidence" caveat can be upgraded for claims 1, 3, 5, 16. The exact wording of the remaining dependent claims (2, 4, 6–15, 17–20) remains unverified.

---

2. What I verified about the reference/citation record

Critical distinction I must not blur: the two WO references appear in the German-language document DE 60210855 T2, whose summary text uses the receiver/processor/transmitter formulation. That formulation matches this patent's summary. However, DE 60210855 T2 is not in the DE/EP family members listed for 7,522,632 (those list DE 60200415 T2 and EP 1244323 B1). It is most likely the German translation belonging to the sibling Bright et al. application — but I could not verify that mapping this session. I therefore treat WO 00/79827 and WO 00/74409 as documented background art in the immediate family, and flag their attribution to 7,522,632's own specification as unconfirmed. Note also that the 7,522,632 specification you supplied contains no citation of any WO reference in its Background.

---

3. Relevant prior art identified, with § 102 analysis

Legal framework (correct for this patent): filed 2001-03-19, i.e., pre-AIA. Pre-AIA 35 U.S.C. § 102(a), (b), (e) and § 103 govern. Relevant critical date: one year before filing = 2000-03-19 for § 102(b) statutory bars.

§ 102(e) note

Both WO references are PCT publications. Pre-AIA § 102(e) reaches U.S. patents and U.S. published applications (and, under the 1999 AIPA amendments, certain international applications designating the U.S. that were published in English). Whether WO 00/79827 or WO 00/74409 qualifies under § 102(e) depends on their designating the U.S., entering the national stage, and language of publication — none of which I verified. Treat them as § 102(a) art unless a § 102(e) qualification is confirmed.

---

4. Forward citations (NOT prior art — included to prevent misattribution)

These are documents that cite 7,522,632, so they cannot be prior art against it:

• US 7,844,270 B2 — "Call transfer for an integrated wireline and wireless service using a temporary directory number" (Nortel Networks), granted 2010-11-30. Lists 7,522,632 in its "Referenced Cited" section.
• The long "Patent Citations (50)" list I encountered (US 5,260,988, US 5,579,375, US 5,722,068, US 5,920,815, US 6,181,938, US 6,424,647, US 6,103,479, etc.) belongs to the Nortel document's own front page — not to 7,522,632. I am explicitly flagging this because those numbers are easy to mis-assign to this patent.

---

5. Why I could not complete the assignment as literally specified

You asked me to "look at each patent citation for 7522632." Doing that literally requires the front page / (56) block of the granted patent, which the available sources did not surface. Specifically:

• Google Patents' rendered text for US7522632 does not expose the "(56) References Cited" block in the snippets returned.
• FreePatentsOnline's 7522632 page returned the description/claims text but not the reference list.
• uspto.report and RPX Insight returned bibliographic, abstract, and claim text but not the (56) list.
• The JP family member (JP 2004076775 B2 / JP2002330179A5) snippets returned forward citing documents (2001-2004 era), which are not the (56) art.

Verification path (definitive):

1. USPTO PatentCenter → Application 09/813,016 → "References Cited" / IFW documents, for the examiner's cited art and any IDS.
2. Patent PDF front page (patentimages.storage.googleapis.com/.../US7522632.pdf, page 1) for the printed (56) list.
3. EP 1244323 B1 / DE 60200415 T2 search report, which typically reproduces the same art set from the common international search.
4. Cross-check the sibling Ser. No. 09/812,401 (Bright et al.) — related applications are often examined against the same references.

If you can paste the front page or the (56) block, I will map each reference to the specific claims (1, 3, 5, 16 and the dependents) with element-by-element § 102/§ 103 reasoning. Until then, the honest answer is: the only prior art I can substantiate as tied to this patent's family is WO 00/79827 A1 and WO 00/74409 A1, and I will not invent the remainder of the citation list.

I'll research the prior art landscape for this patent, since the fetched page text omitted the citations/"Prior Art" reference list and only preserved the keyword set (network, hlr, protocol, message, location register).

Let me chase the actual cited prior-art list (the "References Cited" section that the fetch dropped) and identify the pre-2001 interworking art in this space.

I found the sibling patent's cited-reference list (the shared-spec sibling), which is highly probative. Let me try once more to pin the reference list that actually belongs to US 7,522,632 itself.

Obviousness Analysis — U.S. Patent No. 7,522,632 B2 under 35 U.S.C. § 103

Date of analysis: April 26, 2026

---

0. Evidence caveat — read first

The task instructs me to "use the results from the Prior Art section of this page." The fetched page text for US 7,522,632 did not preserve that section's substantive content. What survived is only the machine-extracted keyword set:

Prior art keywords: network; hlr; protocol; message; location register

The fetched text also omits the claims themselves (the Google Patents page supplies [Description] and [Abstract] but the claims block was not captured), and it omitted the "References Cited" / "Citations" list. So:

• I am building the prior-art universe from (a) the keyword set above, (b) the cited-reference list I was able to retrieve for the same-specification sibling application, and (c) the GSM/ANSI-41 interworking standards and the specification's own admissions.
• Provenance flag: the reference list I retrieved (Section 2.2) is the "Referenced Cited" list of US 6,950,876 B2 (Bright et al.), filed the same day (2001-03-19) on the same specification as US 7,522,632. I could not independently confirm that US 7,522,632's own reference list is identical. Treat it as a strong proxy, not a verified identity.
• Claim language below is taken from the sibling's granted text, the JP family member (JP 4076775 B2 / JP 2002330179 A, which lists 40 claims), and the earlier summary for this patent. Claim numbering for US 7,522,632 is not verified. Flagged where it matters.

If any of these are wrong, the analysis should be re-run against the USPTO PatentCenter PDF.

---

1. Governing law and the level of ordinary skill

• § 103 framework: Graham v. John Deere, 383 U.S. 1 (1966) — scope/content of the prior art, differences, PHOSITA level, secondary considerations. Pre-AIA § 103 applies (effective filing date 2001-03-19, well before 2013-03-16), though the analysis is materially the same.
• KSR Int'l v. Teleflex, 550 U.S. 398 (2007): a combination of known elements is obvious where the improvement is "a predictable use of prior art elements according to their established functions"; the "motivation" may be a design incentive, market pressure, or the mere existence of a finite number of identified, predictable solutions. KSR also endorses reasoning from the patentee's own admissions about the state of the art — which are unusually rich here (Section 2.3).
• POSITA (proposed): a telecommunications engineer with a B.S.E.E./C.S. and 3–5 years' experience in SS7/mobility signaling (IS-41/ANSI-41, GSM MAP), intelligent networks, and location-register design, familiar with TIA and ETSI/3GPP interworking standards. This is a mature, heavily standardized art — a fact that cuts strongly toward obviousness, because the "solution space" was being written down by standards bodies during the 1990s.

---

2. The prior art

2.1 The keyword set as a description of the art

The five keywords — network, hlr, protocol, message, location register — are themselves a fair summary of the field the claims occupy: a home location register that processes messages in multiple protocols across a network. This is the pre-existing art, not the invention.

2.2 Cited references (retrieved from the shared-spec sibling US 6,950,876 B2)

Timing caveat: several of these (US 6,353,620; 6,353,621; 6,611,533; 6,658,011; 6,738,803; 6,741,853; 6,256,497) issued after the 2001-03-19 filing date. They can qualify as prior art only under pre-AIA § 102(e), and only if their effective filing dates precede 2001-03-19 and they are "by another." Their § 102(e) status needs to be checked before being relied on. The safe core of the prior-art universe is the pre-2001 set: Gallagher '784, Urs '204, Karmi '157, Lopez-Torres '759, Joensuu '788, Pfundstein '067, Chan '445, Henry '215, Gessel '213, Nguyen '407, Kay '873, Roach '401, and the standards documents below.

2.3 Standards documents and the patentee's own admissions (the strongest § 103 evidence)

The sibling's cited non-patent literature includes:

• "Interworking/Interoperability Between DCS 1900 and IS-41 Based MAPs for 1800 MHz Personal Communications Systems — Phase I," IS-129 (Nortel, Jul. 1996).
• "Network Interworking between GSM MAP and ANSI-41 MAP," PN-4857, vol. 0, Overview Network Reference Model (Ballot Version, Dec.).

These are TIA/standards-body documents that define the GSM-MAP ↔ ANSI-41 message mappings. Critically, the specification's TABLE 1 — the translation table the patent presents as its own mechanism — is an implementer's restatement of precisely these mappings (e.g., GSM Provide Roaming Number ↔ ANSI Location Request; GSM Send Routing Information ↔ ANSI Routing Request; GSM Update Location ↔ ANSI Registration Notification). A reference that teaches the mapping table teaches the claimed "processing… utilizing a common source of data and common control procedures."

Equally important, the specification admits away most of the claim elements as known art — usable under In re Fout / KSR:

1. "In many wireless communication systems, HLRs and VLRs are used to handle mobility management."
2. "Mobile data communication systems utilize network servers called home agents and foreign agents to provide analogous functions to HLRs and VLRs."
3. "Wireline communication systems utilize functions such as authentication, service provisioning, user profile management, user location management, and service invocation."
4. The mediation device is described as "acting as an IIF (Interworking and Interoperability Function)" — i.e., the applicant concedes IIFs (interworking functions) pre-existed.
5. "Currently, various data is scattered between somewhat separate components of the network, such as the HLR, SCP, and AAA" — conceding the consolidation problem and, implicitly, the desirability of consolidation.
6. "Although ANSI systems communicate with an SCP at the terminating MSC, and GSM systems communicate with an SCP at the (originating) GMSC…" — conceding the network topologies of FIGS. 10–14.
7. FIG. 9 is expressly labeled "as known in the art."
8. The patent frames its own contribution as "more efficient than an Interoperability Interworking Function (IIF)" — an express admission that the IIF architecture was the prior art baseline.

Under KSR, once the problem (mobility management across multiple protocols) and the components (HLRs, VLRs, home/foreign agents, IIFs, protocol translation, shared profile data) are conceded as known, the remaining question is whether the particular arrangement was a predictable variation.

---

3. What the claims require (the elements that carry the § 103 weight)

From the sibling's granted claims, the JP family claims, and the earlier summary, the load-bearing limitations are:

---

4. Combinations that render the claims obvious, with motivations

Combination A — Chambers '497 + Gallagher '784 + Urs '204 (attacks E1–E5, E9–E11)

Teachings: Chambers '497 discloses the complete functional core — an interworking function unit containing an interworking HLR that (i) is reachable by a subscriber of a network of a different standard, (ii) maintains location and permitted-service records in a common interworking register, and (iii) hands service data to the visited network's VLR so a call can be routed through the second network. Gallagher '784 supplies the protocol-translating signaling gateway (terminate protocol 1 → interpret → emit protocol 2), which is structurally the claimed "protocol gateway." Urs '204 supplies a distributed location register whose subscriber data is shared across nodes — the claimed "common source of data."

Motivation to combine (KSR):

• Chambers solves exactly the problem the patent states: "mobility management for users between multiple systems utilizing different protocols." A POSITA seeking to serve dual-mode roamers would start here.
• Placing Gallagher's translating gateway at Chambers' interworking unit is the natural, predictable way to let one interworking register serve more than two protocols instead of building a bespoke IWF for every network pair — the very scaling problem the standards literature (IS-129, PN-4857) was addressing.
• Urs' shared register eliminates the duplicate-profile synchronization problem the patent's specification itself identifies (data "scattered between… HLR, SCP, and AAA"). KSR: combining references to address a recognized deficiency in the primary reference is a paradigm motivation.
• Predictable result: terminate each protocol at its own gateway; convert to a common operation; query one shared database; convert back. No new physical result; a classic layered-abstraction arrangement.

Claim mapping: E1 = Chambers' interworking unit receiving the registration/routing message; E2 = Chambers' interworking HLR record + Gallagher's common interpretive step + Urs' shared data store; E3 = Chambers' provision of data back to the VLR; E4/E5 = Gallagher's gateway (PG) plus a web/CORBA provisioning front end (the specification admits CORBA and web provisioning AGs are conventional); E9/E10 = Chambers' routing of a call into the second network with second-network-formatted service data; E11 = the query→translate→route sequence.

Combination B — GSM/ANSI-41 interworking standards (IS-129; PN-4857) + Boland '621 + Karmi '157 (attacks E2, E9, E12, and the "native/foreign mode" claims)

Teachings: IS-129 and PN-4857 define the message-by-message map between GSM MAP and ANSI-41 MAP — i.e., the common control procedures that convert one protocol's operation into another's. Boland '621 teaches serving a mobile across MSCs supporting multiple intersystem standards. Karmi '157 teaches a single MSC serving multiple service providers.

Motivation: The patent's TABLE 1 is the standard interworking map. A POSITA implementing a multi-protocol HLR in 2000–2001 would not invent a new conversion scheme; they would implement the published TIA/Ballot-version mappings. KSR: "a finite number of identified, predictable solutions" — the standard supplied the solution. Boland and Karmi supply the deployment motivation (carriers operating GSM and ANSI-136/41 footprints, dual-mode handsets) and the architectural teaching (one node serving multiple standards). The specification's own FIG. 5/6 native-mode registration flows are the direct application of IS-129/PN-4857 to registration.

Combination C — Chambers '497 + Joensuu '788 + Pfundstein '067 + the admitted IIF (attacks E6, E7, E8 — the "mediation device" family)

Teachings: Chambers' interworking unit sits in front of the networks' own registers. Joensuu '788 teaches converting a routing address — the mechanism by which the mediation device inserts itself as the "MSC ID" (FIGS. 7, 16, 17: "a location request with the GMSC ID equal to the mediation device (MD)"). Pfundstein '067/'920 teaches a centralized subscriber-data repository with a provisioning front-end. The specification itself concedes the mediation device is "acting as an IIF."

Motivation: If the goal is to interwork without modifying the installed standard HLRs — a stated advantage in this family (the sibling claims recite "without a requirement for any modification to the first standard HLR and/or the second standard HLR") — the obvious implementation is to place a translating, address-substituting node between two unmodified HLRs. That is precisely Chambers + Joensuu. The provision of a provisioning gateway for distributing user data is ordinary network-management administration (and the specification concedes CORBA/web provisioning interfaces are conventional); adding it is a predictable administrative convenience for the operator who now maintains one profile.

Counter-consideration: This combination is the patentee's best non-obviousness argument, because "emulating GMSCs, VMSCs, and MCs by inserting the mediation device's own identifier as the MSC ID" is a fairly specific mechanism, and one could argue the cited art teaches address conversion but not identity emulation of three distinct node classes. Expect the patentee to press here.

Combination D — Urs '204 / Liao '533 / Pfundstein '067 + HLR/SCP/AAA convergence (attacks E7, E10, and the IP/wireline legs)

Teachings: Liao '533 teaches PSTN/IN/IP services interworking; Urs '204 teaches the shared register; Pfundstein '067 teaches centralized subscriber data.

Motivation: The specification concedes the exact deficiency: "Currently, various data is scattered between somewhat separate components of the network, such as the HLR, SCP, and AAA. The MP HLR 101 promotes the simplification and consolidation…" Consolidating scattered databases into one is a recognized, predictable engineering objective; KSR treats "a known technique applied to a known structure" as obvious. Cost pressure (the patent's own "savings gained from synchronizing and updating one HLR instead of many HLRs") is an articulated market motivation.

Combination E — standard GSM/ANSI SMS interworking + the admitted IIF (attacks E12)

The specification states that for cross-protocol SMS, "a mediation device acting as an IIF (Interworking and Interoperability Function) is used to convert the message to the other protocol" — an express admission of prior art. The dependent SMS/MWN claims therefore reduce to the admitted IIF plus the standard FSM (GSM) and SMDPP (ANSI) message flows, which are public standard messages. Maximal one conversion regardless of originating/terminating protocol is a predictable optimization of the known IIF placement, not a new mechanism.

---

5. Consolidated element-by-element summary

---

6. Anticipated rebuttals and secondary considerations

For the patentee:

1. No single reference teaches all elements. True — the case is a combination case, and the patentee will argue improper hindsight. The KSR answer: the motivation comes from the pre-existing problem statement (standards work on GSM/ANSI-41 interworking and the admitted IIF), not from the patent.
2. E8 (emulating GMSC/VMSC/MC) is the point of novelty. The strongest position. The response is that Joensuu '788 teaches address conversion/substitution and the IIF standard teaches masquerading as a visited node.
3. "Without modifying the standard HLRs" is emphasized in the family. Under KSR, a known interposition technique applied to a known architecture is still obvious unless it produces an unexpected result — and the stated benefit (no HLR modification) is a predictable consequence of interposition, not an unexpected one.

Secondary considerations: I found no evidence of commercial success, copying, industry praise, or long-felt unmet need tied to this patent, and — consistent with the earlier litigation section — no identified litigation or licensing campaign that would supply a nexus to secondary considerations. The patent is listed Expired – Fee Related (adjusted expiration 2025-02-12), and the absence of any identified assertion history is at least consistent with the claims being regarded as difficult to enforce over this art. Absent such evidence, secondary considerations do not rebut the § 103 case.

Same-day sibling / double-patenting note: US 6,950,876 B2 (Bright et al.) shares the same specification and same 2001-03-19 filing date as US 7,522,632. It is therefore best characterized as a co-pending sibling raising obviousness-type double patenting (ODP) concerns, not as § 102/§ 103 prior art. The claim-count asymmetry (7,522,632 at 20 claims vs. 6,950,876 at 71) suggests the two applications were divided by restriction/election, with the apparatus family landing in 7,522,632. I could not verify the prosecution history, so the reason for the split is inferred.

---

7. Bottom line

On the record available, the independent claims of US 7,522,632 are, more likely than not, obvious under § 103 over a small number of combinations:

• Primary combination: US 6,256,497 (Chambers) + US 5,933,784 (Gallagher) + US 6,148,204 (Urs), optionally plus US 6,353,621 (Boland) and US 5,884,157 (Karmi) — motivated by the standardized GSM/ANSI-41 interworking problem (IS-129, PN-4857) that the patent's own TABLE 1 restates.
• Strongest supporting evidence is the patentee's own specification, which concedes HLRs, VLRs, home/foreign agents, IIFs, provisioning interfaces, and the scattered-data problem as pre-existing.
• Greatest vulnerability of the § 103 case is element E8 (mediation device emulating GMSC/VMSC/MC by inserting itself as the MSC ID); a well-briefed petitioner should pair Joensuu '788 or the IIF standards with an explicit teaching of node-identity emulation, or the patentee may salvage the FIG. 4 claims.

Verification steps required before this is filing-grade: (i) pull US 7,522,632's actual "References Cited" list from the USPTO PatentCenter / IFW PDF (the fetched page lost it); (ii) confirm the granted claim text and numbering for the 20 claims; (iii) confirm the § 102(e) effective filing dates of the post-2001-issued references (6,353,620; 6,353,621; 6,611,533; 6,658,011; 6,738,803; 6,741,853; 6,256,497) before relying on them; and (iv) obtain the prosecution history to see whether any of these were already applied and overcome, which would materially change the recommendation.