Upload
duc-nguyen
View
290
Download
33
Embed Size (px)
DESCRIPTION
NSN_RNC Dimensioning
Citation preview
1 © Nokia Siemens NetworksFor internal use
3GTPL - RNC Dimensioning
2 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC Variants
RNC196 RNC450 RNC2600
8
3 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC 196
RNC196 RNC450 RNC2600
8
4 © Nokia Siemens NetworksFor internal use
RAN1766SW Gigabit level RNC196 step 8 upgrade
5 © Nokia Siemens Networks
RAN1766 Gigabit level RNC196/step 8 upgrade Introduction
Brief description:• Feature introduces new RNC196 step for RU20.• Feature describes basic requirements and extra units needed for the
upgrade.
Motivation and benefits:• Possibility of using RNC196 in RU20 release.• The operator can get more value for the RNC196 investment
6 © Nokia Siemens Networks
RAN1766 Gigabit level RNC196/step 8 upgrade Functional description
• The new configuration utilises the CDSP-DH and interface unit upgrades that are implemented in RNC196 step 7. Additionally, some new CDSP-DH units are needed.
• CDSP-DH upgrade is in RNC196 step 7,providing HSPA peak rate increase capability. It is introduced in RU10 release (RAN1226). Eight (8) CDSP-DH units are needed in this upgrade.
• Interface unit upgrade for IP is introduced in RU10. It requires SF10E for SFU and the NP2GE-B interface unit(s) for physical Gigabit Ethernet interfaces.
• In RU20 release, new optional STM-1 ATM interface upgrade is supported. NP8S1-B can be taken into use in RNC196 step 8.
• RNC196 step 8 requires that either the IP interface upgrade or the new STM-1 interface upgrade is done to all RAN interfaces and also the CDSP-DH upgrade for HSPA peak rate increase is carried out. Also, approximately 8 CDSP-DH units are needed in addition to the HSPA peak rate upgrade (8 CDSP-DH units).
7 © Nokia Siemens Networks
CDSP-DH
SF10E
NP2GE
HSPA Peak rate IP
RNC196 CS 1-5
HSPA Peak rate IP
SF10E
NP2GECDSP-DH
RNC196 CS 6-7 CS7
RNC196 CS 8
CS8
reconfiguration
CS 5 to CS6-7
CS 5 to CS6-7
Optional Stand alone OMS
NP8S1P
8 CDSP-DH added
SF10E
NP2GEP
8 x ICSU added Removed: GTPU A2SU NIS1/NIP1
8 x CDSP-C => CDSP-DH for
HSPA peak rate
NPS1 +NPGE Max. count = 4 pairsNPS1 Max. count =3 pairs
NP2GE
IP
RAN1766 Gigabit level RNC196/step8 upgrade RNC196 Upgrade paths
9 © Nokia Siemens Networks
RU20 Capacity Figures for RNC196/1to8
10 © Nokia Siemens Networks
RU20 Capacity Figures for RNC196/1to8
HSPA Capacity Figures
HSDPA does not include SHO overhead. HSUPA includes 40% SHO in Iub
*) on top of GTP-U layer
11 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC 450
RNC196 RNC450 RNC2600
8
12 © Nokia Siemens Networks
HSPA Capacity Figures (below)
RU20 Capacity Figures for RNC450/1to3
HSDPA does not include SHO overhead. HSUPA includes 40% SHO in Iub
1) on top of GTP-U layer
13 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC2600
RNC196 RNC450 RNC2600
8
14 © Nokia Siemens Networks
RU20 Capacity Figures for RNC2600/1to3
*) recommended up to 1600 BTSs
Capacity & reference call mix model
15 © Nokia Siemens Networks
HSPA Capacity Figures (below)
RU20 Capacity Figures for RNC2600/1to3
HSDPA does not include SHO overhead. HSUPA includes 40% SHO in Iub
*) on top of GTP-U layer
16 © Nokia Siemens NetworksFor internal use
RAN1793 SW Enhanced RNC2600
17 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600 Introduction
Brief description:•This feature describes how RNC2600 capacity can be increased by SW enhancements.
Motivation and benefits:•Higher RNC capacity allows to handle more subscribers, more traffic•Higher RNC capacity allows to decrease number of RNC’s in network
18 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600 RNC capacity
With SW optimisations the RNC2600 capacityis increased in RU20 as follows:
• PS data throughput in Iub (DL+UL):
• AMR capacity:
• Busy Hour Call•Attempts:•The HW configuration will remain as it is in RU10 release.
3500 MbpsRU202800 Mbps
50 000 ErlRU2020 000 Erl
RU201 440 000b 2 000 000RU20
20 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600 RNC2600 Capacity
RNC model/capacity RNC2600 Step1 RNC2600 Step2 RNC2600 Step3
Iub DL throughput [Mbps] 1100 1800 2500
AMR capacity [Erlangs with 12.2 kbit/s codec] 17000 34000 50000
CS voice over HSPA capacity [Erl] 15000 30000 40000
BTS/Carrier connectivity 1440 2100 2800
HSDPA/HSUPA peak rate per user [Mbps] 21.1/5.8 21.1/5.8 21.1/5.8
RRC connected state UEs 88000 152000 200000
HSPA active users per RNC 20000 35000 50000
Iu-ps HSDPA net bit rate [Mbit/s] 1010 1630 2250
Iu-ps HSUPA net bit rate [Mbit/s] 300 490 675
HSDPA BTS/Carriers 1440 2100 2800
21 © Nokia Siemens Networks
RNC2600 with SW Configurable Capacity LicensingHigh capacity RNC2600 enables capacity licensing in three dimensionsCapacity can be freely SW configured for• Data (Iub PS Data)• Voice (AMR Erlang)• Number of CarriersCapacity upgrades are possible only with an upgrade of a SW licenceNo HW changes is required
capacity step 10….900 Mbps DL0….8000 Erl0….1440 Cells
capacity step 2
0….1500 Mbps DL0….14000 Erl0….2100 Cells
capacity step 3
0….2000 Mbps DL0….20000 Erl0….2800 Cells
22 © Nokia Siemens Networks
RNC2600 AMR Capacity Licensing• RNC counts the number of simultaneous AMR RABs periodically.
• When the amount is greater than the licensed capacity, RNC does not admit new AMR RABs as long as the amount decreases below licensed limit.
• Some overcapacity is allowed and hysteresis is used between starting and stopping the AMR limiting.
Licenced AMR capacity
HW max capacity
PRFILE: AMR Licence Warning Threshold (eg. 90%)
time
#AMR RABs
PRFILE: AMR LicenceDuration to Set Warning (eg. 600s)
Set alarm: “licence_capacity_warning_a”
Cancel alarm: “licence_capacity_warning_a”
PRFILE: AMR LicenceDuration to Cancel Warning (eg. 7 d)
23 © Nokia Siemens Networks
RNC2600 PS Throughput Licensing• PS Throughput licence gives the maximum RNC downlink PS throughput in Mbit/s.
• When the throughput is higher than the licensed capacity, RNC starts to limit downlink PS throughput on each Iu-PS interface.
• Some overcapacity is allowed and hysteresis is used between starting, decreasing and stopping the throughput limiting.
Licenced PS capacity
HW max capacity
PRFILE: PS LicenceWarning Threshold(eg. 90%)
time
PS Throughput
PRFILE: PS LicenceDuration to Set Warning (eg. 600s)
Set alarm: “licence_capacity_warning_a”
Cancel alarm: “licence_capacity_warning_a”
PRFILE: PS LicenceDuration to Cancel Warning (eg. 7 d)
24 © Nokia Siemens NetworksFor internal use
RAN1795 RNC2600 Coverage Optimized Solution
25 © Nokia Siemens Networks
RAN1795 RNC2600 coverage optimized solution Functional description
• Coverage solution is supported by each RNC2600 HW configuration. RNC HW configuration is always the same between the capacity and coverage solution.
• Selection of the configuration mode is done by a RNC capacity SW license keys and no HW changes are required. When the cell connectivity is more than 2800 the maximum PS data throughput and AMR capacity is decreased by 10 %, compared to the RU20 level of cell connectivity.
• Step1 – 1 Cabinet• Step2 – 1.5 Cabinet• Step3 – 2 Cabinets
RNC 2600 CellsAMR Capacity [Erl]
PS Iub data throughput (DL + UL) [Mbit/s]
Step 1 2450 16200 1420Step 2 3600 31500 2270Step 3 4800 45000 2800
26 © Nokia Siemens Networks
RAN1795 RNC2600 coverage optimized solution Activation and operation
• RNC2600 capacity is controlled with licenses defined in feature RAN1198 "RNC2600 SW License Key Controlled Capacity".
• No new license keys are introduced due to this feature RAN1795 RNC2600 coverage optimized solution.
27 © Nokia Siemens Networks
Network dimensioning impact
• RAN1766 Gigabit level RNC196/step8– Additional RNC196 step to take into account during RNC dimensioning
• RAN1793 SW Enhanced RNC2600– Increased RNC2600 capacity limits for all steps need to be taken into
account during RNC Dimensioning
• RAN1795 RNC2600 coverage optimized solution– Possibility of choose higher RNC2600 connectivity limits in cost of
capacity limits in the RNC calculation.
30 © Nokia Siemens Networks
Add SHO and protocol
overhead
Add SHO and protocol overhead
RNC dimensioning based on throughput
Input: Traffic per site in traffic types
Calculate AMR Load
Calculate CS Data load
Calculate NRTData Load
Number of RNCs needed
Apply traffic mix rule
Calculate HSDPALoad
Apply FP Rate
32 © Nokia Siemens Networks
RNC dimensioning based on throughput Frame protocol bit rate
• The load for the CS-Data and NRT traffic needs to be considered at the Frame protocol level
• The RNC throughput limits have been calculated for this reference level
Service (TTI) FP bit rateAMR12.2 16 400CS 64 (20 ms) 66 100PS AM 64 (20ms) 69 500PS AM 128 (20ms) 136 700PS AM 256 (10ms) 273 300PS AM 384 (10ms) 408 000
33 © Nokia Siemens Networks
RNC Dimensioning HSDPA Load
• The HSDPA load is calculated separate from R99 NRT Traffic
• Note that – HSDPA connections can not be in SHO– The protocol overheads are variable
depending on the HSDPA rate.• The overhead variation is presented in
the attached table • RNC is such a big aggregation point for
the traffic that we can use the average user traffic figures to determine the HSDPA traffic load for the RNC
Calculate HSDPALoad
Apply FP Rate
( ) erfic_Per_UsHSDPA_TrafdFP_Overhea1 ficHSDPA_TrafSites teUsersPerSi∑ ∑×+=
Rate above RLC [kbps]
FP bit rate [kbps]
FP overhead over RLC
64 74 16%128 142 11%256 276 8%384 410 7%512 545 6%1024 1084 6%1600 1694 6%2048 2165 6%3360 3557 6%
34 © Nokia Siemens Networks
RNC Dimensioning HSDPA Load Example• We have 2000 sites, 1000 users per site.• Each user downloads a 200 kByte file
during the busy hour• We estimate the average throughput for a
user to be 512 kbps over RLC– FP OH = 6%
Mbpskbps
941444.0100020001.06
1.06 ficHSDPA_Traf1..2000i 1..1000j 3600
8200
≈×××=
×= ∑ ∑= =×
Calculate HSPALoad
Apply FP Rate
Rate above RLC [kbps]
FP bit rate [kbps]
FP overhead over RLC
64 74 16%128 142 11%256 276 8%384 410 7%512 545 6%1024 1084 6%1600 1694 6%2048 2165 6%3360 3557 6%
40 © Nokia Siemens NetworksFor internal use
RNC Dimensioning Exercise
41 © Nokia Siemens Networks
Dimensioning Input
• The RNC under investigation is an RNC2600 Step1• The input assumes activity factor of the NRT services = 15%• Number of Sites = 254• Number of Subscribers per Site = 403• Soft Handover = 30%• CS Data blocking = .1%
42 © Nokia Siemens Networks
Input tableTraffic Model per user
Service mEr/Sub RAB [Kbps] Activity
Service Penetrati
on
BH Traffic Volume [Kbits]
Voice UL 28.44 12.2 0.5 100% 572.12DL 28.44 12.2 0.5 100% 572.12
Video UL 0.11 64 1 100% 24.95DL 0.11 64 1 100% 24.95
Service Kbps/Sub RAB [Kbps] Activity
Service Penetrati
on
BH Traffic Volume [Kbits]
Internet 128 UL 0.0026289 128 - 100% 9.46Internet 128 DL 0.0012680 128 - 100% 4.56Internet 16 UL 0.0001543 16 - 100% 0.56Internet 16 DL 0.0010379 16 - 100% 3.74Internet 256 UL 0.0000000 256 - 100% 0.00Internet 256 DL 0.0005125 256 - 100% 1.84Internet 32 UL 0.0000013 32 - 100% 0.00Internet 32 DL 0.0000492 32 - 100% 0.18Internet 384 UL 0.0000000 384 - 100% 0.00Internet 384 DL 0.0058320 384 - 100% 21.00Internet 64 UL 0.0005675 64 - 100% 2.04Internet 64 DL 0.0002407 64 - 100% 0.87Internet 8 UL 0.0000008 8 - 100% 0.00Internet 8 DL 0.0000089 8 - 100% 0.03HSDPA UL 0.0228467 64 - 100% 82.25
DL 0.1163493 HS I/B - 100% 418.86
43 © Nokia Siemens Networks
Add SHO and protocol
overhead
Add SHO and protocol overhead
RNC dimensioning based on throughput
Input: Traffic per site in traffic types
Calculate AMR Load
Calculate CS Data load
Calculate NRTData Load
Number of RNCs needed
Apply traffic mix rule
Calculate HSDPALoad
Apply FP Rate
This exercise analyses only the throughput limitation of the RNC
44 © Nokia Siemens Networks
AMR Load
The AMR Load is calculated as follows:
Sum all AMR traffic from all users in all sites under the RNC
_____ mErl/Sub * _____ NodeBs * _____ Subscribers per NodeB
= ______ Erl (Enter in AMR Erl)
The RNC2600 Step1 limit is _____Erl (Enter in RNC2600 Step 1 limit)The RNC is ____/____ = ___% loaded of the max load (Calculated)
Calculate AMR Load
45 © Nokia Siemens Networks
CS Data Load The CS DATA Load is calculated as follows:Sum all CS Data traffic from all users in all sites under the RNC
_____ mErl/Sub * _____ NodeB * _____ Sub/NodeB___________________________________________
1000= ______ Erl (Enter in CS Data load)
Add SHO @30% = _____Erl (Enter in Load with SHO)
NP add-in - Calculate Erlb Chans with .1% blocking (.001)
=____Chans x FP layer br____(Enter in Bearer Rate FP)
=________Mbps FP Load level
Add SHO and protocol overhead
Calculate CS Data load
(Applying ErlangB before SHO would give 10% more CS Data load)
46 © Nokia Siemens Networks
PS Data Load – 128, 256,384 Kbps D/L The PS Data Load is calculated as follows:
PS NRT (Bearer Rate) D/L Data traffic from all users in all sites under the RNC
_____ Kbps/Sub (per D/L BR) * _____ NodeB * _____ Sub/NodeB
= ______ Kbps (Enter in Measured Load for BR)
Add SHO @30% = _____Kbps (Enter in Load with SHO)
RNC Measured Load = Sites_NRT_bearer_i Kbps___________________ (Enter Bearer rate and AF)
Bearer_i_rate_x_AF= ________Erl
NP add-in - Calculate Erlb Chans with .1% blocking (.001)
=____Chans x FP layer br____(Enter in Bearer Rate FP)
=________Mbps FP Load level
Add SHO and protocol overhead
Calculate PS Data load
47 © Nokia Siemens Networks
PS Data Load – 64 Kbps D/L PS NRT (Bearer Rates 8,16,32 & 64 Kbps aggregated) D/L Data traffic from all users in all sites under the RNC
8 Kbps/Sub per D/L +16 Kbps/Sub per D/L+ 32Kbps/Sub per D/L+64Kbps/Sub per D/L BR * _____ NodeB * _____ Sub/NodeB
= ______ Kbps (Enter in Measured Load for BR)
Add SHO @30% = _____Kbps (Enter in Load with SHO)
RNC Measured Load = Sites_NRT_bearer_i Kbps___________________ (Enter Bearer rate and AF)
Bearer_i_rate_x_AF= ________Erl
NP add-in - Calculate Erlb Chans with .1% blocking (.001)
=____Chans x FP layer br____(Enter in Bearer Rate FP)
=________Mbps FP Load level
Add SHO and protocol overhead
Calculate PS Data load
48 © Nokia Siemens Networks
HSDPA Data Load
HSDPA Traffic _______ * _____ NodeB * _____ Sub/NodeB
= ______ Kbps (Enter in Measured Load for BR)
RNC Measured Load x FP overhead over RLC (6%) =
________Mbps Rate above RLC [kbps]
FP bit rate [kbps]
FP overhead over RLC
64 74 16%
128 142 11%
256 276 8%
384 410 7%
512 545 6%
1024 1084 6%
1600 1694 6%
2048 2165 6%
3360 3557 6%
Calculate HSPALoad
Apply FP Rate
49 © Nokia Siemens Networks
All NRT Load
Add SHO and protocol
overhead
Calculate NRTData Load
NRT64 NRT128 NRT256 NRT384 HSDPA
Measured Load - Erl for CS - Mbps for PS
136.8 129.8 52.5 597.0 11909.7
Load with SHO 177.9 168.7 68.2 776.1 11909.7
Bearer Nominal Rate 64 128 256 384 N/AActivity Factor 15% 15% 15% 15% N/A
Blocking probability 0.1% 0.1% 0.1% 0.1% N/A
Simultaneous users 33 20 8 26 N/ABearer Rate FP 69.5 136.7 273.3 408 N/A
FP Level Load (Mbps) 2.29 2.73 2.19 10.61 12.62
50 © Nokia Siemens Networks
RNC Dimensioning Calculating RNC Throughput
Check Throughput Limitations
5% is only for RNC2600, for older RNC types 25% is
valid
Total throughput check
CS Data throughput check
PS Data traffic mix check
51 © Nokia Siemens Networks
AMR Erlangs CS Data PS Data NRT64 NRT128 NRT256 NRT384 HSDPA
Measured Load - Erl for CS - Mbps for PS 2910.8 11.1 136.8 129.8 52.5 597.0 11909.7Load with SHO N/A 14.4 177.9 168.7 68.2 776.1 11909.7Bearer Nominal Rate N/A N/A 64 128 256 384 N/AActivity Factor N/A N/A 15% 15% 15% 15% N/ABlocking probability N/A 0.1% 0.1% 0.1% 0.1% 0.1% N/ASimultaneous users N/A 27 33 20 8 26 N/ABearer Rate FP N/A 66.1 69.5 136.7 273.3 408 N/AFP Level Load (Mbps) N/A 1.8 30.4 2.29 2.73 2.19 10.61 12.62RNC450 Step2 limit (RAS 6250 300 300 216 258 302 303 270Load/Limit % 46.6% 0.6% 10.1% 1.1% 1.1% 0.7% 3.5% 4.7%
Total Throughput Check 57.3%
CS Data < 25% Max Iub T OK
DMCU Max Check 11.0%
The check sums the load/limit ratios for all bearers and checks that this is less than 100%
RNC Dimensioning Checking PS Traffic Mix
Check Throughput LimitationsPS Data traffic mix check
The DMCUmax limits are taken here from RAS06 RNC Product Description
52 © Nokia Siemens Networks
RNC Dimensioning – RU10 Checking PS Traffic Mix• The limits for the NRT max and HSDPA load per bearer type are shown in the
tables. These are in reference to the PS traffic load formula shown on the previous slide.
• The additional check is needed because different bearers load the DMCUs in different manner.
• Note the differences between the releases• In RU10 in case of DMCU upgrade needed to enable HSDPA 14.4 peak rate. With
the upgrade the maximum DMCU throughputs are increased so that the defined maximum Iub throughput can be achieved with any single traffic type, i.e. also with R99 64 kbit/s RABs.
– After the upgrade the PS Traffic mix check is not needed any more.
RNC450 (RN2.2 RAS05.1)
150 300 450
Max PS64 [Mbps] 91 189 323Max PS128 [Mbps] 151 307 499Max PS256 [Mbps] 192 385 656Max PS384 [Mbps] 184 383 570HSDPA 135 270 405
RNC450 (RN3.0 – RAS06) 150 300 450
Max PS64 [Mbps] 120 216 344
Max PS128 [Mbps] 144 258 436
Max PS256 [Mbps] 153 302 452
Max PS384 [Mbps] 154 303 451
HSDPA 135 270 405