DESCRIPTION

12/190 46-FAD 104 08 Uen PD2

Traffic Case Description - Location

Updating
Abstract
The purpose of this document is to describe the Traffic Case Location Updating from a
Data Transcript point of view.
The document doesn't explain on BLOCK/SIGNAL level, but that information can be
found in the FUNCTION DESCRIPTION for each function.
Contents
1

Revision Information

2
2.1
2.2
2.3
2.4

Description
Abbreviations
Concerned Nodes
General
Traffic Cases

1 Revision Information
Revision Impacts
A
Document based on earlier CME20
DT Info Models.
B
Rewritten document for a more
comprehensive description.
C
Updated document to SS R7
PD1

Updated document to SS R8s

PD2

Minor R8s updates

2 Description

Prepared Date
ERACLAB 96-0913
ERAMIST 97-0526
ETOTRRE 90-0921
ETOSADO 99-0527
ERAMACI 99-1014

2.1 Abbreviations
BSC
Base Station Controller
C7
CCITT Signalling System no. 7
CC
Country Code
GTRC
Global Title Routing Case
GPRS
General Packet Radio Services
HLR
Home Location Register
HPLMN
Home Public Land Mobile Network
IMSI
International Mobile Subscriber Identity
LA
Location Area
LAI
Location Area Identity
LU
Location Updating
MAP
Mobile Application Part (C7 user)
MGT
Mobile Global Title
MS
Mobile Station
MSC
Mobile services Switching Centre
MSIN
Mobile Station Identification Number
MSISDN
Mobile Station International PSTN/ISDN Number
MTP
Mobile Transfer Part (C7)
NA
Nature of Address
NDC
National Destination Code
NP
Numbering Plan
NS
Number Series

PINTER
Primary INTERmediate
PSP
Primary Signalling Point
PTERM
Primary TERMinating
RA
Routing Area. The geographical area served by one SGSN
SCCP
Signalling Connection Control Part (C7)
SGSN
Serving GPRS Support Node
SMS-SC
Short Message Services - Service Centre
TCAP
Transaction Capabilities Application Part (C7)
TT
Translation Type
VLR
Visitor Location Register

2.2 Concerned Nodes

MSC/VLR
HLR
SGSN

2.3 General
The Location Updating procedure occurs when a MS is switched on in an MSC/VLR
service area, or when an idle MS moves to a new MSC/VLR service area or Location
Area. LU can also occur prior to a call set-up.
The purpose of the LU procedure is for the MS to notify the VLR of its current location.
If the VLR recognises the IMSI of the MS, then the VLR will update the current location
(i.e. update the Location Area). If the VLR does not recognise the IMSI of the MS (i.e.
the MS is not registered in the VLR), then the VLR will ask the HLR, where the
subscription of the MS is held, for subscriber data. The HLR will store the VLR address
and send subscriber data to the VLR where the MS now is registered.
In R8s the GPRS is introduced. The MSC/VLR is connected to the SGSN directly using
the optional Gs interface. The Gs interface is used for dealing efficiently with terminals
that are attached to both GPRS (Packet-Switched) and GSM (Circuit Switched) traffic.

The Gs interface is essential for combined LA / RA update. A mobile terminal will do a

LU to the MSC/VLR and RA update to the SGSN separately. With the Gs interface, the
MSC and SGSN can keep each other updated about the area of terminal. This will save
signalling over radio interface.
This document describes three Location Updating Traffic Cases.

LU for Mobile Subscriber belonging to a combined VLR/HLR.

LU for Mobile Subscriber belonging to a Stand Alone HLR.
LU for International roamers.

2.4 Traffic Cases

2.4.1 General
In the following examples there are figures illustrating the traffic cases in numbered
steps. The text belonging to each event describes data used as input for the different
analysis defined in the DT. The text within brackets is the commands involved in the
analysis.
Note
In the following Traffic Case examples, SCCP routings via GTRC to Signalling
Points for other SCCP nodes are shown. If the SCCP nodes that are pointed out in
the GTRC (command C7GCI) are not reachable for some reason, the re-routing is
handled on MTP level (see MSC/VLR and HLR subfiles 15200, command.
C7RSI).

2.4.2 LU for Mobile Subscribers Belonging to a Combined VLR/HLR.

2.4.2.1 Step 1 (Figure 1)
Location Updating (LU) is initiated when the Mobile Station is powered on or enters a
new MSC/VLR service area. The MS sends a Location Update Request message up to
the MSC/VLR. The message contains the IMSI number of the mobile subscriber and
requires SCCP to carry it from the BSC to the MSC/VLR.

Figure 1
2.4.2.2

Step 2 (Figure 1)

