241819261 Performance Analysis WI RU10 V3 Ppt

104
1 of 17 © Nokia-Siemens Siemens Networks Internal Confidential WORK INSTRUCTION Status: Version 2.0 2009 Utran NSN\CMO\SBU\CSI\NSO NPO Work Instruction: Performance Monitoring & Analysis Title RAN KPI Monitoring Work Instruction Reference Target Group Radio (CSI NSO, NI) Technology 3G Software Release RAS06/RU10 Service Optimization Service Item Performance Monitoring Related Working Item/s Author Poon Chi Keong/Isaac Blanco/P.Ranta Version V3.0 Version Date 18 th September 2009

description

241819261 Performance Analysis WI RU10

Transcript of 241819261 Performance Analysis WI RU10 V3 Ppt

Page 1: 241819261 Performance Analysis WI RU10 V3 Ppt

1 of 17 © Nokia-Siemens Siemens Networks Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009UtranNSN\CMO\SBU\CSI\NSO

NPO

Work Instruction: Performance Monitoring & Analysis

Title RAN KPI Monitoring Work InstructionReference

Target Group Radio (CSI NSO, NI)

Technology 3GSoftware Release RAS06/RU10

Service OptimizationService Item Performance Monitoring

Related Working Item/sAuthor  Poon Chi Keong/Isaac Blanco/P.RantaVersion  V3.0

Version Date  18th September 2009

Page 2: 241819261 Performance Analysis WI RU10 V3 Ppt

2 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Change Record

Copyright © Nokia Siemens Networks. This material, including documentation and any related computer programs, is protected by copyright controlled by Nokia Siemens Networks. All rights are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia Siemens Networks. This material also contains confidential information which may not be disclosed to others without the prior written consent of Nokia Siemens Networks.

Version Date Edited by Section/s Comments0.1 26- Oct-2007 Poon Chi Keong All Draft0.2 18- Aug-2008 Isaac Blanco1.1 10-Oct-2008 Poon Chi Keong RAS06 updated Updated with RAS06 counters & KPI, Packet call and cell

Throughput measurement. Added in Propagation delay and IFHO analysis.

2.0 30.5.2009 Pekka Ranta RU10 basis

3.0 18.09.2009 Pekka Ranta RU10 add on

Page 3: 241819261 Performance Analysis WI RU10 V3 Ppt

3 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 4: 241819261 Performance Analysis WI RU10 V3 Ppt

4 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Purpose and ScopePurpose:The purpose of the work instruction is to describe to a Network Planning engineer an step-by-step delivery of remote

KPI monitoring serviceScope:The Scope of the Work instruction includes: RAN KPI monitoring and analysis Problem identification and problem solution Separate ISHO optimization WI (not included here) can be seen in IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/405632934The following is not-within the scope of this Work instruction: Drive test KPI Monitoring Solution implementation verificationPlease reference to the following associated to this Work Instruction:1. Input/Output Matrix: From Capability ShareNet/IMS Portal

For full check list of Information, tools, resources and output deliverables2. Full Service Delivery Process: from Global Process Portal

For full Service Delivery process and associated engineering processes3. Service Item Description: From Service Product Management Sharenet/IMS Portal

For full Service description which is communicated to customers.4. Service Item Working Card: from Service Product Management Sharenet/IMS Portal

For full specification of MWDs (Man Working Days) and number of resources required, for pricing of services. This is a internal sensitive document.

Page 5: 241819261 Performance Analysis WI RU10 V3 Ppt

5 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 6: 241819261 Performance Analysis WI RU10 V3 Ppt

6 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Service Delivery Step-by-step check list

The following is a step-by-step check list of the service delivery, which is aligned to the Service Delivery Process. Please visit Global Process Portal for full process flow diagram and associated engineering processes.Included in Checklist:It is important that all Interfacing with different departments is considered in the step-by-step delivery of a service

The main cause for efficiency issues in delivering any services are associated with WAITING times of interfacing with different departments or customers for information's, access to tools.

“Press the Button” actions on a tool are also shown.

Page 7: 241819261 Performance Analysis WI RU10 V3 Ppt

7 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Service Delivery Step-by-step check listSTEP TYPE DESCRIPTION TOOL RESPONSIBLE

1 Input Get Customer Input data (SW level, Service, Technology) N/A Customer Team2 Activity Define KPIs + KPI formulas N/A Radio Planner3 Input Get agreement on KPI target/Guarantees for assessment N/A Customer Team

4 Activtity Implement and activate measurement data collection ( Move to Annex)NetAct OSS

Radio Planner

4.1 Activity Activate standard measurement from OSS (Move to Annex)NetAct OSS

Radio Planner4.2 Activity Activating optional measurement from OSS (Move to Annex) NetAct OSS Radio Planner4.3 Activity KPI data collection via Reporting Suite NetAct RS Radio Planner5 Activity Perform Data analysis and Assessment Excel/Access Radio Planner6 Decision Low Call Setup Succes Rate for Voice and Rel99 NRT DCH (flow chart with new RU10 counters) N/A Radio Planner7 Decision High Call Drop Rate for AMR and Rel99 NRT DCH (flow chart with new RU10 counters) N/A Radio Planner8 Decision Low HSDPA Accessibility N/A Radio Planner9 Decision Low HSDPA Retainability N/A Radio Planner

10 Decision Low HSDPA Serving Cell Change Success Rate N/A Radio Planner11 Decision Low HSDPA Throughput N/A Radio Planner12 Decision Low HSUPA Accessibility N/A Radio Planner13 Decision Low HSUPA Retainability N/A Radio Planner14 Decision Low HSUPA SCC success ratio N/A Radio Planner15 Decision Low HSUPA Throughput N/A Radio Planner16 Decision Low ISHO success rate N/A Radio Planner17 Decision Low AMR/Rel99 NRT DCH IFHO Success rate N/A Radio Planner18 Decision Low HSDPA IFHO Success Rate N/A Radio Planner19 Activity Next Step Proposal Word Doc Radio Planner20 Output Produce Executive Summary KPI Report

Page 8: 241819261 Performance Analysis WI RU10 V3 Ppt

8 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Service Delivery Process (Remote KPI Monitoring)

Remote KPI Monitoring ProcessR

emot

e C

ente

r (R

adio

Pla

nner

)C

usto

mer

Tea

m

Get Input from

Customer

Define KPIs and

formulae

Get Customer Agreement on

KPI Guarantees

OSS Data Measurement Collection

Perform Data

Analysis and Assessment

Low in CSSR? High In CDR? Low in HSDPA Accessibility?

Low in HSDPA Retainability?

Look here at HSUPA also!

Page 9: 241819261 Performance Analysis WI RU10 V3 Ppt

9 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Service Delivery Process (Remote KPI Monitoring)

Remote KPI Monitoring ProcessC

usto

mer

Tea

mR

emot

e C

ente

r (R

adio

Pla

nner

)

Low in HSDPA Throughput?

Low in ISHO Success Rate?

Next Step Solution Proposal

Executive Summary

Report

Executive Summary

Report

Low in HSDPA SCC?

Page 10: 241819261 Performance Analysis WI RU10 V3 Ppt

10 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 11: 241819261 Performance Analysis WI RU10 V3 Ppt

11 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Get Customer Input data

1. Get customer network topology Number of RNCs/NodeBs/WCELs Single vendor/multivendor network (RAN, CS core, PS core)

2. Get services, domain or technology network performance area

3. Get current system software level like OSS SW and RNC SW

4. Get available and purchased RNW Measurement Tables

5. Get current methodologies used for KPI collection

STEP-1

KPI Monitoring Information Request Form

Page 12: 241819261 Performance Analysis WI RU10 V3 Ppt

12 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Define RAN KPIs and KPI formulas

1. Define RAN KPI class required Accessibility, Retainability, Mobility, Resource Usage

2. Define the KPI per services offered AMR voice, Video, Rel99 PS call, HSDPA call, HSUPA call

3. Define the Key Performance indication per KPI class and services Call SSR, Packet SSR, Accessibilty,Retainability, mobility (SHO,ISHO,SCC),

Throughput, Interference, CQI

4. Define and update the formulas to calculate KPI based on current RNC SW level RAS5.1/RAS06/RU10

5. Defining targets or Guarantees for each KPIs for assessment

STEP-2

Page 13: 241819261 Performance Analysis WI RU10 V3 Ppt

13 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Define RAN KPIs and KPI formulas

1. Define the major KPIs from RAN KPI classification Accessibility (setup failures, CSSR) Retainability (drops) Mobility (SHO, SCC, ISHO) Throughput Usage (Resource)

STEP-2

BS

RNC 3G MSC

3G SGSN

GGSN Firewall

FMT

GPRS Backbone

Internet

PS data server

PSTN

CS data server

Modem

RAN KPI

Page 14: 241819261 Performance Analysis WI RU10 V3 Ppt

14 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Define RAN KPIs and KPI formulas

SRNC RelocationR

NC

UE BTS2BT

S1

RNC

Accessibility:RRC Setup & Access

RateRAB Setup & Access

RateCall Setup Success

RateHSPA accessibilities

XRetainabi

lity:RRC Drop

RateRAB Drop

RateHSPA Drop

Rate

Mobility:SHO Success

RateHSPA SCC

Success ratioISHO Succ

Ratio

Usage:Cell AvailabilityAve. UL/DL Load

HSPA Throughput X Pre-

emption

SRNC

STEP-2

2. Define the KPI per services offered in the network AMR voice call, Video call, Rel99/Rel4/Rel5 PS call, HSDPA call

3. Define the Key Performance indication per KPI class and services Call setup success rate, Call drop rate, SHO/HSDPA SCC success rate, HSPA

accessibility, HSPA retainability, HSPA throughput

Page 15: 241819261 Performance Analysis WI RU10 V3 Ppt

15 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Define RAN KPIs and KPI formulasSTEP-2

4. Define and updating the formulas to calculate KPI based on current RNC SW level Example of CSSR (RNC_565f) in RAS06/RU10

RAN KPIs List from JUMP

RAS5.1 CSSR

RAS06/RU10 CSSR

Shortcut to JUMP RU10 Report Set: http://nopi.nokiasiemensnetworks.com/reportmanager/htmlset.php?set=426&co=1&m=1&se=1&expand=10404#10404

Page 16: 241819261 Performance Analysis WI RU10 V3 Ppt

16 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Define RAN KPIs and KPI formulas

5. Defining targets or Guarantees for each KPIs for assessment KPI targets must be achievable based on NSN global reference level KPI targets must aligned to RNC and NodeB SW level Commits KPI targets based on area level aggregation; PLMN/RNC level

STEP-2

C:\USERS\RU10\RU10_KPI.zip

Microsoft Excel Worksheet

Page 17: 241819261 Performance Analysis WI RU10 V3 Ppt

17 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Get agreement on KPI Target/Guarantees

1. Discuss with customer on the proposed KPIs and its counters buildingup the KPI

2. Get customer agreement on the list of KPI Guarantees for assessment

STEP-3

KPIs PI name Unit Benchmark KPIs Target KPI StatusRNC_727a Cell Availability, excluding blocked by user state (BLU) % o 99.5% aRNC_154d RRC Setup and Access Complete Ratio from end user perspective % o 99% aRNC_217d RRC Connection Success Ratio % o 99.20% aRNC_565f CSSR CS Voice % o 99.00% aRNC_231c RAB Success ratio, CS Voice % o 99.20% aRNC_566e CSSR UDI % o 98.50% aRNC_232c RAB Success ratio, CS Conv % o 99.00% aRNC_738a Minutes per Drop UDI min o aRNC_576d CSSR PS, NRT % o 99% aRNC_736a RAB Success Ratio, NRT Services, from User Perspective % o 99.00% aRNC_575d CSSR Streaming % o 98.50% aRNC_619a RAB Success Ratio, Streaming % o 99.00% aRNC_153b Soft HO Success rate, RT % o 99.5% aRNC_191b Soft HO Success rate, NRT % o 98.5% aRNC_300c ISHO Success Rate RT % o 97% aRNC_301c ISHO Success Rate NRT % o 83% aRNC_305a Inter-Frequency Hard Handover Success Rate (RT+NRT) % o 97% aRNC_605a HSDPA Accessibility for NRT Traffic from User point of View % o 95.5% aRNC_609a HSDPA Retainability for NRT Traffic % o 97% aRNC_733a HSDPA Serving Cell Change Success Rate % o 98% a

