e2e flow control(ran13.0_02)

E2E Flow Control RAN13.0

Feature Parameter Description

Issue 02

Date 2012-05-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

WCDMA RAN

E2E Flow Control Contents

Issue 02 (2012-05-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

i

Contents

1 Introduction ................................................................................................................................ 1-1

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

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

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

2 Overview ..................................................................................................................................... 2-1

3 E2E Flow Control ...................................................................................................................... 3-1

3.1 E2E Flow Control Phase 1 ............................................................................................................ 3-1


3.3 Overload Indication ....................................................................................................................... 3-4

4 Engineering Guidelines ........................................................................................................... 4-1


4.1.1 Configuration Suggestions for E2E Flow Control Phase 1 ................................................... 4-1

4.1.2 Recommended Parameter Settings ..................................................................................... 4-1

4.1.3 Key Parameter Settings........................................................................................................ 4-1


4.2.1 Configuration Suggestions for E2E Flow Control Phase 2 ................................................... 4-1

4.2.2 Recommended Parameter Settings ..................................................................................... 4-1

5 Parameters ................................................................................................................................. 5-1

6 Counters ...................................................................................................................................... 6-1

7 Glossary ...................................................................................................................................... 7-1

8 Reference Documents ............................................................................................................. 8-1

WCDMA RAN

E2E Flow Control 1 Introduction



1-1

1 Introduction

1.1 Scope

This document describes the principles of end-to-end (E2E) Flow Control. The RNC and NodeB cooperate to implement E2E Flow Control, protecting themselves from being overloaded.

If you need specific overload control measures for mass gathering events, contact Huawei’s professional service teams for tailor-made solutions.

1.2 Intended Audience

This document is intended for:

Personnel who have a good understanding of WCDMA principles

Personnel who need to learn about E2E Flow Control

Personnel who work on Huawei products

1.3 Change History

This section describes the change history of this document. There are two types of changes:

Feature change: refers to a change in the E2E Flow Control feature of a specific product version.

Editorial change: refers to a change in wording or the addition of the information that was not described in the earlier version.

Document Issues

The issues of this document are as follows:

02 (2012-05-30)

01 (2011-10-30)

02 (2012-05-30)

This is the second commercial release of the document for RAN13.0.

Compared with 01 (2011-10-30) of RAN13.0, this issue incorporates the changes described in the following table.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Corrected the switch for enabling the E2E flow control phase 1 .The switch is now RSVDBIT1_BIT31-0 under RsvdPara1, instead of RSVDBIT1_BIT5-1&RSVDBIT1_BIT31-0 under RsvdPara1. For details, see section 3.1 "E2E Flow Control Phase 1."

None

01 (2011-10-30)

This is a new document.

../RNCParaHtml/mbsc/m-para/urrctrlswitch_rsvdpara1.html


WCDMA RAN

E2E Flow Control 2 Overview



2-1

2 Overview

E2e Flow Control protects network elements (NEs) in a radio access network (RAN) from being overloaded. The NEs that participate in flow control are the RNC and NodeB.

Before E2E Flow Control is introduced, the RNC is unaware of whether the NodeB CPU, including the CPU of the baseband and WMPT, is congested or overloaded. Therefore, the RNC continues to admit a large number of RRC CONNECTION REQUEST messages and send RADIO LINK SETUP REQUEST messages to the NodeB over the Iub interface even when the NodeB is congested or overloaded. In this case, the NodeB should reject or discard these RADIO LINK SETUP REQUEST messages, which lower the cell resource utilization. In addition, the access of high-priority services cannot be guaranteed because the NodeB is unaware of the service priority of each message. To address these issues, Huawei has introduced E2E Flow Control Phase 1 and E2E Flow Control Phase 2. E2e Flow Control limits the traffic flow that enters NEs and therefore ensures the stable operation of NEs when these NEs are overloaded. For details about other flow control measures, such as flow control for overloaded RNC units, see the Flow Control Feature Parameter Description. Compared with flow control performed on a single NE, E2E Flow Control has the following benefits:

More reference information is provided for flow control because of cooperation between NEs. For example, if the RNC provides service priority information for the NodeB, the NodeB can implement differentiated flow control based on service priorities to preferentially ensure the access of high-priority services.

Better flow control effects can be achieved because of cooperation between NEs. In E2E Flow Control Phase 2, the RNC performs flow control on RRC CONNECTION REQUEST messages, and the NodeB performs flow control on RADIO LINK SETUP REQUEST messages. Consequently, if the NodeB is overloaded, the RNC reduces the number of unnecessary RRC CONNECTION REQUEST messages to be processed. This action reduces the NodeB Application Part (NBAP) signaling traffic on the Iub interface, increasing resources available to admitted UEs and RAN resource utilization.

Flow%20Control.htm

WCDMA RAN

E2E Flow Control 3 E2E Flow Control



3-1

3 E2E Flow Control

3.1 E2E Flow Control Phase 1

In E2E Flow Control Phase 1, RADIO LINK SETUP REQUEST messages sent by the RNC to the NodeB are categorized by service priority. The NodeB performs flow control based on service priorities to reduce the NodeB CPU load and ensures preferential access of high-priority services.

E2E Flow Control Phase 1 is based on service priorities. It enables a consistent flow control policy between the NodeB and RNC, achieving E2E Flow Control. Figure 3-1 shows E2E Flow Control Phase 1 used in the RRC connection setup procedure.

Figure 3-1 E2E Flow Control Phase 1 used in the RRC connection setup procedure

The procedure for E2E Flow Control Phase 1 is as follows:

1. The UE sends an RRC CONNECTION REQUEST message to the RNC. This message contains information identifying the service initiating the RRC connection request.

2. The RNC sends a RADIO LINK SETUP REQUEST message to the NodeB. This message contains the service priority.

3. Upon receiving the RADIO LINK SETUP REQUEST message, the NodeB checks the CPU load. If the NodeB is overloaded, it rejects or discards the RADIO LINK SETUP REQUEST message based on the service priority instead of blindly discarding this request.

The NodeB makes flow control decisions on RADIO LINK SETUP REQUEST messages from different services based on three thresholds: allowed flow control threshold, preferential flow control threshold, and absolute guaranteed threshold.

Allowed flow control threshold: threshold for starting flow control on real-time services (conversational and streaming services)

WCDMA RAN




3-2

Preferential flow control threshold: threshold for starting flow control on low-priority non-real-time services (background and interactive services)

Absolute guaranteed threshold: threshold for starting flow control on emergency calls

Table 3-1 describes the flow control policies of different services.

Table 3-1 Flow control policies for different services

If... Then...

Allowed flow control threshold > CPU load ≥ Preferential flow control threshold

The NodeB rejects the RADIO LINK SETUP REQUEST messages of BE services (background and interactive services). Then, the procedure continues on to 4.

Absolute guaranteed threshold > CPU load ≥ Allowed flow control threshold

The NodeB rejects the RADIO LINK SETUP REQUEST messages of all services (BE, conversational, and streaming services) except those of emergency calls. Then, the procedure continues on to 4.

CPU load > Absolute guaranteed threshold

The NodeB discards the RADIO LINK SETUP REQUEST messages of all services.

If the CPU load is normal, the NodeB proceeds with the normal radio link setup procedure.

4. If the RADIO LINK SETUP REQUEST message is rejected or discarded due to flow control, the NodeB sends the RNC a RADIO LINK SETUP FAILURE message with the cause value of Control processing overload.

5. The RNC sends the UE an RRC CONNECTION REJECT message, which contains the information element (IE) wait time.

Upon receipt of this message, the UE waits for the period of time specified by the IE wait time and retransmits the RRC CONNECTION REQUEST message. This prevents frequent RRC connection setup attempts and reduces the network load. E2E Flow Control requires the UE to support the processing associated with the IE wait time. For details about the wait time, see the Flow Control Feature Parameter Description.

In other procedures, for example, in a CELL_FACH-to-CELL_DCH state transition procedure, the RNC also sends the NodeB a RADIO LINK SETUP REQUEST message, which carries the service priority. If the NodeB CPU is overloaded in such a procedure, the NodeB performs flow control on the RADIO LINK SETUP FAILURE message by using the policies described in Table 3-1.

The preferential flow control threshold is specified by the FRTRJT parameter on the NodeB side. The absolute guaranteed threshold and allowed flow control threshold cannot be configured by operators. Their default values are 95% and 93%, respectively.

By default, E2E Flow Control Phase 1 is disabled. To enable it, run the SET URRCTRLSWITCH command with the RsvdPara1 parameter set to RSVDBIT1_BIT5-1&RSVDBIT1_BIT31-0 on the RNC side.


In E2E Flow Control Phase 2, the RNC performs flow control on RRC CONNECTION REQUEST messages of new services (excluding emergency calls) based on the CPU congestion level reported by the NodeB and service priorities. The RRC CONNECTION REQUEST messages of low-priority services are preferentially rejected. E2E Flow Control Phase 2 serves as a supplement to E2E Flow Control Phase 1. The former reduces the NBAP signaling traffic on the Iub interface and saves RAN resources.

Flow%20Control.htm

Flow%20Control.htm

../NodeBParaHtml/mml-mo-para/para/CONGCTRLPARA-FRTRJT.html


WCDMA RAN




3-3

Huawei recommends using E2E Flow Control Phase 2 in conjunction with E2E Flow Control Phase 1, which is shown in Figure 3-2.

Figure 3-2 E2E Flow Control Phase 2 used in conjunction with E2E Flow Control Phase 1

The procedure for E2E Flow Control Phase 2 used in conjunction with E2E Flow Control Phase 1 is as follows:

1. The NodeB monitors the CPU load in real time and specifies the congestion level in the measurement report of the Received Total Wideband Power (RTWP).

2. The NodeB periodically reports the RTWP to the RNC.

3. The UE sends an RRC CONNECTION REQUEST message to the RNC. The message contains information about the service initiating the RRC connection request.

4. The RNC limits the number of RRC CONNECTION REQUEST messages admitted at the current second based on the congestion level reported by the NodeB.

The RNC does not perform flow control on RRC CONNECTION REQUEST messages of emergency calls or conversational services. According to the cause of the service establishment, the RNC performs flow control on RRC CONNECTION REQUEST messages of other services based on their service priorities. The following service priorities are in descending order: streaming services > BE services and high-priority signaling > low-priority signaling.

WCDMA RAN




3-4

If the number of RRC CONNECTION REQUEST messages admitted is greater than the preset threshold at the current second, the RNC rejects all subsequent RRC CONNECTION REQUEST messages and responds with RRC CONNECTION REJECT messages. If the number of rejected RRC CONNECTION REQUEST messages is greater than the value of the SysRrcRejNum parameter (set by running the SET UCALLSHOCKCTRL command), the RNC discards all received RRC CONNECTION REQUEST messages and does not respond to UEs with RRC CONNECTION REJECT messages. The number of RRC CONNECTION REQUEST messages that can be admitted at the current second on the RNC can be adjusted by running the SET UCTRLPLNFCPARA command. The default value is recommended. Note that adjusting this parameter directly affects flow control. Consult Huawei technical support before modifying the parameter settings.

5. If an RRC CONNECTION REQUEST message can be admitted, the RNC sends a RADIO LINK SETUP REQUEST message to the NodeB. This message contains the service priority. Then, the NodeB performs E2E Flow Control Phase 1 based on its CPU load. For details, see section 3.1 "E2E Flow Control Phase 1."

By default, E2E Flow Control Phase 2 is disabled. To enable it, run the SET UCTRLPLNFCPARA command with the RanCtrlFcSwitch parameter set to RAN_CTRLPLN_FC-1.

E2E Flow Control Phase 2 automatically stops if the RNC does not receive any RTWP measurement reports for more than 1 minute. When the RNC receives another RTWP measurement report, it starts E2E Flow Control Phase 2.

3.3 Overload Indication

The following counters indicate the number of RRC CONNECTION REQUEST messages discarded when E2E Flow Control Phase 2 is enabled:

VS.LowPriRRC.RanFC.Disc.Num

VS.NormPriRRC.RanFC.Disc.Num

VS.HighPriRRC.RanFC.Disc.Num

The counter VS.NodeB.CPU.Cong.Dur indicates the E2E Flow Control Phase 2 usage duration.

../RNCParaHtml/mbsc/m-para/ucallshockctrl_sysrrcrejnum.html

../RNCParaHtml/mbsc/m-para/uctrlplnfcpara_ranctrlfcswitch.html

WCDMA RAN

E2E Flow Control 4 Engineering Guidelines



4-1

4 Engineering Guidelines


4.1.1 Configuration Suggestions for E2E Flow Control Phase 1

When the NodeB is overloaded, E2E Flow Control Phase 1 reduces the NodeB load, helping to ensure access of high-priority services, such as emergency calls and CS services. It is recommended that E2E Flow Control Phase 1 be enabled.

4.1.2 Recommended Parameter Settings

The following key parameters are related to E2E Flow Control:

FRTRJT

The FRTRJT parameter specifies the flow control threshold for low-priority non-real-time services. The default value of this parameter is 90%, which ensures a smooth network upgrade.

RrcConnRejWaitTmr

After E2E Flow Control is enabled, set the IE wait time in the RRC CONNECTION REJECT message to 15 seconds.

4.1.3 Key Parameter Settings

Setting FRTRJT to a smaller value increases network reliability and the access of CS services and emergency calls is guaranteed when traffic burst occurs. In addition, the NodeB is less likely to break down, which occurs when the NodeB CPU load exceeds the absolute guaranteed threshold.

Setting FRTRJT to a smaller value, however, reduces the radio link setup success rate of the NodeB.

Setting FRTRJT to a larger value increases the number of service setups. For example, if the parameter value is changed from 80% to 90%, 10% more CPU capacity is used for service access. Flow control, however, can be triggered only when the CPU load reaches 90%, which reduces network reliability.


4.2.1 Configuration Suggestions for E2E Flow Control Phase 2

The RNC starts E2E Flow Control Phase 2 before the NodeB CPU is overloaded. Therefore, the RRC setup success rate of PS services may decrease after E2E Flow Control Phase 2 is enabled. E2E Flow Control Phase 2 reduces the signaling traffic over the Iub interface to avoid NodeB overload. Huawei recommends that E2E Flow Control Phase 2 be enabled to increase NodeB reliability.

4.2.2 Recommended Parameter Settings

After E2E Flow Control Phase 2 is enabled, set the reporting period of RTWP to 1 second or less by running the SET ULDM command and modifying the TenMsecForUlBasicMeas parameter. If the reporting period of RTWP is longer than 1 second, the effect of flow control may deteriorate because the feedback of the NodeB CPU usage may be delayed. For example, if the reporting period of RTWP is set to 2 seconds, then in the first second, the RNC can limit the number of RRC CONNECTION REQUEST messages that can be admitted based on the congestion level reported by the NodeB. In the next second, the RNC has to limit those requests assuming that the congestion level remains unchanged.



../RNCParaHtml/mbsc/m-para/ustatetimer_rrcconnrejwaittmr.html




../RNCParaHtml/mbsc/m-para/uldm_tenmsecforulbasicmeas.html

WCDMA RAN

E2E Flow Control 5 Parameters



5-1

5 Parameters

Table 5-1 Parameter description

Parameter ID NE MML Command Description

FRTRJT NodeB SET CONGCTRLPARA

Meaning:Control Plane Congestion First Reject Threshold

GUI Value Range:80~90

Actual Value Range:80~90

Unit:%

Default Value:90

RanCtrlFcSwitch BSC6900 SET UCTRLPLNFCPARA(Optional)

Meaning:Whether to start flow control on the control plane:

1) RAN_CTRLPLN_FC (RAN Integrated Flow Control Switch): When the switch is turned on, the RNC performs flow control on RRC connection setup requests based on the congestion levels reported by the NodeB.

