CALL PROCESSING

In this we discuss the call processing aspect and look into specifics case of a mobile
originated (MO) call and a mobile terminated (MT) call.

MOBILE ORIGINATED (MO) CALL

There are four distinct phase of a mobile originated call-

 Setup phase.
 Ringing phase.
 Conversation phase.
 Release phase.

Out of these phases the setup phase is the most important phase and includes authentication
of the subscriber, Ciphering of data over radio interface, validation of mobile equipment,
validation of subscriber data at VLR for requests service and assignment of a voice channel
on A-interface by MSC. Whenever MS wants to initiate on outgoing call or want to send an
SMS it requested for a channel to BSS over RACH. On receiving request from MS, BSS
assigns a stand-alone dedicated control channel (SDCCH) to MS over access grant channel
(AGCH). Once a SDCCH has been allocated to MS all the call set up information flow takes
place over SDCCH.

A connection management (CM) entity initiates a CM Service Request message to the

network. Network tries to establish an MM connections between the MS and the network and
upon successful establishment of MM connection a CM Service Accept message is received
by MS from the network. MS now sends a Call Set up Request to the network which
contains the dialed digits (DD) of the called party. As the call setup message is received at the
MSC/VLR certain check are performed at MSC/VLR like- whether the requested service is
provisioned for the subscriber or not, whether the dialed digits are sufficient or not, any
operator determined barring (ODB) does not allow call to proceed further etc. As these
checks are performed at MSC/VLR a Call Proceeding Message is sent from the network
towards the MS. After all the checks are successfully passed MSC sends Assignment
command to the BSS which contains a free voice channel on A-interface On getting this
message BSS allocates a free TCH to the MS and informs the MS to attach to it. MS on
attaching to this TCH informs the BSS about it. On receiving a response from the BSS, MSC
switches the speech path toward the calling MS. Thus at the end of Assignment the speech
path is through from MS to MSC. It is important to note that at this stage mobile has not
connected user connection as yet. MS at this stage does not listen anything.

After assignment MSC sends a network set-up message to the PSTN requesting that a
call be set up. Included in the message are the MS dialed digits (DD) and details specifying
which trunk should be used for the call. The PSTN may involve several switching exchanges
1
RTTC MYSORE
before finally reaching the final local exchange responsible for applying the ringing tone to
the destination phone. The local exchange will generate the ringing tone over the trunk, or
series of trunk (if several intermediate switching exchange are involved), to the MSC. At this
point in time MS will hear ringing tone. The PSTN notifies the MSC with a network-alerting
message when this event occurs. MSC informs the MS that the destination number is being
alerted. It is important to note that this is primarily a status message to the MS. The MS hears
the ringing tone from the destination local exchange through the established voice path.

When the destination party goes off hook, PSTN informs the MSC of this event. At this
point, MS is connected to the destination party and billing is started. MSC informs the MS
that connection has been established and MS acknowledges the receipts of the connect
message.

Under normal condition, the termination of a call is MS initiated or network initiated. In this
scenario, we have assumed that MS initiates the release of the call by pressing “end” button
and MS send a disconnect message to the MSC. The PSTN party is notified of the
termination of the call by a release message from the MSC. The end- to- end connection is
terminated. When MSC is left with no side task (e.g. charging indication etc.) to complete a
release message is sent to the MS. MS acknowledges with a release complete message. All
the resources between MSC and the MS are released completely.

Um A

MS BSS MSC/
VLR

Channel Request

 RACH

SD CCH Assignment

 AGCH

Service Request Authentication Ciphering

 Equipment Validation Call set up
Handover(s)
SDCCH Call re lease

2
RTTC MYSORE
 Authentication Parameters

•
Um A F
MS BSS MSC/ EIR
VLR

Request for service

IME I Request Authentication
 Ciphering
SDCCH

IMEI Response (IMEI)


SDCCH

Check IMEI


IMEI Check Results


Call setup
Handover(s)
Call re lease

3
RTTC MYSORE
 Um A

MS BSS MSC/
VLR

