Call Setup Process and Failure Analysis

RADIO PLANNING AND
OPTIMISATION
Call Setup Analysis
Presentation/Discussion
March 2010
Objectives
This presentation will cover the
following:
System Information Messages
Types of Mobile Originating Call
Signalling Flow for Mobile Originating
Call
Call Setup Failures & Possible Causes
Kelvin George Kuyere, Snr RF

Engineer

Contain network parameters sent
to MS through air interface
These parameters are:
Network Identity Parameters
Cell Selection Parameters
System Control Parameters
Network Function Parameters

Engineer

Idle Mode
These are sent to the MS on BCCH

SYS INFO 1
Contains RACH control information and cell
channel description
These include the following:
Cell Frequency Allocation (CA list)
Maximum Retransmission Times (Max retrans)
Extended Transmission Timeslots (Tx_interger)
Cell Bar Access (CBA)
Common Access Control Level(AC)
Call Re-establish Permitted(RE)
Emergency calls permitted(EC)
Engineer

Idle Mode
SYS INFO TYPE 1 Message from
TEMS:

Engineer

Idle Mode
SYS INFO 2
Contains the following:

Neighbour cell description
NCC permitted
RACH control parameters (same as in
SYS INFO TYPE 1)

Engineer

Idle Mode
SYS INFO TYPE 2 Message from TEMS:

Engineer

Idle Mode
SYS INFO 3
Location Area Identity (MCC,MNC,LAC,CI)
Control Channel Description (reserved Access
Grant Blocks, CCCH Configuration, IMSI
Attach/Detach allowed, Paging Multiframes,
T3212)
Cell Option (Power control indication, DTX,
RLINKT)
Cell Selection (MS_TXPWR, ACCMIN, ACS,
NECI)
RACH control parameters (same as in SYS
INFO TYPE 1)
Engineer

Idle Mode
SYS INFO 3 Message from TEMS:

Engineer

Idle
Mode
SYS INFO 4
Cell Selection Parameters
RACH Control Parameters
CBCH Channel Description

Engineer
10

Idle
Mode
SYS INFO 4 Message from TEMS:

Engineer
11

Dedicated Mode
These are sent to the MS on SACCH

SYS INFO 5
Contains neighbour cell BCCH frequencies (Phase 1
Mobiles)
SYS INFO 5Bis
Contains neighbour cell BCCH frequencies which could
not fit in the limited space of TYPE 5 and belong to the
same band as serving BCCH
SYS INFO 5TER
Contains neighbour cell BCCH frequencies whose band
is different from serving BCCH (Dual Band Mobiles)

Engineer
12

Dedicated Mode
SYS INFO 5TER Message from TEMS:

Engineer
13

Dedicated Mode
SYS INFO 6
Cell Identity
LAI
Cell option
NCC Permitted

Engineer
14

Dedicated Mode
SYS INFO TYPE 6 Message from TEMS:

Engineer
15

Dedicated Mode
SYS INFO 7 and 8

These are optional messages, and
contains the following:
Additional Cell Reselection parameters
that were not included in SYS INFO 4.
SYS INFO 13
Contains information related to GPRS.
Only sent if SYS INFO 3, 4, 7 or 8
indicated GPRS support.

Engineer
16
Signalling Flow for MOC

Engineer
17
Mobile Originating Call -MOC

Types
Early Assignment
The network assigns the TCH+FACCH after sending CC
Call Proceeding and completes call setup on the FACCH
Late Assignment
The network does not assign the TCH+FACCH until after
alerting has started
Very Early Assignment
The network makes an immediate assignment on the
TCH+FACCH in the initial RR establishment and
performs the entire transaction on the FACCH
The SDCCH is not used
Engineer
18
Signalling Flow of MOC

MS
Channel Request (UL)- Using RACH
Networ
k
Immediate Assignment (DL)- Using

AGCH
Setup(UL)- Using SDCCH
Call Proceeding (DL)- Using SDCCH
Assignment Command (DL)- Using
SDCCH
Assignment Complete(UL)- Using FACCH on newly
assigned TCH
Alerting(DL)- Using FACCH
Connect(DL)- Using FACCH
Connect Acknowledgement (UL)- Using FACCH
SPEECH
Disconnect(UL)- Using FACCH
Channel Release(DL)- Using FACCH

Engineer
19
Signalling Flow MOC (Um Interface)

Channel Request (Sent on the uplink)
Sent by MS to the network (specifically to the BSC, via the BTS) when the calling
subscriber (A-party) presses the Call Button.
MS sends Channel Request message using the Random Access Channel (RACH).
Channel Request message contains the following:
Cause Value (Reason for requesting the channel)MOC
Random Reference Number
Channel Request Message from TEMS:

