MAP Purge MS and HLR VLR Coordination in Mobile Networks
Mobile networks must keep subscriber location data accurate as devices move between coverage areas, switch between radio technologies, or disappear from the network for extended periods. In GSM and legacy 2G/3G core networks, the Home Location Register (HLR) and Visitor Location Register (VLR) rely on MAP signalling to maintain this state.
The MAP Purge MS operation is used when a VLR removes a mobile subscriber’s temporary record. It tells the HLR that the subscriber is no longer considered present in that VLR. This prevents the home database from treating stale visitor data as a reliable indication of current reachability.
The procedure is especially relevant to SMS delivery, mobile-terminated calls, roaming, and network recovery. A handset may be switched off, move out of service, lose a temporary registration, or be cleared from a VLR after an administrative or capacity event.
Although Australian operators have largely moved towards 4G and 5G packet cores, MAP remains important in interworking, roaming, legacy voice, SMS infrastructure, and signalling security analysis. Engineers working with mixed networks still need to understand how Purge MS affects subscriber state.
The Purpose Of MAP Purge MS
A VLR stores temporary information for subscribers currently associated with the attached Mobile Switching Centre (MSC). This can include the International Mobile Subscriber Identity, temporary mobile subscriber identity, service permissions, authentication parameters, and location-area information. When the VLR deletes that context, it should inform the HLR through PurgeMS.
The HLR then updates its subscriber status to show that the mobile station has been purged from the serving VLR. The HLR may retain identifying information about the last VLR, depending on implementation and the subscriber’s wider state, but it must no longer assume that the VLR can page or serve the handset normally.
PurgeMS is different from normal location updating. A location update establishes a new serving relationship, while PurgeMS reports the removal of an existing temporary relationship. If the device later registers again, the VLR generally obtains subscriber data through an update location procedure and the HLR restores an active serving context.
How HLR And VLR State Changes
The signalling sequence usually begins inside the VLR or MSC platform. After deciding that a subscriber record has been removed, the VLR sends a MAP PurgeMS invoke message towards the HLR. The message identifies the subscriber and may include information associated with the serving node and supported network features.
The HLR validates the request, changes the subscriber’s purge status, and returns a result or error. Successful processing does not mean that the handset has become unreachable forever. It means the HLR has received a specific indication that the previous VLR context should no longer be used as an active location.
When the subscriber reconnects, the handset performs registration procedures and the VLR sends UpdateLocation to the HLR. The HLR can then cancel the old location, transfer the subscriber profile, and mark the new VLR as current. Timing differences between these operations can create short-lived inconsistencies, especially during MSC restarts or signalling congestion.
Effects On Calls, SMS And Roaming
For a mobile-terminated call, the HLR may need to obtain routing information from the serving MSC before the call can be delivered. If the subscriber is marked as purged, the network may return an absent-subscriber or temporarily unreachable result rather than attempting to page through an obsolete VLR.
SMS handling can expose the effect more clearly. The SMS gateway may query the HLR for routing information, and the HLR’s purge state can influence whether the message is forwarded immediately, held for later delivery, or rejected with a temporary failure. Exact behaviour depends on MAP version, operator policy, retry timers, and SMS service-centre configuration.
Roaming adds another layer. A subscriber visiting an overseas network may be purged when the visited VLR loses its context. The home HLR must avoid sending traffic to a stale roaming address while still allowing a fresh registration to replace it. Australian travellers moving between domestic and international networks can therefore encounter behaviour shaped by both home-network policy and the visited operator’s MAP implementation.
Routing, Timers And Signalling Visibility
PurgeMS depends on correct SCCP addressing, global title translation, and routing through signalling transfer points or SIGTRAN signalling gateways. A message can be syntactically valid yet fail operationally if the destination point code, subsystem number, or translated global title is incorrect. The principles explained in STP routing labels help engineers trace this path.
Timers matter because the HLR and VLR must reach a consistent outcome even when a response is delayed. Repeated PurgeMS requests may occur after retransmission, while an expired transaction can leave monitoring systems showing an apparent mismatch. Trace analysis should correlate the invoke, return result, dialogue identifiers, SCCP addresses, and the subsequent UpdateLocation exchange.
In Australia, long travel distances and patchy coverage across regional Queensland, Western Australia, and the Northern Territory can produce frequent registration changes. Urban movement between Sydney, Melbourne, Brisbane, and underground transport environments creates a different pattern, with dense handovers and short periods of radio loss. These conditions make timestamps, retry windows, and subscriber-state alarms valuable when investigating intermittent failures.
Operational Checks For Australian Networks
Operators and private mobile networks should treat PurgeMS as part of a wider state-management process rather than an isolated MAP message. The relevant evidence includes HLR records, VLR activity, MSC logs, SMS gateway responses, roaming transactions, and SIGTRAN transport health.
Australian services must also account for number portability and regulatory obligations administered through the national communications framework. A ported mobile number still requires correct subscriber and routing treatment, while emergency calling arrangements, including access to 000, demand careful separation between ordinary subscriber reachability and emergency-service handling.
Everyday usage patterns add practical complexity. Prepaid customers may leave phones switched off for long periods, while commuters may move repeatedly between Wi-Fi calling, cellular coverage, and congested metropolitan cells. Operators such as Telstra, Optus, and Vodafone may implement different legacy-core policies, so test results should never be generalised from one network without checking vendor and interconnect behaviour.
Recommended Diagnostic Practices
- Correlate PurgeMS with the VLR deletion event and the next UpdateLocation.
- Check SCCP global title translation, point codes, subsystem numbers, and SIGTRAN associations.
- Review HLR, MSC, VLR, and SMSC timers for inconsistent retry behaviour.
- Separate genuine subscriber absence from transport loss, routing failure, and database errors.
- Test domestic roaming, international roaming, prepaid expiry, and long radio-off periods.
- Monitor absent-subscriber responses for unusual spikes after software or configuration changes.
| Network Event | HLR State | VLR State | Likely Service Effect |
|---|---|---|---|
| Normal registration | Subscriber linked to current VLR | Active temporary record | Calls and SMS can be routed |
| PurgeMS accepted | Subscriber marked purged | Record removed or inactive | Delivery may be deferred or rejected |
| Delayed PurgeMS | Old VLR may remain recorded | Context already missing | Temporary routing inconsistency |
| New UpdateLocation | New VLR becomes current | Fresh subscriber context | Normal service can resume |
| Failed MAP transaction | State may remain stale | Local state may differ | Calls, SMS, or roaming can fail |
The essential point is that MAP Purge MS keeps the HLR from trusting a VLR record that has already disappeared. Reliable coordination depends on accurate signalling routes, compatible timers, clear database state transitions, and testing that reflects both Australia’s dense cities and its wide regional coverage.
