June 2010
Introduction / Overview High Level Dimensioning 2G dimensioning guideline 3G dimensioning guideline 2G/3G Network Utilisation 2G/3G traffic related interworking
April 2010
Introduction / Overview
During the last years a 2G and a 3G capacity and dimensioning guideline were developed in close collaboration with the operators.
Introduction
In order to allow a simple and fast read it was decided to choose Power Point format. Also 2G and 3G is put together into one guideline.
In any case the main goal of this guideline is to give support to the operating companies for the task of network dimensioning. It ensures that same way of planning is used and therefore the basement is build to deliver any possible benefit. Moreover, when OpCos using same principles and methods they can learn from each other in sense of best practise sharing.
April 2010
Introduction / Overview
The dimensioning follows a threefold approach with different level of detail to reach the goal of each step
High Level Dimensioning
To get the quantity structures for a given time frame, e.g. 3 years. To support budget estimations. Allows quick what-if analysis. Based on simple tools, e.g. Excel or Access
Introduction
April 2010
network data
traffic translation parameter. e.g. billable to busy hour traffic (necessary to update from time to time)
6 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
2. Network is given as totals, inclusive the planning for following years, expressed in #sites and #carrier (#TRX) -> divided into the same 16 classes 3. The traffic per class is compared with total capacity (in case of 3G sets as outcome from dynamic system simulations or measurements, in case of 2G a modified ErlangB table incl. HR, AMR-HR and GPRS)
Marketing Forecast
BH Network Traffic
Set 1
Set 2 16 classes
4. The result is the demand in terms of total carriers/TRX, total number node B/BTS, required base band boards, required IuB capacity, required number RNC. Each result is also available per class and could be further analysed.
7 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
April 2010
More information about the model can be found in the back up sharing teamroom <LINK>
April 2010
for mature networks with slow coverage roll out valid for strong growing networks at least valid for the old network part 1. The method is to use relative growth figures of marketing forecasts 2. Adapt this growth to the busy traffic measurements of each cell 3. Compare the resulting traffic with capacity tables (3G) or Erlang B model (2G) ADVANTAGE Can be much more accurate, because the network is not classified in 16 classes only, each cell/sector/site could be considered individually Cell specific restrictions can be considered, e.g. different limitations in the spectrum (border regions, different interference situations) Possibility to apply different traffic growth to cell individually when some history is available
April 2010
Reference Year
Max of DLPAYLOAD_SPEECH_(kbits) 06/07 07/08 08/09 CELL-ID AVG2 AVG2 AVG2 62 27923.5 43219.37 72430.77 751 101380.5 156914.5 262970.9 752 88037 136261.7 228359.2 753 101525 157138.1 263345.7 761 22645 35049.43 58738.87 762 24550.5 37998.72 63681.54 763 18858.5 29188.77 48917.06 791 23615.5 36551.55 61256.25 792 54107.5 83746.39 140349.4 793 14496 22436.59 37601.17 801 121323 187781 314699.7 802 53966.5 83528.15 139983.7 803 316394.5 489708.4 820695.7 822 11375 17605.97 29505.61 901 57783.5 89436.02 149884.6 902 59342 91848.23 153927.2 903 18325 28363.03 47533.22 931 22289.5 34499.19 57816.73 932 26219 40581.19 68009.46 933 59526 92133.02 154404.5
09/10 AVG2 128073.5 464990.2 403789.1 465653 103863.2 112602.9 86496.1 108314.5 248168.6 66487.12 556458.1 247521.9 1451170 52172.39 265028.9 272177.1 84049.15 102232.7 120255.6 273021
10/11 AVG2 186156.67 675870 586913.33 676833.33 150966.67 163670 125723.33 157436.67 360716.67 96640 808820 359776.67 2109296.7 75833.333 385223.33 395613.33 122166.67 148596.67 174793.33 396840
11/12 AVG2 248208.9 901160 782551.1 902444.4 201288.9 218226.7 167631.1 209915.6 480955.6 128853.3 1078427 479702.2 2812396 101111.1 513631.1 527484.4 162888.9 198128.9 233057.8 529120
April 2010
Used for 06/07 to 07/08 Capacity settings, original for 5 Codes HSDPA and cat. 6 Voice VT R99 HSDPA User 12.9 0.7 2.6 0.7 min/MB 773 42.4 35.5 56.8 kbits 565836 162816 290816 465306 1484774 UL-util/user 5.60% 24.70% 3.80% 1.40% 100% DL-util/user 4.40% 29.50% 5.60% 11% 100% Code-util/user 1.10% 4.42% 6.15% 0% 66% Max - Utilisation, either UL, DL or Code 07/08 08/09 09/10 10/11 2 24 32 39 0.35 0.38 0.41 0.43 0.45 0.64 0.75 0.99 0.59 0.95 1.06 1.09 0.41 0.56 0.69 0.98 0.37 0.44 0.46 0.48 0.39 0.47 0.51 0.52 0.39 0.47 0.49 0.50 0.42 0.55 0.59 0.59 0.53 0.80 0.88 0.88 0.34 0.35 0.36 0.38 0.42 0.58 0.79 1.13 0.50 0.73 0.80 0.82 0.71 1.22 2.09 2.97 0.40 0.48 0.50 0.50 0.55 0.86 0.94 0.94 0.40 0.52 0.58 0.63 0.75 1.28 1.35 1.25
Used for 08/09 onwards Capacity settings, new for 10 Codes HSDPA and cat. 8 Voice VT R99 HSDPA User 12.0 0.6 2.4 0.7 min/MB 717.6 39.4 33.0 113.6 kbits 525257 151140 269960 930611 UL-util/user 5.97% 26.32% 4.05% 2.98% DL-util/user 4.40% 29.50% 5.60% 20% Code-util/user 2.20% 8.84% 12.30% 0%
Carriers Allowed 2 2 2 2 2 2 2 2 2 2 2 2 2 1 1 1 1
852 Cell Identifier 62 751 752 753 761 762 763 791 792 793 801 802 803 822 901 902 903
06/07 0 0.34 0.43 0.55 0.40 0.37 0.38 0.38 0.41 0.50 0.33 0.40 0.48 0.52 0.39 0.52 0.39 0.71
11/12 54 0.46 1.29 1.25 1.29 0.49 0.53 0.50 0.59 0.89 0.39 1.50 0.83 3.92 0.49 0.94 0.75 1.14
06/07 AVG2 27923.5 101380.5 88037 101525 22645 24550.5 18858.5 23615.5 54107.5 14496 121323 53966.5 316394.5 11375 57783.5 59342 18325
07/08 AVG2 43219.37 156914.5 136261.7 157138.1 35049.43 37998.72 29188.77 36551.55 83746.39 22436.59 187781 83528.15 489708.4 17605.97 89436.02 91848.23 28363.03
08/09 AVG2 72430.77 262970.9 228359.2 263345.7 58738.87 63681.54 48917.06 61256.25 140349.4 37601.17 314699.7 139983.7 820695.7 29505.61 149884.6 153927.2 47533.22
09/10 AVG2 128073.5 464990.2 403789.1 465653 103863.2 112602.9 86496.1 108314.5 248168.6 66487.12 556458.1 247521.9 1451170 52172.39 265028.9 272177.1 84049.15
10/11 AVG2 186156.7 675870 586913.3 676833.3 150966.7 163670 125723.3 157436.7 360716.7 96640 808820 359776.7 2109297 75833.33 385223.3 395613.3 122166.7
11/12 AVG2 248208.9 901160 782551.1 902444.4 201288.9 218226.7 167631.1 209915.6 480955.6 128853.3 1078427 479702.2 2812396 101111.1 513631.1 527484.4 162888.9
traffic estimation
April 2010
1.484
NodeB Pmnoreqdeniedadm
6.000
1.000
Analysis show that from a volume of about 25 Gbyte the blockings gets significant
4.000
500
2.000
Cross check: A good site with up to 20 GByte per week shows that a extra test unit still gets more than 1 Mbps in average (3,6 max), also during busy hour! Total average cell throughput: 2 Mbps
April 2010
Number user with more than 1 MByte (per month, looking only at users making significant traffic) WWW traffic:
in the busy hour (BH): per day: per week: per month: 24 48 87 137
=> 2 Mbps / 0.6% ~ 300: 300 of those WWW users can be served in the area of ONE cell, each of them perceives 1 Mbps throughput during BH
April 2010
DRAWBACK Final capacity per site/nodeB - depends on traffic mix (voice and data services) - depends strongly on how services are used by the customers - depends strongly on when services are used by the customers (daily traffic profile) Difficult to find a representative cell in a network or part of a network
April 2010
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
1. Half Rate
2G Dimensioning Guideline
Concept is that a single connection (either FR or HR) occupies one effective TCH
2 TCH 2 HR%
TCH physical number of traffic channels in a cell HR% ratio between HR calls to the total calls (HR + FR) Example: Cell with two trx and fully utilized:
BCCH SDCCH FR HR HR HR HR FR HR HR FR FR FR
FR
FR
FR
FR
FR
FR
number of TCHs = 14 Effective TCHs = 17 (11 FR connections and 6 HR connections) 35,5% half rate ratio
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2. Queuing 1/2
2G Dimensioning Guideline
25.00
10.00
5.00
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2. Queuing 2/2
2G Dimensioning Guideline
PN A
* [A N+
N C
where and
C * E (N , A) 1 (C 1) * E
C=1+
A(1 e d (N A) ) NA
E(N,A) = Erlang B blocking probability A = offered traffic N = number of channels d = queue waiting time * service rate; service rate = 1/ mean holding time
e.g. maximum queuing time 7.5 sec mean holding time 29 sec
VF-Romania and Vodacom South-Africa have already introduce Queuing into their 2G network. The statements we got are positive concerning
complaints from their customers network performance counters
18 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2G Dimensioning Guideline
Example:
One TRX cell with combined BCCH/SDCCH MMS users primarily using 4-slot mobiles 10 kbps average radio-link bit rate per PDCH MMS of size 30 kByte shall take no longer than 8 seconds 2.2 Erlang traffic in the cell Average number of PDCHs carrying data 2.4
Workflow:
1. Radio-link bandwidth = 4x10 kbps = 40 kbps 2. Required throughput: 30kByte/8 seconds = 30 kbps
April 2010
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2G Dimensioning Guideline
Workflow (continue): 3. Using simulation results shown in the graph on the right, follow the curve corresponding to Radio Link Bandwidth of 40 kbps. Using this curve the requirement of 30 kbps translates into a PDCH Utilisation of no more than 0.4 (40%) 4. Thus we get the minimum required number of PDCHs in the cell = 2.4/0.4 PDCHs = 6 PDCHs (in the present configuration an average of 4.8 PDCHs are available) 5. There are three options to get the required average 6 PDCHs in the cell:
Offload the cell from voice traffic to get 1 Erlang traffic or lower. Dedicate 6 FPDCHs in the cell (not a realistic option) Expand the cell with a second TRX
Simulation results
April 2010
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2G Dimensioning Guideline
2G Network Utilisation
This will be discussed together with the 3G Network Utilisation (please follow this link:
C2 Vodafone Internal Version 1.0 April 2010
2G Dimensioning Guideline
2G features included in the High Level Model and also applicable for the counter based dimensioning
2G Dimensioning Guideline
GPRS implemented only on BCCH trx; Dedicated tsl >=2 (2 for cells with lower capacity i.e. 2trx); Dedicated + Default tsl <=6.
Frame TRX2 TS TS TS TS TS TS TS TS Circuit Switched Territory Packet Switched Territory
TRX1
BCCH
CCCH
TS
TS
TS
TS
TS
TS
Territory border moves dynamically based on Circuit Switched traffic load i.e. voice downgrades data traffic
April 2010
3G Dimensioning Guideline
Content of the 3G dimensioning guideline
3G Dimensioning Guideline
b. Step2: Capacity planning with planning tools (not practiced within Vodafone -> high level way of proceeding see next section) c. Step3: Capacity planning based on counter
April 2010
3G Dimensioning Guideline
Step 2: Capacity planning based on planning tools
Objective
3G Dimensioning Guideline
The planning of capacity based on planning tools is the next logical step after high level dimensioning This step takes among other things a geographic traffic map into account and allows therefore a detailed planning which site has to be expanded or in which area capacity sites needs to be build Planning tools perform the capacity planning by means of Monte Carlo simulations Prerequisites As geographic traffic maps are used for the capacity planning it is crucial to use a traffic map with high quality 1. Based on cell level measurements of 2G networks when 3G networks are newly introduced or 3G traffic is very low 2. Based on cell level measurements of 3G networks 3. A appropriate tool to compile traffic maps based on cell level measurements is available as a special add on module for ArcGis
24 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
3G Dimensioning Guideline
Step 2: Capacity planning based on planning tools
Dimensioning steps 1/3
3G Dimensioning Guideline
The dimensioning with planning tools is an iterative process, which needs to be repeated as long as several KPIs are not fulfilled
1. The first step is to do a coverage analysis part 1 (e.g. coverage by signal-level). For this step the correct definition of sites, transmitters and cells is required as well as suited geographic elevation and land use data together with a proper propagation model. For this step no traffic map is required, the coverage map is based on pilot reception level only (RSCP). 2. The second step starts the capacity planning by performing a number of Monte Carlo simulations. Main output is the load of important resources (DL power consumption, uplink interference level, code tree utilization) - Each simulation step contains at least 20 simulations - The traffic map needs to be scaled correctly for the point in time the planning is done (normally end of next fiscal year)
April 2010
3G Dimensioning Guideline
Step 2: Capacity planning based on planning tools
Dimensioning steps 2/3
3G Dimensioning Guideline
3. The third step is the capacity analysis by analysing the results of the Monte Carlo simulations. - The basic result statistics gives an overview on network performance in terms of users rejected and rejection reasons. - Average results of important parameters are available for each cell, indicating problem cells 4. In parallel to the third step the coverage analysis part 2 should be done. This step takes the load results of step 2 into account. The analysis should be done for the pilot (Ec/Io) and for the reference service (effective service area). Any coverage holes under load conditions can now be detected. 5. If the results of step 3 and 4 doesnt meet the requirements a (planning) optimisation of the transmitters, cells and antennas should be done. After optimisation steps 1 to 4 needs to be repeated (iterative process!)
April 2010
3G Dimensioning Guideline
Step 2: Capacity planning based on planning tools
Dimensioning steps 3/3
3G Dimensioning Guideline
6. If optimisation of the given network is not sufficient enough to cope with the (forecasted) traffic demand, network extensions needs to be planned - Introducing of 2nd carrier on highly loaded sites - Filling coverage holes with new sites - Introducing capacity sites in order to unload a number of overloaded sites of a cluster
In general the steps 1 to 6 needs to be repeated several times until the required targets are meet.
April 2010
3G Dimensioning Guideline
Step 3: Counter based dimensioning
3G Dimensioning Guideline
Objective This step describes the dimensioning of individual sites during the daily work (mostly performed in regional offices). This is done by observation of important network counters of individual sites. In contrast to step 2 it is not based on planning data and model assumptions, it is based on the network and real life conditions.
April 2010
3G Dimensioning Guideline
Step 3: Expansion triggers and thresholds 1/3
3G Dimensioning Guideline
In general a pair of threshold for each important KPI needs to be defined 1. First threshold, indicating that a cell or site switches from low load to a mid to high load situation, so to say from green to yellow status
=> a planning action needs to be triggered, with enough time in advance before any action can be done and threshold 2 is meet
2. Second threshold, indicating that a cell or site switches from a mid to high load situation to a overload situation, so to say from yellow to red status => a action needs to be taken immediately to solve the overload situation, a proper planning is pre-condition
April 2010
3G Dimensioning Guideline
Step 3: Expansion triggers and thresholds 2/3
T2 T1
3G Dimensioning Guideline
time
The lead time t is individual for each KPI to be measured and therefore the setting of T1 and T2. For example the extension of a site with additional base band capacity is much faster done than the introduction of a fill in capacity site. Several open points exists: 1. 2. The system can be further refined, for instance with a hysteresis on the time axis. This might avoid expansions do to seasonal effects as indicated with the dotted line. Or depending on a site classification different thresholds T1 and T2 can be applied, for instance to distinguish basic and premium level coverage areas. Areas with lower importance may have a more relaxed threshold T1 (or T1 and T2)
As aggregation method for any KPI as busy hour (BH) the MAVG8 method takes place (8 highest peaks on separate days of a month). This is the same definition as used for the utilisation reporting.
30 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
3G Dimensioning Guideline
Step 3: Expansion triggers and thresholds 3/3
Aligned to the HSDPA guideline following triggers are defined, during the BH, depending on a general definition of coverage areas, differentiated between 1. triggers based on user perception The values shows only the trigger from yellow to red status! 2. triggers based on resource utilisation
The thresholds for green to yellow still to be defined. Hot spot coverage (HSPA+, up to 43.2 DL peak)
2% User Perception
3G Dimensioning Guideline
Parameter/Trigger
GoS (for CS services, independent from the blocking reason) Average user throughput (HSDPA/HSUPA) DL power for R99 traffic (incl. common channels) Code tree utilisation (incl. R99 and HSDPA) UL Load (R99 only) UL Load (R99 + HSUPA)
31 Radio Dimensioning Guideline, 2G, 3G VTN
2500 kbps / 1000 kbps 67.5% of max PA power 67.5% 60% (4 dB noise rise) 75% (6 dB noise rise)
C2 Vodafone Internal Version 1.0
Resource Utilisation
3G Dimensioning Guideline
Step 3: Expansion options
When one of the triggers listed on the page before is exceeded actions has to take place to solve the overload situation. Following options exists: 1. Optimisation (when not happened so far)
changing the antenna direction (tilt or azimuth) power settings (e.g. different pilot) handover settings to all surrounding or specific neighbour cells low
3G Dimensioning Guideline
2. Base band expansion => only when base band capacity is limited
3. Carrier expansion (when cluster cannot be further optimised)
dividing R99 and HSPA traffic on separate carrier equal distribution of traffic on both carriers adding an amplifier with higher power (when not happened so far) COSTS
=> suited for interference problems and code tree limitations 4. Cell splitting
Introducing higher order sectorisation Introducing capacity fill in sites Customized solutions (indoor, e.g. when lot of traffic comes from a business customer, or VAP etc.)
C2 Vodafone Internal Version 1.0 April 2010
high
3G Dimensioning Guideline
For HSPA 3.6, 7.2 and 14.4: demand driven, 1 carrier default
HSUPA 1.4 or 2 does not trigger an 2nd carrier by default, upgrade threshold driven (see next slides) Dynamic clustering for 2nd carrier is recommended (no fixed rings, fixed factors, etc.)
Tool based planning with ATOLL in dependence of predicted traffic Cluster of only one node B possible if traffic distribution indicates this Cluster size is demand driven no special requirements to cluster geometry
The general parameterization of each carrier should be as follows
The traffic should be diverted between the carriers in order to deliver the best performance for HSDPA users In case that R99 cannot be carried on the first carrier an overflow onto the second carrier should be allowed Before adding another carrier to a cell/sector it has to be ensured that optimization of antennas and radio resource management parameter is already on best level to maintain as low as possible interference
33 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
3G Dimensioning Guideline
It is assumed that majority of packed switched traffic is carried with HSPA technology
default: 3G carrier is used for both, HS and PS traffic.
loaded sites: 1st 3G carrier is mainly used for R99 traffic 2nd 3G carrier is mainly used for HS traffic
high loaded sites: 1st 3G carrier is mainly used for R99 traffic 2nd 3G carrier is used for R99 and HS traffic 3rd 3G carrier is used for HS traffic
April 2010
3G Dimensioning Guideline
2nd or 3rd carrier upgrade triggered by total traffic (sum of R99 and HSDPA) respectively resource shortage 2nd or 3rd carrier upgrades are considered when one of following criteria is meet during the busy hour1: - 2% of blocking (for CS services) is reached - DL power utilization is above 67.5% with to total available amplifier power - Code tree utilization is above 67.5% (total codes for R99 and HSDPA) - user throughput falls below 500 kbps by means of counter measurements Once UL counters deliver secure results - UL2 interference is above 4 dB (~60% load) for R99 in UL only - UL2 interference is above 6 dB (~75% load) when HSUPA is available
1 busy hour is defined as the average of the 8 busiest hours of a month. Each individual busy hour is defined by the highest used resource, which could be UL interference, DL power utilisation or code tree utilisation. 2 2 The UL counters delivers currently still unsecure results. Therefore it is possible to exclude UL as expansion trigger
35 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0
1 The
Upgrade threshold
67,5% 75%
In any case before introducing next carrier it must be checked that the bottle neck is within the air interface (exclude base band, IuB and Core) If it is turned out that only 1 or 2 high power users are responsible for high resource utilisation, upgrades shouldnt be done
April 2010
3G Dimensioning Guideline
Step 3: Example: 2nd Carrier Expansion rule VF-NL
Similar to the HSDPA guideline 3 KPI are observed to detect the need for a second carrier expansion 1. DL Channelization Codes 2. DL Power 3. Optional: HSDPA throughput1
3G Dimensioning Guideline
Basic rule
A cell should be considered as a candidate for 2nd carrier expansion when the RAB establishment failure ratio reaches 2% (for CS services) in the monitoring period 50% of the RAB failures due to lack of DL power 50% of the RAB failures due to lack of DL channelization codes 70% of the RAB failures due to the sum of both reasons above Average user throughput falls below 700 kbps respectively 1200 kbps for 10% of time1
Monitoring period
In line with the current busy hour definition a cell should be considered for 2nd carrier expansion when the conditions of the basic rule applies 8 times per month at different days.
Before adding a 2nd carrier it is mandatory to check that a cell cannot be further optimised in terms of changing antenna parameter for interference minimisation in terms of changing admission control parameters (e.g. reducing allowed SF8 RAB) in terms of changing handover settings and relations ..
1
The HSDPA throughput criterion is optional, because - it can happen that applications does not require a high throughput - that somewhere else in the network a bottleneck exists, e.g. access transmission
C2 Vodafone Internal Version 1.0 April 2010
3. Is increasingly requested by higher management level, e.g. for Investor Relations report
April 2010
April 2010
2G Resource loading
TRX 1 resource = 1 Dimension
3G Resource loading
UL Noise Codes
Channel Elements
Overall utilisation = MAX resource
Beside average utilisation a subset of KPIs have been defined to allow better understanding of situation, e.g.: Load distribution, resource & traffic are needed & KPIs have been defined
39 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
4 resources = 4 Dimensions
DL Power
Solution
2G 3G 3G
TRX (transmission and reception unit) DL power, UL Noise, Codes Base Band Units
More TRX Additional Carrier High power PA More base band boards
By considering the individual impacts of the resources it is possible to perform an assessment in terms of customer & financial impact
As consequence the base band utilisation is excluded from 3G KPI120 and will be reported as separate KPI (KPI119) in future Due to ongoing technical problems with UL measurements and weak correlation to traffic, UL utilisation is not longer included in the MAX function of KPI120, but still reported as sub KPI 120d
April 2010
Situation today
0.025
Utilisation KPIs are well defined for a certain period, allowing relative comparison in time and between networks Absolute targets/thresholds are defined yet, but implementation are not fully completed What should a target fulfil?
0.02
0.015
0.01
0.005
20
40
60
80
100
120
18%
April 2010
Targets:
~ 1%
#cells < 5%
#cells < 10% #cells >= 10%
April 2010
2G/3G Network Utilisation 3G Radio Network Utilisation, QMIS KPI 120 family
The KPI family contains of one main KPI and additional supporting KPIs giving more background information to improve understanding.
3G networks have several resources which needs to be considered: - Power in the DL available for each cell - The codes available for each cell - The UL interference allowed in each cell - The base band capacity boards to process the calls in each node B The final result for KPI 120 is the maximum of the utilisation of each resource. But different resources implies different actions Capacity assumed is always valid for one common design target per resource, which is typically 75% of total available resource. This is necessary to cope with fluctuations in the traffic during busy hour. Each KPI is calculated as average of 8 busiest hours of a month occurring at 8 different days. The busy hour is defined cell individually as highest utilisation of the resources.
A second busy hour definition exists based on traffic (MByte) carried in a cell. This busy hour is typically different from the busy defined on the resources.
44 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
2G/3G Network Utilisation 3G Radio Network Utilisation, QMIS KPI 120 family
Main KPI 120 Mean 3G Radio Network Utilisation. Results can be high because the highest value of the 4 considered resources is reported. To draw conclusions analysis of sub KPIs are recommended. Percentage of the network with a utilization above 90%, indicates critical cell which needs extension when traffic further increase. Percentage of the network with a utilization below 10%, indicates parts of network with very low traffic, mainly cells intended for coverage only. Average DL power utilisation. To resolve this additional carrier required, but high values are less critical in case that HSDPA traffic is the driver.
PI 120 d
Average UL interference utilisation. Higher values than the design target decreases the coverage mainly. To resolve additional carrier required.
Average Code Tree utilisation. To resolve this additional carrier required.
PI 120 e
Important: Compared to 2G networks 3G is a new technology. Capacity is soft and the optimisation of network design and radio resource management can improve utilisation, this means carrying more traffic with less utilised resources.
45 Radio Dimensioning Guideline, 2G, 3G VTN April 2010
2G/3G Network Utilisation 3G Radio Network Utilisation, QMIS KPI 120 family
PI 120 h Total BH traffic (throughput) per cell during busy hour defined when radio resource a maximal utilised. As KPI 120, but the utilisation is measured during hours when traffic is maximal instead when resources are maximal utilised. As KPI 120 h, total BH traffic (throughput) per cell, but busy hour is defined when traffic is maximal. Busy hour traffic of several services: voice, video telephony, R99 data, HSDPA and HSUPA data Percentage of soft handover traffic, needed to assess KPI 120 l-p depending of counter capabilities per vendor.
It is important to point out that in contrast to 2G in 3G two different busy hours exists. Firstly the busy hour of the resources which drives the required network extensions when no further optimisation is possible, secondly the busy hour of resources, when most traffic is carried. It is typical that both hours are not the same, because high usage of HSDPA as more efficient technology reduces utilisation compared to cases when voice or R99 data are highly used. Link to the whole document: <LINK>
46 Radio Dimensioning Guideline, 2G, 3G VTN April 2010
PI 119 a PI 119 b
Percentage of the network with a utilization above 90%, indicates critical node B which needs extension when traffic further increase. Percentage of the network with a utilization below 10%, indicates parts of network with very low traffic, mainly node B intended for coverage only.
Important: There is no further differentiation between UL and DL, because the mapping is very different from vendor to vendor. Some of them have a common resource for both directions.
April 2010
2G/3G Network Utilisation 2G Radio Network Utilisation, QMIS KPI 110 family
The KPI family contains of one main KPI and additional supporting KPIs giving more background information to improve understanding. 2G networks have one resource which needs to be considered: This is the number of time slots per cell. Capacity assumed is always calculated for one common design target, which is 40% usage of half rate and for 2% blocking ratio, independent from OpCo individual targets. This allow a fair comparison. Each KPI is calculated as average of 8 busiest hours of a month occurring at 8 different days. The busy hour is defined cell individually as highest number of used time slots.
April 2010
2G/3G Network Utilisation 2G Radio Network Utilisation, QMIS KPI 110 family
Main KPI 110 Mean 2G Radio Network Utilisation. Values higher than 100% are possible, when - HR usage during busy hour is much higher than 40%. - 2% of blocking cannot be maintained during busy hour. Percentage of the network with a Utilisation above 90%, indicates critical cell which needs extension when traffic further increase. Percentage of the network with a utilization below 10%, indicates parts of network with very low traffic, mainly cells intended for coverage only. Percentage of GPRS/ EDGE traffic. HR ratio design target, helps to justify the main result. Blocking design target, helps to justify the main result. AMR half rate terminal penetration. Independent if AMR-HR feature is activated or not. This KPI should show the potential which AMR-HR could have. Not necessarily to be updated every month.
April 2010
2G/3G Network Utilisation 2G Radio Network Utilisation, QMIS KPI 110 family
PI 110 g AMR-HR percentage of total traffic once the feature is introduced. High values allows good speech quality although HR is used and only half of capacity per customer is required. Total HR (conventional HR + AMR HR) percentage of total traffic (FR + HR) during busy hour. Percentage of cells which fulfil two conditions: Total HR > 40% AND Utilisation > 100% (combined trigger). Please note the total HR traffic consists of the sum of AMR HR and conventional HR.
PI 110 h PI 110 i
April 2010
=>
3G
UL utilisation (120d) causes many problems due to foreign interference (e.g. DECT phones) and unreliable measurements
=> introduction of more sophisticated method without success => finally excluded from KPI120 to avoid hiding results of more important DL or Code utilisation
In many cases base band utilisation has driven final result of KPI120
=> Separated as separate KPI (119) to avoid hiding air interface utilisation
51 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
from a customer perspective in terms of highest quality of service from the economical point of view in terms of lowest costs Traffic management is also driven by the general strategy, for instance When an operator has the strong interest to get rid of 2G as fast as possible the interest is to push as much as possible traffic on 3G => This may require more investments in 3G needs to be done earlier Is the strategy to use both radio networks in parallel with less than possible radio equipment the strategy can be, to push voice onto 2G and to push packet data services onto 3G => Probably higher OPEX costs due to longer time for running 2 networks in parallel Calculations by means of high level calculations for traffic management is one piece of a puzzle for delivering input for strategic decisions, but not the main driver. Therefore a strategy per OpCo is seen as predetermined.
52 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
Goal:
Relax voice IRAT thresholds to delay 3G to 2G HO and keep 3G voice traffic in 3G networks To switch cell change order off for packet Have a very relaxed PS IRAT threshold (alternative: switch triggers off) Expectation: HS to R99 transition due to coverage reason is avoided / minimised
April 2010
To switch cell change order (CCO) off for packet or set an extreme relaxed packet IRAT threshold
Exact values for trigger thresholds are vendor specific and depends on the site density of each operator
Option to increase pilot power. This could be at least a temporarily solution for further delay of 3G to 2G HO. (Trails have shown significant impact to 3G/2G traffic handling, e.g. VF Spain +15% and VF Germany +6% in 3G)
54 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0 April 2010
PS Ec: PS Ec/Io:
- 110 dBm - 14 dB
Typical Observation:
Ranges
PS EC/Io
=< -14
dB
April 2010
Back Up
April 2010
April 2010
. .
April 2010
April 2010
Utilisation KPIs describe resource usage reaching 100% when load exceeds 75%
Resource loading
DL Power
UL Noise
Antennas
Base
Station Access Transmission: Congestion in this link (connection the base station back to the RNC and core network) Leads to reduced throughput for PS services and eventually blocking for CS services Processing Capacity: Within the base station there are physical limits on channel processing capacity and also on Codes which are used to assign 3G Radio Bearers Power/Noise: Many elements formulate the overall power or link budget that the radio network is planned too (not least the site density). Every call/data session uses some of this power budget, excessive load will cause congestion, degradation of customer performance and reduces coverage
61 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0
75% load (design target) = 100% utilisation 100% utilisation does not automatically imply capacity spend. Full investigation is needed first
April 2010
NED
E/// inner urban -107 -15
UK
E/// ALU
NokSie E///
Vendor
-104 -106 -13 -103 -12 -99 Off -101 -14 -14 -105 -12 -105 -12 -102 -13
-102 -13
-105
-105 -14
-115 -11
-103 -12
-106 -13
-115 -18
-115 -15
-115 -15
-108 -14
-115 -10
-107 -13
Ranges
PS EC/Io
=< -14
dB
April 2010
Traffic development 3G
600 Bearerusage_Cv [Erlang]; KW33 Bearerusage_Cv [Erlang]; KW32 Cv12_duration in 3G per RAB [sec] ; KW33 Cv12_duration in 3G per RAB [sec] ; KW32 500 250
-98 -102
-105
Voicetraffic +23%
400
Usage/[Erlang]
200
150
300
100 200 Verweildauer in 3G: exposure 106 -> 129 sec, time + 22%
in 3G +24%
100
50
0 0 24 48 72 96 120 144
April 2010
140.000
1,1
20.000
1,05
0
7. 20 08 7. 20 08 7. 20 08 27 .0 7. 20 08 29 .0 7. 20 08 31 .0 7. 20 08 02 .0 8. 20 08 04 .0 8. 20 08 06 .0 8. 20 08 08 .0 8. 20 08 10 .0 8. 20 08 12 .0 8. 20 08 14 .0 8. 20 08 16 .0 8. 20 08 18 .0 8. 20 08 20 .0 8. 20 08 22 .0 8. 20 08 24 .0 8. 20 08 26 .0 8. 20 08
21 .0
23 .0
> Goal 2 fulfilled : Minimization of compressed mode activity Compressed mode activation -45%
64 Radio Dimensioning Guideline, 2G, 3G VTN C2 Vodafone Internal Version 1.0
25 .0
April 2010
120.000
1,35
IRAT-HO -31%
0,3
No IRAT HO -31%
50.000
HO of IRAT No HO IRAT Anzahl
40.000
0,25
0
8 .2 00 27 8 .0 7. 20 08 29 .0 7. 20 08 31 .0 7. 20 08 02 .0 8. 20 08 04 .0 8. 20 08 06 .0 8. 20 08 08 .0 8. 20 08 10 .0 8. 20 08 12 .0 8. 20 08 14 .0 8. 20 08 16 .0 8. 20 08 18 .0 8. 20 08 20 .0 8. 20 08 22 .0 8. 20 08 24 .0 8. 20 08 26 .0 8. 20 08 .2 00 7. 20 08
0,1
21 .0 7
25 .0 7
23 .0
April 2010
0,70%
P507 / % RAB loss ratio_CS [%]
Drop/Erlang -17%
Drop pro Erlang
0,60%
0,15
0,50%
Drop/Erlang -17%
0,40%
0,1
0,30%
laboratory study shows voice quality good until RSCP ~ -112 dBm
0,20%
0,05
0,10%
0,00%
08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 08
7.
7.
7.
7.
7.
7.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8. .0 24 26
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
21
23
25
27
29
31
02
04
06
08
10
12
14
16
18
20
22
April 2010
.0
8.
11 /0 2/ 20 06
18 /0 2/ 20 06
25 /0 2/ 20 06
04 /0 3/ 20 06