Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
GSM Architecture
Location Update : Call Flows
MS to MS : Call Flow
MS to ISUP : Call Flow
Intra MSC Handover Call Flow
2
GSM Architecture
By:- Deepak Sharma
GSM Architecture
GSM Core
HLR/AUC Network
PSTN PSTN
D C
D
G
ISDN VLR
VLR
C
B B
ISDN
SMS-SC E
other
F F
PLMN MSC EIR GMSC
E
A other
A PLMN
BSC
BSC
A-Bis
IWF IWF A-Bis
B
T
BTS S B
T
B
T
S BTS
GSM Access Mobile S
BTS B
T
Network Station S
Um BTS
Um
data
MS PLMN data MS
4
Components of A Typical Mobile Network
Core
Network
Access
Network
Mobile
Station
5
GSM Areas
PLMN
Cell Cell
BSC Location
Area
MSC Region
6
Mobile Station
MS (Mobile Station)
7
BSS (Base Station Sub-system)
8
NSS (Network and Switching Subsystem)
9
NSS (Network and Switching Subsystem)
10
NSS (Network and Switching Subsystem)
11
Location Update Call Flows
By:- Deepak Sharma
Location Update ?
What is Location Update?
The process of Mobile Station Subscriber identifying to the Network the location in the
coverage area so that the Network can provide services to the Subscriber (using the MS)
based on the services subscribed.
13
Types OF Location Update
14
IMSI Attach Location Update
HLR MSC/VLR BSC BTS MS
Channel Request(CHANN_REQ)
Channel Required(CHANN_REQD)
Channel Activate(CHANN_ACT)
Channel Activate ACK(CHANN_ACT_ACK)
Immediate Assignment (IMM_ASS_CMD)
Location Update Request(LOURQ)
Connect Confirm(CC)
ID Request (ID_REQ)
ID Response (ID_RES)
Send Authentication Information (SAI)
SAI_ACK
Authentication Request(AUTRQ)
Authentication Response(AUTRES)
SRES Comparison
Update Location(UPLOC)
Insert Subscriber Data(ISD)
ISD_ACK
Update Location Ack (UPLOCA)
Cipher Command
Cipher Complete
Location Update Accepted (LOUAC)
TMSI Relocation Complete (TMRCMP)
Clear Command (CLRCOM) Channel Release
Clear Complete (CLRCMP) Channel Disconnect
Released (RLSD)
Release Complete (RLC)
15
Normal Location Update
16
Periodic Location Update
17
Inter VLR Location Update
18
Detailed Messages (Channel Request)
Before performing any of the operation like Location Update or Originating Call,
MS has to reserve the channels for signaling or traffic. For this MS performs
the following sets of transactions with BTS and BSC.
Channel Request – MS request as channel from BTS. Uses RACCH to send this RR
msg.Also have the reason as “Location Update” of establish a connection.
Channel Required : BTS decodes the above message and send this to BSC with the
calculated distance of MS with Timing Advance.
Channel Activate: BSC informs the BTS which channel type to activate and which
channel number to reserve.
TIP:Logical Channels
flows in
UPLINK,DOWNLINK
and Both directions.
19
Detailed Messages
20
Detailed Messages Contd…..
3. Identity Request – DTAP message from the Network to the MS requesting
its IMSI/TMSI/IMEI.
21
Detailed Messages Contd…..
9. Update Location - MAP message from VLR to HLR with location information of
the MS to be stored in the HLR.
10. Insert Subscriber Data - MAP message from HLR to VLR with subscriber
information
11. Insert Subscriber Data Ack - MAP message from VLR to HLR
acknowledging the receipt of ISD
12. Update Location Ack - MAP message from HLR to VLR upon successful
completion of an Update Location request.
13. Cipher Mode Command – BSSMAP message sent from the Network to the
BSS to update the encryption parameters for the concerned MS. The encryption key is sent
in this message to the BSS.Sends Kc and Algorithm A5/1 or A5/2 be used.
14. Cipher Mode Complete – BSSMAP message sent from the BSS to the Network
to indicate that successful stream ciphering has been achieved over the Um I/F.
22
Detailed Messages Contd…..
Information includes TMSI that the MS stores and uses in later transactions
17. Clear Command - BSSMAP message from Network to BSS to clear the
dedicated resource established during the Location Update Request message.
18. Clear Complete - BSSMAP Message from BSS to Network that the
associated dedicated resource has been successfully cleared
23
MS-MS Call Flow
By:- Deepak Sharma
MS-to-MS Call (Originating Half)
27
MS-MS Call Flow (Release procedure)
Disconnect
DTAP
SCCP
Release BSSMAP
Release F Interface
Release Complete C Interface
Release Complete D Interface
Clear Command
Clear Command PSTN I/F
Clear Complete
Clear Complete
Released
Released
Released Complete
Released Complete
28
Detailed Messages
SCCP CR message: containing the MTP Routing Label*, Source Local Reference
Number*, Calling/Called Party Addresses
BSSMAP CMPL3: basically passes location information to the switch (lac and cell id)
DTAP CMSRQ message: classmark2 indication (20-GSM Ph1, 00-GSM ph2,40-
UMTS), mobile identity (IMSI/TMSI), CM Service Type (mobile originated call,
emergency call setup, short message xfer, SS Activation).
29
Detailed Messages Contd….
5. Check IMEI – MAP message from the MSC to the EIR requesting IMEI validation.
This message contains MANY parameters:
SCCP Calling & Called Party address (i.e. MSC # and EIR # and their respective
SSNs)
IMEI value
Transaction ID: contained in each map message and are used to identify messages as
part of a certain dialogue between two nodes. (This has been covered in detail in the
MAP Overview)
Invoke ID: sent by the originating node to uniquely identify a request for an
operation (such as Check IMEI)
30
Detailed Messages Contd….
6. Check IMEI Ack – MAP message from the EIR to the MSC telling replying the IMEI
validation request. It contains parameters similar to above including:
7. Setup- DTAP message sent from either the MS OR the MSC to initiate call
establishment.BASIC call setup information includes:
Speech or DATA bearer capability
Called & Calling Party Numbers
8. Send Info For Outgoing Call (SIOC) : MSC send SIOC to VLR to know the
Call Barring status of the originated call. Ex: BAOC, BAOIC etc
10. Progress – DTAP message from the MSC to the MS indicating the progress of the call in
the event of interworking
31
Detailed Messages Contd….
11. Send Routing Information - MAP message sent from the GMSC to the
HLR requesting information on how to route a call towards a mobile subscriber.
This message includes previously mentioned MAP parameters including:
MSISDN: used by the HLR to determine where the called subscriber is currently
located in order to query its current VLR for a Roaming Number.
Number of Forwarding: indicates how many times the call has been forwarded (max
of 5 times)
12. Provide Roaming Number: HLR to the serving VLR requesting a roaming number
for the called subscriber. It includes:
IMSI: used by the VLR identify the called subscriber so an MSRN can be provisioned to
the MS.
Forwarding Information: this includes the forwarded to number. During SRI, the HLR
may be able to make the determination of Call Forwarding before PRN is invoked (i.e.
CFU).
32
Detailed Messages Contd….
14. Send Routing Info ACK: MAP message sent from the HLR to the GMSC returning
either the Roaming Number of the requested subscriber, forwarding information or an
Error.
Roaming Number: used by the originating MSC to translate to the proper MSC where the
called subscriber is located
Forwarding Information: this includes the forwarded to number. During SRI, the HLR
may be able to make the determination of Call Forwarding before PRN is invoked (i.e.
CFU
15. Paging – BSSMAP message sent from the MSC to the BSS which allows the BSS to
transmit the PAGING message to the proper cells. It Includes:
TIP: MS always listen
mobile identity (either TMSI or IMSI) and the cell identification. to PCH.
After getting Paging Command message from BSC, BTS broadcasts the paging in Air I/F on
PCH.
16. Paging Response - Similar to the CM SERVICE REQUEST message except the
enveloped DTAP message is PGRSP instead of CMSRQ.
20. Alerting – DTAP message sent by MSC to the MS to indicate that called user alerting
has begun.
21. Connect – DTAP message sent by MSC to the MS to indicate that the call has been
accepted.
22. Connect Ack – DTAP message sent by the MS to the MSC to indicate that the call is
being accepted.
23. Disconnect - DTAP message sent by the MS to the MSC indicating that the call needs to
be torn down.
34
MS-ISUP Call Flow
By:- Deepak Sharma
MS-to-ISUP Call
SIOC
CC
Call Proceeding
Assignment_Request
Assignment_Complete
36
MS-to-ISUP Call
Disconnect
ISUP Release (REL)
Release
Release Complete (RLC)
Release Complete
Clear Command (CLRCOM)
Clear Complete (CLRCMP)
Released (RLSD)
Release Complete (RLC)
37
Intra MSC- Inter BSC Handover
********* MO has been moved to BSC2 and rest flow of the call will remain same*************
39
40