Capacity - RNC Capacity Management - Smart Phone Impact

RNC capacity management
CPU load analysis – Smart phone impact
For internal use only

1 © Nokia Siemens Networks Presentation / Author / Date
Introduction
• RNC unit load is forecasted based on

– Network traffic forecast
– Device forecast based on number of data dongles, smart phones,
standard handsets
– A signalling profile for each phone type
• The model was originally created for a customer case

• The RNC2600 ICSU model was modified to more general model created
by product line
• The RNC450 and DMPG model will be further developed by product line
• There is no model done for ICSU performance in RNC196
– It is lower than in RNC450 or RNC2600 so the model does not directly work
– In case a model would be needed probably some adjustment factor that use to
multiply the current “costs” for RNC196
RNC Capacity Model
• ICSU load model for RNC2600

– Models control plane load
– ICSU CPU load calculation is based on the number of signalling events
and so-called „CPU cost” of each event
– There will a model for the DMPG CPU load in the future
• For RNC450 there is similar model for ICSU and DMPG

– RNC450 likely be limited by DMPG rather than ICSU
• Existing RNC capacity model cannot estimate the impact e.g.

increase in smart phone usage to the RNC CPU load, it is
correlating the CPU to the RNC fill rate
– Correlation between CPU load and throughput is not good in many
cases if there are smart phones
https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D422588692
Smartphone impact on RNC dimensioning
ICSU load – RNC CP rule
• List of relevant signalling events having impact on Control
Plane load.
– Pagings per second in BH
– NAS signalling messages per second in BH (incl. SMSs, LAC, RAC
updates, IMSI attaches/detaches, SCC, SRNS relocations)
– Soft Handovers per second in BH
– CS call attempts per second in BH
– PS call attempts per second in BH (both, RT and NRT, Rel99 and

HSDPA)
– DCH-FACH state transitions per second in BH
– HS-DSCH-FACH state transitions per second in BH
– FACH-PCH state transitions per second in BH
– Dedicated NBAP measurements per second in BH

ICSU load – RNC CP rule – Step 1/3
• Calculate aggregated loads, separately for CS/PS –related and common
procedures, using the following formulas (i – particular event) :
CS _ BHCA _ contribution   frequency[i ]  weight[i ]
i 0
PS _ BHCA _ contribution   frequency[i ]  weight[i ]

i 0
common _ BHCA _ contribution   frequency[i ]  weight[i ]

i 0
Weights (for CCP18-A

Event: HW) Weights (for CCP1D HW) Domain
Paging 39 26 Common
NAS signalling 1242 828 Common
SHO 1149 766 Common
CS call 2545 1697 CS
PS call 2409 1606 PS
DCH-FACH 833 555 PS
HS-DSCH-FACH 1113 742 PS
FACH-PCH 443 295 PS
NBAP measurement 29 19 Common

• Calculate “mixed BHCA limit” for concrete RNC Capacity Step according to
the following equation:
Mixed _ BHCA_ lim it  CS _ PS _ ratio * max_CS _ BHCA_  (1  CS _ PS _ ratio) * max_ PS _ BHCA
– where:
– max_CS_BHCA and max_PS_BHCA – BHCA limitations for concrete RNC capacity step
and inlude NAS signalling
– CS_PS_ratio has to be calculated using following formula:
CS _ only _ ratio
CS _ PS _ ratio 
CS _ only _ ratio  PS _ only _ ratio
 Where:
CS _ BHCA _ contribution
CS _ only _ ratio 
max_ CS _ BHCA  common _ BHCA _ contribution
PS _ BHCA _ contribution
PS _ only _ ratio 
max_ PS _ BHCA  common _ BHCA _ contribution

• Finally, check if calculated aggregated BHCA loads don’t exceed
mixed_BHCA_limit:
CS _ BHCA _ contribution  PS _ BHCA _ contribution  common _ BHCA _ contribution

1
mixed _ BHCA _ lim it

UE Forecast INPUT
• When forecasting the smart phone impact, there needs to be

information on the current number of UE types, their share
and growth rates
– E.g. scenarios “what if smart phones double within x months”
– UE categories 7,000,000
 Standard 6,000,000
Number of handsets
5,000,000
 Smart phones 4,000,000
Other
Symbian
 Dongles 3,000,000
