Professional Documents
Culture Documents
5 samples/ARFCN spread
over 3 to 5 secs
Locks on to best
A
Locks on to next
best in BA list
Yes
No
Cell
barred
No
No
C1 > 0
NC
matches
Yes
No
Yes
CAMP ON
A
www.gtllimited.com
No preferred list
Scans 124 ARFCN's
Location Update
No
IF
Found
Yes
No
Yes
Cell
barred
Yes
Successful
Next in BA list
No
C1 > 0
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.
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
1
S
1
11
21
31
41
S
2
S
3
S
4
S
5
50
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
Authentication Request
Authentication Response
RACH
Channel
Request
T3120
Re-transmission
T3120
Immediate Assignment
T3101
Response
AGCH
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
RACH
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
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
Abnormal Cases
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
RACH
RACH
Both Wait for AGCH
Immediate Assignment
Both tune to SDCCH
SABM ( Initial Message )
SABM ( Loc Upd Req )
UA ( Initial Message )
UA ( Initial Message )
DROPS ( since IMSI mismatches )
MM - Common Procedures
TMSI Reallocation
TMSI REALLOCATION
Purpose
Operational Requirements
TMSI REALLOCATION
MSC
TMSI Reallocation Command
T3250
Stops
T3250
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
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
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
EIR
MM - Common
Procedures
Identification
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
XOR
Ciphered
Bits
MM - Common Procedures
Ciphering
MSC
BSC
BTS
Encryption Cmd
start deciphering
start ciphering
Data Indication
Encryption Command
Channel Number
Encryption Information :
Algorithm Identifier
Key
L 3 Information
A3/A8
FNo
( Kc + CKSN )
Network
( CKSN
( stored in MS
( stored in SIM )
Channel Request
Immediate Assignment
Initial Message ( CKSN )
If CKSN Checked , No authentication
Network
Conditions
Operation
Starts
T3220
Abnormal Case
RR-Connection cannot be established or RR-
L.Area = 1
L.Area = 2
Resource Planning
L.Area = 3
What is Location
Update ?
Location Update
L.Area = 1
L.Area = 2
L.Area = 3
Location Updating
Procedure
IMSI Attach
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
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
Authentication Request
Authentication Response
BTS
( SABM ) Loc Upd Req
BSC
Establish Indication
Starts
T3210
MSC
Location Update
Procedure
Abnormal Cases
BSC
Data Request
MS
Loc Upd Reject
Stops
T3210
Stores the Reject Cause
Starts
T3240
Location Update
Procedure
Abnormal Cases on MS side
Channel Request
Immediate Assign
Service Request
Authentication
Ciphering
Set Up
Call Proceeding
Assignment
Alerting
Connection
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
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
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
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. *
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
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
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
MSC
Assignment Command
TCH
Assignment Complete
( FACCH )
CC - Call Establishment
Procedures
Assignment Command
PD : RR TI : 0 MT : AC
Channel Description
-- 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
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
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
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.
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
MSC
CM Re-estb Request
CM Service Accept
Assignment Command (TCH)
Conditions:
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
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 .
Paging
BS_AG_BLKS _RES
F S
F S
F S
F S
F S
F S
F S
F S
I I
I I
I I
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
F S
F S
F S
F S
F S
F S
F S
F S
I I
I I
I I
Paging
Available Paging Blocks on 1 CCCH_Group
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
F S
P0
P1 I
Paging
Total No of Paging Groups on 1 CCCH_Group ( N )
Paging
Paging
Paging Procedures
MSC
BSC
Paging
BTS
Pag Req
Type1/2/3
Paging Command
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
----->
2 IMSI or 2 TMSI
----->
----->
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
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
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
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
SACCH multiframe is 104 TDMA frames(480ms) for TCH and 102 TDMA
frames (470.8ms) for a SDCCH.
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)
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
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
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
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 )
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
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
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
----
BSC
BTS
MS Power Control
SACCH
MS Power Control
Channel Number :
MS Power : Power step 1 to
31
MS
BSC
BTS
BS Power Control
BS Power Control
Channel Number :
BS Power : Power step 1 to 31
Handover
Cell 1
Cell 2
SYNCHRONISED
BTS
C0
C0
MSC
BSC
BTS
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
RF CH Release
DI ( Hand Comp )
Stops
T3103
Hand Performed
RF CH Release Ack
Inter-Cell Handover
Starts
T3105
Stops
T3105
BSC
BTS(Old)
BTS(New)
Handover Detection
Hand CMD
MS
Handover Access
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
Physical Information
Handover Detection
PD : RR TI : 0 MT : HC
Timing Advance : 0 - 63 bits
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 )
DI (Handover Failure)
Handover Failure
Stops
T3103
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
S
T
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
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
DI(Hand Comp)
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
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
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
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
1
0
SACCH Blocks
Once DSC reaches "0", link failure is declared and Mobile does cell reselection.
Database/Parameter Optimization
Frequency Hopping
Frequency
F1
F2
F3
Time
The first time slot of the BCCH TRX is not allowed to hop, it
must be excluded from the hopping sequence.
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.
RTSL 0
TRX-1
TRX-2
f1
f2
TRX-3
f3
TRX-4
f4
f1,
f2,
. . . .
f2,
f3,
f3,
fn
fn
TRX-2
BB-FH
F1(+ BCCH)
TRX-1
F2
F3
TRX-3
Dig.
MSC
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
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 .
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.
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
MAIOOFFSET ,
User definable
These parameters
are set
automatically
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)
1
2
3
4
1
2
3
4
1
2
3
4
+MAIO step
For the TCH layer there are mainly three types of widely
used reuse patterns
PC on
DTX on
PC on, DTX on
PC on
DTX on
PC on, DTX on
GAIN:
1.0 dB
2.3 dB
3.5 dB
C/I improvement
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.
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
BS Tx Power
+ 42
- 75
-95
BS Tx Power
+ 42
Downlink RxQual
MS Tx Power
+ 33
- 70
-90
Database Optimization
Typical problems which GSM subscribers experience are
Coverage issues
Access issues/congestion
Dropped calls
Database Optimization
BSS Parameters are broadly classified into the following groups
Database Optimization
C1 depends on 4 parameters:
Cell Reselection C2
H= 0 if T > penalty_time
H= 1 if T < penalty_time
Why C2??
Cell Prioritisation
Database Optimization
Radio Criteria
Power Budget
Network Criteria
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
General guideline:
TRHO/BTS Parameters
Setting guidelines:
Dropped calls.
Analysis is simple
Usually categorized as
Non RF Reasons
Handover Command
Handover Access
Handover Complete
Handover Failure
Handover Command
Handover Access
Handover Failure
Neighbourlist problems
Drive test data only simulates traffic generated from onroad subscribers. Indoor traffic is not simulated!!
Hardware Optimization
Neighbourlist Optimization
Physical Optimization
Neighbourlist Optimization
THANK YOU
www.gtllimited.com