UL Unified Overload Control(SRAN10.1_01)

SingleRAN

UL Unified Overload Control Feature Parameter Description Issue

01

Date

2015-03-23

HUAWEI TECHNOLOGIES CO., LTD.

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 trademarks and trade names mentioned mentioned in this this document are are the property of of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. 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, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial 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

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 trademarks and trade names mentioned mentioned in this this document are are the property of of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. 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, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2015-03-23)


i

SingleRAN UL Unified Overload Control Feature Parameter Description

Contents

Contents 1 About This This Document........... Document................................. ............................................ ............................................. ............................................. .................................... .............. 1 1.1 Scope........................................................................................................... Scope....... ....................................................................................................................................................................... ................................................................... 1 1.2 Intended Audience..........................................................................................................................................................1 1.3 Change History................................................................................................... H istory............................................................................................................................................................... ............................................................ 1 1.4 Differences Differences Between Base Station Types....................................................................................................................... Types....................................................................................................................... 3

2 Overview.................. Overview......................................... ............................................. ............................................ ............................................ ............................................ .............................. ........ 4 2.1 Background........................................................... Background................................................................................................................................................................. ..........................................................................................................4 ....4 2.2 Introduction................................................................................................. Introduction.................................................................................................................................................................... ................................................................... 4 2.3 Benefits...........................................................................................................................................................................4 Benefits...........................................................................................................................................................................4 2.4 Architecture.................................................................................................. Architecture.................................................................................................................................................................... .................................................................. 4

3 Technical Description........ Description.............................. ............................................ ............................................. ............................................. ........................................7 ..................7 3.1 Introduction................................................................................................. Introduction.................................................................................................................................................................... ................................................................... 7 3.2 Determining Determining the Traffic Status of UMTS and LTE Networks........................................................................................7 Networks........................................................................................7 3.2.1 Determining Determining the Air-Interface Load Status of an LTE Cell by the eNodeB................................................................7 3.2.2 Determining Determining the Air-Interface Load Status of a UMTS Cell by the RNC.................................................................. RNC.................................................................. 8 3.2.3 Determining Determining the Traffic Status of UMT S/L S/LTE TE Inter-RAT Inter-RAT Neighboring Cells and Frequencies by the eCoordinator .............................................................................................................................................................................................. .............................................................................................. ................................................................................................ 9 3.3 Adjusting the Policies of Interoperability Between UMTS and LTE LTE Networks.......................................................... 11 3.3.1 Adjusting Adjusting the Policies of Interoperability from LTE to UMTS.................................................................................11 3.3.2 Adjusting Adjusting the Policies of Interoperability from UMTS to LTE.................................................................................11

4 Related Features........ Features.............................. ............................................ ............................................. ............................................. ............................................ .......................... ....13 13 5 Network Impact........... Impact.................................. ............................................. ............................................ ............................................ ............................................ ........................ 14 6 Engineering Engineering Guidelines............ Guidelines.................................. ............................................ ............................................ ............................................ ............................... ......... 15 6.1 When to Use U se UL Unified Overload Control.......................................................................................... Control.................................................................................................................15 .......................15 6.2 Required Information................................................................................ I nformation................................................................................................................................................... ................................................................... 15 6.3 Network Planning.............................................................................. P lanning......................................................................................................................................................... ........................................................................... 16 6.3.1 RF Planning..................................................................................... Plan ning............................................................................................................................................................... .......................................................................... 16 6.3.2 Network Planning...................................................................................................................................................... Planning...................................................................................................................................................... 16 6.3.3 Hardware Planning....................................................................................................................... Planning.................................................................................................................................................... ............................. 16 6.4 Deployment............................................................... Deployment.................................................................................................................................................................. ................................................................................................... 17 6.4.1 Requirements............................................................................................................................................................. Requirements............................................................................................................................................................. 17

Issue 01 (2015-03-23)


ii


Contents

6.4.2 Data Preparation.......................................................................................................................... Preparation........................................................................................................................................................ .............................. 17 6.4.3 Precautions............................................................................................. Precautions.................................................................................................................................................................22 ....................................................................22 6.4.4 Activation................................................................................. Activation.................................................................................................................................................................. ................................................................................. 22 6.4.4.1 Using MML Commands.........................................................................................................................................22 6.4.4.2 MML Command Examples......................................................................................................................... Examples.................................................................................................................................... ........... 23 6.4.4.3 Using the CME....................................................................................................................................................... CME....................................................................................................................................................... 24 6.4.5 Activation Observation..............................................................................................................................................26 6.4.6 Deactivation............................................................................................................................................................... Deactivation...............................................................................................................................................................28 28 6.4.6.1 Using MML Commands.........................................................................................................................................28 6.4.6.2 MML Command Examples......................................................................................................................... Examples.................................................................................................................................... ........... 28 6.4.6.3 Using the CME....................................................................................................................................................... CME....................................................................................................................................................... 28 6.4.7 Reconfiguration........................................................................................................... Reconfiguration......................................................................................................................................................... .............................................. 29 6.5 Performance Monitoring.......................................................................................... Monitoring...............................................................................................................................................29 .....................................................29 6.6 Parameter Optimization................................................................................................................................................ Optimization................................................................................................................................................ 30 6.7 Troubleshooting............................................................................................................................................................ Troubleshooting............................................................................................................................................................ 30