GUI Value Range:RAN_CTRLPLN_FC(RAN Flow Control Switch)

Actual Value Range:RAN_CTRLPLN_FC

Unit:None

Default Value:None

RrcConnRejWaitTmr

BSC6900 SET USTATETIMER(Optional)

Meaning:Wait time in high-priority RRC connection reject message, the time period the UE has to wait before repeating the rejected procedure of RRC connection



Unit:s

Default Value:4

RsvdPara1 BSC6900 SET URRCTRLSWITCH(Optional)

Meaning:2) NAS_QOS_MOD_SWITCH (QoS Change Switch for NAS)

When the switch is turned on, for UEs whose HS-DSCH category is smaller than 13, if the maximum downlink rate specified in the PDP activation requests from the UEs exceeds 16 Mbit/s, the requests are sent to the CN after the rate is changed to 16 Mbit/s.

When the switch is turned off, the PDP activation


../NodeBMMLHtml/mml-mo-para/mml/set_congctrlpara.html

../NodeBMMLHtml/mml-mo-para/mml/set_congctrlpara.html

../RNCParaHtml/mbsc/m-para/uctrlplnfcpara_ranctrlfcswitch.html

../RNCParaHtml/mbsc/m-mml/set-uctrlplnfcpara.html





../RNCParaHtml/mbsc/m-mml/set-ustatetimer.html




