UL Unified Overload Control(SRAN10.1_01)

7/25/2019 UL Unified Overload Control(SRAN10.1_01)

1/42

SingleRAN

UL Unified Overload Control Feature

Parameter Description

Issue 01

Date 2015-03-23

HUAWEI TECHNOLOGIES CO., LTD.


2/42

Copyright Huawei Technologies Co., Ltd. 2015. 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 thepurchase 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 a 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]

Issue 01 (2015-03-23) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/42

Contents

1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1

1.2 Intended Audience..........................................................................................................................................................1

1.3 Change History...............................................................................................................................................................1

1.4 Differences Between Base Station Types.......................................................................................................................3

2 Overview......................................................................................................................................... 4

2.1 Background.....................................................................................................................................................................4

2.2 Introduction.................................................................................................................................................................... 4

2.3 Benefits...........................................................................................................................................................................4

2.4 Architecture.................................................................................................................................................................... 4

3 Technical Description...................................................................................................................7

3.1 Introduction.................................................................................................................................................................... 7

3.2 Determining the Traffic Status of UMTS and LTE Networks........................................................................................73.2.1 Determining the Air-Interface Load Status of an LTE Cell by the eNodeB................................................................7

3.2.2 Determining the Air-Interface Load Status of a UMTS Cell by the RNC.................................................................. 8

3.2.3 Determining the Traffic Status of UMTS/LTE Inter-RAT Neighboring Cells and Frequencies by the eCoordinator

.............................................................................................................................................................................................. 9

3.3 Adjusting the Policies of Interoperability Between UMTS and LTE Networks.......................................................... 11

3.3.1 Adjusting the Policies of Interoperability from LTE to UMTS.................................................................................11

3.3.2 Adjusting the Policies of Interoperability from UMTS to LTE.................................................................................11

4 Related Features...........................................................................................................................13

5 NetworkImpact........................................................................................................................... 14

6 Engineering Guidelines............................................................................................................. 15

6.1 When to Use UL Unified Overload Control.................................................................................................................15

6.2 Required Information................................................................................................................................................... 15

6.3 Network Planning.........................................................................................................................................................16

6.3.1 RF Planning...............................................................................................................................................................16

6.3.2 Network Planning......................................................................................................................................................16

6.3.3 Hardware Planning.................................................................................................................................................... 16

6.4 Deployment.................................................................................................................................................................. 17

6.4.1 Requirements.............................................................................................................................................................17

SingleRAN

UL Unified Overload Control Feature Parameter

Description Contents



ii


4/42

6.4.2 Data Preparation........................................................................................................................................................ 17

6.4.3 Precautions.................................................................................................................................................................22

6.4.4 Activation.................................................................................................................................................................. 22

6.4.4.1 Using MML Commands.........................................................................................................................................22

6.4.4.2 MML Command Examples.................................................................................................................................... 23

6.4.4.3 Using the CME.......................................................................................................................................................24

6.4.5 Activation Observation..............................................................................................................................................26

6.4.6 Deactivation...............................................................................................................................................................28

6.4.6.1 Using MML Commands.........................................................................................................................................28

6.4.6.2 MML Command Examples.................................................................................................................................... 28

6.4.6.3 Using the CME.......................................................................................................................................................28

6.4.7 Reconfiguration......................................................................................................................................................... 29

6.5 Performance Monitoring...............................................................................................................................................29

6.6 Parameter Optimization................................................................................................................................................30

6.7 Troubleshooting............................................................................................................................................................30

7 Parameters.....................................................................................................................................31

8 Counters........................................................................................................................................ 35

9 Glossary.........................................................................................................................................37

10 Reference Documents...............................................................................................................38

SingleRAN


Description Contents



iii


5/42

1About This Document

1.1 Scope

This document describes MRFD-101402 UL Unified Overload Control, including its

technical principles, related features, network impact, and engineering guidelines.

1.2 Intended Audience

This document is intended for personnel who:

l Need to understand the feature described herein

l Work with Huawei products

1.3 Change History

This section provides information about the changes in different document versions. There are

two types of changes, which are defined as follows:

l Feature change

Changes in features of a specific product version

l Editorial change

Changes in wording or addition of information that was not described in the earlier

version

SRAN10.1 01 (2015-03-23)

This issue includes the following changes.

ChangeType

Change Description Parameter Change

