3G Transmission Dimension Ing Process

3G Transmission Dimensioning
Process
June 2005
Charles Kao
NOKIA
TRS_Presentation_Smart / 01-07-2005/OSP-Manila
Company Confidential
TRS Planning Requirement & Dimensioning
NOKIA
Network Dimensioning Process Flowchart

Input from
customer
RF
Dimensioning
Transmission
Dimensioning
IP
Dimensioning
Network
Dimensioning
done
NOKIA
Trs Network Dimensioning Process Flowchart

Input from RF
Iub
dimensioning
Trs dimensioning
assumptions
NOKIA
RNC
dimensioning
Iu-CS, Iu-PS, Iur

dimensioning
Quantity of
E1, STM-1 etc
required
Network Dimensioning Process

The Customer Requirements and/or Nokia assumptions
Transmission Dimensioning
3G subscriber growth forecast and distribution per region
3G Packet Data, Circuit Switched Data & Voice traffic/sub
CS Core Traffic Model
Coverage Requirements
# of Core sites
QoS requirements
Link Capacity
Number &
configuration of
Node B
RNC location
Iub traffic
IuCS/PS traffic
Node B Dimensioning
RAN Dimensioning
# of sites
configuration of sites
e.g. 1+1+1/SRC/MHA
# and
configuration
of RNC
RAN Inerface
Capacity
requirements
NOKIA
CS/PS Core Network

Dimensioning
# and configuration of core
elements
user plane/control plane
requirements
# of Hardware channels
5
# & type of Iub & Iu

links
# of interface cards
# of AXC
RAN dimensioning output

Interfaces
Iub Link Capacity
(Node B < = > RNC)
Iur Link Capacity
(RNC < = > RNC)
Iu Link Capacity
Circuit Switched (RNC < = > MSC)
Packet Switched (RNC < = > SGSN)
Equipment
Number of RNCs
NOKIA
RAN & Core dimensioning Steps

INTERFACES
Iub_Voice
Iub_CS_data
Total_Iub
Iub_PS
Iu_CS
RNC
Iur
INPUTS
Iu_PS
Traffic
Hypothesis/Assumptions
3G-MSC
Circuit Core Dimensioning
MGW
Packet Core Dimensioning
xGSN
DNS, CG, ....
NOKIA
RAN Protocol Stacks

Iub
Uu
UE
Iu
E.g.,
IPv4, IPv6
RNC
PDCP
RLC-U
MAC
WCDMA
L1
Node B
WCDMA
L1
Gn
E.g.,
IPv4, IPv6
3G-
PDCP
GTP-U
GTP-U
GTP
GTP
RLC-U
UDP
UDP
UDP
UDP
IP
IP
Link
Layer
Link
Layer
PHY
PHY
MAC
IP
IP
FP
FP
LLC/SNAP
LLC/SNAP
AAL2
AAL2
AAL5
AAL5
ATM
ATM
ATM
ATM
PHY
PHY
PHY
PHY
Gi
GGSN
PHY
Each layer in protocol stack will add additional bits to the original payload and depending of the interface,
different overheads are used. Below there are presented protocol stacks for both CS and PS traffic.
In Iu interface there can be distinguished two different types of traffic,
IuCS (Iu-Circuit Switched, data and speech) for connections towards MGW/MSC and
Iu-PS (Iu-Packet Switched) for 3G-SGSN.
Iub
Uu
Iu
UE
IWU
E.g.,
Vocoder
RLC-U
MAC
WCDMA
L1
8
NOKIA
RNC
Node B
WCDMA
L1
MSC
E.g.,
Vocoder
RLC-U
/law
PCM,
UDI,
Iu-CS UP
etc.
/law
PCM,
UDI,
etc.
Iu-CS UP
FP
MAC
FP
AAL2
AAL2
AAL2
AAL2
ATM
ATM
ATM
ATM
Link
Layer
Link
Layer
PHY
PHY
PHY
PHY
PHY
PHY
PSTN/
N-ISDN
PHY
Circuit Switched Traffic

