Академический Документы
Профессиональный Документы
Культура Документы
TERN3 RNC
Nuttavut Sae-Jong
GS MS NPO SD CoC Mobile Core&Radio TH
For internal use
Unique document identifier (ID) / Version number / Life cycle status
1
URA_PCH Trial
URA_PCH Deployment Summary
URA_PCH is activated in TERN3 RNC
1st step: setting URAId = LAC and URA = LAC area on 15.09.2011
3 URAIds for 3 LACs
URAId/LAC: 375/375, 376/376 and 377/377
2nd step: URAId splitting is done on 03.11.2011 to improve RNC load (ICSU
load)
4 URAIds for 3 LACs
URAId/LAC: 375/375, 376/376, 377/377 and 378/376
URA_PCH Trial
1st step deployment
URA_PCH was activate on RNC TERN3 on 15/09/2011 09:00PM
Defined URAId = LAC and 1 URAId per Cell
TERN3 Assessment
TERN3 Paging, ICSU and DMPG Load
It is still has some gap on PCH and RNC load. This is need to be monitor
before activated URA_PCH feature to avoid a PCH and RNC load congestion
at beginning.
RNC
Paging Load
AVG_DMPG_Load
PEAK_DMPG_Load
AVG_ICSU_Load
PEAK_ICSU_Load
25.08.2011
TERN3
17.31%
28.51
67.00
29.09
62.00
26.08.2011
TERN3
17.46%
28.16
70.00
27.88
76.00
27.08.2011
TERN3
16.57%
28.09
79.00
27.52
60.00
28.08.2011
TERN3
16.45%
28.58
70.00
28.46
63.00
29.08.2011
TERN3
17.21%
28.76
68.00
28.94
62.00
30.08.2011
TERN3
17.30%
28.61
71.00
28.50
63.00
31.08.2011
TERN3
17.28%
27.94
61.00
27.98
67.00
LAC376
LAC377
LAC375
For internal use
Unique document identifier (ID) / Version number / Life cycle status
5
URAId = 376
URAId=377
URAId = 375
For internal use
Unique document identifier (ID) / Version number / Life cycle status
6
WCEL Object
Totally 3 URAId (URAId: 375, 376 and 377)
Network KPIs
remain stable
No degradation on
others network KPIs
Network KPIs
remain stable
A result show
URA_PCH Trial
2nd step deployment
Split URAId from 3 URAIds to 4 URAIds
Paging traffic/Paging message in URA_PCH stage is use to be a criteria to
select which URAId is need to split to reduce/balance a paging traffic in
each URA.
URA_PCH Trial
URA Selection for URAId spliting
Due to a paging load is increasing and affecting ICSU load. Therefore, we
have plan to split existing URAId area to improve paging load which will benefit
on RNC capacity (ICSU load).
A URAId split will first starting on URAId area which has high paging
traffic/paging message in URA_PCH
URAId 376 has high paging traffic/paging message in URA_PCH
splitting a half of a site in this URAId area to another URAId (URAId 378)
WCEL Object
Totally 4 URAId (URAId: 375, 376, 377 and 378)
No Network KPIs
degradation are observed
from URA_PCH.
HSDPA Performance
degradation is observed on
08-Nov.
Number of Paging per URAId can be use as a indication for URAId splitting. Each URAId
should have an equal number of paging message. If not, URAID splitting might need on
those UARId.
Remark:
internal use
For
Some sites (west side) in TERN3 are swapped to another vender since about 26-Oct-2011
Unique document identifier (ID) / Version number / Life cycle status
30
Thanks You