The MSC/VLR does not recognise the IMSI number, so it must now request subscriber
data from the HLR. For this to take place the IMSI number must be converted to a
Mobile Global Title (MGT).
The reason for this conversion is that the IMSI numbering plan (E.212) is not recognised
outside the GSM network. If mobile operators agree upon international roaming,
Location Update messages will be sent between the operator networks, using PSTN,
which does not recognise the IMSI numbering plan and therefor are unable to route the
messages. It is therefor stated in the GSM specification, that the MCC and MNC are to be
converted to CC and NDC creating the MGT. The CC and the NDC are parts of the
ISDN/PSTN numbering plan known in all Public Switched Telephone Networks.
The conversion to MGT is performed in the IMSI number analysis, where also the
number format (NA) and MAP version (MAPVER) to be used are determined (see
subfile 76000).
Example 1 MML command definitions
MGISI:IMSIS=240 01, M=5-46 70 => MGT=46 70 7500000000
NA-4
International number format
MAPVER-2
MAP V3 signalling used
.....

In the MGT conversion example above the MCC+MNC part of the IMSI (240 01) are
removed and CC+NDC (46 70) are added. The parameters NA-4 and MAPVER-2
indicates that the MGT is in international format and MAP version 3 will be used in the
signalling between the MSC/VLR and the HLR.
2.4.2.3 Step 3 (Figure 1)
The Location Update MAP message is sent from the MSC/VLR to the HLR using SCCP.
Normally for Location Updating, TT=0 (Translation Type) and NP=7 (Numbering Plan)
are used, (see subfile 75500, command C7GSI). NP=7 indicates that Mobile Global Title
is used for the routing. For information about HLR redundancy, see doc. no. 142/190 46FAD 104 08.
To be able to identify the subscriber and to determine the subscribers HPLMN and HLR,
the CC (46), NDC (70) and the first two digits in MSIN (75) which identifies the HLR
within the own GSM network, have to be analysed.
Example 2 MML command definitions
C7GSI:TT=0
NP=7,
NA=4,
NS=46 70 75,
=> GTRC=8;
C7GCI:GTRC=8,
PSP=OWNSP;

Translation Type
Numbering Plan
Nature of Address
Number Series

Global Title Routing Case

Terminating in own node when combined VLR/HLR

When the HLR is collocated with MSC/VLR (combined VLR/HLR), the LU message
must terminate in the own node. In previously revisions this was done in the SCCP by
specifying TERM in the C7GSI command. But in SS R7 this is done in the SCCP by
specifying a GTRC=8 in the C7GSI cammand, and then in the C7GCI command set the
parameter PSP to OWNSP,see above.
2.4.2.4 Step 4 (Figure 1)
The HLR checks if the subscriber is roaming in a permitted area, (see subfile 75400,
command HGRCI).
Example 3 MML command definitions
HGRCI:AREA=46707 => must not result in Roaming Restriction
(ROAMREST).

If the subscriber is permitted to roam in the area, the HLR stores the new MSC/VLR
address and fetches the subscriber data and creates the "Insert Subscriber Data" message

using the included MSC/VLR address as return destination. Included in the message is
the HLRs own address, specified by command HGCAC subfile 75400. The SCCP
analysis is used to return the subscriber data.
Example 4 MML command definitions
C7GSI:TT=0,
Translation Type
NP=1,
Numbering Plan
NA=4,
Nature of Address
NS=46 70 7570, Number Series (MSC address)
GTRC=8;
C7GCI:GTRC=8,
PSP=OWNSP;

Global Title Routing Case

Terminating in own node when combined VLR/HLR

