WCDMA RNP Radio Network Dimension Ing Huawei

Document code Target readers Edited by
Product name Product version Document version V100R001 WCDMA RNP
WCDMA RNP Radio Network Dimensioning Principles

For internal use only
Prepared by Reviewed by Reviewed by Granted by
URNP-SANA
Date Date Date Date
2003-12-19
Huawei Technologies Co., Ltd.

All rights reserved
WCDMA RNP Radio Network Dimensioning Principle
Revision record
Date 2003-12-19 2004-06-15 Revision version 1.00 1.10 Revision Description Initial issued Author Wu Zhong
In Chapter 3 Capacity Dimensioning Principle, Wu Zhong replacing the old algorithm with the new one, that is Kaufman Robert algorithm for CS services, and Nokia algorithm for PS services. Change CE number in the Table1 and revise according to review. Qinyan
2005-08-18
1.20
11-8-10
All rights reserved.
Page 2 of 50
Table of Contents
1Overview ................................ ................................ ................................ ................................ ..................... 8 2Link Budget Principle ................................ ................................ ................................ ................................ . 8 3Capacity Dimensioning Principle ................................ ................................ ................................ ............... 9 3.1 Brief Introduction to Cell Capacity Dimensioning ................................ ................................ ................ 9 3.2 Dimensioning of Cell Uplink Capacity of Mixed Services ................................ ................................ .. 11 3.2.1 Calculating Single User Load of Each Service in Cell Uplink ................................ ...... 12 3.2.2 Calculating Total Number of Users Supported by Cell................................ ................. 13 3.2.3 Calculating Cell Load of Single PS Service ................................ ................................ ... 13 3.2.4 Calculating Cell Load for All PS Services................................ ................................ ....... 15 3.2.5 Calculating CS Service GoS ................................ ................................ ............................ 15 3.3 Dimensioning of Cell Downlink Capacity of Mixed Services ................................ ............................. 16 3.3.1 Calculating Single User Load of Each Service in Cell Downlink ................................ . 16 3.3.2 Calculating Total Number of Users Supported by Cell................................ ................. 17 3.3.3 Calculating the Cell Load of Single PS Service................................ ............................. 18 3.3.4 Calculating the Cell Load of All PS Services ................................ ................................ . 18 3.3.5 Calculating GoS of CS Service ................................ ................................ ........................ 18 3.4 Balance between Cell Coverage and Cell Capacity ................................ ................................ ............. 20 4NodeB CE Dimensioning Principle ................................ ................................ ................................ .......... 21 4.1 Brief Introduction to NodeB CE Dimensioning ................................ ................................ ................... 21 4.2 NodeB CE Number Calculation ................................ ................................ ................................ ........... 21 5Iub Interface Flow Dimensioning Principle ................................ ................................ .............................. 24 5.1 Brief Introduction to Iub Interface ................................ ................................ ................................ ....... 24 5.2 Basic Ideas for Iub Interface Flow Dimensioning................................ ................................ ................ 27 5.3 Dimensioning of Iub Interface Transmission Flow................................ ................................ .............. 27 5.3.1 Dimensioning of Iub User Plane Flow................................ ................................ ............. 27 5.3.2 Iub Control Plane Flow Dimensioning................................ ................................ ............. 37 5.3.3 Iub Maintenance Bandwidth................................ ................................ ............................. 42 5.3.4 Dimensioning of Total Transmission Flow of Iub Interface................................ .......... 42 5.3.5 Iub E1 Configuration................................ ................................ ................................ .......... 43 6Pending Problems ................................ ................................ ................................ ................................ ..... 43 7Appendix................................ ................................ ................................ ................................ ................... 44 7.1 About Soft Blocking Probability................................ ................................ ................................ .......... 44
11-8-10
Page 3 of 50
List of Tables
Table 1 Table 2 Table 3 Table 4 Corresponding relation between bearer rate and CE_Amplitude ................................ ................... 21 Rate of FP control frame................................ ................................ ................................ ........... 31 Rate of FP common channel................................ ................................ ................................ ..... 32 Rate of signaling of Iub interface control plane ................................ ................................ ............ 41
11-8-10
Page 4 of 50
List of Figures
Figure 1 Figure 2 Figure 3 Basic idea of coverage and capacity iteration dimensioning................................ ......................... 20 UTRAN structure diagram................................ ................................ ................................ ......... 24 Iub interface protocol structure................................ ................................ ................................ .. 26
11-8-10
Page 5 of 50
WCDMA
Di
Pi
i l
WCDMA
Key : WCDMA i t f b : i
P
i t
t
i i
Di
i ,
i
it
i
i
Pi
i i
f bb evi i
1 1 9 D D 1 0 62 6(D9 5 2 62 9 81 '9 71 1 0 61 25 ) ) 2 ( 2) 2 0 0 ( ( 2 2 262D 0 6 1 25A 80) 1 (F2 2' 2D 1 0 )26(B 71 1 0 61 25 ) 30 1 0 66 5 61 (' 28( ' 2 1 BA )1 ( 71 1 0 61 25 ) ' 2B 5A1 2)0E 71 1 0 61 25 ) @ 8(9 (8 6( D 8A 6 62 9 81 '9 71 1 0 61 25 ) 2D 0 1 0 82 08 @' (55A 6 ( 6 1 25A 80) 6 D C
ti
ll
ti
ft
i l
it
B CE
i t f f t
i i i
fl
i l
. It
iz
x l t
ti
f t i
t il
ft
it
ix
: bb evi i ll A MA A A ti elli
AMR A M B ER CCH CE CS DCH DL EIRP P oS
Control Channel Channel Element Circuit S itched Dedicated CHannel Downlink Equi alent Isotropic Radiated Power rame Protocol rade of Service
HT odeB PS RA RNP SHO TCH TMA TU UE UL UMTS WCDMA
Hill Terrain Packet Switched Rural Area Radio Network Planning Soft HandOver Traffic Channel Tower Mounted Amplifier Typical Urban User Equipment Uplink Universal Mobile Telecommunications System Wideband Code Division Multiple
All i t . P
& %
$ #
''
I H
AA
t ti
Multi Rat us
ansf
Mode
Block E or Ratio
BA

