Camp on with preferred list

Scans 124 ARFCN's

5 samples/ARFCN spread
over 3 to 5 secs

Locks on to best

A
Locks on to next
best in BA list

Searches for FCH

IF
Found
Yes

Lock on to next best

Yes

No

Cell
barred
No

Read BCCH Info

No
C1 > 0

NC
matches
Yes

No
Yes
CAMP ON

A
www.gtllimited.com

No preferred list
Scans 124 ARFCN's

Lock on to next best

Locks on to best

Location Update

Searches for FCH

Puts PLMN in
forbidden list

No
IF
Found
Yes

No

Yes

Read BCCH Info

Cell
barred

Yes

Successful

Stores the BA list

Next in BA list

No
C1 > 0

Mobile Frame Synchronization

The purpose of Synchronizing is to read the BCCH message

Mobile gets Synchronized with the cell by SCH

Mobile locates SCH with the help of FCCH

FCCH Burst
TB3

Fixed Bits ( all zeros )

142

FCCH has a easily recognizable structure with all zeros

Mobile knows that SCH follows FCCH

TB3

GP

The maximum time allowed for synchronization is 0.5s, and the maximum time allowed to read the
BCCH data, when being synchronized with the BCCH carrier, is 1.9 secs.

Mobile Frame Synchronization

SCH Burst Contains the TDMA Frame No and BSIC
TB3 Information
39

Midamble
64

Frame Number
(19 Bits)

Superframe No
11 Bits

Information
39

TB3

SCH Burst

BSIC
(6 Bits)

Multiframe No
5 Bits

SCH Frame No
3 Bits

Frame No = 11bits ( To point Superframe No out of 2048 Superframes )

5bits ( To point Multiframe No out of 26 Mulitframes )
3bits ( To Point out the SCH Frame No out of 5 in 1 Multiframe )
MS calculates the TDMA Frame no from this information
0

1
S
1

11

21

31

41

S
2

S
3

S
4

S
5

50

Mobile - Cell Access

Location Update Signaling Diagram
BTS
Channel Req

Immediate Assgn
Loc Upd Req ( SABM )

Auth Req
Auth Resp

Channel Reqd
Channel Activation
Chan Actvn Ack
Imm Assgn Cmd
Establish Ind

Data Request
Data Ind

Data Request
Loc Upd Accept

MSC

BSC

Complete Layer 3 Info

Authentication Request

Authentication Response

Loc Upd Accept

Clear Command
Clear Complete

Mobile Cell Access

RACH

Channel
Request

T3120
Re-transmission
T3120

Immediate Assignment

T3101
Response

AGCH

Immediate Assignment Procedure

BSC

BTS
Channel Request

T3120

Channel Required
Channel Activation
Channel Activation Ack
Immediate Assign Command

Immediate Assignment

T3101

Message Contents
Channel Request
Random Access

TB SYNCH
8
41

Information
36

5 bits
Random Reference
No.

TB
3
3 bits
Establishment
Cause

G
P
6 bits
BSIC (coded
in parity bits)

Establishment Cause
100 -- Answer to paging
101 -- Emergency Call
110 -- Call re-establishment
111 -- Originating Call
0000 -- Location Update
0001 -- IMSI Detach, SMS, SS Management
011 - Reserved for future use

Message Contents
Channel Required
Channel Number --- Indicates on which channel the message was received ( RACH )
Request Reference --- Contains RACH info ( Random No, Cause ), Frame No
Access Delay ---- Delay in terms of bit period ( 0- 63 )
Physical Context --- Optional for manufacturer to add more information ( RxLev etc, )
Immediate Assignment Command
Channel Number --- channel on which the message is to be sent ( AGCH )
Message type --- Immediate Assignment
Channel Description --- SDCCH/4 or SDCCH/8. Sub-channel Number
TSC, ARFCN, Single or Hopping, HSN
Mobile Allocation Table
Request Reference --- Contains RACH info ( Random No, Cause ), Frame No
Timing Advance ---- Timing Advance value ( 0 -63 )
Mobile Allocation --- MAI table if hopping is used
Starting time --- TDMA Frame No if frequency for new channel changes ( NC - case )

Message Contents
BTS

BSC

Channel Request
Channel Request
Immediate Assign Command
Immediate Assign Extended

Immediate Assignment Extended Immediate Assignment Command

Channel Description 1
Request Reference 1
Timing Advance 1
Channel Description 2
Request Reference 2
Timing Advance 2
Mobile Allocation
Starting time

Channel Number -- AGCH

Message type -- Immediate Assign Extended
Channel Description 1
Request Reference 1
Timing Advance 1
Channel Description 2
Request Reference 2
Timing Advance 2
Mobile Allocation
Starting time

Immediate Assignment Procedure Completion

BTS
Channel Request

RACH

Immediate Assign Command

AGCH
Stops
SDCCH

T3120
Initial MS message
(Location Update Request
CM Service Request
Paging Response
CM Reestablishment Request
IMSI Detach)

Abnormal Cases
No Channel ( SDCCH ) available
BTS

BSC

Channel Request
Channel Required
Immediate Assignment Reject

Immediate Assign Command

Stops T3120
Starts T3122
Immediate Assignment Reject
Request Reference 1 -- EC, Ref no, Fr.No
Wait Indication -- T3122
.........
Request Reference 5 -- EC, Ref no, Fr.No
Wait Indication -- T3122

Immediate Assignment Command

Channel Number -- AGCH
Message type -- Immd Assgn Reject
Request Reference 1 -- EC, Ref no, Fr.No
Wait Indication -- T3122
.........
Request Reference 5 -- EC, Ref no, Fr.No
Wait Indication -- T3122

Abnormal Cases

Lower Layer Failure on MS before establishment on SDCCH

-----

Allocated Channels are released

MS returns to Idle Mode
Transaction is process are aborted
Cell reselection may take place

Timer T3101 on Network expires before MS responses

-- Allocated Channels are released
-- Request Forgotten

RACH Collisions
TWO Mobiles Send RACH at same Frame No
with same Reference No and EC
If
both strong

YES

No
One may reach and one may not reach
Network assigns AGCH with the same RRN
Both will tune to SDCCH
One will release the channel during setup

Both rejected
and follow the
Re-transmission
Process
B

ALOHA Process

RACH

RACH

T3120

Rejected

Re-transmission

AGCH

T3120

AGCH

T3120 = 3 - 12,14,16,20,25,32,50 RACH Slots

Maximum Re-transmission = 1,2,4,7
For every Re-transmission T3120 is randomly generated

Traffic Planning/Expansion Planning

-- One RACH reaches one does not

RACH
RACH
Both Wait for AGCH
Immediate Assignment
Both tune to SDCCH
SABM ( Initial Message )
SABM ( Loc Upd Req )

Initial Message = IMS

UA ( Initial Message )
UA ( Initial Message )
DROPS ( since IMSI mismatches )

MM - Common Procedures

TMSI Reallocation Procedure

Authentication Procedure
Identification Procedure
Ciphering *
IMSI Detach Procedure
* Ciphering is not a MM procedure, but since it is linked with other
procedures discussed here , it is covered in this section

TMSI Reallocation

Loc Upd ( IMSI )

TMSI Allocation
Call Setup ( TMSI )
TMSI Reallocation

TMSI REALLOCATION

Purpose

Provide identity confidentiality

Operational Requirements

TMSI is an unambiguous identity associated with LAI

Must be performed at change of Location Areas
Initiated in ciphered mode
Can also be associated with some other procedure

TMSI REALLOCATION

MSC
TMSI Reallocation Command

TMSI Realacation Complete

TMSI Reallocation Complete

No Elements

T3250

Stops
T3250

TMSI Reallocation Command

Location Area Identification
Mobile Identity : TMSI / IMSI

Benchmarking
Authentication
Purpose
-- To verify Subscriber Identity ( IMSI and SIM )
-- To provide a new ciphering key to the Mobile Station
Operational Requirement
-- at each registration
-- at every call attempt ( MOC & MTC ) ( left to operators , but should be done
for visiting subscribers )
-- before performing some supplementary services activation, de-activation,
registration or erasure
-- required for Location Updating for roaming
-- not mandatory prior to IMSI Attach and Detach
Authentication process is always initiated and controlled by the network

Authentication

Ki

RAND

Ki
RAND

A3
A3

SRES
SRES

MM - Common Procedures

Authentication
MSC
Authentication Request

Authentication Response

Authentication Request

T3260

Stops
T3260

Ciphering Key Sequence No -- Values ( 0-6 ) , 7 = No key

Authentication Parameter RAND - 128 bits Random Number
Authentication Response
Authentication Parameter SRES -- 32 bits Signed Response

MM - Common Procedures
Unsuccessful Authentication
Authentication Reject
BTS

MSC

BSC
Authentication Req

Authentication Req

Data Request

T3260

Authentication Resp
Data Indication
Authentication Resp

Authentication Rej

Data Request

Sets Authentication Failure Flag

Waits for Connections to be released
Delete its TMSI,LAI,Ciphering Key, CKSN
Return to IDLE no IMSI state

Authentication Rej

Invalid SRE
Stops
T3260

RR- Connection
Release procedure
initiated

Authentication Reject
No elements

MM - Common Procedures

Abnormal Cases
Expiry of timer T3260
MSC
Authentication Request

Authentication Request

Starts
T3260
T3260 Expires
Re-Starts
T3260

Authentication Reject

T3260 Expires
RR - Connection Release
Procedure initiated

MM - Common Procedures

Identity Check

Identity Check ( IMEI )

Sends IMEI

EIR

White listed / Grey listed / Black listed ?????

MM - Common
Procedures
Identification

MSC requests the Mobile to send its identity , for verification

Identity could be IMSI, TMSI,IMEI
IMEI shall only be sent in ciphered mode

MSC
Identity Request

Identity Response

