RAN Reporting Suite RU10 (OSS5)

23
8/3/2019 RAN Reporting Suite RU10 (OSS5) http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 1/23 1 © Nokia Siemens Networks RU10 / May 2009 Nokia Siemens Networks confidential RAN Reporting Suite RU10 NOTE: This slide-set is in working stage: - Chapters 1-4 are closed; - Chapter 5 is in draft mode, to be updated when the full report set is implemented in RS.

Transcript of RAN Reporting Suite RU10 (OSS5)

Page 1: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 1/23

1 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

RAN Reporting SuiteRU10

NOTE: This slide-set is in working stage:

- Chapters 1-4 are closed;

- Chapter 5 is in draft mode, to be updated when the full report set

is implemented in RS.

Page 2: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 2/23

2 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

Agenda

1. RAN Reporting Suite Component2. Pre-defined Reports Overview

3. Use-case Examples

4. New Counters and Measurements for RU10

5. Pre-defined Reports Presentation

Page 3: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 3/23

3 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

1. RAN Reporting Suite Component

The RAN Reporting Suite Component is designed to provide informationfor Service & Network Planning, Service Creation, Service & NetworkMonitoring and Business Management

Predefined reports are available off-the-shelf and are grouped in variousRAN reporting categories

RAN Reporting Suite Component Rel. 5.1.1 extends the earlier releasewith new reports covering RAS06: RN3.0, WBTS4.0;AXC C3.0

RAN Reporting Suite Component Rel. 5.2.1 extends the earlier releasewith new content covering RU10: RN4.0, WBTS5.0; NB7.0; AXC C5.5

It is running on top of NetAct OSS5.1, on regional & global cluster.

Page 4: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 4/23

4 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

Agenda

1. RAN Reporting Suite Component2. Pre-defined Reports Overview

3. Use-case Examples

4. New Counters and Measurements for RU10

5. Pre-defined Reports Presentation

Page 5: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 5/23

5 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

2. Pre-defined Reports Overview (1)RU10 Basic Report Set

New RU10

Modified RU10

1. System Program

System Program RNC Level RSRAN000

System Program Cell Level RSRAN0842. Capacity

RNC Capacity RSRAN068

RNC capacity usage RSRAN085

Node B Capacity RSRAN066

Cell Capacity RSRAN067

Iub Capacity RSRAN087

Cell Power RSRAN086

NRT DCH Allocations Statistics RSRAN097

NRT Radio Bearer Statistics RSRAN013

3. Service Level

Service/Session Accessibility Analysis RSRAN073

Service/Session Accessability Detailed Analysis RSRAN105

Service/Session Retainability Analysis RSRAN079

Service/Session Retainability Detailed Analysis RSRAN106

RAB Holding Times RSRAN021

Service Summary RSRAN003

4. Traffic

 Allocated Traf fic Amounts (R99 + HSPA) RSRAN070

Cell Data Volume and Throughput at RNC RSRAN077Traffic Summary RSRAN026

Used CE Capacity per RB Type in RNC RSRAN022

Utilization Shares of Total Traffic Allocation Amou RSRAN071

Packet Call RSRAN101

Traffic Model NW Dimensioning RSRAN088

Iur Traffic - L3 RSRAN100

Iub Traffic - Frame Protocol layer RSRAN096

Page 6: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 6/23

6 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

2. Pre-defined Reports Overview (2)RU10 Full Report Set

New RU10

Modified RU10

5. Mobility and Handover 

 Active Set Size for NRT, RT Traffic RSRAN078

HSPA Serving Cell Change RSRAN033

HSPA Inter-Freq HHO RSRAN089IFHO Adjacencies RSRAN044

InterSystem Handover per Cause RSRAN019

InterSystem Handover Performance RSRAN023

InterSystem Handover Reasons RSRAN018

ISHO Adjacencies RSRAN045

Load Based HO Related Resources RSRAN047

Load Based IFHO/ISHO Performance RSRAN048

Load Based IFHO/ISHO Triggering RSRAN049

Service Based IFHO/ISHO Performance RSRAN050

SHO Adjacencies RSRAN046

Soft Handover Performance RSRAN028