Feature

change

None None

SingleRAN


Description 1 About This Document



1


6/42

ChangeType


Editorial

change

Modified the IDs of the following counters:

lL.Traffic.User.Avg

l L.RRC.ConnReq.Att

l L.RRC.SetupFail.ResFail.UserSpec

l L.RRC.SetupFail.ResFail.PUCCH

For details, see 6.2 Required Information.

None

Added requirements for neighboring cells before

feature deployment. For details, see section

6.4.1 Requirements.

None

SRAN10.1 Draft B (2015-02-10)

This issue includes the following changes.

ChangeType


Feature

change

Changed the ID of the UL Unified Overload

Control Switchparameter from

PROCESSSWITCH:

ULUNIOLCTRL_SWITCHto

ULUOCSwitchand changed the correspondingMO from ECOMMONCTRLto

ULUNIOLCTRL. For details, see the

following sections:

l 3.1 Introduction

l 6.4.2 Data Preparation

l 6.4.4 Activation

l 6.4.6 Deactivation

ULUOCSwitch

Editorial

change

None None

SRAN10.1 Draft A (2015-01-15)

This document is created for SRAN10.1.

SingleRAN





2


7/42

1.4 Differences Between Base Station Types

Definition

The macro base stations described in this document refer to 3900 series base stations. These

base stations work in GSM, UMTS, or LTE mode, as listed in the section Scope.

The LampSite base stations described in this document refer to distributed base stations that

provide indoor coverage. These base stations work in UMTS or LTE mode but not in GSM

mode.

The micro base stations described in this document refer to all integrated entities that work in

UMTS or LTE mode but not in GSM mode. Descriptions of boards, cabinets, subracks, slots,

and RRUs do not apply to micro base stations.

The following table defines the types of micro base stations.

Base Station Model RAT

BTS3202E LTE FDD

NOTE

The co-MPT and separate-MPT applications are irrelevant to single-mode micro base stations.

Feature Support by Macro, Micro, and LampSite Base StationsNo difference

Function Implementation in Macro, Micro, and LampSite Base Stations

No difference

SingleRAN





3


8/42

2Overview

2.1 Background

The development of wireless communication technology accelerates the upgrade of wireless

networks and intelligent terminals. Currently, a large number of telecom operators have

deployed co-coverage UMTS and LTE networks, and most mobile terminals can support

multiple modes and enjoy both UMTS and LTE services at the same time. In high-traffic

scenarios, such as sporting events, concerts, and big festivals, as network traffic fluctuates,

multimode terminals' frequent interoperability between UMTS and LTE networks may

generate excess signaling overheads, which affects network performance. Therefore, the UL

Unified Overload Control feature is introduced into hotspots in which UMTS and LTE

networks share the same coverage.

This feature optimizes interoperability between UMTS and LTE networks based on the

network traffic of both networks, in order to improve the RRC setup success rate, access

success rate, and inter-RAT handover success rate of these networks.

2.2 Introduction

With UL Unified Overload Control, the eCoordinator can determine whether UMTS and LTE

networks are under heavy traffic and whether to adjust the policies of handover, redirection,

and reselection between UMTS and LTE networks.

2.3 Benefits

When traffic is constantly heavy on co-coverage UMTS and LTE networks in scenarios such

as sporting events, concerts, and big festivals, this feature can increase the RRC connection

setup success rate, access success rate, and inter-RAT handover success rate of these

networks.

2.4 Architecture

Figure 2-1shows how information is exchanged between network elements (NEs).

SingleRAN


Description 2 Overview



4


9/42

Figure 2-1Information exchange between NEs

Table 2-1describes the functions of these NEs involved in this feature.

Table 2-1Functions of each NE involved in this feature

NE Function

RNC l Periodically reports the air-interface load status of UMTS cells to

the eCoordinator.

l Adjusts the policies of interoperability between UMTS and LTE

networks based on the heavy-traffic state of neighboring LTEcells and frequencies reported by the eCoordinator. For specific

implementation technologies, see 3 Technical Description.

eCoordinator l Based on the traffic status of UMTS and LTE cells periodically

reported by the RNC and eNodeB, respectively, the eCoordinator

periodically determines whether the neighboring LTE cells of

these UMTS cells and the neighboring UMTS cells of these LTE

cells are under heavy traffic and then reports the neighboring cell

