MAP Delete Subscriber Data in Roaming HLR Updates
When a mobile subscriber roams, the Home Location Register (HLR) must keep the visitor’s serving network aligned with the current subscription profile. MAP Delete Subscriber Data is one of the operations used to remove information that is no longer valid in a VLR or SGSN.
The procedure sits within the wider SS7 and SIGTRAN signalling environment. It can affect call handling, SMS delivery, packet data access, supplementary services, and CAMEL-based charging. It is therefore important to read the message as part of a transaction flow rather than as an isolated MAP packet.
For Australian operators, this matters across large LTE and 5G footprints, regional coverage areas, and inbound roaming arrangements involving Telstra, Optus, Vodafone, and overseas partners. A clean subscriber-data update helps prevent stale permissions from remaining active when a customer moves between networks or changes service status.
Why Delete Subscriber Data Exists
The HLR is the authoritative source for a subscriber’s permanent service data, while the VLR or SGSN stores a working copy for the current location. When that working copy must be withdrawn, the HLR sends a MAP DeleteSubscriberData operation to the relevant serving node.
Deletion may apply to selected categories rather than the entire subscriber record. Examples include a teleservice, bearer service, roaming restriction, GPRS subscription, or CAMEL subscription information. The exact contents depend on the MAP version, operator implementation, and the capabilities advertised by the destination network.
This distinction is useful in troubleshooting. A Delete Subscriber Data message does not automatically mean that the subscriber is being disconnected. It may simply remove one obsolete service attribute while other voice, SMS, or data permissions remain intact. Engineers studying the wider protocol stack can use these SS7 learning resources to relate MAP procedures to network architecture.
How the Roaming Sequence Works
A common roaming scenario begins when a handset registers in a new location area. The serving VLR sends MAP UpdateLocation to the HLR, normally carrying the subscriber’s IMSI and the VLR address. The HLR then identifies the previous serving node and sends CancelLocation to remove the old temporary registration.
The HLR follows this with InsertSubscriberData, transferring the current service profile to the new VLR. If data previously held by that VLR is no longer authorised, the HLR can send DeleteSubscriberData to withdraw specific parts of the profile. The VLR returns a result or error component, and the MAP dialogue is closed when the transaction is complete.
This flow is especially relevant when a subscriber changes between domestic and international roaming contexts. An Australian customer moving from metropolitan Sydney to a regional area usually remains on the same home network, but an inbound visitor from New Zealand, Singapore, or the United Kingdom may trigger different inter-operator signalling and commercial controls.
Message Content And Transport
DeleteSubscriberData is transported through the MAP layer over the signalling stack. In traditional networks, that stack commonly includes SCCP and MTP3 over SS7 links. In modern deployments, SIGTRAN protocols such as SCTP and M3UA carry the signalling across IP networks while preserving the higher-layer MAP logic.
The operation identifies the subscriber and includes the categories or parameters to be removed. Depending on the implementation, the message may carry information related to basic services, supplementary services, packet-domain subscriptions, charging triggers, or network-specific data. The return result confirms successful processing, while errors can indicate unknown subscriber, facility not supported, unexpected data value, or system failure.
Transport analysis must account for routing and addressing. Global Title Translation may determine which signalling point receives the message, while SCCP subsystem numbers identify MAP applications such as the HLR or VLR. A useful reference for the lower signalling layer is this MTP3 message guide, which explains how message types support SS7 delivery.
Related MAP Operations Compared
Several MAP procedures can appear close together in a trace, but they have different purposes. InsertSubscriberData adds or refreshes the profile in a serving node. DeleteSubscriberData removes selected profile elements. CancelLocation removes the serving registration itself, while PurgeMS confirms that a subscriber is no longer reachable in a location register.
| MAP operation | Main purpose | Typical direction | Effect on serving data |
|---|---|---|---|
| UpdateLocation | Register the subscriber in a new VLR or SGSN | VLR/SGSN to HLR | Starts location update processing |
| CancelLocation | End an old location registration | HLR to VLR/SGSN | Removes the old registration |
| InsertSubscriberData | Load or refresh authorised services | HLR to VLR/SGSN | Adds or replaces profile data |
| DeleteSubscriberData | Withdraw selected services or attributes | HLR to VLR/SGSN | Removes specified profile elements |
| PurgeMS | Report that the mobile is no longer reachable | VLR to HLR | Marks location data as purged |
The order is not identical in every vendor implementation. Some systems issue deletion as part of a profile change, while others rely on a complete replacement of subscriber data. Packet captures should therefore be interpreted using dialogue identifiers, invoke IDs, timestamps, and the surrounding MAP operations.
Checks For Australian Roaming Deployments
A practical trace review should correlate signalling with subscriber and commercial records. In Australia, long distances between capital cities and regional coverage zones can expose timing, retry, and fallback behaviour that is less visible in dense urban testing around Melbourne or Brisbane.
Useful checks include:
- Confirm the IMSI, VLR or SGSN address, and MAP dialogue identifiers.
- Compare DeleteSubscriberData with the preceding profile-change event.
- Verify that SCCP routing and Global Title Translation select the intended node.
- Check whether the visited network supports the requested data category.
Operators should also examine how legacy 2G or 3G dependencies interact with current LTE and 5G services. Although voice over LTE reduces reliance on older circuit-switched paths, roaming partners may still use different interworking models. A stale service flag can affect SMS, voice fallback, or data access even when the radio network appears healthy.
Failures, Security, And Practical Takeaways
When deletion fails, the subscriber may retain an outdated entitlement or the serving node may keep requesting data that the HLR no longer supports. Analysts should separate protocol failure from policy failure: an absent service may reflect a valid commercial restriction rather than a signalling fault. Governance is also relevant, particularly where configuration changes or privileged access could create an undue advantage guidance concern.
Common warning signs include:
- A successful UpdateLocation followed by rejected subscriber-data operations.
- Repeated DeleteSubscriberData messages with no matching result.
- Mismatched MAP versions or unsupported optional parameters.
- A VLR profile that differs from the HLR after the dialogue closes.
The most reliable method is to follow the complete transaction: identify the serving node, inspect CancelLocation and InsertSubscriberData, decode the deletion categories, and verify the returned result. For Australian roaming environments, add partner-specific routing, long-haul signalling latency, and service-policy differences to that analysis.
The key point is simple: MAP Delete Subscriber Data is a targeted profile-clean-up mechanism within HLR roaming management. It removes obsolete service information from the serving network; it does not, by itself, represent a full subscriber deregistration.