6. Signalling

NBAP Signalling RSRAN027

RRC Signalling RSRAN038

PRACH Propagation Delay RSRAN104

7. HSPA

HSPA Overview RSRAN092

HSPA Scheduling RSRAN091

CQI Distribution RSRAN039HSPA Code and Modulation Usage RSRAN034

HSPA Power Distribution RSRAN074

Channel Switching and HSPA Layering RSRAN075

UE Power Headroom RSRAN090

MAC-hs Efficiency RSRAN040

MAC-hs Retransmissions by Code and Modulation RSRAN041

Number of HSPA Users and UE capability RSRAN051

Page 7: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 7/23

7 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

2. Pre-defined Reports Overview (3)RU10 Full Report Set

New RU10

Modified RU10

8. Transport

 ATM Interface Traffic Load RSRAN081IP Interface Throughput RSRAN099

 ATM VCC Traffic Load RSRAN083

 ATM VPC Traffic Load RSRAN082

FTM Packet Transport Performance RSRAN076

FTM Performance RSRAN072

Iu-PS Throughputs RSRAN064

Iu-CS RSRAN094

M3UA RSRAN093

 ATM Iub Throughput RSRAN080

IP Iub Throughput (BTS pov) RSRAN095

Traffic on AAL5 RSRAN031

Traffic on ATM Layer RSRAN029

Traffic on Physical Medium SubLayer RSRAN030

IP Transport Resource Reservations RSRAN098

 ATM Transport Resource Reservations RSRAN069

9. Hardware

DSP Resource Usage RSRAN102

DSP State Changes RSRAN103

Page 8: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 8/23

8 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

Agenda

1. RAN Reporting Suite Component2. Pre-defined Reports Overview

3. Use-case Examples

4. New Counters and Measurements for RU10

5. The most relevant KPIs for RU106. Pre-defined Reports Presentation

Page 9: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 9/23

9 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

3. Use-Case ExamplesUCs for monitoring

1. Use-case for monitoringservices/sessions

The following services must bemonitored:

 ± Radio Resource Control (RRC)

 ± Radio Access Bearer (RAB)

 ±  AMR (= RAB CS ConversationalQoS parameter SourceDescriptor = Voice) session

 ± Video (= RAB CS ConversationalQoS 64 kbit/s and SourceDescriptor = Unknown) session

 ± CS Streaming Video (= CS RABStreaming QoS) session

 ± Packet (= PS RAB Streaming,Interactive or Background)session

2. Use-case for monitoringresource availability

The resources to be monitored are:

Logical resource availability

 ± Transport channels (CCH, DCH,HS-DSCH, E-DCH)

 ± Code tree blocking

Transport resource availability andblocking

 ± logical Inverse Multiplexing for  ATM (IMA) group interface

 ±Synchronous Digital Hierarchy(SDH) transmission path

 ± user plane ATM VCC (AAL2 path)

 ± IP transport resource availabity

HW availability and blocking

 ± BTS Channel Element (CE)

Page 10: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 10/23

10 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

3. Use-Case ExamplesUCs for monitoring

3. Use-case for throughput andload monitoring

The resources to be monitored are:

Radio Load (PrxTotal; PtxTotal)

 ± Cell

Radio data volume

 ± Cell, Radio bearer 

Transport throughput and load

 ± plane AAL2 type ATM VCC

RAN interface throughput and load

 ± GTP tunnel

 ± FP connection

4. Use cases for mobility

The resources to be monitored are:

Soft handover 

 ± Cell

Inter-System Handover  ± Cell

Page 11: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 11/23

11 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

Agenda

1. RAN Reporting Suite Component2. Pre-defined Reports Overview

3. Use-case Examples

4. New Counters and Measurements for RU10

5. Pre-defined Reports Presentation

Page 12: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 12/23

12 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10Id Measurement

M1000 Cell Resource

M1001 Service Level

M1002 Traffic

M1003 L3 signalling at Iu

M1004 L3 signalling at Iur 

M1005 L3 signalling at Iub

M1006 RRC signalling

M1007 Soft Handover 

M1008 Intra System Hard Handover 

M1009 L3 Relocation signalling

