You are on page 1of 41

3G Baseband Dimensioning step by

step – Step 4: Performance


Monitoring
RU50EP1 BTS resource utilization monitoring (RAN2443)

Paweł Mitka
MBB CS NE SRAN

1 © Nokia 2014 MBB CS NE SRAN Paweł Mitka


Internal document
RAN 2443 BTS resource utilization monitoring
Feature scope
NEW Counters and measurement levels introduced: UPDATED Counters :

• M5011 – HSPA Scheduler level monitoring • M5008 – BTS level monitoring


• Counters: • Counters:
M5011C0-C11 M5008C22-C27
M5008C40-43
• M5012 – FSM Level Monitoring
• Counters: • M5006 – LCG level monitoring
M5012C0-C7 • Counters:
M5006C27-C38
NEW Counters :

• M5008 – BTS level monitoring


• Counters:
M5008C48-C50

• M5006 – LCG level monitoring


• Counters:
M5006C49-C70

4 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


Technical Details
Dependency Table (WCDMA)

Release information Sales information


RAS release RU50 EP1 BSW/ASW BSW
RNC release Support not required RAS SW
RAN
mcRNC release Support not required component
BTS Flexi release WN9.1 Licence control in
-
BTS Flexi Lite NE
Not planned
release Licence control
-
NetAct release NetAct 8 EP2 attributes
UE release Support not required

5 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


For internal use
Interdependencies
RAN2443 BTS Resource Utilization Monitoring

RAN2123 mandatory
Flexi BTS Gigabit
Baseband
• RU30 EP1
• BSW
• FSM software architecture
RAN2443
redesigned to increase module
BTS Resource Utilization
capacity
Monitoring

RAN2626 mandatory
Baseband Load Monitoring

• RU30 EP2
• BSW
• New counter set introduced

6 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


For internal use
Baseband monitoring related counters
RU30/RU40/RU50

M5006: M5008:
• Measurement: LCG level monitoring • Measurement: WBTS level monitoring
• Original product SW release WN7.0 1.0 • Original product SW release WN7.0 2.0
RU30 EP1 RU30 EP2
• Applicable for FSM rel.2 and FSM rel.3 • Applicable for FSM rel.2 and FSM rel.3
• Aggregation on LCG level • Aggregation on WBTS

Aggregation level
Aggregation level

FSM #1 FSM #2
FSM #1 FSM #2
LCG #1 LCG #2
LCG #1 LCG #2

7 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


Baseband monitoring related counters
RU50 EP1

M5011: M5012:
• Measurement: HSPA Scheduler Monitoring • Measurement: FSM Level Monitoring
• Original product SW release WN9.1 • Original product SW release WN9.1
RU50 EP1 RU50 EP1
• Applicable for FSM rel.2 and FSM rel.3 • Applicable ONLY for FSM rel. 2
• Aggregation on Scheduler level • Aggregation on FSM level

Aggregation level
Aggregation level

FSM #1 FSM #2
FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler LCG #1 LCG #2

8 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


Baseband monitoring related counters
Aggregation level

M5006: LCG M5008: WBTS


Aggregation level Aggregation level

FSM #1 FSM #2 FSM #1 FSM #2


LCG #1 LCG #2 LCG #1 LCG #2

M5011: HSPA Scheduler M5012: FSM

Aggregation level Aggregation level

FSM #1 FSM #2 FSM #1 FSM #2


HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler LCG #1 LCG #2

9 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5008: WBTS Aggregation level
Baseband monitoring related counters
M5008 FSM #1 FSM #2
LCG #1 LCG #2

Counter value
New Counter introduced:
HSDPA
• M5008C48: Licensed R99 CE in BTS HS-
HSDPA
HSDPA CCH PIC HSUPA HSUPA FA
• Counter Unit: Channel Element STATIC HYBRID CH
• Counter counts licensed R99CEs and R99CE capacity
coming from hybrid HSUPA PS license
Hybrid HSUPA + Licensed R99CE
• In case of over-licensing or use of Generic License Key
(no license limits set) this counter counts HW part
available for allocation of R99 traffic, i.e. counter shows
OR Counter value
resources that are left after HSDPA, PIC, CCH, static pre- R99 CE over-licensing:
reserved HSUA resource steps and HS-FACH allocations. HSDPA
• Hybrid HSUPA Processing Set equals to 48 R99CE HS-
HSDPA
HSDPA CCH PIC
CCH HSUPA FA
STATIC CH

R99CE licenses