Page 18: 241819261 Performance Analysis WI RU10 V3 Ppt

18 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Login to NetAct Start Page

STEP-4-3

1

2 Select Reporting on the left pane

Method 1

Page 19: 241819261 Performance Analysis WI RU10 V3 Ppt

19 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Select Reporting Suites (RU10 version) on the right pane

STEP-4-3

3

Page 20: 241819261 Performance Analysis WI RU10 V3 Ppt

20 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Select System Program under Nokia 3GRAN

STEP-4-3

4

Page 21: 241819261 Performance Analysis WI RU10 V3 Ppt

21 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Select Absolute time and select KPI data period (start date & end date) – at least 2 to 4 weeks data

STEP-4-3

5

6 5

6

7

8

9

Select Object Type-> PLMN or RNC

7 Select Object under PLMN or RNC

8 Select Object Aggregation-> RNC

9 Select Time Aggregation -> daily

10 Click Generate button to generate reports 10

System program RNC and WCEL level possible in RU10

Page 22: 241819261 Performance Analysis WI RU10 V3 Ppt

22 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Click excel button to save the report into excel format

STEP-4-3

11

Used formula for CSSR and others

Page 23: 241819261 Performance Analysis WI RU10 V3 Ppt

23 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

Select all other reports under Nokia 3GRAN Reports (Capacity, services, traffic etc) in table below using step4 to step11

Reports give details information (root causes) for bad KPI analysis (daily, hourly)

STEP-4-3

12

Item 3G RAN Reports Report Name Object Type Object Aggregation Time Aggregation Measurement Period

1 System Program RSRAN000 PLMN PLMN Daily 4 Weeks

2 System Program RSRAN000 PLMN RNC Daily 4 Weeks

3 System Program RSRAN000 PLMN WCEL Daily 4 Weeks

4 Capactiy RSRAN066, RSRAN067 PLMN WCEL Daily 4 Weeks

5 Capactiy RSRAN066, RSRAN068 PLMN WCEL Hourly 4 Weeks

6 Service Level RSRAN073, RSRAN079 PLMN WCEL Daily 4 Weeks

7 ServiceLevel RSRAN073, RSRAN079 PLMN WCEL Hourly 4 Weeks

8 TrafficRSRAN070, RSRAN077

PLMN WCEL Daily 4 Weeks

9 TrafficRSRAN070, RSRAN077

PLMN WCEL Hourly 4 Weeks

10 Mobility & Handover

RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045

RSRAN046 PLMN WCEL Daily 4 Weeks

11 Mobility & Handover

RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045

RSRAN046 PLMN WCEL Hourly 4 Weeks

12 HSPA RSRAN051, RSRAN039 PLMN WCEL Daily 4 Weeks

13 HSPA RSRAN051, RSRAN039 PLMN WCEL Hourly 4 Weeks

14 Signalling RSRAN027, RSRAN0238 PLMN WCEL Daily 4 Weeks

15 Signalling RSRAN027, RSRAN038 PLMN WCEL Hourly 4 Weeks

Page 24: 241819261 Performance Analysis WI RU10 V3 Ppt

24 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

In OSS 5.1, RS offers (limited) possibility to create own reports, in case they are not included in report set.

STEP-4-3

13

14

Open content browser toCreate report

15

Select counter(s) to be included Into report (from different families possible

also)

16

Create report and givea name for it

Page 25: 241819261 Performance Analysis WI RU10 V3 Ppt

25 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- Reporting Suite/EOSFLEX

In OSS 5.1, RS offers (limited) possibility to create own reports.

STEP-4-3

OSS reports XML

17. Select Report upload page

Upload report template in xml format

18

19 Click Edit report

20

Add new counters or KPIs, Customize counter groupings, graphs and colour thresholds

Page 26: 241819261 Performance Analysis WI RU10 V3 Ppt

26 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Perform data analysis and assessment1. Assess weekly average PLMN/RNC KPI performance to identify KPIs below targets

Start from bigger picture assessment (PLNM -> RNC -> Cluster -> WCEL ) Weekly average will smooth the performance and gives better accuracy of performance assessment as daily

performance varies a lot especially in unloaded network

2. Assess network performance at RNC/Area level to check if bad performance happens across network or only particular RNC/Area

Compare different RNC/Regions performance

3. Apply drill down approach to assess bad performing KPIs in WCEL level Identify the failure call phases Categorizing failure ratio or distribution of each counters (radio, AC, transmission, BTS, RNC) Identify main cause of underperforming KPIs

4. Prioritize analysis Filter using high number of failures or high number failure ratio (weighting) Identify top 50 worst cells

5. Look at failure distribution in the network topology (rural, RNC border, expressway)

6. Make solution proposal to increase KPIs

STEP-5

Page 27: 241819261 Performance Analysis WI RU10 V3 Ppt

27 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Perform data analysis and assessment

Using Reporting Suite/EOSFLX 3G RAN Reports or MS Access KPI Queries

STEP-5

Weekly KPI( PLMN) < X %

No action needed

No

Yes

Yes

No

System Program (PLMN)

Weekly KPI (RNC) < X % ?

System Program (RNC)

Daily KPI (WCEL)

< X%

Identify Call failure phases of bad performing KPIs, for example CSSR

Identify failures root-causes and failure distribution of bad KPIs

Identify Top50 Worst Cells based on highest number of root causes failures

System Program (WCEL) Other 3G RAN Reports

Other 3G RAN Reports Yes

Mataching failure distribution into network topology

System Program (WCEL)

Solution Proposal

Mapinfo

System Program - RSRAN000

Page 28: 241819261 Performance Analysis WI RU10 V3 Ppt

28 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Call Setup failures for Voice and PacketRRC connection setup

RAN resources are reserved for signaling connection between UE and RNC

RRC accessConnection between UE and RRC

RRC activeUE has RRC connection. If dropped, also active RAB is dropped.

RAB setupAttempts to start the call

RAB setup access RAB active phase

UE has RAB connection

CSSR For Voice (RNC_565f) affected if any of the followings take

place. RRC Conn. Setup Fail RRC Conn. Access Fail RAB Setup Fail RAB Setup Access Fail

SetupComplete

AccessComplete

ActiveComplete

SetupSetup AccessAccess ActiveActive

Atte

mpt

s

Setup failures(blocking)

Access failures

Acce

ss ActiveRelease

ActiveFailures

RRCDrop

Succ

ess

Phase:

RRC and RAB phases

STEP-6

Page 29: 241819261 Performance Analysis WI RU10 V3 Ppt

29 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Call/packet Setup improvement in RU10RRC/RAB/PS call Setup & Access Analysis Process Flow Chart

Sites OK ?

Cell and Neighbour Cells availabilityAlarms/Tickets

Setup /Access

Yes

Setup /Access

Setup Failure Cause?

Capacity Optimisation

BTS/TRANS/FROZBS UL/DL Interference (DL codes)

AC

TroubleshootingRNC

RF Optimisation

Top (N) RRC Setup and Access failures

Top (N) RAB Setup/Access or PS Setup failures

Coverage/

Interference

setup

setup

Interference

Coverage

3G cell at inter-

RNC border ?

SRNS Relocation/Iur

troubleshooting

Yes

NO

Access

Setup/Access

SHO based on DSR, CPICH EcNo difference

RAB/DCH setup &failures, UL

coverage counters to see UL spikes

RRC_setup/SRB_act fails, RB_setup failures for

HSDPA

DCH reconfiguration failures AC/BTS/transSHO branch setup fail BTS/Iub, RNC capacity SW, new DSP counters

Rej_DCH_due to power or codes

(UL/DL)

RAB setup fail voice Iur/trans, DCH setup failure for NRT in Iur

Fail_MAC_d_setup_HSDPA

STEP-6

Page 30: 241819261 Performance Analysis WI RU10 V3 Ppt

30 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRRRC Setup Analysis

STEP-6

6-1

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution using Service Report -> RSRAN073

3. RRC_CONN_STP_FAIL_AC Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (Prxtarget ->30 dB)

M1002C1 CH_REQ_LINK_REJ_UL_SRNC ----> Evaluate Prx Resource Problem M1002C2 CH_REQ_LINK_REJ_DL_SRNC ----->Evaluate Ptx Resource Problem

4. RRC_CONN_STP_FAIL_BTSEvaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resourcesCheck BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to evaluate lack of Channel Elements (more info in RSRAN066)Expand the Capacity or decrease the traffic offered to the siteIn case BTS is not responding delete and re-create COCO

5. RRC_CONN_STP_FAIL_TRANSEvaluate Number of reconfiguration failure due the transmissionCheck COCO ConfigurationUse AAL2 Mux in case of two WAMExpand the Iub capacity or decrease the traffic offered to the site

6. RRC_CONN_STP_FAIL_RNC Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)Required ICSU log tracing if no RNC fault or SRNC relocation problem

Page 31: 241819261 Performance Analysis WI RU10 V3 Ppt

31 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRRRC Setup Analysis

STEP-6

6-1

3. RRC_CONN_STP_FAIL_AC due to UL throughput based admission control In RAS06/RU10, UL admission control has changed to have Throughput based AC control and power based

admission control The changes could lead to high AC failure in many call phases (RRRC/RAB setup for AMR/Rel99 NRT/HSPA) if

PrxLoadMarginDCH/PrxLoadMarginDCHMax setting is improper Recommended setting is PrxLoadMarginDCHMax=0dB & PrxLoadMarginDCH =6dB or higher

Page 32: 241819261 Performance Analysis WI RU10 V3 Ppt

32 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRRRC Access Analysis

STEP-6

6-2 7. RRC_CONN_ACC_FAIL_RADIOThis is quite Dominant failure cause in case of sync. problemsThis could happen in Coverage borderUL Coverage -> Decrease Cell Coverage (higher RxlevMin) if the cause is UL interference DL Coverage-> Increase Cell Coverage max :CPICHToRefRABOffset (2->0 dB)

Service Level -> RSRAN073

NBAP: Synchronisation Indication

L1 Synchronisation

RRC: RRC ConnectionSetupComplete (DCH)NBAP: Synchronisation Indication

L1 Synchronisation

RRC: RRC ConnectionSetupComplete (DCH) XUE BT

SRNC

XRRC Access Failures for L1 synchronization

NBAP: Synchronisation Indication

L1 Synchronisation

RRC: RRC ConnectionSetupComplete (DCH)NBAP: Synchronisation Indication

L1 Synchronisation

RRC: RRC ConnectionSetupComplete (DCH) XUE BTS

RNC

RRC Access Failures due to MSCell Reselections (no error)

8. RRC_CONN_ACC_FAIL_MSUL Coverage -> Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference if not the cause)

Page 33: 241819261 Performance Analysis WI RU10 V3 Ppt

33 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSR

RRC Access Analysis

STEP-6

6-2

9. If RRC setup/access failure due to Radio/MS, it is also possible to check whether UEs are located at distance area or close to cell edge area

Propagation delay counters from RRC measurement M1006C128-C148 reports call setup distance during RRC connection request or cell update This give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from neighbouring cells

0

100000

200000

300000

400000

500000

600000

PRACH_DELA

Y_CLA

SS_0

PRACH_DELA

Y_CLA

SS_1

PRACH_DELA

Y_CLA

SS_2

PRACH_DELA