Call Setup Request

 SDCCH

Call Proceeding
Request for service
 Authentication Ciphering
Equipment Va lidation
SDCCH

Um A
MS BSS MSC/ PSTN
VLR

Request for Service Authentication

Ciphering

Equipment va lidation
Network setup
14 (DD ....)

15 Network Alerting

16 Alerting

Connect (answer)
FACCH

17
Start Billing

Connect
18

FACCH
Connect Acknowledgement

19

FACCH
8

4
RTTC MYSORE
 Um A
MS BSS MSC/ PSTN
VLR

Disconnect
20
FACCH Stop Billing

21 Network Release

Release
22
FACCH

Release complete
23
FACCH

24 Clear
command
Channel Release

25 FACCH

Clear Complete
26

MOBILE TERMINATED (MT) CALL-

The different phases of a mobile terminated call are
 Routing analysis
 Paging.
 Call setup.
 Call release.

The phases of mobile terminated (MT) call are similar to a mobile originated (MO) call
except routing analysis and paging phase. Call to a mobile subscriber in a PLMN first comes
to gateway MSC (GMSC). GMSC is the MSC, which is the capable of querying HLR for
subscriber routing information. GMSC need not to be part of home PLMN, though it is
normal practice to have GMSC as part of PLMN in commercially deployed networks.

GMSC opens a MAP (Mobile Application Part) dialogue towards HLR and Send / Routing /
Info-Request (SRI request) specific service message is sent to HLR. SRI request contains
MSISDN of the subscriber. HLR based on location information of this subscriber in its
database, opens a MAP dialogue towards VLR and sends Provide / Roaming / Number-
request (PRN request)to the VLR. VLR responds to PRN request with PRN response
message, which carries an MSRN (mobile subscriber roaming number), which can be used
for routing toward visiting MSC in the network. HLR returns MSRN to GMSC (MSC that
queried HLR) in SRI response message. On getting MSRN the GMSC routes the call towards
VMSC The purpose of this entire exercise is to locate where the terminating mobile
subscriber is.

The MSRN received at GMSC is in international format (Country Code + Area Code
+ subscriber number). Normally, based on the routing info at GMSC, the call may be routed
out of the GMSC towards VMSC of the terminating subscriber, in which case appropriate

5
RTTC MYSORE
signaling protocol (MF or ISUP) depending on the nature of connecting of GMSC with
subsequent exchange along the route will apply. If at VMSC the terminating mobile
subscriber is found to be free (idle), paging is initiated for terminating mobile subscriber.
MSC uses the LAI provided by the VLR to determine which BSS’s should page the MS.
MSC transmit a message to each of these BSS requesting that a page be performed. Included
in the message is the TMSI of the MS. Each of the BSS’s broadcasts the TMSI of the mobile
in a page message on paging channel (PCH).

When MS detects its TMSI broadcast on the paging channel , it responds with a channel
request message over Random Access Channel (RACH). Once BSS receives a channel
request message , it allocates a stand –alone Dedicated Control Channel(SDCCH) and
forwards this channel assignment information to the MS over Access Grant Channel
(AGCH). It is over this SDCCH that the MS communicates with the BSS and MSC until a
traffic channel assigned to the MS. MS transmits paging response message to the BSS over
the SDCCH. Included in this message is MS TMSI and LAI. BSS forwards this paging
response message to the MSC. Now Authentication and Ciphering phases are performed to
check the authenticity of MS and encrypt data over radio interface.

On the network side after paging is initiated, while waiting for paging response, a defensive
timer called, ”Early ACM” timer is run at MSC to avoid network timeouts. On successfully
getting paging response, a setup message is constructed to be sent towards terminating MS. In
case paging fails due to authentication failure or when the subscriber is out of radio-coverage,
the call is cleared.

In case CLIP is not subscribed by the terminating mobile subscriber, calling number is not
included in set-up message. In case CLIP is subscribed and PI value in calling number
parameter indicates “presentation allowed” the number is included in the set-up message. In
case CLIP is subscribed but PI received in calling number parameter indicates “presentation
restricted” then number is included only if CLIRO is also subscribed to.

