WCDMA CE Dimensioning

UMTS CE Dimensioning Principles and Case Studies Internal Open
RAN10~RAN14
UMTS CE Dimensioning Principles and Case

WCDMA CE Dimensioning Principle and Procedure
Studies
RAN10~RAN14
Huawei Technologies Co., Ltd.

All rights reserved
3/6/2013 All rights reserved Page 1 , Total21

RAN10~RAN14
Table of Contents
1 Introduction ............................................................................................................................... 4
2 CE Dimensioning for Erlang Services ...................................................................................... 5
2.1 CEs for R99 Traffic Channel .............................................................................................. 5
2.2 CE factors for CS/VOIP over HSPA services .................................................................... 6
2.3 Peak CEs for Erlang service CE Erlang _ Peak ....................................................................... 7
2.4 Average CEs for Erlang service CE Erlang _ Average ............................................................... 8
2.5 Case Study ......................................................................................................................... 8
3 CE Dimensioning for PS Services ........................................................................................... 9
3.1 CEs for PS Services CE PS _ Average ..................................................................................... 9
3.2 Case Study ....................................................................................................................... 10
4 CE Dimensioning for HSDPA ................................................................................................. 10
4.1 CEs for HSDPA in downlink CEHSDPA _ DL ........................................................................ 10
4.2 CEs for HSDPA in uplink CE HSDPA _ AUL .......................................................................... 11
4.4 Case Study ....................................................................................................................... 13
5 CE Dimensioning for HSUPA ................................................................................................. 14
5.1 CEs for HSUPA in downlink CE HSUPA _ ADL ...................................................................... 14
5.2 CEs for HSUPA in uplink CE HSUPA _ UL ............................................................................ 14
5.3 Case Study ....................................................................................................................... 17
6 Impact on CE from new features in RAN11~RAN14 ............................................................. 18
7 Final Total CEs for All the Services ....................................................................................... 19

RAN10~RAN14
CE Dimensioning Principles and Case Studies

Abstract
This article presents the Channel Element (CE) dimensioning principles and procedures as well
as corresponding case studies.
The principles and values showed in this document are suitable for versions from RAN10
to RAN14.

RAN10~RAN14
1 Introduction
Channel Element (CE) unit is defined as the base band resources required in the NodeB to
WCDMA
provide one voiceCEchannel
Dimensioning Principle
traffic, and Procedure
also including related control plane signaling, compressed
mode, transmit diversity and softer handover.
Huawei CE dimensioning principles have the following general features:
(1) CE license is pooled in one NodeB
(2) No extra CE resource needed for CCH, already reserved by Huawei
(3) No extra CE resource needed for TX diversity
(4) No extra CE resource needed for compressed mode
(5) No extra CE resource needed for softer handover (V2 NodeB)
(6) CE resources for R99 and HSDPA services are designed separately and have no impact
on each other
(7) No extra CE resource needed for HSDPA service traffic channel
And since RAN10 version on, SRB over HSDPA and SRB over HSUPA features are available. If
SRB over HSDPA feature is adopted in the network, SRB of each HSDPA user in downlink
wouldnt consume any CE any more, the same for HSUPA.
The general procedure of CE dimensioning is shown in the following figure:
Figure1 CE dimensioning procedure
[Note]:
RAN10~RAN14
ERL services (Erlang services) in Figure1 include R99 CS services and CS/VOIP over HSPA.
2 CE WCDMA
Dimensioning for Erlang
CE Dimensioning Principle Services
and Procedure
Erlang services here include two parts:

1) R99 CS domain services;
2) CS/VOIP over HSPA services;
2.1 CEs for R99 Traffic Channel
The CE consumption principle for R99 services bearer are detailed in the table below. This
principle wouldnt change with different RAN versions.
Table1 CE Factors of R99 Services of 2-way Receive Diversity
Channel Elements Mapping for R99 Bearers

(2-RX)
SF UL/DL Bearer Uplink Downlink
SF64 / SF128 AMR12.2k 1 1
SF64 / SF128 AMR-WB 2K~19.85K 1 1

