Processing Sets

Nokia Siemens Networks © CONFIDENTIAL APPROVED 3.0

Technical Support Note TS-3GBTS-SW-0157 Baseband load monitoring counters in WN7.0 1.x and WN7.0 2.x releases WN7.0 1.x, WN7.0 2.x This document contains following type of information

Informative X Preventive Corrective Additional categorization Urgent Security Release Upgrade X SW Update Information is classified as Internal Public X Customer Specific


Table of Contents 1. Validity......................................................................................................................................... 3 2. Compatibility / Dependencies to other products ........................................................................... 3 3. Keywords .................................................................................................................................... 3 4. HSPA and Rel99 baseband load monitoring in WN7.0 ................................................................ 3

4.1 Introduction ..................................................................................... 3 4.2 Basic principles of Flexi BTS Baseband load monitoring ................. 4 4.3 Flexi BTS Baseband Load Monitoring in WN7.0 1.x ........................ 4

4.3.1 Monitoring of R99 traffic .................................................................. 4 4.3.2 Monitoring of HSUPA traffic ............................................................. 5 4.3.3 Monitoring of HSDPA traffic ............................................................. 5 4.3.4 Calculation of used HW resources .................................................. 6

4.4 Flexi BTS Baseband load monitoring in WN7.0 2.x ......................... 7 4.4.1 Baseband load monitoring using M5008 counters ........................... 8

4.4.1.1 Monitoring of available BTS level capacity .. 8

4.4.1.2 Monitoring of the used Baseband resources 9

4.4.1.3 Monitoring of Baseband usage ratio ............ 10

4.4.1.4 Monitoring of Baseband total HW capacity usage 11

4.4.2 Examples ...................................................................................... 12 4.4.3 Issues with M5008 counters recognized during pilots of WN7.0 2.0 ...................................................................................................... 14 4.4.4 Correction plan .............................................................................. 15

Contact:

Contact your local Nokia Siemens Networks support

Summary of changes:

dd-mmm-yyyy <Version> <Summary of changes> 17-Feb-2012 1.0 First approved version 05-June-2012 2.0 Second version: Chapter 4.3.1 Notes updated. 25-Jan-2013 3.0 Third version: Chapter 4.4 updated


Purpose

The purpose of this document is to highlight the basic monitoring principle of BTS Baseband monitoring for both WN7.0 1.0 and WN7.0.2.0. Along with the common principle the monitoring possibilities for both releases are shortly mentioned. All the documented monitoring possibilities can be found in details in the WCDMA Capacity Management documents for each corresponding release:

• for WN7.0 1.0 the document version is “issue 2C” (RU30 EP1 version (*), pages 38-45)

• for WN7.0 2.0 the document version is “issue 2D” (RU30 EP2 version, pages 38-47)

1. VALIDITY

Product Category 1 Flexi Multiradio BTS WCDMA X UltraSite UltraSite EUBB

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

N.A

3. KEYWORDS

WN7.0, Baseband load monitoring

4. HSPA AND REL99 BASEBAND LOAD MONITORING IN WN7.0

4.1 Introduction

WN7.0 introduces a new baseband concept for Flexi BTS HW Rel.2. The new architecture is removing the channel element (CE) based capacity allocation for HSPA. Instead dimensioning of HSPA is based on different HSPA processing sets (PS). Rel.99 traffic is licensed with Rel.99 Channel Elements, with the same capacity as before. The HSPA processing sets are capacity units, defined by total BTS throughput and total number of users in BTS in the following way:

For HSDPA:

• HSDPA BTS Processing Set 1: 32Users/7.2Mbps • HSDPA BTS Processing Set 2: 72Users/21Mbps • HSDPA BTS Processing Set 3: 72Users/84Mbps

For HSUPA:

• HSUPA BTS Processing Set: 24Users/5.8Mbps