Apple
RIM
Android
2,000,000
UE forecast
1,000,000
16,000,000
14,000,000 0
Au 1
12,000,000
Au 2
0
D 0
0
11
11
11
D 1
Fe 1
12
12
12
D 2
2
-1
-1
-1
-1
-1
-1
-1
n-
n-
g-
r-
r-
g-
b-
b-
ec
ec
ec
g
ct
ct
ct
Ap
Ap
Ju
Ju
Au
Fe
O
O
10,000,000 Standard Handsets
8,000,000 Smartphones
6,000,000 Dongles
4,000,000
Smart phones can be also
2,000,000
0 divided into different types
Jun-10
Jun-11
Jun-12
Aug-10
Aug-11
Aug-12
Oct-10
Dec-10
Feb-11
Feb-12
Apr-12
Apr-11
Oct-11
Dec-11
Oct-12
Dec-12

UE Profile INPUT
• Green values can be extracted from ICSU logs, red values by manually
matching model output to network statistics
• Idea is to match model output (RRC, paging, CS RABs, PS RABs, SHO
events..) to current number of events in RNC during busy hour
• Note that the raw profile from logs include only UEs that were active
during the log collection
– Since all UEs are not active, the profile is multiplied by an activity factor
– This is the main parameter that need to be manually matched

Traffic INPUT
• The traffic forecast in the RNC is needed to be able to forecast the fill rate
for the RNC
– Voice Erl
– Data Mbps
• This fill rate is compared to the ICSU/DMPG CPU load to see, if the load
caused by smart phones are limiting before the traffic

Result - Fill rate vs. CPU load
• Fill rate calculation and CPU load calculations are on dedicated sheets
per RNC type
– RNC2600 worksheet
– RNC450 worksheet
• Additional sheets can be copied in case more RNCs are analyzed or
different traffic scenarios are calculated
Note that also
other RNC
limitations need to
be checked
The tool in excel
RNC Forecast

The CPU model

ICSU and DMPG load model counters
• The signalling events can be calculated from counters with

following formula:
Events Counter Counter Name Fomula
M1001C66 RAB_STP_ATT_CS_VOICE
M1001C67 RAB_STP_ATT_CS_CONV
CS BHCA =(M1001C66 + M1001C67 + M1001C68 + M1001C599) / DURATION
M1001C68 RAB_STP_ATT_CS_STREA
M1001C599 RAB_STP_ATT_CS_VOICE_WPS
M1001C70 RAB_STP_ATT_PS_STREA
PS BHCA M1001C71 RAB_STP_ATT_PS_INTER =(M1001C70 + M1001C71 + M1001C72) / DURATION
M1001C72 RAB_STP_ATT_PS_BACKG
Paging M1003C36 REC_PAG_MSG =M1003C36 / DURATION
M1007C10 CELL_ADD_REQ_ON_SHO_FOR_RT =((M1007C10 + M1007C12) / (SHO RT) + (M1007C27 + M1007C29) / (SHO NRT)) /
M1007C12 CELL_REPL_REQ_ON_SHO_FOR_RT DURATION
SHO
M1007C27 CELL_ADD_REQ_ON_SHO_FOR_NRT
M1007C29 CELL_REPL_REQ_ON_SHO_FOR_NRT *) SHO RT and SHO NRT see below
DCH-FACH M1006C45 CELL_DCH_STATE_TO_CELL_FACH =M1006C45 / DURATION
HS-DCH-FACH M1006C154 SUCC_HS_DSCH_TO_FACH =M1006C154 / DURATION
M1006C48 CELL_FACH_STATE_CELL_PCH_UPD
FACH-PCH =(M1006C48 + M1006C47) / DURATION
M1006C47 CELL_FACH_STATE_CELL_PCH_INA
NAS M1001C0 RRC_CONN_STP_ATT =(M1001C0 - (CS BHCA) - (PS BHCA)) / DURATION
*)
M1007C0 ONE_CELL_IN_ACT_SET_FOR_RT
M1007C1 TWO_CELLS_IN_ACT_SET_FOR_RT =(M1007C0 + M1007C1 * 2 + M1007C3 * 3 - M1007C6 * 2) / (M1007C0 + M1007C1 +
SHO RT
M1007C2 THREE_CELLS_IN_ACT_SET_RT M1007C3 - M1007C6)
M1007C6 SOFTER_HO_DUR_ON_SRNC_FOR_RT
M1007C19 ONE_CELL_IN_ACT_SET_FOR_NRT
M1007C20 TWO_CELLS_IN_ACT_SET_FOR_NRT =(M1007C19 + M1007C20 * 2 + M1007C21 * 3 - M1007C25 * 2) / (M1007C19 +
SHO NRT
M1007C21 THREE_CELLS_IN_ACT_SET_NRT M1007C20 + M1007C21 - M1007C25)
M1007C25 SOFTER_HO_DUR_ON_SRNC_NRT
NBAP measurements M1005C148 DEDIC_MEAS_REPORT =M1005C148 / DURATION