information to the eNodeB and RNC, for the purposes of target

cell selection during inter-RAT handover.

l Based on the heavy-traffic status of neighboring UMTS cells for

LTE cells and of neighboring LTE cells for UMTS cells, theeCoordinator periodically determines whether the neighboring

UMTS frequencies of these LTE cells and the neighboring LTE

frequencies of these UMTS cells are under heavy traffic and then

reports the neighboring frequency information to the eNodeB and

RNC, for the purposes of target frequency selection during

redirection. For UMTS cells, the neighboring frequency

information is also used for cell reselection.

SingleRAN





5


10/42

NE Function

eNodeB l Periodically reports the heavy-traffic state of LTE cells to the

eCoordinator.

lAdjusts the policies of interoperability between UMTS and LTEnetworks based on the heavy-traffic state of neighboring UMTS

cells and frequencies reported by the eCoordinator. For specific

implementation technologies, see 3 Technical Description.

SingleRAN





6


11/42

3Technical Description

3.1 Introduction

The UL Unified Overload Control feature is controlled by the following switches:

l RNC side:HoSwitch2: HO_UL_UOLC_SWITCH

l eCoordinator side: ULUNIOLCTRL: ULUOCSwitch

These switches must both be turned on to enable this feature.

This feature determines whether UMTS and LTE networks are under heavy traffic and adjusts

the policies of interoperability between these networks accordingly.

3.2 Determining the Traffic Status of UMTS and LTENetworks

3.2.1 Determining the Air-Interface Load Status of an LTE Cell bythe eNodeB

After this feature is enabled, the eNodeB periodically (every five minutes) determines the

states of an LTE cell based on the number of RRC connection setup requests, the RRC

rejection rate due to resource insufficiency, and the number of UEs in connected mode. AnLTE cell has two states: heavy-traffic and normal. Figure 3-1shows how an LTE cell

switches between these states.

SingleRAN


Description 3 Technical Description



7


12/42

Figure 3-1State switching of an LTE cell

l When an LTE cell is in the normal state, if condition 1 is met, the cell enters the heavy-

traffic state. Otherwise, the cell remains in the normal state.

l When an LTE cell is in the heavy-traffic state, if condition 2 is met, the cell enters the

normal state. Otherwise, the cell remains in the heavy-traffic state.

Condi

tion 1

Condition 1 is met if either of the following is true:

l Number of UEs in connected mode UeNumHighThd

l Number of RRC connection setup requests RrcReqNumHighThdand RRCrejection rate due to resource insufficiency RrcRejectRateHighThd

Condi

tion 2

Condition 2 is met if both of the following are true:

l Number of UEs in connected mode < UeNumLowThd

l Number of RRC connection setup requests


13/42

Figure 3-2State switching of a UMTS cell

l When a UMTS cell is in the normal state, if condition 1 is met, the cell enters the

congested state. Otherwise, the cell remains in the normal state.

l When a UMTS cell is in the congested state, if condition 2 is met, the cell enters the

normal state. Otherwise, the cell remains in the congested state.

Condi

tion 1

Condition 1 is met if both of the following are true:

l Downlink non-HSPA power load status DLPwrLoadStaForULUniOLCor

Actual uplink service load status ULActulLoadStaForULUniOLC

l DCH user number load status DchUserLoadStaForULUniOLC

Condi

tion 2

Condition 2 is met if either of the following is true:

l Downlink non-HSPA power load status


14/42

1. Determining the traffic status of neighboring LTE cells for UMTS cells

The eCoordinator periodically (every five minutes) determines the heavy-traffic state of

neighboring LTE cells for UMTS cells based on the relationships of neighboring LTE

cells for UMTS cells and the heavy-traffic state of LTE cells reported by the eNodeB.

2. Determining the traffic status of neighboring UMTS cells for LTE cells

a. The eCoordinator periodically measures the proportion of the duration in which a

UMTS cell is congested based on the air-interface load of the UMTS cell

periodically reported by the RNC. Then, the eCoordinator determines whether the

UMTS cell is in the heavy-traffic or normal state according to the following rules:

- If the proportion of the duration in which a UMTS cell is congested

UCellCongTimeRateHighThd, the UMTS cell is in the heavy-traffic state.

- If the proportion of the duration in which a UMTS cell is congested Enhanced Feature Management> Feature Operation and Maintenance.