In the next chapters Flexi BTS HW Rel. 2 Baseband load monitoring principles in WN7.0 1.0 and WN7.0 2.0 are shortly described.


4.2 Basic principles of Flexi BTS Baseband load monitoring

When attempting to monitor Baseband load of Flexi BTS HW Rel. 2 two cases are to be considered:

1. No baseband pools defined i.e. only one LCG: in this case LCG and BTS level monitoring are the same.

a. If BTS/LCG license utilization is high then first check whether all HW resources are licensed

b. If all HW is licensed and BB resource utilization is still at high level network re-dimensioning is necessary

2. Multiple baseband pools i.e. 2-4 LCGs: Monitoring still should start from LCG level with the following identified cases

a. There are high utilization rates in one/some of the LCGS but not all of them - please consider re-commissioning of LCG/System Module resources

b. There are high utilization rates in all of the LCGs - please check whether all HW resources are licensed

c. If all HW is licensed and BB resource utilization is still at high level network re-dimensioning is necessary

Counters and KPIs related to the cases given above are listed in the WCDMA Capacity Management documents for each corresponding release:

• for WN7.0 1.0 the document version is “issue 2C” (RU30 EP1 version (*), pages 38-45) • for WN7.0 2.0 the document version is “issue 2D” (RU30 EP2 version, pages 38-47)

NOTEs!

WN7.0 1.0 GAPS No direct possibility to estimate Baseband HW and license utilization. No direct possibility to obtain BTS level aggregated counters for R99 CE and HSPA throughput. WN7.0 2.0 introduces M5008 measurement set to close the GAP.

4.3 Flexi BTS Baseband Load Monitoring in WN7.0 1.x

4.3.1 Monitoring of R99 traffic

As mentioned in Capacity Management document for WN7.0 1.0 pages 38-45, the R99 traffic in terms of available and used Rel.99 CEs can be monitored using M5006 counters. In order to obtain BTS level R99 CEs usage average type counters for R99 CE availability and usage can be summed up over existing LCGs. NOTEM5006C0: Counter shows the maximum amount of licensed R99 CE capacity + R99 CE capacity of first HSUPA processing step (=48 R99 CEs)


4.3.2 Monitoring of HSUPA traffic

In WN 7.0 1.x Baseband HSUPA load can be examined directly in terms of number of users and BTS level HSUPA throughput over existing counters. The amount of users can be monitored by applying dedicated RNC counters:

• M1031C1 MAX NUMBER OF HSUPA USERS PER WBTS • M1031C3 SUM OF HSUPA USERS PER BTS • M1031C4 HSPA USERS PEW WBTS DENOMINATOR

The average number of HSUPA users can be calculated=

M1031C3 SUM OF HSUPA USERS PER WBTS M1031C4 HSPA USERS PER WBTS DENOMINATOR

For HSUPA throughput calculation the following counters can be used:

• M5002C2 E-DCH DATA VOLUME FOR SERVING CELL UL • M5002C3 E-DCH DATA VOLUME FOR NON-SERVING CELL IN SERVING E-

DCH RLS UL • M5003C4 E-DCH DATA VOLUME FOR NON-SERVING CELL IN NON-SERVING

E-DCH RLS UL All these counters should be added up and summed over the cells in BTS. Averaged BTS level throughput value can be obtained by dividing the BTS level data volume by 3600 (1 hour reporting period). For more details on possible monitoring cases please consult Capacity Management document for WN7.0 1.0 pages 38-45, or Capacity Management document for WN7.0 2.0 pages 38-47.

NOTEs! In WN7.0 1.0 in the first approximation calculation of HSUPA license utilization can be based on the sole number of HSUPA users, which means not considering the throughput condition of the HSUPA Processing Sets.

4.3.3 Monitoring of HSDPA traffic

For HSDPA, in a similar way as for HSUPA, Baseband resources can be monitored directly in terms of number of users and throughput over existing counters.

