5-rnc&lac&rac&cluster planning 26

7/28/2019 5-RNC&LAC&RAC&Cluster Planning 26

http://slidepdf.com/reader/full/5-rnclacraccluster-planning-26 1/26

RNC/LAC/RAC/Cluster Planning

ZTE University

TD&W&PCS BSS Course Team



RNC Definition

The principles for delimitating the network into RNC are as

follows.

The network traffic distribution: the border of RNC should be

located at the lighter traffic area.

The sites distribution: each RNC has as less neighboring and

handover relations with other RNC as possible.

Make good use of the current RNC delimitation information.

Make good use of the natural geography border.



RNC Definition

Distribute the traffic of each RNC evenly.

MTR sites are planned independently, and belong to the same

RNC if it is possible.

The RNC location will be determined by the switch room.

Considering the network future development, the corresponding

BSC delimitation and traffic should be considered during the

RNC delimitation.



RNC Definition

According to above principles and RNC numbers, the following

is the RNC definition and coverage area of 3G network.

ZTE RNC Definition

ZTE RNC Location

ZRNC101 BMI

ZRNC102 BMI

ZRNC103 BMI

ZRNC201 BPO

ZRNC202 BPO

ZRNC203 BPO



RNC Definition



RNC Traffic Based on Current Existing Traffic

ZTE RNCID RNC/Total Traffic Ratio CS traffic

(Erl)

PS traffic

(Mbps)

ZRNC101 20.00% 1527.2 15.2

ZRNC102 16.90% 1290.484 12.844

ZRNC103 14.28% 1090.4208 10.8528

ZRNC201 17.76% 1356.1536 13.4976

ZRNC202 16.11% 1230.1596 12.2436

ZRNC203 14.95% 1141.582 11.362

Total

traffic

CS (Erl)* 7636

PS (Mbps)* 76

* CS Erlang excluding SHO, include voice and video call (sum of BTS Erlang)

* BH IuPS UP Peak DL Throughput (Peak second Mbps)



Designed Traffic

ZTE RNCID RNC/Total

TrafficRatio

Voice

traffic (Dec 08)

(Erl)

Data

traffic

(Dec 08)

(Gbps)

Voice traffic

(FutureTraffic)

(Erl)

Data traffic

(FutureTraffic)

(Gbps)

ZRNC101 20.00% 13000 1.2 19500 1.8

ZRNC102 16.90% 10985 1.014 16477.5 1.521

ZRNC103 14.28% 9282 0.8568 13923 1.2852

ZRNC201 17.76% 11544 1.0656 17316 1.5984

ZRNC202 16.11% 10471.5 0.9666 15707.25 1.4499

ZRNC203 14.95% 9717.5 0.897 14576.25 1.3455

Total traffic

(Dec 08)

Voice (Erl) 65000

Data(Gbps) 6

Total traffic

(Future

Traffic)

Voice (Erl) 97500

Data

(Gbps)

9

* Radio traffic figures do not include soft handover.



Cluster Definition

The principles for delimitating the network into clusters are

as follows:

The size of the cluster should be 20-40 NodeBs generally.

The city environment factors (dense urban & mean urban etc.),

network factors (Region, RNC&LAC etc.), and coverage clutter

should be considered.

The coverage area of the cluster should be consecutive.

Each cluster has as less neighboring relations with other

clusters as possible, and the clutter & vector can be looked as

the border of the clusters, such as river, hill and buildings, etc.



Cluster Definition

Cluster Name Cluster Priority

Central_to_Admiralty 1

MidLevel 2

West 2 NorthPoint 2

QuarryBay_to_ShauKeiWan 2

LantauExpressway 4

Airport 4

SouthLantau 5

ToKwaWan_to_HungHom 1

HoManTin_to_MaTauWai 3

KowloonCity 1

KowloonTong 1



LAC/RAC Planning

Principles for Delimitating LAC/RAC

LAC/RAC should be as big as possible if the system capacity can bear

Make good use of the geographical border as the LAC/RAC border

Select the low traffic area as the border of LAC /RAC

Distribute the traffic of different LACs evenly

MTR sites are planned independently, and belong to same LAC if

possible

The main principle of LAC/RAC is to reduce location update times,

and guarantee paging success rate.



Paging channel features

PCH message carried by S-CCPCH channel

3gpp stipulate PCCH has two format:

240bit/10ms or 80bit/10ms

One 240bit PCCH frame can support

3 IMSI paging

2 TMSI +2 IMSI paging

1 TMSI +4 IMSI paging

5 TMSI paging paging



LAC/RAC Planning

System Parameters Settings

Paging period: 640ms (configurable)

RAN paging times: 4 (configurable)

CN paging times: 2

CN paging interval: 6s (configurable)

PCCH/PCH format: 240bit per 10ms



Paging Messages of One LAC in BH

RAN paging times maximum theoretical paging messages in BH

1 1800000

2 900000

3 600000

4 450000



ZTE Designed Paging Capability of One LAC in BH

RAN paging times paging capability of one LAC in BH

1 900000

2 450000

3 300000

4 225000



Number of Existing paging messages

NUMBER OF PAGING MESSAGES

INCLUDING BUT UP TO HSDPA3.6MBPS

(PEAK HOURLY NUMBER)

809,980 SUM OF THE PEAK HOURLY PROCESSED

PAGING MESSAGES OF ALL LIVE RNCS(IN NUMBER) (MEASUREMENT PERIOD

= 60min)



Required Number of LAC

RAN paging times Paging capability of one LAC in BH Number of LAC

1 900000 1

2 450000 2

3 300000 3

4 225000 4



Paging Load of each RNC/LAC (Message Number)

ZTE RNCID ZTE LACID RNC/Total 3G Traffic Ratio Paging load

(number)

ZRNC101 1011 20.00% 161996

ZRNC102 1021 16.90% 136886.6

ZRNC103 1031 14.28% 115665.1

ZRNC201 2011 17.76% 143852.4

ZRNC202 2021 16.11% 130487.8

ZRNC203

2031

14.95%

121092

Total paging messages

(number)

809980 100.00% 809980



Designed Number of LAC and Paging Load

RAN paging times 1 2 3 4

Paging capability of one LAC in BH 900000 450000 300000 225000

ZTE LACID Paging load (number) Paging loads(ratio)

1011 161996 18.00% 36.00% 54.00% 72.00%

1021 136886.6 15.21% 30.42% 45.63% 60.84%

1031 115665.1 12.85% 25.70% 38.56% 51.41%

2011 143852.4 15.98% 31.97% 47.95% 63.93%

2021 130487.8 14.50% 29.00% 43.50% 57.99%

2031 121092 13.45% 26.91% 40.36% 53.82%



Number of paging messages for DEC 2008 Traffic

OCT 2007 DEC 2008

Traffic(Erl) 6580 65000

Number of paging messages(peak hourly number) 809,980 8,001,322



Paging Load of each RNC (Message Number)

ZTE RNCID ZTE LACID RNC/Total 3G Traffic

Ratio

Paging load

(number)

ZRNC101 1011 20.00% 1,600,264

ZRNC102 1021 16.90% 1,352,223

ZRNC103 1031 14.28% 1,142,589 ZRNC201 2011 17.76% 1,421,035

ZRNC202 2021 16.11% 1,289,013

ZRNC203 2031 14.95% 1,196,198

Total paging messages

(number)

8,001,322 100.00% 8,001,322



Designed Numbers of LAC and Paging Load

RAN paging times 1 2 3 4

Paging capability of one LAC in BH 900000 450000 300000 225000

ZTE LACID Paging load (number) Paging loads(ratio)

1011 1,600,264 177.81% 355.61% 533.42% 711.23%

1021 1,352,223 150.25% 300.49% 450.74% 600.99%

1031 1,142,589 126.95% 253.91% 380.86% 507.82%

2011 1,421,035 157.89% 315.79% 473.68% 631.57%

2021 1,289,013 143.22% 286.45% 429.67% 572.89%

2031 1,196,198 132.91% 265.82% 398.73% 531.64%



Map of Designed LAC for DEC 2009



RAC Planning

Paging procedure in PS domain is initiated from Network

side, compared with CS domain service, paging load

should be less, so the RAC design is the same with LAC.

That is to say, there are 6 RACs suitable for the 3G

network. Of course it will be adjusted according to the

traffic and paging load growth.

According to above, 3G network LAC&RAC boundaries

are the same with RNC boundaries.



ZTE 3G LAC/RAC/NodeB Mapping



ZTE 3G LAC/RAC/MTR NodeB Mapping

5-rnc&lac&rac&cluster planning 26

Documents