../RNCParaHtml/mbsc/m-mml/set-urrctrlswitch.html



WCDMA RAN




5-2


requests are sent to the CN without changing the maximum downlink rate.

15) RSVDBIT1_BIT15 (Reserved Parameter 1 Bit 15)

When the switch is turned on, the RNC enables the function of AMR mute detection.

When the switch is turned off, the RNC disables the function of AMR mute detection.


When the switch is turned on, the RNC can perform DRDs during the P2D procedure.

When the switch is turned off, the RNC cannot perform DRDs during the P2D procedure.

17) SYSHO_CSIN_PERMIT_SWITCH (2G-to-3G CS Handover Switch)

When the switch is turned on, inter-RAT CS handovers from 2G cells to 3G cells are allowed.

When the switch is turned off, inter-RAT CS handovers from 2G cells to 3G cells are not allowed.


When this switch is turned on, the RNC performs a state transition from CELL_PCH or URA_PCH to CELL_FACH (P2F) upon receiving a CELL UPDATE message with the cause value "uplink data transmission" or "paging response".

When this switch is turned off, if receiving a CELL UPDATE message with the cause value "uplink data transmission" or "paging response," the RNC performs a state transition from CELL_PCH or URA_PCH to CELL_DCH (P2D) in either of the following scenarios:

(1)Congestion occurs on the FACH.

(2)Congestion occurs on the DCCH, and the value of the Establishment cause information element (IE) in the message is Originating Conversational Call, Terminating Conversational Call, or Emergency Call.


When the switch is turned on, for UEs that are

WCDMA RAN




5-3


establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state, the RNC stops establishing AMR services to handle cell update if the RNC receives from the UEs a cell update message containing the cause value "cell reselection."

When the switch is turned off, for UEs that are establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state, if the RNC receives from the UEs a cell update message containing the cause value "cell reselection," the RNC stops establishing AMR services to handle cell update and resumes AMR services only after cell update is completed.


When the switch is turned on, the RNC does not trigger cell update with the cause value "RL Failure" if the RNC detects interrupted downlink transmission on SRB2.

When the switch is turned off, the RNC triggers cell update with the cause value "RL Failure" and reestablishes radio links if the RNC detects interrupted downlink transmission on SRB2.


When the switch is turned on, the RNC does not trigger cell update with the cause value "RL Failure" reported by a UE if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.

When the switch is turned off, the RNC triggers cell update with the cause value "RL Failure" reported by a UE and reestablishes radio links, if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.


When the switch is turned on, for UEs using CS services, the RNC does not trigger cell update with the cause value "RL Failure" reported by a UE, if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.