As previously in case of HSUPA, the HSDPA data volume counter should be summed up for each cell in the BTS and divided by 3600 (1h reporting period), resulting in the average BTS HSDPA throughput.

As HSDPA Baseband resource allocation is static, the resulting throughput value can be used to monitor HSDPA license saturation.

For more monitoring cases please consult Capacity Management document for WN7.0 1.0 pages 38-45 or Capacity Management document for WN7.0 2.0 pages 38-47.


NOTEs!

In WN7.0 1.0 in the first approximation calculation of HSDPA license utilization can be based on the sole number of HSDPA users, which means not considering the throughput condition of the HSDPA Processing Sets.

In WN7.0 2.0 dedicated counters for total HSDPA BTS throughput, total BTS number of users, and HSDPA license utilization are provided.

4.3.4 Calculation of used HW resources

The counters mentioned above allow calculation of used Rel.99 CE and HSPA Processing sets in BTS, and can be used as well to estimate the current Flexi BTS Rel.2 HW utilization. For that purpose: • Calculation of subunits used for R99 traffic can be done by dividing the number of used

Rel.99 CE in the whole BTS by 48 • Calculation of subunits used from HSUPA traffic: with the respective number of HSUPA

users and HSUPA throughput figures please refer to Dimensioning WCDMA RAN: Flexi BTS Baseband document issue “01E”, pages 51-66, tables 24-27, which provide mapping between a given number of HSUPA users and HSUPA throughput into the allocated Baseband subunits

• Calculation of Subunits used for HSDPA traffic: with the value of commissioned HSDPA throughput step please consult Dimensioning WCDMA RAN: Flexi BTS Baseband document issue “01E”, page 35, table 13 in order to obtain configured maximum HSDPA throughput. With that value consult Dimensioning WCDMA RAN: Flexi BTS Baseband document issue “01E”, page 36, table 15, which shows the mapping between the maximum HSDPA throughput and baseband resources allocated for it

• Total Subunit usage is a sum of the subunit usage for R99 and HSPA traffic • Total number of available subunits in Flexi BTS Rel. 2 HW: is also provided in

Dimensioning WCDMA RAN: Flexi BTS Baseband document issue “01E”, page 19 presents capacity of Flexi system modules in terms of CEs. These values divided by 48 will yield the number of available Flexi BTS system module subunits.

NOTE In WN7.0 2.0 dedicated counters for measuring the used and available Baseband subunits, and counter to measure Baseband HW saturation by current licensing are provided.


4.4 Flexi BTS Baseband load monitoring in WN7.0 2.x

New counters introduced with RAN in WN7.0 2.0 are:

M5008C0 HSDPA MAXIMUM MAC-HS THROUGHPUT M5008C1 HSDPA AVERAGE MAC-HS THROUGHPUT M5008C2 HSUPA MAXIMUM MAC-E THROUGHPUT M5008C3 HSUPA AVERAGE MAC-E THROUGHPUT M5008C4 MINIMUM USED CES FOR DL M5008C5 AVERAGE USED CES FOR DL M5008C6 MAXIMUM USED CES FOR DL M5008C7 MINIMUM USED CES FOR UL M5008C8 AVERAGE USED CES FOR UL M5008C9 MAXIMUM USED CES FOR UL M5008C10 MINIMUM USED CE FOR R99 DL M5008C11 AVERAGE USED CE FOR R99 DL M5008C12 MAXIMUM USED CE FOR R99 DL M5008C13 MINIMUM USED CE FOR R99 UL M5008C14 AVERAGE USED CE FOR R99 UL M5008C15 MAXIMUM USED CE FOR R99 UL M5008C16 MINIMUM NUMBER OF HSUPA USERS M5008C17 AVERAGE NUMBER OF HSUPA USERS M5008C18 MAXIMUM NUMBER OF HSUPA USERS M5008C19 MINIMUM NUMBER OF HSDPA USERS M5008C20 AVERAGE NUMBER OF HSDPA USERS M5008C21 MAXIMUM NUMBER OF HSDPA USERS M5008C22 MINIMUM HSDPA PROCESSING SETS UTILIZATION RATIO M5008C23 AVERAGE HSDPA PROCESSING SETS UTILIZATION RATIO M5008C24 MAXIMUM HSDPA PROCESSING SETS UTILIZATION RATIO M5008C25 MINIMUM HSUPA PROCESSING SETS UTILIZATION RATIO M5008C26 AVERAGE HSUPA PROCESSING SETS UTILIZATION RATIO M5008C27 MAXIMUM HSUPA PROCESSING SETS UTILIZATION RATIO M5008C28 LICENSED HARDWARE CAPACITY UTILIZATION RATIO M5008C29 LICENSED HSDPA THROUGHPUT M5008C30 LICENSED HSUPA THROUGHPUT M5008C31 LICENSED NUMBER OF HSDPA USERS M5008C32 LICENSED NUMBER OF HSUPA USERS M5008C33 MINIMUM HSUPA SUBUNITS USAGE M5008C34 AVERAGE HSUPA SUBUNITS USAGE M5008C35 MAXIMUM HSUPA SUBUNITS USAGE M5008C36: MINIMUM NUMBER OF USED SUBUNITS