Circuit Switched Traffic
Circuit switched traffic can be divided in two types, Voice and Data.
Most cases 12.2 kbps (AMR mode 0) for voice is used. This mode corresponds
Enhanced FR in GSM network.
RAN 1 and 1.5 supports the following Voice and Circuit switched service rates which
corresponds to the following bitrates:
AMR Mode
Rate (kbps)
0
12.20
1
10.20
2
7.95
3
7.40
4
6.70
5
5.90
6
5.15
RAN 1 and RAN 1.5 supports the following service rates for circuit switched data.
Rate kbps
9.6
14.4
19.2
28.8
38.4
57.6
64
NOKIA
Comment
Base Rate 1
Base Rate 2
2 x 9.6 kbps
2 x 14.4 kbps
4 x 9.6 kbps
4 x 14.4 kbps
UDI (Unrestricted Digital Information)
7
4.75
Packet Switched Traffic

Packet Switched Traffic
RAN 1 and 1.5 supports the following service rates or combination of them for packet
switched data.
Rate
Rate kbps
10
NOKIA
0
384
1
320
2
256
3
128
4
64
5
32
6
16
7
8
8
0
RAN calculation related protocols & overheads, 1
Air Interface Protocols Assumptions (L1, MAC, RLC,PDCP), Re-Transmission & Buffering
L1 OH includes pilot symbols, TFCI field, closed loop PC bits ...etc,
this is not used by RNC L1, they are generated inside the BS and so this
overhead is not included.
The L1 functions inside the RNC are macro-diversity combining(MDC) & Outer-loop
power control
L2 OH includes MAC & RLC. For CS traffic the RLC is transparent. For PS traffic the
RLC takes care of re-transmission in case of errors, and consequently there is a L2
OH. The assumption is that
L2 re-transmission is 10% (Quality of the radio link, BLER)
15% headroom to avoid infinite buffering.
For PS data this will result 1/0.79 extra overhead :
(1 + 10% L2 reTRX)( 1 + 15% headroom) = 1/0.79 = 26.5% OH.
11
NOKIA
Frame Protocols
Frame protocols are applied to transfer user data and the necessary control information
between the Serving RNC (SRNC) and the BS. They are characterized by a frame structure
consisting of the payload, that contains the data (typically one or more MAC PDUs) and a
header/trailer with control information (used for synchronization, power control, CRC bits, etc).
Three different Frame Protocols are specified in UTRAN:
Iub CCH FP (3GPP TS 25.435)
RAN: DCH FP (3GPP TS 25.427)
Iur CCH FP (3GPP TS 25.425)
They are independent but have a similar structure and coding of the frames.
For Voice (Active and Silent Mode), FP frames (including OH) are sent every TTI
(TransmissionTime Interval) regardless of the activity (Active or Silent) of the user. During the
Silent mode, SID (Silence Descriptor) otherwise known as Comfort Noise frames, are sent every
8th frame of the FP frames (including OH) thus bits are generated even during the silent mode.
12
NOKIA
Iu-User Plane Protocols
Frame Protocols are terminated in the RNC and replaced by Iu-UP (User Plane) protocols in the Iu-CS and
Iu-PS interface. User Plane protocols either operates on Transparent or Support modes. Transparent modes
are used for transmission of GTP-PDUs and no headers at the head of the Iu-UP PDU are defined. Supported
modes are applicable during e.g. the AMR based speech connection thus headers are generated on this
mode of operation. The percentage of header generated on support mode is comparable to the FP headers
thus, traffic calculation in Voice & CS data for Iu-CS interface is similar to Iub calculation.
ATM Protocols
ATM protocols overhead consists of two-layers :

ATM Adaptation Layer 2 (AAL2) - is used to adapt the air-interface protocols into ATM cells.
ATM Layer consists of 5 bytes of overheads that adapts AAL PDUs to ATM cells
PDH/SDH layer ATM cells are then mapped into physical transmission channels implemented using
PDH/SDH technologies.
13
NOKIA
Soft-Handover Factor
Soft Hadover Factor is assumed to be 40%.
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
This value is coming from the IS-95 experience and from our simulations. There is trade off
between SHO gain and capacity and this is somehow of our target in order to get some gain
without waste of our capacity.
In other words, if one RNC manages 100 Voice calls, then it must have 140 (100*1.4) physical
channels (as compared to a GSM BSC managing 100 calls, having 100 time slots).
For transmission networks this factor is only relevant in the Iub interface because the RNC
terminates all connections and selects the connections with the best quality.
For The Customer case, SHO of 30% was adopted
14
NOKIA
Voice Activity Factor
The system uses DTX (Discontinuous Transmission), so when there is no speech, the system
stops transmitting data (on L1). Unless the operator gives the Voice Activity factor, we assume
activity factor as from 50% to 69%. (67% used in The Customer case)
15
NOKIA
Signalling Overheads
Signaling has to be considered for each of the interfaces. Different assumptions are to be defined for Iub, Iur and Iu
interfaces.
In Iub interface this is normally includes
L3 signalling DCH (Dedicated channels) overhead
Mobile signalling overhead in common channel states
CC, MM.
NBAP-C
NBAP-D
AAL2 signalling
Since there is no practical network results available yet, 10% of user-plane traffic can be assumed (based on GSM
experience and modelling) as signalling.
For the Iu interface, signalling overhead is considered as 1% of user-plane traffic.
This is a temporary value as this is also based on GSM experience (the A-interface). This includes AAL2 Signalling
and RANAP signaling for Iu-CS and GTP signalling and RANAP signaling for Iu-PS interface.
For Iur interface, 2- 4 % of the user traffic is assumed to be signaling.. This is includes AAL2 signaling and RNSAP.
This is again based on studies made inside Nokia.
16
NOKIA
Different OH for Different Traffic Classes