10 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5008: WBTS Aggregation level
Baseband monitoring related counters
M5008 FSM #1 FSM #2
LCG #1 LCG #2
New Counters introduced:
M5008C49 Counter value
• M5008C49: Configured PIC subunits in BTS
HSDPA
• Counter Unit: subunits
HS-
• Counter accuracy is 3 digits after decimal point HSDPA PIC CCH HSUPA HSUPA FA
(e.g. 0.125 SU) STATIC HYBRID CH
• 1 PIC pool consumes 1 SU (HW rel.2 and 3)

• M5008C50: Configured HS-FACH subunits M5008C50 Counter value

• Counter Unit: subunits HSDPA


• Counter accuracy is 3 digits after decimal point HS-
(e.g. 0.125 SU) HSDPA PIC CCH HSUPA HSUPA
FA
STATIC HYBRID
• Up to 40 HS-FACH DL users can be defined per LCG CH
with minNumHsfachUsers parameter (up to 4
Resource Stesps can be commissioned)
• Every 10 HS-FACH DL users consumes 0.25 SU in
case of HW rel. 2 and 0.125 SU in case of HW rel.3
11 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2
New Counters introduced:

• M5012C0: MAX used Subunits for R99 in FSM


MAX used R99 subunits
• Counter Unit: subunits HSDPA
• Counter shows maximum usage of subunits for R99CE
(includes R99CE resources used for DCH and R99CE HSDPA
HSDPA HS- PIC HSUPA HSUPA
CCH
used for additional CCCH) FACH STATIC HYBRID
• Sample based (sample with maximum number of
subunits in sampling period which is 5.12 seconds)
• Calculated as max(UL,DL) R99CE consumption. HSDPA

With this counter and M5012C2 (Number of available MAX _ Used _ R99 _ SU
R99 Subunits in FSM), utilization ratio for R99 subunits R99 _ Util _ Ratio  100 
Num _ Avail _ R99 _ SU
can be calculated.

12 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced: Counter value

• M5012C2: Number of Available R99 Subunits in FSM HSDPA

• Counter Unit: subunits HSDPA


HSDPA CCH PIC HSUPA HSUPA
STATIC HYBRID
• Counter shows the min(HW capacity and Licensed capacity
available for R99CE in the FSM) HSDPA
• Licensed capacity is the sum of: Hybrid HSUPA + Licensed R99CE
• Number of dedicated R99 CE licenses from all LCGs
present in FSM
• R99CE capacity of hybrid HSUPA present in FSM (1 OR Counter value
subunit per each hybrid HSUPA PS) R99 CE over-licensing:
• Number of licensed R99 CEs in the common pool HSDPA
(current usage not considered)
• Counter shows current allocation and changes when the HSUPA HSUPA
HSDPA
HSDPA CCH PIC
CCH
configured or licensed capacity per FSM changes. STATIC HYBRID

Licensed R99CE

13 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:

• M5012C1: Maximum used Subunits for HSUPA in FSM