Identity Request
Identity type : IMSI / IMEI / TMSI

T3270

Stops
T3270
Identity Response
Mobile Identity

MM - Common Procedures

Identification
Abnormal Case
Expiry of timer T3270
MSC
Identification Request

Identification Request

Starts
T3270
T3270 Expires
Re-Starts
T3260
T3270 Expires

Releases RR - Connection

MM - Common Procedures
Ciphering

Purpose
-- privacy of speech and data
-- privacy of signaling information

Operational Requirements
-- Implementation dependent
-- Ciphering should be done before confidential signaling information is passed
( Called Number, Calling Number, TMSI )
* Note : IMSI and IMEI are also confidential signaling information ,but they require physical
protection

MM - Common Procedures
RAND

Ki

Ciphering

A8

Frame No
Kc

A5

Ciphering Stream

Information Bits ( 114 )

XOR

Ciphered
Bits

MM - Common Procedures

Ciphering
MSC

BSC

BTS

Cipher Mod Cmd

Cipher Mod Cmd
Start ciphering
& deciphering
correct L2 frame
Ciph Mod Comp

Encryption Cmd
start deciphering

start ciphering
Data Indication

Cipher Mode Command

Cipher Mode setting :
No Ciphering
Start Ciphering

Cipher Mode Complete

Encryption Command
Channel Number
Encryption Information :
Algorithm Identifier
Key
L 3 Information

Cipher Mode Comp

Cipher Mode Command

Layer 3 Header Information
Algorithm Identifier : No encryption/
A5 / 1
Key : Ciphering key

Calculation of Diffraction Loss

Ciphering Key Sequence No ( CKSN )

Authentication Request ( RAND + CKSN )

Ki

A3/A8

Authentication Response ( SRES )

FNo
( Kc + CKSN )

