Anda di halaman 1dari 17

Congestion Control

UMR3.0

UMTS
July, 2003 TAC3 Munich - Guariento 1

Contents

1. Introduction 2. Congestion Control 2.1 Overview 2.2 Algorithm for Implementation 2.3 Parameter 2.4 Message flows 3. Reference Specification

July, 2003

TAC3 Munich - Guariento

1. Introduction (1/2)
 WCDMA radio access has different limiting factors consisting of absolute phenomenon and enviroment dependent ones.  The most important matter is the interference in the radio path.  Due to the essential characteristics of WCDMA, every UE accessing the network generates signals, and meanwhile simultaneously, increases the interference in relation to the other UEs point of view.  During the network planning phase, one of basic criteria is to define the acceptable interference level in order to keep the systems loading functionality in properly. Taking the above into account, two algorithms must be considered in order to verify and recover possible abnormal situations.

- Admission Control - Congestion Control


July, 2003 TAC3 Munich - Guariento 3

1. Introduction (2/2)
RRM Logical Interaction
SRNC Initial Values for Power Control RRC connection request CN RAB assignment Traffic Volume/ Througput Measurements Outer Loop Power Control CRNC O&M Data Node B UE

BLER target Radio Bearer Translation RL setup/reconfig./ Admission Control Code Allocation/ Release/ Defragment. Congestion Control
Intrafrequency/ Interfrequency/ Intersystem measurements Traffic Volume Measurements

Common Measurements

Radio link setup/ deletion Request Radio Bearer Control (CTS, BRA) RL setup/addition deletion

O&M Data

Handover Control Measurement Control

Measurement report

July, 2003

TAC3 Munich - Guariento

2. Congestion Control
1) Overview (1/3)

In order to detect the overload situation, to bring its situation back quickly and to control the target load, Congestion Control is necessary. The general possible actions are ; 1) to reduce the bit rate of PS traffic (CTS) 2) to decrease the bit rate of PS bearer in multicall (BRA) 3) Handover to another WCDMA carrier (interfrequency HO) 4) Bearer dropping (for conversational and streaming traffic class). 3GPP doesnt specify any particular algorithm and then the suppliers implementation is necessary.
July, 2003 TAC3 Munich - Guariento 5

2. Congestion Control
1) Overview (2/3)

Purposes
 

to monitor uplink and downlink load (from AC) to detect the overload situation of the system against the natural load fluctuation due to, for example, the users mobility and activity to handle the congestion to bring the system back to the normal state

Two main functions located at the CRNC:


 

Congestion Detection : Decision if the cell is congestioned or not Congestion Handling (Solution) : Step to decrease the cell power to solve the congestion status
TAC3 Munich - Guariento 6

July, 2003

2. Congestion Control
1) Overview (3/3)
Admission Control CRNC NUL P CommonDL Internal Parameters Bearer drop via RNSAP: Radio Link Failure SRNC

NBAP: Common Measuement Report (RTWP) Reporting Period for RTWP NBAP: Common Measurement Report TCP Reporting Period for TCP

Congestion Control PS RABs Congestion Congestion Handling Detection Congestion (CS+PS) Indication RABs CRNC

Radio Bearer Control Transport Transport ChannelType Channel Type Switch Control Bit Rate Adaptation SRNC CELL DCH CELL FACH DCH HIGH DCH LOW

Uplink Congestion Threshold Downlink Congestion Threshold Uplink Congestion Hysteresis Downlink Congestion Hysteresis

O&M Data Base

Enable Bearer Dropping Enable Transport Ch Type switching in case of congestion K

July, 2003

TAC3 Munich - Guariento

2. Congestion Control
2) Algorithm for Implementation -Detection Procedure(1)The congestion detection is taken place as follow:
IF congestion indication = FALSE THEN IF RTWP - NUL> ICON OR TCP - PDLcommon > PCON THEN congestion indication = TRUE congestion handling procedure ENDIF ELSE IF RTWP - NUL< ICON - ICON, HYST AND TCP - PDLcommon < PCON - PCON,HYST congestion indication = FALSE ENDIF ENDIF
July, 2003 TAC3 Munich - Guariento 8

