Day 1 -Eutran Counters and MO Clases

Day 1 Course Contents

• LTE Performance Management Introduction• EPS Introduction• LTE RAN Evolution• LTE Performance Management Solution• Optimization Solution• EUTRAN Counters• EUTRAN MO Classes• EPS QoS• Radio KPIs Overview

Page2

Radio KPIs Overview

• The quality of network performance is mainly evaluated by KPI (Key Performance Index)– Drive Test KPI/ Stationary Test: Some KPIs should be attained by drive

test, such as such as coverage KPI and latency KPI, measurement results are coming from driver test tools

– Performance Measurement KPI: Most of KPIs are attained by this approach, such as RRC success Rate, HHO success rate,eg, these KPIs are coming from eNodeB performance statistic.

Page2

HUAWEI TECHNOLOGIES Co., Ltd.

www.huawei.com

HUAWEI Confidential

Security Level: Internal

Huawei eRAN KPI Introduction(eRAN 7.1)

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 4

Agenda

KPI System Overview

KPI Detail Description

Recommended KPIs


KPI System Overview

LTE KPIs

Accessibility Retainability IntegrityMobility Latency

• RRC SETUP SR

• E-RAB Setup SR (VoIP/ALL)

• Call Setup SR (VoIP/ALL)

• Call Drop Rate (VoIP/ALL)

• Call Setup Complete Rate (VoIP/ALL)

• Service UL/DL Throughput

• HHO SR (Intra-/Inter- Frequency)

• HO in SR

• Inter-RAT HHO SR

• Access Latency

• Service Latency

• Interrupt Latency

• Radio Network Unavailability Rate

Availability

• Cell UL/DL Traffic Volume

• Radio Bearer Number

Utilization

Radio Network KPI:

Focus on the radio network performance

Service KPI:

Focus on the user

experience

• UL/DL RB Utility Rate

Traffic


KPI Attained Approach

In general, there are two approaches to define or attain KPIs:

• By statistics or counters:Most of KPIs are attained by this approach, such as RRC Success Rate, HHO Success Rate...

• By drive tests or stationary tests:Some KPIs should be attained by drive tests, such as Attach Latency, Handover latency...


Measurement Object for Counter

Measurement Object

Measurement

Unit 1

Measuremen

t Unit 2

...

Counter

1

Counter

2

Counter

3

Counter

4

Counter

5

Counter

6

Counter

7

Measuremen

t

Family 1

...Measuremen

t

Family 2

…… ……

Each measurement result is related to a specific measurement object.Counters are organized by Measurement Unit/Family.


Collection methods (TS 32.403)

CC (Cumulative Counter), for example, Attempted RRC Connection Establishments;GAUGE (dynamic variable), used when data being measured can vary up or down during

the period of measurement, for example, Maximum E-RAB Setup Time;DER (Discrete Event Registration), when data related to a particular event are captured

every nth event is registered, where n can be 1 or larger, for example, Cell Unavailable Time, Mean E-RAB Setup Time;

SI (Status Inspection), for example, Average Number of Simultaneous E-RABs;

Reporting period

The measurement results are collected in a pre-defined reporting period, and this reporting period, in general, is configurable at EMS, for example, 15 minutes, 60 minutes…

Collection Method and Reporting Period


Agenda

KPI System Overview

KPI Detail Description• Accessibility• Retainability• Mobility• Availability• Utilization• Traffic• Integrity• Latency

Recommended KPIs


Accessibility (1) – RRC Setup Success Rate

RRC Setup Success Rate (Service)

The RRC setup procedure is triggered by different reasons as identified by the establishmentCause field in the RRCConnctionRequest message: emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, and delayTolerantAccess-v1020. The UE sets the establishmentCause received by eNodeB. Causes except mo-Signalling are categorized as service related ones, and the cause of mo-Signalling is categorized as signal related ones. This KPI evaluates the RRC setup success rate with service related causes in a cell or cluster.

%100_

__ Service

service

service

AttemptConnectionRRC

SuccessConnectionRRCSSRRRC

RRC Setup Success Rate (Signaling)

This KPI evaluates the RRC setup success rate with signal related causes (mo-Signalling) in a cell or cluster.

%100_

__ Signal

Signal

Signal

AttemptConnectionRRC

SuccessConnectionRRCSSRRRC


Accessibility (2) – Counter Mapping for RRC SSR

L.RRC.ConnReq.Att…