Engineer
20
Signalling Flow MOC (Um Interface) (Cont)

Immediate Assignment (Sent on downlink)
The network (BSC) responds to the Channel Request message
by sending Immediate Assignment message through the BTS
to the MS on the Access Grant Channel (AGCH).
Immediate Assignment message contains the following:
Details of the signalling channel being assigned
Request Reference Details
Depending on the type of MOC as described on slide 16, the
Immediate Assignment message will contain:
SDCCH description for Early Assignment and Late Assignment
TCH + ACCH description for Very Early Assignment
NOTE: In case of no Immediate Assignment sent to MS, the MS will
re-send another Channel Request to the network as defined by the
Parameter Maximum Retransmission, after which it will not send
again and Call Setup will have failed.
Engineer
21

Immediate Assignment Message from TEMS:

Engineer
22

Setup(Sent on uplink)
MS sends setup message to the MSC on
SDCCH, requesting the network to provide
requested connection.
The Setup Message contains the following:
Bearer Capabilities
B-number (called party) details
Setup message is also used to activate the
Call Waiting tone at the MS.

Engineer
23

Setup Message from TEMS:
NB: Authentication and Ciphering have been omitted

Engineer
24

Call Proceeding (Sent on the downlink)
MSC sends call proceeding message to MS on SDCCH
informing it that the requested connection is in
progress.
Call Proceeding Message contains the following:
Transaction ID which may be co-related to the
relevant SETUP message
Call Proceeding Message from TEMS:

Engineer
25

Assignment Command (Sent on the downlink)
BSC sends Assignment Command to MS on
SDCCH, providing the MS with details of radio
resource (TCH or PDTCH) to be used for the
requested connection.
Assignment Command message contains the
following:
Details of the traffic channel being assigned
Amount of power to be used by the MS

Engineer
26

Assignment Command Message from TEMS:

Engineer
27

Assignment Complete (Sent on the uplink)
MS sends Assignment Complete message to BSC
on Fast attributed Control Channel (FACCH) after
it has successfully switched to the assigned TCH
Assignment Complete Message from TEMS:

Engineer
28

Alerting (Sent on the downlink)
MSC sends Alerting message to MS on FACCH, informing
the MS that B-party is being alerted of the connection
The calling MS will at this point hear the ring-back
Alerting Message from TEMS:

Engineer
29

Connect (Sent on the downlink)
MSC sends Connect message to MS on FACCH when the
called party (B-party) picks presses the Answer Button.
This happens after the called party has answered the call
Calling MS switches over to voice on the assigned TCH
Connect Message from TEMS:

Engineer
30

Connect Acknowledgement (Sent on the uplink)
MS sends a Connect Acknowledgement to MSC on
FACCH
At this point the Call has been successfully setup and
speech is on-going.
Connect Acknowledgement Message from TEMS:

Engineer
31
Disconnect (Sent on the Uplink)

MS sends the Disconnect message
when the subscriber presses the
End" button at the end of the call.
Disconnect message contains the
cause code and description for the
disconnection

Engineer
32
Release (Sent on the Downlink)

MSC sends the Release message
informing the MS to release the
assigned resource.
Release Complete
MS sends the Release Complete
confirming that it has now freed the
assigned resource.

Engineer
33
Signalling Flow Mobile Terminating Call

(Um Interface)
Paging Request (Sent on the Downlink to B-Party)
When MSC receives the Setup message from calling party, it
sends the Paging Request to the last Location Area the MS
registered in to locate the MS.
Message contains IMSI/TMSI of the called party, sourced from the
HLR/VLR.
Channel Request
Only the MS whose IMSI/TMSI matches that in the Paging Request
will try to respond by sending Channel Request message.
The rest of the procedure proceeds as in Mobile Originating Call.

Engineer
34
Call Setup Failure Analysis

Engineer
35

Call setup failure can be identified with one
of the following:
RACH attributed call setup failures
Paging attributed call setup failures
SDCCH congestion attributed call setup
failures
SDCCH drop attributed call setup failure
TCH congestion attributed call setup failure

Engineer
36
Causes of Poor RACH Success Rate

MS can fail to use RACH due to any of the following,
thereby causing call setup failure:
Poor BSIC planning
Poor RF environment that can cause high interference
(These two can cause Phantom RACH).
RF spillage that cause path imbalance.
Wrong parameter settings (CRO, ACCMIN, MAXRET,
etc).
Unstable transmission links (Abis) that cause high BER.
BTS Hardware malfunction, faulty antennae, etc.

