Scribd
Upload
3 views

Gsm

Uploaded by

friday18.code
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
3 views

Gsm

Uploaded by

friday18.code
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 45

Data Services in GSM GPRS

GPRS introduces new network elements


• Serving GPRS Support Node (SGSN)
• authentication & authorization, GTP tunneling to GGSN, ciphering & compression,
mobility
management, session management, interaction with HLR,MSC/VLR, charging &
statistics,
as well as NMS interfaces.
• Gateway GPRS Support Node (GGSN)
• interfacing to external data networks (basically it is a network router)
encapsulating data packets in GTP and forwarding them to right SGSN,
routing mobile originated packets to right destination, filtering end user
traffic, as well as collecting charging and statistical information of data
network usage.
GPRS is the result of committees trying to “adapt” Mobile IP to GSM systems.
Introduction

To exercise location tracking, a mobile


service area is partitioned into several
Location Areas (LA) or registration
areas.
 Every LA consists of a group of BTSs.

The major task of mobility


management is to update the location
of an MS when it moves from one LA
to another.
22
Location Update Concept
(Registration)
 The location update (registration) procedure is
initiated by the MS.
 Step 1. The BTs periodically broadcast
the corresponding LA addresses to
the MSs.
 Step 2. When an MS receives an LA address
different from the one stored in it memory, it
sends a registration message to the network.
 Note that
 Every VLR maintains the information of a group of LAs. When an
MS visits an LA, a temporary record of the MS is created in the
VLR to indicate its location (i.e. LA address).
 For every MS, a permanent record is maintained in HLR. The
record stores the address of VLR visited by the MS. 23
Two Issues of GSM Mobility
Databases

 Fault Tolerance.
 If the location database fail, the loss or corruption of location
information will seriously degrade the service offered to the
subscribers.

 Database Overflow.
 The VLR may overflow if too many users move into the VLR-
controlled area in a short period.
 If the VLR is full when a mobile user arrives, the user fails to
register in the database, and thus cannot receive cellular service.
 This phenomenon is called VLR overflow.

24
GSM Basic Location Update
Procedur e

Case 1. Inter-LA Movement


Case 2. Inter-MSC Movement
Case 3. Inter-VLR Movement
GSM Basic Location Update: Inter-LA
Movement (1/3)

The MS moves from LA1 to LA2, where


both LAs are connected to the same
MSC.
In GSM 04.08, Nine message are
exchanged between the MS and the
MSC, and ten messages are
exchanged between the MSC and the
VLR.
Four major steps are discussed here.
27
GSM Basic Location Update: Inter-LA
Movement (2/3)

 Step 1.
 A location update request message is sent (MS->BTS->MSC) .
Location Update Request (Prev. LA, Prev. MSC, Prev. VLR). Note
that New MSC = Prev. MSC, New VLR = Prev. VLR
 The MS identifies itself by the Temporary Mobile Subscriber
Identity (TMSI), which is an alias for IMSI.
 IMSI (International Mobile Subscriber Identity) is used to identify
the called. IMSI is not known to the User but GSM network.
 TMSI is used to avoid sending the IMSI on the radio path, which is
temporary identity is allocated to an MS by the VLR at inter-VLR
registration, and can be changed by the VLR.

28
GSM Basic Location Update: Inter-LA
Movement (3/3)

 Step 2. The MSC forwards the location update


request to the VLR by a TCAP message,
MAP_UPDATE_LOCATION_AREA.
 This message includes (Address of the MSC, TMSI of MS, Prev.
Location Area Identification (LAI), Target LAI, Other Related
Information).

 Steps 3 and 4.
 Part I. The VLR notices that both LA1 and LA2 belong to the same
MSC.
 Part II. The VLR updates the LAI field of the VLR record.
 Part III. The VLR replies an ACK to the MS through the MSC.

29
VLR Failure Restoration

 Service Information of a VLR record recovered by


 The first contact between the VLR and the HLR of the
corresponding MS.

 Location Information of a VLR record


recovered by
 First radio contact between the VLR and the MS

 Mobile Station Information of a VLR record


