Академический Документы
Профессиональный Документы
Культура Документы
• Trial Observations
Did OSC-HR really deliver as per the promise?
• Conclusions
Immediate revenue boost with a positive overall TVO
900 400,000
20 800 350,000
700 300,000
15 600
250,000
Mbps
subs
Erl
500
200,000
10 400
300 150,000
5 200 100,000
100 50,000
0 0 0
2012 2013 2014 2015 2016 2011 2012 2013 2014 2015
• Anticipated growth will require considerable investment in new infrastructure over next 5 years
Additional 835 sites will necessarily be rolled out taking sites count to 3614
Total number of TRX in the network will be 72,033 – more than 66% increase over the present count of 43,218
• However, Robi is planning to roll-out only ~120 sites each year
Without OSC
Cumulative BTS Count Cumulative TRX Count & Reduction %
Without OSC
4000 80000
NSN OSC NSN OSC
3500 Robi's Roll-out Plan ~10% 70000 Percentage Savings
14%
3000 60000
13%
13%
2500 50000
12%
11%
2000 40000
500 10000
0 0
2012 2013 2014 2015 2016 2012 2013 2014 2015 2016
• Planned roll-out of ~120 sites a year will fall well short of the actual capacity required
• However, OSC-HR will allow Robi to cope with growth within the planned roll-out budget
There could be a potential savings of ~10% in terms of sites and ~14% in terms of TRX count
Overall TRX count in the network can be kept flat during the first two years of deployment
On top of potential reduction in CAPEX, OSC-HR would help to realize additional Revenue streams immediately
Network Quality
De/Multiplexing Today’s
OSC0 Network
OSC1
Multiplexing
In urban areas, where coverage limitation does Supported by OSC trial observations
not typically exist, OSC-HR radius could be up
to 100% of cell dominance area
8 © Nokia Siemens Networks
Actual Trial observations from Robi Network
OSC-HR Impact on BSC Peak Traffic
Sum of Peak Traffic (Erl)_ After OSC Sum of Peak Traffic (Erl)_ Before OSC Peak Traffic Growth (%)
6000 35.0%
30.0%
5000
25.0%
4000
20.0%
Erl
3000
15.0%
2000
10.0%
1000
5.0%
BSCs
% of Blocking
% of Blocking
6 6
5 5
4 Traffic Boost 4
Traffic Boost Traffic Boost
3 3
2 2
1 1
0 0
0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 0 10 20 30 40 50 60 70
TCH Traffic (Erl) TCH Traffic (Erl.)
%TCH Blocking_Pre OSC %TCH Blocking_Post OSC %TCH Blocking_Pre OSC %TCH Blocking_Post OSC
• Though OSC-HR would not necessarily generate calls, however, can help to cope with higher demand
Cell level overall traffic boost due to OSC-HR implementation could be as high as ~20%
OSC-HR will significantly reduce potential revenue loss due to blocking
Cells with high blocking would benefit immediately from the soft capacity gain
Even selective deployment of OSC-HR could have network wide positive impact
a) Expand existing sites with more The benefit of deploying OSC-HR will
TRX capacity be realized from savings in CAPEX +
IMPLEX + OPEX due to less TRX
b) In case max capacity is reached, expansion and rolling out of fewer
new capacity sites will have to be new sites in addition to capturing
acquired and built additional traffic immediately
General Assumptions
Currency USD
Taxrate 15%
CAPEX depreciation time 8 years
WACC 14.5%
Without OSC
Cumulative BTS Count Cumulative TRX Count & Reduction %
4000 Without OSC
80000
NSN OSC
NSN OSC
3500 Robi's Roll-out Plan ~10%
70000 Percentage Savings
14%
3000 60000
13%
13%
2500 50000
5%
2000
2%
40000
1500 30000
1000 20000
• Initial deployment of 10%-30% during the first two years would allow for immediate cashing-in of
OSC-HR soft capacity benefits in high-load areas
• However, by the 3rd year i.e. 2014 must catch-up with activation shortfall to cope with the growth
• By the third year of operation, technical bottlenecks (eg. lack of E1 capacity) should be sorted out
for more extensive deployment of OSC-HR
10,000
OPEX, 8.74
5,000
CoS, 0.00
0
2012 2013 2014 2015 2016
-5,000
• OSC-HR Business Case for Robi will have immediate positive impact on overall cash flow situation
The potential from immediate increase of moderate 1.5% traffic leads to capturing an additional Revenue of
15.6 Million USD during the first two years
The value of OSC will primarily be driven by considerable OPEX savings due to reduction in deployed HW
Total Value of Ownership (TVO) Net Savings (CAPEX 3.23 + OPEX 8.74) = 12 Million USD
• OSC-HR as a soft capacity feature can absorb additional traffic when there is demand
• As a soft capacity feature, OSC-HR would always help in easing off blocking, provided radio
condition supports adequate level of OSC-HR triggering
• The potential savings from CAPEX + IMPLEX + OPEX due to less HW infrastructure will
offset the licensing cost of OSC-HR in addition to immediate revenue boost
• Additional future savings in CAPEX & OPEX over five years is justifying using OSC-HR extensively
• Less TRX to cope with growth would limit interference in the network, thus ensuring better quality
• OSC-HR usage would release some time slots for improving PS traffic throughput and speed
• On special occasions, like Eid, OSC-HR could be of huge benefit to Robi capturing
additional revenue at no extra cost by significantly reducing blocking
• If aggressive customer acquisition efforts are made, the network will be ready to absorb additional
traffic demand (both voice and data) using OSC-HR
Samples )%
BSC Name
Sl No
• RX Level Measurement from each 1 CBN06 26.81 6.42 66.77 90% 60.1
BSC taken in May for calculation 2 CBN07 25.87 6.27 67.85 90% 61.1
3 CBN08 26.66 5.29 68.06 90% 61.3
of OSC Usable area 4 CBN12 26.52 5.37 68.11 90% 61.3
CS Traffic has increased by 31.79%. [Traffic gain=(max traffic after-max traffic before)/max traffic before*100%)]
Maximum TCH Traffic hit up to 150.14 Erl with 58 available TCH, whereas without OSC and considering 100% HR with 116 trunks can offer theoretical
116 Erl maximum.
TCH blocking has reduced by 91.48%.
OSC Traffic penetration reached up to 74.61% at cell busy hour
PS traffic has increased by 95%. [PS Traffic gain=(average PS traffic after-average PS traffic before)/average PS traffic before*100%)]
22 © Nokia Siemens Networks
Scenario-2: Cell Busy Hour KPI Comparison: Kalakachua_3 (D27802C)
Attempted CELL <-90dBm & DL Qual0-4 (2- <-90dBm & UL Qual0-4 (2-
Total Available OSC
Segment %TCH TCH % of OSC Site Name
Date Time Traffic TCH in a implement NAME 4th July) 4th July)
Name Blocking Seizures Traffic
(Erlang) cell ation date
for call Kalakachua_3 D27802C 81.77 53.12
07.06.2012 20:00 D27802C 12.45 60.56 56 4186 9-Jul-12
08.15.2012 19:00 D27802C 2.1 100.11 56 6484 9-Jul-12 7.66
Due to bad uplink quality OSC traffic sharing was not satisfactory (only 53% quality sample is in between 0 to 4 which meet the OSC criteria)
Though it carry less % of OSC traffic due to bad quality sample but it helps to reduce TCH congestion by contributing some OSC traffic.
OSC Traffic penetration reached up to 7.66% at cell busy hour
Site to site distance is more than 5 km and call distribution also far from the site which is the possible cause for bad uplink quality.
Most of the quality samples are belongs to Rxlevel 90 to 110dBm for this cell which is out of OSC multiplexing range.