Vous êtes sur la page 1sur 16

SDCCH CONGESTION

SDCCH congestion rate = Failed SDCCH seizures due to busy SDCCH/Total requests for the SDCCH x 100%
SDCCH Blocking Rate = SDCCH Blocked Calls/ SDCCH Seizure Requests *100

Check Equipment faulty and transmission Check Improper Data Configration Check Interference Check LAC planning( on LAC boundary high pagging occur. So high PSR will gone to down and Blocking can occur.

Parameter Setting

SDCCH Availability LAC T3101 (the timer used in the immediate assignment procedure) T3212 (the timer used for periodic updating) range 0 to 255, we adjust 20. 1=6mins

CSSR
BSS CSSR = Immediate Assignment Success Rate x TCH Assignment Success Rate x (1 - SDCCH Drop Rate) x 100%
Check Immediate Assignment Success Rate Check Assignment Success Rate Check SDCCH Drop Rate

DCR
TCH call drop rate (including handover) = Number of call drops on TCH/(Number of successful TCH seizures (signaling channel) + Number of successful TCH seizures (TCH) + Number of successful TCH Seizures in TCH handovers (TCH)) x 100% TCH call drop rate (excluding handover) = Number of call drops on TCH/Number of successful TCH seizures (TCH) x 100%

Hardware failure Transmission problem Version upgrade Parameter setting Intra-network and inter-network interference Coverage problem Antenna system problem Imbalance between uplink and downlink Repeater problem Swapping TRX Usibility Bad HOSR

Pareameter Setting 1. 2. 3. 4. 5. 6. 7. 8. 9. The parameters SACCH Multi-Frames and Radio Link Timeout are set to too small values. The parameter RXLEV_ACCESS_MIN is set to a too small value. The parameter RACH Min.Access Level is set to a too small value. The parameters Min DL Power on HO Candidate Cell and Min Access Level Offset are inappropriately set. The length of timer T3103 (this timer is set to wait for a Handover Complete message) is set to a too small value. The length of timer T3109 (this timer is set to wait for a Release Indication message) is set to a too small value. The length of timer T3111 (this timer specifies the connection release delay) is set to a too small value. The length of timer T305/T308 is set to an invalid or too great value. The parameter TCH Traffic Busy Threshold is set to a too small value.

10. The parameter Call Reestablishment Forbidden is set to Yes. 11. The parameters related to edge handover are inappropriately set. 12. The parameters related to BQ handover are inappropriately set. 13. The parameters related to interference handover are inappropriately set. 14. The parameters related to concentric cell handover are inappropriately set. 15. The parameters related to power control are inappropriately set. 16. T200 and N200 are set to too small values. 17. Some neighboring cell relations are not configured. 18. The parameter MAIO is inappropriately set. 19. The parameter Disconnect Handover Protect Timer is set to a too small value. 20. The parameter TR1N is set to a too small value.

21. The parameters Software Parameter 13 and MAX TA are set to too small values. If a repeater is used, the parameter Directly Magnifier Site Flag is set to No.

TCH Congesion rate


TCH Congestion Rate (All Channels Busy) = Failed TCH Seizures due to Busy TCH / TCH Seizure Requests x 100%
TCH Blocking Rate (Tata) = Failed TCH Seizures due to Busy TCH (Traffic Channel) / TCH Seizure Requests (Traffic Channel) * 100

Network capacity and traffic distribution Faults occurred during equipment installation, transmission, or on the hardware Network interference KPI measurement problems Incorrect parameter settings Third-party device problems Software version problems Check LAC planning( on LAC boundary high pagging occur. So high PSR will gone to down and Blocking can occur.

Parameter check

1. TCH Traffic Busy Threshold(%) is incorrectly set. 2. Tch Traffic Busy Overlay Threshold and Tch Traffic Busy Underlay Threshold are incorrectly set. 3. Assignment Cell Load Judge Enable (BSC6000) is invalid. 4. Directed Retry Load Access Threshold is invalid. 5. Balance Traffic Allowed is not set. 6. Load HO Allowed is not set. 7. Load HO Step Period is set to a too great value. 8. RACH Min.Access Level is set to a too small value. 9. Cell reselection parameters are incorrectly set. 10. Cell Direct Try Forbidden Threshold (BSC6000) is incorrectly set.

11. Direct Retry is set to No. 12. SDCCH Dynamic Adjustment is invalid. 13. Flow control parameters are invalid. 14. Speech Version is incorrectly set.

SDCCH DROP RATE


Call Drop Rate on SDCCH = (Call Drops on SDCCH/Successful SDCCH Seizures + Successful SDCCH Seizures in the signaling channel handover) x 100%

Hardware failure Transmission Version upgrade Parameter setting Intra-network and inter-network interference Poor Coverage Imbalance between uplink and downlink Hardware Faulty

Parameter Setting

1. SACCH Multi-Frames (SACCH period (480ms)) and Radio Link Timeout(SACCH period (480ms)) are set to too small values. 2. RACH Min.Access Level(dBm) is set to a too small value. 3. T200 SDCCH(5ms) and N200 of SDCCH are set to too small values. 4. MAIO is set improperly.

Path Imbalance
Antenna and feeder installation TMA installation Incorrect parameter settings Hardware fault Repeater Antenna matching problem MS user behavior Parameter Setting 1. MS_TXPWR_MAX_CCH

Bi en g

Eu t eakf n r hrno se SC cn so D H gt n C o ei rt a e (B S C -l v o ee r l cl e l -l v ee l ) N o Y e s Cc wt et e h k hh h e e r h da i fuy a wes al r r t N o Y e s Cc wt e h k hh e e r cn soo u o e i nc r gt cs Ccwt e t e h khh h e e r cn soi cu dy o ei ns as b gt e b sta i ut rf c r f Rl nhn b o e a te u e f p m r TH nSC s r C ad D H s C o cagt e h ehT n cng ao oiut n f ri Rtf t e al e iy fu c h t acri goht p co nt t ey s d e ob sSC f ut D H r C rq s eu t es Cc adl a t e h knc r h e e cre o i gl r s o s nna m r pd a

N o

32 2 1

N o

Y e s

Cc wt e t e h k hh h e e r da o i u toi a cng a ns t f ri fuy al t N o Cc wt et e h k hh h e e r q lt oU uiyf m a i t raes a n fc i b e d

Y e s

A srl v t d te a j u en p a e r sc a a m su s r t e h LC A , T3 1 1 0

, T3 2 2 1

Y e s

Re t t e e r oh f W It r rn ihn f ec t ee e

G eo el u tD i d a

N o

Cc wt et e h k hh h e e r cn sodap r o e i ni p a gt s es Y e s E n d

Pol ma d n r b hnl g e i sat d t re

W nh f u i r l t do h t e a l s eae t e t I m i t A i n e tSc es me ae s gm uc s d s n Rt ae , S CH r p aeo DC D Rt r o A i n e tSc esRt s gm uc s ae s n

I m i t Ai n et me ae s gm d s n Sc esRt otme uc s ae p i d i z

S CH r p ae DC D Rt o otme p i d i z

A i n e tSc esR e s gm uc s a s n t otme p i d i z

N o

Wt e t e h hr h e f u i r ci i d a l s e tfe t Y e s Pol ma d n r b hnl g e i c mee optd l

Start

Find the cell with high TCH call drop rate

Faulty hardware or transmission? No

Yes

Rectify the hardware and transmission fault

Yes Upgraded version?

Check whether the version is faulty

Replace the faulty version with a normal one or install a patch

No Adjust parameters related to handover and power control No Solve inter-network interference problem

Incorrect data configuration?

Yes

No Yes Intra-network interference?

Interference?

Yes No Optimize coverage according to the network coverage optimization guide

Check the frequency configuration

Yes Insufficient coverage?

No Yes Adjust the antenna system

Faulty antenna system? No

Yes Imbalance between uplink and downlink? No Yes Faulty repeater? No Normal TCH call drop rate? Yes End

Solve the imbalance problem according to the guide

Solve the repeater problem

Begin

Ensure the rank of SDCCH congestion rate (BSC-level or cell-level) No Yes Check whether the hardware is faulty No Yes Check whether congestion occurs Checkwhether the congestion is caused by burst traffic No Replan the number of TCHs and SDCCHs or change the T3212 configuration Rectify the fault according to the types of burst SDCCH requests Check and clear the corresponding alarms

No

Yes

Check whether the data configuration is faulty No Check whether the quality of Um interface is bad

Yes

Adjust relevant parameters such as LAC, T3101 , T3212

Yes

Refer to the Guide to Deal With Interference

No

Check whether the congestion disappears Yes End

Problem handling started

When the fault is related to Immediate Assignment Success Rate, SDCCH Drop Rate or Assignment Success Rate

Immediate Assignment Success Rate optimized

SDCCH Drop Rate optimized

Assignment Success Rate optimized

No

Whether the fault is rectified Yes Problem handling completed

The HOSR is low Check whether the handover thresholds and the BSC clock over the A interface circuit comply with the standards

Whether the problem occurs in some cells Yes Whether a hardware and transmission failure occurs No Whether the data is configured improperly No Whether the target cell is congested No Whether a clock problem occurs No Whether an interference problem occurs No Whether a coverage problem or uplink and downlink imbalance occurs No Whether the problem occurs in a co-BSC under a co-MSC No Perform automatic neighboring cell optimization

No

Yes

Rectify the hardware and transmission faults

Yes

Change the data configuration

Yes

Check whether a TRX or a channel failure causes high traffic in each timeslot. If yes, change the TCH Traffic Busy Threshold(%) and expand the capacity

Yes

Clear the clock alarm and replace relevant hardware

Yes

Optimize the RF

Yes

Optimize the RF

Yes

Check the common hardware, the handover data configuration between the BSC and the MSC, and the CGI of the cells

End

Start

Determine the area with low paging success rate

Whether the hardware or transmission is faulty No Whether the paging is overloaded or the burst traffic occupies the SDCCH No Whether the data configuration is correct No Whether the interference problem exists No Whether the coverage problem exists No Whether the uplink and downlink balance problem exists No No

Yes

Solve the hardware or transmission problem Adjust the channel configuration, solve the paging overload problem or observe the traffic Adjust the configuration related to the paging on the MSC side Adjust the configuration related to the paging on the BSS side

Yes

Yes

Yes

Solve the interference problem according to the related guide

Yes

Solve the coverage problem according to the related guide

Yes

Solve the uplink and downlink balance coverage problem according to the related guide

Whether the problem persists Yes End

Start

Analysis o immediate as success

Find cells w

Channel Request

Idle Channel Available Normal Assignment Procedure No Successful Assignment No

No Queuing Allowed Yes Queuing Yes

Reassign Allowed Yes Idle Channels Available Yes Yes

No

Queuing Successfully No

No

No Directed Retry Allowed Yes

Reassign

Directed Retry

Reassign Successfully Yes


Measure TCH Seizure Failures Measure Successful TCH Seizures

No

Directed Retry Successfully Yes

Check whether the BTS is an operational Huawei BTS

Possible cause analysis 1

Possible cause analysis 2

1. Check the hardware configuration

Coverage decrease is caused by combination loss due to capacity expansion? Configuration of neighboring cell relations is missing? Check for clock faults, radio link faults, intermittent disconnection, or TRX communication fault. Compare the drive test data before and after network swapping. If the coverage is normal, the BTS fault is excluded from the cause. Check antenna and feeder connections, connectors, combiner, and VSWR. Check whether the antenna is aging. Test the power on top of the cabinet. If the power and receive sensitivity are normal, exclude the BTS fault from the cause.

Check for TRX fault or TRX insufficiency, which may cause congestion and traffic volume decrease.

2. Check the parameter settings

Check the parameters: Cell Layer, Power Class, RACH Min.Access Level, RXLEV_ACCESS_MIN, and CRO.

3. Check the alarms and traffic statistics

Check whether congestion occurs and whether coverage is normal according to traffic statistics, and check the uplink and downlink receive quality.

4. Compare the drive test data

Communicate with the customer that makes complaints and conduct field tests to obtain the first-hand data.

5. Check the BTS antenna and feeder

Check whether the tilt or azimuth angle of the antenna changes , because the main and diversity of the BCCH omnidirectional antenna may change the coverage area, thus decreasing the traffic volume. Check whether additional losses are introduced, such as the additional jumpers, added TMA, and surge protector.

6. Test the power on top of the cabinet

7. Find out other possible causes

Start

Are the uplink and downlink in balance in the cell? No Check the connection of the antenna and feeder in these cells. Yes Is there any problems with the antenna and feeder connection?

Yes

No processing is required for the normal cells.

Is the uplink-downlink imbalance rectified ?

Yes

No Check the parameter settings in this cell. The cause of the problem is identified. The flow is complete. Yes Yes

Are the parameters set correctly? No

Is the uplink-downlink imbalance rectified ?

No Test the cabinet-top power.

Is the transmit power normal? Yes

No

Is the uplink-downlink imbalance rectified ?

No Trace the signaling on the Abis interface in the faulty cells . The hardware fault is confirmed. Send the faulty TRX to Huawei for further analysis.

Conduct fixed-position tests in the faulty cells and trace the signaling on the Abis interface.

Are the user behaviors normal in the faulty cells? Yes Replace the faulty TRX with a normal TRX.

No

Is the uplink-downlink imbalance rectified ?

Yes

No

Is there a problem with the hardware? No

Yes

Send the faulty hardware to Huawei for further analysis .

\\172.16.201.70\bsc6000\data\mtndata\pfm\rslt