Y_CLA

SS_3

PRACH_DELA

Y_CLA

SS_4

PRACH_DELA

Y_CLA

SS_5

PRACH_DELA

Y_CLA

SS_6

PRACH_DELA

Y_CLA

SS_7

PRACH_DELA

Y_CLA

SS_8

PRACH_DELA

Y_CLA

SS_9

PRACH_DELA

Y_CLA

SS_10

PRACH_DELA

Y_CLA

SS_11

PRACH_DELA

Y_CLA

SS_12

PRACH_DELA

Y_CLA

SS_13

PRACH_DELA

Y_CLA

SS_14

PRACH_DELA

Y_CLA

SS_15

PRACH_DELA

Y_CLA

SS_16

PRACH_DELA

Y_CLA

SS_17

PRACH_DELA

Y_CLA

SS_18

PRACH_DELA

Y_CLA

SS_19

PRACH_DELA

Y_CLA

SS_20

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

120.00%

averageCDF

Not available directly from RU10 Reporting Suite

Page 34: 241819261 Performance Analysis WI RU10 V3 Ppt

34 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSR: RU10 UL interference counters

10. In RU10, new coverage counters (RAN1630) for total uplink power (RTWP) measurement also can be used to identify RRC setup/access fail due to AC/Radio/MS.

All the received power is taken into account, not just Rel99 These counters could be used to see UL interference in the cell

M1000C320 Cell_Resource RTWP_CLASS_0M1000C321 Cell_Resource RTWP_CLASS_1M1000C322 Cell_Resource RTWP_CLASS_2M1000C323 Cell_Resource RTWP_CLASS_3M1000C324 Cell_Resource RTWP_CLASS_4M1000C325 Cell_Resource RTWP_CLASS_5M1000C326 Cell_Resource RTWP_CLASS_6M1000C327 Cell_Resource RTWP_CLASS_7M1000C328 Cell_Resource RTWP_CLASS_8M1000C329 Cell_Resource RTWP_CLASS_9M1000C330 Cell_Resource RTWP_CLASS_10M1000C331 Cell_Resource RTWP_CLASS_11M1000C332 Cell_Resource RTWP_CLASS_12M1000C333 Cell_Resource RTWP_CLASS_13M1000C334 Cell_Resource RTWP_CLASS_14M1000C335 Cell_Resource RTWP_CLASS_15M1000C336 Cell_Resource RTWP_CLASS_16M1000C337 Cell_Resource RTWP_CLASS_17M1000C338 Cell_Resource RTWP_CLASS_18M1000C339 Cell_Resource RTWP_CLASS_19M1000C340 Cell_Resource RTWP_CLASS_20M1000C341 Cell_Resource RTWP_CLASS_21

STEP-6

0.00

200.00

400.00

600.00

800.00

1 000.00

1 200.00

1 400.00

29.07.20

09__2

3:00:0

0

30.07.20

09__0

3:00

:00

30.07.20

09__0

7:00:00

30.0

7.2009

__11:0

0:00

30.0

7.200

9__15:0

0:00

30.07

.200

9__19:0

0:00

30.0

7.2009

__23:0

0:00

31.0

7.200

9__03:0

0:00

31.07

.200

9__07:0

0:00

31.07.20

09__

11:00:0

0

31.07.20

09__1

5:00

:00

31.07.20

09__1

9:00

:00

31.07

.2009

__23:00

:00

01.0

8.2009

__03:0

0:00

01.0

8.200

9__07:0

0:00

01.08

.2009

__11:00

:00

01.0

8.2009

__15:0

0:00

01.0

8.200

9__19:0

0:00

01.08

.200

9__23:0

0:00

02.08.20

09__

03:00:0

0

02.08.20

09__0

7:00

:00

02.08.20

09__1

1:00

:00

02.08

.2009

__15:00

:00

02.08.20

09__1

9:00

:00

02.08.20

09__2

3:00

:00

03.0

8.2009

__03:0

0:00

03.0

8.200

9__07:0

0:00

03.0

8.200

9__11:0

0:00

03.08.

2009

__15:0

0:00

RTW P_CLASS_14 (M1000C334, -92..-89 dBm) RTWP_CLASS_15 (M1000C335, -89..-86 dBm)RTW P_CLASS_16 (M1000C336, -86..-83 dBm ) RTWP_CLASS_17 (M1000C337, -83 dBm..-80 dBm)RTW P_CLASS_18 (M1000C338, -80..-75 dBm) RTWP_CLASS_19 (M1000C339, -75..-70 dBm)RTW P_CLASS_20 (M1000C340, -70..-65 dBm) RTWP_CLASS_21 (M1000C341, > -65 dBm)

6-2 RRC Access Analysis

Temporary High UL interference: class_21 could be seen

Page 35: 241819261 Performance Analysis WI RU10 V3 Ppt

35 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRSRB Active Fail Analysis in RU10

STEP-6

6-3

With RU10, there is new counters to measure the setup success of standalone Signaling Radio Bearers (SRBs). Standalone SRB means a successfully established RRC connection that is waiting for the RAB assignment

SRB active fail is pegged when RNC sent RRC:RRC connection Release before RAB assignment With RNC_1219a, this give better visibilities where low CSSR is somehow caused by failure in active standalone

SRB phase

Service Level -> RSRAN073

Page 36: 241819261 Performance Analysis WI RU10 V3 Ppt

36 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRAMR RAB setup/access Analysis

STEP-6

6-4

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution and main failure contributor using Services -> RSRAN073

3. RAB_STP_FAIL_XXX_ACCheck UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacityREQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resourceREQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resourceNO_CODES_AVAILABLE_SF128/SF32 -> Evaluate AMR voice / PS64 code congestionCheck parameter setting with UL throughput based AC and power based AC4. RAB_STP_FAIL_XXX_BTSEvaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resourcesCheck BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to evaluate lack of Channel ElementsExpand the Capacity or decrease the traffic offered to the site5. RAB_STP_FAIL_XXX_TRANSEvaluate Number of reconfiguration failure due the transmissionCheck M1005C128 CANC_ADD_SRNC_TRAN_STP_FAILCheck RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C5336. RAB_ACC_FAIL_XXX_UEEvaluate Cell resource Prx and Ptx (for example high uplink interference)Check RB reconfiguration failure ration ( If offset for activation time (RNC) setting is insufficient – recommmended is 500-700ms )7. RAB_ACC_FAIL_XXX_RNCTypically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)Required ICSU log tracing if no RNC fault or SRNC relocation problem

Service Level -> RSRAN073

Page 37: 241819261 Performance Analysis WI RU10 V3 Ppt

37 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRAMR RAB Setup/Access Analysis in RU10

STEP-6

6-4

8. RAB_Setup_FAIL_CS_Voice_LIC Counter incremented when the RNC rejects a CS Voice RAB request due to AMR capacity license Exceeded (only for RNC2600)

9. RAB_Setup_FAIL_CS_Voice_Iur_TRCounter incremented when a CS voice traffic class RAB setup fails due to Iur transport resources shortage

10. RAB_Setup_FAIL_CS_Voice_Iu_CSCounter incremented when a CS voice traffic class RAB setup fails due to Iu-CS transport resources

Service -> RSRAN073

Page 38: 241819261 Performance Analysis WI RU10 V3 Ppt

38 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRRel99 NRT RAB Setup Success Analysis

STEP-6

6-5

There is two ways to evaluate the Rel99 NRT RAB setup success performance M1001, RNC_576e Packet Service Setup Success Ratio (CSSR) / CSSR PS NRT M1022, RNC_943a R99 Setup Success Ratio from user perspective for NRT/ R99 stp SR Usr

Since RNC_576c (M1001) is measured NRT DCH setup upto 0/0kbps, it is always showing >99.5%. So it is not useful for data call setup analysis Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0) and ends with dedicated resource release (transfer back to FACH/PCH, DCH 0/0, RAB release, outgoing relocation, HHO, ISHO)

Service -> RSRAN073

M1001 M1022

Page 39: 241819261 Performance Analysis WI RU10 V3 Ppt

39 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low CSSRRel99 NRT RAB Setup Success Analysis in RU10

STEP-6

6-5

With RU10, there is new counters which gives better visibilities in terms of Rel99 NRT DCH setup failure causes (DCH0/0 -> DCH x/x kbps or DCH upgrade request) The number of NRT DCH setup rejects for interactive/BG traffic class due to running out of channelisation codes in DL and power in DL/UL (This counter includes initial DCH setups, handover attempts and channel type switches from HS-DSCH to DCH)The number of NRT DCH reconfiguration rejects (bitrate upgrade) for interactive/BG traffic class due to running out of channelizatin codes in DL and power in DL/UL Iur resources setup fails during user plane allocation/modification of PS NRT RAB over IUR branch

Not available in RU10 Report Set

M1002C553 Traffic REJ_DCH_DUE_CODES_INT_DLM1002C554 Traffic REJ_DCH_DUE_CODES_BGR_DLM1002C555 Traffic REJ_DCH_DUE_POWER_INT_DLM1002C556 Traffic REJ_DCH_DUE_POWER_BGR_DLM1002C557 Traffic REJ_DCH_REC_DUE_CODES_INT_DLM1002C558 Traffic REJ_DCH_REC_DUE_CODES_BGR_DLM1002C559 Traffic REJ_DCH_REC_DUE_PWR_INT_DLM1002C560 Traffic REJ_DCH_REC_DUE_PWR_BGR_DL

M1002C626 Traffic REJ_DCH_DUE_POWER_INT_ULM1002C627 Traffic REJ_DCH_DUE_POWER_BGR_ULM1002C628 Traffic REJ_DCH_REC_DUE_PWR_INT_ULM1002C629 Traffic REJ_DCH_REC_DUE_PWR_BGR_UL

0.00

10.00

20.00

30.00

40.00

50.00

60.00

70.00

80.00

90.00

100.00

1 11 21 31 41 51 61 71 81 91 101 111 121 131 141 151 161

max

, ave

occ

upan

cy &

blo

ckin

g (%

)

0.00

50.00

100.00

150.00

200.00

250.00

300.00

RNC_11a_Average code occupancy RNC_520b_Max Occupancy RNC_949a Code blocking rateRej DCH due codes Rej DCH REC due codes

Reconfig reject due to lack of codes M1004C165 FAIL_NRT_DCH_SETUP_IUR NRT DCH SETUP FAIL DUE TO IUR

M1004C166FAIL_NRT_DCH_UL_RECONF_IUR

NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR

M1004C167FAIL_NRT_DCH_DL_RECONF_IUR

NRT DCH DL RECONFIG FAIL FOR NRT RB DUE TO IUR

Page 40: 241819261 Performance Analysis WI RU10 V3 Ppt

40 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low Packet/session success rate (SSSR)Service -> RSRAN073

6-5 Rel99 Packet session setup failures Analysis (M1022)

Evaluate Dominant failures:

AC failure : lack of DL power or high UL interference, UL admission control parameter setting

Other failure: This could be due to max HSPA users limit reached or “radio link failure” during setup

BTS failure: lack of HW CE capacity

DMCU failure: DMCU/DSP faulty or lack of DSP resources in RNC

TRANS failure: lack of Iub capacity

UE failure: UE internal problem (not capability issue)

Cannot differentiate Rel99 DCH , HSDPA, HSUPA setup failure

_DCH_BGRPS_ATT_DCH M1022C8 +_DCH_INTPS_ATT_DCH M1022C7 D_ALLO_BGRD_D_REQ_D_ M1022C32 +D_ALLO_INTD_D_REQ_D_ M1022C31

100 Check KPI RNC_943a for low Rel99 packet SSSR

STEP-6

Page 41: 241819261 Performance Analysis WI RU10 V3 Ppt

41 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low Packet/session success rate (SSSR) Not available in report set