6.4.5 Activation Observation

Use the following two methods to determine whether this feature has taken effect:

Monitoring Counters

On the U2000, monitor the values of the counters listed in Table 6-6. If the value of any

counter is not zero, this feature has taken effect.

SingleRAN


Description 6 Engineering Guidelines



26


31/42

Table 6-6eCoordinator counters

Counter ID Counter Name Counter Description

73430335 VS.ELTECELL.ULUOC.Ov

erload.Num

Number of Times an LTE

Cell Is Overloaded

73430336 VS.ELTECELL.ULUOC.N

FreqStatusMod.Num

Number of Times the

Overload Status of a

Neighboring UMTS

Frequency for an LTE Cell

Changes

73430333 VS.EUMTSCELL.ULUOC.

Overload.Num

Number of Times a UMTS

Cell Is Overloaded

73430334 VS.EUMTSCELL.ULUOC.

NFreqStatusMod.Num

Number of Times the

Overload Status of a

Neighboring LTE Frequencyfor a UMTS Cell Changes

Tracing Messages

On the LMT, if you observe Se and Sr messages as listed in Table 6-7and Table 6-8, this

feature has taken effect.

Table 6-7Messages between the eCoordinator and the eNodeB

Direction Name Description

eCoordinator->eNodeB ULUOC UCELL LOAD Heavy-traffic state of

neighboring UMTS cells

and frequencies for LTE

cells

eNodeB->eCoordinator ENB CELL LOAD

STATUS RPT

Heavy-traffic state of LTE

cells

Table 6-8Messages between the eCoordinator and the RNC

Direction Name Description

eCoordinator->RNC ULUOC LCELL LOAD Heavy-traffic state of

neighboring LTE cells and

frequencies for UMTS cells

RNC->eCoordinator RNC CELL LOAD

STATUS RPT

Air-interface load status of

UMTS cells

SingleRAN





27


32/42

6.4.6 Deactivation

6.4.6.1 Using MML Commands

l eCoordinator

Run the MML command SET ULUNIOLCTRLto set the UL Unified Overload

Control Switchto OFF.

l RNC

Run the MML command SET UCORRMALGOSWITCHto deselect the

HO_UL_UOLC_SWITCHcheck box under the HoSwitch2parameter.

6.4.6.2 MML Command Examples//Turning off the UL Unified Overload Control Switch on the eCoordinator

SET ULUNIOLCTRL: ULUOCSwitch=OFF;

//Turning off the UL Unified Overload Control Switch on the RNC

SET UCORRMALGOSWITCH: HoSwitch2=HO_UL_UOLC_SWITCH-0;

6.4.6.3 Using the CME

NOTE

When configuring the UL Unified Overload Control feature on the CME, perform a single configuration

first, and then perform a batch modification if required. Configure the parameters of a single object

before a batch modification. Perform a batch modification before logging out of the parameter setting

interface.

Step 1 Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 6-9. For instructions

on how to perform the CME single configuration, see CME Single Configuration Operation

Guide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects in batches, click on the CME to start the batch modification wizard.

For instructions on how to perform a batch modification through the CME batch modification

center, press F1 while running the wizard to obtain online help.

Table 6-9Configuring parameters on the CME

SN MO NE ParameterName

Parameter ID Configurable in CMEBatchModification Center

1 UCORRMALGO

SWITCH

RNC UL

Unified

Overloa

d

Control

Switch

HoSwitch2:

HO_UL_UOL

C_SWITCH

Yes

SingleRAN





28


33/42

SN MO NE ParameterName

Parameter ID Configurable in CMEBatchModificatio

n Center

2 ULUNIOLCTRL eCoordinator UL

Unified

Overloa

d

Control

Switch

ULUOCSwitch Yes

----End

6.4.7 Reconfiguration

None

6.5 Performance Monitoring

Feature gains can be monitored by the KPIs listed in Table 6-10or the performance counters

listed in Table 6-11. After this feature takes effect, the values of the KPIs listed in Table 6-10

increase and those of the performance counters listed in Table 6-11decrease.

Table 6-10eNodeB KPIs

KPI Name KPI Description

Inter-RAT Handover Out Success Rate (LTE

to WCDMA)

Success rate of outgoing inter-RAT

handovers from LTE to WCDMA

RRC Setup Success Rate (Service) Success rate of RRC connection setups for