When the switch is turned off, for UEs using CS services, the RNC triggers cell update with the

WCDMA RAN




5-4


cause value "RL Failure" reported by a UE and reestablishes radio links, if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.


When the switch is turned on, for UEs using PS services only, the RNC does not reestablish radio links for a UE if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.

When the switch is turned off, for UEs using PS services only, the RNC triggers cell update with the cause value "RL Failure" reported by a UE and reestablishes radio link, if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss.


When the switch is turned on, the RNC does not reestablish radio links for a UE if the UE reports to the RNC cell update caused by SRB reset.

When the switch is turned off, the RNC reestablishes radio links for a UE if the UE reports to the RNC cell update caused by SRB reset.


When the switch is turned on, for UEs using CS services, if a NodeB reports to the RNC that all radio links for a UE experience synchronization loss, the RNC starts the RL Restore timer whose duration is specified by the RlRstrTmr parameter in the SET USTATETIMER command. After the timer has expired, the RNC triggers cell update with the cause value "radio link failure" and reestablishes radio links for the UE.

When the switch is turned off, for UEs using CS services, if a NodeB reports to the RNC that all radio links for a UE experience synchronization loss, the RNC starts the RL Restore timer whose duration is specified by the T313 parameter in the SET UCONNMODETIMER command. After the timer has expired, the RNC triggers cell update with the cause value "radio link failure" and reestablishes