M5008C37: AVERAGE NUMBER OF USED SUBUNITS M5008C38: MAXIMUM NUMBER OF USED SUBUNITS M5008C39: NUMBER OF SUBUNITS IN BASE BAND M5008C40: CONFIGURED HSDPA USERS M5008C41: CONFIGURED HSUPA USERS M5008C42: CONFIGURED HSDPA THROUGHPUT M5008C43: CONFIGURED HSUPA THROUGHPUT

Please note that OSS release 5.3CD3 supports counters from M5008C0 till M5008C35. All counters from M5008 measurement are supported from OSS5.3CD3 MD1 onwards.

4.4.1 Baseband load monitoring using M5008 counters

The purpose of M5008 measurement is to monitor licensed, commissioned, and used Baseband capacity on BTS level. Therefore M5008 measurement aggregation is BTS, unlike previous Baseband related measurements such as M5001 and M5006, where measurements are aggregated per LCG.

4.4.1.1 Monitoring of available BTS level capacity

Available BTS Baseband capacity can be inspected by monitoring the licensed capacity. • Available R99 licenses

Still M5006C0, M5006C1, and M5006C2 counters shall be used in WN7.0 2.0. These LCG level values should be summed over all existing LCGs in order to obtain BTS level result. Note that those counters include full R99 capacity coming from Hybrid HSUPA Processing Set (meaning that always 48 R99CEs capacity is added to total R99 licensed capacity). Corresponding M5008 measurement counter will be released in RU50 timeframe.

• Available Capacity for HSDPA Users Licensed number of HSDPA users can be seen in the counter M5008C31. The resulting values come from HSDPA Processing Set license keys loaded onto BTS. In order to detect possible commissioning problems counter M5008C40 shows the configured HSDPA users. The resulting values come from the BTS commissioning parameters.

• Available Capacity for HSUPA Users Licensed number of HSUPA users can be seen in the counter M5008C32. The resulting values come from HSUPA Processing Set license keys loaded onto BTS. In order to detect possible commissioning problems counter M5008C41 shows the configured HSUPA users. The resulting value comes from the BTS commissioning parameter.

• Available Capacity for HSDPA Throughput Licensed value of HSDPA Throughput can be seen in the counter M5008C29. The resulting values come from HSDPA Processing Set license keys loaded onto BTS. In order to detect possible commissioning problems counter M5008C42 shows the configured HSDPA Throughput. The resulting value comes from the BTS commissioning parameters.

• Available Capacity for HSUPA Throughput


