Vous êtes sur la page 1sur 17

Huawei RNC

Capacity dimension

Capacity dimension
Principle for capacity dimension
Input from operator
( Total subscribers in network,
traffic model)

RNC capacity limitation


( Erl, Throughput,BHCA)

Radio Network
dimension

Number of WRBS

If Nodebs per
WRBS >100

Subscribers per Nodeb

Subscribers per WRBS

Nodebs per WRBS

Traffic Model Parameters


Traffic Parameter

Value

BHCA CS per sub

0.6

BHCA total per sub

0.9

CS Voice per sub/BH

16,2mErl

CS Data per sub/BH

1,1mErl

CS Video Telephony call duration/BH

135sec

CS call duration/BH

135sec

Rel.99 PS per sub/BH

580bps

Total PS per sub/BH

1160bps

Timer for CH switching (DCH/FACH)

600-800msec

Location update rate sub/BH

2.2

Ratio of soft/softer HO/BH

0.8:0.2

Proportion of HO/BH

30%

Handover times/call/BH (inter/intra RNC


SHO)

7,0 times/call

PS CH switching

4.0 times/call

Cell update/PSCall

3 times/call

Ratio of UL : DL (Rel.99/HSDPA)

1:3.6

Traffic Model from Vodafone


3

Limitation
60Mbps/ WRBS

Limiting factor : throughput capacity

e.g.

2 WRBS

120Mbps / 60Mbps = 2

75,000/ WRBS

Limiting factor : BHCA capacity

e.g.

1 WRBS

60,000 / 75,000 = 0.8

100 NodeB/ WRBS

Limiting factor : NodeB capacity


e.g.

2 WRBS

150 / 100 = 1.5

300 NodeB/ WRBS

Limiting factor : Cell capacity

e.g.

2 WRBS

400 / 300 = 1.3

RNC Dimension
2*63 channalized E1s

VF CALL PROFILE DATAS

RNC Capacity Limitation


CS Erlang and CS Throughput
There define a relationship between CS Erlang and throughput as follows:
1 CS Erlang = 16kbps throughput.
The relation comes from the processing consuming in WFMRb board.

CS Throughput and PS Throughput


For each RNC subrack :
CS throughput + PS throughput <= 60Mbps;
CS throughput < = 40Mbps;

RNC Capacity Limitation


BHCA calculation from CS 40Mbps
Supposing each call duration is 120s. The maximum CS throughput is 40Mbps,
equals to 2500Erl.
Erl = BHCA * Call duration /3600
It can derive that : BHCA = 2500/(120/3600) = 75,000
Equivalent BHCA
1. This index is used to measure the signaling processing capability in WSPUb.
2. The equivalent BHCAconsiders the procedure not only the call procedure, but
also other signalling procedure, including SMS, IMSI attachment, location update,
handover, cell update, URA update, etc.
3. The equivalent BHCA comes from the test data where the WSPUb CPU load is
up to 80%.
4. The maximum equivalent BHCA is 360k and the WSPUb CPU load is 80%.

Note: The actual signaling capacity is limited by Integrated BHCA


7

RNC Capacity Limitation


Equivalent BHCA
Basic Signaling

Equivalent BHCA

CS BHCA per BM per BH

1.00

PS BHCA per RNC per BH

1.00

Location Area Update per RNC per BH

0.46

Routing Area Update per RNC per BH

0.46

Soft Handover Addition per RNC (intra/inter RNC)

0.26

Soft Handover Deletion per RNC (intra/inter RNC)

0.13

Softer Handover Addition per RNC (intra/inter RNC)

0.18

Softer Handover Deletion per RNC (intra/inter RNC)

0.09

CS Inter-RAT handover per RNC

0.56

PS channel switching per RNC

0.41

SMS per RNC per BH

0.46

Paging per RNC per BH

0.01

RRC REJ

0.15

RNC Capacity Limitation


Maximum Subscribers number
The maximum number of subscriber depends on the Integrated BHCA, call
model and maximum data throughput:
Procedure multiplied per Cost

