utran qo s alert actions

QoS Alert actions (For Internal Use Only)

Issue 01

Date 2010-10-27

HUAWEI TECHNOLOGIES CO., LTD.

Issue 01 (2010-10-27) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

i

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com

mailto:[email protected]

QoS Alert actions – for internal use only Contents


iii

Contents

1 Sleeping cell........................................................................................................................... 1-1 1.1 3G Sleeping Cell.CS............................................................................................................................... 1-1

1.1.1 CS call Sleeping Cells definition.................................................................................................... 1-1 1.1.2 Action related ................................................................................................................................ 1-2

1.2 3G Sleeping Cell.PS............................................................................................................................... 1-3 1.2.1 PS call Sleeping Cells definition .................................................................................................... 1-3 1.2.2 Action related ................................................................................................................................ 1-5

2 Call Drop................................................................................................................................ 2-1 2.1 High_Call_Drop_CS .............................................................................................................................. 2-1

2.1.1 High_Call_Drop_CS definition...................................................................................................... 2-1 2.1.2 Action related. ............................................................................................................................... 2-2

2.2 High_Call_Drop_PS............................................................................................................................... 2-2 2.2.1 High_Call_Drop_PS definition. ..................................................................................................... 2-2 2.2.2 Action related. ............................................................................................................................... 2-3

2.3 High_Call_Drop_PS_R99....................................................................................................................... 2-3 2.3.1 High_Call_Drop_PS_R99 definition. ............................................................................................. 2-3 2.3.2 Action related. ............................................................................................................................... 2-3

2.4 High_Call_Drop_HSDPA....................................................................................................................... 2-4 2.4.1 High_Call_Drop_HSDPA definition............................................................................................... 2-4 2.4.2 Action related. ............................................................................................................................... 2-4

2.5 High_Call_Drop_HSUPA....................................................................................................................... 2-5 2.5.1 High_Call_Drop_HSUPA definition............................................................................................... 2-5 2.5.2 Action related. ............................................................................................................................... 2-5

3 Access failure......................................................................................................................... 3-1 3.1 High_RRCEst_failure.CS....................................................................................................................... 3-1

3.1.1 High_RRCEst_failure.CS definition............................................................................................... 3-1 3.1.2 Action related. ............................................................................................................................... 3-1

3.2 High_RRCEst_failure.PS ....................................................................................................................... 3-2 3.2.1 High_RRCEst_failure.PS definition. .............................................................................................. 3-2 3.2.2 Action related. ............................................................................................................................... 3-3

3.3 High_RRCEst_failure.Service ................................................................................................................ 3-3 3.3.1 High_RRCEst_failure.SERVICE definition.................................................................................... 3-3

Contents QoS Alert actions

iv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2010-10-27)

3.3.2 Action related. ............................................................................................................................... 3-4 3.4 High_RRCEst_failure.Other ................................................................................................................... 3-5

3.4.1 High_RRCEst_failure.OTHER definition....................................................................................... 3-5 3.4.2 Action related. ............................................................................................................................... 3-5

3.5 High_RABEst_failure.CS....................................................................................................................... 3-5 3.5.1 High_RABEST_FAILURE.CS definition....................................................................................... 3-5 3.5.2 Action related. ............................................................................................................................... 3-6

3.6 High_RABEst_failure.PS ....................................................................................................................... 3-6 3.6.1 High_RABEST_FAILURE.CS definition....................................................................................... 3-6 3.6.2 Action related. ............................................................................................................................... 3-7

4 Congestion ............................................................................................................................. 4-1 4.1 Cong.ULCE ........................................................................................................................................... 4-1

4.1.1 CONG.ULCE definition................................................................................................................. 4-1 4.1.2 Action related. ............................................................................................................................... 4-1

4.2 Cong.DLCE ........................................................................................................................................... 4-2 4.2.1 CONG.DLCE definition................................................................................................................. 4-2 4.2.2 Action related. ............................................................................................................................... 4-2

4.3 Cong.Code ............................................................................................................................................. 4-2 4.3.1 CONG.CODE definition. ............................................................................................................... 4-2 4.3.2 Action related. ............................................................................................................................... 4-3

4.4 Cong.Pwr ............................................................................................................................................... 4-3 4.4.1 CONG.PWR definition. ................................................................................................................. 4-3 4.4.2 Action related. ............................................................................................................................... 4-4

4.5 Cong.ULIub ........................................................................................................................................... 4-4 4.5.1 CONG.ULIUB definition. .............................................................................................................. 4-4 4.5.2 Action related. ............................................................................................................................... 4-5

4.6 Cong.DLIub ........................................................................................................................................... 4-5 4.6.1 CONG.DLIUB definition. .............................................................................................................. 4-5 4.6.2 Action related. ............................................................................................................................... 4-6

5 CS Erlang drop ...................................................................................................................... 5-1 5.1 Low CS Erlang per drop ......................................................................................................................... 5-1

5.1.1 LOW CS ERLANG PER DROP definition..................................................................................... 5-1 5.1.2 Action related. ............................................................................................................................... 5-1

6 Handover................................................................................................................................ 6-1 6.1 IRAT.CS.Outgoing ................................................................................................................................. 6-1

6.1.1 IRAT.CS.OUTGOING definition. .................................................................................................. 6-1 6.1.2 Action related. ............................................................................................................................... 6-1

6.2 IRATHO.RelocPreOut.CS ...................................................................................................................... 6-2 6.2.1 IRATHO.RELOCPREOUT.CS definition....................................................................................... 6-2 6.2.2 Action related. ............................................................................................................................... 6-2

6.3 IRAT.PS.Outgoing.................................................................................................................................. 6-3

QoS Alert actions – for internal use only Contents


v

6.3.1 IRAT.PS.OUTGOING definition.................................................................................................... 6-3 6.3.2 Action related. ............................................................................................................................... 6-3