SF32 / SF64 AMR-WB 23.05K~23.85K 1.5 1
SF32 / SF64 CS28.8k, CS32K 1.5 1
SF16 / SF32 CS56K, CS57.6K 3 2
SF16 / SF32 CS64k 3 2
SF64 / SF128 PS8k 1 1
SF64 / SF128 PS16k 1 1
SF32 / SF64 PS32k 1.5 1
SF16 / SF32 PS64k 3 2
SF8 / SF16 PS128k 5 4
SF8 / SF16 PS144k 5 4
SF4 / SF8 PS256k 10 8
SF4 / SF8 PS384k 10 8
[Note]:
1. CE factors for each R99 service bearer include CE for traffic and 3.4K DCCH. No separate CE consumption is
required for signaling associated.
2. Transmit diversity does not require additional CE.

RAN10~RAN14
For the CE factors with 4-RX diversity, the CE factors for R99 service bearers are different only in
uplink from 2-RX diversity, typical bearers are shown below:
Table2 Uplink CE Factors of R99 Services of 4-RX diversity
UL CE factor
R99 Bearers
(4-RX diversity)
AMR12.2k 2
CS64K 4
PS64K 4
PS128K 8
PS384K 16
2.2 CE factors for CS/VOIP over HSPA services
CS/VOIP over HSPA is introduced since RAN11. CE consumption of these two kinds of services
needs to be considered together with R99 CS services to guarantee the user experiences. CE
factors of CS/VOIP over HSPA services are shown in following table.
Table3 CE Factors of CS/VOIP over HSPA services
Service Types DL/UL RAN11.0 CE RAN12.0-RAN14.0 CE

consumption consumption
CS over HSPA 10ms Downlink 0 CE 0 CE
Uplink SF32: 1 CE (V2 NodeB) SF32: 1 CE (V2/V1 NodeB)
SF32: 1.5CE (V1 NodeB)
VOIP over HSPA Downlink 0 CE 0 CE
10ms Uplink SF16: 2 CE (V2 NodeB) SF32: 1 CE (V2/V1 NodeB)
SF16: 3 CE (V1 NodeB)
VOIP/CS over HSPA Downlink N/A 0 CE
2ms Uplink SF8: 1 CE (V2/V1 NodeB);
N/A
[Important Note]:
Downlink CS over HSPA and VOIP over HSPA CE consumption in above table is based on SRB over
HSDPA feature, if this feature is not available, then 1 extra CE consumption is needed for each CS/VOIP
over HSPA user in downlink.
Uplink CS over HSPA and VOIP over HSPA CE consumption in above table is based on SRB over HSUPA
feature, if this feature is not available, then 1 extra CE consumption is needed for each CS/VOIP over HSPA
user in uplink.

RAN10~RAN14
2.3 Peak CEs for Erlang service CE Erlang _ Peak
Peak CEs for Erlang services is dimensioned to evaluate peak CE demand for the real-time CS
WCDMA
services with strictCE Dimensioning
GoS Principle
requirements andand Procedure
CS/VOIP over HSPA.
Multidimensional ErlangB algorithm is adopted here to calculate the number of CE needed at
Busy Hour for all Erlang services with respective GoS (grade of service) requirements.
Traditional single service (voice) adopts ErlangB formula. With only one service it is sufficient to
find the peak traffic of a given GoS.
In fact, each radio bearer of various services has different GoS requirement. Multidimensional
ErlangB algorithm calculate the blocking probability for multiple services when accessing the
system with limited resources, which is a way to model multi-service systems where resources
are shared by all services with different GoS requirements. Multidimensional ErlangB algorithm
model is shown in following figure.
Calls
arrival Fixed CE resources
multiservice
Calls
completion
Blocked
calls
Figure2 Multidimensional Erlang B Model
Multidimensional ErlangB model makes it possible to utilize the CE resources effectively. The
resource is shared by all services in multidimensional ErlangB model, which makes use of the fact
that the probability of simultaneous bursts from many independent traffic sources is very small.
The figure below shows the gain when resources are shared compared to resources are
pre-partitioned.

RAN10~RAN14
ErlangB - Partitioning Resources Multidimensional ErlangB - Resources shared
Low Utilization of resources High Utilization of resources
Figure3 Partitioning Resources vs. Resources Shared
In peak CE dimensioning, Multidimensional ErlangB algorithm can calculate traffic, blocking

probability and the peak number of CEs needed for Erlang services, if any two of them are known,
the third one can be deduced.
2.4 Average CEs for Erlang service CE Erlang _ Average
Average CEs for Erlang services is dimensioned to evaluate average CE demand. The following
formula is adopted:
CE Erlang _ Average CSTrafficP erNodeBi (1 SH Overhead) CEFactori