L.RRC.ConnReq.Succ …


Accessibility (3) – QCI Definition

LTE-SAE QoS Class Identifier

There are 9 QCIs defined in 3GPP TS 23.203. Each of QCI has its QoS requirements, and each E-RAB has the attribute of QCI.


Accessibility (4) – ERAB Setup Success Rate

ERAB Setup Success Rate (VoIP)

This KPI can be used to evaluate the E-RAB setup success rate for VoIP services (QCI 1 services) in a cell or cluster.

_ __ _ 100%

_ _

VoIP ERAB SetupSuccessVoIP ERAB SSR

VoIP ERAB SetupAttempt

ERAB Setup Success Rate (All)

This KPI can be used to evaluate the E-RAB setup success rate for all services including the VoIP service in a cell or a cluster.

__ ( ) 100%

_

ERAB SetupSuccessERAB SSR ALL

ERAB SetupAttempt


Accessibility (5) – Counter Mapping for ERAB SSR

ERAB Setup Attempt Counters

ERAB Setup Success Counters

ERAB Setup Attempt Counters

ERAB Setup Success Counters


Accessibility (6) – Call Setup Success Rate

Call Setup Success Rate (VoIP)

This KPI evaluates the success rate of the whole setup procedure for VoIP services (QCI 1 service) in a cell or cluster, which mainly includes three phases: RRC setup phase, S1 Signaling connection establishment phase, and VoIP E-RAB setup phase:

_ 1 _ __ * * 100%

_ 1 _ _Service

Service

RRC ConnectionSuccess S SIGConnectionEstablishSuccess VoIP ERAB SetupSuccessVoIP CSSR

RRC ConnectionAttempt S SIGConnectionEstablishAttempt VoIP ERAB SetupAttempt

Call Setup Success Rate (All)

This KPI can be used to evaluate the call setup success rate for all services including the VoIP service in a cell or a cluster. This KPI mainly includes three phases: RRC setup phase, S1 Signaling connection establishment phase and service E-RAB setup phase:

_ 1 _( ) * * 100%

_ 1 _Service

Service

RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccessCSSR ALL

RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt


Accessibility (7) – Counter Mapping for CSSR


Retainability (1) – Call Drop RateCall Drop Rate (VoIP)

This KPI can be used to evaluate the call drop rate of VoIP services (QCI 1 services) in a cell or cluster. The call drops happen when eNodeB actively initiates an E-RAB (with data in buffer) release process by E-RAB Release Indication or UE Context Release Request message with abnormal causes (the cause other than: Normal Release, Detach, User Inactivity, cs fallback triggered, UE Not Available For PS Service, Successful Handover or Inter-RAT redirection), and all of the other E-RAB releases are considered as normal E-RAB release.

Call Drop Rate (All)

This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster, including VoIP service.

%100Re__

Re___

leaseERABVoIP

leaseAbnormalERABVoIPCDRVoIP

_ Re( ) 100%

_ Re

ERAB Abnormal leaseCDR ALL

ERAB lease

Call Drop Rate (Always Online)

This KPI can be used to evaluate the call drop rate of all the services, including the VoIP service, when the always online state is active. In always online state, the E-RAB number of a UE entering the asynchronous state from synchronous state will be considered for the KPI calculating.

_ 100%Re

ERABAbnormalReleaseOfAlwaysOnlineAlwaysOnline CDR

ERAB leaseOfAlwaysOnline


Retainability (2) – Counter Mapping for Call Drop Rate

Normal and Abnormal release Counters based on the cause

Normal and Abnormal release Counters based on the cause


Retainability (3) – Call Setup Complete Rate

_ 1 _ _ Re( ) * * * 100%

_ 1 _ _ ReService

Service

RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccess ERAB Normal leaseCSTR ALL

RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt ERAB lease

Call Setup Complete Rate (VoIP)

This KPI evaluates the call setup complete rate for VoIP services (QCI 1 services) in a cell or cluster, which means the rate of the VoIP service can be normally terminated once the UE attempt to set up the service. And it can include 4 phases: RRC setup phase, S1 Signaling connection establishment phase, VoIP E-RAB setup phase and VoIP service E-RAB release phase;

Call Setup Complete Rate (All)

Similar as the preceding KPI, this KPI will evaluate the success rate in totally for 4 phases: RRC setup phase, S1 Signaling connection establishment phase, service E-RAB setup phase and service E-RAB release phase;