i t l l
628 F' 26 )2 5 2D ' 0 71 1 0 61 25 ) @ 8(9 (8 2D 0 @' 02D )1 ( 66280'9
71 1 0 61 25 ) @ 8(9 (8 71 1 0 61 25 ) 4' 03 21 0 )('
'2 ' C 2 ' 2@(G 1 0
01 0'D 81 @6 2F 9 () ( 9 () C
i l
, CE, I ,
2 8( ' 2 1 G C I H E
!"!
Abb evi i Access
ll
elli
Page 7 of
RV
WCDMA Radio Network Dimensioning Principle
or internal use only
RS TURTSS RQ
1 Overview
WCDMA radio network dimensioning involves cell uplink/downlink link budget, cell uplink/downlink capacity dimensioning, NodeB CE number dimensioning and NodeB Iub interface transmission flow dimensioning, and so on. These dimensioning principles are introduced in dedicated documents separately, but provided no convenience for viewing and learning the WCDMA radio network dimensioning principles as a whole. or this, the document summaries these principles, providing clear physical explanations on various parts of the radio network dimensioning principles, and providing mathematical deduction process as much as possible. This document comprises the following chapters: Chapter : Brief introduction to the objective and main contents of this document. Chapter : Introduction to the link budget principle. (To keep the integrity of the radio network dimensioning principles, this part is presented as a chapter providing the reference documents only, without the specific link budget principle). Chapter
: The capacity dimensioning principles are given, including the uplink
capacity and downlink capacity dimensioning principles. Chapter : The dimensioning principle and dimensioning process of the number of NodeB CEs are explained. Chapter
: The dimensioning principle and dimensioning process of NodeB Iub
interface transmission flow are described in detail. Chapter : The pending problems in the radio network dimensioning are proposed. Chapter 7: Appendixes.
et Pri
i le
With link budget, we can work out the cell coverage radius in different scenarios and different services covered. or the link budget principle, refer to WCDMA RNP Technology Research on Special Topics High-Level Design Specifications for Link
All rights reserved. Page of
Yc
f e
Y` abYa`` YX
budget Tool [ ] . It is not further described here.
3
3.
ity
imensi ning Princi le
Brief Introduction to Cell Capacity Dimensioning
The WCDMA system can provide the users with diversified services, such as voice service, CS data service, and PS services at various rates. or these mixed services, the analysis of the cell capacity is very complicated, and there is no good solution method yet. Before the capacity dimensioning for mixed services, you need to determine the solutions for the following problems:
service can be represented by a blocking probability of 2%; and that of the Videophone can be represented by a blocking probability of %. oS of PS services: It is the requirement on the probability for the delay which dues to queuing of the PS services. or example, for a probability, the queuing delay should be less than 2s. (2) CS Service: Mixed sevice capacity dimensioning method
various CS services. In the uplink capacity dimensioning, the uplink load of CS service is taken as shared resource at the cell level; while in the donwlink capacity dimensioning, the downlink transmit power of CS service is taken as the shared resource at the cell level. (3) PS service: Mixed service capacity dimensioning method Before the RRM simulation result comes out1, the PS service dimensioning is
services affecting the PS service throughput.
Page
of
sx
The RRM simulation team will provide the simulation result with the oS requirement of PS
The Kaufman Robert algorithm is used to meet different
oS requirements of
st uvsutt sr
( )
oS for CS services and PS services oS of CS services: It is the requirement on the blocking probability of the CS services. or example, the oS of the AMR12.2k voice
services. Dimensioning the PS services respectively. Then, dimensoning uplink capacity , and sum up the uplink load generated by each PS service as the cell uplink load requirement of all the PS services; for donwlink capacity dimensioning, sum up the downlink transmit powers of each PS service as the downlink transmit power of all donwlink PS services. ( ) Consideration on soft handover proportion Uplink capacity dimensioning: Wihtout considering the influence of soft handover on the uplink traffic The uplink MDC gain is calculated based on 0.3dB. Downlink capacity dimensioning: Considering the influence of soft handover on the downlink transmit power The downlink MDC gain is calculated based on 1.0dB.
ote:
bearer rate less than 384k. In the network dimensioning, we may give a high -level item for setting whether to perform soft handover processing for the services with the bearer rate above 4k. (ii) Algorithm group: There is no simulation on the corresponding relation between the services with different bearer rates and the MDC gains. After discussion with the simuation engineers, the MDC gain varies a little with the services at different bearer rates. In the network dimensioning, we can consider the MDC gains are identical for all sevices.
( ) Activity factors of various services AMR voice service: the activity factor is 0. 7. CS data service: the activity factor is 1.0. PS data service: the activity factor is 0. as recommended.
ote: Suppose the DCCC switch is turned on, the activity factor of PS services should be close to 1, and it 2011-08-10 All rights reserved. Page 10 of
(i) RNC:
enerally speaking, we perform soft handover processing for all the services with the
performed with ErlangC, which can embody the
oS requirement of the PS
is recommended to be 0. .
The following are the cell uplink dimensioning process and cell downlink capacity dimensioning process:
Note: The cell capacity discussed here is specially for dedicated channel, instead of common channel. enerally, some low-rate services (for example, lower than 32kbps) can be borne by common channels.
The capacity of common channel is under research.
3.2 Dimensioning of Cell Uplink Capacity of Mixed Services

Before the cell uplink capacity dimensioning, here brief the calculation of the cell uplink load first. The documentation of WCDMA for UMTS [3] provides the uplink load calculation, as shown below:
LUL ! f . 1
j !1
1
1 W Rj
E b
N o j .V j
[4]
The Radio Network Planning and Optimization for UMTS shown below:
provides the result, as
N LUL ! 1 f . S \
N . j !1 1
1 W Rj
.V j
E b
N o j
Note: (i) In the above two formulae, rate,
refers to the neighboring cell interference factor,
is the bit rate of service
j, Vj
spcifies the activity factor of the sevice
j,
and
indicates
users are connected simultaneously in the same cell.
(ii) In the formula (3-2), sectors of the BS.
specifies the sectorization gain, and
refers to the number of
The main difference between the formula (3-1) and the formula (3-2): a)
Eb
N o j
2011-08-10
Page 11 of
(3-1)
(3-2)
is the chip
in the formula (3-1) corresponds to the activity factor V j , while that in the formula (3-2) corresponds to full rate, so they are consistent in principle; b) In the formula (3-2), sectorization gain is considered. In the currernt calculation, we use the formula (3-1). But the existing
obtained by means of simulation with full rate (that means the activity factor is 1), we should use the formula (3-2). Hence, for the cell uplink capacity calculation presents below, we use the formula (3-2) for description and explanation.
3.2.1 Uplink
Calculating Single User Load of Each Service in Cell
The single user load should be calculated for the users with soft handover and the users without soft handover respectively. As the service with soft handover has MDC gain, the corresponding single user load will be smaller. With the formula (3-2), we can work it out as follows: (1) Service j , without soft handover: uplink load of a single user
L j1 ! 1
Eb
1 W Rj
N o j .V j
(2) Service j , with soft handover: uplink load of a single user
L j2 ! 1
1 W Rj
E b
N o MDC UL j .V j
(3) Service j , all users: uplink load of a single user
Lj !
Note: (1)
L j1 L j 2 v SHO 1 SHO
W : 3.84MHz.
All rights reserved. Page 12 of
2011-08-10
i j
is
(1)
(2)
(3)
(2) (3) (4)
R j : Bearer rate of service j . V j : Activity factor of service j .
Eb
N 0 j : Demodulation performance of the receiver of NodeB of service j .

: The MDC gain of uplink of service
( )
j.
( ) SHO: Ratio of users performing uplink soft handover.
3.2.2
Calculating Total Number of Users Supported by Cell
Calculate the number of covered users by means of link budget as the total number of users the cell uplink needs to support. Note: The above is only for the case of single carrier. or the case of multi-carriers, it is calculated as follows:
TotalNumbe rOf sersSu pportedBy ell

Note:
NumberOf o vered sers . NumberOf a rriers
(1) Calculate the cell coverage radius based on link budget result, and then work out the cell coverage area. (2) Calculate the total number of users supported by the cell based on the density of traffic and cell coverage area. (3) In terms of capacity, the number of users to be supported is greater than or equal to the number of covered users, so the number of covered users calculated by means of link budget can be an input for capacity dimensioning. It is similar for the downlink.
capacity will be limited; otherwise, the coverage is limited.
3.2.3
Calculating Cell Load of Single PS Service
(1) Calculate the total throughput (Kbps) of PS services:
TotalThroughputRate ! TotalUserNumber v ThroughputOfSingleUserInBusyHours 3600

2011-08-10 All rights reserved. Page 13 of
(4) If the total number of covered users cant meet the
oS requirement of CS or PS service, the
k v t u u
onr qp m s
(2) Calculate the traffic in the case of no neighbouring interference:
P TotalThrou ghputRate ! v (1 Neighborin gCellInter ferenceFac tor ) Q RvV

( ) (3) Calculate the maximum channel number corresponding to the traffic with the
or PS services, the probability that the delay is less than t t arg et is
Pr[ CallDelay
t t arg et ] .
According to the ErlangC calculation formula, the relation between maximum
Pr[CallDelay " t t arg et ] ! 1 Pr[CallDelay P p0 Q ! P m!1 Q m

Note: (1) m refers to the maximum channel number. (2) H ! L s (3)
m
( )
P m Q H
t arg et
V R
specifies the average call duration.
is the average length of session of PS services. It is an input parameter. rom the view of
service model, the average length vary with different PS services. or www, the average length of uplink session is 12000Bytes, and that of downlink is 0000Bytes.
2011-08-10
Page 14 of
channel number and
premise of meeting the
oS requirement:
oS is shown blow:
t t arg et ]
! Pr ? CallDelay A Pr CallDelay " t t arg et
(4)
|
(4)
m P k P Q m 1 Q p0 ! P k! k !0 m!1 Q m
1
(4) Calculate the cell load of this PS service:
L PS _ j ! !
3.2.4
Calculating Cell Load for All PS Services
Sum up the cell load of each PS service to get the uplink cell load of all the PS services.
3.2.5
(1) Calculate the total cell load allowed for CS services:
CSServiceCellLoad ! TotalCellUplinkLoad SServiceCellLoad

(2) Calculate the traffic of each CS service in the case of no neighboring cell interference:
( )
P ! raffic fS ingle serI n usy ours v otal u be r f sersSu pported v 1 eighborin g ellInter ference ac tor Q (10) (3) Calculate the blocking probability of each CS service:
C
c ! C bk 1
G( c )
C
G( c )
c !0
(11)
2011-08-10
Page 15 of 50
L PS _
! L PS _ j
j
Calculating CS Service
1
1 W
j .V j
oS
(7)
(8)
Note: (1)
Bk : Blocking probability of service k.
(2)
c G( c ) ! a k bk G( c bk ) . Where, K refers to the total CS bearer service in the cell, ak

k !1
indicates the cell traffic corresponding to the CS service k, corresponding to the CS service k, and the CS service k. (3)
nk
refers to the maximum load allowed by the CS service of the cell uplink,
(4) Please note that both cell load and single user load are less than 100%, we can not calculate the blocking probability of each service with the formula (11). To use the formula (11) properly, it is necessary to adjust the cell uplink load of CS service and the single user load of CS service based on a specific ratio. It is recommended to enlarge the single user load and cell uplink load by 10000 times. Suppose the cell uplink load of CS service is 30%, and the single user load of the voice service is 0.82%. In the actual calculation, we can set the cell load of the CS service to 3000, and the single user load of the voice service to 82. Of course, in the actual calculation process, we can find a suitable multiple for enlarging based on the precision of the calculation result and the calculation rate.
3.3 Dimensioning of Cell Downlink Capacity of Mixed Services 3.3.1 Calculating Single User Load of Each Service in Cell
Downlink
(1) Service j , wihtout soft handover: average transmit power of a single user
(2)Service j , with soft handover: average transmit power of a single user

2011-08-10 All rights reserved. Page 16 of 50
p j1 !
x,j
CH
*Vj*P
a 1 a K G( c ) ! 1 . K nK n b !c n1
and
this
relation
bk
indicates the single user load
refers to the number of users simultaneously connected of
CH
* U f P
CL j
is
setup:
c e C.
(12)
(3)Service j , all users: average transmit power of a single user
pj !
Note: (1) (2)
p j1 p j 2 v SHO 1 SHO
W : 3.84MHz
: Bearer rate of service
j , V j : Activity factor of service j
(3) SHO: Ratio of users performing downlink soft handover (4)
Eb
N 0 j : Performance of the transmit end of the NodeB of service j

L
(6) (7) (8)
PDCH : Total transmit power of the downlink service channel
U : Average non-orthogonality factor; f
background noise ( )
CL j : Average coupling loss of cell downlink

Note:
CL j ! AverageMaxi u CouplingLoss fCe llDownlinkWorked ut yMeans fLink udget 10lg(7 / 30)

.
3.3.2
Calculating Total Number of Users Supported by Cell
Cal lat th number of covered users based on the link budget result, and take it as the
Note: The above is only for the case of single carrier. or the case of multi-carriers, it is calcualted as follows:
number of users that the cell downlink needs to support
N 0 : the floor noise of the receiving end of the UE, including thermal noise, Noise
(5)
MDC
: Downlink MDC gain of service
: Neighboring cell interference factor igure and
p j2 !
x,j
CH
Eb N o
* Vj* P
CH
* U f P
CL j
(13)
(14)
TotalNumbe rOfUsersSu pportedByC ell

Note:
NumberOfCo veredUsers . NumberOfCa rriers
The total number of users supported by the cell downlink is calculated in the similar method of uplink capcity dimensioning.
3.3.3
Calculating the Cell Load of Single PS Service
(1) Calculate the traffic of a PS service:
P TotalUserN umber v Throughput OfSingleUs erInBusyHo urs v (1 SHO ) ! Q 3600 v R v V

(15) (2) Calculate the maximum channel number corresponding to the traffic with the
The calculation method is the same as that for uplink. Based on the ErlangC calculation formula, the maximum channel number m
(3) Calculate the downlink transmit power of this PS service:
PPS _ j ! m v Pj
! mv
3.3.4
Sum up the downlink transmit power of each PS service to get the downlink transmit power of all the PS services in the cell:
S _ DL
3.3.5
Calculating
(1) Calculate the traffic of each CS service in the case of soft handover:
2011-08-10
with the
oS requirement of the PS service can be worked out:
p j1 p j 2 v SHO 1 SHO
Calculating the Cell Load of All PS Services
S_ j
premise of meeting the
oS requirement.
oS of CS Service
(16)
(17)
Page 18 of 50
P ! rafficOfS ingle serI n usyHours v otalNu be rOf sersSu pported v 1 SHO Q
(2) Calculte the transmit power of a signle user of each CS service of the cell downlink: It is worked out with the formula (14). (3) Calculate the blocking probability of each CS service:
C
c ! C bk 1
G( c )
C
G( c )
c!0
Please note that the downlink resource here refers to the downlink transmit power of CS service. As the downlink transmit power of PS service has been worked out with the formula (18), so we can get the maximum CS service transmit power by subtracting the PS service transmit power from the total transmit power. Suppose the target load of the cell downlink is 75%, with 25% for common channels and 50% for traffic channel. If the maximum transmit power of the cell downlink is 20W, the total transmit power of the traffic channels will be 10W. Suppose the transmit power of PS service is 5W, the maximum transmit power of CS service will be 5W too.
Note: (1)
Bk : Blocking probability of service k
k !1
Where, K refers to the total number of CS service types in the cell. But being different from the above,
ak
specifies the cell traffic corresponding to CS service k,
bk
specifies the average transmit power of
a single user corresponding to CS service k, and CS service simultaneously. (3)
nk
specifies the number of users connected with the
specifies the maximum transmit power of CS service in the cell,
refers to a certain
transmit power, and
c e C;
All rights reserved. Page 19 of 50
2011-08-10
(2)
G( c ) !
a1 1 a K . K nK n b ! c n1 !
, and a relation is set up::
c ( c ) ! a k bk ( c bk ) .
(18)
(19)
(4) Similar to uplink dimensioning, it is necessary to present the transmit power of CS service of cell downlink and the transmit power of a single user in integers. It is recommended to use mW as the power unit. In the actual iteration dimensioning, you can select a suitable unit for optimal dimensioning precision and dimensioning speed, for example, 5mW.
3.4 Balance between Cell Coverage and Cell Capacity

The cell coverage radius corresponding to the cell load can be worked out by means of link budget, together with the density of traffic, the number of covered users can be calculated. Then based on the number of users supported by the uplink cell and that supported by the downlink cell worked out by means of uplink/dowlink capacity dimensioning, compare the number of the covered users with the cell capacity. If the coverage and capacity are not balanced, you can balance them by adjusting the cell load (uplink load or downlink load), so as to complete the iteration dimensioning to get the cell radius after coverage and capacity balancing. or a certain coverage area, the minimum number of NodeBs required for coverage and the maximum number of users supported by each sector can be worked out.[7] . The following figure shows the basic idea of coverage and capacity iteration dimensioning.
Density of users
Cell load Number of carriers
Cell radius
Cell area
Number of users covered in the cell
Compare
Whether capacity and coverage balanced?
No
Uplink capacity dimensioning and downlink capacity dimensioning
Uplink service information

Adjust cell load Adjust number of cell carrier
Basic idea of coverage and capacity iteration dimensioning

Yes The dimensioning ends
4 NodeB
imensioning Princi le
4.1 Brief Introduction to NodeB CE Dimensioning

CE, channel element, corresponds to basic base band processing unit one by one. or the existing NodeB version, the CE resource of NodeB is shared within the site.
Huawei recommends calculating the number of CEs based on Site. In the calculation of the number of CEs, use the principle similar to that for NodeB capacity dimensioning, namely, Campbell theorem, and then combine different bearers into a virtual bearer to get the Erlangs of this virtual bearer, including uplink Erlang and downlink Erlang. With this method, the number of NodeB CEs worked out will be neither optimistic nor pessimistic. The documentations [2, 8] provide the comparison result. With the ErlangB calculation formula based on a certain blocking probability, you can work out the trunks required for the corresponding virtual bearer (for uplink and downlink respectively). Based on the trunks required for virtual bearer together with the CE_Amplitude under this virtual bearer, you can work out the number of CEs of uplink and downlink of the NodeB site. Of course, you can further calculate the number of uplink boards and downlink boards to be configured in NodeB.
4.2 NodeB CE Number Calculation

1. Corresponding relation between bearer rate and CE_Amplitude Different bearer rates may consume different numbers of CEs. The corresponding relations between bearer rates and the equivalent CE numbers are shown in the following table.
Corresponding relation between bearer rate and CE_Amplitude UL AMR12.2k CS64k PS64
2011-08-10
CE_Amplitude 1.00 3.00 3.00

DL AMR12.2k CS64k PS64
CE_Amplitude 1.00 2.00 2.00

Page 21 of 50
PS144 PS384
5.00 10.00
PS144 PS384
4.00 8.00
Note: The bearer rates and the corresponding CE_Amplitude in the table above, are provided by NodeB.
2. Calculation of NodeB CE number (a) Calculate the traffic at each bearer rate within NodeB: Erlang i (The suffix i represents different bearer rates) or voice service and CS data, as the traffic of a single user in busy hours is
known, you can calculate the corresponding Erlang voice and Erlang CSdata based on the number of users supported by NodeB,. or example, Erlang voice = Traffic of a single user in busy hours number of users supported by NodeB. The traffic of the CS data service can be calculated in the same method. or PS services, as the throughput of a single user in busy hours is known, you
can calculate the traffic of a single user of the corresponding PS service in busy hours. Together with the number of users supported by NodeB, you can calculate Erlang of the PS service with the method similar to that for
Erlang of CS service.
The following is the calculation fomula of the traffic for a single user of the PS service in busy hours.
TrafficOfS ingleUserO f SService InBusyHour s !

.
Throughput OfSingleUs erInBusyHo urs kbit BearerRate kbps v 3600 v ChannelOcc upationRat io
(b) Calculate the CE_Amplitude of the virtual service: Vitual _ CE _ Amplitude With the campbell theory, you can convert the mixed service (at different bearer rates) to a certain virtual service, so as to calculate the CE_Amplitude of this virtual service, as shown below:
CE _ Amplitude Erlang Virtual _ CE _ Amplitude ! CE _ Amplitude Erlang

2 i i i
(c) Calculate virtual traffic: Vitual _ CE _ Amplitude Obviously, the virtual traffic can be calculated as follows:
Virtual _ CE _ Traffic !
(CE _ Amplitude Erlang )

i i i
Virtual _ CE _ Amplitude
(d) Calculate the virtual trunks required: Vitual _ CE _ Trunk
calculate the virtual trunks corresponding to the virtual traffic, as shown below:
Virtual _ CE _ Trunk ! Erlang
1
[ Virtual _ CE _ Traffic v ( 1 SHO )
Where, SHO represents the ratio of soft handover. (e) Calculate the number of CEs required for NodeB: CE _ Num The virtual trunks and the corresponding CE_Amplitude are worked out with the above formula. Then you can calculate the number of CEs to be configured for the NodeB. However, for virtual service, adding one trunk requires adding
Vitual _ CE _ Amplitude CEs, as the following formula:

CE _ Num ! Virtual _ CE _ Amplitude v ( Virtual _ CE _ Trunk 1 ) .
(f) Calculate the number of uplink boards and downlink boards to be configured:
Nu berOf plinkCEsOfNode Nu berof plink oards , Nu berOfCEs Pr ovided y plink oard NumberOfDo nlinkCEsOfNodeB NumberofDo nlinkBoards NumberOfCEs Pr ovidedByDo nlinkBoard
.
Note: (i) Currently, the uplink board can provide 128 CEs, and the downlink board can provide 384 CEs at the maximum. 2011-08-10 All rights reserved. Page 23 of 50
In the view of soft handover ratio and
oS, you can use the ErlangB formula to
GoS ] .
(ii) The NodeB CE number dimensioning is to calculate the number of uplink CEs and downlink CEs respectively, or in one process. Whats difference is the Erlang corresponding to different bearer rates in NodeB of the uplink and downlink may be different.
5 I b Interf ce low
imensioning Princi le
5.1 Brief Introduction to Iub Interface

The UMTS system is composed of three parts: CN, UTRAN and UE. The interface between CN and UTRAN is defined as Iu interface, and that between UTRAN and UE is defined as Uu interface. UTRAN can comprise multiple radio network subsystems (RNS). Each RNS can contain one RNC and one or more NodeBs. The interface between RNC and NodeB is Iub interface. The following is the structure diagram of UTRAN:
UE
ME
Uu
RNS
CN
RNC Iu-CS (ATM) Iu-PS (ATM)
USIM
Iub (ATM) NodeB Iub (ATM) NodeB Iur (ATM) RNS
SS N
RNC Iub (ATM) NodeB Iub (ATM) NodeB Iu-CS (ATM) Iu-PS (ATM)
UTRAN
UTRAN structure diagram
In the 3GPP protocol, all the interfaces in UTRAN and the interface between UTRAN
MSC/VLR
and CN apply the Asynchronous Transfer Mode (ATM) as the transmission mechanism. The Iub interface is open. The basic functions implemented by the Iub interface are as follows: (1) Iub transmission resource management (2) NodeB operation and maintenance, including: Iub link management, cell configuration management, radio network performance measurement,
common transmission channel management, radio resource management, radio network configuration queue, and so on. (3) System information management (4) Common channel traffic management, including access control, power management, data transmission, and so on. (5) Dedicated channel traffic management, including radio link management, radio link monitoring, channel allocation/cancellation, power management,
measurement report, dedicated transmission channel management, data transmission, and so on. (6) Common channel traffic management, including channel allocation/cancellation, power management, transmission channel management, dat transmission, a and so on. (7) Timing and synchronization management, including: transmission channel synchronization (frame synchronization), NodeB-RNC node synchronization, NodeB-NodeB node synchronization. The protocol structure of Iub interface is as follows[9]:
2011-08-10
Page 25 of 50
Radio Network Layer
Control Plane
Node B Application Part NBAP
Transport Network User Plane
Transport Network Control Plane
Transport Network User Plane
Q.2630.1 Transport Network Layer Q.2150.2 SSCF-UNI SSCOP AAL Type5 SSCF-UNI SSCOP AAL Type5 AAL Type2
ATM Physical layer
Iub interface protocol structure
rom the view of horizontal plane of the above figure, the protocol structure
comprises radio network layer and transmission network layer; from the view of vertical plane, the protocol structure comprises control plane and user plane. An Iub interface is connected with one RNC and one NodeB. The transmission information in the Iub interface can be divided into three types: (1) Radio application relevant signaling: The Iub interface allows the negotiation between RNC and NodeB for the relevant radio resource. The information for broadcast channel control and the information transmitted on the broadcast channel are this type of signaling. In addition, the operation maintenance signaling between NodeB and RNC belong to this type of signaling. (2) Iub dedicated channel data stream (3) Iub common channel data stream The dimensioning of the transmission flow of the Iub interface involves not only the service data transmission flow of the expected users on the Iub interface, but also the
User Plane
CPCH FP USCH FP DSCH FP PCH FP FACH FP RACH FP DCH FP
factors like signaling flow. Based on the related documentations[10] and Huaweis relevant document[11], the transmission bandwidth required for the Iub interface and the relevant transmission configurations as well can be calculated.
5.2 Basic Ideas for Iub Interface low Dimensioning

The main purpose of the Iub interface transmission flow is to provide reference for interface configuration in the engineering procedure, as well as the interface configuration in other occasions. The following factors need to be considered for the dimensioning of data transmission flow of the Iub Interface: (1) P data frame utilization (2) AAL2 utilization ratio (3) NBAP flow (4) AAL5 utilization ratio (5) ATM cell utilization ratio (6) E1 utilization ratio (7) ALCAP flow (8) P payload flow (9) P control frame flow (10) Operation maintenance signaling flow
transmission flow of the Iub interface is the sum of three parts of flows, that is, Iub user plane flow + Iub control plane flow + Iub maintenance bandwidth. Therefore, the following are the dimensioning procedures for Iub user plane flow and Iub control plane flow respectively.
5.3 Dimensioning of Iub Interface Transmission low 5.3.1 Dimensioning of Iub User Plane low
1. low features with considering P/AAL2 encapsulation overhead

2011-08-10 All rights reserved.
We can view from the protocol structure of Iub interface from
igure 3 that the
Page 27 of 50
or the frame format, refer to TS25.427. As the overhead of the uplink P frame is
greater than that of the downlink P, the flow should be calculated based on the uplink P overhead.
encapsulation, 3 bytes of overhead (CID/LI/UUI/HEC) is added to the header of each micro cell. The payload of each micro cell is 44 bytes, and the excessive ones will be segmented for encapsulation. The calculation formula for the data rate after P/AAL2 encapsulation is as follows: (Header CRC/FT+CFN+TFI+TB+ E+CRCI+spare+CRC+AAL2 HEAD)8/TTI .
Note: According to the protocol, the spare of data frame is 0 to 2 bytes, the spare of control frame is 0 to 32 types. The RNC supports filling in, but not during transmitting (that means it is not for downlink). In the following flow calculation, it is specified that the uplink data frame uses a 2-byte spare, and the control frame uses a 0-byte spare, for calculating the maximum flow in theory, and the one in the actual application can be analogized according to NodeB.
The following are the data rates of the AMR full rate service after FP/AAL2 encapsulation (The ARM takes the coding unit of 20ms, that is, 50 frames/s, and full rate means the channel activity factor is 1) 12.2kbps: (1+1+3+11+13+8+1+1+2+2+3)8/0.02=18.4kbps 10.2kbps: (1+1+3+9+13+5+1+1+2+2+3)8/0.02=16.4kbps 7.95kbps: (1+1+3+10+11+1+1+2+2+3)8/0.02=14kbps 7.4kbps: (1+1+2+8+11+1+1+2+2+3)8/0.02 =12.8kbps 6.7kbps: (1+1+2+8+10+1+1+2+2+3)8/0.02=12.4kbps 5.9kbps: (1+1+2+7+8+1+1+2+2+3)8/0.02=11.2kbps 5.15kbps: (1+1+2+7+7+1+1+2+2+3)8/0.02=10.8kbps 4.75kbps: (1+1+2+6+7+1+1+2+2+3)8/0.02=10.4kbps The data rate of CS data service after FP/AAL2 encapsulation (full rate): 32kbps: (1+1+1+180+1+1+2+2+33)8/0.02=39.2kbps (TTI=20ms) 64kbps: (1+1+1+280+1+1+2+2+34)8/0.02=72.4kbps (TTI=20ms)
The data encapsulated by
P is then encapsulated by AAL2. During AAL2
14.4kbps: (1+1+1+172+1+1+2+2+32)8/0.04=17.4kbps (TTI= 40ms) 28.8kbps: (1+1+1+272+1+1+2+2+34)8/0.04=33kbps (TTI= 40ms) 57.6kbps: (1+1+1+472+1+1+2+2+37)8/0.04=63.6kbps (TTI= 40ms) The data rate of PS data service after FP/AAL2 encapsulation (full rate): 8kbps: 1+1+1+142+1+1+2+2+32)8/0.04=11.4kbps (TTI=40ms) 16kbps: (1+1+1+142+1+1+2+2+32)8/0.02=22.8kbps (TTI=20ms) 32kbps: (1+1+1+242+1+1+2+2+33)8/0.02=40.8kbps (TTI=20ms) 64kbps: (1+1+1+442+1+1+2+2+35)8/0.02=76.8kbps (TTI=20ms) 128kbps: (1+1+1+842+1+1+2+2+38)8/0.02=147.6kbps (TTI=20ms) 144kbps: (1+1+1+942+1+1+2+2+39)8/0.02=165.6kbps (TTI=20ms) 256kbps: (1+1+1+842+1+1+2+2+38)8/0.01=295.2kbps (TTI=10ms) 384kbps: (1+1+1+1242+1+1+2+2+312)8/0.01=439.2kbps (TTI=10ms) 3.4kbps channel associated signaling overhead (full rate): (1+1+1+119+1+1+2+2+3)8/0.04=6.2kbps (TTI=40ms) 2. FP control frame overhead (a) TIMING ADJUSTMENT: 5byte, Spare Extension: 0--32byte When a time window appears, NodeB sends the time adjusting frame, supposed once per 100TTI (TTI=20ms) for each DCH bearer, the flow will be 16 bps. The time adjusting frame seldom occurs in the actual environment. (b) DL SYNCHRONI ATION: 3byte. Spare Extension: 0--32byte Transport channel synchronization is used for the synchronization of the initial setup stage, and for the troubleshooting for the bottom layer AAL2 as well. The flow of synchronization for the initial stage can be omitted (as service data transmission has not started yet), and that of the synchronization for troubleshooting is related to the detection cycle. For example, if the detection is performed once per 5s, the flow will be 9.6 bps. (c) UL SYNCHRONI ATION: 5byte, Spare Extension: 0--32byte The transport channel synchronization is used for the synchronization of the
initial setup stage, and for the troubleshooting for the bottom layer AAL2 as well. The flow of synchronization for the initial stage can be omitted (as service data transmission has not started yet), and that of the synchronization for troubleshooting is related to the detection cycle. For example, if the detection is performed once per 5s, the flow will be 64 bps. (d) OUTER LOOP POWER CONTROL: 3byte, Spare Extension: 0--32byte The SIR used for updating outer loop power control. Suppose it is once per 400ms, the load flow will be 120 bps. (e) DL NODE SYNCHRONI ATION: 5byte, Spare Extension: 0--32byte Node synchronization is used for Iub delay estimation. It does not attach to call service, thus can be omitted. (f) UL NODE SYNCHRONI ATION: 11byte, Spare Extension: 0--32byte Node synchronization is used for Iub delay estimation. It does not attach to call service, thus can be omitted. (g) DSCH TFCI SIGNALLING [FDD] : 5byte, Spare Extension: 0--32byte, once per10ms At present, the system does not support DSCH, so the flow of DSCH TFCI SIGNALLING is not considered for the moment. (h) RADIO INTERFACE PARAMETER UPDATE [FDD] : 6byte, Spare Extension: 0--32byte Radio parameter update will be initiated after the handover is completed and RLS is added. It can be omitted.
Note: The typical structure of control frame is: (Frame CRC+FT)+Control Frame Type+Control Information+Spare Extension. Where Frame CRC+FT is 1byte, and Control Frame Type is 1byte. In the above calculation, the uplink control frame uses a 32-byte spare, for calcualting the maximum flow in theory. It can be analogized according to the realization of the NodeB in the actual application. Spare filling is not performed for the downlink RNC.
The following table lists the data rates corresponding to various FP control frames.
Rate of FP control frame Message name TIMING ADJUSTMENT DL SYNCHRONIZATION UL SYNCHRONIZATION OUTER LOOP POWER CONTROL DL NODE SYNCHRONIZATION UL NODE SYNCHRONIZATION DSCH TFCI SIGNALLING[FDD] RADIO INTERFACE PARAMETER UPDATE[FDD] Rate (bps) 160 9.6 64 120 It is used for Iub delay estimation, and it does not attach to call service, thus can be omitted. It is used for Iub delay estimation, and it does not attach to call service, thus can be omitted. The system does not support DSCH, so it is not considered for the moment. Radio parameter update will be initiated after the handover is completed and RLS is added, so it can be omitted.
From the above analysis, the flow of control frame is much lower than that of service data frame, so it can be omitted. 3. Common channel Common channel is set up in the cell setup stage with the default channel configurations for general cases. The default configurations of various channels are as follows: (a) RACH TBSize=168 or 360bit, TTI=10ms, the maximum traffic is calculated based on 360 bits. Header CRC/TF+CFN+TFI+PropagationDelay+TB+CRCI+spare+CRC+AAL2 header The flow after FP/AAL2 encapsulation is: (1+1+1+1+360 / 8+1+2+2+32)8 / 0.01 = 48kbps. Each cell can be configured with one to two RACH channels. (b) FACH (i) FACH signaling TBSize=168, TBNum=2, TTI=10ms Header CRC/TF+CFN+TFI+TransmitPowerLevel+TB+spare+CRC+AAL2
header The flow after FP/AAL2 encapsulation is: (1+1+1+1+1682 / 8+2+32)8 / 0.01 = 43.2kbps. (ii) FACH data TBSize=360, TBNum=1, TTI=10ms Header CRC/TF+CFN+TFI+Transmit power level+TB+spare+CRC+AAL2 header The flow after FP/AAL2 encapsulation is: (1+1+1+1+360 / 8+2+32)8 / 0.01 = 45.6kbps. Each cell can be configured with one to four FACH channels. In case there is only one FACH channel, the signaling and data are multiplexed, in the configuration mode for signaling FACH. (c) PCH TBSize=240, TBNum=1, TTI=10ms Header CRC/TF+CFN/PI+TFI+PI-bitmap+TB+spare+CRC+AAL2 header The length of PI-bitm is related to the configuration of common channel.
Corresponding to the configurations of 18, 36, 72 and 144 segments of the PI, it is 3, 5, 9 and 18 bytes in length. The current common channel uses configuration of the PI with 18 segments. The traffic after FP/AAL2 encapsulation is: (1+2+1+3+30+2+3)8 / 0.01 = 33.6kbps. Each cell supports one PCH channel. The following table lists the rates of various FP common channels:
Rate of FP common channel Common channel name RACH 48 Each cell can be configured with one to two RACHs channels. In Huaweis product, each cell is configured with one RACH channels. FACH
2011-08-10
Rate (kbps)
Ramark
Signaling rate: 43.2
Each cell can be configured with one to four FACHs

Page 32 of 50
Data rate: 45.6
channels. In case of there is only one FACH, the signaling and data will be multiplexed, in the configuration mode of signaling FACH. In Huaweis product, each cell is configured with two FACHs, one of which for signaling transmission and the other for data transmission.
PCH
33.6
Each cell supports one PCH.
4. AAL2 sub-multiplexing The AAL2 multiplexing can improve the ATM transmission efficiency, but the additional overhead caused by sub-multiplexing must be considered. When configuring the flow of Iub interface, it is recommended to add 10% of AAL2 multiplexing overhead to it. In the case of AAL2 multiplexing, each ATM cell has 1 byte of overhead (STF domain). In addition, the header of each ATM cell has 5 bytes of overhead.
Note: At present, the TIMER_CU of the AAL2 micro code is set to 500us, that is , a single cell may be in the 500us additional delay brought by sub-multiplexing, namely the maximum PAD filling rate of AAL2. The data of a single application are transmitted equably (for example, AMR TTI=20ms), but the transmission between multiple upper-layer applications are not dispersed equally. That is to say, the flow peak value may occur in a period of time due to the concurrent transmission of multiple applications; and may be idle for a period of time. This is the case of uneven peak/off-peak. As the buffer of the AAL2 micro cell is restricted, if the buffer is full when the transmission failure due to burst flow, the
lowered, thus affecting the performance of the equipment. Therefore, the ATM flow must be able to adapt to this application requirement. Take the 12.2kbps AMR voice for example, the length of each micro cell is 46 bytes. If the TIMER_CU of only one micro cell expires, the PAD of one byte is added. If the single TIMER_CUs of two micro cells expire, the PAD of two bytes is added behind the second one. If the TIMER_CUs of three micro cells expire, the former two cells are transmitted, and the third one will be transmitted in the next time of expiration. Similarly, one AAL2 PACH can bear 248 CIDs, which is updated once per 20ms. The maximum PAD added is 248 bytes (it is an extreme), and the minimum PAD added is 13 bytes (it is
2011-08-10
oS will be surely
Page 33 of 50
transmitted at each TIMER_CU). The corresponding maximum sub-multiplexing overhead is 99.2kpbs, with 2% of multiplexing overhead increased. Take the 10.2kbps AMR voice for example, the extreme multiplexing overhead is 7.8%. By means of analysis on other service types, you can get the application with the lower rate, whose extreme multiplexing overhead is the larger.
5. Activity rate of 3.4K channel associated signaling channel The RRC signaling exchanged for each call and the length are shown as follows: Where, the red ones are for uplink and the blue ones are for downlink.[3]. RB Release RB Release Complete RB Setup RB Setup Complete RRC Connection Release RRC Connection Release Complete RRC Connection Request RRC Connection Setup RRC Connection Setup Complete Initial Direct Transfer Uplink Direct Transfer Downlink direct Transfer UE Capability Enquiry UE Capability Information UE Capability Information confirm Measurement Control Measurement Report measurement report) Active Set Update Active Set Update Complete 54 (Soft handover signaling) 78 (Soft handover signaling) 96 80 208 83 8 6 91 159 45 40 60 60 46 RNC ==> UE 80 UE ==> RNC 46 RNC ==> UE 50 68 (Event triggering
The algorithm of switch setting can be used for the measurement on Uu interface.
The measurement modules involved include AMRC, DCCC, HO and LCS. Different report modes are used for different measurement items. Event report, periodical report and the period of periodical report are configurable at the background. There are six periodical measurement reports and 6 event reports at the maximum. As LCS is used for location only, it is not considered. Each UE uses one type of service only, and use only two HO periodical measurement items (mutually exclusive) and one AMRC or DCCC measurement item, use only four HO event measurement items and one AMRC or DCCC event measurement item. Suppose the period of periodical report is 1s, the event report is transmitted once per 30s, the soft handover overhead is 30%, and there are 3 branches (it is necessary to transmit the activity set update message for twice), the call duration is 60s, and the connecting time is 10s, you can get that the time from conversation to data transmission is 50s. The calculation formula is: (Total byte number8bit / 60s)/ 3400bit/s). Downlink: ((96+208+8+60+46+46+508+5430%2)8/60)/3400 =3.5%; Uplink: ((80+83+6+45+40+60+80+68503+6852+7830%2)8/60)/ 3400 = 44%. Because most RRC flows use the RCL confirmation mode, the activity rate of 3.4kbps channel associated signaling is 50%. 6. User plane flow of Iub interface User plane flow=Common channel flow + Voice service flow + Data service flow + Channel associated signaling flow User plane flow (downlink) =(FACH (Signaling) The number of FACHs (Signaling)+ FACH (data) The number of FACHs (data) + PCH the number of PCHs+ 12.2AMR rate The number of voice users Voice activity factor + PS rate The number of data users Data activity factor + Channel associated signaling flow The number of users Signaling activity factor) AAL2 sub-multiplexing ATM multiplexing = (43.2NFACH
2011-08-10
signaling
+ 45.6NFACH
data
+ 33.6N PCH +18.4NvoiceVADV +

Page 35 of 50
VdataN dataVADD+ 6.2VADS(Nvoice+N data))1.153 / 47 User plane flow (uplink) =(RACH The number of RACH + 12.2AMR rate The number of voice users Voice activity factor + PS rate The number of data users Data activity factor +Channel associated signaling flow The number of users Signaling activity factor) AAL2 sub-multiplexing ATM multiplexing = ( 48NRACH + 18.4 Nvoice VADV + VdataNdata VADD + 6.2 VADS (Nvoice+N data)) 1.1 53 / 47 Minimum number of AAL2 Paths =
Note: (i) The flow unit above is kbps. (ii) NRACH, NFACH signaling, NFACH data and NPCH are the numbers of various types of common channels supported by the whole NodeB. (iii) Nvoice and Ndata are the number of voice users and the number of data users of the whole NodeB. (iv) Vdata is the rate after FP/AAL2 encapsulation, which is contained when the data service is used. (v) The common channel needs to bear the UE common procedures and the low-rate PS service, so it has a high multiplexing efficiency, with the channel activity factor being 1. Generally, for voice service, data service and channel associated signaling, it is used discontinuously, so it is necessary to consider the activity factor. The activity factor of voice VADV ranges from 0.5 to 1. As the usage character of the data service is unknown, it is recommended to set its acticity factor VADD to 1 for guaranteeing its and set the activity factor VADS of signaling to 0.5. (vi) If the common procedures of UE (such as attach, detach and short message) are implemented with dedicated channel, it is necessary to add the requirement on the flow of these procedures. The additioal flow = The number of Iub service users (considering the convergence ratio) The number of sevices in busy hour/3600 Common procedure duration 6.2 VADS 1.1 53/47. (vii) If the tranamission equipment has plentiful resources, in terms of engineering, 25 percent of headroom will be added for supporting burst service. (viii) For the user plane of Iub interface, CBR and RT-VBR are used for PVC in most cases. In the 2011-08-10 All rights reserved. Page 36 of 50
Nvoice Ndata v 2 . 240
oS,
configuration, if CBR is used, it is required that its PCR be greater than or equal to the flow calculated above; if RT-VBR is used, it is required that its SCR be greater than or equal to the above value. In addition, the PCR is 120% of the SCR.
5.3.2
Iub Control Plane Flow Dimensioning
1. Control Plane composition The Iub control plane is composed of one NCP link, one to n CCP links and one ALCAP link. The NCP link is for transmitting the message related to the common procedures, such as audit, cell setup/deletion/re-configuration, common channel setup/deletion/re-configuration, common measurement and radio link setup. The CCP links bears the messages related to dedicated procedures, such as RL addition/deletion/re-configuration, RL recovery failure and dedicated
measurement. The ALCAP link is for transmitting the AAL2 connection message at the Iub interface. The NCP/CCP/ALCAP link is over SAAL directly. Four bytes of protocol head overhead are added for the SAAL (SSCOP). In addition, for the SSCOP, one to three bytes should be filled in so as to align the PDU 4 bytes. 2. Overhead of AAL5 The control plane adopts AAL5 encapsulation, and the relation between SDU and PDU of AAL5 is as follows: If (SDU mod 48) > 40, then PDU = (SDU SDU mod 48))+96. Or, PDU = (SDU (SDU mod 48)) + 48. 3. The signaling exchanged for one call of a single service. The red ones are for uplink and the blue ones are for downlink. The column in the middle specifies the actual length, and the last column specifies the length of the message after AAL5 encapsulation. RL_SET_RE
RL_SET_RESPONSE RL_RESTORE_INDICATION RL_RECONFIG_PREP

2011-08-10
122 74 27 299
=> => => =>
144 <NCP> 96 <NCP> 48 <CCP> 336 <CCP>

Page 37 of 50
RL_RECONFIG_READY RL_RECONFIG_COMMIT
62 21
=> => => 19 => => 16
96 <CCP> 48 <CCP> 96 <CCP> => 48<CCP>
DEDI_MEASUREMENT_INIT 53 DEDI_MEASUREMENT_RESPONSE DEDI_MEASUREMENT_REPORT 36 DEDI_MEASUREMENT_REPORT 36 DEDI_MEASUREMENT_TERMINATE RL_DELETE RL_DELETE _RESPONSE Four ALCAP signaling: ERQ ECF RLSD RLC Common measurement: COMM_MEASUREMENT_INIT 45 COMM_MEASUREMENT_INIT 45 76 13 12 6 34 17
48 (TCP, AMRC/DCCC/DPB) 48 (SIR, OLPC) => 48<CCP>
=> =>
48<CCP> 48<CCP>
=> => => =>
96 <ALCAP> 48 <ALCAP> 48 <ALCAP> 48 <ALCAP>
=> =>
96 (RTWP)<NCP> 96 (TCP) => 48 <NCP> <NCP>
COMM_MEASUREMENT_RESPONSE 19 COMM_MEASUREMENT_REPORT COMM_MEASUREMENT_REPORT
29 =>
48 (RTWP) <NCP> <NCP>
28 => 48 (TCP)
Calculating with the consideration of IMSI attach, IMSI detach, location update, SMS overhead: four times/user/h, based on the convergence ratio of 40, with the ratio of processing frequency to call frequency is (404/3600): (1/60), that is 2.67. (Refer to the MOT traffic model). Generally, these procedures are implemented on common channels, without considering this part of overhead. Huaweis product is set with a switch. That is, the transmission for the engineering can be performed on both dedicated channels and common channels. Therefore, the following provides the analysis for both cases respectively.
(i) NCP The radio link setup message and common measure message are major messages. The procedures for cell management are initial procedures, which can be omitted during flow calculation. In common measurement, two 200-ms periodical measurements are started for each cell. Suppose the whole Node B support N users concurrently, and each user makes each call in 60s. The following dedicated channels are used for the IMSI attach and other procedures: Downlink: 144N/6053/4883.67 =(78N)bps Uplink: ((48+48)M1000/200+96N/603.67)53/488 =(4240M+52N)bps. The following common channels are used for the IMSI attach and other procedures: Downlink: 144N/6053/488 =(22N)bps Uplink: (96M1000/200+96N/60)53/488 =(4240M +15N)bps Where, M is the number of cells supported by NodeB, and N=N voice+Ndata. (ii) CCP When the algorithm switch is turned on, the AMRC starts a periodical measurement with the period of 4.8s, for every RL; the DCCC also starts a periodical measurement with the period of 640ms, and starts a periodical measurement with the period of 700ms for each RL in the case of soft handover. Suppose the soft handover ratio is 30%, and two measurements are started for
each voice and data user and one is started for the attach type service, the flow is calculated as follows: The following dedicated channels are used for the IMSI attach and other procedures: Downlink: ((336+48+(96+48)2+48)+(96+48+48)2.67)N/6053/488 =(182N)bps Uplink: ((48+96+482+48+(48+48+48))2.67)N voice/60+48N
voice(1/4.8+1/0.730%)+(48+96+482+48+(48+48+48)2.67)N data/60+4
8Ndata (1/0.64+1/0.730%))53/488 =(370Nvoice+968Ndata)bps The following common channels are used for the IMSI attach and other procedures: Downlink: (336+48+(96+48)2+48)N/6053/488 =(106N)bps Uplink: ((48+96+482+48)Nvoice/60+48N
voice(1/4.8+1/0.730%)+(48+96+482+48)Ndata /60+48Ndata (1/0.64+1/
0.730%))53/488 =(314Nvoice+891Ndata)bps Where, N=Nvoice+Ndata. It is mainly required for measurement. (iii) ALCAP Suppose NodeB supports N users simultaneously, and each user makes each call in 60s. The following dedicated channels are used for the IMSI attach and other procedures: Downlink:
((96+48)2+(96+48)2.67)N/6053/488 =(99N)bps Uplink: ((48+48)2+(48+48)2.67)N/6053/488 =(66N)bps The following common channels are used for the IMSI attach and other procedures: Downlink: ((96+48)2)N / 6053 / 488 =(43N)bps Uplink: ((48+48)2)N / 6053 / 488 =(29N)bps The following table lists the rates of various types of signaling of the Iub interface:
Rate of signaling of Iub interface control plane Name NCP Uplink rate (bps) 4240M+52N Downlink rate (bps) 78N IMSI 4240M +15N 22N Remarks Dedicated channels used for the attach and other procedures Common channels used for the IMSI CCP 370Nvoice+968Ndata 182N attach and other procedures Dedicated channels used for the IMSI 314Nvoice+891Ndata 106N attach and other procedures Common channels used for the IMSI ALCAP 66N 99N attach and other procedures Dedicated channels used for the IMSI 29N 43N attach and other procedures Common channels used for the IMSI attach and other procedures
2011-08-10
Page 41 of 50
WCDMA Radio Network Dimensioning Principle Note: (i) N=Nvoice +Ndata,, and M is the number of cells supported by NodeB.
(ii) To consider the SAAL overhead and link utilization, it is necessary to add 10% of flow headroom based on the flow mentioned above. (iii) As the product supports the two modes of using dedicated channels and common channels for IMSI attach and other procedures, the larger value of flow in the dimensioning will be used for the signaling dimensioning. That is to cal ulate the signaling flow of the Iub interface in the mode of using c dedicated channels for IMSI attach and other procedures. (iv) The AAL5 overhead has been considered in the signaling rate mentioned above.
5.3.3
Iub Maintenance Bandwidth
The operation and maintenance bandwidth of NodeB is set according to the configuration. The typical value of the operation and maintenance bandwidth of NodeB is 640kbps.
5.3.4
Dimensioning of Total Transmission Flow of Iub Interface
Based on the analysis and calculation of the user plane flow and control plane flow of the Iub interface, together with the Iub interface maintenance bandwidth, the total transmission flow of the Iub interface can be worked out as follows, considering the soft handover headroom: The total transmission flow of the Iub interface = (Iub user plane flow + Iub control plane flow) (1+ Soft handover headroom) + NodeB operation and maintenance bandwidth.
Note: (i) Sub-multiplexing headroom and burst redundancy are considered in the Iub user plane and control plane. (ii) Soft handover headroom should be added to the user plane flow and control plane flow.
2011-08-10
Page 42 of 50
5.3.5
Iub E1 Configuration
The utilization of the E1 link can be calculated in two modes, both of which are supported by Huawei. (1) UNI mode, the E1 utilization rate is: 1920kbps /2048kbps=93.75%. (2) IMA mode, in the case of frame length being 32, the E1 utilization rate is: 1859kbps /2048kbps=90.77%; in the case of frame length being 64, the E1 utilization rate is: 1889kbps /2048kbps=92.24%; in the case of frame length being 128, the E1 utilization rate is: 1904kbps /2048kbps=92.97%; in the case of frame length being 256, the E1 utilization rate is: 1911.5kbps /2048kbps=93.33%. Therefore, based on the Iub transmission flow considering the E1 utilization, the number of E1s to be configured can be worked out as follows: The number of E1s to be configured is
IubInterface otal rans ission raffic( Mbps ) . 2 Mbps v E1 tilization
6 Pending Problems
The above chapters present the WCDMA radio network dimensioning principles. But our research on the radio network dimensioning is not so deep in many aspects so far, and some pending problems are to be solved. At present, the purpose of capacity dimensioning is to calculate the number of users that the cell uplink and downlink can support under a certain cell load, and then compare the capacity dimensioning result with the link budget. Is this dimensioning mode the only one for judging whether the coverage and capacity are balanced? Can the dimensioning and comparison be performed according to the throughput allowed by the PS service (such dimensioning is reasonable and in accord with the ErlangC)? For example, based on the number of users covered by
the cell worked out by means of link budget, together with the traffic of a single user in busy hours of CS service and that of PS service, we can calculate the throughput of the PS services under a certain cell load with the premise of allowing concurrent CS user connection. Similarly, by means of capacity dimensioning, we can work out the throughput of the PS services allowed to access when the coverage requirement is met, and then compare the PS service throughput calculated in these two cases, so as to judge whether the coverage and capacity can be balanced.
7 Appendix
7.1 About Soft Blocking Probability
(1) Features of WCDMA data service For WCDMA data service, the data rate is high, and the number of users communicating simultaneously that can be borne is small. That is, the number of channels is small. However, the channels of WCDMA are different from those of GSM, which are hard channels. If the number of users is greater than the number of channels, the excessive users will surely encounter blocking. The blocking probability can be calculated with the Erlang formula. While the channels of WCDMA is soft channels, and the number of channels varies with the interference. If the blocking probability of hard channels is still used, with a threshold being set, and the Erlang value of the data service being calculated with the Erlang formula, it will make big error. For example: Create a WCDMA single service data model, with the activity factor being 0.1 and the maximum channel capacity being 3.9, and then calculate the Erlang traffic when the blocking probability is 0.02. If the hard threshold is adopted, the maximum channel number is 3, the traffic will be 10 Erlang_B(3, 0.02), that is 6; if the maximum channel number is 4, the traffic will be 10 Erlang_B(4, 0.02), that is 11. That is, when the channel capacity is changed to 4 from 3.9, the traffic changes a lot, which is not practical at all. This is because the channel capacity is small for high-rate data service. When the channel capacity is changed to 4 from 3, it is a large change. But the channel capacity is large for
voice service. For example, when the capacity is changed to 51 from 50, it is a small change. So the hard channel blocking probability is not suitable for the calculation of the WCDMA data flow. (2) New traffic calculation method We still use the above example. When the number of users communicating simultaneously is 3, and the channel capacity is 3.9, so 0.9 more users can access the system. If the method for hard channel is used, no more new users can access. However, with the features of CDMA, we can adopt the probability statistics method for analysis. If the system load is light, it can accept more new users; if it is heavy, it will accept less new users. Therefore, when the channel has headroom of 0.9, the new user accepting rate will be taken as 0.9, and the rejection rate will be 0.1. By far, we can create a new queuing model to get the blocking probability. In this case, the blocking probability can not be represented by the Erlang formula, but should be calculated by means of mathematical derivation. The following shows the derivation process: Suppose the system is a Lost Call Cleared (LCC) system, which does not provide queuing function for the call requests. When a user requests for service, the user can access the system within the preset minimum call setup time if a channel is available. If all the channels are occupied, the call will be blocked, and the user can not access the system. The blocked user returns to an infinite user group at once, and can attempt to access the system any time thereafter. Suppose
Pi
specifies the probability of
users in the system,
Mspecifies
the
arrival rate of the users, capacity is
refers to the user drop-out rate. Then suppose the system to get the maximum channel number
c, which is not an integer. Round up c
N ! ?cA. According
to the detailed derivation process mentioned in Appendix A.1.1 of
Reference [12], we can get:
P N ! M N /N! P 0 N
2011-08-10 All rights reserved.
(7-1)
Page 45 of 50
When the number of users in the system is N, which is the maximum number of users supported by the system, the blocking probability can be calculated with the Erlang
P sPr Pr?blockedA !
formula,
M N /N! /u
k!0
doesnt reached when the number of users in the system is N, set is a decimal fraction, and 0
ratio, the probability of new user permission is reaches N, new users with the probability of with the probability formula:
M P N1 ! P N a N1 u
The above formula indicates the new user permission probability is number of users in the system is
Based on the probability sum of 1, we can get that
substitute the formulae (7-1) and (7-2) into it as follows:
P0 !
P N1 !

5 k!0
When the system has When the system has
no more users can access the system, so the system blocking probability can be worked out as follows:
/u 5 (M k /k!) . As the maximum capacity of the system c
a!cN
(where
1), a
more users can access the system. In terms of
a. Therefore, when the number of users

can access the system and new users
1a
will be rejected. This is shown as the following state transition
(7-2)
when the
N, so that the number of users in the system is N 1.

N1
P 0 , P 1 N1. P
k!0
Pk ! 1
. Then
1 N M k /k! a N N1 /N1 ! M u k!0
PN !

M N N /N!
5 k!0
Mk M N1 /N1 ! u /k! a N
and
a M N1 /N1 ! N
Mk M N1 /N1 ! u /k! a N
users inside, the new user rejection probability is
1 a.
N1
users inside, which is the maximum capacity of the system,

u a. M N1 /N1 !1a M N /N! u N M k /k! a M N1 /N1 ! /u u k!0
P ! P N1 1 a N ! P
The activity factor is not considered in the formula above. Suppose the activity factor is
v, the blocking probability of the system is.

PB !
v a. M N1 /N1 !1a M N /N! uv u N M m /m! a M N1 /N1 ! v/u uv m!0
(7-3)
If the traffic N and the activity the formula above. If
are specified,
PB
can be worked out based on
PB
is specified, and the outgoing traffic is u , you can not get the result with the
M v
above formula, but with the following conversion formula:

PB 1a B a1a M N1 P uv
v M N1 /N1 ! N N1 v M k /k! u k!0
(7-4)
The right of the formula (7-4) is the Erlang formula for calculation convenient. The following is an example of calculating the traffic with the formula (7-4). (3) Application example Suppose the capacity of a system is
c ! 3.1. Round it up to get N ! 3, and then

specify that
a ! c N ! 0.1. The Activity factor v ! 0.1, and

calculate the traffic, as shown below: First calculate the approximate range
PB
0.02, and then
M : v/u
M ! Erlang_B0.02, 3 ! 0.6022 v/u

0.02
The left of the formula (7-4) is 0.90.020.10.941/0.6022 Then the actual traffic is:
! 0.0033.
M ! 1/v Erlang_B0.0033, 4 ! 6.192. /u

This is close to the actual situation, because when the capacity is 3, the traffic will be
6.022; when the capacity is 3.1, the traffic will be 6.192. The increase is small, which is in accord with the actual situation. Then suppose the channel capacity is 3.9, the left of the formula (7-4) is
0.02 0.1 0.020.90.1 1/0.6022 4
! 0.013
then
the
actual
traffic
is
M ! 1/v Erlang_B0.013, 4 ! 9.5. /u

When the channel capacity is 4, the traffic is 11. So the traffic when the channel capacity is 3.9 is very close to the traffic when the channel capacity is 4. It is in accord with the actual situation. Suppose the channel capacity is 3.5, , the then left the of the formula traffic is is
0.02 0.50.020.50.541/0.6022
! 0.005
actual
M ! 1/v Erlang_B0.005, 4 ! 7. /u

accord with the actual situation.
The traffic is between 6 and 11, which is in
Based on these, we can get the following conclusion: Using the new traffic calculation method solves the problem of traffic mutation caused by round-up. With the original method, for example, when the channel capacity is 3.99, the traffic can be calculated with the number of channels of 3. When the channel capacity is 4, the traffic is calculated with the number of channels of 4. The channel capacity is changed to 4 from 3.99, the traffic mutation occurs. With the new traffic calculation method, the traffic varies continuously with the channel capacity, without mutation. The new traffic calculation method adopts the probability statistics method. The lighter the load, the higher the user access probability, and vice versa. For example, if the channel capacity is 3.9, and three channels are in use, a big headroom is available, so the access probability of the system is big, which is 0.9; if the channel capacity is 3.1, and three channels are in use, the headroom is small, so the access probability of the system is small, which is 0.1. This is in accord with the actual situation. To calculate the blocking probability based on traffic, you can use the formula (7-3). To calculate the traffic based on blocking probability, you can use the formula (7-4). In the formula (7-4), you can estimate the traffic first to get the value on the left of the formula,
and then calculate the actual traffic according to the Erlang formula.
2011-08-10
Page 49 of 50
List of references: Wang Mingmin, WCDMA RNP Technology Research on Special Topics -- High-Level Design Specifications for Link budget Tool, internal document, 2002-08 AirCom International Limited 2001, UMTS Applied Planning for Experienced Engineers Harri Holma and Antti Toskala,WCDMA for UMTS, JOHN WILEY & Sons, LTD., 2000 Jaana Laiho, Achim Wacker, Tomas Novosad, Radio Network Planning and Optimization for UMTS, JOHN WILEY & Sons, LTD., 2002 Wang Mingmin, WCDMA RNP Technology Research on Special Topics Calculation of Downlink Interference Headroom in Link Budget, internal document, 2002-05. Miao Jiashu, WCDMA RNP Radio Network Dimensioning Guide, internal document, 2002-09 Wu
Dimensioning, internal document, 2003-11 Wu hong, WCDMA RNP CE Dimensioning Guide, internal document, 2003-07 3GPP TS 25.427 V3.10.0 (2002-12) Clint Smith, Daniel Collins, 3G WIRELESS NETWORKS, McGraw-Hill Win Shengyi, WCDMA RNC Transport Network Layer Traffic Configuration Scheme, 2003-12 Theodore S. Rappaport Radio Communication Principles and Applications, Electronic Industry Publishing Company, 1999.
2011-08-10
hong, WCDMA RNP Low-level Design Specifications for Radio Network
Page 50 of 50

WCDMA RNP Radio Network Dimension Ing Huawei

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WCDMA RNP Radio Network Dimension Ing Huawei

Uploaded by

Copyright:

Available Formats

Document code Target readers Edited by

Product name Product version Document version V100R001 WCDMA RNP

WCDMA RNP Radio Network Dimensioning Principles

Prepared by Reviewed by Reviewed by Granted by

Date Date Date Date

Huawei Technologies Co., Ltd.

WCDMA RNP Radio Network Dimensioning Principle

For internal use only

All rights reserved.

WCDMA RNP Radio Network Dimensioning Principle

For internal use only

All rights reserved.

WCDMA RNP Radio Network Dimensioning Principle

For internal use only

All rights reserved.

WCDMA RNP Radio Network Dimensioning Principle

For internal use only

All rights reserved.

AMR A M B ER CCH CE CS DCH DL EIRP P oS

HT odeB PS RA RNP SHO TCH TMA TU UE UL UMTS WCDMA

628 F' 26 )2 5 2D ' 0 71 1 0 61 25 ) @ 8(9 (8 2D 0 @' 02D )1 ( 66280'9

71 1 0 61 25 ) @ 8(9 (8 71 1 0 61 25 ) 4' 03 21 0 )('

'2 ' C 2 ' 2@(G 1 0

Abb evi i Access

All rights reserved.

WCDMA Radio Network Dimensioning Principle

or internal use only

: The capacity dimensioning principles are given, including the uplink

: The dimensioning principle and dimensioning process of NodeB Iub

WCDMA Radio Network Dimensioning Principle

or internal use only

budget Tool [ ] . It is not further described here.

imensi ning Princi le

Brief Introduction to Cell Capacity Dimensioning

services affecting the PS service throughput.

All rights reserved.

The Kaufman Robert algorithm is used to meet different

WCDMA Radio Network Dimensioning Principle

or internal use only

performed with ErlangC, which can embody the

WCDMA Radio Network Dimensioning Principle

or internal use only

The capacity of common channel is under research.

3.2 Dimensioning of Cell Uplink Capacity of Mixed Services

provides the result, as

Note: (i) In the above two formulae, rate,

refers to the neighboring cell interference factor,

is the bit rate of service

spcifies the activity factor of the sevice

users are connected simultaneously in the same cell.

(ii) In the formula (3-2), sectors of the BS.

specifies the sectorization gain, and

refers to the number of

All rights reserved.

WCDMA Radio Network Dimensioning Principle

or internal use only

Calculating Single User Load of Each Service in Cell

(2) Service j , with soft handover: uplink load of a single user

(3) Service j , all users: uplink load of a single user

WCDMA Radio Network Dimensioning Principle

or internal use only

(2) (3) (4)

R j : Bearer rate of service j . V j : Activity factor of service j .

P TotalThrou ghputRate ! v (1 Neighborin gCellInter ferenceFac tor ) Q RvV

Pr[CallDelay " t t arg et ] ! 1 Pr[CallDelay P p0 Q ! P m!1 Q m

CSServiceCellLoad ! TotalCellUplinkLoad SServiceCellLoad

c G( c ) ! a k bk G( c bk ) . Where, K refers to the total CS bearer service in the cell, ak

CL j ! AverageMaxi u CouplingLoss fCe llDownlinkWorked ut yMeans fLink udget 10lg(7 / 30)

P TotalUserN umber v Throughput OfSingleUs erInBusyHo urs v (1 SHO ) ! Q 3600 v R v V

P ! rafficOfS ingle serI n usyHours v otalNu be rOf sersSu pported v 1 SHO Q