services

RRC Setup Success Rate (Signaling) Success rate of RRC connection setups for

signaling

Table 6-11RNC performance counters

Counter ID Counter Name Counter Description

73423414 VS.U2LTEHO.FailRelocPr

epOutPS.NoResAvail

Number of Failed

Preparations for Outgoing

UMTS-to-LTE PS

Handovers for Cell (No

Resource Available)

SingleRAN





29


34/42

6.6 Parameter Optimization

l If the RRC connection setup success rate (including service and signaling) is low in the

LTE cell, or if the value of the VS.U2LTEHO.FailRelocPrepOutPS.NoResAvail counter

is large in the cell, adjust the settings of the following eNodeB parameters:

Reduce the value of the High UE Number Thd for UL Uni-OLCparameter (ID:

UeNumHighThd). However, the value of this parameter cannot be less than that of

the UeNumLowThdparameter.

Reduce the value of the High RRC Request Number Thd for UL Uni-OLC

parameter (ID:RrcReqNumHighThd). However, the value of this parameter cannot

be less than that of theRrcReqNumLowThdparameter.

Reduce the value of the High RRC Reject Rate Thd for UL Uni-OLC(%)

parameter (ID:RrcRejectRateHighThd). However, the value of this parameter

cannot be less than that of theRrcRejectRateLowThdparameter.

l If the success rate of outgoing inter-RAT handovers from LTE to WCDMA is low, adjust

the settings of the following parameters:

a. Reduce the value of the eCoordinator parameter High Thld for UMTS Cell

Congestion Time Rate(ID: UCellCongTimeRateHighThd).

b. Reduce the value of the RNC parameter DL Power Load Congest Thld for UL

Unified OLC(ID:DLPwrLoadStaForULUniOLC).

Reduce the value of the RNC parameter UL Actual Load Congest Thld for UL

Unified OLC(ID: ULActulLoadStaForULUniOLC).

Reduce the value of the RNC parameter DCH User Number Congest Thld for UL

Unified OLC(ID:DchUserLoadStaForULUniOLC).

6.7 Troubleshooting

None

SingleRAN





30


35/42

7ParametersTable 7-1Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUL

Unified

OLC

RrcReq

NumHig

hThd

MOD

CELLU

LUNIFI

EDOLC

LST

CELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overloa

d

Control

Meaning: Indicates the threshold of the number of

RRC connection setup requests, which is used to

determine whether to start UMTS and LTE unified

overload control. UMTS and LTE unified overload

control starts when both of the following conditions

are met: (1) The number of RRC connection setup

requests is greater than the RrcReqNumHighThd

parameter value; (2)The resource-insufficiency-induced RRC connection rejection rate is greater than

the RrcRejectRateHighThd parameter value.

GUI Value Range: 1~20000

Unit: None

Actual Value Range: 1~20000

Default Value: 2000

SingleRAN


Description 7 Parameters



31


36/42

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUL

Unified

OLC

RrcReje

ctRateHi

ghThd

MOD

CELLU

LUNIFI

EDOLC

LST

CELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overloa

d

Control

Meaning: Indicates the threshold of the resource-

insufficiency-induced RRC connection rejection rate,

which is used to determine whether to start UMTS and

LTE unified overload control. UMTS and LTE unified

overload control starts when both of the following

conditions are met: (1) The resource-insufficiency-

induced RRC connection rejection rate is greater than

the RrcRejectRateHighThd parameter value; (2) The

number of RRC connection setup requests is greater

than the RrcReqNumHighThd parameter value. The

actual threshold equals the percentage value of this

parameter divided by 10. For example, the GUI value

10 indicates that the actual value is 1% (= 10 x 1%/10).


Unit: %


Default Value: 50

CellUL

Unified

OLC

RrcReq

NumLo

wThd

MOD

CELLU

LUNIFI

EDOLC

LSTCELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overloa

d

Control

Meaning: Indicates the threshold of the RRC

connection setup request number, which is used to

determine whether to stop UMTS and LTE unified


control stops if all of the following conditions are met:(1) The number of RRC_CONNECTED UEs is less

than the UeNumLowThd parameter value; (2) The

resource-insufficiency-induced RRC connection

rejection rate is less than the RrcRejectRateLowThd

parameter value; (3) The number of RRC connection

setup requests is less than the RrcReqNumLowThd