6-6 M1022 Rel99 Packet session setup failures Analysis in RU10 In RU10, new counters to identify the Rel99 NRT DCH setup and successful setup based on initial request bit rates or DCH upgrade bit rates Uplink initial request and success include also HSDPA UL return channel This is useful to identify each of the bit rate setup performance and its distribution as well as capacity bottleneckM1022C83 Packet_call INIT_DCH_REQ_64_ULM1022C84 Packet_call INIT_DCH_REQ_64_DLM1022C85 Packet_call INIT_DCH_REQ_128_ULM1022C86 Packet_call INIT_DCH_REQ_128_DLM1022C87 Packet_call INIT_DCH_REQ_256_ULM1022C88 Packet_call INIT_DCH_REQ_256_DLM1022C89 Packet_call INIT_DCH_REQ_384_ULM1022C90 Packet_call INIT_DCH_REQ_384_DL

M1022C91 Packet_call DCH_UPGR_REQ_64_ULM1022C92 Packet_call DCH_UPGR_REQ_64_DLM1022C93 Packet_call DCH_UPGR_REQ_128_ULM1022C94 Packet_call DCH_UPGR_REQ_128_DLM1022C95 Packet_call DCH_UPGR_REQ_256_ULM1022C96 Packet_call DCH_UPGR_REQ_256_DLM1022C97 Packet_call DCH_UPGR_REQ_384_ULM1022C98 Packet_call DCH_UPGR_REQ_384_DL

M1022C99 Packet_call SUCC_INIT_ALLO_64_ULM1022C100 Packet_call SUCC_INIT_ALLO_64_DLM1022C101 Packet_call SUCC_INIT_ALLO_128_ULM1022C102 Packet_call SUCC_INIT_ALLO_128_DLM1022C103 Packet_call SUCC_INIT_ALLO_256_ULM1022C104 Packet_call SUCC_INIT_ALLO_256_DLM1022C105 Packet_call SUCC_INIT_ALLO_384_ULM1022C106 Packet_call SUCC_INIT_ALLO_384_DL

M1022C107 Packet_call SUCC_INIT_ALLO_REQ_64_ULM1022C108 Packet_call SUCC_INIT_ALLO_REQ_64_DLM1022C109 Packet_call SUCC_INIT_ALLO_REQ_128_ULM1022C110 Packet_call SUCC_INIT_ALLO_REQ_128_DLM1022C111 Packet_call SUCC_INIT_ALLO_REQ_256_ULM1022C112 Packet_call SUCC_INIT_ALLO_REQ_256_DLM1022C113 Packet_call SUCC_INIT_ALLO_REQ_384_ULM1022C114 Packet_call SUCC_INIT_ALLO_REQ_384_DL

M1022C115 Packet_call SUCC_UPG_NRT_DCH_64_ULM1022C116 Packet_call SUCC_UPG_NRT_DCH_64_DLM1022C117 Packet_call SUCC_UPG_NRT_DCH_128_ULM1022C118 Packet_call SUCC_UPG_NRT_DCH_128_DLM1022C119 Packet_call SUCC_UPG_NRT_DCH_256_ULM1022C120 Packet_call SUCC_UPG_NRT_DCH_256_DLM1022C121 Packet_call SUCC_UPG_NRT_DCH_384_ULM1022C122 Packet_call SUCC_UPG_NRT_DCH_384_DL

M1022C123 Packet_call SUCC_UPG_NRT_DCH_REQ_64_ULM1022C124 Packet_call SUCC_UPG_NRT_DCH_REQ_64_DLM1022C125 Packet_call SUCC_UPG_NRT_DCH_REQ_128_ULM1022C126 Packet_call SUCC_UPG_NRT_DCH_REQ_128_DLM1022C127 Packet_call SUCC_UPG_NRT_DCH_REQ_256_ULM1022C128 Packet_call SUCC_UPG_NRT_DCH_REQ_256_DLM1022C129 Packet_call SUCC_UPG_NRT_DCH_REQ_384_ULM1022C130 Packet_call SUCC_UPG_NRT_DCH_REQ_384_DL

STEP-6

Page 42: 241819261 Performance Analysis WI RU10 V3 Ppt

42 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low Packet/session success rate (SSSR)

In RU10, new counters also to identify the Rel99 NRT DCH Reconfiguration failure during initial request (DCH0/0 to DCH x/x kbps or cell Fach to DCH) and bit rate upgrade requestAlso HSDPA uplink allocations update these counters

M1022C139

FAIL_REC_INTERA_DCH_UL_AC

DCH UPLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE

M1022C140 FAIL_REC_BGR_DCH_UL_AC

DCH UPLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND

M1022C141

FAIL_REC_INTERA_DCH_DL_AC

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE

M1022C142 FAIL_REC_BGR_DCH_DL_AC

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND

M1022C135 FAIL_REC_INTERA_DCH_UL_BTS

DCH UPLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C136 FAIL_REC_BGR_DCH_UL_BTS

DCH UPLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

M1022C137 FAIL_REC_INTERA_DCH_DL_BTS

DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C138 FAIL_REC_BGR_DCH_DL_BTS

DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

Not avaiable in Report Set

6-6 M1022 Rel99 Packet session setup failures Analysis in RU10

M1022C131

FAIL_REC_INTERA_DCH_UL_TRANS

DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE

M1022C132 FAIL_REC_BGR_DCH_UL_TRANS

DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND

M1022C133

FAIL_REC_INTERA_DCH_DL_TRANS

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE

M1022C134 FAIL_REC_BGR_DCH_DL_TRANS

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND

M1022C143 FAIL_REC_INTERA_DCH_UL_OTHDCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE

M1022C144 FAIL_REC_BGR_DCH_UL_OTHDCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND

M1022C145 FAIL_REC_INTERA_DCH_DL_OTHDCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE

M1022C146 FAIL_REC_BGR_DCH_DL_OTH

DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND

0.00

200.00

400.00

600.00

800.00

1 000.00

1 200.00

1 400.00

1 600.00

1 800.00

2 000.00

1 10 19 28 37 46 55 64 73 82 91 100 109 118

FAIL_REC_BGR_DCH_DL_TRANSFAIL_REC_INTERA_DCH_DL_TRANSFAIL_REC_INTERA_DCH_DL_BTSFAIL_REC_BGR_DCH_DL_BTS

FAIL_REC_INTERA_DCH_DL_AC

FAIL_REC_BGR_DCH_DL_AC

FAIL_REC_INTERA_DCH_DL_OTHFAIL_REC_BGR_DCH_DL_OTH

In DL, Failures mainly from AC (Interactive and Background)

STEP-6

Page 43: 241819261 Performance Analysis WI RU10 V3 Ppt

43 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Call/Packet Drop improvement in RU10Top (N) drops

Cell and its Neighbour Cells availabilityAlarms/Tickets

Configuration & Parameter audit

SHO Success Rate < 90%?

Conf OK ?

Site OK ?

ISHO Failures

Iur performance Investigation Iur

Audit adjacent sites for alarms, Availability, configuration and

capacity

TrafficNeighbours’ Performance (use SHO success per adjs counters to identify badly

performing neighbours) & Map

3G Cell at RNC border?

NO

YES

New site ?

Analyse last detailed radio measurements

RF and IFHO neighbour optimisation

No cell found

ratio >40 %

ISHO Success Rate <

90%

RF and ISHO neighbour optimisation

3G cell covers over a

coverage hole ?

3G cell at inter-RNC border ?

Wrong reference clock (10MHz tuning)

No cell found ratio > 90 % and enough

ADJG

2G Cell Doctor

2G Investigation : TCH blocking or

TCH seizure failure

(interference)

NO

YES

YES

YES

NO

YES

NO

YES

YES

SHO

ISHO

Top issues

SHO based on DSR, CPICH EcNo difference, SHO branch setup fail BTS/Iub

Relocation success in target RNC

HHO RSSI & BSIC time, ISHO cancellation

Max HSPA users in cell/RNC,RNC licensed capacity:Max AMR/Iups

throughput

HSDPA IFHO failures, reject CM

for IFHO

STEP-7

Page 44: 241819261 Performance Analysis WI RU10 V3 Ppt

44 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

High in AMR / Rel99 NRT call drop rate?1. Check if low RNC_231c RAB Success Ratio, Voice (CSR) cells and low RNC_571b

RAB retainability for PS cells and its neighbouring cells of any faulty alarms2. Identify call drop root cause failure distribution and main failure contributor

(radio, Iu, BTS, Iur, MS, RNC) – Services -> RSRAN079

3. Check SHO KPI if performance < 90% ( leads to radio failure) Check if cells are at RNC border (check Iur capacity and SRNC relocation problem) Detect badly performing neighbours using HO success rate per adjacency counters (M1013) High incoming HO failure rate in all adjs – check sync alarms Assessing neighbor list plan and visualization check with map Evaluate HO control parameters and trigger threshold

4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure) Check missing neighbour (M1015), GSM frequency plan neighbour RNC and MSC database

consistency audit, check alarm of reference clock in 3G or in 2G, check 2G TCH congestion Check RRC Drop ISHO RT / NRT

STEP-7

Page 45: 241819261 Performance Analysis WI RU10 V3 Ppt

45 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

High in AMR / Rel99 NRT call drop rate?

5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call drop cause > 50%)

Check UL Lost Active KPI from Iub counters (active L1 synchronization failure) to check UL/DL path loss problem

Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC Mapping radio failures with Tx power and CPICH related parameters -> CPICHToRefRABOffset,

PTXDPCH MAX Check Call reestablishment timer -> T315 for NRT and T314 for RT reestablishment Ecno distribution for bad coverage issue (M1007C38-M1007C47)

6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU

7. If high RAB_ACT_FAIL_XXX_BTS Check if any BTS faulty alarm (7653 cell faulty alarm) If no alarms, COCO detach/attach

8. If high RAB_ACT_FAIL_XXX_MS Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

STEP-7

Services -> RSRAN079

Page 46: 241819261 Performance Analysis WI RU10 V3 Ppt

46 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

High in AMR / Rel99 NRT call drop rate?STEP-7

SHO -> RSRAN028 9. SHO failure Analysis in RU10 Two new counters to identify SHO failure due to lack of Iub capacity or BTS HW CE capacity

RU10 also brings new counters to identify Ecno difference between source – target cell pairs and average Ecno, average RSCP for the neighbour cells based on scrambling codes

Counters updated if RAN1191 Detected Set Reporting and Measurements and RAN1189 CPICH Ec/N0 Difference Counters per Cell Pair feature is licensed

M1007C71SETUP_FAIL_SHO_BRANCH_BTS : When the SHO branch setup fails due to BTS resources. The BTS resources here mean either NBAP: RADIO LINK SETUP FAILURE, NBAP: RADIO LINK ADDITION FAILURE or that RNC does not receive any answer from the BTS. The counter is updated for the cell where the failure occurred. M1007C72 SETUP_FAIL_SHO_BRANCH_IUB :. When the SHO branch setup fails due to Iub transport. The transport failures include both CAC (Connection Admission Control) negative acknowledgements and signaling failures.

M1013C2 AutoDef_SHO_v2 CPICH_ECNO_SHO_DIFF_SUMM1013C3 AutoDef_SHO_v2 CPICH_ECNO_SHO_DIFF_DENOM

M1013C4 AutoDef_SHO_v2 CPICH_ECNO_SHO_SUMM1013C5 AutoDef_SHO_v2 CPICH_ECNO_SHO_DENOMM1013C6 AutoDef_SHO_v2 CPICH_RSCP_SHO_SUMM1013C7 AutoDef_SHO_v2 CPICH_RSCP_SHO_DENOM

M1028C0 Autodef_SHO_DSR CPICH_ECNO_DET_SUMM1028C1 Autodef_SHO_DSR CPICH_ECNO_DET_DENOMM1028C2 Autodef_SHO_DSR CPICH_RSCP_DET_SUMM1028C3 Autodef_SHO_DSR CPICH_RSCP_DET_DENOM