6.4 IRAT.PS.Incoming.................................................................................................................................. 6-4 6.4.1 IRAT.PS.INCOMING definition. ................................................................................................... 6-4 6.4.2 Action related. ............................................................................................................................... 6-5

7 Cell Unavailability................................................................................................................ 7-1 7.1 CellUnavail ............................................................................................................................................ 7-1

7.1.1 Cell Unavailability definition......................................................................................................... 7-1 7.1.2 Action related ................................................................................................................................ 7-1

8 Transmission ......................................................................................................................... 8-1 8.1 Delay Packet .......................................................................................................................................... 8-1

8.1.1 Packet Loss definition.................................................................................................................... 8-1 8.1.2 Action related ................................................................................................................................ 8-2

8.2 Jitter....................................................................................................................................................... 8-2 8.2.1 Jitter definition .............................................................................................................................. 8-2 8.2.2 Action related ................................................................................................................................ 8-3

8.3 RX IP Path utilization............................................................................................................................. 8-3 8.3.1 Rx IP PATH utilization definition................................................................................................... 8-3 8.3.2 Action related ................................................................................................................................ 8-4

8.4 TX IP Path utilization ............................................................................................................................. 8-4 8.4.1 Tx IP PATH utilization definition ................................................................................................... 8-4 8.4.2 Action related ................................................................................................................................ 8-5

QoS Alert actions 1 Sleeping cell


1-1

1 Sleeping cell

Objective. The objective of this document is to define the precise actions to be performed according to related type of QOS alarm at the M2000. All the actions should be started from the first step and if the alarm still not cleared after the stability period, go on with next one.

Actions definition.

1.1 3G Sleeping Cell.CS 1.1.1 CS call Sleeping Cells definition

Sleeping cells is predicted by the following events between 8.00-23.00 each day. - Number of successful incoming CS VP call or AMR call is 0 at least 120 minutes and number of incoming DCH handover is greater than 30..

1 Sleeping cell QoS Alert actions

1-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2010-10-27)

QoS Alerter Name

3G Sleeping Cell.CS

QoS Alerter Scope

ENDTIME > @DAY, "8:00" && ENDTIME <= @DAY, "23:00" Only for cells bearing AMR call and/or CS VP call

Warning Predicate

([RLM.AttRLSetupIub]+[RLM.AttRLAddIub])>={30}))&&([VS.RB.DLConvCS.64]+ [VS.AMR.Ctrl.DL12.2]+[VS.RB.DLStrCS.57.6]+[VS.AMR.Ctrl.DL4.75]+[VS.AMR.Ctrl.DL5.15]+[VS.AMR.Ctrl.DL5.9]+[VS.AMR.Ctrl.DL6.7]+[VS.AMR.Ctrl.DL7.4]+[VS.AMR.Ctrl.DL7.95]+[VS.AMR.Ctrl.DL10.2])={0}) in 120 Minutes

Clearance Predicate

([VS.RB.DLConvCS.64]+ [VS.AMR.Ctrl.DL12.2]+[VS.RB.DLStrCS.57.6]+[VS.AMR.Ctrl.DL4.75]+[VS.AMR.Ctrl.DL5.15]+[VS.AMR.Ctrl.DL5.9]+[VS.AMR.Ctrl.DL6.7]+[VS.AMR.Ctrl.DL7.4]+[VS.AMR.Ctrl.DL7.95]+[VS.AMR.Ctrl.DL10.2])>{0}) in 30 Minutes

Table Name

UMTS Cell : CS Sleeping Cell

Stability (mins)

120

OMC number

1.1.2 Action related l - Check if most of RNC cells have “3G Sleeping Cell.CS” alarm.If they have, maybe

RNC abnormal or Iu CS interface abnormal. l - Check and investigate if there are some users camping in the alarmed cell. If there are

no users or it is just a low traffic cell(such as deserts cell,school cell,office cell),maybe it is a false alarm. Please ignore the alarm.

l - If possible,please inform the local maintenance personnel to dial in the alarmed cell l - Check RNC MML command：LST CELLACCESSSTRICT parameter

“IsAccessClass3Barred”, make sure that the value is “NOT_BARRED”. l - Check and investigate if there’s others type of alarm that specified related problem or

event. If there are, try to fix that problem. l -Make sure that there are no any users in the alarmed cell,then do following actions: l - Deactive the alarmed cell(RNC MML Command:DEA CELL) .1 minute later, reactive

the alarmed cell(RNC MML Command:ACT CELL). - Restart the NodeB’s RRU.

l - If all these actions not solve the problem, send this problem to huawei local team for support.



1-3

1.2 3G Sleeping Cell.PS 1.2.1 PS call Sleeping Cells definition

Sleeping cells is predicted by following between 8.00-23.00 each day. - Number of successful incoming PS call or HSDPA/HSUPA call is 0 at least 120 minutes and number of incoming DCH handover is greater than 30..

1 Sleeping cell QoS Alert actions


Issue 01 (2010-10-27)

QoS Alerter Name

3G PS Sleeping.PS

QoS Alerter Scope

ENDTIME > @DAY, "8:00" && ENDTIME <= @DAY, "23:00" Only for cells bearing PS call and/or HSDPA/HSUPA

Warning Predicate

