RNC & 3G InterfacesRNC & 3G InterfacesDimensioningDimensioning
Ramesh Babu
Nokia Networks
3G&IP Network Planning - APAC
AGENDA
• Dimensioning of 3G Interfaces & RNC
• Common Issues
• Example Dimensioning
MSC/VLR GMSC
CS Domain
PacketnetworkPSTN
SMSC
HLR
Service & subscriber management
3G Network Architecture
Gr Gd
CG
Gn
GGSN
3G-SGSN
InternetIP Backbone
PS Domain
DNS
RADIUSDHCP
Iu
Iu
Iu
Iu
Iur
RNCNode BUm
Iub
Node BATM
Packetnetwork
SS7Network
ChargingCenter
NMS
BG
OtherPLMN
3G MSCand/or
3G SGSN
Iur
Iu
RNC
BSBS
Iub
BS
RNC
BSBS
Iub
BS
RNC
BSBS
Iub
BS
Iu Iu
RNC
BSBS
Iub
BS
IurIur
IuIur
3G MSCand/or
3G SGSN
RAN
Uu
User Equipment(UE)
User Equipment(UE)
3G Interfaces in RAN
• ATM is used as a transport solution in Radio Access Network (3GPP Rel.99)• ATM is standardised as transport bearer in Iub, Iur and Iu • ATM can be over PDH or SDH links
Required Inputs for Dimensioning
• Radio Network Planning Output:• Number of Node Bs• Node B Configuration• Total number of Subscribers in each area• RF Planning assumptions (Blocking %, Soft Handover %,..)
• Rollout Plan
• Geographical Area Distribution or Regions
• Different Type of Traffic Usage• Real-time traffic (Voice and Circuit Switched Data)• Non real-time traffic (All kind of packet data)• Number of active PDP contexts per subscriber
• Simultaneous Data Subscribers during busy hour
• Equipment Location
RAN & Core dimensioning StepsRAN & Core dimensioning Steps
INPUTS
Traffic
Hypothesis/Assumptions
INTERFACES
Iub_Voice
Iub_PS
Iub_CS Total_Iub
RNCIu_CS
Iu_PS
Circuit Core Dimensioning
Iur
Packet Core Dimensioning
3G-MSC
DNS, CG, ....
xGSN
MSS / GW
NokiaRNC
NokiaUltraSiteWDCMA
BTS
Iub
Nokia MSC
Iu-cs
Iu-ps
Nokia
3GSGSN
RANAP on AAL5
AAL2 SIG on AAL5
USER PLANE on AAL2
RANAP on AAL5
USER PLANE on AAL5
AAL2 USER PLANE
AAL2 SIG on AAL5
O&M on AAL5
ATM Module
Interfaces – 3G PP StandardsInterfaces – 3G PP Standards
Different OH for Different Traffic ClassesIub/Iur/Iu-CS Interface Overhead
Each different service require different overheadEach different service require different overhead
Voice services Activity Service bit rate Bit rate below ATM TOTAL
kbps 12.76% OH
RT12.2 (AMR) UL active 12.2 18.9 73.00%silent 0 4.5
RT12.2 (AMR) DL active 12.2 18.0 47.88%silent 0 0.0
RT7.95 (AMR) UL active 7.95 13.5silent 0 4.1
RT7.95 (AMR) DL active 7.95 12.6silent 0 0.0
RT14.4 active 14.4 18.7RT28.8 active 28.8 36.3RT32 active 32 39.9RT33.6 active 33.6 41.7RT56.7 active 56.7 69.8RT64 active 64 78.7 23%
NRT64 64 85.7 34%NRT128 128 166.9NRT256 256 329.3NRT256 320 410.4NRT384 384 491.6 28%
ATM Overhead in Iub
For Voice Activity Factor of 65%
((18.9 x 65%) + (4.5 x 35%)) – ((12.2 x 65%) + (0 x 35%))-------------------------------------------------------------------------- ((12.2 x 65%) + (0 x 35%))
= 73.7 %
For Voice Activity Factor of 50%
((18.9 x 50%) + (4.5 x 50%)) – ((12.2 x 50%) + (0 x 50%))-------------------------------------------------------------------------- ((12.2 x 50%) + (0 x 50%))
= 92 %
Real Time Voice @ 12.2 kbps
ATM Overhead in Iub Real Time CS Data 64 kbps
(78.7 – 64) -------------- 64
= 23 %
Non Real Time PS Data 128 kbps
(166.9 – 128) ----------------- 128
= 30 %
Iub Dimensioning
• Iub is the interface between Base Station and Radio Network Controller • Iub Traffic is the total of both Circuit Switched (Voice & data) and Packet Switched data
IubBS
BS
BS
Iur
Iub
Iub
RNC
RNC
IubIub dimensioning 1/4 dimensioning 1/4 ((VoiceVoice))
Input : Traffic (mErl) / cell / region
BSConfig/ region
Method : Traffic (Erl ) / BS
# TCh / BS
Bit rate (kbps) / BS
Output :
@ BH@ BH
Activity Factor 50%SHO factor 40%
# TCh (voice) / BSAMR rate 12.2 kbit/s
Voice IubBit rate (kbps) / BS
ATM OH voice +73%
Using Erlang B Table
((IubIub dimensioning 2/4dimensioning 2/4
CS Data 64 kbpsCS Data 64 kbps ))
Input : Traffic ( mErl) / cell / region
BSConfig/ region
Method : Traffic (Erl ) / BS
# TCh / BS
Bit rate (kbps) / BS
Output : CS IubBit rate (kbps) / BS
@ BH@ BH
Activity Factor 100%SHO factor 40%
Line rate 64 kbps
# TCh (CS_data) / BS
ATM OH 64k +23%
(IubIub dimensioning 3/4dimensioning 3/4
(PS DataPS Data ))
Input : Traffic (kbits) / cell / region
BSConfig/ region
Method : Bit rate (kbps) / BS
Output : PS IubBit rate (kbps) / BS
@ BH@ BH
Activity Factor 100%SHO factor 40%ATM OH (64k +28%, 128k +25%, 384k +23%)
L1 adaptation rate 26.5%
For each service
Iub Throughput Calculation• Circuit Switched Traffic (RT)
Voice AMR Data Rate - 12.2 Kbps
12.2 Kbps
Soft Handover - 40%
17.08 Kbps
ATM Overhead - 73%
29.54 Kbps
DTX - 50%
14.77 Kbps
Total Traffic = 14.77 X Physical Channels required
• Packet Switched Traffic (NRT)
Data Bearer 128 Kbps
X Kbps
Soft Handover - 40%
X Kbps
L1 Data Rate – 26.5%
ATM Overhead - 25%
X Kbps
X Kbps
Total Traffic = No of Subscribers X Traffic
Iub Throughput Calculation
Circuit Switched Traffic (CS Voice and CS Data) =
Packet Switched Traffic =
X Physical Channels required
X Subscribers
Total Iub Traffic = Circuit Switched Traffic + Packet Switched Traffic
10% Signalling Overheadin BSS
Iur Dimensioning
• Iur interface is the traffic between two different RNCs. Eg for Soft Handover
Iub
RNC
RNC
RNC
Iur
Iur
SS DS DS
S
Base Station
Serving RNC D Drifting RNC
Soft Handover
Soft Handover
• Soft Handover is assumed to be 40 %
• Assumption
35% of the Mobiles are connected to two or more Base Stations at the same time.
30% of the Mobiles are in two way SHOs 5% of the Mobiles are in three way SHOs
Consequently on average every Call occupies
65% x 1 + 30% x 2 + 5% x 3 = 1.4 Physical Channels
If One RNC handles 100 Voice Calls, it needs 140 Physical Channels (100 x 1.4)
Iur Dimensioning
• Iur traffic mainly depends on the pattern of RNC to RNC handover traffic » Parameters involved - Velocity of the Mobile, RNC area etc.
• Each RNC will be connected to the adjacent RNC directly. One RNC could be connected to many different RNCs.
• Studies inside Nokia shows that Iur is about 7 – 8 % of Iub (user plane traffic). For dimensioning Nokia adopts 7.5 %.
MSC
IurRNC
BSBS
Iub
BS
RNC
BSBS BS
RNC
BSBS BS
Iu
Iur
MSC SGSN
IuIu
Iub Iub
Example RNC Iur Interface Connection
RNC2
RNC3
RNC1
RNC5
RNC4
RNC Region 1
RNC Region 2
Example RNC Iur Interface ConnectionReal Case Example
RNC2
RNC3
RNC1
RNC5
RNC4
RNC Region 1
RNC Region 2
SINGAPORE
Why No Iur Connection between
RNC2 – RNC4RNC3 – RNC1
Iu Interface Dimensioning (1/3)Iu Interface Dimensioning (1/3)
RNC
MGW SGSN
CS
PS
Iu interface
• Iu interface is split in to two parts
> Between RNC and MGW for Circuit Switched Traffic - Payload carried over AAL2> Between RNC and SGSN for Packet Switched Traffic - Payload carried over AAL5
Protocol Stack (Iu CS / Iu PS)Protocol Stack (Iu CS / Iu PS)
D O C U M E N T T Y P E 1 ( 1 )
T y p e U n it O r D e p a r tm e n t H e r eT y p e Y o u r N a m e H e r e T y p e D a te H e r e
A A L 2
P H Y
A T M
P H Y
A T M
A A L 2
F P
P H Y
A A L 2
P H Y
A T M
L in kL a y e r
P H Y
A A L 2
P H Y
A T M
W C D M AL 1
F P
W C D M AL 1
E .g . ,V o c o d e r
P H Y
P S T N /N - IS D N
AI uIu bU u
IW U
R N C
N o d e B
U E
E
Iu - C S U PIu - C S U P
E .g . ,V o c o d e r
L in kL a y e r
la wP C M ,U D I ,e tc .
la wP C M ,U D I ,e tc .
M S C
R L C - U
M A C
R L C - U
M A C
Circuit Switched Services – Iu CS
D O C U M E N T T Y P E 1 ( 1 )
T y p e U n itO r D e p a r tm e n tH e r eT y p e Y o u r N a m e H e r e T y p e D a te H e r e
I P
A A L 5
P H Y
U D P
L L C / S N A P
G T P - U
A T M
P H Y
A T M
A A L 2
F P
P D C P
U D P
I P
L in kL a y e r
P H Y
G T P
I P
A A L 5
P H Y
U D P
L L C / S N A P
G T P - U
A T M
U D P
I P
L in kL a y e r
P H Y
G T P
A A L 2
P H Y
A T M
W C D M AL 1
F P
W C D M AL 1
P D C P
E .g . ,IP v 4 , IP v 6
P H Y
E .g . ,IP v 4 , IP v 6
G nIuIu bU uG G S N
3 G -S G S N
R N C
N o d e B
U EG i
R L C - U
M A C
R L C - U
M A C
Packet Switched Services – Iu PS
IuIu Interface Dimensioning (2/3)Interface Dimensioning (2/3)((IuIu CS trafficCS traffic ))
Input :
Method :
Output :
For each service (voice, CS 64 k, ..)
@ BH@ BH
Total Traffic (Erl) / RNC area
ErlangB (GOS-0.5%)
# TCh/ RNC area
Line rate (12,2; 64 k; …)Activity Factor for voice: 50%ATM OH (as in Iub)
Signalling overhead + 1%
Traffic ( Erl) / BS / region# BSs& Config/ region
Bit rate (kbps) / clutter
IuIu Interface Dimensioning (3/3)Interface Dimensioning (3/3)((IuIu PS trafficPS traffic ))
Input : Traffic (kbits) / BS / region
#BSs&Config/ region
Method :
Output : Bit rate (kbps) / region
@ BH@ BH
ATM, AAL5, IP, UDP, GTP OH + 25%Signalling overhead + 1%
Bit rate (kbps) / clutter
For packet sizeOf 512 bytes
Iu-PS Calculation ExampleIu-PS Calculation ExampleFor Packet Switched traffic, OH varies with the length of the IP packet
1. Packet length = 128 Bytes
2. AAL5 PDU = (128 + 8 Encap+20 IP+ 8 UDP+ 12 GTP ) = 176 bytes
3. AAL5 PDU + trailer = (176+8) = 184
4. AAL5 Padding = roundup(184/48) x 48 = 192 (11 bytes padding)
5. Including ATM headers = 192/48 x 53 = 212 Bytes
Total OH required = 69% ((212-128)/128)
DOCUMENTTYPE
TypeUnitOrDepartmentHereTypeYourNameHere TypeDateHere
ATM AAL5 Encap IP UDP GTP ….Data
8 20 8 12 (packet length)
128 bytes
8 bytes encapsulation
20 bytes IP Header
8 bytes UDP
12 bytes GTP
8 bytes Trailer Bits
176 bytes
184 bytes
128 bytes
Iu-PS Overhead - Example (1/3)Iu-PS Overhead - Example (1/3)
48 bytes48 bytes 48 bytes 48 bytes
8 bytes Paddin
g
184 bytes
48 bytes 48 bytes 48 bytes 48 bytes 48 bytes 48 bytes 48 bytes 48 bytes
48 bytes 48 bytes 48 bytes
48 48 48 40
48 bytes
192 bytes
5 bytes ATM
Overhead
212 bytes
Iu-PS Overhead - Example (2/3)Iu-PS Overhead - Example (2/3)
ATM Cells
Iu-PS Overhead - Example (3/3)Iu-PS Overhead - Example (3/3)
128 bytes
212 bytes
Increase from Original 128 bytes to 212 bytes
Percentage of Increase - (212 – 128 / 128) * 100
65 % of Overhead for a IP Packet size of 128 Bytes
Iu-PS relative OH = (Packet size)
Iu Throughput Calculation• Circuit Switched Traffic to MSC
Voice AMR Data Rate - 12.2 Kbps
12.2 Kbps
ATM Overhead - 73%
23.54 Kbps
DTX - 50%
11.89 Kbps
Total Traffic = 11.89 X Physical Channels required
• Packet Switched Traffic to SGSN
Data Bearer 128 Kbps
X Kbps
IP, ATM Overhead - 65%
X Kbps
Signalling OH in SGSN - 1%
X Kbps
Total Traffic = No of Subscribers X Traffic
Signalling OH in MSC - 1%
23.78 Kbps
Radio Network Controller (RNC)
Based on Nokia ATM Platform
3G Network Architecture
MSC/VLR GMSC
CS Domain
PacketnetworkPSTN
SMSC
HLR
Service & subscriber management
Gr Gd
CG
Gn
GGSN
3G-SGSN
InternetIP Backbone
PS Domain
DNS
RADIUSDHCP
Iu
Iu
Iu
Iu
Iur
RNCNode BUm
Iub
Node BATM
Packetnetwork
SS7Network
ChargingCenter
NMS
BG
OtherPLMN
RNC Role
• Mobility Management
• Connection and Radio link Management
• Ciphering and Integrity Checking
• ATM and IP traffic management
• Integrated Transmission Interfaces
Radio Network Controller (RNC)Rel.1 Release: 26-130 Mbit/s Dynamic Traffic Capacity
1 2
3
4
5
Release1 Phase 1
Config.
Iub Mbit/s Node Bs Carriers STM-1 E11 26 85 256 4 642 52 128 384 4 963 78 170 512 4 1284 104 213 640 4 1605 130 256 768 4 192
Max. capacity in different configurationsIub traffic capacity Interfaces
Radio Network Controller (RNC)Rel.2 Release: 48-196 Mbit/s Dynamic Traffic Capacity
1 2
3
4
5
Release 1 Phase 1.5
Config.
Iub Mbit/s Node Bs Carriers STM-1 E11 48 128 384 4*4 6*162 85 192 576 4*4 8*163 122 256 768 4*4 10*164 159 320 960 4*4 12*165 196 384 1152 4*4 14*16
Iub traffic capacity InterfacesMax. capacity in different configurations
RNC Area Planning
RNCBS
GGSN
SGSN
MSC
ATM Module
BSBS
RNC Region-1
RNCBS
BSBS
RNC Region-2
RNC DimensioningRNC DimensioningKey limiting factors in RNC Dimensioning
• Maximum Throughput
- Rel 1 130 Mbit/s
- Rel 2 196 Mbit/s
- Rel 3 400 Mbit/s
• Maximum number or carriers
- Rel 1 768 Carriers
- Rel 2 1152 Carriers
- Rel 3 2304 Carriers
• Maximum number of Node Bs
- Rel 1 256 BTS
- Rel 2 384 BTS
- Rel 3 768 BTS
• depending on the case, one of the above limitations will apply
RNC Dimensioning PrincipleRNC Dimensioning Principle Summary Summary
Check the number of carriers per RNC
Check the number of NodeBs per RNC
RNC nominal traffic capacity
Carriers to be connectedCarriers connectivity per RNC * Fillrate
BTS to be connectedBTS connectivity capacity per RNC * Fillrate
Total user traffic in the area
Voice erlangs* 16kbit/s
CS-data erlangs* data rate
PS-data volume(busy hour)
* SHO overhead * SHO overhead * SHO overhead
Capacity Almost Independent of the Traffic Mix
RNC DimensioningRNC Dimensioning
Dimensioning Crietria
• Total throughput against the maximum throughput capacity of RNC
• Total Carriers against the maximum carrier capacity of RNC
• Total Base Stations against the maximum Node B capacity of RNC
• Fill rate of 90%
Final No of RNC - Maximum value attained by the above three Criteria
Common IssuesCommon Issues
Throughput Capacity of RNCThroughput Capacity of RNC
RNC throughput capacity expressed only in one direction and also represents only the Capacity of DMCU. O & M signalling is handled separately in OMU.
Nokia RNC could support 196 Mbps on UL and also 196 Mbps on DL.
Other Vendors mention the RNC throughput as 392 Mbps (UL + DL)
MGW
SGSN
196 Mbps
Iub
Iu
Traffic split between Voice & DataTraffic split between Voice & DataThroughput capacity of Nokia RNC is 196 Mbps.
What is the Traffic split between Voice and Data ?
Voice
Data
Combination of any percentage of Voice and Data
RNC upgrade from 196 – 400 MbpsRNC upgrade from 196 – 400 Mbps
196 Mbps 400 Mbps
Upgrade Path
No Upgrade path and cost defined yet.
400 Mbps RNC is provided as new boxes for the additional traffic for Later phases.
Voice Channels - 16 kbps in RNCVoice Channels - 16 kbps in RNC
MGW
Voice Channel at 12.2 kbps or lesser
Voice Channel at 16 kbps
12.2 or lesser
Even lower bitrates requires as much processing capacity (user and control plane)Within RNC as a 16kbps channels.
In the Transmission it is taken as original bit rates.
Iur carried over Iu InterfaceIur carried over Iu Interface
RNCBS
GGSN
SGSN
MSC
MGW
BSBS
RNC Region-1
RNCBS
BSBS
RNC Region-2
RNC linked directly for Iur connection
Iur Traffic is carried through Iu over to core and then to RNC
Interface Ports on RNCInterface Ports on RNCTotal Traffic (Iub + Iu + Iur) must be considered to calculate the interface Requirement in RNC.
50 Node B- DU
50 X 0.33 E1
50 Node B- DU
50 X 0.66 E1
80 Node B- U
80 Node B- U
80 X 0.44 E1
80 X 0.88 E1
Daisy Chain Configuration
Interface Ports on RNCInterface Ports on RNC
50 Node B- DU
50 X 0.33 E1
50 Node B- DU
50 X 0.33 E1
80 Node B- U
80 Node B- U
80 X 0.44 E1
80 X 0.44 E1
Star Configuration
No of E1 Interface required at RNC = 260
Available E1 Interface at RNC = 192What is the Solution
AXCAXC
AXC
AXC
1 X STM1
1 X STM11 X STM1
Introduce Multiplexing Equipment to Groom the Traffic
RNC Dimensioning CriteriaRNC Dimensioning CriteriaNokia’s Dimensioning criteria for RNC
• Throughput• Carriers• Node B
Some Operators specify RNC to be dimensioned based on -
• Subscribers
• Number of Soft Handovers
• Cell broadcast message
• UE Positioning Request
• Number of Hard Handovers
• Iub, Iu, Iur and O&M Traffic
RNCNode B
ATM Transmission Medium
ATM Overhead in RNCATM Overhead in RNC
ATM OH added at NIU
ATM OH stripped off at the Interface unit
of RNC
ATM Overhead is considered only on the Transmission
The ATM OH is stripped off at the NIU of RNC
Hence traffic to RNC will not include ATM overhead.
Dimensioning Exercise Dimensioning Exercise
Objective
• Dimension the Interfaces Iub, Iu & Iur
• Determine the number of RNCs required
• Understand the output format from an IP Planner
Case StudyCase Study
3G RAN Network Dimensioning for an Operator in Singapore
SINGAPORE
Case StudyCase Study
Singapore classified in to four different regions Dense Urban Urban Suburban
Rural
DU UU SUSU
Indoor considered to be with in Dense Urban
.
.
.
.
.
.
.
.
..
. .
.
.
Inputs from OperatorInputs from Operator
Subscriber Information
Subscribers Phase 1 Phase 2 Phase 3
Dense Urban 17477 45567 82478Urban 15421 49055 109027Suburban 1495 7674 20811Rural 5607 32703 72685Total 40000 135000 285000
Services to be offered
Circuit Switched • Voice 12.2 kbps• CS Data 14.4 kbps• CS Data 64 kbps
Packet Switched• PS Data 16 kbps• PS Data 64 kbps• PS Data 128 kbps• PS Data 384 kbps
PS 16 kbps UL, kbps/sub
Phase 1 Phase 2 Phase 3PS 16
kbps DL, kbps/sub
Phase 1 Phase 2 Phase 3
kbps/sub kbps/subDense Urban 0.1760 0.2372 0.2778 Dense Urban 0.0176 0.0237 0.0278Urban 0.3911 0.3954 0.3704 Urban 0.0391 0.0395 0.0370Suburban 0.1956 0.2175 0.2223 Suburban 0.0196 0.0217 0.0222Rural 0.2347 0.2768 0.2963 Rural 0.0235 0.0277 0.0296
PS 64kbps UL, kbps/sub
Phase 1 Phase 2 Phase 3PS 64
kbps DL, kbps/sub
Phase 1 Phase 2 Phase 3
kbps/sub kbps/subDense Urban 0.0320 0.0608 0.1134 Dense Urban 0.1681 0.2231 0.3821Urban 0.0712 0.1014 0.1513 Urban 0.3735 0.3718 0.5095Suburban 0.0356 0.0557 0.0817 Suburban 0.1867 0.2045 0.3057Rural 0.0427 0.0709 0.1210 Rural 0.2241 0.2603 0.4076
PS 128kbps UL, kbps/sub
Phase 1 Phase 2 Phase 3PS 128
kbps DL, kbps/sub
Phase 1 Phase 2 Phase 3
kbps/sub kbps/subDense Urban 0.1596 0.5543 1.6394 Dense Urban 0.6185 0.0 0.0Urban 0.3547 0.9239 2.1859 Urban 1.3745 2.0361 0.0Suburban 0.1773 0.5081 1.3115 Suburban 0.6873 1.1199 0.0Rural 0.2128 0.6467 1.7487 Rural 0.8247 1.4253 3.1681
PS 384 kbps UL, kbps/sub
Phase 1 Phase 2 Phase 3PS 384
kbps DL, kbps/sub
Phase 1 Phase 2 Phase 3
kbps/sub kbps/subDense Urban 0.0 0.0 0.0 Dense Urban 0.0 1.2217 2.9701Urban 0.0 0.0 0.0 Urban 0.0 0.0 3.9602Suburban 0.0 0.0 0.0 Suburban 0.0 0.0 2.3761Rural 0.0 0.0 0.0 Rural 0.0 0.0 0.0
CS Voice 12.2 Phase 1 Phase 2 Phase 3mE/sub
27.0 32.0 56.0
CS Data 14.4 Phase 1 Phase 2 Phase 3mE/sub
4.0 8.0 10.0
CS Data 64 Phase 1 Phase 2 Phase 3mE/sub
0.0 0.0 8.0
Traffic for different ServicesTraffic for different Services
Radio Planning OutputRadio Planning Output
Region Base Station Type Phase 1 Phase 2 Phase 3Dense Urban UltraSite Optima Compact ROC 145 215 0
UltraSite Optima Compact CEC 0 0 215
Urban UltraSite Optima Compact CEC 302 604 900
Suburban UltraSite Optima Compact CEC 131 221 429
Rural MetroSite Node B 100 190 290
Other Radio Planning Parameters
• Radio Blocking 2 %• Voice Activity Factor (DTX) 67%• Soft Handover Factor 40%• Voice AMR Data Rate 12.2 kbps
ADD ATM OH for Voice 73%
Taking into account only
67% of traffic due to DTX.
Multiplied by AMR data rate of
12.2 kbps
Adding SHO factor of 40%
Using Erlang B Table with Blocking
probability of 2%
Voice Traffic of 27mErl multiplied
by the subs.
Dense Urban Urban Suburban Rural
Subs and BTS Sites BTS Configuration 111 111 111 111Number of Sites 145 302 131 100Total Number of Sites 145 302 131 100
CS VoiceNo of Subs 17,477 15,421 1,495 5,607Total Subs / BS 120.53 51.06 11.41 56.07Total Erl / BS 3.25 1.38 0.31 1.51Phy CH Req. 8 5 3 5SHO 11.20 7.00 4.20 7.00Bit Rate (Kbps) 136.64 85.40 51.24 85.40DTX 91.55 57.22 34.33 57.22Bit Rate (Kbps)+ATM O_H 158.38 98.99 59.39 98.99
Phase 1
Iub Calculation Iub Calculation CS Voice TrafficCS Voice Traffic
Voice + CS Data + 1% Sig OH in
MSC
ADD ATM OH for CS Data 25%
Multiplied by data rate of 144 kbps
Adding SHO factor of 40%
Using Erlang B Table with Blocking
probability of 2%
CS Data of 4mErl multiplied by the
subs.
Iub CalculationIub CalculationCS Data TrafficCS Data Traffic
Dense Urban Urban Suburban RuralCS Data @ 14.4 kbpsSimultaneous Subscribers 7119 13959 677 3046Subscribers per BS 49.10 46.22 5.17 30.46Total Erl / BS 0.20 0.18 0.02 0.12Phy CH Req 2 2 2 2SHO 2.80 2.80 2.80 2.80Bit Rate (Kbps) 40.32 40.32 40.32 40.32Bit Rate (Kbps)+ATM O_H 49.59 49.59 49.59 49.59
Phase 1
Total CS Voice 158.38 98.99 59.39 98.99Total CS Data 49.59 49.59 49.59 49.59Total CS Traffic + Sig.OH 210.05 150.07 110.08 150.07
26.5% OH for retransmission &
bufferingADD ATM OH for PS Data 16 kbps
58%
Adding SHO factor of 40%
PS 16 kbps data traffic. Max of UL
or DL
Total CS Traffic + Sig.OH 210.05 150.07 110.08 150.07
Iub Calculation Iub Calculation PS Data Traffic (16 kbps)PS Data Traffic (16 kbps)
PS Data 16 KbpsSimultaneous Subscribers 17477 15421 1495 5607Subscribers per BTS site 120.53 51.06 11.41 56.07Data Rate Kbps 21.21 19.97 2.23 13.16L1 Data Rate Kbps 28.28 26.63 2.98 17.55SHO 39.60 37.28 4.17 24.56Bit Rate (Kbps) + O_H 62.56 58.90 6.58 38.81
ADD ATM OH for PS Data 64 kbps
33%
PS 64 kbps data traffic. Max of UL
or DL
Total CS Traffic + Sig.OH 210.05 150.07 110.08 150.07
Iub Calculation Iub Calculation PS Data Traffic (64 kbps)PS Data Traffic (64 kbps)
Total PS Data 16 kbps 62.56 58.90 6.58 38.81
33% OH for retransmission &
bufferingAdding SHO factor of 40%
PS Data 64 kbpsSimultaneous Subscribers 17477 15421 1495 5607Subscribers per BTS site 120.53 51.06 11.41 56.07Data Rate Kbps 20.26 19.07 2.13 12.57L1 Data Rate Kbps 27.01 25.43 2.84 16.75SHO 37.82 35.60 3.98 23.46Bit Rate (Kbps) + O_H 50.30 47.35 5.29 31.20
ADD ATM OH for PS Data 64 kbps
30%
PS 128 kbps data traffic. Max
of UL or DL 33% OH for
retransmission & buffering
Adding SHO factor of 40%
Iub Calculation Iub Calculation PS Data Traffic (128 kbps)PS Data Traffic (128 kbps)
Total CS Traffic + Sig.OH 210.05 150.07 110.08 150.07Total PS Data 16 kbps 62.56 58.90 6.58 38.81Total PS Data 64 kbps 50.30 47.35 5.29 31.20
PS Data 128 kbpsSimultaneous Subscribers 17477 15421 1495 5607Subscribers per BTS site 120.53 51.06 11.41 56.07Data Rate Kbps 74.55 70.19 7.84 46.24L1 Data Rate Kbps 99.40 93.58 10.46 61.66SHO 139.15 131.01 14.64 86.32Bit Rate (Kbps) + O_H 180.90 170.32 19.03 112.22
Total Iub + 10% Signalling OH
Iub Calculation Iub Calculation
Total CS + PS Total CS Traffic + Sig.OH 210.05 150.07 110.08 150.07Total PS Data 16 kbps 62.56 58.90 6.58 38.81Total PS Data 64 kbps 50.30 47.35 5.29 31.20Total PS Data 128 kbps 180.90 170.32 19.03 112.22Total Traffic Per BS kbps 503.82 426.63 140.98 332.29
BS Traffic + Sig OH in Mbps 0.55 0.47 0.16 0.37
RNC
DU U SU Rural
0.55 Mbps
0.47 Mbps 0.16 Mbps
0.37 Mbps
ADD ATM OH for Voice 73%
Multiplied by AMR data rate of
12.2 kbps
Using Erlang B Table with
Blocking prob of 0.5%
Total Voice Traffic
irrespective of No of BS as in Iub
Iu Calculation Iu Calculation Iu CS Voice Iu CS Voice
CS VoiceNo of Subscribers 17477 15421 1495 5607Total V_Erl (Erl) 471.88 416.37 40.37 151.39CSV_CH 508 451 56 176Total Voice in kbps 6197.6 5502.2 683.2 2147.2Total traffic + O_H Mbps 10.72 9.52 1.18 3.71
Note : No Soft Handover in Iu interface.
Voice with DTX + CS Data & 1&
Sig in MSC
ADD ATM OH for Voice 23%
Multiplied by AMR data rate of
12.2 kbps
Using Erlang B Table with
Blocking prob of 0.5%
Total CS Data Traffic
irrespective of No of BS as in Iub
Iu Calculation Iu Calculation Iu CS Data Iu CS Data
CS Data @ 14.4 KbpsSubscribers 7119 13959 677 3046Total V_Erl (Erl) 28.48 55.84 2.71 12.18CSD_CH 42.00 73.00 8.00 22.00Total CS Data in kbps 604.80 1051.20 115.20 316.80Total CS Data + O_H Mbps 0.74 1.29 0.14 0.39
Total Iu CS Voice 10.72 9.52 1.18 3.71
Total Iu CS Traffic
Total Iu CS Data 0.74 1.29 0.14 0.39RNC ---> MSC Mbps 8.01 7.75 0.94 2.91
Total Iu CS Traffic for Singapore for Phase 1 = 19.61 Mbps
Add 1% Signalling OH in
SGSN
Add IP/ATM Traffic OH based on Packet size
Total PS Data of all services. Max
of UL/DL
Iu Calculation Iu Calculation Iu PS Data Iu PS Data
Iu PS TrafficRNC to SGSN Traffic 16.82 14.84 1.44 5.40PD Traffic + O_H Mbps 18.67 16.48 1.60 5.99Traffic to SGSN + Sig OH 18.86 16.64 1.61 6.05
Total Iu PS Traffic for Singapore for Phase 1 = 43.16 Mbps
RNC
Iu CS 19.61 Mbps
Iu PS 43.61 Mbps
MGW
SGSN
RNC DimensioningRNC Dimensioning
Projected Time Schedule
Phases Roll Out RNC
Phase 1 2H 2002Phase 2 2H 2003Phase 3 2H 2004
196 Mbps196 Mbps400 Mbps
What Release of RNC to be proposed ?
RNC DimensioningRNC Dimensioning
Total Traffic without ATM
Overhead
Note: ROC BS Type for DU
which is only 1 Carrier
Addl Traffic after deducting the
capacity of RNC in Phase2
Area BS Type #Sites (BS)Total Iub per site
Total BS trafficto RNC
Total RNCTraffic (Mbps)
Total Carriers
(Mbps) Mbps
Phase 1 216.5 1,744DU 111 ROC 145 0.6 63.23 U 111 302 0.5 107.58 SU 111 131 0.2 17.07 Rural 111 100 0.4 28.67
678Phase 2 897.4 3,705DU 111 CEC 215 1.7 270.16 U 111 604 0.9 387.93 SU 111 221 0.3 55.75 Rural 111 195 1.3 183.57
1235Phase 3 3893.6 5,562DU 111 215 6.4 1,005.36 U 111 900 2.8 1,863.35 SU 111 429 0.9 295.42 Addl TrafficRural 111 310 3.2 729.50 2982.4
1854
Fill Rate of 80% Used
# RNC LimitedCarriers
Required # of RNC
FullConfig on Last RNC
1.89 1.38 2.21 2.21 2 1 0 3
#RNC Limited by NodeB
# RNC LimitedProcessing Capacity
RNC 1
RNC 2 Total
4.02 5.72 4.02 5.72 5 4 0 6
5 4 10 16
9.32 9.32
1
2
3
4
5 1
Phase 1 Configuration
1
2
3
4
51
2
3
4
5
X 5
1
2
3
4Phase 2 Configuration
1
2
3
4
5
X 5
1
2
3
4Phase 3 Config
X 10 - 400 Mbps
Top Related