Network
( CKSN

( stored in MS

( stored in SIM )

Channel Request
Immediate Assignment
Initial Message ( CKSN )
If CKSN Checked , No authentication

Network

IMSI Detach Procedure

Purpose

To mark the Mobile as inactive in the network

Conditions

Mobile Station Power down

SIM is removed

Operation

If no RR-connection exists, RR-connection will be first established

If RR-connection exists, then all MM - connections will be first released
If Location Update procedure is On, than it will be finished, then this procedure will
be started

IMSI Detach Procedure

MSC
IMSI Detach Indication

Starts
T3220

Marks MS as detached in VLR

Will not sent any page

Wait for RR-Connection Release

If T3220 expires, MS will localy release

RR-Connection

IMSI Detach Indication

PD : MM
TI : 0
MT : IDI
Mobile Station Classmark 1
Mobile Identity

Abnormal Case
RR-Connection cannot be established or RR-

Connection is lost before message is sent, then the

IMSI detach is aborted by the MS

Importance of Location Area

L.Area = 1

L.Area = 2

Reduce Paging Load

Resource Planning

L.Area = 3

What is Location
Update ?

MSC should know the Location of the Mobile for paging.

Mobile is continuously changing Location Area.
Mobile when changes Location Area informs the MSC about its new L.A

Process of informing MSC about new Location Area is Location Update

Location Update

L.Area = 1

L.Area = 2

L.Area = 3

Location Updating
Procedure
IMSI Attach

-- Power on in same LAI

-- Compliment to Explicit IMSI Detach
Normal Location Update

-- Change in LAI due to mobility

-- Power on in new LAI
-- MS unknown in VLR as a response to Connection establishment request
Periodic Updating

-- Expiry of Periodic Update Timer ( T3212 )

-- In the event of MS out of Service , on exit, MSC will mark it as Implicit
Detach in the VLR
-- Timer is reset to "0" on any Loc Update, first MM message recd , MS
responded to page, on expiry of timer

Okumura Model
Location Update is done at VLR or VLR and HLR
Update at VLR
-- When MS roams into a new Location Area
-- Periodically

Update at HLR
-- When MS registers in a new VLR
-- When MS registers in the same VLR, but MSC Location Area has changed
and HLR requires new routing information
-- On HLR or VLR Restoration

Location Update Signaling Diagram

BTS
Channel Req

Immediate Assgn
Loc Upd Req ( SABM )

Auth Req
Auth Resp

Channel Reqd
Channel Activation
Chan Actvn Ack
Imm Assgn Cmd
Establish Ind

Data Request
Data Ind

Data Request
Loc Upd Accept

MSC

BSC

Complete Layer 3 Info

Authentication Request

Authentication Response

Loc Upd Accept

Clear Command
Clear Complete

Location Update Procedure

BTS
( SABM ) Loc Upd Req

BSC

Establish Indication

Starts
T3210

MSC

( CR )Comp Layer 3 Info

( UA ) Loc Upd Req

MM - Security Procedures
Data Request
Loc Upd Accept
Stops
T3210

Loc Upd Request : MS Identity(IMSI/TMSI), Classmark, and OLD LAI

Loc Upd Accept

Location Update
Procedure
Abnormal Cases

Location Update Rejection

BTS

BSC

Data Request

MS
Loc Upd Reject

Loc Upd Reject

Stops
T3210
Stores the Reject Cause
Starts
T3240

Location Update Reject

Reject Cause
-- IMSI Unknown
-- PLMN not allowed
-- LA not allowed
-- TMSI not allocated

Location Update
Procedure
Abnormal Cases on MS side

Random Access Fails

No response to RACH after max_retransmissions

Timer T3213 is started
MS goes for a cell reselection, with return to cell inhibited for 5 secs
After 5 secs , the MS returns to the cell where Random access failed
On expiry, procedure is initiated again

Mobile Originated Call

Channel Request
Immediate Assign
Service Request
Authentication
Ciphering
Set Up
Call Proceeding
Assignment
Alerting
Connection

CC - Call Establishment Procedures

Mobile Originated Call

MS
Channel Req

Imm Assgn
CM Serv Req

MSC

BSC

BTS
Channel Reqd
Channel Actvn
Chan Actvn Ack
Imm Assgn
Establish ind

CL3 Informtn

Authentication
CM Service Accept
Cipher Mode Setting and TMSI Reallocation
Set Up
Call Proceeding
Assgn Cmd
Assign Comp

Assgn Cmd

Assgn Req

Assign Comp

Assign Comp

Alert
Connect
Connect Ack
Speech

CC- Call Establishment

Procedure
Service Request
MSC
CM Service Request
Starts
T3230 & T303

CM Service Accept
Stops
T3230
CM Service Request

CM Service Accept
PD : MM TI : 1-7 MT : CSR
--- No Information Elements

PD : MM TI : 1-7 MT : CSR
CM Service Type : MOC , Emergency Call, SMS transfer, SS activation
Ciphering Key Sequence Number : 000 - 111
Mobile Station Classmark 2 : Power , Revision , Encryption,Frequency, SMS
Mobile Identity : IMSI, TMSI , IMEI

CC - Call Establishment
Procedures
Abnormal Case

CM Service Rejection
MSC

CM Serv Reject
Stops
T3230

Network starts RR connection

release

T3230 Expires
-- Mobile aborts the RR connection

CM Service Reject
Reject Cause
#4 : IMSI unknown in VLR
#17 : Network Failure
#22 : Congestion
#32 : Service Option not supported
#33 : Requested Service option not subscribed
#34 : Service option temporarily out of order
#38 : Call cannot be identified

CC - Call Establishment Procedures

SETUP
MSC
Setup

Call Proceeding
Stops
T303
Starts
T310
Setup

Call Proceeding
PD : CC TI : 1-7 MT : CP
Repeat Indicator : Used for in-call modification procedure
Bearer Capabilities : Included if the network has to specify the
connection element
Progress Indicator : *

PD : CC TI : 1-7 MT : S
Bearer Capabilities : *
Mobile Identity : IMSI, TMSI , IMEI
Calling Party Sub-Address : X.213 / ISO 8348 AD2 coding , user specifed coding
Called Party Sub-Address : X.213 / ISO 8348 AD2 coding , user specifed coding
User -User : Convey information between the MS & the remote ISDN user. *

CC - Call Establishment Procedures

Abnormal Cases
Invalid Call Information
MSC
Setup

Release Complete

Stops
T303
Releases the MM connection
Returns to Idle Mode

Release Complete
PD : CC TI : 1-7 MT : RC
Cause : See next page

CC - Call Establishment Procedures

1 Unassigned ( unallocated) number
3
6
16
17
18
19
21
22
26
27
28
29
30
31
34
38
41
42
43

No route to destination
Channel unacceptable
Normal clearing
User busy
No user responding
User alerting, no answer
Call rejected
Number changed
Non selected user clearing
Destination out of order
Invaid num format( incomplete num )
Facility Rejected
Response to Status Enquiry
Normal, unspecifed
No circuit / channel available
Network out of order
Temporary failure
Switching equipment congestion
Access information discarded

44 requested circuit/chan unavailable

47
49
50
57
58
63
65
69
70
79
81
88
91
95
127

Resources unavailable,unspecified
Quality of Service unavailable
Requested facility not subscribed
Bearer Capability not authorized
Bearer Capability not presently available
Service or option not available
Beare Service noit implemented
Requested facility not implemented
Only restricted data capability available
Service or option not implemented
Invalid transaction identifier value
Incompatible destination
Invalid transit network selection
Invalid message, unspecified
Interworking, Unspecified
# 96 - # 101 = Protocol error
102 Recovery on timer expiry

CC - Call Establishment Procedures

Channel Assignment

MSC
Assignment Command
TCH
Assignment Complete
( FACCH )

CC - Call Establishment
Procedures

Assignment Command
PD : RR TI : 0 MT : AC
Channel Description

Channel type & TDMA offset

00001
0001T
001TT
01TTT

Channel Mode : signaling only,

speech full rate,
speech half rate
Data- 9.6 / 4.8 / 2.4 kbps full
Data- 9.6 / 4.8 / 2.4 kbps half

-- TCH / F
-- TCH / H
-- SDCCH/ 4
-- SDCCH/ 8
T indicates the subchannel
Timeslot Number : 0 - 7
TSC : BCC - 0 - 7
Hopping Channel : Single , Hopping
Channel Selector : For single Channel -- Band Number, ARFCN
For Hopping Channel -- MAIO ( 0 - 63 ), HSN ( 0 - Cyclic

1 - 63 = Algorithm )
Power Command : Power Level ( 0 to 31 )
Cell Channel Description : Used to decode the Mobile Allocation table
Mobile Allocation table

CC - Call Establishment Procedures

Abnormal Cases

MSC
Assignment Command
SDCCH
Assignment Complete
( SDCCH )

Assignment Failure
PD : RR TI : 0 MT : AF
RR Cause : No cell allocation available
Invalid Message
Invalid Information element contents
Protocol Error

CC - Call Establishment Procedures

Alerting

MSC
Alerting

Stops
T310

Alerting
PD : CC TI : 1 -7 MT : A
Progress Indicator :
Coding standard - Q.931 , GSM
Location - connected element ( explained earlier )
Progress Indicator - In band information
or appropriate pattern ( RBT,BT ) now available

CC - Call Establishment Procedures

Call Connection

MSC
Connect
Connect Acknowledge

Connect
Connect Acknowledge
PD : CC TI : 1 -7 MT : C
PD : CC TI : 1 -7 MT : C
Progress Indicator :
---- no information elements
Coding standard - Q.931 , GSM
Location - connected element ( explained earlier )
Progress Indicator - In band information
or appropriate pattern ( RBT,BT, Connection tone )
now available

Emergency Calls
-- GSM Specs define ' 112' as emergency number
-- '112' is accessible with or without SIM
-- Without SIM it is sent on the best channel
-- Mobile on sensing '112' sets the establishment
cause to emergency call in the RACH
-- Routing of this call can be done to a desired
location defined in the Switch.

CC - Call Establishment Procedures

Emergency Calls
Service Request
MSC
CM Serv Request
CM Service Accept
Emergency Setup
Call Proceeding

CM Serv Request
PD : MM TI : 1-7 MT : CSR
CM Service Type : Emergency Call
CKSN : 000 - 111
Mobile Station Classmark 2 :
Mobile Identity : IMSI, TMSI , IMEI

Emergency Setup
PD : CC TI : 1-7 MT : CSR
Bearer Capability : Only significance is for full rate/
half rate speech coding

CC - Call Establishment Procedures

Call Re-establishment

MSC
CM Re-estb Request
CM Service Accept
Assignment Command (TCH)

Conditions:

Call Re-establishment should be allowed in the cell

Occurs only on lower layer failure ( RF Link )
Mobile should be in active mode on TCH
New cell should be in the same BSC
Re-establishment will occur within 20 secs

Paging
Paging is process by which Mobile receives incoming calls
Mobile has to monitor the paging channel to receive paging messages
Mobile will not monitor all paging channels, it will monitor the channel specific
to its CCCH_Group and Paging Group

CCCH_ GROUP

BCCH defines the number of PCHN ( timeslots ) supporting CCCH

CCCH can be allocated only to TN 0,2,4,6
CCCH will have the same structure on all allocated timeslots ( 9 blocks )
Each PCHN supporting CCCH is alloted a CCCH_Group No ( range : 0 .. 3 )
Each CCCH_Group carries its own group of Mobiles.
Mobiles will listen to paging messages and send RACH's only in their specific group

0
B
9 blocks

1
D

2
C
9 blocks

C
9 blocks

6
C
9 blocks

7
T

Paging Group

Within the CCCH_Group , Mobile listen to paging in specific paging (CCCH) blocks only
The block specific to a mobile is its Paging Group

TN
0

CCCH_GROUP

Paging Group

Paging
How to derive CCCH_Group and Paging Group for a mobile ?
Let us understand some parameters required to achieve this .

1. BS_CC_CHANS : Total No of PCHN supporting CCCH ( Sys Info Type 3 )

Range : 1 - 4
2. BS_AG_BLKS_RES : Blocks reserved for AGCH
3. BS_PA_MFRMS : Multiframe Repetition rate
4. IMSI : 15 digit Mobile Identity

We will now understand 2 & 3

Paging
BS_AG_BLKS _RES

51 Frame Combined ( B + D )Multiframe Structure [ TN 0 ]

F S

F S

F S

F S

F S

51 Frame Multiframe Non-Combined ( B ) structure [ TN 0 ]

F S

F S

F S

F S

F S

I I

Additional PCHN supporting CCCH ( B+C)

I

I I

I I

Each BCCH and CCCH block = 4 Frames

CCCH = AGCH + PCH
For Non-Combined & B+C, CCCH = 9
For Combined ,
CCCH = 3

Paging
BS_AG_BLKS _RES
--- Some CCCH Blocks can be reserved for AGCH
--- This parameter broadcasted on BCCH informs the Mobile
about the number of blocks reserved for AGCH
The value for Non-Combined MF structure ranges between 0 - 7
For combined MF structure it ranges between 0-2
Example

51 Frame Combined ( B + D )Multiframe Structure [ TN 0 ]

F S

F S

F S

F S

F S

51 Frame Multiframe Non-Combined ( B ) structure [ TN 0 ]

F S

F S

F S

F S

F S

I I

Additional PCHN supporting CCCH ( B+C)

I

I I

I I

Paging
Available Paging Blocks on 1 CCCH_Group

Available Paging Blocks = CCCH Blocks -- bs_ag_blks_res

Maximum AGCH Reservation for Non-Combined = 7
Available Paging Blocks = 2
Maximum AGCH Reservation for Combined
= 2
Available Paging Blocks = 1
Mimimum AGCH Reservartion for Non-Combined = 0
Available Paging Blocks = 9
Minimum AGCH Reservation for Combined
=0
Available Paging Blocks = 3
No of Paging Blocks will have a range of 1 - 9

Reducing Time Dispersion Issues

BS_PA_MFRMS
-- No of Multiframes after which Same Paging Group is repeated
-- This Parameter is broadcasted on BCCH
-- Ranges between 0 -- 9 Multiframes
F S

F S

F S

F S

F S

P0

P1 I
MF 2

F S

F S

F S

F S

F S

P2

P3 I
MF 3

F S

F S

F S

F S

Mobile belonging to Paging Group P0 will remain idle during P1 ,P2,P3

Mobile utilizes power only during PO. This is known as DRX

F S

P0

P1 I

Paging
Total No of Paging Groups on 1 CCCH_Group ( N )

No of Paging Groups = Paging Blocks x Repitition of Paging BLock

N = [ CCCH - bs_ag_blks_res ] x bs_pa_mfrms

Range of Paging Groups on 1 CCCH_Group

Minimum Available Paging Groups = Min Pag blocks x Min bs_pa_mfrms
= 1 x 1 = 1
Maximum Available Paging Groups = Max Pag blocks x Max bs_pa_mfrms
= 9 x 9 = 81

Paging

How does a Mobile knows it CCCH_Group Paging Group No ?

CCCH_Group = [ ( IMSI mod 1000 ) mod ( BS_CC_CHANS x N ) ] div N

Pag Grp No = [ ( IMSI mod 1000 ) mod ( BS_CC_CHANS x N ) ] mod N

N = Total Paging Groups = No of Paging Blocks x bs_pa_mfrms

Would you like to do an

exercise ?
Calculate the CCCH_Group & Paging group for a Mobile with IMSI
404001234765898 in a cell with 2 PCHN's for CCCH and 7 blocks
reserved for AGCH, and paging group repetition is after 5
multiframes ?
C=1 & P=8

Paging
Paging Procedures

MSC

BSC
Paging

( IMSI/TMSI, IMSI, LAI )

BTS

Calculates Pag Grp No

for cells of LAI

Pag Req
Type1/2/3

Paging Command

( IMSI or TMSI,Pag Grp No)

BTS packs some paging requests and sends them together in Paging Requests messages on Air
Interface.
The Mobile on the other hand listens to it corresponding Paging Group On getting a Paging Message
belonging to its IMSI/TMSI it sends a response
* Detailed Paging Procedure will be explained with Mobile Terminated Calls

Frequency Planning
Packing of Paging Requests

Paging Request Type 1

----->

2 IMSI or 2 TMSI

Paging Request Type 2

----->

2 TMSI and 1 IMSI or TMSI

Paging Request Type 3

----->

4 TMSI

Paging Mode
Normal mode : Paging Message is specific Paging Group only
Full Mode : Paging Message for that group can occur in any Paging Block
Extended : If paging message has more data, it follows in next block

Mobile Terminated Call

Paging
Channel Request
Immediate Assign
Paging Response
Authentication
Ciphering
Set Up
Call Confirmed
Assignment
Alerting
Connection

Mobile Terminated Call

MS
Paging Request
Channel Req

Imm Assgn
Paging Response

MSC

BSC

BTS

Paging Command

Paging

Channel Reqd
Channel Actvn
Chan Actvn Ack
Imm Assgn
Establish ind
CM Service Accept
Security Procedures
Set Up
Call Proceeding
TCH Assignment
Alert
Connect
Connect Ack
Speech

CL3 Informant

Paging
BTS

MSC

BSC

Paging Command

Paging
Starts
T3113

Paging Request 1/2/3

Paging Request 1
Paging

Message Type : P
PD : RR TI : 0 MT : PR
IMSI : 15 digits
Page Mode : Normal, Extended
TMSI : ( omitted if not used )
Re-organization, Same as before
Cell Identifier List :
Mobile Identity : IMSI, TMSI
Cell Id Discrimtr - CGI,LAC & CI,
Mobile Identity : IMSI, TMS
CI,LAC, All cells
-------------------------------------------------------------------------------Paging Request 2
Paging Request 3
Paging Command
TMSI
TMSI
TMSI
TMSI
Channel Number : PAGCH
Mobile Identity : IMSI, TMSI
TMSI
Paging Group :
TMSI

CC - Call Establishment
Procedures
SETUP

MSC
Setup
Call Confirmed
Setup
PD : CC TI : 1-7 MT : S
Bearer Capabilities : *
Mobile Identity : IMSI, TMSI , IMEI
Calling Party BCD Number : Number of the calling party
User -User : Convey information between the MS & the remote ISDN user. *
Call Confirmed
PD : CC TI : 1-7 MT : CP
Repeat Indicator : Used for in-call modification procedure
Bearer Capabilities : Included if the network has to specify the
connection element
* Detailed explained earlier in
MOC

Alerting
Alerting

MSC

Connect
Connect Acknowledge

Alerting
PD : CC TI : 1 -7 MT : A
Progress Indicator :
Coding standard - Q.931 , GSM
Location - connected element ( explained earlier )
Progress Indicator - In band information
or appropriate pattern now available

Active Mode Procedures

Mobile in Active Mode
-- Mobile receives the signal strength of the serving cell
-- Mobile transmits
-- During the Idle timeslots measures signal strength of neighbor

BTS

0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 I I I I I I I 0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 I I I I I I I

Measurement Period Available to Mobile

End of Reception to start of Transmission is = 2 Timelsots
End of Transmission to start of Reception is = 4 Timeslots
End of Transmisson in 25th frame to start = 12 Timelsots
of reception in 1st frame in next MF

--- Mobile does measurement of neighbors in last two cases only

Measurements in Active Mode

Measurements are made over each SACCH multiframe .

SACCH multiframe is 104 TDMA frames(480ms) for TCH and 102 TDMA
frames (470.8ms) for a SDCCH.

MS shall make a RxLev measurement in every TDMA frame on at least one

of the BCCH carriers indicated in the BA one after another .

Measurements on the frame preceding the idle frame may be optionally

omitted to allow more time to MS for BCCH synchronization.

If frequency hopping is used and if BCCH carrier is in the hopping sequence

and PWRC indicator is set , then the BCCH carrier bursts will not be used in
the averaging process for RxLev, but for RxQual it will be used.

Measurements made during the previous recording period are to be

discarded.

Measurements in Active Mode

Full and Sub
Rxlev_Full & RxQual_Full : Measurements taken over full set of TDMA frames
Full set of TDMA frames : 102 for SDCCH
Full set of TDMA frames : 104 TCH
Rxlev_Sub & RxQual_Sub : Measurements taken over subset of TDMA frames
If even one frame is not transmitted in the measurement
period,
then it is considered as subset
of TDMA frames.

When are sub measurements done practically ?

When DTX used, and the receiver enters the DTX mode , then the measurement is done over all the frames
is not valid.

With DTX, if there is completely no speech for 480ms, then still there will be 8 frames of SID and 4
frames of SACCH, these 12 subset frames will be used for sub measurements .

DTX is not used on BCCH carrier (all timeslots) , hence if the call is on a TCH which is on a BCH carrier,
then it will always be FULL, and in the measurement report both Sub and Full values will be same.

DTX is not used on the SDCCH also , hence the above clause applies to this also.

On a TCH carrier, when DTX was used by the BTS in the previous 480ms period, measurement is Sub,
else it is full.

If Frequency Hopping was used, and BCH carrier was a part of it, and dowlink power control is used,
then the measurements for Rx_Lev will always be sub ( since BCH carrier frames are not included in the
measurement averaging)

Mobile in Active Mode

--- Mobile also has to verify Neighbor ARFCN by decoding BSIC
--- BSIC can be decoded by getting SCH of neighboring cells which is on its TS 0
--- Mobile uses the Idle time slot to locate TS0 of neighbor
Will the mobile hit SCH on TS0 of neighbor ?
--- TCH MF is 26 and CCH MF is 51 ( non-divisible )
--- Sliding Multiframe Cycles helps mobile in getting SCH ( next pg )
--- As seen, Within 11 cycle, idle TS will align with SCH ( about 1.2 seconds )
--- Within 10 secs mobile will be able to decode BSIC of 6 neighbors
--- MS shall keep on decoding the BSIC for each carrier at least one in 10s

TCH Multiframe

T T T T T T T T T T T T A T T T T T T T T T T T T

25
I

0 T 2 3 4 5 6 7 0 I I I I I I I

Sliding Multiframe Cycle

S B B B B C C C C

S C C C C C C C C

C C
C CC
S C C

C C C

C C C C C

C C C C C C C

A T

0
T

T
T

I
T

A T

TI

TT TT

A T

TI

T
T

A T

TT TT TI

A T

TT TT TT

A T

TT TT TT

A T

TT TT TT

A T

TT TT TT

1325
T

A T

TT TT IT

Measurement Reporting

--- Mobile sends the measurement report to the BTS in every SACCH Frame
--- Measurement Report is of 18 octets and takes 4 SACCH bursts
--- It takes 480ms to send 1 Measurement Report

TCH Multiframe 1

25 0

TCH Multiframe 2

25

T T T T T T T T T T T T A T T T T T T T T T T T T I T T T T T T T T T T T T A T T T T T T T T T T T T I

120ms

SACCH Report From Mobile

Layer 1 Header
--- MS Tx Power Level
--- Timing Advance
Serving Cell
-------------

BCCH Indicator
DTX( indicates whether DTX was used by the MS in measurement period )
RXLEV ( 0 - 63 ) = ( -110dbm to -48dbm )
RXQUAL ( 0 - 7 ) = ( > 0.2 % to 12.8 % )

Neighbouring Cells ( 6 )
------------

No of cells measured
RXLEV of each cell ( 0 - 63 ) = ( - 110dbm to -48dbm )
ARFCN of each cell
BSIC of each ARFCN

The MS has to take at least 32 samples for each measurement

Measurement on BTS
Measurement Result from BTS
--- BS Power
--- Received Signal Strength on Uplink ( --110dbm to -48dbm )
--- Receive Quality on Uplink ( BER >0.2 % to 12.8 % )
--- Layer 3 MS Info ( Measurement Report send by MS )
--- Layer 1 MS Info ( MS Power & Timing Advance )

The BTS has to take at least 32 samples for each measurement

of RxLev and RxQual

Measurement Averaging
--- The BSC Averages the Measurement received after a set
period ( Hreqave )
--- The averaging could be following types :

Unweighted Average

Weighted Average

Modified Median

Hreqave : Averaging Period for Rxlev,Rxqual &

Timing Advance
( In terms of SACCH Frames
( 480ms ). Range : ( 1, 31 )

Exercise !!!
MS --> BTS
(SACCH)

Report
Number

Rxqual

Rxlev(s)

N1

-98

-100

-98

-97

-90

-94

----

-102

----

----

-100

-98

-102

-98

-90

-96

----

-----

-101

----

3
4

5
2

-102
-99

-96
-97

-------

-97
-96

-94
-97

-99
-100

---104

-101
-99

-102
-101

-99
----

5
6
7
8
9
10

6
5
1
5
5
5

-105
-103
-97
-104
-104
-105

-100
-95
-98
-103
-95
----

-100
-----99
----

-99
-96
-94
-96
-95
-94

-99
-99
-97
-94
-95
-96

-----------99
-98

----------------100

-97
-96
-94
-94
-96
-97

-98
-99
-98
-96
-98
-98

----102
-100
------------

Result
Number

Rxqual

Rxlev

-99

-97

3
4
5
6
7
8
9

4
3
5
5
0
4
5

-103
-100
-103
-102
-97
-102
-102

10

-104

N2

BTS

N3

N4

+
( Abis )

N5

N6

N7

N8

BSC

Generate the Measurement

Results table at BSC if
HREQAVE = 2

N9

Answer
Downlink Measurements

Uplink Measurements

Averg
Number

Rxqual

Rxlev(s)

Result
Number

Rxqual

Rxlev

2.5

-99

-98

2
3
4
5

3.5
5.5
3
5

-100.5
-104
-100.5
-104.5

2
3
4
5

3.5
5
2
5

-101.5
-102.5
-99.5
-102.5

Neighbour Measurements
Averg
Number

N1

N2

N3

-99

-100

-97.5

-90

-95

----

-102

-101

-96.5

----

-96.5

-95.5

-99.5

-104

-100

-101.5

-97.5

-100

-97.5

-99

----

----

-96.5

-98.5

-100.5

---

-95

-95.5

---

----

-94

-97

-100

-95

----

-94.5

-95.5

-98.5

-100

-96.5

-98

-----

N4

N5

N6

N7

N8

N9
----99
----

Power Control Procedure

MS Power
Control MS

BSC

BTS

MS Power Control
SACCH

MS Power Control
Channel Number :
MS Power : Power step 1 to
31

BS Power Control ( optional )

MS

BSC

BTS
BS Power Control

BS Power Control
Channel Number :
BS Power : Power step 1 to 31

Handover

Cell 1

Cell 2

Handover is a process by which the control/communication of a Mobile is transferred from

one cell to another

Criteria for Handover

--- Receive Quality (RXQUAL) on Uplink & Downlink.

--- Receive Signal Strength (RXLEV) on Uplink & Downlink.
--- Distance ( Timing Advance ).
--- Interference Level.
--- Power Budget.

Internal Inter-Cell Handover

SYNCHRONISED

BTS
C0

C0

Internal Inter-Cell Handover

Non-synchronized
BTS

MSC

BSC

BTS

--- This type of Handover takes place if the cell to which

which handover is to be done belongs to the same BSC.
--- In this the BSC handles everything without involving MSC.
--- The MSC will be informed by the BSC after Handover.

Inter-Cell Handover Procedure

BTS
(Old)

MS

BTS
(New)

BSC

MSC

CH Actvn

Hand CMD
Hand Access

CH Actvn Ack

DR ( Hand Cmd )
Starts
T3103

Starts
T3124

Hand Detec
Phys Info

Stops
T3124

Hand Complete

Any Correct Frame

RF CH Release

DI ( Hand Comp )
Stops
T3103

Hand Performed
RF CH Release Ack

Inter-Cell Handover

Starts
T3105
Stops
T3105

Inter-cell Handover Procedure

Synchronous
MS

BSC

BTS(Old)

BTS(New)

Handover Detection

Hand CMD

MS

Handover Access

BTS starts transmission on the activated channel with ciphering

BTS starts transmission on SACCH also
MS sends Handover Access burst in four successive slots, immediately starts ciphering & starts
sending and receiving information.
BTS on receiving the correct Handover Access Burst starts reception on the activated channel

Asynchronous
MS

BTS(Old)

Hand CMD

MS
BTS(New)
Handover Access
Handover Detection
Physical Info
Starts

BSC

T3105
Stops
T3105

Correct
Frame

BTS starts transmission on the activated channel with ciphering,but not on SACCH
MS starts T3124,sends Handover Access burst continously, activates deciphering, starts reception
BTS sends a Physical Information Message, starts T3105, starts transmission on SACCH , also starts
reception on main ch.
MS stops T3124 and starts the normal transmission and reception on the main channel

Starts
T3124

Inter-Cell Handover
Procedure
BTS(Old)

MS

BTS(New)

BSC

Handover Detection

Hand CMD

Starts
T3105

Handover Access
Physical Info
Correct Frame

Stops
T3105

Handover Access
TB
8

MS

SYNCH
41

Information
36

8 bits
Handover Reference No

TB
3

GP

6 bits
BSIC

( BSIC is XOR with Parity Bits )

Physical Information

Handover Detection

PD : RR TI : 0 MT : HC
Timing Advance : 0 - 63 bits

Channel Number : TCH ,SDCCH/4,SDCCH/8

TN No ,Subchannel No
(SDCCH )

Inter-Cell Handover Procedure

BTS(Old)
RF Channel Release

BTS(New)

BSC

MS

Handover Complete

DI (Handover Complete)
Stops
T3103

MSC
Handover Performed

Handover Performed
Message Type : HP
Cause : Uplink Quality,Uplink Strength
Uplink Strength,Downlink strength
Distance, O & M Intervention, Call Control,
Better Cell, Equipment Failure,No Resource

Handover Complete

PD : RR TI : 0 MT : HC
RR Cause : Normal Release ( of old channels

Cell Indentifier : *
Cell identification discriminator :
-- Whole CGI/ LAC&CI / CI only
Cell identification 1 : MCC + MNC + LAC + CI
Radio Channel Identity : *
Channel Description, MA table, Starting time

* Optional

Inter-Cell Handover
Procedure
Abnormal Cases
MS

BTS(Old)

BSC

BTS(New)

Handover Detection

Hand CMD

MS

Handover Access
T3124 Expires
( asynchronous )

Lower layer failure

occurs
MS Deactivates new
channels
Activates Old Channels, &
sends

DI (Handover Failure)

Handover Failure

Stops
T3103

Handover Failure

MS resumes normal operation

( as no handover attempt had
occurred )

PD : RR TI : 0 MT : HC
RR Cause : Abnormal Release ( unspecified ), Channel Unacceptable, timer expired,
Invalid Message( unspecified ), No CA available, Protocol errors

S
T

External Inter-Cell Handover

BSC

BTS

MSC

BSC

BTS

--- In this type of Handover,the Mobile is handed over to a cell which belongs to another
BSC.
--- The MSC is completely involved in this Handover

External Inter-Cell Handover Procedure

BTS

MS

MSC

BSC(Old)

BSC(New)

BTS

Hand Reqd
Starts
T7

Hand CMD

DI(Hand CMD)

Hand CMD

Hand Reqst
Hand Reqst Ack

CH Actvn
CH Actvn Ack

Stops
T7

Hand Access
Hand Detect

Phy Info

Hand Detection

Hand Comp
Clear CMD

Hand Comp

INTER - BSC Handover

DI(Hand Comp)

External Inter-Cell Handover Procedure

BTS

MS

BSC(Old)

MSC

BSC(New)

BTS

Hand Access
Phy Info

Hand Detect

Hand Detection

Hand Comp
Hand Comp

DI(Hand Comp)

Handover Command

Handover Command

Message Type : HC

Message Type : HC
RR Cause : Normal Release ( old channels ) Optional

External Inter-Cell Handover Procedure

Abnormal Case
MS

BSC(Old)

Handover Failure

Handover Failure

BSC(New)

MSC

Clear Command

Handover Failure
PD : RR TI : 0 MT : HC
RR Cause : Abnormal Release ( unspecified ), Channel Unacceptable, timer expired,
Invalid Message( unspecified ), No CA available, Protocol errors

Handover Failure

PD : RR TI : 0 MT : HC
Cause : Radio Interface Failure , reversion to old channel
RR Cause : Abnormal Release ( unspecified ), Channel Unacceptable, timer expired
Invalid Message( unspecified ), No CA available, Protocol errors

Intra-Cell Handover

BTS

Interference

Handover on Interference is based on RXQUAL & RXLEV

If RXQUAL is poor and RXLEV is good , then Handover takes place

Interference Handover is an Intra-cell Handover

Intra-Cell Handover
BTS

MS

BSC
Channel Activation
Channel Actvn Ack

Assignment Command
Old Channel

DR ( Assgn Command)
Starts
T10

Assignment Complete

DI ( Assgn Complete )
Stops
T10
RF Channel Release

New Channel

RF Channel Release Ack

Channel Activation
Channel Number :
Activation Type : intra cell handover
Channel Mode :
Channel Identification :
Encryption Information :
BS Power, MS Power , Timing Advance:
BS & MS Power Parameter :

CC - Call Clearing

Release of Call

MSC
TCH
F
A
C
C
H

Disconnect
Starts
T305
Release
Stops
T305
Release Comp
Channel Release

Disconnect
PD : CC TI:1 -7 MT : D
Cause : #16 - Normal Clearing
#38 - Network Out of
Order

Release

Channel Release

PD : RR TI : 0 MT : CR
Cause : - Normal Release
- Abnormal Release, unspecified
- No activity on radio path
Release Complete
- Preemptive release
- No CA available ( handover )
PD : CC TI:1 -7 MT : R Cause :
Not reqd
PD : CC TI:1 -7 MT : R
Cause : Not reqd

Radio Link Failure

Radio Link Failure is based on SACCH Messages

It is controlled by the Radio Link Counter ( S )

The max value of ' S ' is broadcasted on BCCH

If Mobile is not able to decode SACCH message

' S ' decreases by 1

If Mobile is able to decode SACCH message

' S ' increases by 2

If ' S ' reaches 0 , Radio Link failure is declared

Radio Link Failure

BCCH = ' S ' is 4

1
0
SACCH Blocks

Radio Link Failure in Idle

Mode

Idle Mode Link Failure depends on the counter DSC

DSC is initialized to the nearest integer of 90 / Bs_pa_mfrms.

For every Paging Message non-decode ( BFI=1), DSC is decreased by 4.

For every successful decode, it is increased by 1.

Once DSC reaches "0", link failure is declared and Mobile does cell reselection.

Database/Parameter Optimization

GSM Features Before proceeding to database parameters,

let us discuss some important GSM features which are
commonly being used in current networks.

GSM networks worldwide are mainly affected by the

following types of problems:- 1) Coverage issues, 2)
Interference issues, 3)Capacity issues.

Interference in GSM networks can be reduced significantly

by using some special features, as mentioned

Frequency Hopping

DTX and Voice Activity Detection

Dynamic Power Control

Database Optimization Frequency Hopping

Frequency hopping is one of the standardised capacity

enhancement features in GSM system. It offers a significant
capacity gain without any costly infrastructure requirements.

Frequency hopping can co-exist with most of the other

capacity enhancement features and in many cases it
significantly boosts the effect of those features.

Frequency hopping can be briefly defined as a sequential

change of carrier frequency on the radio link between the
mobile and the base station.

When frequency hopping is used, the carrier frequency is

changed between each consecutive TDMA frame. This means
that for each connection the change of the frequency may
happen between every burst.

Database Optimization Frequency Hopping

At first, the frequency hopping was used in military

applications in order to improve the secrecy and to make the
system more robust against jamming.

In cellular network, the frequency hopping also provides some

additional benefits such as frequency diversity and
interference diversity.

Database Optimization Frequency Hopping

Frequency

Call is transmitted through several

frequencies in order to
average the interference (interference diversity)
minimise the impact of fading (frequency diversity)

F1
F2
F3

Time

Database Optimization Frequency Hopping

There are two methods of frequency hopping in GSM,

Baseband Frequency Hopping (BB FH) and Synthesised
Frequency Hopping (RF FH).

In the baseband frequency hopping the TRXs operate at

fixed frequencies.

Frequency hopping is generated by switching consecutive

bursts in each time slot through different TRXs according to
the assigned hopping sequence.

The number of frequencies to hop over is determined by the

number of TRXs

Database Optimization Frequency Hopping

The first time slot of the BCCH TRX is not allowed to hop, it
must be excluded from the hopping sequence.

This leads to three different hopping groups.

The first group doesnt hop and it includes only the BCCH
time slot.

The second group consists of the first time slots of the nonBCCH TRXs.

The third group includes time slots one through seven from
every TRX.

Database Optimization Baseband Hopping

RTSL 0
TRX-1

TRX-2

f1

B = BCCH timeslot. It does not hop.

f2

Time slots 1...7 of all TRXs

hop over (f1,f2,f3,f4).

TRX-3

f3

TRX-4

f4

Time slot 0 of TRX-2,-3,-4 hop over f2,f3,f4.

Baseband hopping (BB FH).

Database Optimization RF Hopping

In the synthesised frequency hopping all the TRXs except

the BCCH TRX change their frequency for every TDMA
frame according to the hopping sequence.

Thus the BCCH TRX doesnt hop.

The number of frequencies to hop over is limited to 63, which

is the maximum number of frequencies in the Mobile
Allocation (MA) list.

Database Optimization RF Hopping

TRX-1

B = BCCH timeslot. TRX does not hop.

Non-BCCH TRXs are hopping over

f1,

f1,
f2,

. . . .

the MA-list (f1,f2,f3,...,fn) attached to the cell.

f2,

f3,

f3,

fn

fn

TRX-2

Synthesised hopping (RF FH).

Database Optimization RF Hopping

The biggest limitation in baseband hopping is that the number

of the hopping frequencies is the same as the number of
TRXs.

In synthesised hopping the number of the hopping

frequencies can be anything between the number of hopping
TRXs and 63.

Database Optimization Frequency Hopping

BB-FH

F1(+ BCCH)

TRX-1

F2
F3

TRX-3

Dig.
MSC

MS does not see

any difference

Frequency

F1
F2
F3

RF

BSC
TCSM

Time

RF-FH

TRX-1

F1, F2, F3

TRX-2

BCCH

Dig.

RF
BB-FH is feasible with large configurations
RF-FH is viable with smaller configurations

The difference between BB and RF FH.

Database Optimization RF Hopping Cell

Allocation

The Cell Allocation (CA) is a list of all the frequencies

allocated to a cell. The CA is transmitted regularly on the
BCCH.

Usually it is also included in the signaling messages that

command the mobile to start using a frequency hopping logical
channel. The cell allocation may be different for each cell.

In PGSM 900 the CA list may include all the 124 available
frequencies [GSM 04.08].

However, the practical limit is 64, since the MA-list can only
point to 64 frequencies that are included in the CA list .

Database Optimization RF Hopping Mobile

Allocation

The MA is a list of hopping frequencies transmitted to a

mobile every time it is assigned to a hopping physical channel.

The MA-list is automatically generated if the baseband

hopping is used.

If the network utilises the RF hopping, the MA-lists have to

be generated for each cell by the network planner.

The MA-list is able to point to 64 of the frequencies defined

in the CA list

However, the BCCH frequency is also included in the CA list,

so the practical maximum number of frequencies in the MAlist is 63.

The frequencies in the MA-list are required to be in

increasing order because of the type of signaling used to
transfer the MA-list.

Database Optimization RF Hopping HSN

The Hopping Sequence Number (HSN) indicates which

hopping sequence of the 64 available is selected.

The hopping sequence determines the order in which the

frequencies in the MA-list are to be used.

The HSNs 1 - 63 are pseudo random sequences used in the

random hopping while the HSN 0 is reserved for a sequential
sequence used in the cyclic hopping.

The hopping sequence algorithm takes HSN and FN as an

input and the output of the hopping sequence generation is a
Mobile Allocation Index (MAI) which is a number ranging
from 0 to the number of frequencies in the MA-list
subtracted by one.

The HSN is a cell specific parameter.

Database Optimization RF Hopping MAIO

When there is more than one TRX in the BTS using the same
MA-list the Mobile Allocation Index Offset (MAIO) is used
to ensure that each TRX uses always an unique frequency.

Each hopping TRX is allocated a different MAIO. MAIO is

added to MAI when the frequency to be used is determined
from the MA-list.

MAIO and HSN are transmitted to a mobile together with

the MA-list.
The MAIOoffset (Nokia) is a cell specific parameter defining
the MAIOTRX for the first hopping TRX in a cell. The MAIOs

for the other hopping TRXs are automatically allocated

according to the MAIOstep-parameter

Database Optimization RF Hopping MAIO

For this TDMA frame the output from the algorithm is 1

FN & HSN GSM Hopping algorithm

MAI(0...N-1) =

MA INDEX
(MAI)

MA

1
1 + MAIOTRX

MAIOTRX
TRX-1
0
TRX-2
1
TRX-3
2

N-2

N-1

f1

f2

f3

f4

fN-1

fN

TRX-1 TRX-2 TRX-3

MAIOOFFSET ,
User definable

These parameters
are set
automatically

Database Optimization RF Hopping MAIO

Step

The MAIOstep is a Nokia specific parameter used in the MAIO

allocation to the TRXs.

The MAIO for the first hopping TRXs in each cell is defined by the
cell specific MAIOoffset parameter

MAIOs for the other hopping TRXs are assigned by adding the
MAIOstep to the MAIO of the previous hopping TRX

MAIOTRX(N) =

MAIOoffset + MAIOstep(n-1)

Database Optimization RF Hopping MAIO

Sector TRX # HSN

1
2
3
4
1
2
3
4
1
2
3
4

MAIO stepMAIOoffsetl MAIO

Non-hopping BCCH TRX

7
2
0
0
2
4
Non-hopping BCCH TRX
7
2
6
6
8
10
Non-hopping BCCH TRX
7
2
12
12
14
16

+MAIO step

MAIO step indicates the

difference between the MAIOs of
successive TRXs in a cell.

Example of the use of the MAIO related parameters.

Database Optimization RF Hopping Reuse

patterns

When RF Hopping is deployed the BCCH layer is planned using

the standard 4X3 or 7X3 or an intermediate suitable pattern.

Maximum protection is assigned while planning to the BCCH

layer as it is critical to call setup procedure.

For the TCH layer there are mainly three types of widely
used reuse patterns

1X1 All sectors in the network use a single MA list.

1X3 3 MA lists are created. Sec A of each cell uses MAL1,

Sec B uses MAL2 and Sec 3 uses MAL3

Ad-hoc/Mixed SFH Multiple MA lists are used. Can have as

many MA lists as the number of sectors in the network. The
reuse is based on fractional loading * with a maximum loading
factor of 100 %.

Database Optimization RF Hopping Loading

Factor

Loading Factor This is the ratio of no of TRX to the no of

hopping frequencies in the MA list

Loading Factor = No of Hopping TRX/No of Frequencies.

For eg. Loading factor = 50 % if there are 2 TRX and 4

hopping frequencies.

Lowest practically achievable loading factor is 33 %for

1X3, 17 % for 1X1 and highest is 100 % .

Usually 100% loading factor is used in case of ad-hoc RF

hopping, for cells with higher configuration (6-6-6),
however for lower configuration like (2-2-2) 50 %
loading factor could be used.

In case of ad-hoc hopping the loading factor can be

planned to be specific to the cell configuration.

Database Optimization DTX & Power Control

Power control and the DTX are standard GSM features,

which are designed to minimise the interference.

These are mandatory features in the UL, but it is up to the

network operator to decide whether to use them or not.

DTX prevents unnecessary transmissions when there is no

need to transfer information

Power control is used to optimise the transmitted signal

strength so that the signal strength at the receiver is still
adequate.

These features can be individually activated for uplink and

downlink.

Operators have been widely using both features in UL

direction mainly in order to maximise the battery life in
mobiles.

Database Optimization DTX & Power Control

In a non-hopping network these features provide some quality

gain for some users, but this gain cannot be transferred
effectively to increased capacity, since the maximum
interference experienced by each user is likely to remain the
same.

The power control mechanism doesnt function optimally

because the interference sources are stable causing chain
effects where the increase of transmission power of one
transmitter causes worse quality in the interfered receiver,
which in turn causes the power increase in another
transmitter and so on.

This means that, for example, one mobile located in a

coverage limited area may severely limit the possibility of
several other transmitters to reduce their power.

Database Optimization DTX & Power Control

In a non-hopping network these features provide some quality

gain for some users, but this gain cannot be transferred
effectively to increased capacity, since the maximum
interference experienced by each user is likely to remain the
same.

The power control mechanism doesnt function optimally

because the interference sources are stable causing chain
effects where the increase of transmission power of one
transmitter causes worse quality in the interfered receiver,
which in turn causes the power increase in another
transmitter and so on.

This means that, for example, one mobile located in a

coverage limited area may severely limit the possibility of
several other transmitters to reduce their power.

Database Optimization DTX & Power Control

In a random hopping network the quality gain provided by

both features can be efficiently exploited to capacity gain
because the gain is more equally distributed among the users.

Since the typical voice activity factor (also called DTX

factor) is less than 0.5, DTX effectively cuts the network
load in half when it is used.

The power control works more efficiently because each user

has many interference sources. If, one interferer increases
its power, the effect on the quality of the connection is not
seriously affected. In fact, it is probable that some other
interferers are decreasing their powers at the same time.
Thus, the system is more stable and chaining effects
mentioned earlier do not occur frequently.

Database Optimization DTX & Power Control

Reuse 3/9, TU 3km/h

PC on
DTX on
PC on, DTX on

Reuse 3/9, TU 50km/h

GAIN:
1.4 dB
2.3 dB
3.7 dB

PC on
DTX on
PC on, DTX on

GAIN:
1.0 dB
2.3 dB
3.5 dB

C/I improvement

The simulated gain of PC and DTX with FH.

Database Optimization DTX & Power Control

DTX has some effect on the RXQual distribution.

Normally the BER is averaged over the duration of one

SACCH frame lasting 0.48 seconds and consisting of 104
TDMA frames.

However, four of these TDMA frames are used for

measurements, so that only 100 bursts are actually
transmitted and received.

When DTX is in use and there is no speech activity, only the

bursts transmitting the silence descriptor frame (SIDframe) and the SACCH are transmitted.

When there are periods of no speech activity, the BER is

estimated over just the bursts carrying the silence
descriptor frame and the SACCH. This includes only 12
bursts over which the BER is averaged (sub quality).

Database Optimization DTX & Power Control

BER gets averaged much more effectively when DTX is not

used yielding to a quality distribution where the proportion of
moderate quality values is enhanced.

The sub quality distribution is wider than the full quality

distribution, meaning that more good and bad quality samples
are experienced.

The differences between full and sub quality distributions

are largest in frequency hopping networks utilising low
frequency allocation reuse, since in that kind of networks the
interference situation may be very different from burst to
burst.

A couple of severely interfered bursts may cause very bad

quality for the sub quality sample when they happen to occur
in the set of 12 bursts over which the sub quality is
determined.

Database Optimization DTX & Power Control

The full quality sample of the same time period has probably
only moderate quality deterioration because of the better
averaging of BER over 100 bursts.

In a real network utilising DTX the quality distribution is a

mixture of full and sub quality samples.

The proportions of full and sub samples depend on the speech

activity factor also known as the DTX factor.

The differences in the BER averaging processes cause

significant differences in the RXQUAL distributions. These
differences should be taken into account when the RXQUAL
distributions of networks utilising and not utilising DTX are
compared.

Database Optimization DTX & Power Control

1/1 reuse 15 freqs
40.00 %

35.00 %

30.00 %

25.00 %

RxQ full
RxQ sub

20.00 %

15.00 %

10.00 %

5.00 %

0.00 %
Q0

Q1

Q2

Q3

Q4

Q5

Q6

Q7

The distribution of normal RXQual and subRXQual values in a

frequency hopping network.

Database Optimization DTX & Power Control

Power Control what to optimize??

The parameters to optimize in case of power control are the

window settings.

BS Tx Power

Database Optimization DTX & Power Control

+ 42

- 75

Downlink Rxlev (dBm)

-95

Downlink Power Control Typical Rxlev Window settings

BS Tx Power

Database Optimization DTX & Power Control

+ 42

Downlink RxQual

Downlink Power Control Typical RxQual Window settings

MS Tx Power

Database Optimization DTX & Power Control

+ 33

- 70

Uplink Rxlev (dBm)

-90

Uplink Power Control Typical Rxlev Window settings

Database Optimization DTX & Power Control

Power Control parameters which can be set

Downlink/Uplink Rxlev threshold (l_rxlev_dl_p /

l_rxlev_ul_p)

RxQual threshold(l_rxqual_dl_p / l_rxqual_ul_p)

Power increment/reduction step size

(pow_inc_step_size_dl/pow_red_step_size_d)

Dynamic step adjust algorithm(dyn_step_adj)

Database Optimization DTX & Power Control

Power Control Features

Objective is to reduce average interference

In case of uplink also helps in saving battery power

Algorithm works on measurement reports sent by the MS

every 480 ms (SACCH frame)

Downlink power control cannot be applied to BCCH carrier

Uplink power control is mandatory but downlink power control

is not mandatory. Feature selectable by the operator.

For controlling interference in the network the operator uses

DTX, Power Control and Frequency Hopping. These features
effectively act as combined forces in interference reduction
and improved call quality.

Database Optimization
Typical problems which GSM subscribers experience are

Coverage issues

Voice quality issues

Access issues/congestion

Handover related issues

Dropped calls

Database Optimization
BSS Parameters are broadly classified into the following groups

Access related parameters

Call handling/Handover related parameters

Congestion related parameters

Database Optimization

Database Optimization IDLE Mode Cell

Selection

The MS uses a "path loss criterion" parameter C1 to

determine whether a cell is suitable to camp on [GSM 03.22]

C1 depends on 4 parameters:

1. Received signal level (suitably averaged)

2. The parameter rxLevAccessMin, which is broadcast on the

BCCH, and is related to the minimum signal that the operator
wants the network to receive when being initially accessed by an
MS

3. The parameter msTxPwrMaxCCH, which is also broadcast on

the BCCH, and is the maximum power that an MS may use when
initially accessing the network

4. The maximum power of the MS.

Database Optimization IDLE Mode Cell

Selection
Cell Selection in IDLE Mode, based on C1
Radio Criteria
C1 =(A - Max(B,0))
A =Received Level Average- p1
B =p2 - Maximum RF Power of theMobileStation
p1 =rxLevelAccessMin
p2 =msTxPowerMaxCCH

Database Optimization IDLE Mode Cell

Selection
Cell Reselection

In case of reselection from one cell to another in the same location

area the C1 value of target cell must be higher than source cell

In case of reselection to a target cell in a different location area

the C1 value must be greater than that of the source cell by a
database parameter cell_reselect_hysteresis

Cell Reselection C2

C2 is an option GSM feature which can only be used for cell

reselection, it can be enabled or disabled on a cell basis.

If C2 parameters are not being broadcast the C1 process is used for

reselection.

Database Optimization IDLE Mode Cell

Selection
Cell Reselection C2

C2= C1 + cell_reselect_offset temporary offset * H

(penalty_time T) (for penalty_time <31)

H= 0 if T > penalty_time

H= 1 if T < penalty_time

C2= C1 cell_reselect_offset (for penalty_time= 31)

Why C2??

Cell Prioritisation

As a means of encouraging MSs to select some suitable cells

in preference to others

Database Optimization IDLE Mode Cell

Selection
Example of C2 usage

In dualband network-- to give different priorities for

different band

In multilayer-- to give priority to microcell for slow moving

traffic

Any other special case where specific cell required higher

priority than the rest

Cell Reselection Strategy

Positive offset-- encourage MSs to select that cell

Negative offset-- discourage MSs to select that cell for the

duration penalty Time period

Database Optimization

Database Optimization Handovers

Handover

The handover (HO) process is one of the fundamental

principles in cellular mobile radio, maintaining the call in
progress whilst the mobile subscriber is moving through the
network.

In idle mode the MS does a cell reselection, whereas in

dedicated mode the MS performs a handover.

Handovers are mainly classified into two types

A) Inter cell handovers

