You are on page 1of 8

Technical Support Note

TS-RNC-SW-141

Cell_PCH L2 Resource
Optimization
R a d i o Co n t r o l l e r s
I P A - RN C: R N 5 . 0 , R N6 . 0
m c R N C: mc R NC 2 . 0

A p p r o va l d a t e : 3 0 - J u n - 2 0 1 3
This document contains following
type of information
Informative
Preventive
Corrective X
Additional categorization
Urgent
Security
Release Upgrade
SW Update
Information is classified as
Internal
Public X
Customer Specific

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 1
Table of Contents

1. Validity......................................................................................................................................... 3
2. Compatibility / Dependencies to other products ........................................................................... 3
3. Keywords .................................................................................................................................... 3
4. Summary ..................................................................................................................................... 3
5. Detailed description for IPA-RNC ................................................................................................ 3
5.1 ..... How to detect a lack of DSP resources .................................................................................. 4
5.2 ..... HW capacity upgrade considerations..................................................................................... 6
6. Detailed description for mcRNC................................................................................................... 6
7. Solution / Instructions .................................................................................................................. 6
8. Note ............................................................................................................................................ 7
9. References .................................................................................................................................. 7

Contact:

Contact your local Nokia Siemens Networks support.

Summary of changes:

28-Dec-2009 1.0 The first version of document.


14-Jan-2010 2.0 Activation instructions added to chapter 6.
17-Mar-2010 3.0 TN updated concerning RNC2600, chapter 5.
07-Jun-2011 4.0 RN6.0 validity added. Chapter 5.1 added.
20-Jun-2011 5.0 Chapter 5 content revised.
16-Jan-2013 6.0 RU40 validity checked.
TS Note valid also for mcRNC.
30-Jun-2013 7.0 Removed RN7.0 and mcRNC3.0 validity, 007:0251
RN30_MAINT_028 is not used after RN7.0 commercial
release (P8) and mcRNC3.0.

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 2
Purpose
This document contains generic information about products. These can be instructions that
explain problem situations in the field, instructions on how to prevent or how to recover
from problem situations, announcements about changes or preliminary information as
requirements for new features or releases.

1. VALIDITY

Product RU20 RU30 RU40


IPA-RNC x RN5.0 x RN6.0 RN7.0
RNC OMS for IPA-RNC RN5.0 RN6.0 Not Supported
(Integrated)
RNC OMS RNC OMS 5.0 RNC OMS 1.0 RNC OMS 2.0
(Standalone)
mcRNC x mcRNC2.0 mcRNC3.0
Flexi Direct RNC I-Ada3.0 I-Ada4.0 I-Ada5.0
Flexi Direct OMS I-OMS3.0 I-OMS4.0 I-OMS5.0

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

3. KEYWORDS

Cell_PCH

4. SUMMARY

RNC resource management keeps Layer 2 resources for a Cell_PCH user if the availability
of the DSP/USPU resources is above a certain threshold. The L2 resources are released
for Cell_PCH users if the resource availability is less than this internal threshold. It has
been discovered that leaving L2 resources for Cell_PCH users can be inefficient even if
the average DSP/USPU resource availability level is high.

The Cell_PCH resource reservations can prevent resource allocations in case of


Cell_FACH state transition or they can prevent upgrading the bit-rate allocation, if locally in
that particular DSP/USPU there is unnecessary resource reservation and even if in
average in RNC level there would be sufficient resources available.

5. DETAILED DESCRIPTION FOR IPA-RNC

In cases where CDSP types are changed -- for instance as part of the CDSP-DH
replacement upgrade, CDSP-DH feature upgrade, RNC450 upgrade to RNC2600 or in all
configurations which have CDSP-DH cards -- it is possible that the abovementioned
threshold for releasing PCH resources is exceeded, causing significant increases in
Cell_FACH and Cell_PCH load which could lead to KPI degradation.

The CDSP-C card is not supported anymore in RU40 and onwards.

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 3
The DSP architecture is different in CDSP-C and replacement cards, even though the
overall capacity is the same (32 PS384k calls per DMCU):
o CDSP-C has eight DSPs per DMPG, each supporting one 384k PS call.
o CDSP-DH in replacement mode has one DSP per DMPG, supporting eight 384 PS
calls. The other DSP is reserved for CCH services.

DSP resources are reserved for PCH-state users depending on the DSP load information
RM3 (resource management) sent to L3. DSP load is indicated by how many PS384k calls
fits per DSP on average. If the DSP filling level calculated over all DSPs equipped to the
RNC is such that, on average, 1.3 or less PS384k calls per DSP would fit in, then
CELL_PCH users are released.

With the C cards, there will be many DSPs which do not have the capacity for a single
384k call. This decreases the average availability. Replacement DH-card DSPs will almost
always have capacity for at least one 384k PS call.

With CDSP-DH the resource management calculates the availability differently because
the number of DSPs per DMPG is different. It has been seen that the resource availability
with CDSP-C was such that L2 resources were removed from Cell_PCH state users,
however, after the CDSP-DH upgrade, RNC resource management (RM3) calculates the
availability so that the threshold was not exceeded but the L2 resources were left for
Cell_PCH state users. This causes potential DSP blocking for Cell_FACH resource
allocations because resource management calculates the availability differently with
CDSP-DH because the number of DSPs per DMPG is different.

