umts ce dimensioning principles and case studies-v2-2009014[1]

WCDMA CE Dimensioning Principle and ProcedureInternal Open

Product name Confidentiality level

WCDMA RNP For internal and external use

Product versionTotal 14 pages

1.4

UMTS CE Dimensioning Principles and

Case Studies

Prepared by WCDMA-RNP Date 2009-02-04

Reviewed by Date yyyy-mm-dd

Reviewed by Date yyyy-mm-dd

Granted by Date yyyy-mm-dd

Huawei Technologies Co., Ltd.All rights reserved

4/17/2023 All rights reserved , Total15


Important Notice:

Please send us your comments or requests via URNP-

[email protected] .

We will improve the quality of the material to meet your requirements

ASAP.

Revision Record

Date Version CR ID Revision Description Author

2006-11-30

1.1 initial version Deng Liang

2007-10-31

1.2 (1)CE dimensioning of HSUPA is introduced

(2)CE dimensioning case study is introduced

(3)Update the CE dimensioning formula of HSDPA

(4)Update CE dimensioning flow chart(5)Huawei CE features are introduced(6)Update the total CE dimensioning

Pan Yaping

2008-07-01

1.3 (1)Introduce CE dimensioning principles since RAN10 version

(2)Introduce CE dimensioning case studies since RAN10 version

(3)Update case studies by reducing soft handover into 20%

Li Zhichao

2009-02-04 1.4 根据CR 01和02修改相关章节 Xu Haihong

2009-08-15 1.5 根据最新产品宣传口径更新HSPA CE算法 Tian Feng

Change Request (CR) Record

CR ID CR Originator

CR Date CR Description CR Feedback

01Lihong (51769)

2009-02-04

目前投标都已经是RAN11.0了，文档里面的CE消耗关系还没有到RAN11.0.另外，CE消耗表最好写清楚是哪个版本，建议保留RAN10,新增RAN11.0

接受

01 Lihong (51769)

2009-02-04

4.3章节，RAN10的HSDPA的CE计算，是否有问题？

拒绝



Table of Contents

1 Introduction...........................................................................................................................32 CE Dimensioning for CS Services......................................................................................32.1 CEs for R99 Traffic Channel.........................................................................................32.2 Peak CEs for CS service................................................................................................32.3 Average CEs for CS service..........................................................................................32.4 Case Study.......................................................................................................................3

3 CE Dimensioning for PS Services......................................................................................33.1 CEs for PS Services........................................................................................................33.2 Case Study.......................................................................................................................3

4 CE Dimensioning for HSDPA A-DCH.................................................................................34.1 CEs for HSDPA A-DCH before RAN10 version...........................................................34.2 CEs for HSDPA A-DCH of RAN10 & RAN11 version..................................................34.3 Case Study.......................................................................................................................3

5 CE Dimensioning for HSUPA and its A-DCH....................................................................35.1 CEs for HSUPA and A-DCH before RAN10 version...................................................35.2 CEs for HSUPA and A-DCH of RAN10 & RAN11........................................................35.3 Case Study.......................................................................................................................35.4 CEs for All the Services.................................................................................................35.5 Case Study.......................................................................................................................3



CE Dimensioning Principles and Case Studies

Abstract：This article presents the Channel Element (CE) dimensioning principles as

well as corresponding case studies in which the principles are demonstrated

quantitatively with assumptions.

1 Introduction

Channel Element (CE) unit is defined as the base band resources required in the

NodeB to provide one voice channel traffic, simultaneously including control plane

signaling, compressed mode, transmit diversity and softer handover.

Huawei CE dimensioning principles have the following general features:

(1) CEs resource are pooled in one NodeB

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

(3) No need extra CE resource for TX diversity

(4) No need extra CE resource for compressed mode

(5) No need extra CE resource for softer handover

(6) CE resource for R99 and HSDPA services are designed separately and have

no impact on each other

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

(8) CE resource for R99 and HSUPA services are shared together

Before RAN10 version, Huawei CE consumption mainly comes from the following

aspects:

(1) CS services of R99

(2) PS services of R99