MAX used HSUPA subunits
• Counter Unit: subunits HSDPA
• Counter shows actual HSUPA resource step usage (only
active HSUPA resources are shown – resources HSDPA
HSDPA CCH PIC HSUPA HSUPA HSUPA
allocated for HSUPA but currently not used by HSUPA STATIC HYBRID
users are not shown.
• Sample based (sample with maximum number of
subunits in sampling period 5.12 seconds) HSDPA

With M5012C1 counter and M5012C3 (Number of MAX _ Used _ HSUPA _ SU


HSUPA _ Util _ Ratio  100 
available HSUPA Subunits in FSM), utilization ratio for Num _ Avail _ HSUPA _ SU
HSUPA subunits can be calculated.

14 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:


Counter value
• M5012C3: Number of Available HSUPA Subunits in HSDPA
FSM HS-
HSDPA
HSDPA CCH PIC HSUPA HSUPA
FA
STATIC HYBRID
• Counter Unit: subunits CH
• Counter shows the min(HW capacity and Licensed capacity HSDPA
available for HSUPA per LCG). If more than one LCGs have
HSUPA resources on FSM then calculated values are HSUPA Processing Sets
summed up.
• Licensed capacity is the sum of HSUPA resource steps which
can be allocated for HSUPA processing with HSUPA
OR Counter value
HSUPA over-licensing:
Processing Set licenses allocated to schedulers of the FSM.
• Counter shows current allocation and changes when the HSDPA
configured or licensed capacity per FSM changes. HS-
• HSUPA Processing Sets are mapped to HW resources with HSDPA
HSDPA CCH PIC
CCH HSUPA HSUPA FA
use of Nokia Internal tables STATIC HYBRID CH
• Up to 15 subunits can be used for HSUPA traffic processing in
case of SM rel. 2.
• HS-FACH resources cannot be collocated with HSUPA HSUPA Processing Sets
resources
15 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:

• M5012C3: Number of Available HSUPA


Subunits in FSM
• Example: HSDPA
2 system modules HW rel.2, 2 LCGs, 4 HSUPA
Processing Sets HSDPA
• In case when part of HW resources for
LCG#1 is allocated on second SM, those
resources are not shown in a counter as
available for HSUPA usage.
Counter value Counter value

HSUPA HSUPA
HSDPA HSDPA
HYBRID HYBRID

LCG#1 LCG#2

16 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2
New Counters introduced:
Counter value
• M5012C4: Configured HSDPA Subunits in FSM
HSDPA
• Counter Unit: subunits HS-
• Counter shows the total number of configured subunits for HSDPA
HSDPA CCH PIC FA HSUPA HSUPA
HSDPA processing in FSM. In case when there are no HW CH STATIC HYBRID
resources available for commissioned throughput steps, HSDPA
counter shows actually allocated subunits.
• Allocated subunits is calculated form Subunits_for_HSDPA
formula • Results:
• Subunits_for_HSDPA = Max {Round up ((2 * MIMO cells +
• Example: non-MIMO cells )/ 6) + 1 ;
• 2 System Modules, Subunits_for_HSDPA_throughput } + number of LCGs *
• 2 LCGs (60%,40% BB HW capacity, defined with 0.25
MAX HW Capacity parameter), where: Subunits_for_HSDPA_throughput - commissioned
• In both cases 3 MIMO cells resources for HSDPA
• 2 schedulers on each FSM configured with
throughput step 6 – 84 Mbps maximum HSDPA • Subunits_for_HSDPA = Max {Round up ((2 * 3 + 0 )/ 6) + 1
scheduler throughput per FSM. ; 2} + 1 * 0.25 = 2.25

17 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5012: FSM Aggregation level
Baseband monitoring related counters
M5012 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:


M5012C7 M5012C5 M5012C6
• M5012C5: Configured PIC Subunits in FSM HSDPA
• Up to 2 PIC pools per SM can be configured (max 2SU) HS-
• PIC pools are allocated on SM where HSPA schedulers HSDPA
HSDPA CCH PIC FA
for that LCG exists HSDPA CH

• M5012C6: Configured HS-FACH Subunits in FSM Allocation Examples:


• Up to 4 resource steps can be allocated per LCG with • HSDPA activated on both System Modules
minNumHsfachUsers parameter (up to 4 Resource
Stesps can be commissioned) HS HS
D CCH PIC FSM #1 FSM #2 D CCH PIC
• Each resource step consumes of 0.25 SU which allows FSM #1 FSM #2 PA
PA
for up to 10 HS-FACH users.
LCG #1 LCG #2
• HS-FACH resources are allocated on SM where HSPA
schedulers for LCG exists • HSDPA activated on one System Module

• M5012C7: Number of used CCCH Subunits in FSM HS


D CCH PIC FSM #1 CCH FSM #2
• Additional CCCH resources are calculated, resources PA
FSM #1 FSM #2
included in HW price are excluded.
LCG #1 LCG #2
18 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

New Counters introduced:


• Sample based
• Integer number
• M5011C0: Maximum Number of HSDPA Users in Scheduler
• M5011C6: Maximum Number of HSUPA Users in Scheduler • Average definition:
Summing up all samples in each
• M5011C1: Average Number of HSDPA Users in Scheduler measurement period and dividing
• M5011C7: Average Number of HSUPA Users in Scheduler by number of samples

• Maximum definition:
The sample with maximum form
• M5011C3: Maximum HSDPA throughput in Scheduler • Mbit/s all the samples in the
• M5011C9: Maximum HSUPA throughput in Scheduler • Accuracy: 3 digits measurement period
after comma
• Updated over the measurement
• M5011C4: Average HSDPA throughput in scheduler
• M5011C10: Average HSUPA throughput in scheduler period
• Sampling interval: 5.12 sec

19 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

New Counters introduced:

• M5011C2: Available Number of HSDPA Users in Example cont.:


Scheduler • In case of HW rel. 3. – normal HSPA for LCG1,
• Counter shows the min(scheduler capabilities and License small HSPA for LCG2, small HSPA for LCG3:
distribution)
• License distribution refers to sum of final amount of licenses LCG1: Scheduler #1 = commissioning + common=
assigned to LCGs based on commissioning parameters and =25% * 72 + (100% - 25% -25%)*72 = 18 + 36 = 54
initial common pool. LCG1: Scheduler #2 = commissioning + common=
• Counter is updated when BTS HW capacity, HSDPA =25% * 72 + (100% - 25% -25%)*72 = 18 + 36 = 54
configuration or HSDPA licensed capacity is changed.
• Scheduler capability: 240 users LCG2: Scheduler #1 = commissioning + common=
• License distribution example: 3 LCGs, 1 BTS PS 3 ie. =25% * 72 + (100% - 25% -25%)*72 = 18 + 36 = 54
72 users.
LCG3: Scheduler #1 = commissioning + common=
=0% * 72 + (100% - 25% -25%)*72 = 36

In this scenario license distribution is limiting factor for


every scheduler
20 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

• M5011C2: Available Number of HSDPA Users in


Scheduler

Example cont.:
• In case of HW rel. 2. – 2 System Modules, 2 schedulers
per module, 1 HSDPA PS 3

FSM#1 Scheduler 1 = LCG1 licenses + LCG2 licenses +


common pool = 25% * 72 + 25% * 72 + (100% - 25% -
25%)*72 = 18 + 36 = 72

FSM#1 Scheduler 2 = 72

FSM#2 Scheduler 1 = common pool = (100% - 25% -


25%)*72 = 36
HSDPA 1 HSDPA 1
FSM#2 Scheduler 2 = 36 FSM #1 FSM #2
FSM HSDPA
#1 2 FSM #2 HSDPA 2