i
Where,
SH Overhead is the soft handover ratio.
CSTrafficP erNodeBi is the traffic for each kind of Elrang services (R99 CS services and
VOIP/CS over HSPA) per NodeB.
2.5 Case Study
1. Assumptions
Subscriber number per NodeB: 2000
Voice traffic per subscriber: 0.02Erl
CS over HSPA traffic per subscriber: 0.001Erl
Soft Handover Overhead: 20%
GoS requirement of voice: 2%
GoS requirement of VP: 2%
2. Calculation
1 Peak CE Dimension
RAN10~RAN14
Traffic of voice: 0.02*2000*(1+20%) = 48 Erl
Traffic of CS over HSPA: 0.001*2000*(1+20%) = 2.4 Erl
Voice peak CE demand are 59 CEs in uplink and 59 CEs in downlink respectively.
CS over HSPA
WCDMA peak CE demands
CE Dimensioning areProcedure
Principle and 14CEs ((1+1)*7=14) in uplink and 7(1*7=7) CEs in
downlink respectively.
Considering the CE resource share between voice and CS over HSPA services, by
multidimensional ErlangB algorithm, the final total peak CEs demand are 68 CEs in uplink
and 61 CEs in downlink.
2 Average CE Dimension
Voice average CE demands are 2000*0.02*(1+20%)*1=48 CEs in uplink and 48 CEs in
CS over HSPA average CE demands are 2000*0.001*(1+20%)*(1+1) = 5 CEs in uplink
and 2000*0.001*(1+20%)*1= 3 CEs in downlink respectively.
The final total average CEs demand are 48+5=53 CEs in uplink and 48+3=51 CEs in
3 Final CE Dimension
Since the peak values are bigger than the average ones, so the final CE consumption is
68 in uplink and 61 in downlink.
3 CE Dimensioning for PS Services
3.1 CEs for PS Services CE PS _ Average
The method to calculate the CE consumed by PS services is similar to that to calculate the
average CE consumed by CS services.
CE PS _ Average PSTrafficp erNodeBi (1 SH Overhead) 1Rburst_ i ) 1Rretransmission ) CEFactor i
i
Wherein
ThroughputPerNodeBi
PSTrafficp erNodeBi
Ri i 3600
ThroughputPerNodeBi ( kbit ): the busy hour throughput per NodeB for service i .
i : channel element utilization rate for service i.
Ri kbps: Bearer bit rate for service i .
Rb u r _s it is the burst ratio of service i .

RAN10~RAN14
Rretransmission is the re-transmission ratio of service i .
SH Overhead is the soft handover ratio which considers the CE consumption caused by
the soft handover.
3.2 Case Study
Assumption:
UL PS64k throughput per user: 50kbit
DL PS64k throughput per user: 100kbit
DL PS128k throughput per user: 80kbit
PS traffic burst: 20%
Retransmission rate of R99 PS services: 5%
Channel element utilization rate: 0.7
Then,
2000 * 50
CE for UL PS64k: * 3 * (1 20%) * (1 20%) * (1 5%) 3 CEs
64 * 0.7 * 3600
2000 *100
CE for DL PS64k: * 2 * (1 20%) * (1 20%) * (1 5%) 4 CEs
64 * 0.7 * 3600
2000 * 80
CE for DL PS128k: * 4 * (1 20%) * (1 20%) * (1 5%) 3 CEs
128 * 0.7 * 3600
Total CE for UL PS services is CEPS _ UL = 3 CEs
And total CE for DL PS services is CE PS _ DL =4+3= 7 CEs
4 CE Dimensioning for HSDPA
4.1 CEs for HSDPA in downlink CEHSDPA_ DL
In downlink, when HSDPA users access the network, both the traffic and signaling are setup.
Since Huawei designed the dedicated chipset for HSDPA traffic processing, so the downlink
HSDPA traffic wouldnt consume any CE resources any more which gives no impact on R99
baseband resources. So does HS-SCCH channel of HSDPA.
Thus the CE in downlink for HSDPA is only consumed by signaling of HSDPA services.
SRB with 3.4k signaling for each HSDPA users have two options: 1) Bear on DCH; 2) Bear on
HSDPA (Only if with SRB over HSDPA feature).

