CE Dimension

Error! Reference source not found.
WCDMA CE Dimensioning Principle and

Procedure
Internal Open

10/12/2014 All rights reserved Page 1 , Total19

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

Error! Reference source not found.WCDMA CE Dimensioning Principle and
Procedure
Internal Open


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 RAN13.

Procedure
Internal Open


1 Introduction
Channel Element (CE) unit is defined as the base band resources required in the NodeB to
provide one voice channel traffic, 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]:

Procedure
Internal Open


ERL services (Erlang services) in Figure1 include R99 CS services and CS/VOIP over HSPA.

2 CE Dimensioning for Erlang Services
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.

Procedure
Internal Open


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
R99 Bearers
UL CE factor
(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

[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.

Service Types DL/UL RAN11.0 CE
consumption
RAN12.0/RAN13.0 CE
consumption
CS over HSPA 10ms Downlink 0 CE 0 CE
Uplink

SF32: 1 CE (V2 NodeB)
SF32: 1.5CE (V1 NodeB)
SF32: 1 CE (V2/V1 NodeB)
VOIP over HSPA
10ms
Downlink 0 CE 0 CE
Uplink

VOIP/CS over HSPA
2ms
Downlink N/A 0 CE
Uplink
N/A
SF8: 1 CE (V2/V1 NodeB);

Procedure
Internal Open


2.3 Peak CEs for Erlang service
Peak Erlang
CE
_

Peak CEs for Erlang services is dimensioned to evaluate peak CE demand for the real-time CS
services with strict GoS requirements and 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.

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.

multiservice
Blocked
calls
Calls
arrival
Calls
completion
Fixed CE resources

Procedure
Internal Open


Low Utilization of resources
ErlangB - Partitioning Resources Multidimensional ErlangB - Resources shared
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
Average Erlang
CE
_

Average CEs for Erlang services is dimensioned to evaluate average CE demand. The following
formula is adopted:
i
i
i Average Erlang
CEFactor erNodeB CSTrafficP CE + =

Overhead) SH 1 (
_

Where,
Overhead SH is the soft handover ratio.
i
erNodeB CSTrafficP 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

Procedure
Internal Open


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 peak CE demands are 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
Average PS
CE
_

The method to calculate the CE consumed by PS services is similar to that to calculate the
average CE consumed by CS services.
i on transmissi re i burst
i
i Average PS
CEFactor R R erNodeB PSTrafficp CE + =

) 1 ) 1 Overhead) SH 1 (
_ _

Wherein

3600
=
i i
i
i
R
PerNodeB Throughput
erNodeB PSTrafficp

i
PerNodeB Throughput ( kbit ): the busy hour throughput per NodeB for service i .
i
: channel element utilization rate for service i .
i
R kbps: Bearer bit rate for service i .

i burst
R
_
is the burst ratio of service i .

Procedure
Internal Open


on transmissi re
R

is the re-transmission ratio of service i .
Overhead SH 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,
CE for UL PS64k: = + + + 5%) (1 * 20%) (1 * 20%) (1 * 3 *
3600 * 0.7 * 64
50 * 2000
3 CEs
CE for DL PS64k: = + + + 5%) (1 * 20%) (1 * 20%) (1 * 2 *
3600 * 0.7 * 64
100 * 2000
4 CEs
CE for DL PS128k: = + + + 5%) (1 * 20%) (1 * 20%) (1 * 4 *
3600 * 0.7 * 128
80 * 2000
3 CEs
Total CE for UL PS services is
UL PS
CE
_
= 3 CEs
And total CE for DL PS services is
DL PS
CE
_
=4+3= 7 CEs

4 CE Dimensioning for HSDPA
4.1 CEs for HSDPA in downlink
DL HSDPA
CE
_

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).