WCDMA RAN




5-5


radio links for the UE.


When the switch is turned off, the RNC performs the CELL_DCH-to-CELL_FACH (D2F for short) procedure on UEs that support fast dormancy.

When the switch is turned on, the RNC performs the CELL_DCH-to-CELL_PCH (D2P for short) procedure on UEs that support fast dormancy.

GUI Value Range:RSVDBIT1_BIT1, NAS_QOS_MOD_SWITCH, RSVDBIT1_BIT3, RSVDBIT1_BIT4, RSVDBIT1_BIT5, RSVDBIT1_BIT6, RSVDBIT1_BIT7, RSVDBIT1_BIT8, RSVDBIT1_BIT9, RSVDBIT1_BIT10, RSVDBIT1_BIT11, RSVDBIT1_BIT12, RSVDBIT1_BIT13, RSVDBIT1_BIT14, RSVDBIT1_BIT15, RSVDBIT1_BIT16, SYSHO_CSIN_PERMIT_SWITCH, RSVDBIT1_BIT18, RSVDBIT1_BIT19, RSVDBIT1_BIT20, RSVDBIT1_BIT21, RSVDBIT1_BIT22, RSVDBIT1_BIT23, RSVDBIT1_BIT24, RSVDBIT1_BIT25, RSVDBIT1_BIT26, RSVDBIT1_BIT27, RSVDBIT1_BIT28, RSVDBIT1_BIT29, RSVDBIT1_BIT30, RSVDBIT1_BIT31, RSVDBIT1_BIT32

Actual Value Range:This parameter is set to 0 or 1 according to the related domains.

Unit:None

Default Value:None

SysRrcRejNum BSC6900 SET UCALLSHOCKCTRL(Optional)

Meaning:The parameter specifies the maximum number of RRC Connection Reject messages per second from SPU subsystem to UE. When the SPU subsystem is in flow control state, the system will respond RRC Connection Reject message to UE. If the number of RRC Connection Reject messages exceeds the value of the parameter, RNC will discard the RRC connection request.



Unit:None

Default Value:100

../RNCParaHtml/mbsc/m-para/ucallshockctrl_sysrrcrejnum.html

../RNCParaHtml/mbsc/m-mml/set-ucallshockctrl.html



WCDMA RAN




5-6


TenMsecForUlBasicMeas

BSC6900 SET ULDM(Mandatory)

Meaning:UL basic common measurement report cycle. For detailed information of this parameter, refer to 3GPP TS 25.433.



Unit:10ms

Default Value:100



../RNCParaHtml/mbsc/m-mml/set-uldm.html

../RNCParaHtml/mbsc/m-mml/set-uldm.html

WCDMA RAN

E2E Flow Control 6 Counters



6-1

6 Counters

There are no specific counters associated with this feature.

WCDMA RAN

E2E Flow Control 7 Glossary



7-1

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

Glossary.htm

WCDMA RAN

E2E Flow Control 8 Reference Documents



8-1

8 Reference Documents

[1] Flow Control Feature Parameter Description

Flow%20Control.htm