RAN10~RAN14
If SRB is borne on DCH, each HSDPA user would consume ONE CE, therefore CE resources
consumed by HSDPA services is equal to the number of simultaneously connected HSDPA users,
which can be calculated according to the following formula:
WCDMA CE Dimensioning PrincipleThroughput PerNodeB HSDPA (kbit)
and Procedure
CE HSDPA _ DL LinksHSDPA *1 * (1 Pre ) * (1 Rburst ) *1
AverageOnlineThroughputPerUserHSDPA (kbps) * 3600
Where,
AverageOnlineThroughputPerUserHSDPA (kbps) means the average HSDPA user
throughput of online HSDPA users;
Pre is the retransmission ratio;
Rburst is the service burst ratio of HSDPA;
If SRB is borne on HSDPA, which means SRB over HSDPA feature is activated. In this case,
downlink signaling of HSDPA wouldnt consume any CE resources.
Note
SRB over HSDPA feature is supported since RAN10.0.
SRB over HSDPA feature is optional feature and not cost free.
SRB over HSDPA feature is applicable only both supported by RAN and terminal. If any of them doesnt
support this feature, then SRB of each HSDPA user still consumes one CE.
4.2 CEs for HSDPA in uplink CE HSDPA _ AUL
The Associated Channel (refer to A-DCH in following contents) of HSDPA in uplink including:
HS-DPCCH and DCH. HS-DPCCH is for the CQI, ACK/NACK feedback in uplink. DCH is for
signaling, TCP/RLC ACK feedback and the associated traffic in uplink for HSDPA.
CEs for HS-DPCCH are already reserved in the system. Only DCH here would consume CE
resources, which can be calculated by the following formula:
CE HSDPA _ AUL {LinksHSDPA * CEFactor A DCH ( LinksOnlineHSDPA LinksHSDPA ) *1} * (1 SHOoverhead )
Where,
LinksHSDPA means the simultaneously online HSDPA users which are active ( with data
transferring).
LinksOnlineHSDPA means the simultaneously online HSDPA users( active and inactive).
The reason why we differentiate the LinksHSDPA and LinksOnlineHSDPA is because in the real
network, there are a lot of HSDPA users who are online without transferring data in one period of

RAN10~RAN14
time. These users follow the different CE consumption principle compare to the users with data
transferring.
So the final CE consumed

WCDMA by the Principle
CE Dimensioning HSDPA andA-DCH can be described as following:
Procedure
ThroughputPerNodeB HSDPA (kbit )
CEHSDPA _ AUL { * CEFactor A DCH
AverageThroughputPer UserHSDPA (kbps) * 3600
ThroughputPerNodeB HSDPA (kbit ) ThroughputPerNodeB HSDPA (kbit )
( ) * CEInactivUser } * (1 Pre ) * (1 Rburst)
AverageOnlineThroughputPerUserHSDPA (kbps) * 3600 AverageThroughputPer UserHSDPA (kbps) * 3600
* (1 SHOoverhead )
Where,
Pre is the retransmission of HSDPA service
Rburst is the burst ratio of HSDPA service.

SHOoverhead is the soft handover ratio of A-DCH of HSDPA.
AverageThroughputPer UserHSDPA (kbps) means the average HSDPA data transferring
throughput, normally 400~600Kbps is suggested due to HUAWEIs experiences.
AverageOnlineThroughputPerUserHSDPA (kbps) means the average HSDPA online throughput,
normally 30~50Kbps is suggested due to HUAWEIs experiences.
ThroughputPerNodeBHSDPA (kbit)
So gives the all the simultaneously
AverageOnlineThroughputPerUserHSDPA (kbps) * 3600
ThroughputPerNodeB HSDPA (kbit )
online HSDPA users number, means the
AverageThroughputPer UserHSDPA (kbps) * 3600
simultaneously online HSDPA users active.
CEInactivUser is the CE consumed by the online inactive users, this value is different in different RAN
version, for the RAN version since RAN11(including RAN11), this value is 1.
CEFactor A DCH is the CE consumed by each A-DCH. The value of CEFactor A DCH is
influenced by the following two factors:
1) Data rate of A-DCH;
2) A-DCH bears on R99 PS or HSUPA. If the data rate of A-DCH is 64Kbps and borne on R99
CEFactor A DCH
PS, so the is 3.
Data rate of A-DCH has a close relation with the HSDPA data throughput, can be found in the
mapping table as following:
Table4 Uplink A-DCH throughput VS. HSDPA service throughput