B) Intra cell handovers

Inter cell handovers further classified as

Inter BSS ie between two cells belonging to different

BSCs

Intra BSS ie between two cells belonging to same BSC

Database Optimization Handovers

Handover

Intra cell handovers is the switching of call from one

channel/TRX to another TRX within the same cell/BTS. This
is an optional feature which can be enabled on a cell basis.
Intra cell handovers usually take place when the Rxqual on
the source channel deteriorates.

Handover process may be initiated due to the following main

reasons

Radio Criteria

To maintain receive level/receive quality

Absolute MS-BS distance

Power Budget

Network Criteria

Traffic load (to manage traffic distribution)

Database Optimization Handovers

Handovers also classified as imperative/non-imperative based

on the reason for which the process is triggered.

The cause value contained in the handover recognised

message will affect the evaluation process in the BSC.

Handover causes may be prioritized as follows

1. Uplink Quality

2. Uplink Interference

3. Downlink Quality

4. Downlink Interference

5. Uplink Level

6. Downlink Level

7. Distance

8. Power Budget

Database Optimization Handovers

Power budget handover

If an MS on a allocated resource during its measurement

reporting process sees another channel that would provide an
equal or better quality radio link requiring a lower output
power then a handover may be initiated.

Handovers due to power budget ensure that the MS is always