Engineer
37

RACH Success Affected by
5. Faulty
Antenna/Cable
3. Poor Coverage/
Spillage
1. Poor BSIC Plan
Poor RACH
Success Rate
7. TX
Problems
6.
CRO/ACCMIN/MAXRE
T
4. Phantom RACH

Engineer
2. BCCH Plan
38
Causes of Poor Paging Success Rate

Paging can fail due to any of the following, thereby causing
mobile terminating call setup failure:
Wrong Parameter settings at both Cell and MSC level
(BS_PA_MFRMS, etc).
Excess Paging Discards.
Poor RF environment that can cause high interference.
Poor paging strategy.
SDCCH congestion that can cause MS fail to respond to paging.
Incorrect LAC dimensioning that can increase the paging time.
Unstable transmission link (Abis, A interface) that can cause
high BER.

Engineer
39

Paging Success Affected by
3. Incorrect MSC
Parameters
1. Incorrect Cell
Parameters
Poor Paging Succ.

Rate
5. Poor Paging
Strategy
4. Poor RF
Environment
2. Excess Paging
Discards

Engineer
40

Paging Success Affected
8. Incorrect LAC
Dimensioning
6. SDCCH
Congestion
Poor Paging Succ.

Rate
9. Abis/A Fluctuations or
Errors
7. Abis/A interface
congestion

Engineer
41
Causes of High SDCCH Congestion Rate

High SDCCH congestion can occur due to any of
the following, thereby causing call setup failure:
Adaptive Configuration of Logical Channels where
resources can alternate between TCH and SDCCH.
SDCCH Dimensioning where few channels have
been defined but SDCCH demand is high.
High volume of SMS or USSD traffic.
High volume of Location Area Updates.
RF spillage that causes the cell to have extra
demand due to excess coverage.

Engineer
42

High SDCCH Congestion Rate
RF
Spillage
High SMS
Volume
Adaptive Configuration of Logical

Channels
High SDCCH Cong.

Rate
High LU
Volume
SDCCH
Dimension

Engineer
43
Causes of High SDCCH Drop Rate

High SDCCH drop rate can occur due to any of the
following, thereby causing call setup failure:
Poor RF environment that can cause high
interference or low signal strength.
High Timing Advance.
TCH congestion.
Wrong power control settings
Congestion in the transcoder.
Adaptive configuration of logical channels.
Wrong installation of diversity antennas

Engineer
44

High SDCCH Drop Rate
Adaptive
Configuration
Other
Reasons
High TA
Signal
Strength
SDCCH Drop
Rate
Power Control
Settings
TCH
Congestion
Transcoder
Congestion

Engineer
Interference
45
Mechanisms for Reducing TCH Congestion

The following mechanisms can be used to reduce TCH
congestion:
Deploying Multi-Band operation (GSM+DCS) to offload the
congested layers.
Enabling Half-Rate support.
Enabling Cell Load Sharing features.
Enabling Hierarchical Cell Structure (HCS).
Enabling Assignment to Other Cells (Directed Retry).
Increasing the site density.
Deploying In-Building solutions to offload Macro-cell layers.
TRX Expansion.

Engineer
46

High TCH Congestion Rate (Reduction Mechanism)
Multi-Band
Operation
Half-Rate
TCH Cong.
Rate
Assignment to
Another Cell
Hierarchical Cell
Structure
Cell Load Sharing

Engineer
47

High TCH Congestion Rate (Reduction Mechanism)
Micro-Cell Layer
Directed
Retry
TRX
Upgrade
TCH Cong.
Rate
In-door Solutions
Site Density
RF Optimisation (Traffic
Offload)

Engineer
48
References:
3GPP TS 24.008
ETSI EN 300 908

Engineer
49
THANK YOU

Engineer
50

Call Setup Process and Failure Analysis

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Call Setup Process and Failure Analysis

Caricato da

Copyright:

Formati disponibili

RADIO PLANNING AND

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

These are sent to the MS on BCCH

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

Contains the following:

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

These are sent to the MS on SACCH

Kelvin George Kuyere, Snr RF

System Information Messages

SYS INFO 5TER Message from TEMS:

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

Kelvin George Kuyere, Snr RF

System Information Messages

SYS INFO 7 and 8

Kelvin George Kuyere, Snr RF

Signalling Flow for MOC

Kelvin George Kuyere, Snr RF

Mobile Originating Call -MOC

Signalling Flow of MOC

Channel Request (UL)- Using RACH

Immediate Assignment (DL)- Using

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF

Signalling Flow MOC (Um Interface) (Cont)

Kelvin George Kuyere, Snr RF