THEN

2. Congestion Control
2) Algorithm for Implementation -Detection Procedure(2)-

UL Case
No congestion
RTWP - Nul < UL Congestion threshold RTWP - Nul > UL Congestion threshold

Congestion detected

RTWP UL Congestion threshold(0,...,62dB)

NUL (update at AC) Time Reporting Period for RTWP


July, 2003 TAC3 Munich - Guariento 9

2. Congestion Control
2) Algorithm for Implementation -Detection Procedure(2)-

DL Case
No congestion
TCP -PDLcommon< DL Congestion threshold TCP - PDLcommon > DL Congestion threshold

Congestion detected

TCP

DL Congestion threshold(0,...,22dB) PDLcommon (update at AC) Time Reporting Period for transmitted carrier power
July, 2003 TAC3 Munich - Guariento 10

2. Congestion Control
2) Algorithm for Implementation -Handling (Solution) Procedure(1)After the traffic congestion is detected in the cell, Handling (Solution) procedure is started. Its aim is to make the cell UL/DL powers be lower than the threshold values by following actions ; Countermeasure to stop the power increase - New Bearer Denied; by Admission Control based on Congestion Indicator Countermeasure to clear the congestion status Step 1 - Transport Channel Type Switching procedure for PS call - Bit Rate Adaptation procedure for PS+CS call Step 2 - Call Drop for a certain RAB combination ranking
July, 2003 TAC3 Munich - Guariento 11

2. Congestion Control
2) Algorithm for Implementation -Handling (Solution) Procedure(2)Congestion Handling is performed, in the congestion cell, as follow:
0. New Bearer Denied by Admission Control based on Congestion Indicator 1. Selection of Target UEs
1) UEs with PS service 2) Ranking based upon the Spreading Factors (SF) from the lowest one

2. Activation of CTS and BRA Procedure


1) Starting from the first K UEs (K is an O&M parameter) with the lowest SF 2) UE Single PS RAB case If enable CTS parameter (O&M) is set to ON, Actvation of CTS and Transition from CELL_DCH to CELL_FACH 3) If there are remaining UEs with multibearer (PS+CS)

If enable CTS parameter (O&M) is set to ON, Activation of BRA (DCH_HIGH to DCH_LOW)8

3. Repetition of the procedure 2 during every Reporting Period (O&M data) until solution of the congestion
If in the last iteration of stage 2 only L UEs were treated, then stage 4 begins immediately, without waiting until the end of the next Reporting Period. In this case, the first iteration of stage 2 handles only K-L UEs.

4. Bearer Dropping in case the congestion persists after the Procedure 2 and 3
0) Under the situation that all PS RABs had been changed to CELL_FACH and all PS+CS RABls to the lower bit rate 1) If Bearer dropping parameter (O&M) is set to ON Re-ranking All UEs in the cell using their SF starting from the lower one regardless their service combination. The algorithm imforms RNC to drop the first K UEs (O&M data) in the list by RRC Connection Release Stage 2 is repeated every "Reporting Period", until all UEs have been treated. The CC algorithm has to make sure that for the same UE, no subsequent release requests are generated.

July, 2003

TAC3 Munich - Guariento

12

2. Congestion Control
2) Algorithm for Implementation -Handling (Solution) Procedure(3)Congestion detect RTWP New bearer Congestion denied Indication Step 1: CTS(DCH to FACH) for PS Step 2: Drop of users Congestion resolved for UL Congestion hysteresis (0,...,10dB) Time Reporting Period for RTWP - Number of bearers dropped or switched in one step(0,,10 by O&M data) - Enable transport/physical channel reconfiguration : True(step 1) / False(no action) by O&M data - Enable bearer dropping : True(step 2) / False(no action) by O&M data TCP Congestion detect Congestion Indication New bearer denied

UL
Congestion threshold

Congestion resolved for both UL and DL