M1010 Inter System Hard Handover 

M1011 Location Services

M1012 Service Area Broadcast

M1013 Autodef Soft Handover M1014 AutoDef Inter Frequency HHO

M1015 AutoDef Inter System Handover 

M1016 RCPM OLPC

M1017 RCPM RLC

M1018 RCPM UEQ

M1020 A-GPS Server Interface

M1021 Iu-PC Interface

M1022 Packet Call

M1023 Cell Throughput

M1024 RCPM OLPC WCEL

M1025 RCPM OLPC RNC

M1026 RCPM RLC WCEL

M1027 RCPM RLC RNC

M1028 Autodef SHO DSR

M800 AAL2 Resource Reservation

M801 Iu-PS

M802 RNC Capacity Usage

M803 RNC RTP/RTCP

M804 RNC IP CAC

RNC Measurement

Id Measurement

92001 NodeB Resource

92002 NodeB Cell

92003 NodeB HSDPA

92004 NodeB HSUPA

92005 NodeB E1 Transmission Line

92006 NodeB J1 Transmission Line

92007 NodeB STM Transmission Line

92008 NodeB IMA Transmission Line

92009 NodeB E1 Virtual Path

92010 NodeB J1 Virtual Path

92011 NodeB STM Virtual Path

92012 NodeB IMA Virtual Path92013 NodeB E1 Virtual Channel

92014 NodeB J1 Virtual Channel

92015 NodeB STM Virtual Channel

92016 NodeB IMA Virtual Channel

SNodeB Measurement

Id Measurement

M5000 HSPA in WBTS

M5001 WBTS HW Resource

M5002 Cell Throughput in WBTS

M5003 Frame Protocol in WBTS

M5101 FTM PDH Interface

M5102 FTM SDH Interface

M5105 FTM ATM Interface

M5106 FTM ATM VC Connection

M5107 FTM ATM VP Connection

M5110 FTM Ethernet link

M5113 FTM Pseudowire MPLS

M5114 FTM PSN tunnel IPM5115 AAL2 Scheduling Performance in BTS

M5116 FTM Timing over Packet

M5117 FTM IP statistics

M5118 FTM PHB statistics

WBTS/FTM Measurement

New RU10 measurement

New RU10 counters

Measurement no longer in use

Page 13: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 13/23

13 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

Id Measurement

M145 PDH Statistics

M208 MTP Signalling link availability

M209 MTP signalling link performance

M210 MTP signalling link utilization

M211 MTP signalling point status

M212 MTP Signalling link set and route set availability

M213 MTP Signalling traffic report of signalling points

M214 MTP Signalling traffic report of user parts

M215 MTP matrix signalling traffic

M216 SCCP signalling point

M217 SCCP subsystem

M218 SCCP local subsystem availability

M219 SCCP single meters

M513 STM-1 interface

M514 IMA logical interface measurements

M516 SONET/SDH Protection Group measurement

M528 ATM layer performance

M529 ATM Virtual Path Connection

M530 ATM Virtual Channel Connection

M531 ATM Route Load

M532 ATM Interface

M546 SAAL signalling protocol at UNI

Platform Measurement

Id Measurement

M547 AAL5 protocol measurement in DMX

M548 AAL2 signalling protocol at UNI

M549 AAL5 protocol measurement in Chorus

M550 AAL2 Path CAC Resource

M552 AAL2 Signalling at NNI

M553  AAL2 Scheduling Performance in RNC

M563 TCP/IP Protocol

M564 Ethernet interface performance

M565 IP measurement on IP interface

M566 UDP measurement on IP interface

M567 IP QOS measurement

M568 IP Based Route

M592 Unit Load measurement

M594 Overload control with WAC Performance

M608  Availability performance measurement

M609 DSP service statistics

M612 DSP state changes

M613 DSP performance measurement

M615 DSP Resource Utilisation

M617 DSP Load

M661 M3UA Association Set

Platform Measurement

5.New Counters and Measurements for RU10

New RU10 measurement

New RU10 counters

Measurement no longer in use

Page 14: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 14/23

14 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

4.New Counters and Measurements for RU10RU10 features that impact the data model

