GSM MAP Location Update Procedure Across SS7 Networks
A mobile subscriber’s location update is the signalling transaction that keeps the core network informed about the serving VLR and the subscriber’s current location area. In a GSM network, this process connects radio access procedures with MAP operations carried through SS7 or an IP-based SIGTRAN transport.
The exchange is easy to misunderstand because several events occur together: authentication, ciphering, VLR registration, HLR data synchronisation and TMSI allocation. Reading the sequence layer by layer makes it easier to diagnose rejected updates, roaming problems and delayed call delivery.
| Situation | Main signalling path | Typical result | Useful diagnostic clue |
|---|---|---|---|
| Normal movement between location areas | MS → BTS/BSC → MSC/VLR | Location Update Accept | New location area stored |
| Move to a different VLR | VLR → HLR → old VLR | Subscriber data transferred | Cancel Location at old VLR |
| Periodic registration | MS → serving MSC/VLR | Location refreshed | Timer-driven request |
| Authentication failure | VLR ↔ HLR/AuC | Update rejected | MAP authentication or security error |
| Temporary radio or SS7 fault | Radio network or signalling route | Timeout or retry | Missing response or SCCP failure |
Why a mobile performs a location update
The handset initiates a location update when it detects a new Location Area Identity, after a periodic timer expires, or when it performs an IMSI attach. A Location Updating Request travels over the GSM radio interface using Radio Resource and Mobility Management procedures. The message normally carries the IMSI or a temporary identity such as the TMSI, together with the new location area information.
The serving MSC and VLR check whether the subscriber is already known locally. If the handset has moved between location areas controlled by the same VLR, the operation may be largely local. A change of VLR requires a wider database transaction so that the HLR knows where to route mobile-terminated calls and short messages.
Protocol layers behind the exchange
MAP messages sit above TCAP and SCCP in a traditional SS7 architecture. MTP3 provides signalling point routing, while MTP2 and the physical bearer carry the lower-level signalling. The global title of an IMSI, MSISDN or network node can be translated by SCCP Global Title Translation to select the correct HLR or VLR destination.
Modern operators often transport this signalling over SIGTRAN. SCTP provides the transport association, while M3UA carries MTP3-user messages between signalling gateways and application servers. Engineers studying these layers can use the SS7 training courses to connect MAP call flows with SCCP addressing, MTP routing and SIGTRAN deployment.
The main MAP message flow
After radio-level access and initial checks, the serving VLR sends MAP UpdateLocation to the HLR. The request identifies the serving VLR and the subscriber. The HLR records the new VLR address, then commonly sends MAP CancelLocation to the previous VLR. This removes stale registration data and prevents the old serving node from accepting traffic for the subscriber.
The HLR then sends MAP InsertSubscriberData to the new VLR. The data may include the subscriber’s provisioned services, roaming restrictions, bearer capabilities and supplementary-service settings. Once the VLR confirms the data, the HLR returns an UpdateLocation result. The MSC can then complete the air-interface procedure with Location Update Accept, often followed by TMSI Reallocation.
Authentication and subscriber security
Authentication is usually performed before the registration is accepted. The VLR may request authentication vectors from the HLR using MAP SendAuthenticationInfo. Those vectors are generated with support from the AuC and contain parameters used to challenge the SIM. The handset calculates a response, while the network compares it with the expected value.
Air-interface ciphering protects the radio exchange after security procedures succeed. This protection should not be confused with encryption across every SS7 segment. Legacy MAP signalling may travel through trusted operator interconnects, while IP-based signalling requires carefully controlled SCTP associations, signalling firewalls, screening rules and monitoring.
Timers, errors and repeated attempts
A failed update can result from a rejected roaming agreement, an unknown subscriber, an illegal equipment identity, congestion or an unreachable HLR. MAP return errors provide useful categories, but a trace must also show SCCP errors, TCAP dialogue termination and lower-layer retransmissions. A missing response may indicate routing failure rather than a subscriber problem.
Periodic location updates are governed by network-configured timer values and handset behaviour. If the timer expires without successful registration, the device retries according to the mobility-management rules. Radio coverage gaps on long rural routes, including areas between Adelaide and regional South Australia, can therefore look like core-network failures unless radio and SS7 traces are correlated.
Reading a packet or signalling trace
Start with the time relationship between the air-interface Location Updating Request and the first MAP operation. Identify the originating and destination signalling point codes, SCCP called and calling party addresses, TCAP transaction identifiers and MAP component types. This reveals whether the request reached the intended HLR and whether the dialogue completed normally.
Next, check for UpdateLocation, CancelLocation and InsertSubscriberData in their expected order. A missing CancelLocation may leave stale VLR state, while missing subscriber data can produce an apparently successful registration followed by failed supplementary services. Analysts can document an unresolved trace through the support contact page when a protocol question requires specialist review.
Australian deployment considerations
Australian subscribers commonly move between dense metropolitan cells in Sydney, Melbourne, Brisbane or Perth and large low-density coverage areas. A handset commuting by train in Melbourne may cross several location areas quickly, while a device travelling through the outback can remain radio-attached to one broad area for much longer. These different mobility patterns affect update frequency and trace volume.
Domestic roaming, MVNO arrangements and inter-operator signalling make correct global title routing especially important in the Australian market. Operators must also handle privacy obligations under the Privacy Act 1988 and related telecommunications requirements when retaining subscriber or location records. Location-update logs should therefore be access-controlled, minimised where appropriate and handled as sensitive operational data.
The essential sequence is simple to remember: the handset reports a new location, the serving VLR contacts the HLR through MAP, old registration is cleared, subscriber data is supplied, and the network confirms the update. Tracing that sequence across GSM, SS7 or SIGTRAN layers is the key to distinguishing radio faults, database errors and signalling-route failures.