recovered by
 Either by contact with the HLR or the MS
VLR Record Restoration Initiation
Even t 1 － MS Registration

The VLR considers the registration as a


case of inter-VLR movement.
Following the normal registration
procedure defined in inter-VLR
movement.
In this case, the TMSI sent from the MS to
the VLR cannot be recognized, and the
MS is asked to send IMSI over the air.
VLR Record Restoration Initiation
Even t 2 － MS Call Origination

When the VLR receives the call origination


request
MAP_SEND_INFO_OUTGOING_CALL from
the MSC, the VLR record of the MS is not
found.
The VLR considers the situation as a
system error, with the cause “unidentified
subscriber”.
The request is rejected, and the MS is
asked to initiate the location registration
VLR Record Restoration Initiation
Event 3 － MS Call Termination (1/)
 Steps 1-3. Similar to the first three steps of the
basic call termination procedure, the VLR is
queried to provide the MSRN.
 Note that since the record has been erased after the failure, the
search fails. The VLR creates a VLR record for the MS.
 Neither the service nor the location info is available.

 Steps 4 and 7.
 Since the VLR does not have the routing information, it uses the
MSC number provided by MAP_PROVIDE_ROAMING_NUMBER
message to create MSRN.
 The number is sent back to the gateway MSC to setup the call in
Step 8.
VLR Record Restoration Initiation
Event 3 － MS Call Termination (2/)

 Steps 5 and 6.
 The VLR recovers the service information of the VLR record by
sending a MAP_PROVIDE_ROAMING_NUMBER message to the
HLR.
 The HLR sends the service information to the VLR using the
MAP_INSERT_SUBSCRIBER_DATA message.
 At this point, the service information of the VLR record has been
recovered.
 However, the location information, specifically, the LAI number,
still not available. This information will be recovered at Step 11.

 Note that Steps 4 and 5 can be executed in


parallel.
VLR Record Restoration Initiation
Event 3 － MS Call Termination (3/)

 Step 8. After the gateway MSC receives the MSRN


in Step 7, the SS7 ISUP message IAM is sent to
the target MSC.
 Steps 9-11.
 The target MSC does not have the LAI info of the MS.
 In order to proceed to set up the call, the MSC sends the message
MAP_SEND_INFO_FOR_INCOMING_CALL to the VLR.
 Unfortunately, the VLR does not have the LAI info either.
 Hence the VLR asks the MSC to determine the LA of the MS by
sending a MAP_SEARCH_FOR_MOBILE_SUBSCRIBER message.
VLR Record Restoration Initiation
Even t 3 － MS Call Termination (4/4)

 Steps 12 and 13.


 The MSC initiates paging of the MS in all LAs.
 If the paging is successful, the current LA address of the MS is
sent back to the VLR by the MAP_PROCESS_ACCESS_REQUEST
message.
 At this point, the location information of the VLR record is
recovered.

 Note that
 MAP_SEARCH_FOR_MOBILE_SUBSCRIBER is an expensive
operation because every BTS connected to the MSC must perform
the paging operation.
 To avoid this “Wide Area Paging”, the GSM system may
periodically asks the MSs to re-register.
HLR Restoration Procedure (1/3)

After an HLR failure, the data in the


backup are reloaded into the HLR.
An Uncovered Period = the time interval
after the last backup operation and
before the restart of the HLR.
Data that have been changed in the
uncovered period can not be recovered.
HLR Restoration Procedure (2/3)

Step 1. The HLR sends an SS7 TCAP


message MAP_RESET to the VLRs where
its MSs are located.
Step 2. All the VLRs derive all MSs of the
HLR. For each MS, they send an SS7
TCAP message,
MAP_UPDATE_LOCATION, to the HLR.
HLR Restoration Procedure (3/3)

The HLR restoration procedure is not robust.


 An MS may move into a VLR (which does not have any other MSs from the
given HLR residing) during the uncovered period.
 The new location is not known to the HLR at the last check- pointing time.
 If so, the HLR will not be locate the VLR of the MS during Step 1 of HLR
restoration.

VLR Identification Algorithm is to solve the problem.

You might also like