MS on receiving the set-up message performs compatibility Checking before responding to

the set-up message – it is possible that MS might be incompatible for certain types of call set-
ups. Assuming that MS passes compatibility checking, it acknowledges the call setup with
set-up confirm message. After getting set-up confirm message from the MS, MSC performs
assignment phase (similar to one discussed in MO call) and a voice path is established from
MSC to the MS. MS begins altering the user after it receives the traffic channel assignment.
MS send alerting message to the MSC .MSC upon receiving the alerting indication from the
MS, begins generating an audible ringing tone to the calling party and sends a network
alerting via GMSC to the PSTN. Prior to this the calling party heard silence.

At this point in the call, MS is alerting the called party by generating on audible tone. One of
the three events can occur-calling party hangs-up, mobile subscriber answers the phone, or
the MSC times out waiting for the mobile subscriber to the answer the call. Since radio traffic
channel is a valuable resource, GSM does not allow a MS to ring forever.

6
RTTC MYSORE
In the present scenario we have assumed that the mobile subscriber answers the phone. The
MS in response to this action stops alerting and sends a connect message to the MSC. MSC
removes the audible tone to the PSTN and connects the PSTN trunk to BSS trunk (terrestrial
channel) and sends a connect message via GMSC to the PSTN. The caller and the called
party now have a complete talk path. This event typically marks the beginning of the call for
billing purposes. MSC sends a connect acknowledge message to the MS.

The release triggered by the land user is done in similar way as the release triggered by
mobile user. MSC receives a release message from the network to terminate end-to-end
connection. PSTN stops billing the calling landline subscriber. MSC sends a disconnect
message towards the MS and MS responds by a Release message. MSC release the
connection to the PSTN and acknowledges by sending a Release Complete message to PSTN.
Now the voice trunk between MSC and BSS is cleared, traffic channel (TCH) is released and
the resources are completely released.

The mobile-to-mobile call scenario is a combination of phases encountered in mobile

originated (MO) and mobile terminated (MT) call.

Um A
MS BSS MSC/ PSTN
VLR

Disconnect
20
FACCH Stop Billing

21 Network Release

Release
22
FACCH

Release complete
23
FACCH

24 Clear
command
Channel Release

25 FACCH

Clear Complete
26

7
RTTC MYSORE
 Um A
MS BSS MSC/
VLR

Routing analysis
6 Perform P age (T MSI)

Page
7
PCH

Channel Request
8
RACH

SDCCH
Assignment
9 AGCH

Page Res ponse

(TMSI, LAI)
10
SDCCH

11 Page Res ponse

Authentication
Relea
Ciphering
se
Equipment validation
Call setup
Handover (s) 12
Call release

Um A
MS BSS MSC/
VLR

Routing analysis
Paging
Authentication
Ciphering
Equipment validation
Call Setup
12
SDCCH

13 Call Set up Confirm

SDCCH

Ass ign Trunk &

14 Radio Channel

Ass ign Radio

15 Channel
SDCCH

Radio Assignment
Complete
16
SDCCH
Trunk & Radio
Assignment
Complete Relea
17
se
Handover (s)
Call release 13

8
RTTC MYSORE
 Um A
MS BSS MSC/ HLR GMSC PSTN
VLR

Rout ing analysis

Paging
Authent icat ion
Ciphering
Equipment validat ion

Mobile Alerting
18
FACCH

19 Network Altering
Connect

Connect (Off - hook)

20
FACCH

21 Connect

22 Connect Acknowledge

FACCH
Releas
e

Handover (s)
Call release 14

Um A
MS BSS MSC/ HLR GMSC PSTN
VLR

Routing analysis
Paging
Authentication
Ciphering
Equipment validation
Call setup
Handover(s)
23

Network Release

Disconnect
24
FACCH

Release
25

FACCH Release Complete

Release Complete
26
FACCH

27 Clear
Command

28 Channel Release
FACCH
Clear Complete
29
15

*******

9
RTTC MYSORE