7 Parameters..... Parameters............................ ............................................. ............................................ ............................................ ............................................ .......................................31 .................31 8 Counters.......... Counters................................ ............................................ ............................................ ............................................ ............................................ ...................................... ................ 35 9 Glossary......... Glossary................................ ............................................. ............................................ ............................................ ............................................ .......................................37 .................37 10 Reference Documents.......... Documents................................ ............................................. ............................................. ............................................ .................................. ............ 38

Issue 01 (2015-03-23)


iii


1 About This Document

1

About 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 l

Need to understand the feature described herein 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.

Issue 01 (2015-03-23)

Change Type

Change Description

Parameter Change

Feature change

None

None


1



Change Type

Change Description

Parameter Change

Editorial change

Modified the IDs of the following counters:

None

l

L.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. Added requirements for neighboring cells before None feature deployment. For details, see section 6.4.1 Requirements.

SRAN10.1 Draft B (2015-02-10) This issue includes the following changes.

Change Type

Change Description

Parameter Change

Feature change

Changed the ID of the UL Unified Overload Control Switch parameter from PROCESSSWITCH: ULUNIOLCTRL_SWITCH to ULUOCSwitch and changed the corresponding MO from ECOMMONCTRL to ULUNIOLCTRL . For details, see the following sections:

ULUOCSwitch

Editorial change

l

3.1 Introduction

l

6.4.2 Data Preparation

l

6.4.4 Activation

l

6.4.6 Deactivation

None

None

SRAN10.1 Draft A (2015-01-15) This document is created for SRAN10.1.

Issue 01 (2015-03-23)


2



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 Stations No difference

Function Implementation in Macro, Micro, and LampSite Base Stations No difference

Issue 01 (2015-03-23)


3


2 Overview

2

Overview

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-1 shows how information is exchanged between network elements (NEs).

Issue 01 (2015-03-23)


4


2 Overview

Figure 2-1 Information exchange between NEs

Table 2-1 describes the functions of these NEs involved in this feature. Table 2-1 Functions 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 LTE cells and frequencies reported by the eCoordinator. For specific implementation technologies, see 3 Technical Description.

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, the eCoordinator 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.

eCoordinator

Issue 01 (2015-03-23)


5


Issue 01 (2015-03-23)

2 Overview

NE

Function

eNodeB

l

Periodically reports the heavy-traffic state of LTE cells to the eCoordinator.

l

Adjusts the policies of interoperability between UMTS and LTE networks based on the heavy-traffic state of neighboring UMTS cells and frequencies reported by the eCoordinator. For specific implementation technologies, see 3 Technical Description.


6


3 Technical Description

3

Technical 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 LTE Networks 3.2.1 Determining the Air-Interface Load Status of an LTE Cell by the 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. An LTE cell has two states: heavy-traffic and normal. Figure 3-1 shows how an LTE cell switches between these states.

Issue 01 (2015-03-23)


7



Figure 3-1 State switching of an LTE cell

l

When an LTE cell is in the normal state, if condition 1 is met, the cell enters the heavytraffic 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

Condi tion 2

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 ≥ RrcReqNumHighThd and RRC rejection rate due to resource insufficiency ≥ RrcRejectRateHighThd

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 < RrcReqNumLowThd and RRC rejection rate due to resource insufficiency < RrcRejectRateLowThd

The eNodeB reports the air-interface load status of LTE cells to the eCoordinator every five minutes.

3.2.2 Determining the Air-Interface Load Status of a UMTS Cell by the RNC After this feature is enabled, the RNC periodically determines the air-interface load status of a UMTS cell based on the downlink non-HSPA power load status, actual uplink service load status, and DCH user number load status. A UMTS cell has two states: congested and normal. Figure 3-2 shows how a UMTS cell switches between these states.

Issue 01 (2015-03-23)


8



Figure 3-2 State 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

Condi tion 2

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

Downlink non-HSPA power load status ≥ DLPwrLoadStaForULUniOLC or Actual uplink service load status ≥ ULActulLoadStaForULUniOLC

l

DCH user number load status ≥ DchUserLoadStaForULUniOLC

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

Downlink non-HSPA power load status < DLPwrLoadStaForULUniOLC and Actual uplink service load status < ULActulLoadStaForULUniOLC

l

DCH user number load status < DchUserLoadStaForULUniOLC

NOTE

For descriptions of the downlink non-HSPA power load status, actual uplink service load status, and DCH user number load status, see RAN Load Measurement Feature Parameter Description.

The RNC reports the information about congested UMTS cells to the eCoordinator every five seconds.

3.2.3 Determining the Traffic Status of UMTS/LTE Inter-RAT Neighboring Cells and Frequencies by the eCoordinator Determining the Traffic Status of Inter-RAT Neighboring Cells After this feature is enabled, the eCoordinator performs the following operations: Issue 01 (2015-03-23)


9


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 < UCellCongTimeRateLowThd , the UMTS cell is in the normal state.

b.

The eCoordinator periodically determines the heavy-traffic state of neighboring UMTS cells for LTE cells based on the relationships of neighboring UMTS cells for LTE cells and the heavy-traffic state of UMTS cells.

The eCoordinator periodically (every five minutes) reports the heavy-traffic state of neighboring UMTS cells for LTE cells to the eNodeB, and reports that of neighboring LTE cells for UMTS cells to the RNC.