RAN10~RAN14
4.4 Case Study
Assumption:
Traffic model of HSDPA: 3600kbit
Requirement of average data throughput per user: 400Kbps
Requirement of average online throughput per user: 50Kbps
HSDPA traffic burst: 0
HSDPA retransmission rate: 10%
SRB over HSDPA feature is off, A-DCH of HSDPA bears on R99 PS.
Soft handover ratio of R99/HSUPA services is 20%.
No MIMO or DC-HSDPA is involved.
Then,
CE in downlink:
2000 * 3600
CE HSDPA _ DL LinksHSDPA *1 * (1 0%) * (1 10%) *1 = 44 CEs
3600 * 50
CE in uplink:
CEFactor A DCH =1.5 CE (400Kbps HSDPA throughput mapping to 32Kbps A-DCH, which
consumes 1.5 CE in R99 PS)
CE HSDPA _ AUL LinksHSDPA * CEFactor A DCH ( LinksOnlineHSDPA LinksHSDPA ) =
2000 * 3600 2000 * 3600 2000 * 3600

{ *1.5 ( ) *1} * (1 0%) * (1 10%) * (1 20%)
3600 * 400 3600 * 50 3600 * 400
= 56 CE

RAN10~RAN14
5 CE Dimensioning for HSUPA
5.1 CEs for HSUPA in downlink CE HSUPA _ ADL

In downlink, there are two kinds of HSUPA channels:

1) Common channel: E-HICH,E-AGCH,E-RGCH
2) A-DCH of HSUPA
CE needed for Common channel are already reserved in the system of Huawei, so no additional
CE will be consumed any more.
A-DCH of HSUPA is borne on HSDPA in default parameter configuration, so this part will be also
handled by the dedicated chipset of HSDPA. Thus no CE resources are needed for A-DCH of
HSUPA in downlink.
5.2 CEs for HSUPA in uplink CE HSUPA _ UL
For the uplink of HSUPA, there are two parts which would consume uplink CE:
Signalling of HSUPA users (SRB)
Traffic of HSUPA users
The total CE consumed for HSUPA in uplink can be calculated by the following formula:
CEHSUPA _ UL CESRB _ UL CETraffic_ UL

Where,
CE SRB _ UL is the CE consumed by the SRB of HSUPA users
CETraffic_UL is the CE consumed by the traffic of HSUPA services
CE of SRB of HSUPA users: CE SRB _ UL
For the SRB with 3.4k signaling for each HSUPA users have two options: 1) Bear on DCH; 2)
Bear on HSUPA (with SRB over HSUPA feature).
If SRB is borne on DCH, each HSUPA user would consume ONE additional CE for SRB,
therefore CE resources consumed by SRB of HSUPA users is equal to the number of
simultaneously connected HSUPA users, which can be calculated according to the following
formula:
CE SRB _ UL LinksHSUPA *1

RAN10~RAN14
ThroughputPerNodeB HSUPA (kbit)
* (1 Pre ) * (1 Rburst) * (1 SH Overhead) *1
AverageOnlineThroughputPerUserHSUPA (kbps) * 3600
If SRB is borne
WCDMA onCE
HSUPA, no additional
Dimensioning CE Procedure
Principle and is consumed by the SRB of HSUPA services.
CE of traffic of HSUPA services: CETraffic_ UL
For the CE consumed by the HSUPA traffic, can be calculated by the following formula:
ThroughputPerNodeB HSUPA (kbit )
CETraffic _ UL { * CEFactor HSUPA
AverageThroughputPer UserHSUPA (kbps) * 3600
ThroughputPerNodeB HSUPA (kbit ) ThroughputPerNodeB HSUPA (kbit )
( ) * CE InactiveUser }
AverageOnlineThroughputPerUserHSUPA (kbps) * 3600 AverageThroughputPer UserHSUPA (kbps) * 3600
* (1 Pre ) * (1 Rburst) * (1 SHOoverhead )
Where,
Pre is the retransmission of HSUPA service
Rburst is the burst ratio of HSUPA service.

means the simultaneously online HSUPA
AverageThroughputPer UserHSUPA (kbps) * 3600
users number with data transferring.
means the simultaneously online
AverageOnlineThroughputPerUserHSUPA (kbps) * 3600
HSUPA users number.
CEInactivUser is the CE consumed by the online inactive users, this value is different in different RAN
version, for the RAN version since RAN11(including RAN11), this value is 1.
CEFactorHSUPA can be found in the following table:
Table5 CE mapping of HSUPA for NodeB3900 in RAN10~RAN14 with 2RX
CE factor MAC-e Bit-rate (Kbps)

