You are on page 1of 7

BSS Overload Control

Abstract The purpose of this document is to provide guidelines to the customer while dealing with overload conditions in the BSS and steps to be taken to minimize the service impact.

Revision: 2.0 Date: 25th October 2012 Issued by: INDIA CARE

.....................................................................................................................................................................................................................3 4 PROBLEM RECOVERY ..3 3 SYMPTOMS .....................................................................................................................3 2 PROBLEM DESCRIPTION.5 .....................TABLE OF CONTENTS 1 BACKGROUND..............................4 5 RECOMMENDATIONS .............................................

Under extreme conditions. a single page message is send to all BTSs. when a high spike in traffic is anticipated in the network. if a page arrives from MSC at a single MTL-LCF. this card will duplicate this page and send it to all RSL-LCFs. The document helps to detect overload conditions and suggests actions to be taken to bring the BSC and sites back into service. GSM paging requires paging all cells under a location area. Thus. natural calamities and New Year’s Eve can cause overload condition in the BSC. A RSL-LCF upon receiving this page message. If a traffic surge occurs. This exhausts the HDLC transmission buffers and fills up the mailboxes and as a result pages are dropped as paging queue is full. a sizeable number of pages would be by IMSI which uses up twice as much paging capacity as a TMSI page. 2 PROBLEM DESCRIPTION: Analysis of the field data shows the most of the overload conditions are due to high paging rates that occur suddenly. The document also provides recommendations/guidelines to be implemented in advance.1 BACKGROUND High traffic generated due to events like cricket matches. the offered load can easily drive the link utilization far beyond the engineered operating point. safe test audit failure DRI OOS . 3 SYMPTOMS The paging overload condition builds up with in very short a period so it’s important that problem is detected on the onset itself. At this stage with the MSC repeating pages due to no response from the mobile. RSLs are engineered to operate at 25% utilization under normal operating conditions. Following are the typical symptoms seen in BSCs and sites belonging to the same LAC under extreme overload conditions – Alarm 224. This way. The problem is compounded by repeat paging by IMSI and repeated call attempts by the calling party and lack of AGCH capacity to handle the increased traffic. the call processing is severely impacted and the BSC can experience service failures. will duplicate it and send it to all RSLs assigned to that LCF.

handover msg etc to be dropped. . Unlock the BTS site one by one every 3-5 minute while checking the MTL status. For LCF congestion control there are two configurable parameters rsl_lcf_congestion_thi and rsl_lcf_congestion_tlow. call setup msg . Lock all the BTS at the BSC. db cross download msg. These actions will quickly bring the paging load to a manageable level. The feature will help to detect onset of congestion and reduce paging traffic till the congestion abates. • • • • • • • • Lock all MTLs in the MSC. reset/OOS of devices occur and call processing is affected. if enabled at the MSC. In GSR 8 Software. Disable global paging. Reduce paging load by disabling SMS delivery reports. RSL congestion control feature is enabled by default in the software.NIU OOS RSL OOS MTL transitions LCF resets The surge in paging load will cause non paging messages like heartbeat msg. Unlock all MTLs in the MSC and check if MTLs transition to B-U at BSC. Disable Repeat Paging at MSC. audit msg. 4 PROBLEM RECOVERIES A number of actions must be taken to reduce the incoming signaling to the BSC depending on the severity of the problem. It is recommended not to change the default values of these two parameters which are 60% and 25% respectively. RSL congestion Control feature is introduced to control paging overload. When the messages are discarded. In the worst case it may be required to bar incoming calls and SMS in the LAC which is overloaded.

• Check MTL utilization and add MTLs if required.5 RECOMMENDATIONS Following are the actions to be implemented in the network when huge surge in traffic is expected. Channel requests will only be repeated upto M+1 times where M is equal to max_retran. • Increase the number of SDCCH in cells. • Make sure congestion relief is enabled. • Enable fast call setup using tch_usage_threshold parameter. For SBCCH cells. wherever possible. • Equip OMF processor in advance to reduce the load on BSP. the threshold is calculated considering the TCH resources in outer zone only. These are only guidelines and it’s recommended to fine tune the parameter settings based on the actual call traffic in the network. • Add RSLs in sites were RSL is congested. • Enable extended paging to smooth out the small peaks in paging load. Channel requests for call setup will be assigned directly to TCH minimizing SDCCH usage. • Reduce maximum retransmission value max_retrans to 2 retransmissions or one retransmission. broadcast on BCCH system information. if required based on the current call model. • Enable dynamic reconfiguration of SDCCH where call setup blocking is more than 0%. Valid range of max_retrans is 0 to 3 0 Maximum [1] retransmission 1 Maximum [2] retransmissions 2 Maximum [4] retransmissions 3 Maximum [7] retransmissions . Note: The SMS_INIT_ON_TCH_FCS stat needs to be enabled when FCS is used for consistency in the CSSR formula. • Its recommended to reassess the LAC dimensioning of the whole network and make any changes.

the next one is sent after a wait period. . 12 After the first channel request has been sent without reply.• Change the parameter tx_integer to a higher value for e. where T is a value dependent on tx_integer (broadcast on BCCH system information) and S is a preset number dependent on the value of T and multiframe type. made up of a random number of RACH slots. S+1 . The recommended parameter settings are as below. This may be turned on only if the subscribers are classified to different access classes. S+T –1). .g. . • Reassign high traffic carrying sites and distribute load equally among LCFs • Avoid equipping RSLs and MTLs on same LCF GPROC • Turn on RACH flow control and TCH flow control for cells were heavy congestion is expected. flow_control_t1 flow_control_t2 tch_flow_control tch_busy_critical_threshold tch_busy_norm_threshold ssm_normal_overload_threshold ssm_critical_overload_threshold ccch_load_period RACH_load_period RACH_load_type RACH_load_threshold 10000 15000 1 100 90 60 70 12 4 0 see below The rach load threshold is dependent on SDs in the cell and as rule can be calculated as. This wait period is in the set (S.

we want to turn off the relevant device audits for site 2: • device_audit 2 off dri 0 0 0 • device_audit 2 off msi 0 0 0 • device_audit 0 off rsl 2 0 0 (Note this command can only be executed at the BSC for this device: RSL) • Turn on MSC Overload flow control by setting bss_msc_overload_allowed parameter to value of 1. the BSS bars one access class at a time if it receives an OVERLOAD message.SDs 8 16 24 32 rach_load_threshold 100 200 300 400 • Switch off device audit tests for DRIs and NIU for sites with heavy congestion. END OF DOCUMENT . It would be better if repeat paging/global paging could be turned off at the MSC. In addition to the above actions. When this parameter is enabled. further precautions may be taken at the MSC in consultation with the MSC vendor. • The Safe test audit is a low priority task and if a radio is under heavy processor utilization. then DRI safe test audit failures occur. • Increase repeat paging timer at MSC to a higher value. For example. This mechanism allows the MSC to notify the BSS that it is becoming overloaded and to reduce the amount of information being sent to the MSC from the BSS. This is to allow the original page to be transmitted and to reduce the adverse impact of IMSI paging during onset of paging overload.