Determining the Traffic Status of Inter-RAT Neighboring Frequencies 1.

Determining the traffic status of the cells operating in the inter-RAT neighboring frequency The eCoordinator periodically (every 15 minutes) measures the proportion of the duration in which a cell operating in the neighboring frequency is in the heavy-traffic state. Then, the eCoordinator determines whether the cell is in the heavy-traffic or normal state according to the following rules:

2.

–

If the proportion of the duration in which a cell is in the heavy-traffic state ≥ ULUOCTimeRateHighThd , the eCoordinator regards the cell as a heavy-traffic cell when determining the traffic status of the inter-RAT neighboring frequency for UMTS and LTE cells.

–

If the proportion of the duration in which a cell is in the heavy-traffic state < ULUOCTimeRateLowThd , the eCoordinator regards the cell as a normal cell when determining the traffic status of the inter-RAT neighboring frequency for UMTS and LTE cells.

Determining the traffic status of the inter-RAT neighboring frequency

–

If an overlapping neighboring UMTS/LTE cell or a neighboring UMTS/LTE cell for blind handover is configured in a neighboring UMTS/LTE frequency, and if the cell is in the heavy-traffic state, the neighboring frequency is considered to be in the heavy-traffic state.

–

If an overlapping neighboring UMTS/LTE cell or a neighboring UMTS/LTE cell for blind handover is not configured in a neighboring UMTS/LTE frequency, and if all the neighboring UMTS and LTE cells operating in this frequency are in the heavytraffic state, this frequency is considered to be in the heavy-traffic state.

The eCoordinator periodically reports the neighboring UMTS frequency of heavy-traffic LTE cells to the eNodeB and reports the neighboring LTE frequency of heavy-traffic UMTS cells to the RNC. Issue 01 (2015-03-23)


10



3.3 Adjusting the Policies of Interoperability Between UMTS and LTE Networks 3.3.1 Adjusting the Policies of Interoperability from LTE to UMTS This feature adjusts the inter-RAT handover (indicated by the features below) from LTE to UMTS as follows: l

LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN, LOFD-001072 Distance based inter-RAT handover to UTRAN, and UL-Quality-based Inter-RAT Handover to UTRAN The system groups cells and frequencies depending on whether they are under heavy traffic and preferentially selects the cells and frequencies in the non-heavy-traffic group as the target cell and frequency. For details, see eRAN Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

l

LOFD-001043 Service based inter-RAT handover to UTRAN

–

A heavy-traffic neighboring UMTS cell is not used as the target cell for handover.

–

A heavy-traffic neighboring UMTS frequency is not used as the target frequency for redirection.

For details about the LOFD-001043 Service based inter-RAT handover to UTRAN feature, see eRAN Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

3.3.2 Adjusting the Policies of Interoperability from UMTS to LTE Adjusting the Policies of Handover and Redirection from UMTS to LTE This feature adjusts the following UMTS-to-LTE handover and redirection features: l

WRFD-150220 Coverage Based PS Handover from UMTS to LTE and WRFD-150219 Coverage Based PS Redirection from UMTS to LTE The system groups cells and frequencies depending on whether they are under heavy traffic and preferentially selects the cells and frequencies in the non-heavy-traffic group as the target cell and frequency.

l

l

Issue 01 (2015-03-23)

WRFD-140218 Service-Based PS Handover from UMTS to LTE, WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE, WRFD-150217 Load Based PS Handover from UMTS to LTE, and WRFD-150216 Load Based PS Redirection from UMTS to LTE

–

A heavy-traffic neighboring LTE cell is not used as the target cell for handover.

–

A heavy-traffic neighboring LTE frequency is not used as the target frequency for redirection.

WRFD-140226 Fast Return from UMTS to LTE and WRFD-171223 Fast Return to LTE for SRVCC User Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

11



A heavy-traffic neighboring LTE frequency is not used as the target frequency for redirection. NOTE

For details about the policies of interoperability from UMTS to LTE, see RAN Interoperability Between UMTS and LTE Feature Parameter Description.

Adjusting the Policies of Reselection from UMTS to LTE Based on the heavy-traffic state of neighboring LTE frequencies for UMTS cells reported by the eCoordinator, the RNC adjusts the EQrxlevmin and EQqualmin thresholds in SIB19 as follows, so that it is difficult for UEs to reselect heavy-traffic neighboring LTE frequencies: l

EQrxlevmin _after adjustment = MAX( EQrxlevmin, EQrxlevmin + EQrxlevminOffset )

l

EQqualmin _after adjustment = MAX( EQqualmin, EQqualmin + EQqualminOffset )

When receiving from the eCoordinator the information that the status of neighboring LTE frequencies for UMTS cells changes from heavy-traffic to normal, the RNC periodically (every 15 minutes) adjusts the previous thresholds in SIB19 as follows: l

EQrxlevmin _after adjustment = MAX( EQrxlevmin, EQrxlevmin + EQrxlevminOffset - N x EQrxlevminStep)

l

EQqualmin _after adjustment = MAX( EQqualmin, EQqualmin + EQqualminOffset - N x EQqualminStep), where N indicates the number of periods.

When the EQrxlevmin and EQqualmin return to default values, the adjustment of these two thresholds stops in SIB19, as shown in Figure 3-3. The following figure uses the EQrxlevmin as an example. Figure 3-3 Adjustment of the EQrxlevmin