Licensed value of HSUPA Throughput can be seen in the counter M5008C30. The resulting values come from HSUPA Processing Set license keys loaded onto BTS. In order to detect possible commissioning problems counter M5008C43 shows the configured HSUPA Throughput. The resulting value comes from the BTS commissioning parameter.

• Available BTS hardware for further licensing

Saturation of BTS hardware with already existing licenses is shown in the counter M5008C28 Licensed HW Capacity Utilization Ratio. This information is helpful to decide if, in case of identified capacity congestion, license extension is sufficient or if hardware extension is necessary.

4.4.1.2 Monitoring of the used Baseband resources

The used BTS Baseband capacity can be monitored as follows. • Used R99 Channel Elements

Counters M5008C10, M5008C11, M5008C12, M5008C13, M5008C14, and M5008C15 show the minimum, average, and maximum used R99CEs respectively in downlink and uplink direction. Note that the resources used for pure R99 traffic are reported.

• Used capacity for HSDPA Users Counters M5008C19, M5008C20, and M5008C21 show the minimum, average, and maximum number of HSDPA users in BTS.

• Used capacity for HSUPA Users Counters M5008C16, M5008C17, and M5008C18 show the minimum, average, and maximum number of HSUPA users in BTS. Note that SHO users are also included in the calculation.

• Used Capacity for HSDPA Throughput M5008C0 and M5008C1 show maximum and average HSDPA BTS level throughput.

• Used Capacity for HSUPA Throughput

Counters M5008C2, M5008C3 show maximum and average HSUPA BTS level throughput. Note: Issue has been observed with these counters. Please refer to chapter 4.4.3 for details, and to chapter 4.4.4 for correction plan. Until the correction is available used HSUPA throughput capacity should be monitored as described in 4.3.2.


4.4.1.3 Monitoring of Baseband usage ratio