Microsoft Excel

Worksheet 

Page 15: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 15/23

15 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

RAN1004: Streaming QoS for HSPA:This feature brings the support of Streaming QoS traffic class Radio Access Bearers(RABs) on HSPA.

Streaming services with guaranteed bit rate requirements improve servicedifferentiation and thus provide the possibility for increased revenue.

Counter examples: ± Channel Release counters

5.New Counters and Measurements for RU10

M1002C578 HS-DSCH NORMAL RELEASE FOR STREAMING

M1002C579 HS-DSCH RELEASE DUE TO OTHER FAILURE FOR STREAMING

M1002C580 HS-DSCH RELEASE DUE TO MOBILITY DCH TRANSITION FOR STREAMING

M1002C609 E-DCH NORMAL RELEASE FOR STREAMING

M1002C610 E-DCH RELEASE DUE HS-DSCH SERVING CELL CHANGE FOR STREAMING

M1002C611 E-DCH RELEASE DUE TO RL FAILURE FOR STREAMING

M1002C612 E-DCH RELEASE DUE TO OTHER FAILURE FOR STREAMING

Page 16: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 16/23

16 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

RAN1004: Streaming QoS for HSPA:

Counter examples: ± Streaming Packet Call Setup Failures counters

 ± Multi RAB counters

5.New Counters and Measurements for RU10

M1022C184 PACKET CALL SETUP FAIL DUE TO AC FOR STREAMING

M1022C185 PACKET CALL SETUP FAIL DUE TO BTS FOR STREAMING

M1022C186 PACKET CALL SETUP FAIL DUE TO DMCU RES FOR STREAMING

M1022C187 PACKET CALL SETUP FAIL DUE TO TRANSM FOR STREAMING

M1022C188 PACKET CALL SETUP FAIL DUE TO UE FOR STREAMING

M1022C189 PACKET CALL SETUP FAIL DUE TO OTHER REASONS FOR STREAMING

M1002C596 AMR + HS-DSCH SETUP FAILURE FOR STREAMING

M1002C597 AMR + HS-DSCH ALLOCATIONS FOR STREAMING

M1002C598 AMR + HS-DSCH NORMAL RELEASE FOR STREAMING

M1002C619 AMR + RT-HSPA + NRT-HSPA ALLOCATION

M1002C620 AMR + RT-HSPA + MULTI-NRT-HSPA ALLOCATION

M1002C621 RT-HSPA + NRT-HSPA ALLOCATION

M1002C622 RT-HSPA + MULTI-NRT-HSPA ALLOCATION

Page 17: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 17/23

17 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

RAN1262: QoS Aware HSPA Scheduling:This feature allows service and subscriber differentiation in HSPA for NRT trafficclasses.

This feature allows service and subscriber differentiation and supports differenttariffing plans for NRT traffic classes. For example, premium services andsubscribers will have a higher priority over low tariff broadband HSPA data traffic.

Counter examples: ± HSUPA Scheduled Priority Indication (SPI) counters:

5.New Counters and Measurements for RU10

M5002C22 TOTAL HSUPA DATA FOR SPI 0

M5002C23 TOTAL HSUPA DATA FOR SPI 1

M5002C24 TOTAL HSUPA DATA FOR SPI 2

M5002C25 TOTAL HSUPA DATA FOR SPI 3

M5002C26 TOTAL HSUPA DATA FOR SPI 4

M5002C27 TOTAL HSUPA DATA FOR SPI 5

M5002C28 TOTAL HSUPA DATA FOR SPI 6

M5002C29 TOTAL HSUPA DATA FOR SPI 7

M5002C30 TOTAL HSUPA DATA FOR SPI 8

M5002C31 TOTAL HSUPA DATA FOR SPI 9

M5002C32 TOTAL HSUPA DATA FOR SPI 10

M5002C33 TOTAL HSUPA DATA FOR SPI 11

M5002C34 TOTAL HSUPA DATA FOR SPI 12

M5002C35 TOTAL HSUPA DATA FOR SPI 13

M5002C36 TOTAL HSUPA DATA FOR SPI 14

M5002C37 TOTAL HSUPA DATA FOR SPI 15