([RLM.AttRLSetupIub]+[RLM.AttRLAddIub])>={30}))&&(([VS.PS.Bkg.DL.8.Thruput] + [VS.PS.Bkg.DL.16.Thruput] + [VS.PS.Bkg.DL.32.Thruput] + [VS.PS.Bkg.DL.64.Thruput] + [VS.PS.Bkg.DL.128.Thruput] + [VS.PS.Bkg.DL.144.Thruput] + [VS.PS.Bkg.DL.256.Thruput] + [VS.PS.Bkg.DL.384.Thruput] + [VS.PS.Int.DL.8.Thruput] + [VS.PS.Int.DL.16.Thruput] + [VS.PS.Int.DL.32.Thruput] + [VS.PS.Int.DL.64.Thruput] + [VS.PS.Int.DL.128.Thruput] + [VS.PS.Int.DL.144.Thruput] + [VS.PS.Int.DL.256.Thruput] + [VS.PS.Int.DL.384.Thruput] + [VS.PS.Str.DL.32.Thruput] + [VS.PS.Str.DL.64.Thruput] + [VS.PS.Str.DL.128.Thruput] + [VS.PS.Str.DL.144.Thruput] + [VS.DcchSrbKbps.Dl.Thruput]+[VS.PS.Bkg.UL.8.Thruput] + [VS.PS.Bkg.UL.16.Thruput] + [VS.PS.Bkg.UL.32.Thruput] + [VS.PS.Bkg.UL.64.Thruput] + [VS.PS.Bkg.UL.128.Thruput] + [VS.PS.Bkg.UL.144.Thruput] + [VS.PS.Bkg.UL.256.Thruput] + [VS.PS.Bkg.UL.384.Thruput] + [VS.PS.Int.UL.8.Thruput] + [VS.PS.Int.UL.16.Thruput] + [VS.PS.Int.UL.32.Thruput] + [VS.PS.Int.UL.64.Thruput] + [VS.PS.Int.UL.128.Thruput] + [VS.PS.Int.UL.144.Thruput] + [VS.PS.Int.UL.256.Thruput] + [VS.PS.Int.UL.384.Thruput] + [VS.PS.Str.UL.16.Thruput] + [VS.PS.Str.UL.32.Thruput] + [VS.PS.Str.UL.64.Thruput] + [VS.DcchSrbKbps.Ul.Thruput]+[VS.HSDPA.MeanChThroughput.TotalBytes]+[VS.HSUPA.MeanChThroughput.TotalBytes])={0}) in 120 minutes

Clearance Predicate

(([VS.PS.Bkg.DL.8.Thruput] + [VS.PS.Bkg.DL.16.Thruput] + [VS.PS.Bkg.DL.32.Thruput] + [VS.PS.Bkg.DL.64.Thruput] + [VS.PS.Bkg.DL.128.Thruput] + [VS.PS.Bkg.DL.144.Thruput] + [VS.PS.Bkg.DL.256.Thruput] + [VS.PS.Bkg.DL.384.Thruput] + [VS.PS.Int.DL.8.Thruput] + [VS.PS.Int.DL.16.Thruput] + [VS.PS.Int.DL.32.Thruput] + [VS.PS.Int.DL.64.Thruput] + [VS.PS.Int.DL.128.Thruput] + [VS.PS.Int.DL.144.Thruput] + [VS.PS.Int.DL.256.Thruput] + [VS.PS.Int.DL.384.Thruput] + [VS.PS.Str.DL.32.Thruput] + [VS.PS.Str.DL.64.Thruput] + [VS.PS.Str.DL.128.Thruput] + [VS.PS.Str.DL.144.Thruput] + [VS.DcchSrbKbps.Dl.Thruput]+[VS.PS.Bkg.UL.8.Thruput] + [VS.PS.Bkg.UL.16.Thruput] + [VS.PS.Bkg.UL.32.Thruput] + [VS.PS.Bkg.UL.64.Thruput] + [VS.PS.Bkg.UL.128.Thruput] + [VS.PS.Bkg.UL.144.Thruput] + [VS.PS.Bkg.UL.256.Thruput] + [VS.PS.Bkg.UL.384.Thruput] + [VS.PS.Int.UL.8.Thruput] + [VS.PS.Int.UL.16.Thruput] + [VS.PS.Int.UL.32.Thruput] + [VS.PS.Int.UL.64.Thruput] + [VS.PS.Int.UL.128.Thruput] + [VS.PS.Int.UL.144.Thruput] + [VS.PS.Int.UL.256.Thruput] + [VS.PS.Int.UL.384.Thruput] + [VS.PS.Str.UL.16.Thruput] + [VS.PS.Str.UL.32.Thruput] + [VS.PS.Str.UL.64.Thruput] + [VS.DcchSrbKbps.Ul.Thruput]+[VS.HSDPA.MeanChThroughput.TotalBytes]+[VS.HSUPA.MeanChThroughput.TotalBytes])>{0}) in 30 Minutes



1-5

Table Name UMTS Cell :PS Sleeping Cell

Stability (mins) 120

OMC number

1.2.2 Action related

l - Check if most of RNC cells have “3G Sleeping Cell.PS” alarm.If they have, maybe RNC abnormal or Iu PS interface abnormal.

l - Check and investigate if there are some users camping in the alarmed cell. If there are no users or it is just a low traffic cell(such as deserts cell,school cell,office cell),maybe it is a false alarm. Please ignore the alarm.

l - If possible,please inform the local maintenance personnel to do PS traffic(http/ftp) in the alarmed cell

l - Check RNC MML command：LST CELLACCESSSTRICT parameter “IsAccessClass3Barred”, make sure that the value is “NOT_BARRED”.

l - Check and investigate if there’s others type of alarm that specified related problem or event. If there are, try to fix that problem.

l -Make sure that there are no any users in the alarmed cell,then do following actions: l - Deactive the alarmed cell(RNC MML Command:DEA CELL) .1 minute later, reactive

the alarmed cell(RNC MML Command:ACT CELL). - Restart the NodeB’s RRU.

l - If all these actions not solve the problem, send this problem to huawei local team for support.

QoS Alert actions 2 Call Drop


2-1

2 Call Drop

Objective. The objective of this document is to define the precise actions to be performed according to related type of QOS alarm at the OMC-R. All the actions should be started from the first step and if the alarm still not cleared after the stability period, go on with next one.

Actions definition.

2.1 High_Call_Drop_CS 2.1.1 High_Call_Drop_CS definition.

High_Call_Drop_CS is predicted by this event between 8.00-23.00 each day.