Page 47: 241819261 Performance Analysis WI RU10 V3 Ppt

47 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

High in AMR / Rel99 NRT call drop rate?STEP-7

10. Drop due to Radio Analysis in RU10 RU10 brings in new feature for RRC Re-establishment for RT and Multi-RAB

This feature is associated with parameter T314 and RT call re-establishment is “on” when T314> 0s. Generally, AMR drop call rate in OSS stats will greatly improved

New counters to measure the performance of call re-establishment for RT & Multi-RAB

M1006C186 RRC RRC_RE_EST_SUCC_RTM1006C187 RRC RRC_RE_EST_FAIL_UE_RTM1006C188 RRC RRC_RE_EST_FAIL_NOREPLY_RTM1006C189 RRC RRC_RE_EST_SUCC_MRM1006C190 RRC RRC_RE_EST_FAIL_UE_MRM1006C191 RRC RRC_RE_EST_FAIL_NOREPLY_MR

Page 48: 241819261 Performance Analysis WI RU10 V3 Ppt

48 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

High in AMR / Rel99 NRT call drop rate?

KPI Rel99 NRT DCH Drop Call Rate from Packet Call (M1022)

M_D_D_BGRPS_REL_NOR M1022C50M_D_D_INTPS_REL_NOR M1022C49BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61[%] ePerspectiv User End from Ratio SuccessR99 RNC_944a

1

M_D_D_BGRPS_REL_NOR M1022C50M_D_D_INTPS_REL_NOR M1022C49BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61[%] ePerspectiv User End from Ratio Call Dropped R99

STEP-7

Page 49: 241819261 Performance Analysis WI RU10 V3 Ppt

49 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Accessibility

HSDPA Accessibility failure cause analysis can be done with traffic measurements (RNC_605b) and Packet call measurements (RNC_914b)

STEP-8 System Program – RNC_605a Service Level –RNC_914a

Low HSDPA accessibility (RNC_605b)

Check Number of simultaneous HSDPA users in BTS or cell level depending on the scheduler type

Check BH Channel Element resource Usage (Lack of CE for UL return Channel)

Check BH UL Power Congestion(Lack of Radio resources for UL return Ch.)

Check BH AAL2 Iub congestion(Lack of Iub resources for UL return Ch.)

Check RB reconfiguration failure rate(Terminal Problem)

Check RNC Unit load (DMPG), max number of users/RNC, DSP failures and faulty alarms

No Action Needed

Too many HSDPA users reached

HSDPA Setup Fail due BTS

Rejection of UL Return Channel Rejections

HSDPA Setup Fail Iub (Both UL & DL)

HSDPA Setup Fail UE

HSDPA Setup Fail RNC Internal

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Based on Traffic measurement

analysis (M1002)

Page 50: 241819261 Performance Analysis WI RU10 V3 Ppt

50 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Accessibility STEP-8

PS Setup Failure due AC

Low HSPA Setup Performance (RNC_914b)

Yes

No

Air Interface

PS Setup Failure due BTS

Yes

No

BTS

PS Setup Failure due Iub

Yes

No

Iub

PS Setup Failure due to, DMCU

YesRNC

Problem In

PS Setup failure due to Others

No

YesHigh Traffic Event

Yes

RSRAN073

PS Setup failure due to UE

No action needed

Terminal Issue?

HSDPA Accessibility failure analysis based on Packet Call Measurement (M1022)

Others failure could be max HSPA users been reached or “radio link failure” during setup

If not DMCU faulty, check DSP resource usage and availability with RU10 M609 DSP Service Stats and M615 DSP Resource.

M613 not longer valid in RU10

Page 51: 241819261 Performance Analysis WI RU10 V3 Ppt

51 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA AccessibilityWith RU10, there is new counters in packet call to identify packet call attempt to cells which are not HSPA enabled. New KPI (RNC_914b) gives better results in terms of HSDPA accessibility when networks mixed with HSPA and non-HSPA enabled cells. This avoids separate aggregation which required previously in RAS06.RNC_914b does not include statistics from serving cell change mobility. Thus, the performance could be lower as well due to statistical calculation

STEP-8

RNC_914b: (NetAct names)

100* sum(HS_E_REQ_HS_E_ALLO_INT + HS_E_REQ_HS_E_ALLO_BGR + HS_E_REQ_HS_D_ALLO_INT + HS_E_REQ_HS_D_ALLO_BGR + HS_D_REQ_HS_D_ALLO_INT + HS_D_REQ_HS_D_ALLO_BGR) / sum(PS_ATT_HSDSCH_EDCH_INT + PS_ATT_HSDSCH_EDCH_BGR + PS_ATT_HSDSCH_DCH_INT + PS_ATT_HSDSCH_DCH_BGR - HS_D_REQ_D_D_ALLO_BGR_CELL - HS_D_REQ_D_D_ALLO_INT_CELL - HS_E_REQ_D_D_ALLO_BGR_CELL - HS_E_REQ_D_D_ALLO_INT_CELL)

RNC_605b: (NetAct names)100* sum(ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FLOW_BGR) / sum(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR + SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR + SETUP_FAIL_UE_HS_DSCH_INT + SETUP_FAIL_UE_HS_DSCH_BGR + DCH_SEL_MAX_HSDPA_USERS_INT + DCH_SEL_MAX_HSDPA_USERS_BGR)

The number of DCH/DCH allocations after an HS-DCSH/E-DCH request for the background traffic class due to the cell not supporting HSUPA and HSDPA

Page 52: 241819261 Performance Analysis WI RU10 V3 Ppt

52 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

1. Identify root cause of failure distribution and main failure contributor

2. If high HSDPA Access Failure _too many HSDPA users Check simultaneous HSDPA users (RNC_646c to RNC_654c) & (RNC_1028b to RNC_1035b)

& (RNC_1665a to RNC_1668a) RU10 new counters on max & average HSPA users

3. If high HSDPA Access Failure_UL DCH Rejected HS-DSCH return channel due to lack of radio power resource Check M1002C521 or M1002C522 or M1000C144 – only when HSDPA static allocation Check Cell resource PrxTotal, PtxTotal Check parameter setting for uplink throughput based and interference based admission control

4. If high HSDPA Access Failure_UE Check RB reconfiguration failure rate ICSU log for UE types troubleshooting ? RU10 new counters to measure HSDPA setup success in RB reconfiguration phase

Low HSDPA AccessibilitySTEP-8 Service level -> RSRAN073

M1000C282 Cell_Resource MAX_HSDPA_USERS_IN_CELLM1000C283 Cell_Resource MAX_HSUPA_USERS_IN_CELLM1000C284 Cell_Resource SUM_HSDPA_USERS_IN_CELLM1000C285 Cell_Resource DENOM_HSDPA_USERS_PER_CELLM1000C286 Cell_Resource SUM_HSUPA_USERS_IN_CELLM1000C287 Cell_Resource DENOM_HSUPA_USERS_PER_CELL

M1006C149 RRC ATT_RB_SETUP_HSDPAM1006C150 RRC SUCC_RB_SETUP_HSDPAM1006C192 RRC FAIL_RB_SETUP_HSDPA_NOREPLYM1006C193 RRC FAIL_RB_SETUP_HSDPA_UE

Page 53: 241819261 Performance Analysis WI RU10 V3 Ppt

53 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Accessibility5. If high HSDPA Access Failure_BTS

Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH) Too high SHO overhead – all branches must have enough CE capacity if UE is in SHO when HS-DSCH

allocation is started RU10 brings new counters measure on the setup/success/failure for HSDPA MAC-d setup on

NBAP Radio link Reconfiguration phase

6. HS-DSCH return channel setup fail due to Iub transport Breakdown the failure distribution (64,128,384,MAC-d) Evaluate RU10 UL rejection failure cause (M1022C131…C146) Evaluate number of reconfiguration failure due the transmission Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

STEP-8

0

200

400

600

800

1000

1200

1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 2870

5

10

15

20

25

30

SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic)

AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)

M1005C241 L3Iub ATT_MACD_SETUP_FOR_HSDPAM1005C242 L3Iub SUCC_MACD_SETUP_FOR_HSDPAM1005C247 L3Iub FAIL_MACD_SETUP_HSDPA_NORESPM1005C248 L3Iub FAIL_MACD_SETUP_HSDPA_RNLM1005C249 L3Iub FAIL_MACD_SETUP_HSDPA_TRM1005C250 L3Iub FAIL_MACD_SETUP_HSDPA_PROTM1005C251 L3Iub FAIL_MACD_SETUP_HSDPA_MISC

Page 54: 241819261 Performance Analysis WI RU10 V3 Ppt

54 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Retainability

HSDPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_609a) and Packet Call measurements (RNC_920a)- optional measurement. Radio link failures should be analyzed.

STEP-9 System Program Report

RNC_920a/609a<X %

Check SCC Failure Rate – Radio, Iub, CE resource congestion

Check for RNC failures and use RNC logging if required

No Action Needed

HSPA packet call Radiolink failures

HSPA packet call failures - other

No

Yes

Yes

Yes

No

Check CQI distribution and Ecno distribution for coverage issue

Check HSDPA mobility parameter – Add/Drop window, SCC parameter

Service - RSRAN079

Page 55: 241819261 Performance Analysis WI RU10 V3 Ppt

55 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Retainability (RNC_920a)

KPI RNC_920a :100 -100 * sum ( PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR + PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR ) -------------------------------------------- sum ( PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR + PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR + PS_REL_NORM_HS_E_INT + PS_REL_NORM_HS_E_BGR + PS_REL_NORM_HS_D_INT + PS_REL_NORM_HS_D_BGR )

RNC_609a:100 * sum(REL_ALLO_NORM_HS_DSCH_INT + REL_ALLO_NORM_HS_DSCH_BGR) ---------------------------------------------------------------- sum( REL_ALLO_NORM_HS_DSCH_INT + REL_ALLO_NORM_HS_DSCH_BGR + REL_ALLO_OTH_FAIL_HSDSCH_INT + REL_ALLO_OTH_FAIL_HSDSCH_BGR + REL_ALLO_RL_FAIL_HS_DSCH_INT + REL_ALLO_RL_FAIL_HS_DSCH_BGR)

STEP-9

Service Level -> RSRAN079

Page 56: 241819261 Performance Analysis WI RU10 V3 Ppt

56 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

1. Identify root cause failure distribution and main contributor of low retainability

2. If high HSDPA Radio Link Failures (NRT) – dominant cause Compare to Cell Update ATT due to Radio link Failure (M1006C39) and Cell Update ATT due

to RLC Recoverable Error (M1006C40) Check Serving Cell Change failure rate (KPI RNC_733a) - high SCC failures lead to radio link

failure Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue

(M1007C38-M1007C47) Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late) Check call re-establishment T315 timer due to radio link failure

Low HSDPA RetainabilitySTEP-9Service Level -> RSRAN079-> RNC_609a

Normal release

Page 57: 241819261 Performance Analysis WI RU10 V3 Ppt

57 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Retainability

3. If high HSDPA Non- Radio Link Failures (NRL) UE responding with some failure message or not responding to some message but no RL

failure (timer expiry) Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure

rate Required ICSU log for further troubleshooting ?

STEP-9Service Level -> RSRAN079

Page 58: 241819261 Performance Analysis WI RU10 V3 Ppt

58 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA SCC Success Ratio HSDPA SCC failure causes Analysis Flow Chart

There seems not to be a relation with poor SCC success and HSDPA retainability. SCC success rate for HSDPA and HSUPA is not very accurate in cell level as denominator is incremented in the source cell (old serving cell) and numerator is incremented in the target cell (new serving cell).

STEP-10

Top N cells

SCC Fail BTS

RNC_733a < X %

SCC Fail AC SCC Fail Transmission SCC Fail UE