linked to the cell with minimum pathloss though the quality
and level thresholds may not be exceeded.

Handover to the target cell takes place when PBGT>

hoMarginPBGT

PBGT = (msTxPwrMax Av_Rxlev_DL_HO (btsTxPwrMax

BTS_TXPWR)) (msTxPwrMax(n) Av_Rxlev_NCELL(n))
where n nth adjacent cell which is a handover candidate

Database Optimization Handovers

Power budget handover

hoMarginPBGT is a parameter which can be set on a cell to

cell basis. Each cell may have a different value for each
neighbour cell which is a candidate for power budget
handover.

hoMargin is expressed in dB and is usually set to 4. However

this may be reduced if the handover needs to be speeded or
increased to 6 or higher to prevent ping-pong or to delay
handovers

In some cases negative homargin may also be used.

Database Optimization Handovers

Handover Algorithms

Handover algorithms are used in addition to default

parameters to control the handover process

These algorithms assist in mobility management and are

effective in traffic distribution.

The algorithms have an important role to play in GSM

networks which use multi-band or multi-layer architectures.

Database Optimization Handovers

Handover Algorithms

In Motorola system there are 7 procedures. These are set by

the parameter pbgt_alg_type. The algorithms are briefly
defined as follows:

Type 1 Conventional GSM PBGT