• R99 Channel Elements usage ratio in Uplink direction The maximum R99 CEs usage ratio in Uplink can be obtained via formula R99CEs usage ratio = M5008C15 / sum over LCGs (M5006C1 Average R99 CE utilization ratio in Uplink direction can be obtained from KPI: RNC_5412a Avg CE Util rat UL Flx2 = M5008C14 / sum over LCGs (M5006C1 Note: UL is taking into account as UL is always consuming more R99CE than DL due to HSDPA return channels.

• HSDPA Users utilization ratio The maximum HSDPA users utilization ratio can be obtained as: Max HSDPA Users utilization ratio = M5008C21/M5008C31 Also available as KPI RNC_5398a Max n HSDPA u util ratio

• HSUPA Users utilization ratio The maximum HSUPA users utilization ratio can be calculated from: RNC_5399a Max HSUPA users utilization ratio = M5008C18/M5008C32

• HSDPA Throughput utilization ratio The maximum HSDPA Throughput utilization ratio can be calculated as: KPI RNC_5396a Max HSDPA Throughput utilization ratio = M5008C0/M5008C29

• HSUPA Throughput utilization ratio

The maximum HSUPA Throughput utilization ratio can be calculated as: RNC_5397a Max HSUPA Throughput utilization ratio = M5008C2/M5008C30 Note: Due to issue discovered with HSUPA throughput counters M5008C2 and M5008C3 (please refer to 4.4.3), this Kpi can only be used after correction of these counters. Until then AVERAGE HSUPA throughput utilization ratio can be calculated as described in chapter 4.3.2. Avg HSUPA Throughput utilization ratio = average HSUPA Throughput as described in 4.3.2 / M5008C30

• HSDPA Processing set utilization ratio Minimum, average, and maximum utilization of HSDPA processing sets is given in counters M5008C22, M5008C23, and M5008C24, respectively.


• HSUPA Processing set utilization ratio Minimum, average, and maximum utilization of HSUPA processing sets is given in counters M5008C25, M5008C26, and M5008C27, respectively. Note: Due to issue discovered with HSUPA ratio counters (please refer to 4.4.3), saturation of HSUPA licenses can be monitored in terms of number of users only. Correction plan can be found in chapter 4.4.4.: HSUPA PS utilization ratio = M5008C17/M5008C32

4.4.1.4 Monitoring of Baseband total HW capacity usage

With counters and KPIs described in chapters 4.4.1.1 to 4.4.1.3 utilization rates considering licensed capacity can be calculated in order to perform proactive capacity measurement. Naturally capacity monitoring against license cannot give full information in case of unlimited capacity license. Therefore several counters were introduced that give info about available and used BTS hardware capacity, in terms of subunits: • Available HW Capacity for traffic

Number of Baseband subunits available in BTS hardware can be seen in the counter M5008C39. Note that BTS site hardware updates, i.e. adding/removing Flexi System module, hardware malfunction resulting in subunit capacity decrease, and configuration change of BTS might result in changing the value of this counter. Note: Issue has been discovered with this counter. Depending on configuration (e.g.3+3+3) not all SU can be used for traffic. This is not reflected in M5008C39 (more info in 4.4.3; correction plan in 4.4.4). In order to remove contribution of configuration the following procedure can be applied:

M5008C39 NUMBER OF SU in BB 1 subunit should be subtracted for every 3 cells.

• Used HSUPA Hardware Capacity The number of subunits used by HSUPA is given in the counters M5008C33, M5008C34, and M5008C35. Due to issue discovered with the HSUPA resources calculation those counters might be showing higher usage values than actually occurring. Please refer to 4.4.3 for details.

• Used BTS Hardware Capacity Total number of used HW capacity in BTS is given by the counters M5008C36, M5008C37, and M5008C38. Note: Due to issue discovered with HSUPA resources calculation those counters could show higher usage values than actually occurring.


In addition these counters contain capacity (SU), that cannot be used for traffic e.g. in case of 3+3+3 configuration. In order to remove contribution of configuration the following procedure can be applied:

• M5008C36-M5008C38 MIN/AVG/MAX USED BB SU • 1 subunit should be subtracted for every 3 cells. In addition 1 SU shall be subtracted (free CCCH SU)

Finally SU used for PIC are not yet included in used subunits. In order to add contribution of PIC the following procedure can be applied:

• M5008C36-M5008C38 MIN/AVG/MAX USED BB SU 1 Subunit shall be added per configured PIC pool

More info in 4.4.3; correction plan in 4.4.4.

• Used BTS Hardware Capacity ratio The maximum used BTS Hardware capacity ratio can be calculated as: RNC_5409a Max BTS Hardware utilization ratio = M5008C38/M5008C39

4.4.2 Examples

BTS is configured with one LCG in 3+3+3, has two Flexi System modules (FSMD and FSME). Licensing and commissioning configuration is as follows:

HSDPA Processing Set type3 1 HSDPA Processing Set type2 3 HSUPA Processing Set type1 7 Rel99 CEs = 366 366

M5008 measurement for an example BTS yields the following results:

NUM_BB_SUBUNITS (M5008C39) 33

LIC_HW_CAP_UTIL_RAT (M5008C28) 77

Regarding “Dimensioning WCDMA RAN: Flexi BTS Baseband” document the number of Baseband subunits is 30 = 12 (FSMD) + 18 (FSME).


Due to the issue discovered with M5008 counters (see chapter 4.4.3), counter M5008C39 currently reports 33. SU needed for TX are not excluded. As described in 4.4.1.4 1 SU per every 3 cells need to be subtracted to get the real number of available Baseband.

Counter Now After Correction

M5008C39 33 30

Counter M5008C28 has value 77. It means that the existing example BTS Baseband capacity is 77% filled with the existing licenses. The counter shows the ratio: M5008C28 = Hardware Capacity allocated by existing licenses / Hardware Capacity available for traffic * 100% Where: Hardware Capacity allocated by existing licenses = licensed HSDPA[CE] + licensed HSUPA [CE] + licensed R99[CE] Hardware Capacity Available for traffic= HW capacity of BTS [CE]- HW capacity for configuration[CE] all expressed in R99 channel elements. So in case of the example BTS, the calculation is as follows: FSMD+FSME = 30 SU == 1440 CE total HW capacity

Resources allocation in CE: R99 = 366 CE; HSUPA = 504 CE (7 PS * 72 CE); HSDPA = 240 CE (1 PS3 + 3 PS2 == 1 *84Mbps + 3* 21Mbps = 147Mbps, but there are two schedulers commissioned: one with 105Mbps == 3 SU, and one with 42Mbps == 2SU; In total 5SU for HSDPA == 240 CE)


Hardware Capacity allocated by licenses = 240 + 504 + 366 = 1110 CE Hence M5008C28 = 1110/1440 ~77%

4.4.3 Issues with M5008 counters recognized during pilots of WN7.0 2.0

The following issues have been recognized with the M5008 counters during pilots of WN7.0 2.0: • HSUPA throughput related counters show unrealistic throughput values

Counters M5008C2 Maximum HSUPA Throughput and M5008C3 Average HSUPA Throughput are currently based on HW reserved for HSUPA. Therefore these cannot be compared with the real UE Throughput based on the incoming HSUPA data volume. Due to HSUPA resource pre-allocation (see below) those counters can indicate HSUPA throughput even though there is no HSUPA users in BTS. Counter update will be done with CR2195. This issue is also impacting Minimum, Average and Maximum HSUPA PROCESSING SETS UTILIZATION RATIO (M5008C25, M5008C26, M5008C27) Workaround is described in chapter 4.3.2

• Used HSUPA resources are shown based on Baseband reservation principle and not the actual usage. Counters M5008C33, M5008C34, and M5008C35 show BB resources reserved for HSUPA traffic. That might lead to misleading indications of high HSUPA BB utilization, as HSUPA pre-allocates resources in order to provide better QoS, and thus not all the reserved resources are, in fact, used. Counter update will be done with CR2197.

• Subunit related counters show values different than those from Flexi BB dimensioning guideline. It has been observed that counters M5008C36, M5008C37, M5008C38, and M5008C39 show all the used Baseband resources, also the free subunits included in the HW price, hence the observed difference between the counter values and official Flexi Base Band dimensioning documentation. This fact also leads to values of Base Band utilization ratio being artificially higher than expected. PIC pools not reported in Subunits related counters. Subunits used for PIC are not included in counters M5008C36, M5008C37, M5008C38

Now After Correction

Counter NO PIC PIC NO PIC PIC M5008C38 10 10 10 12

Workaround is described in chapter 4.4.1.4. Counter update will be done with CR2172.

• In addition it has been observed that there are small deviations between actual number of HSUPA and HSDPA users reported by BTS counters M5008 and RNC counters M1031. Reason is different sampling interval, which is 1 second in case of M1031 and 5 seconds in case of M5008 BTS counters.


4.4.4 Correction plan

Changes in the counters are planed as follows: WN7.0 2.1 – CR2195: M5008C2 Maximum HSUPA Throughput and M5008C3 Average HSUPA Throughput will be showing real UE HSUPA throughput, based on the incoming data volume. WN7.0 2.2 – CR2197:Counters M5008C25, M5008C26, M5008C27 as well as M5008C33, M5008C34, and M5008C35 will be showing HSUPA resources actively used, it means without HSUPA pre-allocations. WN7.0 2.3 CR2172:Counters M5008C36, M5008C37, M5008C38, and M5008C39 will not contain contribution from subunits included in HW price. PIC pools, if configured, will be included. Note that changes introduced in WN7.0 2.1 and WN7.0 2.2 will be also available in RU40 main release, and changes introduced in WN7.0 2.3 in RU40 maintenance release.


Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved.

Processing Sets

Documents

Transcript of Processing Sets