- CS call drop ratio seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_Call_Drop_CS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Call_Drop_CS rate>10% in 2 continue hours and SUM(<VS.RAB.Loss.CS.RF> + <VS.RAB.Loss.CS.Abnorm> + <VS.RAB.Loss.CS.Norm>) must be more 20 times.

Clearance Predicate

Call_Drop_CS rate<5% in 1 continue hours

Table Name

Stability (mins) 60

OMC number

2 Call Drop QoS Alert actions


Issue 01 (2010-10-27)

2.1.2 Action related. Check alerting in M2000.

Check cell radius and Handover radius, ADD LOCELL: RADIUS=29000, HORAD=0, if the query result is not equals to baseline configuration, adjust to the baseline configuration. Baseline configuration is RADIUS=29000, HORAD=0.

Calculate the ratio between emergency call and CS call. If the ratio is bigger than 50% of a cell, in which there are a lot of emergency call. Then find out some special scenario within the cell coverage. The formula is RRC.AttConnEstab.EmgCall/( RRC.AttConnEstab.OrgConvCall + RRC.AttConnEstab.TmConvCall + RRC.AttConnEstab.EmgCall)

Check the IUB transmission problem of the site, to which the problem cell belongs.

Check the clock problem of the site, to which the problem cell belongs.

Check the interference around.

Check the inter-RAT HO problem.

Check the abnormal call drop ratio, abnormal call drop times / total call drop times, if the abnormal call ratio is bigger than 20%, send this problem to huawei local team for support.

2.2 High_Call_Drop_PS 2.2.1 High_Call_Drop_PS definition.

High_Call_Drop_PS is predicted by this event between 8.00-23.00 each day.