SCC Fail Others

No action needed

Check CE resource usage at BH

scrambling code congestion BH

DL power congestion

BH ?

Check AAL2 Iub resource congestion at BH

Check RB reconfiguration Failure rate

Check RNC internal transport resources (DMPG) – ICSU troubleshooting

No

Yes

YesYes Yes YesYes

No No NoNo

No

HSDPA SCC Success Ratio

SCC Fail Prevention

timer

Check HSDPACellChangeMinInterval parameter

Check Maximum number of HSDPA users

No

No

Yes

Mobility & Handover –RSRAN033

RNC_733a:100* sum(SCC_INTRA_BTS_SUCCESSFUL + SCC_INTER_BTS_SUCCESSFUL) / sum(SCC_STARTED_CPICH_ECNO + SCC_STARTED_UL_SIR_ERROR + SCC_STARTED_ACTIVE_SET_UPD + SCC_STARTED_OTHER_REASON)

Page 59: 241819261 Performance Analysis WI RU10 V3 Ppt

59 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA SCC Success Ratio

1. Determine HSDPA SCC success ratio (RNC_733a), SCC failure rate and failure cause distribution

2. Check target cells HSDPA Setup performance (M1002C401 – M1002C428) if source

cells SCC failure rate is high To find out which target cells are causing the SCC failure

3. If high SCC_FAILED_due_to_AC Check target cells M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 if SCC

failures due to the lack of DL power (SCC_Failed_due_to_AC) Check target cells M1002C521 or M1002C522 or M1000C144 (RAS06) – only when HSDPA static

allocation Check target cells number of simultaneous active HSDPA users

STEP-10

Mobility & Handover –RSRAN033

Page 60: 241819261 Performance Analysis WI RU10 V3 Ppt

60 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA SCC Success Ratio 4. If high SCC_FAILED_due_to_BTS

Check target cells M1002C416/424 SETUP_FAIL_BTS_HS_DSCH_XXX Check target cells CE resource utilisation at BH using M5001 counters for lack of UL return channel

resource Check NBAP Radio Link Reconfiguration Failure rate Check SHO overhead – use lower value for AdditionWindow (closer to 0 dB) in HSDPA FMCS than in the

RT/NRT FMCS, to have smaller SHO area for HSDPA users. 5. If high SCC_FAILED_due_to_UE

Check target cells M1002C415/423 SETUP_FAIL_UE_HS_DSCH_XXX Check RB reconfiguration Failure rate Require ICSU troubleshooting for UE types monitoring

6. If high SCC_FAILED_due_to_TRANS Check target cells of M1002C414 SETUP_FAIL_IUB_MAC_D_INT or M1002C422

SETUP_FAIL_IUB_MAC_D_BGR Evaluate number of reconfiguration failure due the transmission Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL Check M1001C531-C533 RAB_STP_FAIL_XXX_IUB_AAL2

7. If high SCC_FAILED_due_to_Others Check RNC internal transport resources usage (DMPG) Require ICSU troubleshooting

STEP-10

Mobility & Handover –RSRAN033

Page 61: 241819261 Performance Analysis WI RU10 V3 Ppt

61 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Cell/User ThroughputSTEP-11

HSDPA throughput limiting factors:

System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039

HSDPA Throughput AnalysisAir interface support from CQI distribution

HSDPA Throughput Available from Iub

BTS Power Availability for HSDPA

Cell Channelisation code Availability for

HSDPA

RNC limiting factors: DSP, #simultaneous HSDPA users and

throughput

Iu-PS capacity available or HSDPA

HSDPA UL Return channel limitation (CE)

HSDPA UL Return channel limitation (Iub)

HSDPA UL Return channel limitation (UL

Interference)

Problem in

Air Interface

Iub

BTS

RNC

Iu-PS

BTS scheduler limitation

(#simultaneous users per scheduler)

Page 62: 241819261 Performance Analysis WI RU10 V3 Ppt

62 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Cell/User Throughput

STEP-11

1. Check HSDPA active Throughput in the cell (RNC_722b/c) and Average throughput in the cell (RNC_606c) or with cell throughput in RNC/WBTS measurements (RNC_941a) KPI RNC_941a : sum ( HS_DSCH_DATA_VOL * 8) /sum ( 1000 * PERIOD_DURATION)* 60 (kbps)

RNC_606c: sum(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS) / sum(PERIOD_DURATION)*60 (kbps)

2. Calculate rough HSDPA User Throughput by dividing RNC_722b with average number of simultaneous HSDPA users (RNC_726a) or two new KPIs based on users in buffer where v2.1 is for user throughput <1.5Mbps

System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039Traffic - RSRAN077

ELLSS_3_0_IN_CHSDPA_USERELLSS_2_1_IN_CHSDPA_USERELLSS_1_2_IN_CHSDPA_USERELLSS_0_3_IN_CHSDPA_USERELLSS_2_0_IN_CHSDPA_USERELLSS_1_1_IN_CHSDPA_USERELLSS_0_2_IN_CHSDPA_USERELLSS_1_0_IN_CHSDPA_USERELLSS_0_1_IN_CHSDPA_USER

ELLS)S_3_0_IN_CHSDPA_USERELLSS_0_3_IN_CHSDPA_USERELLSS_2_1_IN_CHSDPA_USERCELLSRS_1_2_IN_(HSDPA_USE3

ELLS)S_2_0_IN_CHSDPA_USERELLSS_1_1_IN_CHSDPA_USERCELLSRS_0_2_IN_(HSDPA_USE2ELLS)S_1_0_IN_CHSDPA_USERCELLSRS_0_1_IN_(HSDPA_USE

_PER_TTI_WITH_DATAHSDPA_BUFF

500TSHS_MACD_BIDISCARDED_-SS_MACD_BITRECEIVED_H v3.0experienceuser End

2_PER_TTI_WITH_DATAHSDPA_BUFF

500TSHS_MACD_BIDISCARDED_-SS_MACD_BITRECEIVED_H v2.1experienceuser End

M5002C21 Cell_Throughput_WBTS HS_TOTAL_DATA

Available in RU10

Page 63: 241819261 Performance Analysis WI RU10 V3 Ppt

63 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Cell/User ThroughputBelow is comparison of all the throughput per user formulas as well as RNC_722b

Average HSDPA Throughput per User has increased a lot based on users in

data buffer

STEP-11

Page 64: 241819261 Performance Analysis WI RU10 V3 Ppt

64 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA cell/user Throughput

STEP-11

3. Check RNC_706a Ave Reported CQI and CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47)

4. High CQI / Ecno but low HSDPA user throughput Check problem at core network or application server (FTP, HTTP) or in measurement tools &