(3) Associated DCH (A-DCH) of HSDPA

(4) Associated DCH of HSUPA

(5) HSUPA traffic

And since RAN10 version, if SRB over HSPA feature is available .part of A-DCH of

HSDPA and HSUPA will not consume CE any more. if SRB over HSPA feature is

not available，there are some different CE Dimension in HSDPA and HSUPA.



The procedure of CE dimensioning is shown as the following figure:

Figure1 CE dimensioning procedure

2 CE Dimensioning for CS Services

2.1 CEs for R99 Traffic Channel

Table1 CE Factors of R99 Services

Bearer type CE Factors (UL)

CE Factors (DL)

WB-AMR6.6k 1 1

WB-AMR8.85k 1 1

WB-AMR12.65k 1 1

WB-AMR14.25k 1 1

WB-AMR15.85k 1 1

WB-AMR18.25k 1 1

WB-AMR19.85k 1 1

WB-AMR23.05k 1.5 1



WB-AMR23.85k 1.5 1

AMR4.75k 1 1

AMR5.9k 1 1

AMR7.95k 1 1

AMR12.2k 1 1

CS28.8k 1.5 1

CS32 1.5 1

CS56k 3 2

CS57.6 3 2

CS64k 3 2

PS8k 1 1

PS16k 1 1

PS32k 1.5 1

PS64k 3 2

PS128k 5 4

PS144k 5 4

PS256 10 8

PS384k 10 8

2.2 Peak CEs for CS service

Peak CEs for CS service is dimensioned to evaluate peak CE demand for the GoS

requirements as real-time services specially.

Multidimensional ErlangB algorithm is adopted in this part on the basis of traffic

of NodeB, CE factors, and GoS requirement of each service.

2.3 Average CEs for CS service

Average CEs for CS service is dimensioned to evaluate average CE demand, to

which total average CE demand would be calculated by adding average CE

demand of PS service.

The following formula is adopted in this part with consideration of CS traffic and

soft handover ratio:



(1)(2)

2.4 Case Study

Assumption:

Subscriber number per NodeB: 2000

Voice traffic per subscriber: 0.02Erl

VP traffic per subscriber: 0.001Erl

Soft Handover Overhead: 20%

GoS requirement of voice: 2%

GoS requirement of VP: 2%

Then,

（1） Peak CE Dimension

Traffic of voice: 0.02*2000*(1+20%) = 48 Erl

Traffic of VP: 0.001*2000*(1+20%) = 2.4 Erl

Voice peak CE demand are 59 CEs in uplink and 59 CEs in downlink

respectively.

VP peak CE demand are 21 CEs in uplink and 13 CEs in downlink

respectively.

Considering the CE resource share between voice and VP services, by

multidimensional ErlangB algorithm, the final total peak CEs demand are 74 CEs

in uplink and 68 CEs in downlink.

（2） Average CE Dimension

Voice average CE demand are 2000*0.02*(1+20%)*1=48 CEs in uplink and

48 CEs in downlink respectively.

VP average CE demand are 2000*0.001*(1+20%)*3=7 CEs in uplink and

2000*0.001*(1+20%)*2=5 CEs in downlink respectively.

The final total average CEs demand are 55 CEs in uplink and 53 CEs in

downlink respectively.

3 CE Dimensioning for PS Services

3.1 CEs for PS Services

The method to calculate the CE consumed by PS services is similar to that to



calculate the average CE consumed by CS services.

Wherein

The impact on CE consumption of soft handover overhead, PS traffic burst and

retransmission caused by error transmission should be considered.

( kbit ): the busy hour throughput per NodeB for service .

: channel element utilization rate for service .

（kbps）: Bearer bit rate for service .

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: 3 CEs

CE for DL PS64k: 4 CEs

CE for DL PS128k: 3 CEs

Total CE for UL PS services is = 3 CEs

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



4 CE Dimensioning for HSDPA and its A-DCH

4.1 CEs for HSDPA A-DCH before RAN10 version

In the uplink, A-DCH functions for transmitting signaling and control information

and according to traffic assignment design, two possible scenarios are

presented here:

(1) UL traffic model of R99 or HSUPA includes the uplink traffic of HSDPA

If the UL traffic of R99 includes the HSDPA uplink traffic, no additional CE should

be taken into account.

(2) UL traffic model of R99 or HSUPA does not include the uplink traffic of

HSDPA

If the uplink traffic of R99 does not include HSDPA uplink traffic, the additional

CE consumed by A-DCH should be taken into account, which can be calculated

by the following formula:

A-DCH CE factor is normally suggested to be configured as PS64k and the

impact of traffic burst and retransmission should be considered.

While In downlink, when each HSDPA subscriber accesses the network, one A-

DCH bearing 3.4k signaling should be set up, which consumes one CE.

Therefore CE resource consumed by HSDPA A-DCH is equal to the number of

simultaneously connected HSDPA users, which can be calculated according to

the following formula:

4.2 CEs for HSDPA A-DCH of RAN10 & RAN11 version

In uplink, since RAN10 version, CE consumed by A-DCH has the same process

method as the version before RAN10.

But in downlink SRB over HSDPA feature is available since RAN10.0. In

downlink CE dimensioning ,if SRB over HSDPA feature in activated, then A-DPCH

will no longer consume an CE, but if SRB over HSDPA feature is not activated,

then the CE consumption of A-DPCH in downlink is exactly the same to the

version before RAN10.0.



4.3 Impact of 64QAM and MIMO on HSDPA CE consumption.

In RAN 11 version, downlink 2*2MIMO/64QAM could be supported. For

64QAM, its deployment has no influence on uplink and downlink HSDPA CE

consumption. But for 2*2MIMO, to process HS-DPCCH, one additional uplink CE

will be required for one MIMO subscriber.

The deployment of MIMO has no influence on HSDPA downlink CE consumption.

4.4 Case Study

Assumption:


Traffic model of HSDPA: 1200kbit

Requirement of average throughput per user: 400kbps

HSDPA traffic burst: 0

Then,

1. If network expansion based on the version before RAN10:

Assuming the uplink traffic of R99 already includes the uplink traffic of HSDPA

A-DCH and therefore the CE consumed by HSDPA A-DCH in uplink is

= 0 CE

But CE consumed by HSDPA A-DCH in downlink is

= 2 CEs

2. As for new deployment network based on the version RAN10 & RAN11:

In downlink, If the SRB over HSDPA, there will consume 0 CE.if the SRB not

over HSDPA,

There will consume 2 CE like the version before RAN10.

5 CE Dimensioning for HSUPA and its A-DCH

5.1 CEs for HSUPA and A-DCH before RAN10 version

CE consumed by HSUPA traffic channel depends on the simultaneous

connected link number.

Wherein,



Considering the impact on CE consumption of soft handover overhead, HSUPA

traffic burst and retransmission caused by error transmission, the more CEs

could be needed by HSUPA traffic channel.

Table2 CE Factors of HSUPA Phase I

MinSFHSUPA Rate

(kbps)CE Factors HSUPA

Phase I

SF32 32 3.5

SF16 64 5

SF8 128 7

SF4 672 12

2*SF4 1376 22

2*SF2 - Not Support

2*SF2+2*SF4 - Not Support

Before RAN10 version, in uplink, CE factors in Phase I have already included the

CE consumption by A-DCH and E-DPCCH. Therefore no extra CEs are required

for HSUPA A-DCH.

In downlink, A-DCH CE consumption depends on the bearer rate. For example,

A-DCH is borne on PS64k, 2 CEs are consumed by each A-DCH. And the impact

of soft handover overhead should be taken into account.

5.2 CEs for HSUPA and A-DCH of RAN10 & RAN11

The CE Dimensioning for HSUPA and A-DCH of RAN10 & RAN11 has the same process

method as the version before RAN10.

Table3 CE Factors of RAN10 & RAN11 （The rate of RLC ）

MinSFHSUPA Rate(kbps) RAN

10.0Phase II

RAN11.0

10ms TTI

2ms TTINode B 3800

Node B 3900

SF32 32 　 1.5 1.5 1

SF16 64 　 3 3 2

SF8 128 　 5 5 4