SF
RAN10.0 RAN11.0 RAN12.0-14.0 Cat 5 10ms Cat 6 2ms Cat 7-9 2ms
SF32 1.5 1 1 37.2
SF16 3 2 2 70.8
SF8 5 4 4 154.8
SF4 10 8 8 711 699 699
2*SF4 20 16 16 1448.4 1371 1371
2*SF2 32 32 32 1995 2883 2883
2*SF2 +
48 48 48
2*SF4 5739 4059
Not Not
2*M2+2*M4 64
support support 699 11498

RAN10~RAN14
We can see form the above table that SF4 is the critical point, before this 10ms is adopted; after
this 2ms is preferred (efficiency is higher).
Also it is noted
WCDMA that
CEthroughput in Principle
Dimensioning the above andtable is at MAC-e layer. But normally the throughput
Procedure
input is at RLC layer, so the convert of throughput between RLC and MAC-e is needed.
If RLC layer throughput is known, following formulas could be used to calculate the MAC-e
throughput:
Rate RLC Head MAC e

Rate MAC e (1 SBLER )
PRLC TTI
Where,
Parameters Definition Unit

RateMAC-e Throughput in MAC-e kbps
RateRLC Throughput in RLC kbps
Efficiency in RLC, normally 320/336 is
PRLC
suggested
Overhead of MAC-e, 18bit is
HeadMAC-e bit
suggested
TTI TTI ms
SBLER Normally 10% is suggested
So it is very easy to calculate the MAC-e throughput with RLC throughput, shown below for your
reference.
Table6 CE mapping of HSUPA for NodeB3900 in RAN10~RAN14 with 2RX with RLC throughput
SBLER=10%
MAC-e Bit-rate (Kbps) RLC Bit-rate

CE factor (Kbps)
RAN12- Cat 5 Cat 6 Cat 7-9 Cat 5 Cat 6 Cat 7-9
SF RAN10 RAN11 14 10ms 2ms 2ms 10ms 2ms 2ms
SF32 1.5 1 1 37.2 30
SF16 3 2 2 70.8 59
SF8 5 4 4 154.8 131
SF4 10 8 8 711 699 699 608 591 591
2*SF4 20 16 16 1448.4 1371 1371 1240 1167 1167
2*SF2 32 32 32 1995 2883 2883 1708 2463 2463
2*SF2 +
2*SF4 48 48 48 5739 4059 4911 3471
2*M2+2* Not Not
M4 support support 64 699 11498 9847
If the RLC throughput you need to input just match the RLC throughput in the above table, you
can just take the value in above table. If not, then linear interpolation () is suggested to
get the MAC-e throughput to calculate the real CE consumption.

RAN10~RAN14
For example:
If the RLC throughput is 1167Kbps, which just matches the value in the table, so the MAC-e
throughput is 1371Kbps which needs 16 CE in RAN12.0-14.0.
If the RLCWCDMA
throughput is 500Kbps,Principle
CE Dimensioning no value andmatched,
Procedurefrom the calculation we can get the MAC-e
throughput with 10ms TTI is 585.3Kbps, which is between SF8(MAC-e throughput is 154.8) and
SF4(MAC-e throughput is711).
If the version is RAN12, so the CE consumption for RLC 500kbps is calculated as below:
(8 4) * (585.3 154.8)
4 =7.10 CE
711 154.8
Note:
HSUPA online with no data transferring user consumes 1 CE or TRB since RAN11.0 version, but for version
RAN10/RAN6.1, one RLC PDU CE 1.5CE is needed for 10ms TTI, 8 CE is needed for 2ms TTI is needed for
HSUPA users TRB even when HSUPA user is online but no data is transferring.
5.3 Case Study
Assumption:
Traffic model of HSUPA: 500kbit
Requirement of average throughput per user: 128kbps
Requirement of average online throughput per user: 20Kbps
Burst ratio of HSUPA is 0%, re-transmission rate is 11%.
SRB over HSUPA feature is off.
SRB over HSDPA feature is adopted.
RAN version: RAN11.0, 2ms TTI is adopted.
Then,
1. CEs in downlink
HSUPA is borne on HSDPA, No CE consumed.
2. CEs in uplink
CE for SRB
2000 * 500
LinksHSUPA * (1 20%) * (1 11%) *1 = 19 CE
20 * 3600
CE for traffic
MAC-e throughput for 128Kbps is 151Kbps, which consumes 3.9 CE