Page 18: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 18/23

18 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10

RAN1262: QoS Aware HSPA Scheduling:

Counter examples:

 ± HSDPA Scheduled Priority Indication (SPI) counters:

M5002C5 TOTAL MAC-HS PDUS FOR SPI 0

M5002C6 TOTAL MAC-HS PDUS FOR SPI 1

M5002C7 TOTAL MAC-HS PDUS FOR SPI 2

M5002C8 TOTAL MAC-HS PDUS FOR SPI 3

M5002C9 TOTAL MAC-HS PDUS FOR SPI 4

M5002C10 TOTAL MAC-HS PDUS FOR SPI 5

M5002C11 TOTAL MAC-HS PDUS FOR SPI 6

M5002C12 TOTAL MAC-HS PDUS FOR SPI 7

M5002C13 TOTAL MAC-HS PDUS FOR SPI 8

M5002C14 TOTAL MAC-HS PDUS FOR SPI 9

M5002C15 TOTAL MAC-HS PDUS FOR SPI 10

M5002C16 TOTAL MAC-HS PDUS FOR SPI 11

M5002C17 TOTAL MAC-HS PDUS FOR SPI 12

M5002C18 TOTAL MAC-HS PDUS FOR SPI 13

M5002C19 TOTAL MAC-HS PDUS FOR SPI 14

M5002C20 TOTAL MAC-HS PDUS FOR SPI 15

Page 19: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 19/23

19 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10

RAN1198: RNC2600 SW License Key Controlled Capacity:

RNC capacity is controled with SW licence keys. BSW price is based on thelicensed capacity.

Main RNC capacity parameters can be optimized based on customer needs.Capacity upgrades can be performed by licence key delivery only, in which casethere is no need for additional HW. BSW price is derived directly from customer needs.

Counter examples:

 ± Licensed Capacity Monitoring:

M802C0 AMR_AVERAGE

M802C1 AMR_MAX

M802C2 AMR_DISTR_CLASS_0

M802C3 AMR_DISTR_CLASS_1

M802C4 AMR_DISTR_CLASS_2

M802C5 AMR_DISTR_CLASS_3

M802C6 AMR_DISTR_CLASS_4

M802C7 AMR_LIC_CAPACITY

M802C8 IU_PS_THR_AVERAGE

M802C9 IU_PS_THR_PEAK

M802C10 IUB_PS_THR_DISTR_CLASS_0

M802C11 IUB_PS_THR_DISTR_CLASS_1

M802C12 IUB_PS_THR_DISTR_CLASS_2

M802C13 IUB_PS_THR_DISTR_CLASS_3

M802C14 IUB_PS_THR_DISTR_CLASS_4

M802C15 IUB_PS_THR_LIC_CAPACITY

M802C16 IU_PS_THR_LIMIT_DURATION

M802C17 AVE_RRC_CONN_MODE_USERS

M802C18 MAX_RRC_CONN_MODE_USERS

M802C19 AVE_USERS_CELL_DCH

M802C20 AVE_USERS_CELL_FACH

M802C21 AVE_USERS_CELL_PCH

M802C22 AVE_USERS_URA_PCH

Page 20: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 20/23

20 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10

RAN1126: Counters for RAB and DCH Setups and Failure Cases:This feature introduces new counters for more detailed monitoring of RAB,DCH/HS-DSCH and counters for SHO branch setup failure cases.

OPEX savings are achieved through simplified network monitoring andoptimization due to the new statistics. Optimized network expansions meansavings in CAPEX.

Counter examples: ± DCH Requests:

M1022C83 INITIAL DCH REQUESTS FOR BITRATE 64 KBPS AND LOWER UL

M1022C84 INITIAL DCH REQUESTS FOR BITRATE 64 KBPS AND LOWER DL

M1022C85 INITIAL DCH REQUESTS FOR BITRATE 128 KBPS UL

M1022C86 INITIAL DCH REQUESTS FOR BITRATE 128 KBPS DL

M1022C87 INITIAL DCH REQUESTS FOR BITRATE 256 KBPS UL

M1022C88 INITIAL DCH REQUESTS FOR BITRATE 256 KBPS DL