parameter value.


Unit: None


Default Value: 1000

SingleRAN





32


37/42

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUL

Unified

OLC

RrcReje

ctRateL

owThd

MOD

CELLU

LUNIFI

EDOLC

LST

CELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overloa

d

Control

Meaning: Indicates the threshold of the resource-

insufficiency-induced RRC connection rejection rate,

which is used to determine whether to stop UMTS and

LTE unified overload control. UMTS and LTE unified

overload control stops if all of the following

conditions are met: (1) The number of

RRC_CONNECTED UEs is less than the

UeNumLowThd parameter value; (2) The resource-

insufficiency-induced RRC connection rejection rate

is less than the RrcRejectRateLowThd parameter

value; (3) The number of RRC connection setup

requests is less than the RrcReqNumLowThd

parameter value. The actual threshold equals thepercentage value of this parameter divided by 10. For

example, the GUI value 10 indicates that the actual

value is 1% (= 10 x 1%/10).


Unit: %


Default Value: 10

CellUL

Unified

OLC

UeNum

HighTh

d

MOD

CELLU

LUNIFIEDOLC

LST

CELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overload

Control

Meaning: Indicates the RRC_CONNECTED UE

number threshold used to determine whether to start

UMTS and LTE unified overload control. UMTS andLTE unified overload control starts when the number

of RRC_CONNECTED UEs is greater than this

parameter value.


Unit: None


Default Value: 400

SingleRAN





33


38/42

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellUL

Unified

OLC

UeNum

LowThd

MOD

CELLU

LUNIFI

EDOLC

LST

CELLU

LUNIFI

EDOLC

MRFD-

101402

UL

Unifed

Overloa

d

Control

Meaning: Indicates the threshold of the

RRC_CONNECTED UE number, which is used to

determine whether to stop UMTS and LTE unified


control stops if all of the following conditions are met:

(1) The number of RRC_CONNECTED UEs is less

than the UeNumLowThd parameter value; (2) The

resource-insufficiency-induced RRC connection

rejection rate is less than the RrcRejectRateLowThd

parameter value; (3) The number of RRC connection

setup requests is less than the RrcReqNumLowThd

parameter value.


Unit: None


Default Value: 250

SingleRAN





34


39/42

8CountersTable 8-1Counters

Counter ID Counter Name CounterDescription

Feature ID Feature Name

1526726658 L.RRC.ConnReq.At

t

Number of RRC

connection setup

requests

(retransmission

excluded)

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002007

TDLBFD-002007

RRC Connection

Management

RRC Connection

Management

1526727378 L.Traffic.User.Avg Average number of users in a cell

Multi-mode: NoneGSM: None

UMTS: None

LTE:

LBFD-002007

TDLBFD-002007

RRC ConnectionManagement

RRC Connection

Management

1526728485 L.RRC.SetupFail.R

esFail.SRS

Number of RRC

connection setup

failures due to SRS

resource allocation

failure

Multi-mode: None

GSM: None

UMTS: None

LTE:LBFD-002007

TDLBFD-002007

RRC Connection

Management

RRC Connection

Management


esFail.PUCCH

Number of RRC

connection setup

failures due to

PUCCH resource

allocation failure

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002007

TDLBFD-002007

RRC Connection

Management

RRC Connection

Management

SingleRAN


Description 8 Counters



35


40/42

Counter ID Counter Name CounterDescription

Feature ID Feature Name


ej.FlowCtrl

Number of times

the eNodeB sends

an RRC Connection

Reject message to

the UE due to flow

control

Multi-mode: None

GSM: NoneUMTS: None

LTE:

LBFD-002007

TDLBFD-002007

RRC Connection

Management

RRC Connection

Management


esFail.UserSpec

Number of RRC

connection setup

failures because of

limitation of UE

number

specification

Multi-mode: None

GSM: None

UMTS: None

LTE:

LBFD-002007TDLBFD-002007

RRC Connection

Management

RRC Connection

Management

SingleRAN


Description 8 Counters



36


41/42

9GlossaryFor the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN


Description 9 Glossary



37


42/42

10Reference Documents1. RANLoad Measurement Feature Parameter Description

2. eRANInter-RAT Mobility Management in Connected Mode

3. RANInteroperability Between UMTS and LTE Feature Parameter Description

SingleRAN


Description 10 Reference Documents