Each different service require different overhead
Voice services
Activity Service bit rate

kbps
RT12.2 (AMR) UL active

silent
RT12.2 (AMR) DL active
silent
RT Services
Overhead vs
Traffic Classes?
RT64
17
NOKIA
Activity service bit rate

kbps
active
NRT Services
NRT64
NRT128
NRT256
NRT256
NRT384
12.2
0
12.2
0
UL/DL
DL
DL
DL
DL
L1 bit rate
kbps
12.2
0
12.2
0
L1 bit rate
kbps
64
64
service bit rate

kbps
L1 bit rate
kbps
64
128
256
320
384
67.2
134.4
268.8
336
403.2
Bit rate incl. FP Bit rate below ATM

kbps
12.76%
15.6
2.8
14.8
0
18.9
4.5
18.0
0.0

kbps
12.76%
65
78.7

kbps
12.76%
71.2
138.4
272.8
340
407.2
85.7
166.9
329.3
410.4
491.6
AAL2 OH
Voice services
Activity Service bit rate L1 bit rate

kbps
kbps
TTI
ms
Data/frame FP OH Total /frame Bit rate incl. FP AAL2 PDU AAL2 OH Bits to ATM Bit rate below AAL2
kbps
bit
octet
bit
#
octet
bits
kbps
12.2
15.6
RT12.2 (AMR) UL active
12.2
20
244
7
312
1
3
336
16.8
0
2.8
silent
0
20
0
7
56
1
3
80
4.0
12.2
14.8
RT12.2 (AMR) DL active
12.2
20
244
5
296
1
3
320
16.0
0
0
silent
0
20
0
0
0
0
3
0
0.0
RT Services
Activity service bit rate L1 bit rate Frame period Data/frame FP OH Total /frame Bit rate incl. FP AAL2 PDU AAL2 OH Bits to ATM Bit rate below AAL2
kbps
kbps
kbps
ms
bit
octet
bit
#
octet
bits
kbps
RT14.4
RT28.8
RT32
RT33.6
RT56.7
RT64
active
active
active
active
active
active
18
NOKIA
14.4
28.8
32
33.6
56.7
64
40
40
40
40
40
40
576
1152
1280
1344
2268
2560
5
5
5
5
5
5
616
1192
1320
1384
2308
2600
15.4
29.8
33
34.6
57.7
65
2
4
4
4
7
8
3
3
3
3
3
3
664
1288
1416
1480
2476
2792
16.6
32.2
35.4
37.0
61.9
69.8
service bit rate L1 bit rate Frame period Data/frame FP OH Total /frame Bit rate incl. FP AAL2 PDU AAL2 OH Bits to ATM Bit rate below AAL2
kbps
kbps
kbps
ms
bit
octet
bit
#
octet
bits
kbps
NRT Services
NRT8
NRT16
NRT32
NRT64
NRT128
NRT256
NRT256
NRT384
14.4
28.8
32
33.6
56.7
64
UL/DL
UL/DL
UL/DL
UL/DL
DL
DL
DL
DL
8
16
32
64
128
256
320
384
9.6
17.6
33.6
67.2
134.4
268.8
336
403.2
10
10
10
10
10
10
10
10
96
176
336
672
1344
2688
3360
4032
5
5
5
5
5
5
5
5
136
216
376
712
1384
2728
3400
4072
13.6
21.6
37.6
71.2
138.4
272.8
340
407.2
1
1
2
2
4
8
10
12
3
3
3
3
3
3
3
3
160
240
424
760
1480
2920
3640
4360
16.0
24.0
42.4
76.0
148.0
292.0
364.0
436.0
RAN Dimensioning Inputs