PC settings Check any shortage on Iub user plane and CEs shortage due to DCH traffic is too high Check if UL return channel is limiting due to interference (PrxLoadMarginMaxDCH -> 0 dB) Check the if there is code blocking for HSDPA (set HSPDSCHMarginSF128 from 8-> 0) Check HSDPA power parameter setting (M1000C232-C235) & (M1000C236-C239) Check simultaneous HSDPA users in the Node B Scheduler (increase the scheduler capacity

from 16 users/BTS to 48 users/BTS (16/cell) Check HSDPA FMCS mobility parameters (lower window add for HSDPA than for R99 to save

capacity in target cell due to smaller SHO OH) Throughput limitation per user (throttled user) is active in Core?

System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039

Page 65: 241819261 Performance Analysis WI RU10 V3 Ppt

65 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSDPA Cell/Users Throughput

STEP-11

5. HSDPA power in BTS The counters tell the number of samples (TTI) per class when the actual used HS-PDSCH power (given as %

value from the max HS-PDSCH pwr) is within the limits defined for a class This give hints whether low HSDPA throughput due to lack of HSDPA power (high RT/Rel99 NRT traffics in the

cell)

6. DMPG resource sharing causes the total throughput per user is not only limited by the # simultaneous users per cell and their activity but also the amount of simultaneous users per DMPG (per RNC sharing the total RNC throughput) and their activity

M5000C268 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_01M5000C269 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_02M5000C270 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_03M5000C271 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_04M5000C272 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_05M5000C273 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_06M5000C274 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_07M5000C275 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_08M5000C276 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_09M5000C277 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_10

Max HSDPA Throughput per RNC (62 x 7.2Mbps currently on RNC Throughput 450Mbps)

Sum ( #_users_with_data_in_buff_per_TTI / all_active_TTIs) x avg_#_HSDPA_users_in_RNC

HSDPA_NRTD_PEAK_CALLS

Page 66: 241819261 Performance Analysis WI RU10 V3 Ppt

66 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

HSUPA Accessibility Failure Cause Analysis can be done based on Traffic measurements (RNC_913a) and Packet call measurements (RNC_915c)- optional

Low HSUPA Accessibility

Low HSUPA accessibility

Check Number of simultaneous HSUPA users(20/cell, 24/NodeB )

Check BH Channel element resource usage UL/DL(BTS in state that no capacity available for EDCH)

HSUPA is not supported in SHO branch

Check BH Channel element resource usage UL/DL

Check RB reconfiguration failure rate(Terminal problem)

Check AAL2 connections (not enough CID) or Signalling problems

No Action Needed

Too many HSUPA users reached

UL DCH selected due BTS HW

HSUPA fail due Not Acceptable Active

Set

HSUPA Setup Fail BTS

HSUPA Setup Fail UE

HSUPA Setup Fail TRANS

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

No

Go for troubleshooting( E.g. RNC internal failures)

HSUPA Setup Fail Other

Yes

Set

up

fai

lur es

Sel

ect

ion

fai

lur es

STEP-12

Based on failure analysis from Traffic Measurement (M1002)

Page 67: 241819261 Performance Analysis WI RU10 V3 Ppt

67 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Accessibility

RNC_915c :

100* sum(HS_E_REQ_HS_E_ALLO_STRE + HS_E_REQ_HS_E_ALLO_INT + HS_E_REQ_HS_E_ALLO_BGR) / sum(PS_ATT_HSDSCH_EDCH_STRE + PS_ATT_HSDSCH_EDCH_INT + PS_ATT_HSDSCH_EDCH_BGR - HS_E_REQ_HS_D_ALLO_STR_CELL - HS_E_REQ_HS_D_ALLO_BGR_CELL - HS_E_REQ_HS_D_ALLO_INT_CELL - HS_E_REQ_D_D_ALLO_STR_CELL - HS_E_REQ_D_D_ALLO_BGR_CELL - HS_E_REQ_D_D_ALLO_INT_CELL)

With RU10, there is new counters in packet call to identify packet call attempt to cells which are not HSPA enabled. New KPI (RNC_915c) gives better results in terms of HSUPA accessibility when networks mixed with HSPA and non-HSPA enabled cells. This avoids separate aggregation which required previously in RAS06.RNC_914b does not include statistics from serving cell change mobility. Thus, the performance could be lower as well due to statistical calculation

RNC_913a:100 * sum ( ALLO_SUCCESS_EDCH_INT + ALLO_SUCCESS_EDCH_BGR ) --------------------------------------------- sum ( ALLO_SUCCESS_EDCH_INT + ALLO_SUCCESS_EDCH_BGR + EDCH_ALLO_CANC_NA_AS_BGR + EDCH_ALLO_CANC_NA_AS_INT + UL_DCH_SEL_MAX_HSUPA_USR_BGR + UL_DCH_SEL_MAX_HSUPA_USR_INT + UL_DCH_SEL_BTS_HW_INT + UL_DCH_SEL_BTS_HW_BGR + SETUP_FAIL_EDCH_BTS_BGR + SETUP_FAIL_EDCH_BTS_INT + SETUP_FAIL_EDCH_OTHER_BGR + SETUP_FAIL_EDCH_OTHER_INT + SETUP_FAIL_EDCH_TRANS_BGR + SETUP_FAIL_EDCH_TRANS_INT + SETUP_FAIL_EDCH_UE_BGR + SETUP_FAIL_EDCH_UE_INT )

STEP-12System Program -> RSRAN000

Service Level-> RSRAN073

The number of DCH/DCH allocations after an HS-DCSH/E-DCH request for the backg/interactive traffic class due to the cell not supporting HSUPA and HSDPA

Page 68: 241819261 Performance Analysis WI RU10 V3 Ppt

68 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Accessibility HSUPA Accessibility KPI is measured with RNC_913a (Traffic Measurement) If HSDPA setup is failing also HSUPA setup will fail, but it could be also that only HSUPA will fail. The reasons are similar to HSDPA

RNC_956b E-DCH Setup FR due to BTS (RL reconfiguration failure to RNC)RNC_1105b E-DCH Setup FR due to Transport (RL reconfiguration cancel from RNC)RNC_1106b E-DCH Setup FR due to UE (RB reconfiguration failure from UE)RNC_1104b E-DCH Setup FR due to Other Failures (RNC internal reason)RNC_1103bE-DCH Allocation FR due to NA AS (due to non-acceptable E-DCH active set)

Also there could be too many HSUPA users (20/cell, 24/NodeB,In RU10:64 users/Node B)RNC_968b UL DCH Selected due to too many HSUPA usersRNC_969b DL DCH Selected due to the HSDPA power (updated when only HSDPA static power allocation used)

HSUPA setup failed due to BTS reports HSUPA cannot be allocatedRNC_957b E-DCH Not Selected due the BTS HW (BTS sent radio resource measurement report)M1000C268-C270 – These counters measure the BTS HW limitation during HSUPA Calls

STEP-12System Program -> RSRAN000Service Level -> RSRAN073

Page 69: 241819261 Performance Analysis WI RU10 V3 Ppt

69 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Accessibility

For static resource allocation the power could limitM1002C521 DL_DCH_SEL_HSDPA_POWER_INT M1002C522 DL_DCH_SEL_HSDPA_POWER_BGRM1002C602DL_DCH_SEL_HSDPA_POWER_STR

AC: (PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA) EDCH cannot be allocated in case HSUPA is not supported in SHO branch

M1002C519 EDCH_ALLO_CANC_NA_AS_INTM1002C520 EDCH_ALLO_CANC_NA_AS_BGRM1002C601EDCH_ALLO_CANC_NA_AS_STR

STEP-12 System Program -> RSRAN000Service Level -> RSRAN073

Page 70: 241819261 Performance Analysis WI RU10 V3 Ppt

70 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

HSUPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_919a) and Packet call measurements (RNC_921b)

Low HSUPA RetainabilitySTEP-13

RNC_919a / 921b <

X %

Check SCC Failure Rate – Radio, Iub, CE resource congestion

Check for RNC failures??

No Action Needed

HSPA packet call Radiolink failures

HSPA packet call failures - other

No

Yes

Yes

Yes

No

Check CQI distribution and Ecno distribution for coverage issue

Check HSDPA mobility parameter – Add/Drop window, SCC parameter

Page 71: 241819261 Performance Analysis WI RU10 V3 Ppt

71 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Retainability

RNC_921b (Packet Call Measurement) 100-100* sum(PS_REL_RL_FAIL_HS_E_STRE + PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_E_STRE + PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR) / sum(PS_REL_RL_FAIL_HS_E_STRE + PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_E_STRE + PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR + PS_REL_NORM_HS_E_STRE + PS_REL_NORM_HS_E_INT + PS_REL_NORM_HS_E_BGR + PS_SWI_HS_E_TO_D_D_STRE + PS_SWI_HS_E_TO_D_D_INT + PS_SWI_HS_E_TO_D_D_BGR)

RNC_919a (traffic measurement)100 * sum ( REL_EDCH_NORM_INT + REL_EDCH_NORM_BGR + REL_EDCH_HSDSCH_SCC_INT + REL_EDCH_HSDSCH_SCC_BGR ) ---------------------------------------- sum ( REL_EDCH_NORM_INT + REL_EDCH_NORM_BGR + REL_EDCH_HSDSCH_SCC_INT + REL_EDCH_HSDSCH_SCC_BGR + REL_EDCH_RL_FAIL_INT + REL_EDCH_RL_FAIL_BGR + REL_EDCH_OTHER_FAIL_INT + REL_EDCH_OTHER_FAIL_BGR )

System Program - RSRAN000Services -> RSRAN079

STEP-13

Page 72: 241819261 Performance Analysis WI RU10 V3 Ppt

72 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

The retainability of all successfully allocated E-DCH resources for NRT traffic is measured with KPI RNC_919a (Traffic Measurement) There are several reasons for HSUPA release:

RNC_1108a E-DCH Rel due to RL FailuresRNC_1109a E-DCH Rel due to Other FailuresRNC_1115a E-DCH Rel due to HS-DSCH serving cell change

(SCC released is included in both nominator/denominator of RNC_919a)

RL fail is incremented If: a radio link failure happens during HSDPA call (coverage issue) uplink RLC unrecoverable error happens (Cell Update by UE) RLC-entity in RNC reports RLC protocol reset

If RNC_919a < x%, refer also to step9 (low HSDPA retainability)

Low HSUPA RetainabilitySTEP-13

System Program - RSRAN000Services -> RSRAN079

Page 73: 241819261 Performance Analysis WI RU10 V3 Ppt

73 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA SCC Success Ratio

HSUPA Serving Cell Success Ratio is measured with RNC_918b HSUPA Serving Cell Change are only done when the HSDPA Serving Cell Change is needed (HSUPA SCC attempt is pegged along with HSDPA SCC attempt) There are no failure counters for E-DCH serving cell change, but the failures are seen through HS-DSCH serving cell change counters Check M1008C242 EDCH_DOWNG_DCH_IN_SCC - this counter incremented in new HS-DSCH serving cell when HS-DSCH serving cell change was successful, but uplink was downgraded from E-DCH to DCH

RNC_918b:

100 * sum ( EDCH_SCC_INTRA_BTS_SUCCESS + EDCH_SCC_INTER_BTS_SUCCESS ) -------------------------------------------

sum ( EDCH_SCC_STARTED )

System Program – RSRAN000Mobility & Handover –RSRAN033

STEP-14

Page 74: 241819261 Performance Analysis WI RU10 V3 Ppt

74 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Throughput

Check Mininum, Maximum & Average HSUPA throughput from WBTS counter measurement (M5000C153)

Check average or data volume HSUPA throughput from Cell Throughput measurement with RNC_952csum(NRT_EDCH_UL_DATA_VOL + RT_E_DCH_UL_STREA_DATA) * 8 / sum(PERIOD_DURATION)*1000000*60

Check HSUPA throughput from M5002 Cell Throughput_WBTS and its throughput distributions in classes

Check HSUPA user throughput by dividing aboved with KPI RNC_1037a -Average number of simultaneous HSUPA users, during HSUPA usage

Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000

STEP-15

Counter ID Measurement Counter nameM5002C41 Cell_Throughput_WBTS UE_HSUPA_TP03M5002C42 Cell_Throughput_WBTS UE_HSUPA_TP04M5002C43 Cell_Throughput_WBTS UE_HSUPA_TP05M5002C44 Cell_Throughput_WBTS UE_HSUPA_TP06M5002C45 Cell_Throughput_WBTS UE_HSUPA_TP07M5002C38 Cell_Throughput_WBTS UE_HSUPA_TP00M5002C39 Cell_Throughput_WBTS UE_HSUPA_TP01M5002C40 Cell_Throughput_WBTS UE_HSUPA_TP02M5002C46 Cell_Throughput_WBTS UE_HSUPA_TP08M5002C47 Cell_Throughput_WBTS UE_HSUPA_TP09M5002C48 Cell_Throughput_WBTS UE_HSUPA_TP10M5002C49 Cell_Throughput_WBTS UE_HSUPA_TP11M5002C2 Cell_Throughput_WBTS EDCH_DATA_SCELL_ULM5002C3 Cell_Throughput_WBTS EDCH_DATA_NSC_S_EDCH_ULM5002C4 Cell_Throughput_WBTS EDCH_DATA_NSC_NS_EDCH_UL

Note: HSUPA cell throughput measurement is less accurate than HSDPA cell throughput due to counters updating across total measurement period and not in active data transfer period

Page 75: 241819261 Performance Analysis WI RU10 V3 Ppt

75 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA ThroughputCheck CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47) Check If low throughput due to high number of retransmission & failed retransmission (RNC_917a HSUPA MAC-es BLER) Check KPI RNC_1165a/RNC_1166a for low HSUPA throughput due to Iub congestion (frame delay or frame loss) In RU10, there is new counters to check on the Rise Over Thermal in Fractional load:L = 1 - (Pnoise/Ptotal), The fractional load is calculated in the normal scheduling operation. HSUPA throughput will be limited by high fractional load in the cells

Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000

STEP-15

M5000C245 FRACT_LOAD_DISTR_CLASS_00 - Ptotal>=Pnoise : (L = 0). M5000C246 FRACT_LOAD_DISTR_CLASS_01 - Ptotal>=Pnoise : (0 < L <= 0.05)M5000C247 FRACT_LOAD_DISTR_CLASS_02 - Ptotal>=Pnoise : (0.05 < L <= 0.1)M5000C248 FRACT_LOAD_DISTR_CLASS_03 - Ptotal>=Pnoise : (0.1 < L <= 0.15)M5000C249 FRACT_LOAD_DISTR_CLASS_04 - Ptotal>=Pnoise : (0.15 < L <= 0.2)M5000C250 FRACT_LOAD_DISTR_CLASS_05 - Ptotal>=Pnoise : (0.2 < L <= 0.25)M5000C251 FRACT_LOAD_DISTR_CLASS_06 - Ptotal>=Pnoise : (0.25 < L <= 0.3)M5000C252 FRACT_LOAD_DISTR_CLASS_07 - Ptotal>=Pnoise : (0.3 < L <= 0.35)M5000C253 FRACT_LOAD_DISTR_CLASS_08 - Ptotal>=Pnoise : (0.35 < L <= 0.4)M5000C254 FRACT_LOAD_DISTR_CLASS_09 - Ptotal>=Pnoise : (0.4 < L <= 0.45)M5000C255 FRACT_LOAD_DISTR_CLASS_10 - Ptotal>=Pnoise : (0.45 < L <= 0.5)M5000C256 FRACT_LOAD_DISTR_CLASS_11 - Ptotal>=Pnoise : (0.5 < L <= 0.55)M5000C257 FRACT_LOAD_DISTR_CLASS_12 - Ptotal>=Pnoise : (0.55 < L <= 0.6)M5000C258 FRACT_LOAD_DISTR_CLASS_13 - Ptotal>=Pnoise : (0.6 < L <= 0.65)M5000C259 FRACT_LOAD_DISTR_CLASS_14 - Ptotal>=Pnoise : (0.65 < L <= 0.7)M5000C260 FRACT_LOAD_DISTR_CLASS_15 - Ptotal>=Pnoise : (0.7 < L <= 0.75)M5000C261 FRACT_LOAD_DISTR_CLASS_16 - Ptotal>=Pnoise : (0.75 < L <= 0.8)M5000C262 FRACT_LOAD_DISTR_CLASS_17 - Ptotal>=Pnoise : (0.8 < L <= 0.85)M5000C263 FRACT_LOAD_DISTR_CLASS_18 - Ptotal>=Pnoise : (0.85 < L <= 0.9)M5000C264 FRACT_LOAD_DISTR_CLASS_19 - Ptotal>=Pnoise : (0.9 < L <= 0.95)M5000C265 FRACT_LOAD_DISTR_CLASS_20 - Ptotal>=Pnoise : (0.95 < L <= 1)

Page 76: 241819261 Performance Analysis WI RU10 V3 Ppt

76 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low HSUPA Throughput

Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47)