NOTE

For details about the policies of reselection from UMTS to LTE, see Interoperability Between UMTS and LTE Feature Parameter Description.

Issue 01 (2015-03-23)


12


4 Related Features

4

Related Features

Prerequisite Features None

Mutually Exclusive Features None

Impacted Features l

l

l

This feature affects the target LTE cell and frequency selection during handover and redirection involved in the following features:

–

WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE

–

WRFD-140218 Service-Based PS Handover from UMTS to LTE

–

WRFD-150219 Coverage Based PS Redirection from UMTS to LTE

–

WRFD-150220 Coverage Based PS Handover from UMTS to LTE

–

WRFD-150216 Load Based PS Redirection from UMTS to LTE

–

WRFD-150217 Load Based PS Handover from UMTS to LTE

This feature affects the target LTE frequency selection during redirection involved in the following features:

–

WRFD-140226 Fast Return from UMTS to LTE

–

WRFD-171223 Fast Return to LTE for SRVCC User

This feature affects the target UMTS cell and frequency selection during handover and redirection involved in the following features:

–

LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN

–

LOFD-001043 Service based inter-RAT handover to UTRAN

–

LOFD-001072 Distance based Inter-RAT handover to UTRAN

–

UL-quality-based inter-RAT handover to UTRAN or GERAN

For details about the impact, see 3.3 Adjusting the Policies of Interoperability Between UMTS and LTE Networks .

Issue 01 (2015-03-23)


13


5 Network Impact

5

Network Impact

System Capacity No impact.

Network Performance 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.

Issue 01 (2015-03-23)


14


6 Engineering Guidelines

6

Engineering Guidelines

6.1 When to Use UL Unified Overload Control This feature is recommended when traffic is constantly heavy on co-coverage UMTS and LTE networks in scenarios such as sporting events, concerts, and big festivals.

6.2 Required Information Obtain the values of the performance counters or KPIs listed in Table 6-1 to help determine the configuration of heavy traffic-related parameter thresholds for UMTS and LTE cells according to the actual situation of the live network and to evaluate feature gains. Table 6-1 Performance counters or KPIs whose values need to be obtained before feature deployment

Issue 01 (2015-03-23)

Counter ID

Counter Name

Counter Description

Mo de

15267273 78

L.Traffic.User.Avg

Average number of users in a cell

LTE

15267266 58

L.RRC.ConnReq.Att

Number of RRC connection setup requests (retransmission excluded)

15267299 49

L.RRC.SetupFail.ResFail.UserS pec

Number of RRC connection setup failures because of limitation of UE number specification

15267284 86

L.RRC.SetupFail.ResFail.PUCC Number of RRC connection setup failures due to PUCCH resource H allocation failure

15267284 85

L.RRC.SetupFail.ResFail.SRS

Number of RRC connection setup failures due to SRS resource allocation failure


15



Counter ID

Counter Name

Counter Description

15267284 90

L.RRC.SetupFail.Rej.FlowCtrl

Number of times the eNodeB sends an RRC Connection Reject message to the UE due to flow control

-

Inter-RAT Handover Out Success Rate (LTE to WCDMA)

Success rate of outgoing interRAT 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

73410510

VS.CellDCHUEs

Number of UEs in CELL_DCH State for Cell

67193610

VS.RRC.Rej.DLPower.Cong

Number of RRC Connection Rejects for Cell (DL Power Congestion)

67193609

VS.RRC.Rej.ULPower.Cong

Number of RRC Connection Rejects for Cell (UL Power Congestion)

73423414

VS.U2LTEHO.FailRelocPrepOu tPS.NoResAvail

Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (No Resource Available)

Mo de

UM TS

6.3 Network Planning 6.3.1 RF Planning None

6.3.2 Network Planning Co-coverage UMTS and LTE networks are required.

6.3.3 Hardware Planning The UL Unified Overload Control feature has the following requirements for hardware planning: l

The eCoordinator must be deployed.

l

UMTS and LTE radio network devices must all be provided by Huawei and connect to the same eCoordinator.

Issue 01 (2015-03-23)


16



6.4 Deployment 6.4.1 Requirements Other Features For details, see 4 Related Features.

Hardware The eCoordinator must be deployed.

License Feature ID

Feature Name

License Control Item ID

License Control Item

NE

Sales Unit

MRFD-10140 2

UL Unified Overload Control

LEC2ULU VS01

UL Unified Overload Control

eCoordinator

Per cell

Other Requirements l

The eNodeB and eCoordinator must be time-synchronized.

l

The neighboring LTE cells of the UMTS cell must be configured. For details, see BSC6910 UMTS Initial Configuration Guide in BSC6910 UMTS Product Documentation and BSC6900 UMTS Initial Configuration Guide in BSC6900 UMTS Product Documentation.

l

The neighboring UMTS cells of the LTE cell must be configured. For details, see Inter RAT Mobility Management in Connected Mode Feature Parameter Description in eRAN Feature Documentation and in eRAN TDD Feature Documentation.

6.4.2 Data Preparation Table 6-2 eCoordinator data preparation

Issue 01 (2015-03-23)

MO

Param eter Name

Param eter ID

Setting Notes

Data Source

ULUN IOLC TRLL CELL

Cell Index Type

Query CellId Type