In general, the following inputs are required for dimensioning:
Total number of Subscribers (Subs)
Number of Subscribers for Voice
Number of Subscribers for CSD/ Service class
Number of Subscribers for PSD/ Service class
Number of Base Stations
Average Voice traffic / busy hour
Average CSD traffic / busy hour
Average PSD traffic / busy hour
Uu interface blocking
Voice Activity Factor for Voice (VAF=50-69%)
19
NOKIA
Iub Interface Dimensioning

BS
RNC
BS
Iub
RNC
Iur
BS
Iub
Iub
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
20
NOKIA
Iub Protocol Overhead Assumptions

The overhead for Iub transmission includes :
Frame Protocol layer header (variable length frame, one frame every transport block set interval)
AAL2 segmentation header
ATM cell header
Soft Handover factor is assumed to be 40% (30% in The Customer case).
For PS traffic, we will assume Air Interface Overheads (RLC, Re-transmission & Buffering) as
26.5% as calculated above.
21
NOKIA
Iub Dimensioning, CS Traffic

Input information
10 mErl/sub (Voice)
5 mErl/sub (CS data) Service rate 64
kbit/s
500 subs/BTS
SHO = 40%
VAF = 65%
Iub sig. = 10%
7,5 Erl /BTS

Erlang B table (Traffic with 2% blocking)
14 ch's/BTS
SHO = 40%
20 ch's/BTS
Voice channels/BTS
10 mErl
15 mErl
22
NOKIA
CS data channels/BTS
5 mErl
15 mErl
x 20 ch's = 14 ch's
x 20 ch's = 7 ch's
Iub Dimensioning, CS Voice
Voice channel in Uu = 12,2 kbit/s
Voice in the ATM
Voice channel, Active = 18,9 kbit/s
Voice channel, Silent = 4,5 kbit/s
VAF = 65%
VAF of 67% is used in The Customer case

Average voice rate in ATM:
18,9 kbit/s x 65 % + (4,5 kbit/s x 35%) = 13,86 kbit/s
23
NOKIA
Iub Dimensioning, CS Traffic

CS Data
Voice
14 ch's/BTS x 13,86 kbit/s/ch = 194,04 kbit/s/BTS
7 ch's/BTS x 64 kbit/s/ch = 448 kbit/s/BTS
ATM OH = 23%
551 kbit/s
Total CS traffic in Iub/BTS = (194,04 kbit/s + 551 kbit/s) + 10 % Iub sig. = 819,5 kbit/s
24
NOKIA
Iub Dimensioning (3/3), PS Data

Traffic ( kbits) / cell / region
Input :
For each service
Method :
Bit rate (kbps) / BS

Activity Factor
SHO factor
ATM OH
L1 BufDelay OH
Output :
25
NOKIA
@ BH
BS Config / region
PS Iub Bit rate (kbps) / BS
100%
30%
(64k +33%, 128k +30%, 384k +28%)
26.5%
Iur Dimensioning
RNC
RNC
Iur
Iub
RNC
Iur
Iur interface is the traffic between two different RNCs. Eg for Soft Handover
26
NOKIA
Introduction to Iur Interface
MSC
SGSN
Iu
MSC
Iu
Iur
RNC
Iur
RNC
Iub
Iub
BS BS BS
Iu
BS BS BS
RNC
Iub
BS BS BS
Iur interface is needed for :

Transmitting and receiving the MS signal via two different BS which belong to two
different RNCs.
Signalling between the individual RNCs, (e.g. for HO establishments).
27
NOKIA
RNC Dimensioning
Based on Nokia ATM Platform

28
NOKIA
Nokia RNC Dimensioning
What need to be checked ?
29
NOKIA
Iub throughtput
Number of carriers
Number of BTS's
Nokia Radio Network Controller

Rel. 1.5 & 2: 48-196 Mbit/s Dynamic Traffic Capacity
RNC release 1.5 & 2

Config.
3
4
Iub traffic capacity

Iub Mbit/s
BTSs
Carriers
STM-1
E1
48
128
384
4*4
6*16
85
192
576
4*4
8*16
122
256
768
4*4
10*16
159
320
960
4*4
12*16
196
384
1152
4*4
14*16
30
NOKIA
Interfaces
Nokia RNC Dimensioning