_ 1 _ _ _ _ Re_ * * *

_ 1 _ _Service

Service

RRC ConnectionSuccess S SIGConnectionEstablishSuccess VoIP ERAB SetupSuccess VoIP ERAB Normal leaseVoIP CSTR

RRC ConnectionAttempt S SIGConnectionEstablishAttempt VoIP ERAB SetupAttempt Vo 100%

_ _ ReIP ERAB lease

Call Setup Complete Rate (Always Online)

Similar as the preceding KPI, this KPI will evaluate the success rate in totally for 4 phases: RRC setup phase, S1 Signaling connection establishment phase, service E-RAB setup phase and service E-RAB release phase (when the always online state is active);

_ 1 _( ) * * *

_ 1 _Service

Service

RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccess ERABAbnormalReleaseOfAlwayCSTR AlwaysOnline

RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt 100%

Re

sOnline

ERAB leaseOfAlwaysOnline


Retainability (4) – Counter Mapping for CSCR


Mobility (1) – Intra-LTE Handover (Out) Success Rate

Intra-Frequency Handover Out Success Rate

This KPI can be used to evaluate the intra-frequency outgoing handover success rate in a cell or cluster.

%100_

___

ptHOOutAttemIntraF

ssHOOutSucceIntraFSRHOOutIntraF

Inter-Frequency Handover Out Success Rate This KPI can be used to evaluate the inter-frequency outgoing handover success rate in a cell or cluster.

%100_

___

ptHOOutAttemInterF

ssHOOutSucceInterFSRHOOutInterF


Mobility (2) – Counter Mapping for Intra-LTE HO SR

Handover Attempt Counters

Handover Success Counters


Mobility (3) – Intra-LTE Handover In Success Rate

Handover In Success Rate

This KPI can be used to evaluate the incoming handover success rate in a cell or cluster.

%100_ tHOInAttemp

sHOInSuccesSRHOIn


Mobility (4) – Counter Mapping for Intra-LTE HO In SR

HO in Attempt Counters

HO in Success Counters


Mobility (5) – Inter-RAT Handover Success Rate

Inter-RAT Handover Success Rate (LTE to WCDMA)

This KPI can be used to evaluate the inter-RAT handover success rate from LTE to WCDMA in a cluster.

%100_2_

_2__2_

AttemptOutWLIRATHO

SuccessOutWLIRATHOSRWLIRATHO out

Inter-RAT Handover Success Rate (LTE to GERAN)

This KPI can be used to evaluate the inter-RAT handover success rate from LTE to GERAN in a cluster.

%100_2_

_2__2_

AttemptOutGLIRATHO

SuccessOutGLIRATHOSRGLIRATHO out

Inter-RAT Handover Success Rate (LTE to TD-SCDMA)

This KPI can be used to evaluate the inter-RAT handover success rate from LTE to TD-SCDMA in a cluster.

_ 2 __ 2 _ 100%

_ 2 _out

IRATHO L T SuccessOutIRATHO L T SR

IRATHO L T AttemptOut


Mobility (6) – Inter-RAT Handover Success Rate

Inter-RAT Handover Success Rate (LTE to CDMA2000)

This KPI can be used to evaluate the inter-RAT handover success rate from LTE to CDMA2000 in a cluster.

_ 2 __ 2 _ 100%

_ 2 _out

IRATHO L C SuccessOutIRATHO L C SR

IRATHO L C AttemptOut


Mobility (7) – Counter Mapping for Inter-RAT HO SR

B point, HO attempt, and distinguish the target system by an element "targetRAT-Type" in the message

C point, HO Success


Availability (1) – Radio Network Unavailability Rate

Radio Network Unavailability Rate

This KPI provides the percentage of time that a cell is unavailable in order to evaluate the degradation of the network performance caused by the unavailable cells. It is calculated based on the time of all cell unavailability in the radio network (cluster).

Where the {SP} denotes the reports period of counters, and the unit is minutes.


Availability (2) – Counter Mapping for RAN Unavailability Rate


Utilization (1) – DL/UL RB Utility Rate

Uplink Resource Block Utility Rate

This KPI evaluates the uplink RB (Resource Block) utility rate of a cell or cluster.

%100_

__

AvailableULRB

UsedULRBeUtilityRatULRB

Downlink Resource Block Utility Rate

This KPI evaluates the downlink RB (Resource Block) utility rate of a cell or cluster.

%100_

__

AvailableDLRB