RAN10~RAN14
CETraffic _ UL = { 2000 * 500 * 3.9 ( 2000 * 500 2000 * 500 ) * 1} * (1 20%) * (1 11%) 28 CE
128 * 3600 20 * 3600 128 * 3600
Total CE in uplink
19+28
WCDMA CE= Dimensioning
47 CE Principle and Procedure
6 Impact on CE from new features in RAN11~RAN14
CE consumption principles for all new features in RAN11~RAN14 versions are detailed in
following table.
Table7 CE Consumption Principles for new features in RAN11~RAN14
Service Types DL/UL RAN11.0 CE RAN12.0/13.0 RAN14.0 CE

consumption CE consumption
consumption
CS over HSPA 10ms Downlink 0 CE 0 CE 0 CE
Uplink SF32: 1 CE (V2 NodeB) SF32: 1 CE SF32: 1 CE
SF32: 1.5CE (V1 NodeB) (V2/V1 NodeB) (V2/V1
NodeB)
VOIP over HSPA Downlink 0 CE 0 CE 0 CE
10ms Uplink SF16: 2 CE (V2 NodeB) SF32: 1 CE SF32: 1 CE
SF16: 3 CE (V1 NodeB) (V2/V1 NodeB) (V2/V1
NodeB)
VOIP/CS over HSPA Downlink N/A 0 CE 0 CE
2ms Uplink SF8: 1 CE SF8: 1 CE
N/A (V2/V1 (V2/V1
NodeB); NodeB);
Downlink 0 CE 0 CE 0 CE
64QAM
Uplink 0 CE 0 CE 0 CE
MIMO Downlink 0 CE 0 CE 0 CE
Uplink One user need 1 0 CE 0 CE
additional CE for
HS-DPCCH
DC-HSDPA/DC-MIMO Downlink N/A 0 CE 0 CE
Uplink N/A 0 CE 0 CE
Downlink N/A N/A 0 CE
DC-HSUPA Uplink Double of
N/A N/A
HSUPA
[Note]:
EULP / EULPd / EBBI / EBBC / EBBCd cards are for V1 NodeB.
WBBPb / WBBPd cards are for V2 NodeB.
Downlink CS over HSPA and VOIP over HSPA CE consumption in above table is based on SRB over
HSDPA feature, if this feature is not available, then 1 extra CE consumption is needed for each CS/VOIP
over HSPA user in downlink.
Uplink CS over HSPA and VOIP over HSPA CE consumption in above table is based on SRB over HSUPA
feature, if this feature is not available, then 1 extra CE consumption is needed for each CS/VOIP over HSPA
user in uplink.

RAN10~RAN14
Well take RAN11.0 for example to explain the table above.
1. 64QAM and MIMO in RAN11.0

Since RAN 11 version, downlink 2*2MIMO and 64QAM feature are available.
64QAM feature has no impact on HSDPA CE consumption both in uplink and downlink.
MIMO also has no impact on CE consumption in downlink. But in uplink, one additional
HS-DPCCH is needed for each MIMO users, which introduce one additional uplink CE
consumption.
2. CS over HSPA in RAN11.0
For CS over HSPA services in downlink, the CE principles are totally the same to HSDPA. Which
means no CE consumption in downlink with SRB over HSDPA feature, but 1 CE is needed for
each CS over HSPA user if SRB over HSDPA feature is not available.
For CS over HSPA services in uplink, CE consumption is different in different NodeB platform, for
V2 platform NodeB 1 CE is consumed for each CS over HSPA service.
7 Final Total CEs for All the Services

CE resources assignment algorithm between CS and PS within NodeB is clearly demonstrated in
Figure4.
Total CE
CE Resource
CE Peak for CS
CE occupied by PS
CE Average for CS
CE occupied by CS
Time
Figure4 CE Shared between PS and CS Services