Set this parameter to the cell index type of the LTE cell to be enabled with this feature.

Networ k plan


17


MO

ULUN IOLC TRLU CELL

ULUN IOLC TRL

Issue 01 (2015-03-23)

Param eter Name

Param eter ID


Setting Notes

Data Source

Mobile MCC Country Code

Set this parameter to the MCC of the LTE cell to be enabled with this feature.

Networ k plan

Mobile MNC Networ k Code

Set this parameter to the MNC of the LTE cell to be enabled with this feature.

Networ k plan

eNodeB eNode ID BId

Set this parameter to the eNodeB ID of the LTE cell to be enabled with this feature.

Networ k plan

Cell ID CellId

Set this parameter to the cell ID of the LTE cell to be enabled with this feature.

Networ k plan

Cell Index Type

Set this parameter to the cell index type of the UMTS cell to be enabled with this feature.

Networ k plan

Mobile MCC Country Code

Set this parameter to the MCC of the UMTS cell to be enabled with this feature.

Networ k plan

Mobile MNC Networ k Code

Set this parameter to the MNC of the UMTS cell to be enabled with this feature.

Networ k plan

RNC ID LogicR ncId

Set this parameter to the RNC ID of the UMTS cell to be enabled with this feature.

Networ k plan

Cell ID CellId

Set this parameter to the cell ID of the UMTS cell to be enabled with this feature.

Networ k plan

UL Unified Overloa d Control Switch

ULUO CSwitc h

Set this switch to ON for UMTS and LTE cells that are enabled with this feature.

Networ k plan

Low Thld for UL Overloa d Control Time Rate

ULUO CTime RateLo wThd

If this parameter is set to a smaller value, the duration during which this feature is effective is longer.

Networ k plan

Query CellId Type

If this parameter is set to a larger value, the duration during which this feature is effective is shorter. The feature gains cannot be obtained in this case. ULUOCTimeRateLowThd must be less than ULUOCTimeRateHighThd .


18


MO


Param eter Name

Param eter ID

Setting Notes

Data Source

High Thld for UL Overloa d Control Time Rate

ULUO CTime RateHi ghThd

If this parameter is set to a larger value, this feature is less likely to be triggered when the cell is overloaded. The feature gains cannot be obtained in this case.

Networ k plan

Low Thld for UMTS Cell Congest ion Time Rate

UCellC ongTi meRat eLowT hd

High Thld for UMTS Cell Congest ion Time Rate

UCellC ongTi meRat eHigh Thd

If this parameter is set to a smaller value, this feature is more likely to be triggered when the cell is overloaded. ULUOCTimeRateHighThd must be greater than ULUOCTimeRateLowThd .


Networ k plan

If this parameter is set to a larger value, the duration during which this feature is effective is shorter. The feature gains cannot be obtained in this case. UCellCongTimeRateLowThd must be less than UCellCongTimeRateHighThd .

If this parameter is set to a larger value, this feature is less likely to be triggered when the UMTS cell is overloaded. The feature gains cannot be obtained in this case.

Networ k plan

If this parameter is set to a smaller value, this feature is more likely to be triggered when the UMTS cell is overloaded. UCellCongTimeRateHighThd must be greater than UCellCongTimeRateLowThd .

Table 6-3 eNodeB data preparation

M O

Paramete r Name

Cell High UE UL Number Uni Thd for fied UL UniOLC OL C

Issue 01 (2015-03-23)

Param eter ID

Setting Notes

Data Source

UeNu mHigh Thd

If this parameter is set to a large value, this feature may not be triggered when the cell is overloaded.

Networ k plan

If this parameter is set to a smaller value, this feature is more likely to be triggered.


19


M O

Issue 01 (2015-03-23)


Paramete r Name

Param eter ID

Setting Notes

Data Source

Low UE Number Thd for UL UniOLC

UeNu mLow Thd


Networ k plan

High RRC Reject Rate Thd for UL Uni-OLC

RrcRej ectRate HighT hd


Low RRC Reject Rate Thd for UL Uni-OLC

RrcRej ectRate LowTh d


High RRC Request Number Thd for UL UniOLC

RrcRe qNum HighT hd


Low RRC Request Number Thd for UL UniOLC

RrcRe qNum LowTh d


If this parameter is set to a larger value, this feature may become ineffective when the cell is overloaded. Networ k plan

If this parameter is set to a smaller value, this feature is more likely to be triggered. Networ k plan

If this parameter is set to a larger value, this feature may become ineffective when the cell is overloaded. Networ k plan

If this parameter is set to a smaller value, this feature is more likely to be triggered. Networ k plan

If this parameter is set to a larger value, this feature may become ineffective when the cell is overloaded.


20



Table 6-4 RNC data preparation

M O

Paramete r Name

Param eter ID

Setting Notes

Data Source

UC EL LL DM

DL Power Load Congest Thld for UL Unified OLC

DLPwr LoadSt aForU LUniO LC

If this parameter is set to a smaller value, the initial state is less congested and the downlink power load is more likely to become congested. In this case, the air interface load of a cell is more likely to become congested. If this parameter is set to a larger value, the initial state is more congested and the downlink power load is less likely to become congested. In this case, the air interface load of a cell is less likely to become congested.

Networ k plan

UL Actual Load Congest Thld for UL Unified OLC

ULAct ulLoad StaFor ULUni OLC