New deliveries of RNC2600 from factory contain only CDSP-DH plug-in units. However
Cell_PCH L2 resources can cause blocking also with the new delivery RNC2600
configurations in networks which have a high amount of PS calls. This is because PS calls
Cell_FACH and bit-rate upgrade L2 resources need to be allocated from the same DSP
where the user SRB is allocated. Thus, certain DSPs can be fully utilized, but Cell_PCH L2
resource release is not triggered because in RNC level the load level has not been
exceeded.

5.1 How to detect a lack of DSP resources

o Situation can be verified by checking DMPG service pool configuration and HS_DCH
statistical counters.

ZWPI:S;

SERVICE POOL CONFIGURED ACTUAL NUMBER OF


SHARE % SHARE % UNITS
------------------------------------------------------------

3 CCH 16 16 46 DSPs
4 DCH_HS 0 0 0 DSPs
8 HS_DCH 84 84 242 DSPs

ZWPS:P;

DMPG PQ PROCESSING CAPACITY AVAILABILITY:


ID PPC SETUP CURRENT % AVERAGE % LOWEST % UNITS
-----------------------------------------------------------------------

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 4
0 DSP_POOL 77 77 76 144
1 DCH_DMPG - - - -
2 HS_DMPG - - - -

DSP CAPACITY AVAILABILITY:


ID SERVICE POOL CURRENT % AVERAGE % LOWEST % UNITS
--------------------------------------------------------------------
0 DCH1 - - - -
1 DCH2 - - - -
2 HSPA - - - -
3 CCH 76 76 76 46
4 DCH_HS - - - -
5 CCH_REP - - - -
6 DCH_REP - - - -
7 DCH_HS_R - - - -
8 HS_DCH 5 6 4 242

Low CURRENT % in HS_DCH indicates restriction in availability of the DSP resources.

o The rejected counters can be checked with MML command.

ZWPS:E:POOL=8;

LOADING PROGRAM VERSION 12.3-0

SERVICE POOL: HS_DCH

SERVICE TYPE DSP_BUSY PQ_BUSY MODIFY OVERFLOW OTHER


--------------------------------------------------------------------
SL 0 0 0 0 0
RTCSDATA 0 0 0 0 0
AMR 0 0 0 0 0
NRTPSR99 9 0 9649 0 3
RTPSR99 0 0 0 0 0
HSCCH 0 0 0 0 0
HSDPANR 2 0 55140 0 1
HSUPANR 0 0 0 0 0
HSPASWI 0 0 1223 0 0
IPIUAMR 4731 0 0 0 0
IPIURTCS 0 0 0 0 0
HSDPART 0 0 0 0 0
HSUPART 0 0 0 0 0
RTHSPASW 0 0 0 0 0
HSUPART2 0 0 0 0 0

o High values in DMCU-related counters indicate lacking resources. The following counters
should be checked: M1022C13 Packet call setup failures due to DMCU for interactive,
M1022C14 for background and M1022C186 for streaming.

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 5
5.2 HW capacity upgrade considerations

HW capacity expansion does not necessarily remove problems in DSP resources. In any
case, after HW upgrades the network planning and pool configuration due to capacity step
expansion must be re-iterated. However, if for example smart phone penetration is high
and users stay long in Cell_PCH, the DSP resource problem might still remain. In such a
case it is recommended to do the PRFILE modification.

Note that HW addition will not add resources if the pool configuration is not reconfigured.
The situation can be verified by checking the DMPG service pool configuration and
HS_DCH statistical counters. PRFILE modification (to value 1) is recommended in case
the CURRENT % in HS_DCH is low.

6. DETAILED DESCRIPTION FOR MCRNC

mcRNC has a so-called logical (UP service counter model) based resource counting and
UP load balancing, like IPA-RNC. The counter model approximates the resultant UP load
to the UP resource unit physical resources (memory capacity use, CPU time use). The
reason why Cell_PCH state UEs should not be granted by default UP resources is
because the physical UP resource is not over-dimensioned.

For mcRNC the PRFILE value 1 should be used.

7. SOLUTION / INSTRUCTIONS

The PRFILE parameter can be used to change the resource management so that L2
resources are released always when the user is moved to Cell_PCH state. In IPA-RNC
this change shall be taken into use when upgrading CDSP-C to CDSP-DH units, and also
in new deliveries of RNC2600. In mcRNC this value should be 1.

PRFILE activation:
IPA-RNC:
ZWOC:7,251,1;
mcRNC:
set app-parameter configuration-parameter class 7 number 251 value
0x1
When the PRFILE value is changed to 1, it overrides the normal resource release
mechanism causing the L2 resources to be released immediately when entering the
Cell_PCH state.
After the PRFILE parameter change, the resource manager always releases the L2
resources when the user is moved to the Cell_PCH state. For IPA-RNC the behavior is
thus the same as it was earlier with CDSP-C HW.

The parameter can be reverted by changing its value to its original default value of 0:
IPA-RNC:
ZWOC:7,251,0;
mcRNC:
set app-parameter configuration-parameter class 7 number 251 value
0x0

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 6
8. NOTE

9. REFERENCES

PR NA04509981: Releasing the DSP resources from the Cell_PCH user immediately
when the state changes are not happening

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 7
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. All rights reserved.

TS-RNC-SW-141
Nokia Siemens Networks
CONFIDENTIAL
APPROVED 7.0 Page 8