Check If low throughput due to high number of retransmission & failed retransmission (RNC_917a HSUPA MAC-es BLER)

Check KPI RNC_1165a/RNC_1166a for low HSUPA throughput due to Iub congestion (frame delay or frame loss)

Check AVG_NON_HSDPA_PWR (M1000C138) & AVG_ACTIVE_NON_HSDPA_PWR to investigate whether high DCH power (DCH traffic) causes low HSUPA throughput Others reasons with low HSUPA throughput

Check problem at core network or application server Check HSPA FMCS / SCC mobility related parameters & performance

Note: HSUPA throughput measurement is less accurate than HSDPA throughput due to counters updating across total measurement period

Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000

STEP-15

Page 77: 241819261 Performance Analysis WI RU10 V3 Ppt

77 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low ISHO success rate

See Separate ISHO optimization WI for RU10/BSS13! https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/405632934

STEP-16

Page 78: 241819261 Performance Analysis WI RU10 V3 Ppt

78 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low in AMR/Rel99 IFHO success rate?

1. Analysis should be performed for each service (i.e. AMR, Rel99 NRT)

2. Breakdown IFHO analysis into three phases: Compressed mode performance (not in RAS06 Reporting suite – check KPI from M1008)

Inter-Freq measurement success ((not in RAS06 Reporting suite – check KPI from M1008)

Inter-Freq handover success (RNC_168a from system program)

3. If high IFHO compressed mode start not possible Check busy hour data of PrxTotal , PtxTotal and M1000C22

AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 for AC rejection

STEP-17

System Program – RSRAN000Mobility & Handover – RSRAN044

100* sum(SUCC_HHO_CAUSED_SHO_INCAP_RT + SUCC_HHO_SHO_INCAP_NRT + SUCC_INTRA_INTRA_HHO_ATT_RT + SUCC_INTRA_INTER_HHO_ATT_RT + SUCC_INTER_HHO_ATT_RT + SUCC_INTRA_INTRA_HHO_ATT_NRT + SUCC_INTRA_INTER_HHO_ATT_NRT + SUCC_INTER_HHO_ATT_NRT) / sum(HHO_ATT_CAUSED_SHO_INCAP_RT + IMMED_HHO_CSD_SHO_INCAP_RT + HHO_ATT_CAUSED_SHO_INCAP_NRT + IMMED_HHO_CSD_SHO_INCAP_NRT + INTRA_INTRA_HHO_ATT_RT + INTRA_INTER_HHO_ATT_RT + INTER_HHO_ATT_RT + INTRA_INTRA_HHO_ATT_NRT + INTRA_INTER_HHO_ATT_NRT + INTER_HHO_ATT_NRT)

Page 79: 241819261 Performance Analysis WI RU10 V3 Ppt

79 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Low AMR/Rel99 IFHO success rate4. If Low IFHO Measurement Success Rate (PI from M1008)

Check ADJI neighbour list for missing neighbours (too little ADJI defined) or bad existing ADJI performance (RNC_904a/RNC_901a)

• Too strict AdjiMinEcno margin and AdjiPathloss margin in RSCP trigger IFHO• Too late started IFHO (triggering threshold)• CM Measurement Period too short (recommended 12MRs) Check EcNo Distribution (M1007C38-M1007C47) or progation delay counters (M1006) to

indicate low coverage / interference problem

5. If Low IFHO Success Rate (RNC_168a < 95%)• Mobility issues either serving cell does not able to receive uplink RRC: Physical channel

reconfiguration complete message (timer expired) or UE response with physical channel reconfiguration failure to source RNC

• This is not related to target cell resource as IFHO Att is triggering after target cell resource has been made

• Mobility issues where source cell signal quality expected to be degraded rapidly (at least 3s gap from CM) due to UE moving away from F4 source cell after IFHO attempt to target cell (F3) is failed and UEs revert to old configuration

6. May require further troubleshooting with ICSU logging to determine root cause of failure

STEP-17 System Program – RSRAN000Mobility & Handover – RSRAN044

Page 80: 241819261 Performance Analysis WI RU10 V3 Ppt

81 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Next step proposal

1. Comparing results and discover potential improvement area

2. Propose short term or long term solution on under performing KPIs

STEP-19

Page 81: 241819261 Performance Analysis WI RU10 V3 Ppt

82 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Generate Executive Summary Report

1. Describe Executive Summary, Introduction and workscope2. Describe network topology in customer network3. Describe software version of each network element4. Describe KPI targets5. Describe KPI collection methodologies6. Present Network Performance Summary (statistics in table and graphical

presentation per each KPI targets)7. Describe Call setup performance analysis ( RRC / RAB performance )8. Describe Resource (Utilization) Performance in terms of RRC/RAB blocking9. Describe Power and UL noise analysis10. CS Voice, UDI, PS, SHO, HSPA performance analysis11. GAP Analysis and improvement solution proposal12. Conclusions

STEP-20

KPI Monitoring Report Template

Page 82: 241819261 Performance Analysis WI RU10 V3 Ppt

83 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 83: 241819261 Performance Analysis WI RU10 V3 Ppt

84 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

References

[1] 3G Data Performance Optimization guide[2] 3G KPI Work Shop[3] 3G RANOP training material

Page 84: 241819261 Performance Analysis WI RU10 V3 Ppt

85 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 85: 241819261 Performance Analysis WI RU10 V3 Ppt

86 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Acronyms/Glossary

Page 86: 241819261 Performance Analysis WI RU10 V3 Ppt

87 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Contents

1. Purpose and Scope2. Service Delivery Step-by-Step check list

2.2 Service Delivery steps3. References4. Acronyms/Glossary5. Annex

Page 87: 241819261 Performance Analysis WI RU10 V3 Ppt

88 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection

Activate the measurements4.1 Standard measurements (M1000, M1001 and so on..)4.2 Optional measurements (M500, M530, M550, M800, M6XX,

M802…)

Define tools to be used for performance counters and KPI collection

4.3 RAS06/RU10 Reporting Suite KPI Data Collection4.4 SQL Scripts KPI data collection

Use only when Reporting Suite is not available In-formal NSN tool (no technical support is guaranteed)

STEP-4

Page 88: 241819261 Performance Analysis WI RU10 V3 Ppt

89 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Activate standard measurements (if required)

In the example, Traffic measurement were not active

STEP-4.1

3 Select the interval (1 hour)

4 Select active days (All)

5 Press Start

1 In the Aplication Launcher, open the “RNW Measurement Management”

2

Page 89: 241819261 Performance Analysis WI RU10 V3 Ppt

90 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Activate other measurements (M530, M550, M800)1. AAL2, ATM and DSP measurements are quite useful to activate from

RNC (can be optional measurements in some NWs, depending on the contract)

2. They are activated at VCI or RNC level, manually (530 example below)

1 In the Aplication Launcher, open the “NE Measurement Explorer”

STEP-4.2

Page 90: 241819261 Performance Analysis WI RU10 V3 Ppt

91 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Choose the type of measurement (for example: M550) 2

Click the Measurement Management tap

3

In Menu\Object List, choose Search Object List

4

Activate the AAL2 measurementsSTEP-4.2

Page 91: 241819261 Performance Analysis WI RU10 V3 Ppt

92 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

In case there is an existing object list, Stop the measurements

5

If there is no, then create it from Menu\Object Lists, and then edit it

Activate the AAL2 MeasurementsSTEP-4.2

Page 92: 241819261 Performance Analysis WI RU10 V3 Ppt

93 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Edit the list (right click button) 6

Activate the AAL2 MeasurementsSTEP-4.2

Page 93: 241819261 Performance Analysis WI RU10 V3 Ppt

94 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Enter the data (Interface/VPI/VCI) into the fields which are in yellow. Press "Add"

5

Activate the AAL2 MeasurementsSTEP-4.2

When all the interfaces have been introduced, press OK, and the window is closed

6

Page 94: 241819261 Performance Analysis WI RU10 V3 Ppt

95 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

The meas should be reactivated again by pressing “Start”

7

Activate the AAL2 MeasurementsSTEP-4.2

Page 95: 241819261 Performance Analysis WI RU10 V3 Ppt

96 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

How to get the IF/VPI/VCI for a given WBTS?

In the Application Launcher, open the “RNC RNW Object Browser”

1

In the Object Browser, scroll down until finding the COCO from the WBTS desired and double click on it (COCOid=WBTSid)

2

Notice thatCOCOid=WBTSid

STEP-4.2

Page 96: 241819261 Performance Analysis WI RU10 V3 Ppt

97 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Select the User Plane links3 Here you can find the IF/VPI/VCI4

How to get the IF/VPI/VCI for a given WBTS?STEP-4.2

Page 97: 241819261 Performance Analysis WI RU10 V3 Ppt

98 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

M550 AAL2 CAC measurements

M550C9 and M550C14 useful to see AAL2_CAC congestion (Iub)

STEP-4.2

Page 98: 241819261 Performance Analysis WI RU10 V3 Ppt

99 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Activate RU10: M609 DSP service statistics

1

2

3

4

Create new object list, Name it and select all

available objects

Page 99: 241819261 Performance Analysis WI RU10 V3 Ppt

100 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Activate RU10: M609 DSP service statistics

5

6Start time should be fixed to full hour so

that the counter results match to other tables, this is valid for other

measurements as wellWhen pressing the list name (5) those objects are

seen here

7

Page 100: 241819261 Performance Analysis WI RU10 V3 Ppt

101 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- SQL Scripts Data collection (RAS06)

Log in to OSS ServerTelnet: XXX.XXX.XXX.XXXUser: XXXPassword: XXXX

Go to directorty /m/home/xxx/xxx/xxx storing the script

‘ Type “ls” ‘ to list the script or ls *.lst ‘ to list specific file.

Run the script from the unix promptCommand: ./pns11script_new.sh From the prompt, select the date where to

collect the datae.g.Enter Relative Start Date(1 for yesterday) : 7Enter Relative End Date(1 for yesterday) : 1

Create the daily raw measurement data using pre-defined scripts

STEP-4-3

1

1-1

1-2

1-3

1-4

Method 2

RAS06 daily Scripts

Page 101: 241819261 Performance Analysis WI RU10 V3 Ppt

102 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- SQL Scripts Data collection

After finish the script, the measurement data will be created under the same directory

The extension file name is <.lst> as can be seen from the left picture.

FTP to the OSS at the same directory storing thescripts

FTP: FTP xxx.xxx.xx.xxUser: XXXPassword: xxxxxxxx

ftp> prompt ‘ to turn off the interactive mode

Then type mget *.lst ‘ to get all the file on the collected date

Transfer raw measurement data to the other PC2

2-1

2-2

2-3

STEP-4-3 Method 2

Page 102: 241819261 Performance Analysis WI RU10 V3 Ppt

103 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Implement measurement data collection- SQL Scripts Data collection

Covert the measurement data (*.lst) into (*.txt) format

To rename the file into txt format

3

3-1

STEP-4-3 Method 2

Page 103: 241819261 Performance Analysis WI RU10 V3 Ppt

104 of 17 © Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY – FileName.ppt

Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009utranNSN\CMO\SBU\CSI\NSO

Click the “Import Raw Data” to import all the <*.txt> files into the database.

The data will be imported into the following pre-defined template table

Define your key KPI or using pre-defined KPI from Queries for analysis(fine-tune KPI formula basedon customer specific requirement)

Implement measurement data collection- SQL Scripts Data collection

Import the data into the MS-Access Database

STEP-4-3

4

5-1

5-2

Method 2

5-3 RAS06 KPI Access database

Page 104: 241819261 Performance Analysis WI RU10 V3 Ppt

105 of 17 © Nokia-Siemens Siemens Networks Internal ConfidentialWORK INSTRUCTIONStatus: Version 2.02009UtranNSN\CMO\SBU\CSI\NSO

End of Work Instruction