DL
Congestion threshold

Step 1: CTS(DCH to FACH) or BRA for PS Step 2: Drop of users Congestion resolved for DL Congestion hysteresis (0,...,10dB) Time

Reporitng period for TCP

July, 2003

TAC3 Munich - Guariento

13

2. Congestion Control
2) Algorithm for Implementation -Remarks
Since the RNSAP does not support the radio link load indication in R99 [ 1 ], an RNC internal proprietary message is defined to trigger a forced transport channel type switch. The bearer dropping will be invoked by the RNSAP procedure Radio Link Failure. In case of CTS/BRA on DRNC, a RL Failure is signalled to the SRNC. A forced transport channel type switch is the preferred method to handle a congestion, because a transport channel type switch does not degrade the QoS contract for the given best effort data users.

July, 2003

TAC3 Munich - Guariento

14

2. Congestion Control
3) Operator Configurable Parameters
Name Uplink congestion threshold Uplink congestion hysteresis Downlink congestion threshold Downlink congestion hysteresis Reporting period for RTWP Reporting period for Transmitted Carrier Power Number of bearers dropped/switched in one step Enable bearer dropping Enable transport/ physical channel reconfiguration Q3-Name sbs3gRanUlC ongT sbs3gRanUlC ongH sbs3gRanDlC ongT hmi ul_cngt ul_cngh dl_cngt Type Real Real Real Range Unit 0,...,62 by dB step of 0.1 0,...,10 by dB step of 0.1 0,...,20 by dB step of 0.1 0,...,10 by dB step of 0.1 10, 20, ..., 60000 1, 2, 3,..., 60 10, 20, ..., 60000 1, 2, 3, ..., 60 0,...,10 ms min ms min R/W RW RW RW Default 10 2 6 Description Uplink congestion threshold Uplink congestion hysteresis Downlink congestion threshold

sbs3gRanDlC dl_cngt ongH sbs3gRanRT WBP sbs3gRanRe pTcp sbs3gRanK mmti_rtwbp

Real

RW

Downlink congestion hysteresis

Integ er Integ er Integ er

RW

5000

Reporting period for RTWP

mmti_tcp

RW

5000

Reporting period Carrier Power

for

Transmitted

RW

Number of bearers dropped/switched in one step

sbs3gRanEn ableBD sbs3gRanEn ableTPChR

ebd etpchr

Boole False, True an Boole False, True an

RW RW

True True

Enable bearer dropping Enable transport/physical reconfiguration channel

July, 2003

TAC3 Munich - Guariento

15

2. Congestion Control
4) Message Flows

Bearer dropping:
UE NodeB RNC SGSN/MSC

No load (V = 0) Common Measurement Report (RTWP/RSSI) Common Measurement Report (Tx Carrier NUL = RTWP
PDL,common = Tx Carier Power Note: wa=0 in cell adc object

Perform CS Call / PS Call Common Measurement Report (RTWP/RSSI) Common Measurement Report (Tx Carrier If RSSI NUL > ICON OR Tx Carrier Power PDL,common Iu-Release Request (release due to utran generated Iu-Release (Initiating message) RRC Connection Release RRC Connection Release Complete RL Deletion (Initiating message) RL Deletion (Successful Outcome message) REL (AAL2) REL (AAL2) RLC (AAL2) RLC (AAL2) Iu-Release (Successful Outcome message) RLSD (SCCP) RLC (SCCP)

July, 2003

TAC3 Munich - Guariento

16

3. Reference Specification
Reference 3GPP documentation
   

3GPP TR 25.922 Radio Resource Management Strategies 3GPP TS 25.413 UTRAN Iu interface RANAP Signalling 3GPP TS 25.423 UTRAN Iur interface RNSAP Signalling 3GPP TS 25.433 UTRAN Iub interface NBAP Signalling
UMR pre2.0 and 2.0 are compliant with 3GPP R99/March/Y01 baseline.

July, 2003

TAC3 Munich - Guariento

17

Anda mungkin juga menyukai