MAP Cancel Location And Roaming Number Retrieval In SS7
Mobile roaming depends on accurate location data inside the home location register (HLR) and the visitor location register (VLR). When a subscriber moves between serving MSC areas, MAP messages update the network so that incoming calls can be directed to the correct visited network.
MAP Cancel Location is part of that mobility-control process. It removes an outdated subscriber record from a previous VLR, while Provide Roaming Number (PRN) obtains a temporary mobile station roaming number (MSRN) for an incoming call.
For Australian operators and international roamers moving between networks in Sydney, Perth, or regional Queensland, the sequence must remain reliable across long signalling paths. A failure may leave a stale VLR entry, delay call delivery, or produce an absent-subscriber response even when the handset is switched on.
Where Cancel Location Fits
When a mobile subscriber performs a location update in a new MSC/VLR area, the new VLR informs the HLR of the change. The HLR then sends MAP_CANCEL_LOCATION to the old VLR, identifying the subscriber with an IMSI and specifying the cancellation cause.
The old VLR deletes the subscriber’s temporary data, such as location information, authentication context, and service parameters held for that visitor. This prevents the former serving area from responding to later requests with obsolete routing information.
Cancel Location can also occur when a subscription is withdrawn, a prepaid account is cleared, or an operator needs to purge a record administratively. It is therefore a database-consistency operation rather than a direct instruction to allocate a roaming number.
The Roaming Number Retrieval Flow
For a mobile-terminated call, the originating caller reaches a gateway MSC (GMSC). The GMSC sends MAP_SEND_ROUTING_INFORMATION (SRI) to the subscriber’s HLR. The HLR identifies the current VLR and serving MSC, then sends MAP_PROVIDE_ROAMING_NUMBER (PRN) towards that serving node.
The VLR asks its associated MSC to allocate an MSRN. That number is temporary and routable within the visited network. The PRN response carries the MSRN back to the HLR, which returns it in the SRI response to the GMSC. The GMSC then sends an ISUP Initial Address Message towards the visited MSC using the MSRN.
Cancel Location is usually associated with the preceding or subsequent mobility update, not inserted into the PRN exchange itself. If a new location update has already invalidated the old VLR, the HLR must have a current serving address before it requests a roaming number.
Message Sequence And Timing
A simplified signalling sequence is: new VLR sends an update to the HLR; the HLR sends Cancel Location to the old VLR; the HLR confirms the new location; a GMSC sends SRI; the HLR sends PRN to the current VLR; and the VLR returns the allocated MSRN. The exact ordering can vary with implementation and MAP version.
Timers are important because SRI, PRN, and Cancel Location may cross several signalling transfer points or an international roaming hub. A timeout should not be treated as proof that the subscriber is unreachable. It may indicate congestion, a failed SCCP route, an overloaded HLR, or a filtering policy between networks.
Australian traffic can expose these issues during busy periods in the Sydney CBD or around major events at Melbourne venues. A subscriber may be registered through a domestic visited network while the call setup traverses an international signalling partner, creating extra latency and more points for failure.
Addressing And Transport Considerations
The HLR and VLR must be reachable through correct SCCP global title translation and point-code routing. Engineers validating an Australian deployment should account for national and international signalling domains, translated Global Titles, and differences between 14-bit, 24-bit, and variable-length point-code conventions. A practical reference on SS7 point-code formats helps when interpreting traces from mixed equipment.
MAP runs above TCAP and SCCP, while the underlying transport may be traditional TDM-based SS7 or SIGTRAN over IP. In older MSC environments, M2UA can carry MTP3 user signalling across an IP network; the M2UA adaptation layer is relevant when a legacy switch is connected to an IP signalling gateway.
Transport conversion must preserve sequence control, availability, and correct signalling-point identity. A working IP ping proves little: MAP traffic can still fail because of SCTP association problems, M2UA state changes, SCCP routing errors, or a misconfigured point-code mask.
Fault Diagnosis In A Live Network
A trace should correlate the subscriber’s IMSI, HLR address, VLR address, transaction identifiers, and timestamps. Look for MAP errors such as unknown subscriber, roaming not allowed, absent subscriber, system failure, and resource limitation. The return result from Cancel Location should be assessed separately from the later PRN response.
If PRN fails after a successful location update, investigate the current VLR, MSC allocation, roaming agreement, and MSRN pool. If Cancel Location fails, check whether the old VLR retains a stale record and whether repeated location updates are creating duplicate or conflicting state.
Coverage conditions in remote Australia can make diagnosis less obvious. A handset near Alice Springs, across the Great Dividing Range, or travelling through sparsely served areas may disappear temporarily without a signalling fault. Logs should distinguish radio reachability, MAP transaction failure, and a genuinely inactive subscriber.
Comparing The Key MAP Operations
| Operation | Main direction | Purpose | Typical call or mobility stage |
|---|---|---|---|
| Cancel Location | HLR to old VLR | Deletes obsolete visitor data | After a subscriber registers in a new VLR |
| Update Location | New VLR to HLR | Records the current serving area | Subscriber location registration |
| Send Routing Information | GMSC to HLR | Requests routing data for an incoming call | Start of mobile-terminated call setup |
| Provide Roaming Number | HLR to current VLR | Requests a temporary MSRN | After SRI identifies the serving VLR |
| PRN Result | Current VLR to HLR | Returns the allocated MSRN | Before GMSC routing through the visited MSC |
The key distinction is operational: Cancel Location keeps mobility databases clean, while PRN supplies the temporary address used to complete a call. An operator may see both in the same subscriber journey, but they solve different problems.
For reliable troubleshooting, follow the subscriber state from location update through old-record deletion, SRI, PRN, and ISUP call routing. What matters most is remembering that a current VLR record enables roaming number retrieval, while MAP Cancel Location removes the record that must no longer be trusted.