If this parameter is set to a smaller value, the initial state is less congested and the uplink actual load is more likely to become congested. In this case, the air interface load of a cell is more likely to become congested.

Networ k plan

UC EL LN FR EQ PRI OI NF O

Issue 01 (2015-03-23)

If this parameter is set to a larger value, the initial state is more congested and the uplink actual load is less likely to become congested. In this case, the air interface load of a cell is less likely to become congested.

DCH User DchUs erLoad Number Congest StaFor ULUni Thld for UL OLC Unified OLC

If this parameter is set to a smaller value, the initial state is less congested and the DCH user number is more likely to become congested. In this case, the air interface load of a cell is more likely to become congested.

Networ k plan

Offset to E-UTRA RSRP Thld

EQrxle vminO ffset

If this parameter is set to a smaller value, UEs are Networ more likely to reselect the cells operating in this k plan frequency. Setting this parameter to a too small value may cause UEs to reselect LTE cells still when this feature takes effect, which has a load impact on the LTE network.

Offset to E-UTRA RSRQ Thld

EQqua lminOf fset

If this parameter is set to a smaller value, UEs are Networ more likely to reselect the cells operating in this k plan frequency. Setting this parameter to a too small value may cause UEs to reselect LTE cells still when this feature takes effect, which has a load impact on the LTE network.

If this parameter is set to a larger value, the initial state is more congested and the DCH user number is less likely to become congested. In this case, the air interface load of a cell is less likely to become congested.


21


M O

Paramete r Name

UC OR RM AL GO SW ITC H

Setting Notes

Data Source

Adjustmen EQrxle vminSt t Step for ep E-UTRA RSRP Thld

If this parameter is set to a larger value, the minimum access level threshold of the cells that operate in the target frequency is more quickly adjusted and UEs are more likely to reselect the cells operating in this frequency when this feature becomes ineffective. Setting this parameter to a too large value may cause a large number of UEs to reselect LTE cells, which has a load impact on the LTE network.

Networ k plan

Adjustmen EQqua lminSt t Step for ep E-UTRA RSRQ Thld

If this parameter is set to a larger value, the minimum access level threshold of the cells that operate in the target frequency is more quickly adjusted and UEs are more likely to reselect the cells operating in this frequency when this feature becomes ineffective. Setting this parameter to a too large value may cause a large number of UEs to reselect LTE cells, which has a load impact on the LTE network.

Networ k plan

UL Unified Overload Control Switch

Param eter ID


HoSwit Set this parameter to ON in order to enable the ch2: UL Unified Overload Control feature. HO_U L_UO LC_S WITC H

Networ k plan

6.4.3 Precautions None

6.4.4 Activation 6.4.4.1 Using MML Commands Run the following MML commands on the eNodeB, RNC, and eCoordinator: l

eNodeB Run the MML command MOD CELLULUNIFIEDOLC to set the following parameters:

Issue 01 (2015-03-23)

–

High UE Number Thd for UL Uni-OLC

–

Low UE Number Thd for UL Uni-OLC

–

High RRC Reject Rate Thd for UL Uni-OLC(%) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

22


l

l

–

Low RRC Reject Rate Thd for UL Uni-OLC(%)

–

High RRC Request Number Thd for UL Uni-OLC

–

Low RRC Request Number Thd for UL Uni-OLC


RNC a.

Run the MML command ADD UCELLLDM to set the following parameters: DL Power Load Congest Thld for UL Unified OLC , UL Actual Load Congest Thld for UL Unified OLC, and DCH User Number Congest Thld for UL Unified OLC

b.

Run the MML command ADD UCELLNFREQPRIOINFO to set the following parameters: Offset to E-UTRA RSRP Thld, Offset to E-UTRA RSRQ Thld, Adjustment Step for E-UTRA RSRP Thld , and Adjustment Step for E-UTRA RSRQ Thld

c.

Run the MML command SET UCORRMALGOSWITCH to select the HO_UL_UOLC_SWITCH check box under the HoSwitch2 parameter.

eCoordinator a.

Add LTE cells for UL Unified Overload Control. Run the MML command ADD ULUNIOLCTRLLCELL to set the following parameters: Cell Index Type, Mobile Country Code, Mobile Network Code, eNodeB ID, and Cell ID

b.

Add UMTS cells for UL Unified Overload Control. Run the MML command ADD ULUNIOLCTRLUCELL to set the following parameters: Cell Index Type, Mobile Country Code, Mobile Network Code, RNC ID, and Cell ID

c.

Run the MML command SET ULUNIOLCTRL to turn on the UL Unified Overload Control Switch and set the following parameters: Low Thld for UL Overload Control Time Rate, High Thld for UL Overload Control Time Rate, Low Thld for UMTS Cell Congestion Time Rate, and High Thld for UMTS Cell Congestion Time Rate