Therefore, for the CE dimensioning in RAN10, the total CE dimension in uplink and downlink can
be summarized respectively as the following formulas:
CEUL _ Total Max(CE Erlang _ Peak _ UL , CE Erlang _ Average_ UL CE PS _ Average_ UL CE HSDPA _ AUL CE HSUPA _ UL )
RAN10~RAN14
CE DL _ Total Max(CE Erlang _ Peak _ DL , CE Erlang _ Average_ DL CE PS _ Average_ DL CE HSDPA _ DL CE HSUPA _ ADL )
For the CE dimensioning in RAN11~RAN14, the total CE dimension in uplink and downlink can be
summarized respectively
WCDMA as the following
CE Dimensioning formulas:
Principle and Procedure
CEUL _ Total Max(CE Erlang _ Peak _ UL , CE Erlang _ Average _ UL CE PS _ Average _ UL CE HSDPA _ AUL CE HSUPA _ UL CE MIMO CE DC / DC MIMO )
CE DL _ Total Max(CE Erlang _ Peak _ DL , CE Erlang _ Average_ DL CE PS _ Average_ DL CE HSDPA _ DL CE HSUPA _ ADL )

RAN10~RAN14

WCDMA CE Dimensioning

Hochgeladen von

Dokumentinformationen

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

WCDMA CE Dimensioning

Hochgeladen von

Copyright:

Verfügbare Formate

UMTS CE Dimensioning Principles and Case Studies Internal Open

UMTS CE Dimensioning Principles and Case

Huawei Technologies Co., Ltd.

3/6/2013 All rights reserved Page 1 , Total21

3/6/2013 All rights reserved Page 2 , Total21

WCDMA CE Dimensioning Principle and Procedure

3/6/2013 All rights reserved Page 3 , Total21

Huawei CE dimensioning principles have the following general features:

(1) CE license is pooled in one NodeB

(2) No extra CE resource needed for CCH, already reserved by Huawei

(3) No extra CE resource needed for TX diversity

(4) No extra CE resource needed for compressed mode

(5) No extra CE resource needed for softer handover (V2 NodeB)

(7) No extra CE resource needed for HSDPA service traffic channel

The general procedure of CE dimensioning is shown in the following figure:

Figure1 CE dimensioning procedure

Erlang services here include two parts:

2.1 CEs for R99 Traffic Channel

Table1 CE Factors of R99 Services of 2-way Receive Diversity

Channel Elements Mapping for R99 Bearers

SF64 / SF128 AMR12.2k 1 1

SF64 / SF128 AMR-WB 2K~19.85K 1 1

2. Transmit diversity does not require additional CE.

3/6/2013 All rights reserved Page 5 , Total21

2.2 CE factors for CS/VOIP over HSPA services

Table3 CE Factors of CS/VOIP over HSPA services

Service Types DL/UL RAN11.0 CE RAN12.0-RAN14.0 CE

3/6/2013 All rights reserved Page 6 , Total21

Figure2 Multidimensional Erlang B Model

3/6/2013 All rights reserved Page 7 , Total21

WCDMA CE Dimensioning Principle and Procedure

Low Utilization of resources High Utilization of resources

Figure3 Partitioning Resources vs. Resources Shared

In peak CE dimensioning, Multidimensional ErlangB algorithm can calculate traffic, blocking

2.4 Average CEs for Erlang service CE Erlang _ Average

CE Erlang _ Average CSTrafficP erNodeBi (1 SH Overhead) CEFactori

2.5 Case Study

3 CE Dimensioning for PS Services

3.1 CEs for PS Services CE PS _ Average

Rb u r _s it is the burst ratio of service i .

3/6/2013 All rights reserved Page 9 , Total21

3.2 Case Study

And total CE for DL PS services is CE PS _ DL =4+3= 7 CEs

4 CE Dimensioning for HSDPA

4.1 CEs for HSDPA in downlink CEHSDPA_ DL

3/6/2013 All rights reserved Page 10 , Total21

Rburst is the service burst ratio of HSDPA;

4.2 CEs for HSDPA in uplink CE HSDPA _ AUL

3/6/2013 All rights reserved Page 11 , Total21

So the final CE consumed

Rburst is the burst ratio of HSDPA service.

3/6/2013 All rights reserved Page 12 , Total21

WCDMA CE Dimensioning Principle and Procedure

4.4 Case Study

2000 * 3600 2000 * 3600 2000 * 3600

3/6/2013 All rights reserved Page 13 , Total21

5.1 CEs for HSUPA in downlink CE HSUPA _ ADL

In downlink, there are two kinds of HSUPA channels:

5.2 CEs for HSUPA in uplink CE HSUPA _ UL

CEHSUPA _ UL CESRB _ UL CETraffic_ UL

CETraffic_UL is the CE consumed by the traffic of HSUPA services

CE of SRB of HSUPA users: CE SRB _ UL

3/6/2013 All rights reserved Page 14 , Total21

CE of traffic of HSUPA services: CETraffic_ UL