MLC API Exposure Function

Provide Subscriber Location, Anytime Interrogation and Send Routing Info For Location are exposed from a single node. An application resolves exact coordinates through the network's SMLC when one exists, falls back to last-known Cell ID when it doesn't, or simply resolves the serving node address and IMSI behind an MSISDN — without three separate integrations.

A configurable SCCP routing table — global titles, point codes, subsystem numbers, and solitary, dominant or load-sharing rules — lets one MLC-AEF instance reach several mobile networks at once and route each location query to the right one.

Service state, SCTP link state, M3UA peer state and overload threshold breaches are reported as SNMP traps, alongside a CDR stream per location transaction (dialog, invoke ID, MSISDN, IMSI, duration, response outcome). Positioning traffic is observable through the same tooling as the rest of the signalling estate.

The same Provide Subscriber Location, Anytime Interrogation and Send Routing Info For Location APIs serve a subscriber whether the network resolves them over MAP toward an HLR/MSC (2G/3G), Diameter SLg/SLh toward an MME/HSS (4G), or Namf_Location/Nlmf_Location toward an AMF/LMF (5G). MLC-AEF resolves the difference beneath the API, so an application integrated once keeps working as the subscriber — or the network itself — moves between generations.

MLC-AEF's configuration includes a CAPIF binding — a Core Function URL and a cyclic publishing interval — so the same three location APIs can be onboarded, authorized and routed through the Common API Framework when the operator chooses to expose them beyond its own network.