LCG #1 LCG #2 LCG #3

21 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

New Counters introduced:

• M5011C5: Available HSDPA Throughput in • Scheduler licensed throughput is calculated in following way:
Scheduler Scheduler _ licensed _ throughput 
 
• Counter shows the min(scheduler licensed  
( Number_of_HSDPA_Proc essing_Set s _ 2  
throughput; allocated HSDPA scheduler  
Round _ down  4  Number_of_HSDPA_Proc essing_Set s_3)    21Mbps 
throughput)  
  Scheduler _ HSDPA _ throughput _ step 

  
• Allocated HSDPA scheduler throughput is based   Total _ number _ of _ throughput _ step _ per _ BTS  

on commissioned throughput steps • Example for FSME 1 Scheduler ID 1
(2 x HSDPA Processing Sets 3 and 1x HSDPA Processing Sets 2 :

Scheduler _ licensed _ throughput 


  86.4  
Round _ down (1  4  2)      21Mbps  
  259.2  
  1 
 Round _ down (9)      21Mbps   63Mbps 
  3 
22 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

New Counters introduced:

• M5011C8: Available HSUPA Users in Scheduler • If after calculation the sum of HSUPA BTS Processing Sets
• M5011C11: Available HSUPA Throughput in Scheduler is lower than total number of commissioned HSUPA BTS
Processing Sets, then remaining HSUPA PS is allocated
• Counters shows the min(HW resources, licenses, scheduler iteratively starting from LCG with the lowest ID
capabilities)
• Licenses are assigned based on commissioned values: • Example:

LCG#1  RoundDown (0.34  6)  2


LCG#2  RoundDown (0.33  6)  1
and formula:
LCG#3  RoundDown (0.33  6)  1
LCG#x_Number_of_HSUPA_Processi ng_Sets 
• LCG#1 and LCG#2 in this example gets additional 1 licenses
 RoundDown ( Share _ of _ HSUPA _ Licenses _ LCG# x  each:
 Number _ of _ Available _ HSUPA _ PS _ per _ BTS ) LCG#1 =3, LCG#2=2, LCG#3=1

23 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5011: Scheduler Aggregation level
Baseband monitoring related counters
M5011 FSM #1 FSM #2
HSDPA HSUPA HSDPA HSUPA
Scheduler Scheduler Scheduler Scheduler

New Counters introduced:

• M5011C8: Available HSUPA Users in Scheduler • HW resources refers to initial amount of the HW resources
• M5011C11: Available HSUPA Throughput in Scheduler available for HSUPA Subunits allocation
HSDPA
• Counters shows the min(HW resources, licenses, scheduler
capabilities) HSDPA HSUPA HSUPA
• In case of SM rel2 – 40 HSUPA users per one subunit as HYBRID STATIC
maximum is assumed.
• In case of SM rel3 – 80 HSUPA users per one subunit as LCG1 LCG2
maximum is assumed.
• In case of SM rel2 – 11.6 Mbps per one subunit as • Example: 4 Subunits left for HSUPA allocation, HW rel.3, Normal
maximum is assumed. HSPA, 6 HSUPA PS 1.
• In case of SM rel3 – 33 Mbps per one subunit as maximum • Max 240 active users, – scheduler capability
is assumed. • 34.8 Mbps Throughput and 144 users - licenses
• 132 Mbps and 320 users – HW resources
• Available HW resources does not comprise those allocated • Result:
for HSDPA, CCCH free and additional, PIC, HS-FACH 34.8 Mbps Available HSUPA Throughput in Scheduler
• HS-FACH resources cannot be collocated with HSUPA 144 Available HSUPA Users in Scheduler
resources

24 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:


• Sample based
• Integer number
• M5006C55: Maximum Number of HSDPA Users in LCG
• M5006C58: Maximum Number of HSUPA Users in LCG • Average definition:
Summing up all samples in each
• M5006C56: Average Number of HSDPA Users in LCG measurement period and dividing
• M5006C59: Average Number of HSUPA Users in LCG by number of samples

• Maximum definition:
The sample with maximum form
• M5006C61: Maximum HSDPA throughput in LCG all the samples in the
• M5006C64: Maximum HSUPA throughput in LCG measurement period
• Updated over the measurement
• M5006C62: Average HSDPA throughput in LCG
• M5006C65: Average HSUPA throughput in LCG period
• Sampling interval: 5.12 sec

26 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counter introduced:

• M5006C57: Available number of HSDPA users in


LCG

• Counters shows the min(Licensed HSDPA users,


HSDPA user scheduler capability)
• HSDPA user scheduler capability – is calculated based
on maximum number of HSDPA users that can be
served by scheduler and number of shedulers to which
LCG has an access. (e.g. in case of SM rel. 2 and 2
schedulers activated it means that number of HSDPA
users is 480 per each LCG (that have an access to
those schedulers)

• Licensed HSDPA users – is the maximum number of HSDPA 1 HSDPA 1


FSM #1 FSM #2
HSDPA users based on Processing Sets available in FSM HSDPA
#1 2 FSM #2 HSDPA 2
LCG (the sum of LCG dedicated resources and
LCG #1 LCG #2 LCG #3
common HSDPA users pool)
27 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:

• M5006C60: Available number of HSUPA users in LCG • If after calculation the sum of HSUPA BTS Processing Sets
• M5006C66: Available HSUPA throughput in LCG is lower than total number of commissioned HSUPA BTS
Processing Sets, then remaining HSUPA PS is allocated
• Counters shows the min(HW resources, licenses, scheduler iteratively starting from LCG with the lowest ID
capabilities)
• Licenses are assigned based on commissioned values: • Example:

LCG#1  RoundDown (0.33  6)  1


LCG#2  RoundDown (0.33  6)  1
LCG#3  RoundDown (0.34  6)  2
LCG#x_Number_of_HSUPA_Processi ng_Sets 
 RoundDown ( Share _ of _ HSUPA _ Licenses _ LCG# x  • LCG#1 and LCG#2 in this example gets additional 1 licenses
 Number _ of _ Available _ HSUPA _ PS _ per _ BTS ) each:
LCG#1 =2, LCG#2=2, LCG#3=2

28 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counters introduced:

• M5006C60: Available number of HSUPA users in LCG • HW resources refers to initial amount of the HW resources
• M5006C66: Available HSUPA throughput in LCG available for HSUPA Subunits allocation
HSDPA
• Counters shows the min(HW resources, licenses, scheduler
capabilities) HSDPA HSUPA HSUPA
• In case of SM rel2 – 40 HSUPA users per one subunit as HYBRID STATIC
maximum is assumed.
• In case of SM rel3 – 80 HSUPA users per one subunit as LCG1 LCG2
maximum is assumed.
• In case of SM rel2 – 11.6 Mbps per one subunit as • Example: 4 Subunits left for HSUPA allocation, HW rel.3, Normal
maximum is assumed. HSPA, 6 HSUPA PS 1 per LCG.
• In case of SM rel3 – 33 Mbps per one subunit as maximum • Max 240 active users, – scheduler capability
is assumed. • 34.8 Mbps Throughput and 144 users - licenses
• 132 Mbps and 320 users – HW resources
• Available HW resources does not comprise those allocated • Result:
for HSDPA, CCCH free and additional, PIC, HS-FACH 34.8 Mbps Available HSUPA Throughput in Scheduler
• In case where not whole SU is available, number of users 140 Available HSUPA Users in Scheduler
and throughput is calculated proportionally to available
resources (part of subunit)
29 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counter introduced:

• M5006C63: Available HSDPA throughput in LCG • Scheduler licensed throughput is calculated in following way
Scheduler _ licensed _ throughput 
• Counter Unit: Mbps
 
• Counters shows the sum of HSDPA schedulers’ throughput  
from all HSDPA schedulers to which LCG has access. ( Number_of_HSDPA_Proc essing_Set s _ 2  
 
• HSDPA scheduler throughput is min(scheduler licensed Round _ down  4  Number_of_HSDPA_Proc essing_Set s_3)    21Mbps 
throughput; allocated HSDPA scheduler throughput)  
  Scheduler _ HSDPA _ throughput _ step 

 
  Total _ number _ of _ throughput _ step _ per _ BTS  
• Allocated HSDPA scheduler throughput is based on
commissioned throughput steps: • Example for FSME 1 Scheduler ID 1
(2 x HSDPA Processing Sets 3 and 1x HSDPA Processing Sets 2 :

Scheduler _ licensed _ throughput 


  86.4  
Round _ down (1  4  2)      21Mbps  
  259.2  
  1 
 Round _ down (9)      21Mbps   63Mbps 
  3 
30 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

NEW counters showing utilization ratio of HSUPA/HSDPA Processing Sets:

Average definition:
• M5006C67: Maximum HSDPA Processing Sets Utilization Ratio
Summing up all samples in each measurement
• M5006C68: Average HSDPA Processing Sets Utilization Ratio
period and dividing by number of samples
Maximum definition:
• M5006C69: Maximum HSUPA Processing Sets Utilization Ratio
The sample with maximum form all the samples in
• M5006C70: Average HSUPA Processing Sets Utilization Ratio
the measurement period

• Counters based on two factors – Throughput Utilization Ratio and Users


utilization ratio – both are calculated and average is taken as a sample.
LCG _ HSPA _ Throghput _ Sample Based on M5006C61/M5006C64 Sample
LCG _ HSPA _ Thr _ Util  100 
LCG _ Avail _ HSPA _ Throughput M5006C63/M5006C66

LCG _ HSPA _ Users _ Sample Based on M5006C55/M5006C58 Sample


LCG _ HSPA _ User _ Util  100 
LCG _ Avail _ HSPA _ Users M5006C57/M5006C60

LCG _ HSPA _ PS _ Util _ Sample  AVG( LCG _ HSPA _ Thr _ Util; LCG _ HSPA _ User _ Util )

31 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counter introduced:

• M5006C45: Allocated HSDPA Subunits in LCG Allocated HSDPA Subunits in LCG

• Counter Unit: subunits HSDPA HW rel. 2

• In case of Flexi HW rel. 2. where HSDPA schedulers are HSDPA


HSUPA HSDPA
common, number of cells principle is used. HSDPA SUs are
divided according to number of LCG cells.
• If LCG has HSDPA schedulers on two System Modules, LCG1 LCG2
resources are summed up.
• For Flexi HW rel. 3 HSDPA scheduler is LCG specific

• Example:
2 LCGs, one SM rel. 2; 3 and 6 cells per LCG configured. LCG#1  4.5  (3 / 9)  1.5SU
HSDPA SUs coming from allocation (commissioning) is
4.5SU LCG#2  4.5  (6 / 9)  3SU

32 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2
New Counter introduced:

• M5006C49 - 54: LCG HW Resource Utilization


• Nominator comprise resources allocated for Rel99 traffic,
CLASS 1 (0 – <50) %
HSUPA (actively used), additional CCCH, PIC, HS-FACH
CLASS 2 (50 – <70) %
CLASS 3 (70 – <80) % LCG1
CLASS 4 (80 – <90) % HS-
CLASS 5 (90 – <100) % HSDPA
HSDPA PIC CCH HSUPA FA
CH
CLASS 6 {100} %

• Counter Unit: subunits


Nominator
• Counter type: SUM
• Denominator comprise the HW assigned to LCG without
• Counters show how many utilization rate samples have HSDPA resources and free CCCH
been detected within the range LCG1
• Counters are incremented when the sample of the
utilization rate is within respective class range HS-
HSDPA
HSDPA PIC CCH HSUPA FA
CH
HW _ capacity _ used _ by _ traffic _ in _ LCG
HW_Res_Uti l_Sample   100%
Available _ HW _ capacity _ in _ LCG
Denominator
33 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
Please fill in a short survey
Your feedback is valuable to us!
KIND REQUEST TO YOU:
PLEASE FILL IN THE SURVEY NOW
LINK DISTRIBUTED IN THE CHAT PANEL

To get the certificate proving participation in the training please login


with your NSN credentials and download the certificate after
submitting yours marks.

34 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


For internal use
Backup

35 © Nokia 2014 MBB CS NE SRAN Paweł Mitka


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

New Counter introduced: Hardware available for Rel99 CE allocation


HSDPA
HSDPA
HS-
• M5006C46: Number of R99 Plus HSUPA HSDPA
HSDPA PIC CCH
HSUPA
FA
HYBRID
Overlapping Subunits in LCG CH

• Counter Unit: subunits


Licensed R99CE
• Counter shows the resources that are overlapping between
R99 CE licenses and HSUPA Processing Set licenses.
+
Hardware available for HSUPA
HSDPA
HSDPA
• Overlapping licenses are calculated as sum of subunits
HS-
licensed for Rel 99 traffic and HSUPA traffic (in case of over- HSDPA HSUPA
FA
HSDPA PIC CCH
licensing available hardware is taken into account). Then from HYBRID
CH
the calculated sum, subunits available for Rel99 traffic and


HSUPA traffic allocation are subtracted.
HSDPA, PIC, free-CCH and HS-FACH resources are NOT - HSUPA PS Licenses
HSUPA
HS-
considered. HSDPA
HSDPA PIC CCH FA
HYBRID
• If the result of calculation is lower than zero, counter reports CH
zero.
HW available for allocation
=
COUNTER VALUE
36 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2
HSDPA
HSDPA
New Counter introduced: HS-
HSDPA HSUPA
HSDPA PIC CCH FA
HYBRID
• M5006C47: Average Used R99 from overlapping CH

Subunits in LCG
Subunits used by Rel99 traffic
• Counter Unit: subunits - HS-
• Counters show the utilization by Rel99 traffic of resources HSDPA
HSDPA PIC CCH
HSUPA
FA
HYBRID
that are overlapping between R99 CE licenses and HSUPA CH
Processing Set licenses (see M5012C2).
• Counters are calculated as the subtract of used subunits Rel99 CE Licenses
and licensed resources, and then overlapping resources


are added.
If the result of calculation is lower than zero, counter reports
+ HS-
zero. HSDPA
HSDPA PIC FA
CH
• Hybrid resources used by Rel99 traffic are not taken into
account
Overlapping resources

COUNTER VALUE
=
37 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2
HSDPA
HSDPA
New Counter introduced: HS-
HSDPA HSUPA
HSDPA PIC CCH FA
HYBRID
• M5006C48: Average Used HSUPA from overlapping CH

Subunits in LCG
Subunits used by HSUPA traffic
• Counter Unit: subunits - HS-
• Counters show the utilization by HSUPA traffic of resources HSDPA
HSDPA PIC CCH
HSUPA
FA
HYBRID
that are overlapping between R99 CE licenses and HSUPA CH
Processing Set licenses (see M5006C46).
• Counters are calculated as the subtract of used subunits HSUPA PS Licenses
and licensed resources, and then overlapping resources
are added. +
• If the result of calculation is lower than zero, counter reports HS-
zero. HSDPA
HSDPA PIC FA
CH
• Hybrid resources used by HSUPA traffic are taken into
account
Overlapping resources

=
COUNTER VALUE
38 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
Changes in existing counters

39 © Nokia 2014 MBB CS NE SRAN Paweł Mitka


M5006: LCG Aggregation level
Baseband monitoring related counters
M5006 FSM #1 FSM #2
LCG #1 LCG #2

Changes in Counters introduced:


• HW resources for HSDPA/HSUPA schedulers refers to initial
• M5006C27-C38 BTS HSPA user amount utilization
amount of the HW resources available for HSDPA/HSUPA
ratio
Subunits allocation
• Counters Unit: Integer number
HSDPA
• Counters corrected for over-licensing cases, i.e. in BTS it is
possible to license more HSPA users than it is supported by HSDPA HSUPA
HSUPA
HW capacity.
• BEFORE introduction of RAN2443:
In case of over-licensing counters showed low utilization LCG1 LCG2
rates.
• AFTER introduction of RAN2443:
Calculation is done as a ratio: in nominator current number of
HSDPA/HSUPA users is used. Denominator is calculated as
min(number of licensed HSUPA/HSDPA users; allocated
scheduler capacity limit of HSDPA/HSUPA users) In case
that LCG is handled by more than one scheduler, maximum
number of users coming from all schedulers is added.
40 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5008: WBTS Aggregation level
Baseband monitoring related counters
M5008 FSM #1 FSM #2
LCG #1 LCG #2

Changes in Counters introduced: • AFTER introduction of RAN2443:


Limiting factors taken into account, in cases of HW limitation
(licensed capacity higher than available hardware resources),
• M5008C22-C27 HSDPA/HSUPA Processing Sets
HW capacity is denominator that is taken into calculations.
Utilization Ratio
HSDPA Processing Set Utilization based on two conditions:
Throughput and Number of Users. In each sample both
• Counters Unit: Percentage conditions calculated and average taken into counter.
• Counters corrected in order to take into account all limiting In calculation for MIN/AVG/MAX HSUPA Processing Sets
factors in the BTS. In BTS it is possible to configure more Utilization Ratio (M5008C25-C27) three conditions taken into
HSPA users and throughput than can be supported by account and average of them used in each sample:
existing HW resources. 1.Percentage of number of HSUPA users in BTS, calculated as
• BEFORE introduction of RAN2443: ratio of the current HSUPA users to the licensed number of
Not all limiting factors taken into account, counters showed HSUPA users.
low utilization rates in cases where denominator wasn’t 2.Percentage of number of HSUPA throughput, calculated as
calculated appropriately (e.g. licensed capacity used in case ratio of the current HSUPA throughput to the licensed HSUPA
of hardware limitation) throughput.
Processing Set Utilization based on following conditions: 3.Percentage of Baseband resources used to handle HSUPA
Throughput, No. of users and additionally, in case of HSUPA, load calculated as ratio of the used Subunits* to the licensed
hardware consumption. In each sample maximum from all of subunits. (*only HSUPA resources that are actually assigned to
the conditions used. the users at the moment are taken into account)
41 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014
M5008: WBTS Aggregation level
Baseband monitoring related counters
M5008 FSM #1 FSM #2
LCG #1 LCG #2

Changes in Counters introduced: • AFTER introduction of RAN2443:

Limiting factors taken into account


• M5008C40 Configured HSDPA Users
• M5008C41 Configured HSUPA Users In calculation for Configured HSDPA Users:
• Number of configured users is calculated as the min(Processing
• Counters Unit: Integer Sets commissioned by user; number of allocated
schedulers*maximum number of users per scheduler).
• Counters corrected in order to take into account all limiting PS commissioned by user is taken from parameters:
factors in the BTS. In BTS it is possible to configure more numberOfHSDPASet1, numberOfHSDPASet2,
HSPA users than can be supported by existing HW numberOfHSDPASet3
resources.
In calculation for Configured HSUPA Users:
• BEFORE introduction of RAN2443: • Number of configured users is calculated as the min(HW resources;
Not all limiting factors taken into account, counters showed Processing Sets commissioned by user; number of allocated
low utilization rates in cases where denominator wasn’t schedulers*maximum number of users per scheduler).
calculated appropriately (e.g. commissioned PS commissioned by user is taken from parameter:
HSDPA/HSUPA PS used in case of hardware limitation) numberOfHSUPASet1
HW resources are the resources available for HSUPA allocation

42 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014


M5008: WBTS Aggregation level
Baseband monitoring related counters
M5008 FSM #1 FSM #2
LCG #1 LCG #2

Changes in Counters introduced: • AFTER introduction of RAN2443:

In calculation for Configured HSDPA throughput for SM rel 2:


• M5008C42 Configured HSDPA Throughput
• Configured throughput is calculated as the min(Processing Sets
• M5008C43 Configured HSUPA Throughput commissioned by user*; sum of schedulers throughput; allocated
resources**).
• Counters Unit: Integer Allocated resources is calculated form Subunits_for_HSDPA formula
(please see M5012C4 counter description)
• Counters corrected in order to take into account all limiting
factors in the BTS. In BTS it is possible to configure more In calculation for Configured HSDPA throughput for SM rel 3:
HSPA throughput than can be supported by existing HW • Number of configured users is calculated as the min(Processing
resources. Sets commissioned by user*; sum of schedulers throughput**).

AFTER introduction of RAN2443:


In calculation for Configured HSUPA throughput : * PS commissioned by user is taken from parameters:
• Number of configured users is calculated as the min(HW numberOfHSDPASet1, numberOfHSDPASet2,
resources; Processing Sets commissioned by user;). numberOfHSDPASet3
* PS commissioned by user is taken from parameter: ** Sum of schedulers throughput is calculated as the sum of
numberOfHSUPASet1
allocated throughput steps for each scheduler
HW resources are the resources available for HSUPA
allocation
43 © Nokia 2014 MBB CS NE SRAN Paweł Mitka 22/10/2014