TS-RNC-SW-166-I5

Technical Support Note TS-RNC-SW-166

New PM counters to improve Voice CSSR calculation Radio Controllers IPA-RNC: RN5.0 MP5, RN6.0 1.0, RN7.0 mcRNC: mcRNC2.0, mcRNC3.0 Flexi Direct RNC: I-Ada5.0

A p p r o v a l d a t e : 0 3 - J a n - 2 0 1 3 This document contains following type of information Informative

X

Preventive Corrective Ad di ti onal on al c atego ri zati on Urgent Security Release Upgrade SW Update Information is classif ied as as Internal Public

X

Customer Specific

TS-RNC-SW-166 Nokia Siemens Networks © CONFIDENTIAL APPROVED 5.0

Page 1

Table of Contents 1. 2. 3. 4. 5. 6. 7.

Validity .......................................................... ........................................................... ....................... 3 Keywords........................................................... ........................................................... .................. 3 Summary ........................................................... ........................................................... .................. 3 Detailed description ........................................................... ........................................................... .. 3 Solution / Instructions ........................................................ ........................................................... .. 4 Note ....................................................... .............................. ........................................................... 6 References ..................................................................................... ................................................ 6

Contact: Contact your local Nokia Siemens Networks support.

Summary of changes: 01-Jun-2011 12-Aug-2011 21-Nov-2011 13-Apr-2012

1.0 2.0 3.0 4.0

03-Jan-2013

5.0


First version. Updated version for RN5.0 MP5 and RN6.0 1.0. Formula with counter IDs added. TS Note combined for several products. Also, document was moved to a new template. RU40 validity checked.

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 Produ ct IPA-RNC RNC OMS for IPA-RNC (Integrated) RNC OMS (Standalone) mcRNC Flexi Direct RNC Flexi Direct OMS

RU20 x

RN5.0 RN5.0

RU30 x

RNC OMS 5.0

x

RNC OMS 1.0 x

I-Ada3.0 I-OMS3.0

RN6.0 RN6.0

RU40

mcRNC2.0 I-Ada4.0 I-OMS4.0

RN7.0 Not Supported RNC OMS 2.0

x x

mcRNC3.0 I-Ada5.0 I-OMS5.0

2. KEYWORDS CSSR, counters, Cell_PCH

3. SUMMARY In RU30 new counters are introduced to improve information about performance of CS Voice calls started at PCH state. These new counters can be used to calculate Voice Call Setup Success Ratio (CSSR) more accurate. In RU20 (IPA-RNC RN5.0 MP5) same implementation is done with spare counters. In RU40 same implementation is in use as in RU30. In Flexi Direct RNC counters M1006C253 and M1006C254 are supported first time in I-Ada5.0 release.

4. DETAILED DESCRIPTION Current Voice CSSR KPI are built based on RRC setup & access success ratio (for different causes e.g. Conv. Call for voice) * Voice RAB setup & access success ratio. With RRC procedure all calls started from Cell_Idle are included in CSSR calculation. But with increased number of smartphones and implementation of PCH in the networks more and more calls are not started from Cell_Idle, but from Cell_PCH state. As calls started from Cell_PCH are not using RRC procedure but Cell Update procedure they are not fully included in CSSR formula. This means that in case voice call is initiated from Cell_PCH state and there is some failure during the cell update procedure this is not reflected to current CSSR KPI (RNC_565). As the number of voice calls started from Cell_PCH state is rapidly increasing in the networks and no proper counters were existing new counters are implemented. These counters can be used to adapt Voice CSSR formula. TS-RNC-SW-166 Nokia Siemens Networks © CONFIDENTIAL APPROVED 5.0

Page 3

5. SOLUTION / INSTRUCTIONS Since 3GPP REL5 the cell update message includes optional establishment cause field. This establishment cause includes the same causes as for RRC setup and is used to trigger new counters.