CPU load model
• A proof of the model can be done comparing the estimated

CPU based on the signalling events and the weight and
compare that to the measured CPU taken from the RNC

RNC2600 ICSU Weights
• These weights are from NE

presentation on smart
phones (link)
• Base load has been

adjusted using the available
measurement data in the
RNC2600 ICSU sheet
– Could be adjusted in each case
in case there is need to

RNC450 ICSU and DMPG Weights
• Basically the UE profiles

are multiplied with number
of UEs to obtain number
of cost events
• The unit load is then
sumproduct of the cost
events and the costs,
divided by number of units
• Also a base load is
applied
• HS DMPG model is mostly
based on HS Erlangs,
while other models are
based only on the number
of events.

Counter and KPIs in RU10 for Reporting Suite
• Following counters and KPIs are needed at hourly level in

addition to the M592 unit load for ICSU and DMPG (individual
unit’s CPU load needed due to pool mapping)
RAB setup attempts for CS Voice calls RNC_346A
RAB Setup Attempts for PS I&B calls RNC_1071A Two reports:
rec_pag_msg (M1003C36)
One for counters and
Soft Handover Overhead for RT RNC_980B
KPIs
SHO Overhead for NRT RNC_1762A
cell_dch_state_to_cell_fach (M1006C45)
Other for the average
SUCC_HS_DSCH_TO_FACH (M1006C154)
and peak CPU load
cell_fach_state_cell_pch_ina (M1006C47)
cell_fach_state_cell_pch_upd (M1006C48)
rrc_conn_stp_att (M1001C0)
DEDIC_MEAS_REPORT (M1005C148)
RS reports RU10
cell_add_req_on_sho_for_rt (M1007C10)
cell_add_req_on_sho_for_nrt (M1007C27)
cell_del_req_on_sho_for_rt (M1007C11)
cell_del_req_on_sho_for_nrt (M1007C28)

Counter and KPIs in RU20 for Reporting Suite
• The KPI RNC_1071A does not exist in RU20

RS reports RU20
• These Customised report works for RU20

How to Upload xml Report in Reporting Suite
Use Report upload page

for uploading the xml file
XML reports for

Reporting Suite

How to Upload xml Report in Reporting Suite
• Select the report from the directory

Run the Report
• Select the correct RNC and reporting level

– e.g. Report level “RNC” and Time level “hourly”


Capacity - RNC Capacity Management - Smart Phone Impact

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Capacity - RNC Capacity Management - Smart Phone Impact

Загружено:

Авторское право:

Доступные форматы

RNC capacity management

CPU load analysis – Smart phone impact

For internal use only

• RNC unit load is forecasted based on

• The model was originally created for a customer case

• ICSU load model for RNC2600

• For RNC450 there is similar model for ICSU and DMPG

• Existing RNC capacity model cannot estimate the impact e.g.

– PS call attempts per second in BH (both, RT and NRT, Rel99 and

For internal use only

PS _ BHCA _ contribution   frequency[i ]  weight[i ]

common _ BHCA _ contribution   frequency[i ]  weight[i ]

Weights (for CCP18-A

For internal use only

For internal use only

CS _ BHCA _ contribution  PS _ BHCA _ contribution  common _ BHCA _ contribution

For internal use only

• When forecasting the smart phone impact, there needs to be

For internal use only

For internal use only

For internal use only

The tool in excel

For internal use only

For internal use only

• The signalling events can be calculated from counters with

For internal use only

• A proof of the model can be done comparing the estimated

For internal use only

• These weights are from NE

• Base load has been

For internal use only

• Basically the UE profiles

For internal use only

• Following counters and KPIs are needed at hourly level in

For internal use only

• The KPI RNC_1071A does not exist in RU20

For internal use only

Use Report upload page

XML reports for

For internal use only

• Select the report from the directory

For internal use only

• Select the correct RNC and reporting level

For internal use only

Вам также может понравиться