- PS call drop ratio seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_Call_Drop_PS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Call_Drop_PS rate >6% in 2 continue hours and SUM(( <VS.RAB.Loss.PS.RF> + <VS.RAB.Loss.PS.Abnorm> + <VS.RAB.Loss.PS.Norm> ) must be more 150 times.

Clearance Predicate

Call_Drop_PS rate<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number



2-3








2.3 High_Call_Drop_PS_R99 2.3.1 High_Call_Drop_PS_R99 definition.

High_Call_Drop_PS_R99 is predicted by this event between 8.00-23.00 each day.

- PS R99 call drop ratio seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_Call_Drop_PS_R99

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Call_Drop_PS(R99) rate>6% in 2 continue hours and SUM( <VS.RAB.Loss.PS.RF> + <VS.RAB.Loss.PS.Abnorm> + <VS.RAB.Loss.PS.Norm>- <VS.HSDPA.RAB.Loss.InActivity> - <VS.HSDPA.RAB.Loss.Abnorm.NonRF> - <VS.HSDPA.RAB.Loss.RF>- <VS.HSDPA.RAB.Loss.Norm> must be more 50 times.

Clearance Predicate

Call_Drop_PS(R99) rate<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number




Issue 01 (2010-10-27)







2.4 High_Call_Drop_HSDPA 2.4.1 High_Call_Drop_HSDPA definition.

High_Call_Drop_HSDPA is predicted by this event between 8.00-23.00 each day.

- HSDPA call drop ratio seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_Call_Drop_HSDPA

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Call_Drop_HSDPA rate>6% in 2 continue hours SUM(<VS.HSDPA.RAB.Loss.InActivity> + <VS.HSDPA.RAB.Loss.Abnorm.NonRF> + <VS.HSDPA.RAB.Loss.RF> + <VS.HSDPA.RAB.Loss.Norm> ) must be more 100 times.

Clearance Predicate

Call_Drop_HSDPA rate<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number





2-5






2.5 High_Call_Drop_HSUPA 2.5.1 High_Call_Drop_HSUPA definition.

High_Call_Drop_HSUPA is predicted by this event between 8.00-23.00 each day.

- HSUPA call drop ratio seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_Call_Drop_HSUPA

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Call_Drop_HSUPA rate>6% in 2 continue hours SUM( <VS.HSUPA.RAB.Loss.Norm> + <VS.HSUPA.RAB.Loss.Abnorm> ) must be more 50 times.

Clearance Predicate

Call_Drop_HSUPA rate<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number









Issue 01 (2010-10-27)


QoS Alert actions 3 Access failure


3-1

3 Access failure

3.1 High_RRCEst_failure.CS

3.1.1 High_RRCEst_failure.CS definition. High_RRCEst_failure.CS is predicted by this event between 8.00-23.00 each day.

- RRC CS establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_RRCEst_failure.CS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

RRCEst_failure rate(CS)>5% in 3 continue hoursand SUM(<RRC.AttConnEstab.OrgConvCall> + <RRC.AttConnEstab.TmConvCall> + <RRC.AttConnEstab.EmgCall>) must be more 20 times

Clearance Predicate

RRCEst_failure rate(CS)<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number

3.1.2 Action related. Check resource congestion status of the cell. Check CE, Code, IUB bandwidth, TCP etc.

Check the transmission of IUB interface.

Check the AAL2 path configuration.

3 Access failure QoS Alert actions


Issue 01 (2010-10-27)

Check alerting of the cell in M2000.

Check the SPU load of the cell locate.

Check the FACH channel congestion status.

Check the interference of the cell around.

After check the factors above and solve them, the RRC establish problem still exist, send this problem to huawei local team for support.

3.2 High_RRCEst_failure.PS 3.2.1 High_RRCEst_failure.PS definition.

High_RRCEst_failure.PS is predicted by this event between 8.00-23.00 each day.

- RRC PS establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_RRCEst_failure.PS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

RRCEst_failure rate(PS)>5% in 3 continue hours and SUM( <RRC.AttConnEstab.OrgStrCall> + <RRC.AttConnEstab.OrgInterCall> + <RRC.AttConnEstab.OrgBkgCall> + <RRC.AttConnEstab.OgSubCall> + <RRC.AttConnEstab.OgHhPrSig> + <RRC.AttConnEstab.OgLwPrSig> + <RRC.AttConnEstab.TmStrCall> + <RRC.AttConnEstab.TmInterCall> + <RRC.AttConnEstab.TmBkgCall> + <RRC.AttConnEstab.TmHhPrSig> + <RRC.AttConnEstab.TmLwPrSig> + <RRC.AttConnEstab.Unknown> + <RRC.AttConnEstab.Reg> + <RRC.AttConnEstab.CallReEst> ) must be more 150 times

Clearance Predicate

RRCEst_failure rate(PS)<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number



3-3









3.3 High_RRCEst_failure.Service

3.3.1 High_RRCEst_failure.SERVICE definition. High_RRCEst_failure.SERVICE is predicted by this event between 8.00-23.00 each day.

- RRC Service establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.



Issue 01 (2010-10-27)

Qos Alerter Name

High_RRCEst_failure.SERVICE

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

>8% in 3 continue hours and SUM( <RRC.AttConnEstab.OrgConvCall> + <RRC.AttConnEstab.OrgStrCall> + <RRC.AttConnEstab.OrgInterCall> + <RRC.AttConnEstab.OrgBkgCall> + <RRC.AttConnEstab.OgSubCall> + <RRC.AttConnEstab.OgHhPrSig> + <RRC.AttConnEstab.OgLwPrSig> + <RRC.AttConnEstab.TmConvCall> + <RRC.AttConnEstab.TmStrCall> + <RRC.AttConnEstab.TmInterCall> + <RRC.AttConnEstab.TmBkgCall> + <RRC.AttConnEstab.TmHhPrSig> + <RRC.AttConnEstab.TmLwPrSig> + <RRC.AttConnEstab.Unknown> + <RRC.AttConnEstab.Reg> + <RRC.AttConnEstab.EmgCall> + <RRC.AttConnEstab.CallReEst> ) must be more 170 times

Clearance Predicate

<6% in 1 continue hours

Table Name

Stability (mins) 60

OMC number











3-5

3.4 High_RRCEst_failure.Other

3.4.1 High_RRCEst_failure.OTHER definition. High_RRCEst_failure.OTHER is predicted by this event between 8.00-23.00 each day.

- RRC establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_RRCEst_failure.OTHER

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

RRCEst_failure rate(Other)>5% in 2 continue hours

Clearance Predicate

RRCEst_failure rate(Other)<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number









3.5 High_RABEst_failure.CS

3.5.1 High_RABEST_FAILURE.CS definition. High_RABEST_FAILURE.CS is predicted by this event between 8.00-23.00 each day.



Issue 01 (2010-10-27)

- RAB CS establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.

Qos Alerter Name

High_RABEST_FAILURE.CS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

RABEst_failure rate(CS)>5% in 3 continue hours and SUM ( <VS.RAB.AttEstab.AMR> + <VS.RAB.AttEstCS.Conv.64> ) must be more then 20 times

Clearance Predicate

RABEst_failure rate(CS)<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number







3.6 High_RABEst_failure.PS

3.6.1 High_RABEST_FAILURE.CS definition. High_RABEST_FAILURE.PS is predicted by this event between 8.00-23.00 each day.

- RAB PS establish failure seized by mobile for any purpose is greater than 0 at least 60 minutes.



3-7

Qos Alerter Name

High_RABEST_FAILURE.PS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

RABEst_failure rate(PS)>5% in 3 continue hours and SUM( <VS.RAB.AttEstabPS.Conv> + <VS.RAB.AttEstabPS.Str> + <VS.RAB.AttEstabPS.Inter> + <VS.RAB.AttEstabPS.Bkg> )must be more then 150 times

Clearance Predicate

RABEst_failure rate(PS)<4% in 1 continue hours

Table Name

Stability (mins) 60

OMC number







QoS Alert actions 4 Congestion


4-1

4 Congestion

4.1 Cong.ULCE

4.1.1 CONG.ULCE definition. CONG.ULCE is predicted by this event between 8.00-23.00 each day.

- ULCE congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

CONG.ULCE

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(ULCE)>2% in 2 continue hours

Clearance Predicate

Cong rate(ULCE)=0% in 30 continue minutes

Table Name

Stability (mins) 30

OMC number

4.1.2 Action related. Check if the Node B dynamic CE adjustment algorithm switch is open. If the algorithm switch is open, then change the GBR to smaller. SET USERGBR : UlGBR=D32, DlGBR=D32

After optimization the CE congestion is still there, then some CE resource expansion is recommended.

If all these actions not solve the problem, send this problem to huawei local team for support.

4 Congestion QoS Alert actions


Issue 01 (2010-10-27)

4.2 Cong.DLCE

4.2.1 CONG.DLCE definition. CONG.DLCE is predicted by this event between 8.00-23.00 each day.

- DLCE congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

CONG.DLCE

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(DLCE)>2% in 1 continue hours

Clearance Predicate

Cong rate(DLCE)=0% in 30 continue minutes

Table Name

Stability (mins) 30

OMC number

4.2.2 Action related. Check if the Node B dynamic CE adjustment algorithm switch is open. If the algorithm switch is open, then change the GBR to smaller. SET USERGBR : UlGBR=D32, DlGBR=D32

After optimization the CE congestion is still there, then some CE resource expansion is recommended.


4.3 Cong.Code 4.3.1 CONG.CODE definition.

CONG.CODE is predicted by this event between 8.00-23.00 each day.

- CODE congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.



4-3

Qos Alerter Name

CONG.CODE

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(Code)>2% in 1 continue hours

Clearance Predicate

Cong rate(Code)=0% in 30 continue minutes

Table Name

Stability (mins) 30

OMC number

4.3.2 Action related. Check the HSDPA code configuration. Change the parameter ALLOCCODEMODE to manual, change the code distribution to dynamic type in command MOD CELLHSDPA. HS-PDSCH max code number is 15, min code number is 1.

After optimization the code congestion is still there, some code resource expansion is recommended.


4.4 Cong.Pwr 4.4.1 CONG.PWR definition.

CONG.PWR is predicted by this event between 8.00-23.00 each day.

- Power congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.



Issue 01 (2010-10-27)

Qos Alerter Name

CONG.PWR

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(Power)>2% in 2 continue hours

Clearance Predicate

Cong rate(Power)=0% in 1 continue hours

Table Name

Stability (mins) 30

OMC number

4.4.2 Action related. Check the HSPA power access switch is closed. MOD CELLALGOSWITCH: NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0&HSDPA_GBP_MEAS-0. The switch should be closed.

If the power congestion is uplink, check the equipment version is RAN 12 and if the HSPA power access switch is closed already, modify equivalent user number to 140 or bigger, MOD CELLCAC: UlTotalEqUserNum=140.

If the power congestion is downlink, check the equipment version is RAN 12 and if the HSPA power access switch is closed ready, modify power access algorithm to loose access strategy, the command is MOD CELLALGOSWITCH: NBMDlCacAlgoSelSwitch=ALGORITHM_THIRD

After optimization if the power congestion is still there, some power resource expansion is recommended.


4.5 Cong.ULIub 4.5.1 CONG.ULIUB definition.

CONG.ULIUB is predicted by this event between 8.00-23.00 each day.

- IUB UL congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.



4-5

Qos Alerter Name

CONG.ULIUB

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(ULIub)>2% in 2 continue hours

Clearance Predicate

Cong rate(ULIub)=0% in 1 continue hours

Table Name

Stability (mins) 30

OMC number

4.5.2 Action related. Check the NCP / CCP congestion status. If the IUB bandwidth Utilization is bigger than 80%, expand the NCP / CCP bandwidth is necessary.

Check the user plan congestion status. If the real-time bandwidth configuration of path is smaller than 1.5M, the configuration can be changed to physical bandwidth. If the transmission is ATM type, bandwidth calculation is that 1E1 equals to 1.9 M, 2E1 equals to 3.8M, etc. If the transmission is IP type, check the real physical bandwidth.

If the path configuration is correct, change the BE service factor, the command is MOD TRMFACTOR: PSINTERDL=10, PSINTERUL=10, PSBKGDL=10, PSBKGUL=10, HDINTERDL=10, HDBKGDL=10, HUINTERUL=10, HUBKGUL=10

If the congestion is still there, change the GBR to smaller, the command is SET USERGBR : UlGBR=D32, DlGBR=D32

After optimization, the IUB transmission is still there, some IUB transmission expansion is recommended.


4.6 Cong.DLIub

4.6.1 CONG.DLIUB definition. CONG.DLIUB is predicted by this event between 8.00-23.00 each day.

- IUB DL congestion seized by mobile for any purpose is greater than 0 at least 30 minutes.



Issue 01 (2010-10-27)

Qos Alerter Name

CONG.DLIUB

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

Cong rate(ULIub)>2% in 2 continue hours

Clearance Predicate

Cong rate(ULIub)=0% in 1 continue hours

Table Name

Stability (mins) 30

OMC number

4.6.2 Action related. Check the NCP / CCP congestion status. If the IUB bandwidth Utilization is bigger than 80%, expand the NCP / CCP bandwidth is necessary.

Check the user plan congestion status. If the real-time bandwidth configuration of path is smaller than 1.5M, than the configuration can be changed to physical bandwidth. If the transmission is ATM type, bandwidth calculation is that 1E1 equals to 1.9 M, 2E1 equals to 3.8M. If the transmission is IP type, check the real physical bandwidth.

If the path configuration is correct, change the BE service factor, the command is MOD TRMFACTOR: PSINTERDL=10, PSINTERUL=10, PSBKGDL=10, PSBKGUL=10, HDINTERDL=10, HDBKGDL=10, HUINTERUL=10, HUBKGUL=10

If the congestion is still, change the GBR to smaller, the command is SET USERGBR : UlGBR=D32, DlGBR=D32

After optimization, the IUB transmission is still there, some IUB transmission expansion is recommended.


QoS Alert actions 5 CS Erlang drop


5-1

5 CS Erlang drop

5.1 Low CS Erlang per drop 5.1.1 LOW CS ERLANG PER DROP definition.

LOW CS ERLANG PER DROP is predicted by this event between 8.00-23.00 each day.

- LOW CS ERLANG PER DROP seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

LOW CS ERLANG PER DROP

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

CS Erlang per drop < 30 in 2 continue hours and (<VS.RB.DLConvCS.64> *4+ <VS.AMR.Ctrl.DL12.2> <VS.RB.DLStrCS.57.6.>*4+<VS.AMR.Ctrl.DL4.75>+<VS.AMR.Ctrl.DL5.15>+<VS.AMR.Ctrl.DL5.9>+<VS.AMR.Ctrl.DL6.7>+<VS.AMR.Ctrl.DL7.4>+<VS.AMR.Ctrl.DL7.95>+<VS.AMR.Ctrl.DL10.2>)/( <VS.RAB.Loss.CS.RF> + <VS.RAB.Loss.CS.Abnorm> + <VS.RAB.Loss.CS.Norm> )>0.016

Clearance Predicate

CS Erlang per drop > 40 in 1 continue hours

Table Name

Stability (mins)

30

OMC number


5 CS Erlang drop QoS Alert actions


Issue 01 (2010-10-27)


Calculate the ratio between emergency call and CS call. If the ratio is bigger than 50% of a cell, in which there are a lot of emergency call. Then find out some special scenario within the cell coverage. The formula is RRC.AttConnEstab.EmgCall/( RRC.AttConnEstab.OrgConvCall + RRC.AttConnEstab.TmConvCall + RRC.AttConnEstab.EmgCall)






QoS Alert actions 6 Handover


6-1

6 Handover

6.1 IRAT.CS.Outgoing

6.1.1 IRAT.CS.OUTGOING definition. IRAT.CS.OUTGOING is predicted by this event between 8.00-23.00 each day.

- IRAT.CS.OUTGOing seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

IRAT.CS.OUTGOING

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

IRAT.CS.Outgoing success rate<85% in 3 continue hours check the detail time with stat.

Clearance Predicate

IRAT.CS.Outgoing success rate>90% in 1 continue hours

Table Name

Stability (mins) 30

OMC number

6.1.2 Action related. Check the IRAT-HO neighbor, if there is something wrong, unreasonable, or missing, rectify them.

Check consistency of IRAT-HO 2G neighbor configuration information in RNC and GSM cell configuration information in BSC. If the information is not consistent, rectify them.

Check the CIO configuration of 3G cell face to 2G, if the CIO is not 0, change to 0 is recommended.

Check the clock alerting of GSM neighbor sites.

6 Handover QoS Alert actions


Issue 01 (2010-10-27)

Check clock alerting of 3G sites.

Check the interference of 2G sites around.

Check the IRAT-HO target threshold, if not 16, change to 16, the command is ADD CELLINTERRATHOCOV: TargetRatCsThd=16. If the IRAT-HO failure is still there, change the value to bigger, max value is 26. If the optimization did not affect the result, change the value to the original one.

Check the consistency of encryption algorithm configuration between 3G and 2G. Make sure the consistency.

Check the right FrequencyList configuration of IRAT-HO neighbor. If not correct, rectify it in GSM side.

Check the terminal capability to support the IRAT-HO.

Check the coverage around.

After optimization, if the IRAT-HO CS outgoing failure is still high, send this problem to huawei local team for support.

6.2 IRATHO.RelocPreOut.CS

6.2.1 IRATHO.RELOCPREOUT.CS definition. IRATHO.RELOCPREOUT.CS is predicted by this event between 8.00-23.00 each day.

- IRATHO.RELOCPREOUT.CS seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

IRATHO.RELOCPREOUT.CS

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

IRATHO.RelocPreOut.CS Success rate <90%

Clearance Predicate

IRATHO.RelocPreOut.CS Success rate >92%

Table Name

Stability (mins) 30

OMC number

6.2.2 Action related. Check the consistency of PLMN, LAC, BSIC information between UMTS Cell and GSM cell, which configured as IRAT-HO neighbors. If it is not consistency, change it in RNC side.



6-3

Check the consistency of PLMN, LAC, BSIC information between UMTS MSC side and GSM side. If it is not consistency, change it in 3G CN side.

If 2G and 3G not share the same MSC, check the LAC configuration of 3G in 2G CN side, if it is missing, compensate for it.

Check the Inter-RAT in BSC Handover Enable for 3G user. If it configure unable, change to enable.

Check the interaction configuration between different CN. It should be configured normally.

Check the congestion status of 2G TCH. If the congestion ratio is bigger than 1%, optimize the 2G resource is recommended.



After the optimization, the IRAT-HO prepare failure is still high, send this problem to huawei local team for support.

6.3 IRAT.PS.Outgoing 6.3.1 IRAT.PS.OUTGOING definition.

IRAT.PS.OUTGOING is predicted by this event between 8.00-23.00 each day.

- IRAT.PS.OUTGOING seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

IRAT.PS.OUTGOING

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

IRAT.PS.Outgoing success rate<75% in 2 continue hours check the detail time with stat.

Clearance Predicate

IRAT.PS.Outgoing success rate>80% in 1 continue hours

Table Name

Stability (mins) 30

OMC number

6.3.2 Action related. Check the IRAT-HO neighbor, if there is something wrong, unreasonable, or missing, rectify them.

Check consistency of IRAT-HO 2G neighbor configuration information in RNC and GSM cell configuration information in BSC. If the information is not consistent, rectify them.

6 Handover QoS Alert actions


Issue 01 (2010-10-27)

Check the CIO configuration of 3G cell face to 2G, if the CIO is not 0, change to 0 is recommended.

Check the clock alerting of GSM neighbor sites.

Check clock alerting of 3G sites.

Check the interference of 2G sites around.

Check the IRAT-HO target threshold, if not 16, change to 16, the command is ADD CELLINTERRATHOCOV: TargetRatCsThd=16. If the IRAT-HO failure is still there, change the value to bigger, max value is 26. If the optimization did not affect the result, change the value to the original one.

Check the consistency of encryption algorithm configuration between 3G and 2G. Make sure the consistency.

Check the right FrequencyList configuration of IRAT-HO neighbor. If not correct, rectify it in GSM side.



After optimization, if the IRAT-HO PS outgoing failure is still high, send this problem to huawei local team for support.

6.4 IRAT.PS.Incoming 6.4.1 IRAT.PS.INCOMING definition.

IRAT.PS.INCOMING is predicted by this event between 8.00-23.00 each day.

- IRAT.PS.INCOMING seized by mobile for any purpose is greater than 0 at least 30 minutes.

Qos Alerter Name

IRAT.PS.INCOMING

QoS Alerter Scope

08:00 - 24:00

Warning Predicate

IRAT.PS.Incoming success rate<95% in 2 continue hours check the detail time with stat.

Clearance Predicate

IRAT.PS.Incoming success rate>98% in 1 continue hours

Table Name

Stability (mins) 30

OMC number



6-5









QoS Alert actions 7 Cell Unavailability


7-1

7 Cell Unavailability

7.1 CellUnavail 7.1.1 Cell Unavailability definition

Generally, the “Cell Unavailability” QOS alarm is not necessary,because RNC has the equivalent alarm “ALM-2006: Cell Unavailable”.

Cell Unavailability is predicted by the following event between 8.00-23.00 each day. - Time length of cell unavailable is lagger 90% in 1 continue hours..

QoS Alerter Name

Cell Unavailability

QoS Alerter Scope

ENDTIME > @DAY, "0:00" && ENDTIME <= @DAY, "23:59"

Warning Predicate

[VS.Cell.Ratio.of.UnavailTime.OM]>{90}

Clearance Predicate

[VS.Cell.Ratio.of.UnavailTime.OM]={0}

Table Name UMTS Cell : Cell Unavailability

Stability (mins) 120

OMC number

7.1.2 Action related l - Check the RNC alarm if there is “ALM-2006: Cell Unavailable” about QOS alarmed

cell. If there are, try to fix that problem. l - Check RNC MML command：”DSP CELL”. l - Check the NodeB alarm if there is “ALM-28203: Local Cell Unavailable” about QOS

alarmed cell. If there are, try to fix that problem. l - Check NodeB MML command：”DSP LOCELL”

7 Cell Unavailability QoS Alert actions


Issue 01 (2010-10-27)

l - Check and investigate if there’s others type of alarm that specified related problem or event. If there are, try to fix that problem.

- If all these actions not solve the problem, send this problem to Huawei local support team

QoS Alert actions 8 Transmission


8-1

8 Transmission

Objective. The objective of this document is to define the precise actions to be performed according to related type of QOS alarm at the M2000. All the actions should be started from the first step and if the alarm still not cleared after the stability period, go on with next one.

Actions definition.

8.1 Delay Packet 8.1.1 Packet Loss definition

- The packet loss of IuCS is measured by the counter “VS.IPPATH.RTP.LossPktRatio.Rx”.

- The packet loss of IuPS is measured by the counter “VS.IPPATH.PING.MeanLOST”.

- The packet loss of Iub is measured by the counter “VS.IPPATH.PING.MeanLOST” or “VS.IPPM.Forword.DropMeans”.

The ping switch in the IPPATH configuration command “add/mod ippath” should be opened.

The IPPM function should be activated in the command “ACT IPPM”.

8 Transmission QoS Alert actions


Issue 01 (2010-10-27)

QoS Alerter Name

Packet Loss

QoS Alerter Scope


Warning Predicate

(Packet Loss > 5%)

Clearance Predicate

(Packet Loss < 1%)

Table Name Packet Loss

Stability (mins) 30

OMC number

8.1.2 Action related - Check the transmission bandwidth, whether the transmission is congestion.

- Ping the IP address in the middle L3 device step by step to make sure which device caused the packet loss. And then do next step.

- If it is L2 networking, need observe whether the alarm or the interface traffic statistic in the middle transmission device is normal.

- Start the IP/MAC capture function to do next step analysis at the same time in BTS/BSC LMT.

- Test the QoS of the transmission with the test instrument.


8.2 Jitter 8.2.1 Jitter definition

- The Jitter of IuCS is measured by the counter “VS.IPPATH.RTP.AverageJitter”.

- The Jitter of IuPS is measured by the counter “VS.IPPATH.PING.MeanJITTER”.

- The Jitter of Iub is measured by the counter “VS.IPPATH.PING.MeanJITTER” or “VS.IPPM.Forward.JitterStandardDeviation”.

The ping switch in the IPPATH configuration command “add/mod ippath” should be opened.

The IPPM function should be activated in the command “ACT IPPM”.



8-3

QoS Alerter Name

Jitter

QoS Alerter Scope


Warning Predicate

(Jitter > 15ms)

Clearance Predicate

(Jitter < 7ms)

Table Name Jitter

Stability (mins) 30

OMC number

8.2.2 Action related - Check the transmission bandwidth, whether the transmission is congestion.

- Ping the IP address in the middle L3 device step by step to make sure which device caused the jitter. And then do next step.

- If it is L2 networking, need observe whether the alarm or the interface traffic statistic in the middle transmission device is normal.

- Start the IP/MAC capture function to do next step analysis at the same time in BTS/BSC LMT.

- Test the QoS of the transmission with the test instrument.

If all these actions not solve the problem, send this problem to huawei local support team.

8.3 RX IP Path utilization 8.3.1 Rx IP PATH utilization definition

- The utilization of Iub is calculated by the following formula:

VS.IPDlAvgUsed.1/ VS.IPDlTotal.1(NodeB counter)

-The utilization of IuCS/IuPS is calculated by the following formula:

VS.FEGE.RXMEANSPEED/ LP_CFG_BW or

SUM（VS.SCTP.RXMEANSPEED，VS.IPPATH.IPLAYER.MEAN.RX）/ LP_CFG_BW

8 Transmission QoS Alert actions


Issue 01 (2010-10-27)

QoS Alerter Name

RX bandwidth utilization

QoS Alerter Scope


Warning Predicate

( > 95%)

Clearance Predicate

(< 90%)

Table Name RX bandwidth utilization

Stability (mins) 30

OMC number

8.3.2 Action related - Check whether the actual traffic is heavy.

- Check whether the retransmission or packet loss is existed.

- Expansion is adopted if the utilization is up to 95% in a long time.


8.4 TX IP Path utilization 8.4.1 Tx IP PATH utilization definition

- The utilization of Iub is calculated by the following formula:

VS.IPUlAvgUsed.1/ VS.IPUlTotal.1(NodeB counter)

-The utilization of IuCS/IuPS is calculated by the following formula:

VS.FEGE.TXMEANSPEED/ LP_CFG_BW or

SUM（VS.SCTP.TXMEANSPEED，VS.IPPATH.IPLAYER.MEAN.TX）/ LP_CFG_BW



8-5

QoS Alerter Name

TX bandwidth utilization

QoS Alerter Scope


Warning Predicate

( > 95%)

Clearance Predicate

(< 90%)

Table Name TX bandwidth utilization

Stability (mins) 30

OMC number

8.4.2 Action related - Check whether the actual traffic is heavy.

- Check whether the retransmission or packet loss is existed.

- Expansion is adopted if the utilization is up to 95% in a long time.


utran qo s alert actions

Engineering

huawei trademarks

huawei proprietary

huawei industrial base

g sleeping

sleeping cells definition

contents issue

cs definition

internal use