Procedure
Internal Open


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:
1 * ) 1 ( * ) 1 ( *
3600 * ) (
) (
1 *
_ burst re
HSDPA
HSDPA
HSDPA DL HSDPA
R P
kbps putPerUser ineThrough AverageOnl
kbit PerNodeB Throughput
Links CE + + = =

Where,
) (kbps putPerUser ineThrough AverageOnl
HSDPA
means the average HSDPA user throughput
of online HSDPA users;
re
P is the retransmission ratio;
burst
R 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
AUL HSDPA
CE
_

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:
) 1 ( * } 1 * ) ( * {
_
d SHOoverhea Links Links CEFactor Links CE
HSDPA A OnlineHSDP DCH A HSDPA AUL HSDPA
+ + =

Where,
HSDPA
Links means the simultaneously online HSDPA users which are active ( with data
transferring).
A OnlineHSDP
Links means the simultaneously online HSDPA users( active and inactive).
The reason why we differentiate the
HSDPA
Links and
A OnlineHSDP
Links is because in the real
network, there are a lot of HSDPA users who are online without transferring data in one period of

Procedure
Internal Open


time. These users follow the different CE consumption principle compare to the users with data
transferring.

So the final CE consumed by the HSDPA A-DCH can be described as following:
) 1 ( *
) 1 ( * ) 1 ( * } * )
3600 * ) (
) (
3600 * ) (
) (
(
*
3600 * ) (
) (
{
_
d SHOoverhea
R P CE
kbps User oughputPer AverageThr
CEFactor
CE
burst re r InactivUse
HSDPA
HSDPA
HSDPA
HSDPA
DCH A
HSDPA
HSDPA
AUL HSDPA
+
+ + +
=

Where,
re
P is the retransmission of HSDPA service
burst
R is the burst ratio of HSDPA service.
d SHOoverhea is the soft handover ratio of A-DCH of HSDPA.
) (kbps User oughputPer AverageThr
HSDPA
means the average HSDPA data transferring
throughput, normally 400~600Kbps is suggested due to HUAWEIs experiences.
) (kbps putPerUser ineThrough AverageOnl
HSDPA
means the average HSDPA online throughput,
normally 30~50Kbps is suggested due to HUAWEIs experiences.
So
3600 * ) (
) (
HSDPA
HSDPA
gives the all the simultaneously
online HSDPA users number,
3600 * ) (
) (
HSDPA
HSDPA
means the
simultaneously online HSDPA users active.

r InactivUse
CE 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.

DCH A
CEFactor

is the CE consumed by each A-DCH. The value of
DCH A
CEFactor

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
PS, so the
DCH A
CEFactor

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

Procedure
Internal Open


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:
1 * %) 10 1 ( * %) 0 1 ( *
50 * 3600
3600 * 2000
1 *
_
+ + = =
HSDPA DL HSDPA
Links CE = 44 CEs
CE in uplink:
DCH A
CEFactor

=1.5 CE (400Kbps HSDPA throughput mapping to 32Kbps A-DCH,
which consumes 1.5 CE in R99 PS)
) ( *
_ HSDPA A OnlineHSDP DCH A HSDPA AUL HSDPA
Links Links CEFactor Links CE + =

=
%) 20 1 ( * %) 10 1 ( * %) 0 1 ( * } 1 * )
400 * 3600
3600 * 2000
50 * 3600
3600 * 2000
( 5 . 1 *
400 * 3600
3600 * 2000
{ + + + +
= 56 CE

Procedure
Internal Open


5 CE Dimensioning for HSUPA
5.1 CEs for HSUPA in downlink
ADL HSUPA
CE
_

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
UL HSUPA
CE
_

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:
UL Traffic UL SRB UL HSUPA
CE CE CE
_ _ _
+ =

Where,
UL SRB
CE
_
is the CE consumed by the SRB of HSUPA users
UL Traffic
CE
_
is the CE consumed by the traffic of HSUPA services

CE of SRB of HSUPA users:
UL SRB
CE
_

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:

1 *
_ HSUPA UL SRB
Links CE =

Procedure
Internal Open


1 * Overhead) SH 1 ( * ) 1 ( * ) 1 ( *
3600 * ) (
) (
+ + + =
burst re
HSUPA
HSUPA
R P

If SRB is borne on HSUPA, no additional CE is consumed by the SRB of HSUPA services.

CE of traffic of HSUPA services:
UL Traffic
CE
_

For the CE consumed by the HSUPA traffic, can be calculated by the following formula:
) 1 ( * ) 1 ( * ) 1 ( *
} CE * )
3600 * ) (
) (

3600 * ) (
) (
(
*
3600 * ) (
) (
{
er InactiveUs
_
d SHOoverhea R P
CEFactor
CE
burst re
HSUPA
HSUPA
HSUPA
HSUPA
HSUPA
HSUPA
HSUPA
UL Traffic
+ + +
+
=

Where,
re
P is the retransmission of HSUPA service
burst
R is the burst ratio of HSUPA service.

3600 * ) (
) (
HSUPA
HSUPA
means the simultaneously online HSUPA
users number with data transferring.
3600 * ) (
) (
HSUPA
HSUPA
means the simultaneously online
HSUPA users number.
r InactivUse
CE 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.
HSUPA
CEFactor can be found in the following table:
Table5 CE mapping of HSUPA for NodeB3900 in RAN10~RAN13 with 2RX
SF
CE factor MAC-e Bit-rate (Kbps)
RAN10.0 RAN11.0 RAN12.0/13.0 Cat 5 10ms Cat 6 2ms Cat 7 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 +
2*SF4
48 48 48
5739 4059
2*M2+2*M4
Not
support
Not
support
64

699 11498

Procedure
Internal Open


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 that throughput in the above table is at MAC-e layer. But normally the throughput
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:
) 1 ( SBLER
TTI
Head
P
Rate
Rate
e MAC
RLC
RLC
e MAC

|
|
.
|
\
|
+ =

Where,

Parameters Definition Unit
Rate
MAC-e
Throughput in MAC-e kbps
Rate
RLC
Throughput in RLC kbps
P
RLC

Efficiency in RLC, normally 320/336
is suggested

Head
MAC-e

Overhead of MAC-e, 18bit is
suggested
bit
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~RAN13 with 2RX with RLC throughput
SBLER=10%
SF
CE factor
MAC-e Bit-rate (Kbps)
RLC Bit-rate
(Kbps)
RAN10 RAN11
RAN12/
13
Cat 5
10ms
Cat 6
2ms
Cat 7
2ms
Cat 5
10ms
Cat 6
2ms
Cat 7
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*
M4
Not
support
Not
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.

Procedure
Internal Open


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/13.0.
If the RLC throughput is 500Kbps, no value matched, from 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 . 154 711
) 8 . 154 3 . 585 ( * ) 4 8 (
4

+ =7.10 CE

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 CE1.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
1 * %) 11 1 ( * %) 20 1 ( *
3600 * 20
500 * 2000
+ + =
HSUPA
Links = 19 CE
CE for traffic
MAC-e throughput for 128Kbps is 151Kbps, which consumes 3.9 CE

Procedure
Internal Open


UL Traffic
CE
_
=
= + + + %) 11 1 ( * %) 20 1 ( * } 1 * )
3600 * 128
500 * 2000
3600 * 20
500 * 2000
( 9 . 3 *
3600 * 128
500 * 2000
{
28 CE
Total CE in uplink
19+28 = 47 CE
6 Impact on CE from new features in RAN11~RAN13
CE consumption principles for all new features in RAN11~RAN13 versions are detailed in
following table.
Table7 CE Consumption Principles for new features in RAN11~RAN13

[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.

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.
Service Types DL/UL RAN11.0 CE
consumption
RAN12.0/13.0 CE
consumption
CS over HSPA 10ms Downlink 0 CE 0 CE
Uplink

SF32: 1.5CE (V1 NodeB)
VOIP over HSPA
10ms
Downlink 0 CE 0 CE
Uplink SF16: 2 CE (V2 NodeB)
VOIP/CS over HSPA
2ms
Downlink N/A 0 CE
Uplink
N/A
SF8: 1 CE (V2/V1 NodeB);
64QAM
Downlink 0 CE 0 CE
Uplink 0 CE 0 CE
MIMO Downlink 0 CE 0 CE
Uplink One user need 1 additional
CE for HS-DPCCH
0 CE
DC-HSDPA/DC-MIMO Downlink N/A 0 CE
Uplink
N/A
0 CE

Procedure
Internal Open


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 Peak for CS
CE Average for CS
CE occupied by CS
CE occupied by PS
C
E

R
e
s
o
u
r
c
e
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:

) , (
_ _ _ _ _ _ _ _ _ UL HSUPA AUL HSDPA UL Average PS UL Average Erlang UL Peak Erlang Total UL
CE CE CE CE CE Max CE + + + =
) , (
_ _ _ _ _ _ _ _ _ ADL HSUPA DL HSDPA DL Average PS DL Average Erlang DL Peak Erlang Total DL

For the CE dimensioning in RAN11~RAN13, the total CE dimension in uplink and downlink can
be summarized respectively as the following formulas:
) , (
/ _ _ _ _ _ _ _ _ _ MIMO DC DC MIMO UL HSUPA AUL HSDPA UL Average PS UL Average Erlang UL Peak Erlang Total UL
CE CE CE CE CE CE CE Max CE

+ + + + + =
) , (
_ _ _ _ _ _ _ _ _ ADL HSUPA DL HSDPA DL Average PS DL Average Erlang DL Peak Erlang Total DL

Procedure
Internal Open


CE Dimension

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

CE Dimension

Hochgeladen von

Copyright:

Verfügbare Formate

Error! Reference source not found.

WCDMA CE Dimensioning Principle and

Das könnte Ihnen auch gefallen