Date post: | 30-Oct-2015 |
Category: |
Documents |
Upload: | anshul-srivastava |
View: | 78 times |
Download: | 0 times |
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 1/42
1 © Nokia Siemens Networks
For internal use
3GTPL - RNC Dimensioning
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 2/42
2 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC Variants
RNC196 RNC450 RNC2600
8
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 3/42
3 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC 196
RNC196 RNC450 RNC2600
8
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 4/424 © Nokia Siemens Networks
For internal use
RAN1766SW Gigabit level RNC196 step 8 upgrade
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 5/425 © Nokia Siemens Networks
RAN1766 Gigabit level RNC196/step 8 upgradeIntroduction
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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 6/426 © Nokia Siemens Networks
RAN1766 Gigabit level RNC196/step 8 upgradeFunctional description
• The new configuration utilises the CDSP-DH and interface unit upgrades thatare implemented in RNC196 step 7. Additionally, some new CDSP-DH unitsare needed.
• CDSP-DH upgrade is in RNC196 step 7,providing HSPA peak rate increasecapability. It is introduced in RU10 release (RAN1226). Eight (8) CDSP-DHunits 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-1interface upgrade is done to all RAN interfaces and also the CDSP-DHupgrade for HSPA peak rate increase is carried out. Also, approximately 8
CDSP-DH units are needed in addition to the HSPA peak rate upgrade (8CDSP-DH units).
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 7/427 © Nokia Siemens Networks
CDSP-DH
SF10E
NP2GE
HSPA
Peak rate IP
RNC196CS 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
OptionalStandaloneOMS
NP8S1P
8 CDSP-DH added
SF10E
NP2GEP
8 x ICSU added Removed:GTPU
A2SUNIS1/NIP1
8 x CDSP-C=> CDSP-DH for HSPA peak rate
NPS1 +NPGEMax. count = 4 pairs
NPS1Max. count =3 pairs
NP2GE
IP
RAN1766 Gigabit level RNC196/step8 upgradeRNC196 Upgrade paths
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 8/42
9 © Nokia Siemens Networks
RU20 Capacity Figures for RNC196/1to8
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 9/42
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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 10/42
11 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC 450
RNC196 RNC450 RNC2600
8
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 11/42
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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 12/42
13 © Nokia Siemens Networks
3
211 2
3
4
5
6 7
RNC Dimensioning – RNC2600
RNC196 RNC450 RNC2600
8
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 13/42
14 © Nokia Siemens Networks
RU20 Capacity Figures for RNC2600/1to3
*) recommended up to 1600 BTSs
Capacity & reference call mix model
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 14/42
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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 15/42
16 © Nokia Siemens Networks
For internal use
RAN1793 SW Enhanced RNC2600
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 16/42
17 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600Introduction
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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 17/42
18 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600RNC 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
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 18/42
20 © Nokia Siemens Networks
RAN1793 SW Enhanced RNC2600RNC2600 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
C2600 S C f C
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 19/42
21 © Nokia Siemens Networks
RNC2600 with SW Configurable CapacityLicensing
High capacity RNC2600enables capacity licensingin three dimensions
Capacity can be freely SWconfigured for
• Data (Iub PS Data)
• Voice (AMR Erlang)• Number of Carriers
Capacity upgrades are
possible only with anupgrade of a SW licence
No HW changes is required
capacity step 1
0….900 Mbps DL
0….8000 Erl
0….1440 Cells
capacity step 2
0….1500 Mbps DL
0….14000 Erl
0….2100 Cells
capacity step 3
0….2000 Mbps DL
0….20000 Erl
0….2800 Cells
RNC2600 AMR C it Li i
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 20/42
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 notadmit new AMR RABs as long as the amount decreases below licensedlimit.
• Some overcapacity is allowed and hysteresis is used between starting andstopping the AMR limiting.
LicencedAMR capacity
HW max capacity
PRFILE:AMR
LicenceWarning
Threshold (eg. 90%)
time
#AMR RABs
PRFILE:AMR Licence
Durat ion to Set
Warning (eg. 600s)
Set alarm:
“licence_capacity_warning_a”
Cancel alarm:
“licence_capacity_warning_a”
PRFILE:AMR Licence
Dura ti on t o Cancel
Warning (eg. 7 d)
RNC2600 PS Th h t Li i
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 21/42
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 tolimit 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 Licence
Warni ng Threshold (eg. 90%)
time
PS Throughput
PRFILE:PS Licence
Dura ti on t o Set
Warning (eg. 600s)
Set alarm:
“licence_capacity_warning_a”
Cancel alarm:
“licence_capacity_warning_a”
PRFILE:PS Licence
Dura ti on t o Cancel
Warning (eg. 7 d)
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 22/42
24 © Nokia Siemens Networks
For internal use
RAN1795 RNC2600 Coverage Optimized Solution
RAN1795 RNC2600 coverage optimized solution
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 23/42
25 © Nokia Siemens Networks
RAN1795 RNC2600 coverage optimized solutionFunctional description
• Coverage solution is supported by each RNC2600 HW configuration.RNC HW configuration is always the same between the capacity andcoverage solution.
• Selection of the configuration mode is done by a RNC capacity SWlicense keys and no HW changes are required. When the cell connectivityis more than 2800 the maximum PS data throughput and AMR capacity isdecreased by 10 %, compared to the RU20 level of cell connectivity.
• Step1 – 1 Cabinet
• Step2 – 1.5 Cabinet
• Step3 – 2 Cabinets
RNC 2600 Cells
AMR
Capacity [Erl]
PS Iub data
throughput (DL +
UL) [Mbit/s]
Step 1 2450 16200 1420
Step 2 3600 31500 2270
Step 3 4800 45000 2800
RAN1795 RNC2600 coverage optimized solution
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 24/42
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 RAN1795RNC2600 coverage optimized solution.
Network dimensioning impact
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 25/42
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 intoaccount during RNC Dimensioning
• RAN1795 RNC2600 coverage optimized solution
– Possibility of choose higher RNC2600 connectivity limits in cost of
capacity limits in the RNC calculation.
RNC dimensioning based on throughput
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 26/42
30 © Nokia Siemens Networks
Add SHO and
protocoloverhead
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 NRT
Data Load
Number of RNCs needed
Apply traffic mix rule
Calculate HSDPA
Load
Apply FP
Rate
RNC dimensioning based on throughput
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 27/42
32 © Nokia Siemens Networks
RNC dimensioning based on throughputFrame 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 rate
AMR12.2 16 400
CS 64 (20 ms) 66 100
PS AM 64 (20ms) 69 500
PS AM 128 (20ms) 136 700
PS AM 256 (10ms) 273 300
PS AM 384 (10ms) 408 000
RNC Dimensioning
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 28/42
33 © Nokia Siemens Networks
RNC DimensioningHSDPA Load
• The HSDPA load is calculated separatefrom R99 NRT Traffic
• Note that
– HSDPA connections can not be in SHO
– The protocol overheads are variabledepending on the HSDPA rate.
• The overhead variation is presented inthe attached table
• RNC is such a big aggregation point for the traffic that we can use the averageuser traffic figures to determine theHSDPA traffic load for the RNC
Calculate HSDPA
Load
Apply FP
Rate
( ) er fic_Per_UsHSDPA_Traf dFP_Overhea1ficHSDPA_Traf Sites teUsersPerSi∑ ∑×+=
Rateabove RLC[kbps]
FP bit rate[kbps]
FPoverheadover 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%
RNC Dimensioning
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 29/42
34 © Nokia Siemens Networks
RNC DimensioningHSDPA Load Example
• We have 2000 sites, 1000 users per site.
• Each user downloads a 200 kByte fileduring the busy hour
• We estimate the average throughput for a
user to be 512 kbps over RLC – FP OH = 6%
Mbps
kbps
941
444.0100020001.06
1.06ficHSDPA_Traf 1..2000i 1..1000 j 3600
8200
≈
×××=
×= ∑ ∑= =
×
Calculate HSPA
Load
Apply FP
Rate
Rateabove RLC[kbps]
FP bit rate[kbps]
FPoverheadover 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%
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 30/42
40 © Nokia Siemens Networks
For internal use
RNC Dimensioning Exercise
Dimensioning Input
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 31/42
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%
Input table
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 32/42
42 © Nokia Siemens Networks
pTraffic Model per user
Service mEr/Sub RAB [Kbps] Activity
ServicePenetrati
on
BHTrafficVolume[Kbits]
Voice UL 28.44 12.2 0.5 100% 572.12
DL 28.44 12.2 0.5 100% 572.12
Video UL 0.11 64 1 100% 24.95
DL 0.11 64 1 100% 24.95
Service Kbps/Sub RAB [Kbps] Activity
ServicePenetrati
on
BHTrafficVolume[Kbits]
Internet 128 UL 0.0026289 128 - 100% 9.46
Internet 128 DL 0.0012680 128 - 100% 4.56
Internet 16 UL 0.0001543 16 - 100% 0.56
Internet 16 DL 0.0010379 16 - 100% 3.74
Internet 256 UL 0.0000000 256 - 100% 0.00
Internet 256 DL 0.0005125 256 - 100% 1.84
Internet 32 UL 0.0000013 32 - 100% 0.00
Internet 32 DL 0.0000492 32 - 100% 0.18
Internet 384 UL 0.0000000 384 - 100% 0.00
Internet 384 DL 0.0058320 384 - 100% 21.00
Internet 64 UL 0.0005675 64 - 100% 2.04
Internet 64 DL 0.0002407 64 - 100% 0.87
Internet 8 UL 0.0000008 8 - 100% 0.00
Internet 8 DL 0.0000089 8 - 100% 0.03
HSDPA UL 0.0228467 64 - 100% 82.25
DL 0.1163493 HS I/B - 100% 418.86
RNC dimensioning based on throughput
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 33/42
43 © Nokia Siemens Networks
Add SHO and
protocoloverhead
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 NRT
Data Load
Number of RNCs needed
Apply traffic mix rule
Calculate HSDPA
Load
Apply FP
Rate
This exercise analyses only
the throughput limitation of
the RNC
AMR Load
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 34/42
44 © Nokia Siemens Networks
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
CS Data Load
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 35/42
45 © Nokia Siemens Networks
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)
PS Data Load – 128, 256,384 Kbps D/L
Calculate PS
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 36/42
46 © Nokia Siemens Networks
, , pThe 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 andprotocol overhead
Data load
PS Data Load – 64 Kbps D/L
C l l t PS
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 37/42
47 © Nokia Siemens Networks
p
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
HSDPA Data Load
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 38/42
48 © Nokia Siemens Networks
HSDPA Traffic _______ * _____ NodeB * _____ Sub/NodeB
= ______ Kbps (Enter in Measured Load for BR)
RNC Measured Load x FP overhead over RLC (6%) =
________Mbps Rate aboveRLC [kbps]
FP bit rate[kbps]
FP overheadover 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 HSPA
Load
Apply FP
Rate
All NRT Load
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 39/42
49 © Nokia Siemens Networks
Add SHO and
protocol
overhead
Calculate NRT
Data 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/A
Activity Factor 15% 15% 15% 15% N/A
Blocking probability 0.1% 0.1% 0.1% 0.1% N/A
Simultaneous users33 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
RNC Dimensioning
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 40/42
50 © Nokia Siemens Networks
Calculating RNC ThroughputCheck
Throughput Limitations
5% is only for RNC2600, for
older RNC types 25% isvalid
Total throughput check
CS Data throughput check
PS Data traffic mix check
RNC Dimensioning
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 41/42
51 © Nokia Siemens Networks
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.7
Bearer Nominal Rate N/A N/A 64 128 256 384 N/A
Activity Factor N/A N/A 15% 15% 15% 15% N/A
Blocking probability N/A 0.1% 0.1% 0.1% 0.1% 0.1% N/A
Simultaneous users N/A 27 33 20 8 26 N/A
Bearer Rate FP N/A 66.1 69.5 136.7 273.3 408 N/A
FP Level Load (Mbps) N/A 1.8 30.4 2.29 2.73 2.19 10.61 12.62
RNC450 Step2 limit (RAS 6250 300 300 216 258 302 303 270
Load/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 OK
DMCU Max Check 11.0%
The check sums the load/limit ratios for
all bearers and checks that this is less than 100%
Checking PS Traffic MixCheck
Throughput LimitationsPS Data traffic mix check
The DMCUmax limits are taken here from RAS06 RNC Product Description
RNC Dimensioning – RU10
7/16/2019 132592287-08-RNC-Dimensioning
http://slidepdf.com/reader/full/132592287-08-rnc-dimensioning 42/42
52 © Nokia Siemens Networks
Checking PS Traffic Mix
• The limits for the NRT max and HSDPA load per bearer type are shown in thetables. These are in reference to the PS traffic load formula shown on the previousslide.
• The additional check is needed because different bearers load the DMCUs indifferent manner.
• Note the differences between the releases
• In RU10 in case of DMCU upgrade needed to enable HSDPA 14.4 peak rate. Withthe upgrade the maximum DMCU throughputs are increased so that the definedmaximum 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 323
Max PS128 [Mbps] 151 307 499
Max PS256 [Mbps] 192 385 656
Max PS384 [Mbps] 184 383 570
HSDPA 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