Limitations:
Iub Data Throughput
Number of Carriers
Number of Node Bs
Release 1.5
196 Mbps
1152 carriers
384 Node Bs
Inputs:
RNC fill rate 90%
Circuit Switched Voice
Circuit Switched Data
Packet Switched Data
31
NOKIA
Voice Channels, 16Kbps in RNC
MGW
12.2 or lesser
Voice Channel at 12.2 kbps or lesser
Voice Channel at 16 kbps
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.
32
NOKIA
ATM Overhead in RNC
ATM OH added at
NIU
ATM OH stripped off

at the Interface unit
of RNC
RNC
Node B
ATM Transmission Medium
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.
33
NOKIA
Nokia RNC Dimensioning Principle

Capacity Almost Independent of the Traffic Mix
Check the number of carriers per RNC
Check the number of Node B per RNC
RNC nominal traffic capacity
Carriers to be connected
Carriers connectivity per RNC * Fillrate
Node B to be connected
Node B connectivity capacity per RNC * Fillrate
Voice erlangs
* 16kbit/s
CS-data erlangs
* data rate 1)
PS-data volume
(busy hour)
* SHO overhead
* SHO overhead
* SHO overhead
Total user traffic in the area
34
NOKIA
Limiting Factors in Nokia RNC 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% (Customer input)
Final No of RNC - Maximum value attained by the above three Criteria
35
NOKIA
Iu Interface Dimensioning
MGW
SGSN
PS
CS
Iu interface
RNC
36
NOKIA
Iu Dimensioning Flow
Data CS Traffic @ X kbit/s
Voice CS Traffic
@ 12.2 kbit.s
Data PS Traffic @ X kbit/s
Voice Activity
Factor
(VAF=67%)
ATM overhead (ATMOH)

@ X kbit/s
ATM overhead
(ATMOH) @
12.2 kbit/s
Iu signalling (SigOH%) 1%
Iu-CS Capacity needed
37
NOKIA
ATM overhead (ATMOH)

@ X kbit/s
Iu signalling (SigOH%) 1%
Iu-PS Capacity needed

Iu-CS Protocol Overheads

The transmission overheads between RNC and MSC are similar to the
overheads of Voice and Circuit Switched traffic in Iub. Therefore the
calculation of Iu traffic from RNC to MGW/MSC is similar to Iub traffic
calculation. The only difference is that all subscribers under one RNC are
pooled together and the calculations are based on that.
SHO is not included because all connections are terminated at the RNC.
38
NOKIA
Iu-CS Interface Dimensioning

For each service (voice, CS 64kbps)
Input :
Method :
Traffic ( Erl) / BS / region

# BSs & Config / region
@ BH
Total Traffic (Erl) / RNC area
Erlang B (GOS- 0.1%)

# TCh / RNC area
Line rate (12.2kbps, 64kbps )
Activity Factor for voice: 67%
ATM OH (as in Iub)
Signalling overhead + 1%
Output :
39
NOKIA
Bit rate (kbps) / clutter
Iu-PS Protocol Overheads

Between RNC and 3G-SGSN transmission overheads are unique and their relative size
depends strongly on the packet size that needs to be transmitted from RNC to 3GSGSN.
The traffic comes from the mobile station to the RNC, then it is tunnelled through the
3G-SGSN to destination (Internet, Intranet). This tunnelling requires GTP plus UDP
and IP (encapsulated) running on AAL5 ATM transmission media.
PHY
ATM
AAL5
Encap
8
20
User Data
AAL5 PDU
AAL5 PDU + trailer
AAL5 PDU + trailer + padding
Including ATM headers
Total OH required
40
NOKIA
IPv4
UDP
8
GTP
Data
12
(Packet Length)
= 512 Bytes (TCP session)

= (512 + 8 Encap+20 IP+ 8 UDP+ 12 GTP)
= 560 bytes
=(560+8) = 568
= Roundup (568/48) x 48
12 cells needed, 8 bytes of padding
= Roundup (568/48) x 53 = 636
= (636-512)/512
= 24% OH
AAL5
PDU
Max. 65535 Octets
Trailer 8 octets
AAL 5 layer
48 Octets
ATM layer
ATM header 5 octets
41
NOKIA
Padding 0-47 octets
Iu-PS Interface Dimensioning
Input :
Traffic ( kbits) / BS / region
@ BH
# BSs & Config / region