6.4.4.2 MML Command Examples //Setting UL Unified Overload Control-related threshold parameters on the eNodeB MOD CellULUnifiedOLC: LocalCellId=0, UeNumHighThd=400, UeNumLowThd=300, RrcRejectRateHighThd=2000, RrcRejectRateLowThd=1000, RrcReqNumHighThd=50, RrcReqNumLowThd=10; //Setting UL Unified Overload Control-related threshold parameters on the RNC ADD UCELLLDM: CELLID=1, DLPwrLoadStaForULUniOLC=DL_HEAVY_STATE, ULActulLoadStaForULUniOLC=UL_HEAVY_STATE, DchUserLoadStaForULUniOLC=DCHUSER_HEAVY_STATE; ADD UCELLNFREQPRIOINFO: CELLID=1, EQrxlevminOffset=40, EQqualminOffset=20, EQrxlevminStep=10, EQqualminStep=5; //Turning on the UL Unified Overload Control Switch on the RNC SET UCORRMALGOSWITCH: HoSwitch2=HO_UL_UOLC_SWITCH-1; //Turning on the UL Unified Overload Control Switch and setting parameters related to UL Unified Overload Control on the eCoordinator ADD ULUNIOLCTRLLCELL: QueryCellIdType=BYCGI, MCC="454", MNC="06", eNodeBId=30019, CellId=1; ADD ULUNIOLCTRLUCELL: QueryCellIdType=BYCGI, MCC="460", MNC="04", LogicRncId=12, CellId=1; SET ULUNIOLCTRL: ULUOCSwitch=ON, ULUOCTimeRateLowThd=70, ULUOCTimeRateHighThd=10, UCellCongTimeRateLowThd=70, UCellCongTimeRateHighThd=50;

Issue 01 (2015-03-23)


23



6.4.4.3 Using the CME Method 1 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 6.4.2 Data Preparation. 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-5 Configuring parameters on the CME

Issue 01 (2015-03-23)

SN

MO

NE

Parameter Name

Parameter ID

Configurabl e in CME Batch Modificatio n Center

1

CellULUnifi edOLC

eNodeB

High UE Number Thd for UL UniOLC

UeNumHigh Thd

Yes

Low UE Number Thd for UL UniOLC

UeNumHigh Thd

Yes

High RRC Reject Rate Thd for UL Uni-OLC

RrcRejectRat Yes eHighThd

Low RRC Reject Rate Thd for UL Uni-OLC

RrcRejectRat eLowThd

High RRC Request Number Thd for UL Uni-OLC

RrcReqNum HighThd

Yes

Low RRC Request Number Thd for UL Uni-OLC

RrcReqNum LowThd

Yes


24



SN

MO

NE

Parameter Name

Parameter ID


2

UCELLLD M

RNC

DL Power Load Congest Thld for UL Unified OLC

DLPwrLoad StaForULUn iOLC

Yes

UL Actual Load Congest Thld for UL Unified OLC

Yes ULActulLoa dStaForULU niOLC

DCH User Number Congest Thld for UL Unified OLC

DchUserLoa Yes dStaForULU niOLC

Offset to E-UTRA RSRP Thld

EQrxlevmin Offset

Yes

Offset to E-UTRA RSRQ Thld

EQqualminO ffset

Yes

3

UCELLNF REQPRIOI NFO

RNC

Adjustment Step for EQrxlevminS Yes E-UTRA RSRP Thld tep Adjustment Step for E-UTRA RSRQ Thld

EQqualminS tep

Yes

HoSwitch2: HO_UL_UO LC_SWITC H

Yes

QueryCellId Type

Yes

Mobile Country Code

MCC

Yes

Mobile Network Code

MNC

Yes

4

UCORRMA LGOSWIT CH

RNC


5

ULUNIOLC TRLLCEL L

eCoordina tor

Cell Index Type

eNodeB ID

eNodeBId

Yes

CellId

Yes

QueryCellId Type

Yes

Mobile Country Code

MCC

Yes

Mobile Network Code

MNC

Yes

Cell ID 6

Issue 01 (2015-03-23)

ULUNIOLC TRLUCEL L

eCoordina tor

Cell Index Type


25


SN

7

MO

NE

ULUNIOLC TRL

eCoordina tor


Parameter Name

Parameter ID


RNC ID

LogicRncId

Yes

Cell ID

CellId

Yes


ULUOCSwit ch

Yes

Low Thld for UL Overload Control Time Rate

ULUOCTime RateLowThd

Yes

High Thld for UL Overload Control Time Rate

ULUOCTime RateHighTh d

Yes

Low Thld for UMTS Cell Congestion Time Rate

UCellCongTi meRateLowT hd

Yes

High Thld for UMTS Cell Congestion Time Rate

UCellCongTi meRateHigh Thd

Yes

----End

Method 2 This feature can be batch activated using the CME. For detailed operations, see the following section in the CME product documentation or online help: Managing the CME > CME Guidelines > 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.

Issue 01 (2015-03-23)


26



Table 6-6 eCoordinator counters

Counter ID

Counter Name

Counter Description

73430335

VS.ELTECELL.ULUOC.Ov Number of Times an LTE erload.Num 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 Frequency for a UMTS Cell Changes

Tracing Messages On the LMT, if you observe Se and Sr messages as listed in Table 6-7 and Table 6-8, this feature has taken effect. Table 6-7 Messages 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-8 Messages between the eCoordinator and the RNC

Issue 01 (2015-03-23)

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


27



6.4.6 Deactivation 6.4.6.1 Using MML Commands eCoordinator

l

Run the MML command SET ULUNIOLCTRL to set the UL Unified Overload Control Switch to OFF. RNC

l

Run the MML command SET UCORRMALGOSWITCH to deselect the HO_UL_UOLC_SWITCH check box under the HoSwitch2 parameter.

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 Operati on 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-9 Configuring parameters on the CME