360k

equivalent BHCA(# Subscriber, call model) < Maximum Equivalent BHCA


60M per subRack

Total throughput ( #Subscriber, call model) < Maximum data throughput

Board information
WFMRb
1.

WFMRb board is user plane processing board, handling the user data of
AAL2 cell for Iu/Iub/Iur interface.

2.

One RNC subrack contains 10 WFMRb with the maximum capability of


60Mbps for PS throughput or 40Mbps for CS throughput

3.

The maximum user plane capability of WFMRb board in RAN5.1 is 6Mbps


for PS packet processing. (MAC layer 7.2M)

4.

For CS voice processing, 4Mbps can be handle for each WFMRb board.

5.

WFMRb board contributes to the RNC total PS throughput as well as the


CS throughput.

10

Board information
WSPUb
1.

WSPUb board is signalling processing board which handle the RANAP/


RNSAP/SS7/QAAL2/RRC/NBAP signaling;

2.

Each WSPUb board could handle 75,000 BHCA (for typical traffic model) which
does not includes the location update, paging, handover, SMS,
attaching/detaching, etc. procedure.

3.

The maximum equivalent BHCA is 360k and the WSPUb CPU load is 80%.

WOSEc
1.

WOSEc board is Iub interface board.

2.

Each WOSEc board can process 60Mbps throughput.

11

Board Information
Summary
1.

WFMRb and WSPUb are the main boards contributing to RNC capacity;

2.

WOSEc board is the Iub interface board which is not the limitation for the
RNC capacity;

3.

WMUXb board is the switching board in each sub-rack and is not the
limitation for the RNC capacity;

12

Some analysis for New Years eve

1.

Between 00:00-00:15, Altogether 21000 CS call attempts processed by


RNC 121, but only 13000 RAB assigned by CN, so somewhere in CN must
be overload.

2.

Between 00:00-00:59, Altogether 51055 RRC connect rejected, among


them 49683 belong to SMS, only 1372 belong to voice call.

Conclusion:
Between 00:00-00:15, both RNC and CN are overloaded.
RNC is overloaded (RRC rejection) with only 600 Erlangs because abnormal
high number of SMS and Core network lack of reply.

13

SMS
locUpdate

200 7-01 -01 10:00:0 0

200 7-0 1-01 09:00:00

2 007 -01-01 08:0 0:0 0

2 007 -01-0 1 0 7:0 0:00

2 007 -01-01 06:0 0:0 0

200 7-0 1-01 05:00:00

200 7-0 1-01 04:00:0 0

20 07-01-01 0 3:00 :00

2 007 -01-0 1 0 2:0 0:00

2 007 -01-0 1 01:0 0:00

200 7-0 1-01 00:00:00

200 6-12-31 23:00:0 0

20 06-1 2-31 2 2:00 :00

20 06-12-3 1 2 1:00 :00

RRC EVOLUTION NEW YEAR CHARTS


RRC.FailConnEstab.Cong

60000
50000
40000

30000
20000
10000

CS call orig

interRAT

14

Mapping nodeb to SubRack


40 nodeb on SubRack1

15

Half of NodeB on Cpu1

SPU load evolution

More space on User plane than Signalling plane

16

SPU Dimension using current CPU load

Total nber of subcribers in network: 1000k


600Erl

Erlangs_RNC121/TotalErlangs=2% =>20k Subs in RNC121

Erlangs for each Nodeb from counters

Nodeb to SPU map( worse SPU 40 nodeb among 87)

The cpu load is 8% for common task if the traffic load is 0

Cpu load with 275 Erlangs=40% at BH and limit is 80%


=> the SPU can handle 275*(80-8)/(40-8)=618 Erlangs
=> If 618/87=7 Erlangs per nodeB => a SPU can handle 550/7=78Nodeb

Erlangs per SPU


=600*40/87=275 Erl

17

Vous aimerez peut-être aussi