UsedDLRBeUtilityRatDLRB


Utilization (2) – Counter Mapping for RB Utility Rate


Utilization (3) – Average CPU Load

Average CPU Load

This KPI is used to evaluate the CPU usage in busy hours. It indicates the system load. The CPU load is calculated by averaging the CPU usage ratio in the measurement period.

MeanCPUUtility


Utilization (4) – Counter Mapping for Average CPU Load


Traffic (1) – Active Users

Active Users

This group of KPIs consist of 6 KPIs, which are used to evaluate the number of UEs in RRC_CONNECTED mode in a cell, the user numbers with uplink data in the buffer or with downlink data in the buffer, and also give the average user number and maximum user number in a cell or cluster.

DLAvgActiveUserNumber

DLMaxActiveUserNumber

AvgUserNumber

MaxUserNumber

ULAvgActiveUserNumberULMaxActiveUserNumber


Traffic (2) – Counter Mapping for Active Users






Traffic (5) – Radio Bearers

Radio Bearers

The radio bearers KPIs consist of ten sub-KPIs, one is for the total of radio bearers and the other nine are for nine QCIs. This set of KPIs can be used to evaluate the average radio bearers in a cell or a cluster. The radio bearer for each QCI is based on the number of active RRC connections for each QCI according to the QCI defined in the QoS information.

……

9__QCIrsRadioBeare

1__QCIrsRadioBeare

RadioBearers


Traffic (6) – Counter Mapping for Radio Bearers


Traffic (7) – Traffic Volume

Downlink Traffic Volume

Similar to the radio bearers KPIs, the downlink traffic volume KPIs consist of ten sub-KPIs, one is for the total of traffic volume for DRBs and the other nine are for nine QCIs. This group of KPIs can be used to evaluate the DL traffic volume in a cell, which is measured at the PDCP layer excluding the PDCP header

…… 9__QCIolumeDLTrafficV_ _1DLTrafficVolume QCI

Uplink Traffic Volume

Similar to the downlink traffic volume KPIs, the uplink traffic volume KPIs consist of ten sub-KPIs, one is for the total of traffic volume for DRBs and the other nine are for nine QCIs. This group of KPIs can be used to evaluate the uplink traffic volume in a cell. The KPIs are measured at the PDCP layer excluding the PDCP header.

1__QCIolumeULTrafficV 9__QCIolumeULTrafficV……

DLTrafficVolume

ULTrafficVolume


Traffic (8) – Counter Mapping for Traffic Volume


Traffic (9) – Counter Mapping for Traffic Volume


Service Integrity (1) – Service Average Throughput

Service Downlink Average Throughput

This set of KPIs consists of nine sub-KPIs mapped into nine QCIs (QCI 1~9). These KPIs evaluate the downlink throughput of a service with a specific QCI per user in each cell, reflecting the end-user experience.

Service Uplink Average Throughput

Same with the service downlink average throughput, this set of KPIs consists of nine sub-KPIs mapped into nine QCIs (QCI 1~9), and the meaning is also similar with it.

1__QCIhroughputULAverageT

……

9__QCIhroughputULAverageT

1__QCIhroughputDLAverageT

……

9__QCIhroughputDLAverageT

The total downlink traffic volume at PDCP layer of each QCI and total duration for transmitting them are measured within a measurement period. Then the average throughput of each QCI is obtained at the end of the measurement period.


Service Integrity (2) – Cell Average Throughput

Cell Downlink Average Throughput

This KPI evaluates a cell's average downlink throughput when data is transferring in the downlink. It reflects the cell capacity.

Cell Uplink Average Throughput

Same with the cell downlink average throughput, this set of KPI reflects the cell capacity, and the meaning is also similar with it.

The total downlink traffic volume at PDCP layer in a cell and total duration for transmitting which is measured within a measurement period. Then the average throughput of cell is obtained at the end of the measurement period.

CellDLTrafficVolumeCellDLAveThp

CellDLTransferTime

CellULTrafficVolumeCellULAveThp

CellULTransferTime


Service Integrity (3) – Cell Maximum Throughput

Cell Downlink Maximum Throughput

This KPI evaluates a cell's maximum downlink throughput when data is transferring in the downlink. It reflects the cell capacity. It is calculated based on maximum value of downlink traffic volume which are transferred at each second.

Cell Uplink Maximum Throughput

Same with the cell uplink maximum throughput. It is calculated based on maximum value of uplink traffic volume which are transferred at each second.