Method :
Bit rate (kbps) / region

ATM, AAL5, IP, UDP, GTP OH + 24%
Signalling overhead + 1%
Output :
Bit rate (Mbps) / region
RNC --> SGSN

42
NOKIA
For packet size

Of 512 bytes
Via ATM/AAL5
Transmission Lines Calculation in RAN

When a needed amount of the physical connections (for example E1's or STM1s)
are calculated it should be always noticed that only available payload part of the
connection can be used. It was specified in ATM Forum that TS 0 & TS 16 are
not to be used for ATM traffic. Thus
Table 1: SONET Multiplexing Hierarchy

Electrical
Signal
43
NOKIA
Optical
Signal
Gross
Rate
(Mbps)
User Rate
(Mbps)
STS-1
OC-1
51.84
49.536
STS-3
OC-3
155.52
149.46
STS-12
OC-12
622.08
594.432
STS-48
OC-48
2488.32 2377.728
Possibility of Introducing AXCs

Max. capacity in different configurations
Iub traffic capacity
Interfaces
Config.
1
2
3
4
5
50 Node B- DU
BTS
128
192
256
320
384
RNC
AXC
50 X 0.33 E1
Iub Mbit/s
48
85
122
159
196
1 X STM1
1 X STM1
AXC
50 X 0.33 E1
1 X STM1
AXC
AXC
80 X 0.44 E1
80 X 0.44 E1
80 Node B- U
50 Node B- DU
80 Node B- U
44
NOKIA
Carriers
384
576
768
960
1152
STM-1
4*4
4*4
4*4
4*4
4*4
E1
64
96
128
160
192
Detailed Transmission requirement, NetAct Planner
45
NOKIA
46
NOKIA

3G Transmission Dimension Ing Process

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

3G Transmission Dimension Ing Process

Hochgeladen von

Copyright:

Verfügbare Formate

3G Transmission Dimensioning

TRS Planning Requirement & Dimensioning

Network Dimensioning Process Flowchart

Trs Network Dimensioning Process Flowchart

Iu-CS, Iu-PS, Iur

Network Dimensioning Process

CS/PS Core Network

# & type of Iub & Iu

RAN dimensioning output

(Node B < = > RNC)

Iur Link Capacity

(RNC < = > RNC)

RAN & Core dimensioning Steps

Packet Core Dimensioning

RAN Protocol Stacks

Circuit Switched Traffic

Packet Switched Traffic

RAN calculation related protocols & overheads, 1

RAN calculation related protocols & overheads, 2

Iub CCH FP (3GPP TS 25.435)

RAN: DCH FP (3GPP TS 25.427)

Iur CCH FP (3GPP TS 25.425)

RAN calculation related protocols & overheads, 3

Iu-User Plane Protocols

ATM protocols overhead consists of two-layers :

RAN calculation related protocols & overheads, 4

RAN calculation related protocols & overheads, 5

Voice Activity Factor

RAN calculation related protocols & overheads, 6

Different OH for Different Traffic Classes

Activity Service bit rate

RT12.2 (AMR) UL active

Activity service bit rate

service bit rate

Bit rate incl. FP Bit rate below ATM

Bit rate incl. FP Bit rate below ATM

Bit rate incl. FP Bit rate below ATM

Activity Service bit rate L1 bit rate

RAN Dimensioning Inputs

Iub Interface Dimensioning

Iub Protocol Overhead Assumptions

Iub Dimensioning, CS Traffic

7,5 Erl /BTS

Iub Dimensioning, CS Voice

Voice channel in Uu = 12,2 kbit/s

Voice in the ATM

Voice channel, Active = 18,9 kbit/s

Voice channel, Silent = 4,5 kbit/s

VAF of 67% is used in The Customer case

Iub Dimensioning, CS Traffic

7 ch's/BTS x 64 kbit/s/ch = 448 kbit/s/BTS

Iub Dimensioning (3/3), PS Data

Bit rate (kbps) / BS

PS Iub Bit rate (kbps) / BS

Introduction to Iur Interface

Iur interface is needed for :

Based on Nokia ATM Platform

Nokia RNC Dimensioning

What need to be checked ?

Nokia Radio Network Controller

RNC release 1.5 & 2

Iub traffic capacity

Nokia RNC Dimensioning