M1022C89 INITIAL DCH REQUESTS FOR BITRATE 384 KBPS UL

M1022C90 INITIAL DCH REQUESTS FOR BITRATE 384 KBPS DL

M1022C107

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 64

KBPS AND LOWER UL

M1022C108

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 64

KBPS AND LOWER DL

M1022C109

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 128

KBPS UL

M1022C110

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 128

KBPS DL

M1022C111

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 256

KBPS UL

M1022C112

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 256

KBPS DL

M1022C113

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 384

KBPS UL

M1022C114

INITIAL DCH ALLOCATION SUCCESS WITH REQUESTED BITRATE 384

KBPS DL

Page 21: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 21/23

21 © Nokia Siemens Networks RU10 / May 2009

Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10

RAN1126: Counters for RAB and DCH Setups and Failure Cases:

Counter examples: ± DCH Reconfigurations Failures:

M1022C131DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FORINTERACTIVE

M1022C132

DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR

BACKGROUND

M1022C133

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR

INTERACTIVE

M1022C134

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR

BACKGROUND

M1022C135 DCH UPLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C136 DCH UPLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

M1022C137 DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C138 DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

M1022C139 DCH UPLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE

M1022C140 DCH UPLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND

M1022C141

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR

INTERACTIVE

M1022C142

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR

BACKGROUND

M1022C143

DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR

INTERACTIVE

M1022C144

DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR

BACKGROUND

M1022C145

DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS

FOR INTERACTIVE

M1022C146

DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS

FOR BACKGROUND

Page 22: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 22/23

22 © Nokia Siemens Networks RU10 / May 2009Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10

Transport in RU10:RAN1253: Iub Transport QoS

RAN1634: IP based Iub for UltraSite WCDMA BTS

RAN75: IP Based Iu-CS

RAN750: IP Based Iu-PS

RAN76: IP Based Iur 

Page 23: RAN Reporting Suite RU10 (OSS5)

8/3/2019 RAN Reporting Suite RU10 (OSS5)

http://slidepdf.com/reader/full/ran-reporting-suite-ru10-oss5 23/23

23 © Nokia Siemens Networks RU10 / May 2009Nokia Siemens Networks confidential

5.New Counters and Measurements for RU10 RAN1253: Iub Transport QoS

RAN1634: IP based Iub for UltraSite WCDMA BTS ± These two features introduce the 3GPP-compliant IP transport option for the Iub interface in RNC

(both features), in Flexi WCDMA BTS and in UltraSite WCDMA BTS, respectively. To use thesefeatures, RNC and BTS have to be equipped with transport units providing Ethernet interfaces.

RAN75: IP Based Iu-CS

RAN750: IP Based Iu-PS

RAN76: IP Based Iur  ± These three features enable the 3GPP-compliant IP transport option for the respective logical

interface on the RNC.

M553C10 Q1_QUE_USAGE_PEAK

M553C11 Q1_QUE_PACKETS_SUM

M553C12 Q1_QUE_SAMPLES

M553C13 Q1_QUE_DELAY_PEAK

M553C14 Q1_QUE_DELAY_SUM

M553C15 Q1_QUE_DELAY_SAMPLES

M553C16 Q1_QUE_DRP_EVENTS

RAN1253 Counter examples: ATM Scheduling Queue

Performance Monitoring (4

different QoS queues)

RAN1634, RAN75, RAN750,

RAN76 and Counter examples:

IP performance monitoring

M568C0 OUT_DATA_IP_ROUTE

M568C1 IN_DATA_IP_ROUTE

M568C2 COMMITTED_BIT_RATE_IP_ROUTE

M568C3 SUM_RESERVED_RATE_IP_ROUTE

M568C4 MIN_RESERVED_RATE_IP_ROUTE

M568C5 MAX_RESERVED_RATE_IP_ROUTE

M568C6 SUM_IP_UDP_CONN_IP_ROUTE

M568C7 MIN_IP_UDP_CONN_IP_ROUTE

M568C8 MAX_IP_UDP_CONN_IP_ROUTE

M568C9 NBR_SAMPLES_IP_ROUTE