cdma2000 1xEV-DO

Rev.A Scheduling
Algorithm BSC 6600
Cluster Pekanbaru

Date

: 06 Feb 2012

Prepared by

: EVDO Project Team

Current Condition at Pekanbaru

Pekanbaru has low average user throughput under 300 Kbps, this cluster will be implemented
Scheduling Algorithm for Average User Throughput improvement.

Page 2

Equation

Default Value for GOS Factor

Gold (n) = 3 ; Ratio of Rate = 2(3-1)
=2(2)
=4
Silver (n) = 2 ; Ratio of Rate = 2(2-1)
= 2(1)
=2
Bronze (n) = 1; Ratio of Rate = 2(1-1)
= 2(0)
=1
minimum value is 1, so 0 value will be replace with 1

Example:
With GOS Factor Value for Gold, Silver and Bronze (3:2:1).
Comparation for Subscriber Speed are
Bronze Subscriber with estimation speed 100 Kbps
Silver Subscriber estimation speed about 200 Kbps
Gold Subscriber estimation speed about 400 Kbps
Average Speed from 4 Subscriber
(Gold = 1 user ; Silver = 2 users ; Bronze = 1 user )

= 225 Kbps

Page 3

BSC 6600 Scheduling Algorithm

By Using Call Data Record in OMStar CDMA we can find Subscriber amount based on QoS.
The CDR take a 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 %

Micros oft Office

Excel 97-2003 Works heet

Page 4

Subcriber Ratio
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.

Speed = 100 Kbps for Bronze

Highest Average
User Speed

Micros oft Office

Excel 97-2003 Works heet

Page 5

BSC 6600 Scheduling Algorithm

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.

E:\Pekanbaru Optim\
GOS Factor.txt

E:\Pekanbaru Optim\
GOS Factor Rollback.t

KPI monitoring
Execution of GOS Factor at 17 Jan 2012, there is improvement about 11,15 % for average user
throughput after 3 weeks monitoring activity.

Page 7

KPI monitoring
Execution of GOS Factor at 17 Jan 2012, Average DRC in BSC Pekanbaru still normal.

Page 8

Testing 1 (Low Traffic) Methodology

Page 9

Testing 1 (Low Traffic) Location

We conduct the field test in 2689_Srimeranti-2, the test begin at 5 January 2012 - 07:00 and the
location take a place in low active user. We using 3 different IMSI with different QoS (Gold, Silver
and Bronze)

Page 10

Testing 1 (Low Traffic)

Near location (100 m) based on SINR : 9 upto 14 (dB)
Medium location (700 m) based on SINR : 0 upto 8 (dB)
Far location ( 2000 m) based on SINR : -12 upto 0 (dB)

5 Feb 2012

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.

Page 11

Bandwidth limitation from QoS Parameter

Page 12

Testing 1 (Low Traffic)

Based on Bandwidth limitation Silver and Bronze subscriber has limitation in user throughput due
to QoS Forward Limited Rate.

Page 13

Testing 1 (Low Traffic) Summary

Page 14

Testing 2 (High Traffic)

We conduct the second field test in surrounding coverage high traffic area on 7 Feb 2012, in the
busy hour around 20:00 to 24:00.

Page 15

Testing 2 (High Traffic)

Good SINR : 9-14 [dB]

Time 21:45 22:45

MediumSINR : 0-8 [dB]

Time 20:00 21:30

BadSINR : (-12 ) - 0 [dB]

Time 23:15 01:00

Page 16

Testing 2 (High Traffic)

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
Bronze Subscriber.

Page 17

Testing 2 (High Traffic)

From OMC calculation compare with

Field Test there is different about 4.95%

Page 18

Testing 2 (High Traffic) Summary

Throughput Sensitive Profile ID

Page 19

Thank You