1 ( )

1000( )

CellULMaxTrafficVolumeforEach s bitCellULMaxThp

ms

1 ( )

1000( )

CellDLMaxTrafficVolumeforEach s bitCellDLMaxThp

ms


Service Integrity (4) – Counter Mapping for Service Average Throughput


Service Integrity (5) – Measurement Principle for Throughput

Refer to TS 32.450


Service Integrity (6) – Counter Mapping for Service Average Throughput


Service Integrity (7) – Counter Mapping for Cell Average Throughput


Service Integrity (8) – Counter Mapping for Cell Maximum Throughput


Latency (1)

Access Latency

This group of KPIs can be used to evaluate the latency of access phase.

AccessLatency_Attach

Defined as the duration from the time the UE sends an AttachRequest message to the time the UE sends an AttachComplete message.

AccessLatency_Idle2Active

Defined as the duration from the time the UE (in idle mode) sends an RRCConnectionRequest message to the time the UE sends an RRCConnectionReconfiguration message.


Latency (2)

Control Plane HO Interrupt LatencyThis group of KPIs can be used to evaluate the control plane interrupt latency during the handover. We can further distinguish them by different handover scenarios.

This group of KPIs is measured through drive tests. Defined as the duration from the time the UE receives the handover command (RRCConnectionReconfiguration after MeasurementReport) to the time the UE sends the handover confirm message (RRCConectionReconfigurationComplete).

HOIntraLTEInterruptneControlPla ___

CLIRATHOInterruptneControlPla 2___WLIRATHOInterruptneControlPla 2___GLIRATHOInterruptneControlPla 2___

Service Latency

This group of KPIs can be used to evaluate the latency of a particular service. We can distinguish them by different services. This KPI can be attained by drive tests (or stationary tests).

bytesPingencyServiceLat 32__bytesPingencyServiceLat 1460__


Latency (3)

User Plane HO Interrupt Latency

This group of KPIs can be used to evaluate the user plane interrupt latency during the handover. We can further distinguish them by different handover scenarios.

The user plane interrupt latency is different when observed at different layers, for example, at IP layer or RLC layer or MAC layer.

This group of KPIs is measured through drive tests. Defined as the duration from the last RLC layer package received before the handover, to the first RLC layer package received after handover. It can be observed in Probe.

HOIntraLTEInterruptUserPlane ___

CLIRATHOInterruptUserPlane 2___

GLIRATHOInterruptUserPlane 2___

WLIRATHOInterruptUserPlane 2___


Agenda

KPI System Overview

KPI Detail Description

Recommended KPIs


Recommended KPIs

The recommended KPIs at this phase include:

KPI Class KPI Name

Accessibility

RRC Setup Success Rate (Service)

RRC Setup Success Rate (Signaling)

ERAB Setup Success Rate (All)

Retainability Call Drop Rate (All)

Mobility Intra-Frequency Handover Out Success Rate

Traffic

Radio Bearers for Total and QCI 1~9

Downlink Traffic Volume for Total and QCI 1~9

Uplink Traffic Volume for Total and QCI 1~9

IntegrityService Downlink Average Throughput for QCI 1~9

Service Downlink Average Throughput for QCI 1~9


Performance Data Manager

Page 56

(iManager PRS V100R006 Product Description V1.1)

The PRS is a platform used to manage mobile network performance reports and analyze network performance.


Customizing Reports

Page 57

(iManager PRS V100R006 Product Description V1.1)


Restrictions on Measurement Activations

The period of measurement on the northbound interface should be consistent with that on the southbound interface. So far, Huawei support 15 minutes and 60 minutes periods as default.

There is no restriction on the number of NE objects or measurement objects. The measurement period can be15 minutes or 60 minutes. M2000 can provide all measurement results of all managed NEs via northbound performance file interface.

Page59

Contents

1. KPI Overview2. Performance KPI3. Driver test KPI

Page59

Coverage Ratio

• Object : Coverage test (RSRQ & RSRP)• Evaluation formula:

– Coverage radio = valid test kilometers / total test kilometers

• Standard: – The valid test kilometers should be satisfied for

RSRP ≥ -110dBm， RSRQ ≥ -3dB

Page60

Date post:	23-Dec-2015
Category:	Documents
Upload:	sunil-kumar
View:	31 times
Download:	2 times

Day 1 -Eutran Counters and MO Clases

Documents