Vous êtes sur la page 1sur 14

Call Setup Time and Slot Cycle

Index
Originating call setup process

ORM Origination Message Send from the Mobile


ECAM Extended Channel Assignment from RAN, confirming
all the resources are available, if for instance ECAMs are not
received after the BTS Acknowledgement for the ORM, then it
most likely is a Blocked Call, reason could be WC, CE, Power or
Backhaul
SCCM Service Connect Completion Message, confirmation
from the Mobile for the Service Connect Message sent by the
RAN, which says there are no issues in the Originating Mobile
side and the Originating subscriber is ready to TALK
Originating call setup Call Flow
Terminating call setup process

GPM General Page Message, For incoming call, the Mobile


will be notified about the same on the GPM
Page Response Response from the Mobile for an incoming
call
ECAM Resources confirmed
SCCM Service Connect Completion Terminating Mobile
ready to TALK

End to End Call Setup Time is from Origination message from


the Originating Mobile to SCCM time at the terminating mobile,
which confirms that both parties are READY TO TALK
Terminating call setup Call Flow
Slot Cycle Index

This value determines the Wake Up Cycle Time for the mobiles
If set to 0 value, Mobile listens and decodes all the Paging
Channel Messages send, which is not really required, and
consumes a lot of battery life, when on the idle mobile
This is the reason why there are Non-Zero values for SCI, which
lets mobile set a Wake Up Time which defines the time interval
when the mobiles wake up decode the paging message and
goes back to sleep.
This time is 1.28 Secs for SCI =1 and 2.56 Secs for SCI=2
The same ends in saving a lot of battery life
Call Setup Time for SCI = 0 & 1 values for TTSL
Origination to SCCM on Origination to SCCM on
terminating Mobile for SCI = 0 in terminating Mobile for SCI = 1 in
Secs Secs Delta in Secs
Average 5.5 6.08 0.58
Min 3.27 3.36 0.09
Max 20.88 18.82 -2.06
Std Deviation 2.5 2.96 0.46

The samples are taken from around 500-600 calls, with


Originating mobile stationary and the terminating mobile is
moving
As can be seen the delta is very negligible, which says that the
Wake up cycle for the mobile with SCI = 1 is optimum value for
battery life and for Call Setup Time
Origination to Page request to the terminating
Mobile SCI = 0
80

70

60

50

40 Orig-Page

30

20

10

0
0.00
0.50
1.00
1.50
2.00
2.50
3.00
3.50
4.00
4.50
5.00
5.50
6.00
6.50
7.00
7.50
8.00
8.50
9.00
9.50
10.00
10.50
11.00
11.50
12.00
12.50
13.00
13.50
14.00
14.50
15.00
15.50
16.00
16.50
17.00
17.50
18.00
18.50
19.00
19.50
20.00
As can be seen, the time the originating mobile sends the ORM
to the time Page is seen on the terminating Mobile is around 4.5
secs for 93% of the mobiles for SCI =0
Origination to Page request to the terminating
Mobile, SCI = 1, Mobiles waking up every 1.28Sec
and receiving the incoming Page
100

90

80

70

60

Ericsson
50
Lucent

40

30 1.28s

1.28s
20
1.28s
10

0
00:00.0
00:00.5
00:01.0
00:01.5
00:02.0
00:02.5
00:03.0
00:03.5
00:04.0
00:04.5
00:05.0
00:05.5
00:06.0
00:06.5
00:07.0
00:07.5
00:08.0
00:08.5
00:09.0
00:09.5
00:10.0
00:10.5
00:11.0
00:11.5
00:12.0
00:12.5
00:13.0
00:13.5
00:14.0
00:14.5
00:15.0
00:15.5
00:16.0
As can be seen, the time the originating mobile sends the ORM to the
time Page is seen on the terminating Mobile is around 4.5 secs for 92%
of the mobiles for SCI =1. Data collected when T3113 timer value was
10sec in Chennai, resulting in some mobiles receiving Pages in the 2nd
attempt, @ 12 Sec and more. The same is changed to 7 secs.
Differences
Only 1% of the mobiles will have an End to End call setup time
better than 6 secs if we change the SCI from 1 to 0

But look into this statistics: (based on QCOM documents)

We loose around 60 hours of battery life for 5100 chipsets, and


the newer the chipset is, we are loosing more battery life, by
changing SCI from 1 to 0
Most of our handsets are either 5100 or 5105 chipsets
Conclusion
Changing SCI values from 1 to 0 is not a good solution for the Call Setup
Time, subscribers will start complaining they are loosing battery life on
the mobiles
Trade Off is huge between the expected call setup time improvement to
the degradation of battery life
Recommended value for SCI should be 1 for TTSL networks

What is causing the perceived Call Setup Time


problem
Is it calls to/from other networks, including the landline calls
Do we have a control in the setup times for these calls?
Suggestions to improve Call Setup Time which
can be controlled within TTSL

Available patch for IS-Page in E/// switch, which does


simultaneous Global and IS Page as the 2nd Page to be loaded,
thus eliminating the requirement of 3rd Page, and hence reduce
the Call Setup Time of around 3-4% customers by 6-7 seconds
T3113 timer in the switch should be kept to 6 secs for SCI = 1
value, for 1st Page and 7 secs for 2nd Page
Can we reduce the T3113 timer value to 5 secs?
For SCI = 1
We are in the process of talking with E/// and Motorola to try and
set the Access Parameters to the following value, which can help
set the T3113 value to < 6secs, which can result in saving 2 secs
for the 2nd Page Request from the MSC, for SCI = 1.

Access Parameter Proposed Value


Max_Rsp_Seq 2
Num_Step 4
Acc_Tmo 1
Prob_Bkoff 0
Bkoff 0
Thank You

Vous aimerez peut-être aussi