Type 2 Restricted PBGT for macro cells

Type 3 PBGT with Rxlev as qualifier

Type 4 PBGT with time in cell as qualifier

Type 5 PBGT with delay since neighbour level exceeds

threshold as qualifier

Type 6 Delayed power budget using dynamic handover

margin

Type 7 PBGT algorithm to avoid adjacent channel

interference

Database Optimization Handovers

Handover Algorithms

Of the seven, the most commonly used are Type1, 2, 3 and 7.

Each handover candidate cell can be defined as one of the

seven types of neighbour to the source cell.

Handover per cause

The handover per cause statistic is a counter-array statistic

which counts the reason for each handover event on all cells
for which it is enabled.

This statistic gives important information about the handover

performance of the cells and can be used for troubleshooting
cells which have high handover failure rate.

Database Optimization Handovers

Handover per neighbour

This statistic gives the value of no of handover attempts as

well as successes for each neighbour cell. This statistic is
also helpful in troubleshooting handover performance, it can
be used to identify neighbour relations which have a high
handover failure rate

The handover per neighbour statistic can also be used for

neighbourlist pruning.

Database Optimization

Database Optimization TRHO/Congestion

Related Parameters
TRHO What does it do??

TRHO effectively reduces the service area of the congested

cells

Increases service area of under-utilised target cells