The HLR orders the old serving MSC/VLR to cancel all information about the subscriber
since the MS now is served by another MSC/VLR.
The communication HLR-VLR is from now on always sent in an international format,
using TT=0, NP=1 (indicating ISDN/PSTN numbering plan E.163/E.164) and NA=4 (see
subfile 75500, command C7GSI.
The VLR stores the subscriber data and sends a Location Updating confirmation message
to the MS.

2.4.3 LU for Mobile Subscribers Belonging to a Stand Alone HLR

2.4.3.1 General
In this traffic case, the HLR is not integrated with the MSC/VLR, which means that the
MSC/VLR must route the Location Updating MAP message out on the C7 signalling
network, addressed by MGT to the HLR.

Figure 2
2.4.3.2

Step 1+2 (Figure 2)

Step 1 and 2 are identical to the ones described in paragraph 2.4.2.1 and 2.4.2.2.
2.4.3.3 Step 3 (Figure 2)
The Global Title analysis (SCCP) of the LU message, will instead of being sent to a
GTRC for terminating, be sent to a GTRC for Primary Terminating (PTERM)(see subfile
75500, command C7GSI).
Example 5 MML command definitions
C7GSI:TT=0,
NP=7,
NA=4,
NS=46 70 75,
GTRC=5;

Translation Type
Numbering Plan
Nature of Address
Number Series
Global Title Routing Case leading to HLR

The GTRC is defined with the command C7GCI.

Example 6 MML command definitions
C7GCI:GTRC=5,
PSP=2-700,
PTERM;

Global Title Routing Case

Primary Signalling Point
Primary TERMinating

The Signalling Point (2-700) for the ST_HLR (Stand alone HLR) is pointed out, and
defined as Primary Terminating (PTERM). The PTERM parameter indicates that the next
SCCP node (in this case the HLR) is the receiver of the MAP/SCCP message. This makes
it possible to omit the Global Title analysis in the ST_HLR.
2.4.3.4 Step 4 (Figure 2)
The LU message terminates in the ST_HLR (without Global Title analysis) and the
ST_HLR responds by sending the subscriber data back to MSC/VLR using the
MSC/VLR address as Global Title, same principal as in paragraph 2.4.2.4 (see subfile
75500).
Example 7 MML command definitions
C7GSI:TT=0,
NP=1,
NA=4,
NS=46 70 757 0000
=> GTRC=1.
C7GCI:GTRC=1,
PSP=2-300,
=> PTERM;

(MSC/VLR address)

(MSC/VLR Signalling Point)

The "Insert Subscriber Data" message is received and terminated in the MSC/VLR
without using the SCCP analysis, due to the definition of PTERM (GTRC=1) in the
HLR. This means that the VLR address, doesnt have to be defined (for the VLR-HLR
communication) in the MSC/VLRs SCCP analysis. Its defined here, because external
equipment such as SMS-SC, EIR etc. usually cant use the PTERM functionality.
The LU is now completed and the mobile subscriber can roam in the new MSCs service
area.

2.4.4 LU for International Roamers

2.4.4.1 General
The LU procedure for an international subscriber is similar to what was explained in
paragraph 2.4.3.
In the example below a Swedish operator has an international roaming agreement with a
German operator. This agreement makes it possible for German subscribers to roam in
Sweden and vice verse.

Figure 3
2.4.4.2

Step 1+2 (Figure 3)

A German subscriber powers on his/her MS in a Swedish MSC/VLR service area.

The IMSI number is converted to a German MGT which makes it possible to route the
LU message towards Germany, in this case via the PSTN.
Example 8 MML command definitions
MGISI:IMSI=262 02, M=5-49 172 => MGT=49 172....
NA=4
MAPVER=1
.....

The MGT consists of the German Country Code CC=49, National Destination Code
NDC=172 and Mobile Subscriber Identity MSIN. The PSTN exchanges will now be able
to route the LU message to the German HLR, analysing the CC and NDC in the SCCP
address message (see paragraph 2.4.2.2).
2.4.4.3 Step 3 (Figure 3)

The MGT is used in the SCCP analysis to route the LU message towards the international
signalling network. In this case, only the Country Code has to be analysed in order to get
the GTRC (see subfile 75500, command C7GSI).
Example 9 MML command definitions
C7GSI:TT=0,
NP=7,
NA=4,
NS=49,
GTRC=4;

Translation Type
Numbering Plan
Nature of Address
Number Series (Country Code for Germany)
Global Title Routing Case towards PSTN

The GTRC is defined with C7GCI (see subfile 75500, command C7GCI).
Example 10 MML command definitions
C7GCI:GTRC=4,
PSP=2-400,
PINTER;

(SP for PSTN)

Since the MSC/VLR doesn't know the Signalling Point of the destination node (German
HLR), the node is unable to give the ultimate destination of the SCCP message. The
GTRC is therefor defined as Primary Intermediate and routed towards the international
signalling network. This means that the next SCCP node is considered to be an
intermediate SCCP node.
2.4.4.4 Step 4 (Figure 3)
In the intermediate SCCP node, in this case a switch in the PSTN network, a new Global
Title analysis takes place. The result is a new GTRC, pointing towards an international
switch in Germany. Of course there could be a lot more intermediate nodes involved in
the interrogation depending on the network structure.
2.4.4.5 Step 5-7 (Figure 3)
The SCCP routing continues until the terminating HLR in Germany is found.
The HLR then checks the MSIN in order to identify the subscriber, and responds by
sending back the subscriber data to the originating VLR. This is done by using the
address of the originating VLR as Global Title (NS) in the SCCP analysis (same
procedure as in paragraph 2.4.2.4).
The VLR-HLR communication proceeds until all data have been sent, and the LU is
completed. LU for other international roamers is handled in the same way with the
Country Code as input to the SCCP analysis.

References
1/1553 1/APT 210 25/1 Uen A
Traffic handling
142/190 46-FAD 104 08 A
HLR Redundancy
1/190 82-CNT 218 1296 A
C7GSI
9/190 82-CNT 218 1296 A
C7GCI
157/190 46-FAD 104 08 PA2
General Packet Radio Services system (GPRS) for CCS