SF4 672 640 10 10 8

2*SF4 1399 1280 20 20 16

2*SF2 2886 2720 32 32 32

2*SF2+2*SF4 5742 5440 48 48 48

For RAN10 & RAN11 version, ,4/17/2023 All rights reserved , Total15


In uplink, when the SRB over HSUPA ,A-DCH, as well as E-DPCCH will never

consume additional CE any more, in Phase II as presented in table 3. If the SRB

of HSUPA is carried on the R99 DCH, an extra CE is consumed. Thus, one CE

should be added to the CE number in the table above. But when we use Node B

3800， the CE Factors of RAN 11.0 is same as RAN 10.0 Phase II. there will

consume extra 2 CEs for each service like Phase I as presented in table 2.

In downlink, A-DCH CE consumption depends on the bearer strategy. If A-DCH is still

borne on R99, CE required is similar to that in Phase I, and if A-DCH is borne on HSDPA,

no additional CE is consumed.

5.3 Case Study

Assumption:


Traffic model of HSUPA: 500kbit

Requirement of average throughput per user: 250kbps


Downlink A-DCH is borne on PS64k

Then,


The CE consumption of average throughput 250kbps is 8 CEs derived from

the following formula:

,

and =2

So, in uplink, the CE number consumed by HSUPA traffic channel and A-

DCH are =2*8=16 CEs, including 2CEs for A-DCH and 14 CEs for

HSUPA traffic channel.

And in downlink A-DCH on PS64k needs = 2*2=4 CEs

2. As for new deployment network based on the version RAN10

In uplink, 6 CEs will be enough for each HSUPA link and total 12 CEs but 0

CE for A-DCH finally.

In downlink, when A-DCH is borne on HSDPA, 0 CE will be required.

3. As for new deployment network based on the version RAN11:

1) For Node B 3800

, x=6



In uplink, 6 CEs will be enough for each HSUPA link and total 12 CEs but 0



2) For Node B 3900

, x=7

In uplink, 7 CEs will be enough for each HSUPA link and total 14CEs but 0



remark :1．All of these are based on SRB OVER HSUPA 。IF the SRB OVER DCH，each connection

should consume extra 1 CE

5.4 CEs for All the Services

PS services including HSPA packet services adopts the access strategies called

“Best Effort”, which means PS services could only occupy the remaining CE

resource after all the CS services are satisfied. The real-time CE resources

assignment between CS and PS within NodeB is clearly demonstrated in Figure2.

Figure2 CE Shared between PS and CS Services

When HSUPA and HSDPA co-exist in the network, the uplink and downlink A-DCH

can be shared between HSUPA and HSDPA. and it is based on SRB not over

HSPA.

: CE consumed by uplink A-DCH of HSUPA;

: CE consumed by downlink A-DCH of HSDPA;



Therefore, according to the previous presentation, the total CE dimension in

uplink and downlink can be summarized respectively as the following formulas:

Remark: If SRB over HSDPA feature is available, the uplink and downlink A-DCH will not

consume any CE.

5.5 Case Study

Based on the assumption and calculation of above case studies, the finally CE

summary for different version should be:


= Max (2, 0)=2 CE

= Max(4, 2)=4 CE

= Max(74, 55+3+2+14)=74 CEs

= Max(68, 53+7+4)=68 CEs


= Max (0, 0)=0 CE

= Max(0, 0)=0 CE

= Max(74, 55+3+0+12)=74CEs

= Max(68, 53+7+0)=68 Ces


= Max (0, 0)=0 CE

= Max(0, 0)=0 CE

1) For 3800

= Max(74, 55+3+0+12)=74CEs

= Max(68, 53+7+0)=68 CEs

2) FOR 3900

= Max(74, 55+3+0+14)=74CEs

= Max(68, 53+7+0)=68 CEs



Remark: All of these cases are based on SRB over HSPA.


umts ce dimensioning principles and case studies-v2-2009014[1]

Documents

ce dimensioning of hsupa

ce dimensioning case

total ce dimensioning

huawei ce features

need extra ce resource

huawei ce consumption

ces resource

hsdpa services