HO is triggered using a special parameter

amhTrhoPbgtMargin instead of hoMarginPbgt

General guideline:

Target cell Rxlevaccessmin should be set higher to

avoid bad downlink Rxqual after HO

amhTrhoPbgtMargin must be lower than hoMarginPbgt

Database Optimization TRHO/Congestion

Related Parameters
TRHO/BSC Parameters

amhUpperloadthreshold This parameter determines

minimum traffic load threshold at which cell starts to intiate
TRHO default value 80 %

amhMaxLoadOfTargetCell This parameter determines

maximum traffic load threshold beyond which target cell will
not accept TRHO hand-ins default value 60 %

TRHO/BTS Parameters

amhTrhoPbgtMargin This parameter is new Pbgt margin

when cell exceeds amhUpperloadthresh. Its the revised
power budget margin which replaces the normal Pbgt
definition when the Trho criteria are met default value is 5
dB.

Database Optimization TRHO/Congestion

Related Parameters
TRHO/Adjacency Parameters

trhoTargetLevel This parameter determines the minimum

RSSI of the valid target cell candidate reported by the
mobile default is 85 dBm

Database Optimization TRHO/Congestion

Related Parameters
Directed Retry

A transition (handover) from SDCCH in one cell to a TCH in

another cell during call setup due to unavailability of an empty
TCH within the first cell.

