This document discusses testing and results from implementing a new scheduling algorithm with adjusted GoS factor values in the Pekanbaru cluster to improve average user throughput. The cluster was previously experiencing low average throughput under 300 Kbps. Testing of a 5:4:1 GoS factor ratio in low and high traffic conditions showed an 11.15% improvement in average throughput over 33 weeks. Nearby, medium, and far locations were tested with different subscriber types. The changes were found to effectively prioritize higher quality subscribers even at a distance.
Presentation on how to chat with PDF using ChatGPT code interpreter
BSC 6600 Scheduling Algorithm Improves Pekanbaru User Throughput
1. cdma2000 1xEV-DO
Rev.A Scheduling
Algorithm BSC 6600
Cluster Pekanbaru
Date : 06 Feb 2012
Prepared by : EVDO Project Team
2. Current Condition at Pekanbaru
Pekanbaru has low average user throughput under 300 Kbps, this cluster will be implemented
Pekanbaru has low average user throughput under 300 Kbps, this cluster will be implemented
Scheduling Algorithm for Average User Throughput improvement.
Scheduling Algorithm for Average User Throughput improvement.
P a ge 2
3. Equation
Default Value for GOS Factor Example:
•Gold (n) = 3 ; Ratio of Rate = 2(3-1) With GOS Factor Value for Gold, Silver and Bronze (3:2:1).
=2(2) Comparation for Subscriber Speed are
=4 •Bronze Subscriber with estimation speed 100 Kbps
•Silver (n) = 2 ; Ratio of Rate = 2(2-1) •Silver Subscriber estimation speed about 200 Kbps
= 2(1) •Gold Subscriber estimation speed about 400 Kbps
=2
•Bronze (n) = 1; Ratio of Rate = 2(1-1)
= 2(0) •Average Speed from 4 Subscriber
=1 (Gold = 1 user ; Silver = 2 user’s ; Bronze = 1 user )
minimum value is 1, so 0 value will be replace with 1
= 225 Kbps
P a ge 3
4. BSC 6600 Scheduling Algorithm
By Using Call Data Record in OMStar CDMA we can find Subscriber amount based on QoS.
By Using Call Data Record in OMStar CDMA we can find Subscriber amount based on QoS.
The CDR take aadate on 30 Dec 2011.
The CDR take date on 30 Dec 2011.
Ratio Gold Subscriber : 86/298 = 28.85 %
Ratio Silver Subscriber: 138/298 = 46.3 %
Ratio Bronze Subscriber: 74/298 = 24.85 %
Microsoft Office
Excel 97-2003 Worksheet
P a ge 4
5. Subcriber Ratio
Default value for GOS Factor is 3:2:1 , , then with calculation we find ratio 5:4:1 for GOS Factor that
Default value for GOS Factor is 3:2:1 then with calculation we find ratio 5:4:1 for GOS Factor that
Result high average user speed.
Result high average user speed.
Speed = 100 Kbps for Bronze
Highest Average
User Speed
Microsoft Office
Excel 97-2003 Worksheet
P a ge 5
6. BSC 6600 Scheduling Algorithm
We propose to change GOS Factor value to 5:4:1. We will monitoring average user throughput
We propose to change GOS Factor value to 5:4:1. We will monitoring average user throughput
If the KPI getting worst than before, we have to roolback again to default value 3:2:1 for GOS Factor.
If the KPI getting worst than before, we have to roolback again to default value 3:2:1 for GOS Factor.
E:Pekanbaru Optim
GOS Factor.txt E:Pekanbaru Optim
GOS Factor Rollback.t
7. KPI monitoring
Execution of GOS Factor at 17 Jan 2012, there is improvement about 11,15 % for average user
Execution of GOS Factor at 17 Jan 2012, there is improvement about 11,15 % for average user
throughput after 33weeks monitoring activity.
throughput after weeks monitoring activity.
P a ge 7
8. KPI monitoring
Execution of GOS Factor at 17 Jan 2012, Average DRC in BSC Pekanbaru still normal.
Execution of GOS Factor at 17 Jan 2012, Average DRC in BSC Pekanbaru still normal.
P a ge 8
10. Testing – 1 (Low Traffic) Location
We conduct the field test in 2689_Srimeranti-2, the test begin at 55January 2012 - -07:00 and the
We conduct the field test in 2689_Srimeranti-2, the test begin at January 2012 07:00 and the
location take aaplace in low active user. We using 33different IMSI with different QoS (Gold, Silver
location take place in low active user. We using different IMSI with different QoS (Gold, Silver
and Bronze)
and Bronze)
P a ge 10
11. Testing – 1 (Low Traffic)
Near location (100 m) based on SINR : :99upto 14 (dB)
Near location (100 m) based on SINR upto 14 (dB)
Medium location (700 m) based on SINR : :00upto 88(dB)
Medium location (700 m) based on SINR upto (dB)
Far location ( (2000 m) based on SINR : :-12 upto 00(dB)
Far location 2000 m) based on SINR -12 upto (dB)
5 Feb 2012
Medium test occur in the early morning when average user throughput in low traffic.
Medium test occur in the early morning when average user throughput in low traffic.
Near test occur when the average user throughput in high traffic.
Near test occur when the average user throughput in high traffic.
P a ge 11
13. Testing – 1 (Low Traffic)
Based on Bandwidth limitation Silver and Bronze subscriber has limitation in user throughput due
Based on Bandwidth limitation Silver and Bronze subscriber has limitation in user throughput due
to QoS Forward Limited Rate.
to QoS Forward Limited Rate.
P a ge 13
15. Testing – 2 (High Traffic)
We conduct the second field test in surrounding coverage high traffic area on 77Feb 2012, in the
We conduct the second field test in surrounding coverage high traffic area on Feb 2012, in the
busy hour around 20:00 to 24:00.
busy hour around 20:00 to 24:00.
P a ge 15
16. Testing – 2 (High Traffic)
Good SINR : 9-14 [dB] MediumSINR : 0-8 [dB] BadSINR : (-12 ) - 0 [dB]
Time 21:45 – 22:45 Time 20:00 – 21:30 Time 23:15 – 01:00
P a ge 16
17. Testing – 2 (High Traffic)
GOS Factor 5:4:1 with ratio rate 8:6:1 in High Traffic condition really take effect by Scheduling
GOS Factor 5:4:1 with ratio rate 8:6:1 in High Traffic condition really take effect by Scheduling
Algorithm. Even in Far distance Gold Subscriber and Silver Subscriber have high priority than
Algorithm. Even in Far distance Gold Subscriber and Silver Subscriber have high priority than
Bronze Subscriber.
Bronze Subscriber.
P a ge 17
18. Testing – 2 (High Traffic)
8
6
1
From OMC calculation compare with
Field Test there is different about 4.95%
P a ge 18
19. Testing – 2 (High Traffic) Summary
Throughput Sensitive Profile ID
Throughput Sensitive Profile ID
P a ge 19