Issue 01 (2015-03-23)

SN

MO

NE

Parame ter Name

Parameter ID


1

UCORRMALGO SWITCH

RNC


HoSwitch2: HO_UL_UOL C_SWITCH

Yes


28



SN

MO

NE

Parame ter Name

Parameter ID


2

ULUNIOLCTRL

eCoordinator


ULUOCSwitch

Yes

----End

6.4.7 Reconfiguration None

6.5 Performance Monitoring Feature gains can be monitored by the KPIs listed in Table 6-10 or 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-11 decrease. Table 6-10 eNodeB 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-11 RNC performance counters

Issue 01 (2015-03-23)

Counter ID

Counter Name

73423414

VS.U2LTEHO.FailRelocPr Number of Failed epOutPS.NoResAvail Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (No Resource Available)


Counter Description

29



6.6 Parameter Optimization l

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-OLC parameter (ID: UeNumHighThd ). However, the value of this parameter cannot be less than that of the UeNumLowThd parameter.

–

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 the RrcReqNumLowThd parameter.

–

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 the RrcRejectRateLowThd parameter.

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

Issue 01 (2015-03-23)


30


7 Parameters

7

Parameters

Table 7-1 Parameters

MO

Parame ter ID

MML Feature Comma ID nd

Feature Name

Description

CellUL Unified OLC

RrcReq NumHig hThd

MOD CELLU LUNIFI EDOLC

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-insufficiencyinduced RRC connection rejection rate is greater than the RrcRejectRateHighThd parameter value.

LST CELLU LUNIFI EDOLC

MRFD101402

GUI Value Range: 1~20000 Unit: None Actual Value Range: 1~20000 Default Value: 2000

Issue 01 (2015-03-23)


31


7 Parameters

MO

Parame ter ID


Feature Name

Description

CellUL Unified OLC

RrcReje ctRateHi ghThd



Meaning: Indicates the threshold of the resourceinsufficiency-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-insufficiencyinduced 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).

MRFD101402


GUI Value Range: 0~200 Unit: % Actual Value Range: 0~200 Default Value: 50 CellUL Unified OLC

RrcReq NumLo wThd

MOD CELLU LUNIFI EDOLC LST CELLU LUNIFI EDOLC

MRFD101402


Meaning: Indicates the threshold of the RRC connection setup request number, 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. GUI Value Range: 1~20000 Unit: None Actual Value Range: 1~20000 Default Value: 1000

Issue 01 (2015-03-23)


32


7 Parameters

MO

Parame ter ID


Feature Name

Description

CellUL Unified OLC

RrcReje ctRateL owThd



Meaning: Indicates the threshold of the resourceinsufficiency-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 resourceinsufficiency-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 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).

MRFD101402


GUI Value Range: 0~200 Unit: % Actual Value Range: 0~200 Default Value: 10 CellUL Unified OLC

UeNum HighTh d

MOD CELLU LUNIFI EDOLC LST CELLU LUNIFI EDOLC

MRFD101402


Meaning: Indicates the RRC_CONNECTED UE number threshold used to determine whether to start UMTS and LTE unified overload control. UMTS and LTE unified overload control starts when the number of RRC_CONNECTED UEs is greater than this parameter value. GUI Value Range: 1~1200 Unit: None Actual Value Range: 1~1200 Default Value: 400

Issue 01 (2015-03-23)


33


7 Parameters

MO

Parame ter ID


Feature Name

Description

CellUL Unified OLC

UeNum LowThd



Meaning: Indicates the threshold of the RRC_CONNECTED UE number, 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.


MRFD101402

GUI Value Range: 1~1200 Unit: None Actual Value Range: 1~1200 Default Value: 250

Issue 01 (2015-03-23)


34


8 Counters

8

Counters

Table 8-1 Counters

Counter ID

Counter Name

Counter Description

1526726658

L.RRC.ConnReq.At Number of RRC t connection setup requests (retransmission excluded)

Feature ID

Feature Name

Multi-mode: None

RRC Connection Management

GSM: None UMTS: None LTE: LBFD-002007


TDLBFD-002007 1526727378

L.Traffic.User.Avg

Average number of users in a cell

Multi-mode: None GSM: None UMTS: None LTE: LBFD-002007

RRC Connection Management RRC Connection Management

TDLBFD-002007 1526728485

L.RRC.SetupFail.R Number of RRC esFail.SRS connection setup failures due to SRS resource allocation failure



TDLBFD-002007 1526728486

L.RRC.SetupFail.R Number of RRC esFail.PUCCH connection setup failures due to PUCCH resource allocation failure



TDLBFD-002007

Issue 01 (2015-03-23)


35


8 Counters

Counter ID

Counter Name

Counter Description

1526728490

L.RRC.SetupFail.R Number of times ej.FlowCtrl the eNodeB sends an RRC Connection Reject message to the UE due to flow control

Feature ID

Feature Name

Multi-mode: None


GSM: None UMTS: None LTE: LBFD-002007


TDLBFD-002007 1526729949

L.RRC.SetupFail.R Number of RRC esFail.UserSpec connection setup failures because of limitation of UE number specification



TDLBFD-002007

Issue 01 (2015-03-23)


36


9 Glossary

9

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2015-03-23)


37

UL Unified Overload Control(SRAN10.1_01)

Recommend Documents