To control traffic distribution between cells to avoid a call

rejection.

Can be used for both MOC and MTC

Setting guidelines:

drThreshold should be higher than Rxlevmincell

(Rxlevaccessmin); else the improved target cell selection
criteria will be ignored.

Database Optimization TRHO/Congestion

Related Parameters
Congestion Relief

This procedure is initiated when an MS is assigned to an

SDCCH, requires a TCH and none are available.

Two options are offered for deciding how many handover

procedures are actually initiated.

First Option The no. of HO procedures initiated is at most

the no. of outstanding requests for a TCH.

Second Option This allows for initiation of a HO procedure

for each MS that meets the modified criteria to support the
feature.

RF Optimization Analysis and troubleshooting

Things which normally subscribers normally experience
(common problems)

No coverage/poor coverage issues.

Dropped calls.

Failed handovers/Dominant server issues.

Breaks in speech/crackling sound or bad voice quality.

Access related problems Network Busy.

Often all the above problems are addressed to the RF

optimization team for resolution

RF Optimization Poor Coverage Issues

Poor Coverage Issues

Coverage problems are one of the most concerning issues.

Subscribers experience a No network or Network Search

scenarios on the fringe area of the cells.

Mostly these problems are experienced in suburban areas and

also in many cases inbuilding coverage problems occur.

Analysis is simple

TEMS equipment/test phone displays Rxlev of serving cell

and neighbour cells Generally problem occurs when Rxlev
drops below 95 dBm. When the Rxlev drops to 100 dBm or
lower the subscriber experiences a fluctuating single bar or
a network search scenario.

When Rxlev (DL) drops below 95 dBm its very difficult to

have successful call setup, as typically the uplink Rxlev would
be much lower.

RF Optimization Poor Coverage Issues

Poor Coverage Issues (Steps to solve the problem)

Analyze the extent of area which is experiencing a coverage

problem

Can this be solved by physical optimization??

Possible steps would be to improve the existing serving cell

strength by proper antenna orientation or up-tilting the
antenna.

If it is an indoor coverage/limited area coverage issue, this

could be resolved by deploying a repeater/micro cell if the
traffic requirement in the question area is high.

In case of rural/suburban cells where the concern is a weak

uplink TMA could be installed.

RF Optimization Drop Call Troubleshooting

Dropped Calls

Dropped calls may be attributed to several reasons.

Usually categorized as

Drop during call setup aka SDCCH Drop.

Drop during call progress aka TCH Drop.

Drop due to failed handovers with no recovery.

Call drops may occur due to RF/non RF reasons.

RF Reasons attributing to dropped calls

Weak coverage RL timer times out.

Interference low C/I bad Rxqual RL timer times out.

Faulty TRX resulting in low C/I call may drop during

setup or after TCH assignment RL timer may/may not
time out.

RF Optimization Drop Call Troubleshooting

Dropped Calls

Non RF Reasons

Switch related MS experiences a Downlink Disconnect

abnormal release, usually with a Cause Value.

CV 47 is a common example Layer 3 message DL

Disconnect.

Non RF related call drops need to be escalated to isolate

the fault which could be related to the switch/transcoder
or at any point in the Abis/A Interface.

RF Optimization Handover Problems

Handover Failures/Problems

Handover failures may also be attributed to different

reasons.

Usually occur due to RF reasons.

Common RF reasons for handover failures

Interference Co BCCH/Co BSIC issue.

Faulty hardware on target cell.

Improper neighbourlist definition

Steps to identify and solve Handover issues.

Use TEMS (layer 3 messages) to identify the cell to which

the MS attempts handover and results in a failure

RF Optimization Handover Problems

Steps to identify and solve Handover issues.

The sequence of layer 3 messages

Handover Command

Handover Access

Handover Complete

Handover Failure

Sometimes the sequence of messages would be

Handover Command

Handover Access

Handover Failure

RF Optimization Handover Problems

Steps to identify and solve Handover issues.

The Handover Command message contains information about

the BCCH and BSIC of the target cell to which the handover
was attempted. Check for any possible Co BCCH/Co BSIC
interferers.

Check for possible hardware faults on the target cell.

Neighbourlist problems

Sometimes handover problems occur due to improper

neighbourlist definition.

Neighbour Rxlevel are reported to be strong, but Handover

Command does not get initiated.

Call drags on the source cell and in some situation drops.

Most common cause is improper definition of neighbour

BSIC/BCCH

RF Optimization Handover Problems

Steps to identify and solve Handover issues.
Neighbourlist Problems

Crosscheck with RF BSC dump to confirm the BCCH/BSIC

and other parameters of the target cell.

Report any inconsistencies to the OMCR personnel.

RF Optimization Special Tools

Traditional RF Optimization

Traditional RF Optimization involves drive testing for data

collection

Drive testing is periodically done to monitor the network

performance

Mainly two types a)Long call continuous data collection

b) Short call for statistical analysis

Drive tests provide inputs for optimizing coverage and quality

of the network.

Usage of simulation/coverage prediction tools like PLANET,

ASSET, NETPLAN, etc.

Usually the simulation tool also contains an AFP component or

is available as a separate tool.

RF Optimization Special Tools

Traditional RF Optimization

Simulation tools work on standard prediction models.

Variety of standard models could be used Okumura Hata,

Lees model, Cost 231, etc.

Some tools have customized models (e.g Motorola Netplan

uses XLOS model which works on virtual heights)

Inputs used by the prediction tool digital terrain data,

clutter data, in some cases clutter heights.

Model tuning process a must to achieve near accurate

predictions from the tool.

RF Optimization Special Tools

Limitations of Traditional RF Optimization

Drive test data only simulates traffic generated from onroad subscribers. Indoor traffic is not simulated!!

Simulation tools work in a GIGO(garbage in garbage out)

fashion.

The model generated by a simulation tool highly depends on

the accuracy of the input data (terrain, clutter data,etc.).
Clutter/buildings change continuously needs to be updated
often.

Often tedious and iterative process.

Optimization works on a trial-and-error basis.

For good results its necessary to have detailed local

knowledge of city, subscribers, terrain, clutter.

RF Optimization Special Tools

Solution??

OEM vendors/Third Party vendors have developed special

tools which make the optimization process simpler.

These tools work on mobile statistics aka measurement

reports

The measurement reports are sent by each MS in the

network every 480 milliseconds.

The MRs provide accurate information about the network as

seen by the MS

MRs have information about serving cell and 6 neighbour cells

This information can be used effectively for generating a

model which is much more accurate than prediction model
generated by standard prediction tools.

RF Optimization Special Tools

Solution??

MRs are generated by all subscribers on road, inbuilding, fast

moving, slow moving, etc.

Example of tools which work on measurement reports/mobile

statistics currently available

IOS (Intelligent Optimisation Services) patented by

Motorola.

SCHEMA GSM Forte.

Worldwide many GSM operators have opted for these tools

and have found satisfactory results.

RF Optimization Special Tools - IOS

MOTOROLA IOS

Motorola Inc has developed a very powerful tool.

Initially known as IOP (Intelligent Optimization Product)

Currently Motorola markets it as a service hence IOS

(Intelligent Optimization Service)

This tool is an integration of

Powerful collection platform which connects to BSS and

interrogates the BSS for collection of MRs

Analysis platform which includes integration of CTP(call

trace product), Cellopt AFP.

Cellopt AFP uses interference matrix generated using the

MRs

Easy to use Windows NT GUI

RF Optimization Special Tools - IOS

MOTOROLA IOS

Motorola IOS cycles can be run to conduct the following

optimization activities

Hardware Optimization

Neighbourlist Optimization

Physical Optimization

Frequency Plan (fixed, hopping, various patterns)

Motorola is in process of conducting trials for MVIOS

(Multivendor IOS) which supports other OEM vendors like
Nokia, Ericsson, etc.

RF Optimization Special Tools Schema GSM

Forte
SCHEMA GSM FORTE

SCHEMA(based in ISRAEL) has developed an efficient

product called GSM Forte

This tool also uses mobile statistics/measurement reports.

GSM Forte currently supports Nokia, Ericsson and Alcatel.

Development is ongoing to support other vendors like Nortel,
Siemens, etc.

GSM Forte also uses interference matrix generated from

mobile statistics. The product offers

Frequency Plan Optimization

Neighbourlist Optimization

Database parameter Optimization (will be included in

future versions)

RF Optimization Special Tools Schema GSM

Forte
SCHEMA GSM FORTE

GSM Forte has been widely adopted by several GSM

operators across the globe.

Effective in generating fast and accurate frequency plans and

day to day neighbourlist optimization.

Hutch India major customer in India.

Strategic partnership with GTL for providing presales, post

sales, tech-support, premium services to its various
customers in India and other regions.

Succesfully implemented trial optimization project and 2

premium services project.!! These projects were
independently implemented by us.

THANK YOU

www.gtllimited.com