Professional Documents
Culture Documents
Call Setup Time
Call Setup Time
• During drive testing can be noted that there are call setup failures where the network does not seem to respond to
RRC Connection Requests with RRC Connection Setup –message.These are problems due to the spiky UL noise
and due to that the power ramping is not aggressive enough to provide high enough Tx power for the terminal
during open loop PC
PowerOffsetLastPreamblePRACHmessage
L1ACK/AICH
PtxAICH
Downlink / BS
PowerRampStepPRACHpreamble
UEtxPowerMaxPRACH
…. ….
PRACHRequiredReceivedCI Uplink / UE
Preamble 1 Preamble n RACH Message part
PRACH_preamble_retrans: The maximum
number of preambles allowed in one preamble
ramping cycle
The PRACHRequiredReceivedCI (-20dB) allow to calculate the UEpower for the fist preambleas in the
following:
The parameter PRACHRequiredReceivedCI can be set to -18…-20dB instead of the default -25dB (typically -
20dB is enough)
Call setup Time – Preamble PRACH
Typical improvement passing from -25dB to -20dB:
PRACH req. C/I = -25dB PRACH req. C/I = -20dB Clear improvement number of sent
100% preambles per RRC Connection Request
90% for –20dB case. For –20dB 50% of cases
80%
the needed number of preambles is <=4
70%
60%
where as for –25dB it is ~6.5
50%
40%
30%
20%
10% There should be significant improvement
0% also for call setup delay
1 2 3 4 5 6 7 8
Call setup Time – Preamble PRACH
The average number of acknowledged PRACH preambles during the RRI period can be calculated based on the
KPI below
RACH load due to preamble can then be calculated by dividing the above further by the max number preambles
can be received during RRI
• For example if RRI period is 200ms the are 10 20ms RACH frames and in each 20ms RACH frame there are
15 RACH sub slots within each it is possible to receive and decode max 4 preambles -> therefore in 200ms it
is possible to receive 15*4*10=600 preambles
Why 13.6kbit/s?
Use of 13.6 kbit/s SRB also in highly loaded networks
Decreased setup times (PDP context activation minimum 0.7s lower)
Improved Iub efficiency
7
Nokia RAN1.5 (3.4 kbps) + M11
6
Nokia RAN04 (13.6 kbps) + M12
5 Nokia RAN target
Seconds
0
3G-3G CS call setup PS call setup DCH allocation
Call setup Time – KPI
In RN2.2 the following counters are available to monitor the Call Setup Time
In detail we have:
RRC connection setup completeUE RNC 100 140 UE and paging of MT-UE
CM service request UE CS 200 340 (CS core feature)
Security mode command RNC UE 100 440
Security mode complete UE RNC 200 640
Setup UE CS 300 940
Call proceeding CS UE 1001040 Paging RNC UE 400 1340
Radio bearer setup RNC UE 1001140 RRC connection request UE RNC 50 1390
Radio bearer setup complete UE RNC 3001440 RRC connection setup RNC UE 40 1430
RACH/FACH
RRC connection setup complete
UE RNC 100 1530
Paging response UE CS 100 1630
Security mode command RNC UE 100 1730
Security mode complete UE RNC 200 1930
Setup CS UE 300 2230
Call confirmed UE CS 100 2330
Radio bearer setup RNC UE 100 2430
Radio bearer setup complete UE RNC 300 2730
Alerting CS UE 250 2980 CS UE 250 2980
<3.0 s mobile-to-mobile
AMR call setup time
Call setup Time – Annex2
Typical value for PS Call Setup Time
Common channels
used for setup to avoid
slow synchronized
reconfigurations later
RACH/FACH
RRC connection setup RNC UE 40 40
RRC connection setup complete UE RNC 100 140
GPRS service request UE PC 200 340 Parallel RB setup and
Security mode command RNC UE 100 440
RL/AAL2 setups (or pre-
reserved Radio links)
Security mode complete UE RNC 200 640
PDP context activation request UE PC 250 890
Radio bearer setup RNC UE 150 1040
Radio bearer setup complete UE RNC 300 1340
PDP context activation accept PC UE 200 1540