In RU30 and RU40 CELL_UPDATE_ATT_CS_CALL (M1006C253): Number of started Cell Update procedures with cause "Originating Conversational Call", "Terminating Conversational Call" or "Emergency Call". The counter is updated when the RNC receives Cell Update from the UE with mentioned causes. CELL_UPDATE_SUCC_CS_CALL (M1006C254): Number of successful Cell Update procedures with cause "Originating Conversational Call", "Terminating Conversational Call" or "Emergency Call". The counter is updated when the UE responds Radio Bearer Reconfiguration Complete after the RNC has sent Cell Update Confirm as a response to Cell Update with the mentioned causes.

In RU20 (IPA-RNC RN5.0 MP5) with same trigger conditions SPARE_1_RRC (M1006C78): Number of started Cell Update procedures with cause "Originating Conversational Call", "Terminating Conversational Call" or "Emergency Call". SPARE_2_RRC (M1006C79): Number of successful Cell Update procedures with cause "Originating Conversational Call", "Terminating Conversational Call" or "Emergency Call".

Attempt counter is not updated immediately when the cell update is received, but only after the result of the procedure is known. If the procedure was successful update both attempt and success counters, but if it fails update only attempt counter This excludes repeated Cell Updates, that are not impacting end user perception, from counting in following cases: - UE is sending a new CU to another cell after Cell reselection - UE is sending CU several times to the same cell before procedure is finished

With new counters Voice CSSR can be adapted. Formula (logical) RRC _ Successful _ Establishments + Successful _ CellUpdates VoiceRAB _ Successful _ Establishments RRC _ Setup _ Attempts + Started _ CellUpdates


∗

VoiceRAB _ Setup _ Attempts

Page 4

Formula (NetAct names) sum(MOC_CO NV_CALL_ATTS MOC_CONV_CALL_FAILS+ MTC_CONV_CALL_ATTS MTC_CONV_CALL_FAILS+ EMERGENCY_ CALL_FAILS-

+

sum(CELL_UPDATE_SUCC_CS_ CALL )

EMERGENCY_ CALL_FAILSRRC_ACC_REL_EMERGENCY RRC_ACC_REL_MO_CONV 100 *

RRC_ACC_REL_MT_CONV) sum(MOC_CO NV_CALL_ATTS +

∗

sum(RAB_ACC_COMP_CS_ VOICE) sum(RAB_STP_ATT_CS_VOICE)

MTC_CONV_CALL_ATTS + EMERGENCY_ CALL_ATTS RRC_ATT_REP_MO_CONV RRC_ATT_REP_MT_CONV RRC_ATT_REP_EMERGENCY -

+

sum(CELL_UPDATE_ATT_CS_CALL )

RRC_ACC_REL_EMERGENCY RRC_ACC_REL_MO_CONV RRC_ACC_REL_MT_CONV RRC_CONN_STP_REJ_EMERG_CALL)

Formula (counter IDs) sum(M1001C 22 M1001C23 + M1001C32 M1001C33 + M1001C40 -

+

sum( M1006C254 )

M1001C41 M1001C562 M1001C553 100 *

M1001C558)

∗

sum(M1001C 22 +

sum(M1001C115) sum(M1001C 66)

M1001C32 + M1001C40 M1001C573 M1001C578 -

+

sum( M1006C253 )

M1001C582 M1001C562 M1001C553 M1001C558 M1001C617)


Page 5

Formula for RU20 (IPA-RNC RN5.0 MP5) can be adapted by replacing - M1006C254 CELL_UPDATE_SUCC_CS_CALL by M1006C79 SPARE_2_RRC - M1006C253 CELL_UPDATE_ATT_CS_CALL by M1006C78 SPARE_1_RRC

6. NOTE Establishment cause field in cell update message is optional. Currently it is not verified how many UEs are using it. Adapted Voice CSSR (RNC_5093b Voice Call Setup Success Ratio (RRC+CU)) is included in Reporting Suite for RU30 EP1.

7. REFERENCES NA04878470 Cell update cause calculation NA04943351 Voice Call Setup Success Ratio Implementation Change Required


Page 6

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 ri ghts reserved.


Page 7

TS-RNC-SW-166-I5

Recommend Documents