systematic Important Timers

1 T3101
I. Definition T3101 is the BSC timer controlling time of immediate assignment process. II. Format T3101 ranges from 0 to 255s. The recommended value is 3s. III. Configuration and Influence In an immediate assignment process, the BSC requires BTS to provide SDCCH to set up signaling channel. When the BSC sends a channel activation message, T3101 starts timing. When the BSC receives the setup instruction sent by BTS, T3101 stops timing. When T3101 expires, the system releases corresponding SDCCH resources. Proper configuration of T3101 reduces congestion due to dual assignment SDCCH effectively. The greater the T3101 is, the longer the inefficient time for using signaling resources is. For example, if the extended transmission delay is improperly configured (usually the sum of T and S is over small), the MS fails in responding to the network side, so the MS resends the random access request message. Therefore, the network side will assign SDCCH (the network cannot distinguish the repeated sending access request from the first send). For better use of signaling resources, especially in activating queue function, you must configure T3101 to a smaller value. The minimum interval for sending channel activation message and receiving setup indicator is 600ms. For non-overload BSS, the maximum interval is 1.8s.

2 T3103
I. Definition In inter- and intra-BSS handover, the BSC determines the time for keeping TCH both in handoveroriginated cell and target cell. When the timer receives handover completion (intra-BSC) or clearing (inter-BSC) message, T3103 stops. II. Format T3103 ranges from 0 to 255s. The recommended value is 5s. III. Configuration and Influence The following paragraph is an example of inter-BSS handover. When T3103 receives the handover command, it is reset and starts timing. When it receives clearing command, it is reset. This means that T3103 reserves two channels when it is timing, one channel for source BSC, and one channel for target BSC. If it is over long, two channels are occupied for a long time and resources might be wasted. According to the tests, if the NSS timer is properly configured, the handover process occurs within 5s. Therefore, the recommended value is 5s.

3 T3105
I. Definition See the protocol 0408 and 0858. When sending physical information, the network starts T3105. If the timer expires before receiving any correct frames from MS, the network resends physical information and restarts the T3105. The maximum repeated times is Ny1. II. Format T3105 ranges from 0 to 255, with unit of 10ms. III. Configuration and Influence The physical information is sent on FACCH. The time for sending four TDMA in a time on FACCH is about 18ms. If the next physical information is just sent 18ms after the first one, probably the first physical information is still being sent. The minimum time for sending physical information continuously and most quickly is 20ms. IV. Precautions T3105 is related to the timer NY1. If T3105 is small, configure NY1 to a greater value. If a handover trial fails and the T3105 of the target cell expires for Ny times before the original cell receives the HANDOVER FAILURE message, the target BTS sends the CONNECTION FAILURE INDICATION message to the target BSC. The counter of target BSC is renewed though MS might return to the original channel. To avoid this, the T3105 must meet the following foulard: Ny * T3105 > T3124 + delta Wherein, delta is the time between expiration of T3124 and receiving HANDOVER FAILURE message by original BSC.

4 T3107
I. Definition T3107 is a BSC timer, restricting the time for executing TCH assignment instruction. It caters for TCH assignment of intracell handover and channel assignment of calling. II. Format T3107 ranges form 0s to 255s. The recommended values are as follows:

10s when channel resources are enough. 5s when channel resources are limited. III. Configuration and Influence

T3107 starts after the BSC sends the ASS_CMD message to BTS. It stops after the BSC receives the ASS_CMP or ASS_FAIL message sent by BTS. If T3107 expires, the system judges that the MS disconnects to the network, so the occupied resource is released to other MSs. According to the measured statistics result of network, the channel assignment is complete within 2s. If the BSC does not receive ASS_CMP message after 2s, the assignment command fails. If the radio link is bad and some information must be resent, the process might be prolonged to 5s. To avoid premature disconnection, configure T3107 to 10s. In this way, the MS can reuse the original channel when handover or assignment fails. Therefore the call drop due to intracell handover decreases or the system service quality of re-assignment is improved (if the system supports reassignment function). However, the channel resource might be wasted for several seconds. When the network capacity is limited, you must save the resource as possible.

5 T3109
I. Definition The BSC restricts the releasing resource of SACCH by T3109. II. Format T3109 ranges from 3s to 34s. The recommended T3109 is as follows: T3109 = a + RdioLinktimeOut x 0.480s, a = 1s or 2s. III. Configuration and Influence T3109 measures the time for channel releasing indicator after sending MS clearing instructions. It starts after the BSC sends DEACT_SACCH message to BTS. It stops after the BSC receives the REL_INC message sent by BTS. When T3109 expires, the BSC sends the CLEAR REQUEST message to MSC. IV. Precautions The sum of T3111 and T3109 must be greater than RadioLinkTimeOut. If T3109 is over small, the corresponding radio resources are re-allocated before RadioLinkTimeOut is due (radio link is not released).

6 T3111
I. Definition T3111 is a connection release delay timer, used in deactivation of delayed channel after disconnection of major signaling link. T3111 aims to spare some time for repeated disconnections. When BSC receives the REL_IND message sent by BTS, T3111 starts. For time protection, T3111 stops until expiration and the BSC sends the RF_CHAN_REL message to BTS. II. Format T3111 ranges from 0s to 5s. The recommended value is 2s. III. Configuration and Influence After the disconnection of major signaling link, T3111 delays the release of channels. It allows the base station to retransmit the instruction for releasing radio channels to MS within delayed time. After the base station sends a release request massage, the radio resources remain for T3111 time. If the system capacity is small, configure T3111 as short as possible. The minimum value of T3111 is 2s, over five multiples of the time for resending MS the instruction for releasing radio channel resources. A greater T3111 might be of no help, but affects congestion of SDCCH and TCH easily.

7 Parameter T3212
I. Definition In a GSM network, the causes to location updating are as follows:

The MS attach. The MS detects that its location area changes.

The network forces MS to update location periodically. The network controls how frequent the MS updates location, and the period for location updating is determined by the parameter T3212.

II. Format T3212 ranges from 0 to 255, with unit of 6 minutes (1/10 hour). If T3212 = 1, it means that T3212 is 6 minutes. If T3212 = 255, it means that T3212 is 25 hours and 30 minutes. If T3212 = 0, it means that MS is not required for periodical location updating in the cell. The recommended T3212 is 240. III. Configuration and Influence As an important means, the periodical location updating enables network to connect to MSs closely. Therefore, the short the period is, the overall service performance of the network is. Anyhow frequent periodical location updating brings two negative aspects: The signaling flow of the network increases sharply and the utilization of radio resource declines. When the period is over long, the processing capability of network elements (NE, including MSC, BSC, and BTS) is directly affected. The MS must transmit signals with greater power, so the average standby time is shortened sharply. Therefore, configure T3212 according to resource utilization in various aspects of network.

T3212 is configured by equipment room operators. Its value depends on the flow and processing capability of each NE. Configure T3212 as follows: Configure T3212 to a greater value (such as 16 hours, 20 hours, or even 25 hours) in areas with heavy traffic and signaling flow. Configure T3212 to a smaller value (such as 3 hours or 6 hours) in areas with low traffic and signaling flow. Configure T3212 to 0 in areas with traffic overrunning the system capacity. To configure T3212 properly, you must permanently measure the processing capability and flow of each UE in the running network, such as:

The processing capability of MSC and BSC A interface, Abis interface, and Um interface The capability of HLR and VLR If any of the previously listed NEs is overloaded, you can consider increasing T3212.

IV. Precautions T3212 cannot be over small. Otherwise, the signaling flow at each interface increases sharply and the MS (especially handset) consumes increasing power. If the T3212 is smaller than 30 minutes (excluding 0), the network will be fiercely impacted. Configuring T3212 of different cells in the same location area to the same value is recommended. In addition, the T3212 must be consistent with related parameters of switching side (smaller than the implicit detach timer at switching side). If the T3212 of different cells in the same location area is the same, in the cell reselection, the MS continues to time according the T3212 of the original cell. If the T3212 of the original and target cell in the same location area is different, the MS uses the T3212 of the original cell modulo that of the serving cell. According to the actual tests of MS in the network, if the T3212 in the same location area is different, after the MS performs modulo algorithm based on behaviors of some users, the MS might power on normally. However, the MS fails in originating location updating, so the network identifies it as implicit detach. Now the MS powers on normally, but a user has powered off prompt appears when it is called.

8 T3122
I. Definition T3122 defines the period that the MS must wait for before the second trial calling if the first trial calling fails. It aims to avoid congestion of SDCCH due to repeated trial calling by MS and to relieve system load. II. Format T3122 ranges from 0s to 255s. The recommended value is 10s. III. Configuration and Influence The value of T3122 is included in the immediate assignment reject message. After the MS receives the immediate assignment reject message (no channels for signaling, A interface failure, overload of central processing unit, namely, CPU), it can send new trial calling request after T3122. T3122 aims to relieve radio signaling and voice channel resources. T3122 also help avoid systematic overload. When the CPU is overloaded, the system multiplies T3122 by a factor (determined by processorLoadSupconf) to increase T3122 through overload control. In peak load time, you can manage network access by increasing T3122. Namely, you can increase the interval between two continuous trial callings to relieve network load.

9 T3124
I. Definition T3124 is used in occupation process in asynchronous handover. It is the time for MS to receive the physical information send by network side. II. Format Configure it to 675ms when the channel type of assigned channel for HANDOVER COMMAND message is SDCCH (+ SACCH). Configure it to 320ms in other situations. III. Configuration and Influence When the MS sends the HANDOVER ACCESS message on the primary DCCH, T3124 starts. When the MS receives a PHYSICAL INFORMATION message, the MS stops T3124, stops sending access burst, activates the PCH in sending and receiving mode, and connects to the channel if necessary. If the assigned channel is a SDCCH (+ SACCH), you must enable MS to receive a correct PHYSICAL INFORMATION message sent by network side in any block. If T3124 expires (only in asynchronization) or the low layer link fails in the new channel before sending the HANDOVER COMPLETE message, the MS proceeds as follows: 1) Deactivate the new channel 2) Restart the original channel 3) Reconnect to TCH 4) Trigger to setup primary signaling link Then the MS sends the HANDOVER FAILURE message on the primary signaling link and return normal operation before trial handover. The parameters for returning the original channel are those before response to the HANDOVER COMMAND message (such as in encryption mode).

10 T11
I. Definition T11 is an assignment request queue timer.

II. Format T11 is determined by equipment room operators. It indicates the maximum queuing delay for assignment request. III. Configuration and Influence When the BSC is sending the ASSIGNMENT REQUEST message, no TCHs are available. The ASSIGNMENT REQUEST message must be put to a queue and the BSC sends the QUEUING INDICATION message to MSC. Meanwhile, T11 starts timing. When the BSC sends the ASSIGNMENT COMPLETE message (TCH is successfully assigned) or the ASSIGNMENT FAILURE message (TCH is not assigned) to MSC, T11 stops timing. If T11 expires, the corresponding ASSIGNMENT REQUEST message is removed from queue and the BSC sends a CLEAR REQUEST message with the cause of no radio resource available to MSC to clear calling. Assignment queuing helps reduce service rejection times due to congestion, so enabling it is recommended in a network. Anyhow, T11 cannot be over great and it must be configured according to customer habits.

11 T200
I. Definition T200 is important (both the MS and base station have T200) at Um interface in data link layer LAPDm. LAPDm has different channels, such as SDCCH, FACCH, and SACCH, and the transmission rate of different channel is different, so T 200 must be configured with different values. The type of the channels corresponding to T200 is the value of the T200. II. Format Different channels corresponds different values of T200. According to the protocol, when SAPI = 0 and SAPI = 3, the T200 of corresponding data link is dependently implemented, depending on delay of synchronous processing mechanism and process in layer 1 and layer 2. Table 7-1 Value range and default of each type of T200 T200 T200_SDCCH_SAPI0 T200_FACCH_Full_Rate T200_FACCH_Half_Rate T200_SACCH_TCH SAPI0 T200_SACCH_TCH SAPI3 T200_SACCH_SDCCH T200_SDCCH_SAPI3 III. Configuration and Influence T200 avoids deadlock in sending data in data link layer. The data link layer changes the physical link in which error occurs easily to data link with no errors. At the two ends of the data link communication system, a confirm-to-resend mechanism is used. Namely, receiving a message by the receiver must be confirmed by the sender. If it is unknown that the message is lost, both two ends wait for messages, so the system confronts a deadlock. Therefore, T200 is used by the sender. When T200 expires, the sender judges that the receiver fails in receiving the message, so it resends the message. When the sender needs to confirm whether the receiver has received the message, T200 starts. When the sender receives the response from the receiver, T200 stops. When T200 expires, the resending Minimum 50 40 40 120 120 50 50 Maximum 100 100 100 200 200 100 100 Default 60; /* = 60 * 5 ms */ 50; /* = 50 * 5 ms */ 50; /* = 50 * 5 ms */ 150; /* = 150 * 10 ms */ 150; /* = 150 * 10 ms */ 60; /* = 60 * 10 ms */ 60; /* = 60 * 5 ms */

mechanism starts. If the sender receives no response from the receiver after multiple resendings, it sends ERROR INDICATION (T200 expiration) to layer 3. IV. Precautions T200 must be properly configured to ensure a predictable behavior at Um interface. The rules for configuring T200 include: The potentially-existing lost frames in radio link must be detected as possible. Necessary retransmission of frames must start at the earliest possible moment. If the response is delayed due to UE failure, the T200 cannot expire before receiving and processing the next frame from the opposite end. If T200 expires and no other frames are sent by preference, the related frames must be resent in the message block. T 200 starts immediately after next PH-READY-TO-SEND.

12 N200
I. Definition N200 is the resending times after expiration of T200. II. Format To configure N200, follow rules below: 1) When SAPI = 0 or 3, N200 depends on the state and the channel used. When multiframe operation is set up, it ensures a common time value for layer 2 link failure in all channels. For layer 2 link establishment and release, configure N200 to 5. 2) In timer recovery state, configure N200 as below: 5 (SACCH) 23 (SDCCH) 34 (FACCH of full rate) 29 (FACCH of half rate) 3) When SAPI is unequal to 0 or 3, configure N200 to 5, as shown in Table 1-6. Table 7-2 Situations of SAPI unequal to 0 or 3 SAPI Channel Valid response delay Minimum resending delay Trmin 51 Maximum resending delay

Tresp Trmax Note 3 MS: 11 51 BSS: 32 0 FACCH/Full rate 9 26 39 0 FACCH/Half rate 10 34 44 3 SDCCH MS: 11 51 51 Note 1 BSS: 32 25/129 Note 3 SACCH(with TCH) 312 416 Note 2 2 The TDMA frame is the measurement unit of values in this table, equal to 120/26ms (approximately 4.615ms) Note 1: It caters for the process without SAPI 0 transmission. Otherwise, it does not have a upper limit due to the priority of SAPI 0 transmission. Note 2: You can configure it to a greater value only when PCH is unavailable due to SAPI frame transmission if SAPI = 3. Note 3: It caters only for sending monitoring frames that are available and without F equal to 1. 0 SDCCH

III. Configuration and Influence If the BSC fails in receiving lay 2 response message after multiple resending, it sends the ERROR INDICATION message (T200 expires) to layer 3. The BSC takes statistics of ERROR INDICATION message by corresponding traffic measurement counter. When T200 or N200 is configured to an over small value, call drop occurs probably due to ERROR INDICATION.

It can also be related to Lapd but that's not the same Timer. Lapd T200 is lapd N200 are different from T200 and N200. Thanks again. Someone was telling me this is related to the LapD Signalling and T200 expiry means failure on the LapD interface. is this true? T200 is an air interface timer regulating the communication between MS and BTS. It defines the rate of repetition of a message (on BTS side) on the air if it is not acknowledged by MS. If the message was repeated N200 times and no answer was received by MS, an error indication with cause T200 expired is provided to BSC. T200=ny1 * N200 where ny1 is configurable on BTS database
There are two timers called T200s and T200f associated with sdcch and facch respectively for the supervision of messages which transfer from BTS to mobile. Range for both of this timer are from 220 to 1260 with step of 20 and Unit is 20ms. Overview:This timer is used on different control channel types and determines the waiting time for a layer 2 frame acknowledgement. During any dedicated connection the BTS and the MS exchange specific LAPDm signalling messages in the so-called in 'acknowledged mode'. This mode is started with an SABM and normally ends with the LAPDm DISCONNECT.All messages within this 'acknowledged mode' are checked by the LAPDm flow control mechanisms based on sequence numbers that are assigned to each transmitted LAPD message. Only for those messages that are transmitted in acknowledged mode the timer T200 is used as waiting time for the layer2 acknowledgement to a transmitted message. MS also uses the layer 2 acknowledgement mechanisms based on T200 in the same way as the BTS. In the MS, however, the T200 timer values are not variable but hardcoded. Functional description:When the BTS transmits a DL layer-2 frame on the air (e.g. an I-frame with an embedded layer 3 message) the BTS starts the timer T200 and waits for the acknowledgement frame from the MS. The

acknowledgement frame can be another I-frame sent by the MS in the UL (if the MS has to transmit a layer-3 DTAP message anyway) as well as RECEIVE READY (RR) if there is nothing else to be transmitted on layer 3. If the acknowledgement from the MS is not received within T200 the transmission of the layer 2 frame is repeated and T200 restarted. The total number of repetitions is restricted to N200, a fixed value for the BTS side specified by GSM which depends on the following control channel types: N200(SDCCH)=23, N200(SACCH)=5, N200(FACCH/FR)=34, N200(FACCH/HR)=29 If T200 expires after the last layer 2 frame repetition the BTS sends an ERROR INDICATION with cause 'T200 expired N200+1 times' (followed by a RELEASE INDICATION) message to the BSC, which releases the associated resources. Read more about other GSM timers:GSM timers Optimized value and uses:Based on project trial optimized value for both timers are 800ms.

Low TCH Assignment Success Rate

Here is the some possible solution for Low TCH Assignment Success Rate Successful assignments show the number of successful TCH allocations at call setup.At unsuccessful assignment, the Assignment Complete message, sent by the MS, was never received by the BTS. Probable Reasons The reason for a low number of successful assignments might be the following items: 1.No Dominant Serving Cell Action:Check coverage plots, perform drive tests. Solution:Add new base station. You may like this Which Parameters helps to reduce TCH Congestion Rate? 2.Severe Congestion on the TCH Action:Check failed TCH allocation for assignment due to congestion. Check failed TCH allocation for handover due to congestion . Check TCH congestion.

3.Low Signal Strength for Call Access The signal strength might be higher on the BCCH than on the TCH. Action:Check signal strength of BCCH and TCH. Perform MTR recordings. Solution: Adjust and increase TCH output power.

4.Interference Interference, disturbance on SDCCH or target TCH frequency. Action:Check Interference. Solution:Improve frequency plan and decrease interference. 5.Faulty Transceiver Action:Check BTS Error Log. Solution:Replace or repair faulty equipment. 6.Low Output Power Action:Check set output power parameters and the actual transceiver output power. Solution: Increase output power or replace faulty transceiver.

Which Parameters helps to reduce TCH Congestion Rate in Huawei System?

Below mentioned parameters may cause TCH Congestion & also help you to reduce TCH Congestion:

1. TCH Traffic Busy Threshold(%) 2. RXLEV_ACCESS_MIN 3. SACCH Multi-Frames and Radio Link Timeout 4. SDCCH Dynamic Adjustment 5. RACH Min.Access Level 6. Speech Version 7. TCH Immediate Assignment 8. Speech Version 9. Fix Abis Prior Choose Abis Load Threshold 10. Assignment Cell Load Judge Enable 11. Flex Abis Prior Choose Abis Load Threshold

12. Directed Retry Load Access Threshold 13. Balance Traffic Allowed 14. Load HO Allowed 15. Load HO Step Period 16. Load HO Step Level 17. Cell Direct Try Forbidden Threshold 18. Direct Retry 19. SDCCH Dynamic Adjustment 20. Direct Retry and Cell Direct Try Forbidden Threshold 21. AMR TCH/H Prior Allowed 22. T3103 23. T3107 24. F2H HO th/ H2F HO th 25. Maximum Ratio Threshold of PDTCH

If any one knows other parameters for this kindly share. And if any one want to know how these parameters works please reply. Similar Threads:

How Antenna Hopping helps to increase receive gain? SD & TCH Congestion removal TIPS How to reduce SDCCH blocking? Huawei_Case Analysis Congestion

Above mentioned parameters are for Huawei System, name of the same may be vary from system to system, but its influence is same in the network. TCH Traffic Busy Threshold : When TCH Assignment Rate reaches or exceeds this threshold BSC starts to assigns halfrate channels. If this parameter is set to very small value there will e high TCH Congestion on the cell. However this parameter will increases channel usages rate & also degrades speech Quality. By increasing the value of this parameter we can get relief in congestion. RXLEV_ACCESS_MIN : This parameter specifies the minimum receive level of an MS to access the BSS. If this parameter is set to a too small value, some MSs with low receive levels may access the network and TCH congestion is likely to occur. You can set this parameter to a great value to reduce the TCH congestion rate. The counters such as call setup success rate and the counters related to traffic volume, however, are accordingly affected. SACCH Multi-Frames and Radio Link Timeout : SACCH Multi-Frames is parameter used in UPLINK & Radio Link Timeout(RLT) is used for DOWNLINK.

SACCH Multi-Frames : When the BTS receives the SACCH measurement report from the MS, the counter for determining whether a radio link is faulty is set to the value of this parameter. Each time the BTS fails to decode the SACCH measurement report sent by the MS, the counter decreases by 1. If the BTS successfully decodes the SACCH measurement report, the counter increases by 2. When the value of the counter is 0, the radio link fails.The BTS sends a connection failure indication message to the BSC.The judgment standard is whether the SACCH message is correctly decoded. Radio Link Timeout : This parameter specifies when an MS disconnects a call if the MS unsuccessfully decodes the SACCH message. Once a dedicated channel is assigned to the MS, the counter S is enabled and the initial value is set to this parameter value. Each time an SACCH message is not decoded, the counter S decreases by 1. Each time an SACCH message is correctly decoded, the counter S increases by 2.When the counter S is equal to 0, the downlink radio link is considered as failed.Therefore, when the voice or data quality is degraded to an unacceptable situation and it cannot be improved through power control or channel handover, the connection is to be re-established or released. When these parameter is set to very high value inspite of poor quality channel will be occupied and this will cause TCH Congestion. SDCCH Dynamic Adjustment : When no of users increases some users may not be able to access the network due to lack of SDCCHs. If this parameter is set to YES TCH will be converted into SDCCH. This will cause less no of TCHs & will increase TCH Congestion. RACH Min.Access Level : This parameter specifies the level threshold for the MS access. If this parameter is set to a too small value, some MSs with low signal levels may access the network and TCH congestion is likely to occur. You can set this parameter to a great value to reduce the TCH congestion rate. The counters such as call setup success rate and paging success rate, however, are affected.

Speech Version : This parameter contains 6 digits which should be set either to 0 or to 1. 1 means speech version is enable & 0 means speech version is disable. First three digit of this indicates Half Rate speech versions & last three digits indicates Full Rate speech version. First digit of both the half rate & full rate pair indicates AMR Half Rate & AMR Full Rate, second indicates Enhanced Half Rate(EHR) & Enhanced Full Rate (EFR), third digit indicates Normal Half Rate & Normal Full Rate. If your speech version is set to 111111 then all the speech versions are enable and if 1011111 means Enhance Half Rate is disable and rest all are enable. If this parameter is set to wrong value means if any digit is set to 0 and the same speech version is enable at MSC end then there will be problem during assignment procedure. And if half rate is disable in this parameter then there will be no half rate assignment in the cell.

TCH Immediate Assignment : If this parameter is set to YES then during assignment procedure if SDCCH isn't available then BSC directly assigns TCHs. If this parameter is set to NO then the attempt will blocked. This parameter helps to relieve congestion & improve Channel Assignment Success Rate. Fix Abis Prior Choose Abis Load Threshold : This parameter specifies the static Abis resource load threshold. When the static Abis resource load is lower than the value of Fix Abis Prior Choose Abis Load Thred(%), the TCHF is preferentially assigned. Otherwise, the TCHF or TCHH is preferred according to the dynamic Abis resource load. Flex Abis Prior Choose Abis Load Threshold : When the static Abis resource load is higher than the value of Fix Abis Prior Choose Abis Load Threshold(%) and the dynamic Abis resource load is higher than the value of Flex Abis Prior Choose Abis Load Threshold(%), the TCHH is preferred. Otherwise, the TCHF is preferred

Directed retry parameters Directed Retry Permitted : This parameter specifies whether to allow directed retry. In directed retry, a handover procedure is performed to hand over the MS to a neighbor cell. Directed retry is an emergency measure for abnormal peak traffic in the local wireless network. It is not a primary method of clearing traffic congestion. If directed retry is preformed frequently in a local network, you must adjust the TRX configuration of the BTS and the network layout. Directed Retry will be performed only if Assignment Cell Load Judge Enable is set to Yes. > Parameters Need to be tuned to enable DRT: 1. 2. 3. 4. 5. Directed Retry Permitted : YES Assignment Cell Load Judge Enable : YES Directed Retry Load Access Threshold : 80 Directed Retry Handover Level Range : 72 Cell Directed Retry Forbidden Threshold : 90

Directed Retry Load Access Threshold : This parameter is used to adjust candidate target cells for directed retry in HO Algorithm I. When target cells are selected during directed retry, only the cells whose loads are smaller than or equal to the Directed Retry Load Access Threshold are selected as candidate target cells.If the value of the parameter is too high, the cells with heavy loads are selected as candidate target cells so that the handover does not make sense. If the value of the parameter is too low, it is difficult to select candidate target cells. During directed retry, only the cells whose loads are smaller than or equal to Directed Retry Load Access Threshold are selected as candidate target cells. Cell Directed Retry Forbidden Threshold : If Assignment Cell Load Judge Enable is set to Yes, the

directed retry procedure is started if the following two conditions are met: The cell supports the directed retry procedure. The load of the cell is greater than or equal to the Cell Directed Retry Forbidden Threshold.

Directed Retry Handover Level Range : This parameter specifies the value range of the difference in the signal level between the neighbor cell and the serving cell when the directed retry procedure is triggered.

How to improve HOSR for a 2G system ?

methods other than neighbour tuning n all for improving HOSR for a cell.

I want to know the parameter which when altered produces quick and efficient improvement in HOSR ? Look there is direct relation between DL qual and HOSR So if you will be able to improve your DL qual than your HOSR will automaticaly improve. To improve DL qual you can refer How to improve DL RX Quality? One more to improve HOSR is to increase Handover timer T3103 in BSC.Make sure it should be less timer T10 atleast by 2 sec. You can also change thresold values of PbgtMargin,LevelMargin and Qualmargin to have some improvement. Also check if there are lot of intracell HO failures are there.Then check for the hardware issues or intracell HO thresolds. 1.HOSR is directly related to DL qual so improve network DL qual. How to improve DL RX Quality? 2. You can also increase timer T3103 in BSC.Make sure it should be less than T10 atlease by 2 sec. 3. Also check if there are lot of Intracell HO failures.Then check for Hardware issues or inracell HO theresolds. 4. Try to change PBGT,Qual and Level Margin and see any effect. 5. Check if MSC controlled HO's are getting failed. 6. Remove Co-BCCH,BSIC combination in neighbour. 7. Remove hardware alarms Below mentioned timers will help you to improve HOSR. T7 Timer for sending outgoing external inter-cell handover requests and handover commands

T8 Timer for running outgoing external inter-cell handover commands and handover completion or clearance T3103 From the time when an intra-cell or inter-cell handover command is executed to the time of an intra-cell or inter-cell handover completion T3105 During an asynchronous handover, from the time when the BTS sends the MS a physical message to the time when the BTS receives the set asynchronous balanced mode (SABM) from the MS T3124 During an asynchronous handover, from the time when the MS sends the network a handover access Burst message to the time when the MS receives a physical message from the BTS

How to improve TBF Drop?

There are several ways you can work for TBF Drop.

Check frequency in BBH and the retransmission rate in those cells. if high retransmission --> for sure there is problem on Frequency. Improve C/I (reduce interference) Try use most BCCH TRX TS for PDCH Make sure (E)GPRS link adaptation is enabled. If frequency change doesn't get good result limit the (E)GPRS coding scheme up to MCS7 instead of MCS9. MCS7 is more robust than MCS9 Reduce no. of users per PDCH Check PCU congestion/Utilization

GSM KPI Improvement Guide

Total Pages : 24 Table of Content ABSTRACT 1. INTRODUCTION 2. BTS STATISTICS 2.1 DESCRIPTION OF MEASUREMENTS 2.1.1 Intermittent Fault Measurement 2.1.2 TRA Synchronization Fault Measurement 2.1.3 Connection Statistics Measurement 2.2 BTS COUNTERS AND OBJECT TYPE 2.2.1 TRANSCEIVER GROUP 2.2.2 Timeslots 2.3 BTS STATISTIC AND FORMULA 2.4 CAPABILITIES 2.4.1 Object Type: MOTG 2.4.2 Object Type: MOTS 3. MOTS STATISTICS COLLECTION 3.1 COMMAND DESCRIPTION: RXMFP 3.2 EXECUTING THE RXMFP COMMAND 3.3 COUNTER SIZE

3.4 COLLECTING THE COUNTER STATISTICS 3.5 RECOLLECTION OF STATISTICS 4. DROPPED CALL RATE 4.1 DROPPED CALL RATE PER TIMESLOT 4.2 DROPPED CALL RATE PER TRX 5. TABULATING STATISTICS 5.1 COMMAND DESCRIPTION 5.1.1 Command description RXCDP 5.1.2 Command description RXHDP 5.2 TABULATING COUNTER VALUES FOR NON FREQUENCY HOPPING CELLS 5.3 TABULATING COUNTER VALUES FOR SYNTHESIZER HOPPING CELLS 5.4 TABULATING COUNTER VALUES FOR BASEBAND HOPPING CELLS 6. ANALYSIS OF TIMESLOT PERFORMANCE 6.1 FREQUENCY INTERFERENCE NON HOPPING 6.2 FREQUENCY INTERFERENCE SYNTHESIZER HOPPING 6.3 FREQUENCY INTERFERENCE BASEBAND HOPPING 6.4 HARDWARE FAULTY 7. SUMMARY 8. REFERENCE KPIs to be monitored

SD Blocking SD Drop TCH Blocking TCH Assignment TCH Drop HOSR Difference Between Blocking and Congestion Reasons for TCH Blocking Solutions for removal of TCH Blocking Reasons for TCH Assignment failure Solutions for removal of TCH Drop Reasons for HOSR Solutions for removal of HOSR

What is Call Drop? The TCH call drop rate refers to the ratio of call drops to successful TCH seizures after the BSC successfully assigns TCHs to MSs. The TCH call drop rate can be measured from the following aspects:

TCH call drop rate (including handover) TCH call drop rate (excluding handover)

Formulas for Call Drop including handovers: 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%

Formulas for Call Drop excluding handovers: TCH call drop rate (excluding handover) = Number of call drops on TCH/Number of successful TCH seizures (TCH) x 100% Parameter Check list for Call Drop: These parameters are common for all the vendors the only difference is its name will be different. The settings of some parameters on the BSC and MSC sides may affect the TCH call drop rate. If the following situations occur, the TCH call drop rate may increase: 1. The parameters SACCH Multi-Frames and Radio Link Timeout are set to too small values. 2. The parameter RXLEV_ACCESS_MIN is set to a too small value. 3. The parameter RACH Min.Access Level is set to a too small value. 4. The parameters Min DL Power on HO Candidate Cell and Min Access Level Offset are inappropriately set. 5. The length of timer T3103 (this timer is set to wait for a Handover Complete message) is set to a too small value. 6. The length of timer T3109 (this timer is set to wait for a Release Indication message) is set to a too small value. 7. The length of timer T3111 (this timer specifies the connection release delay) is set to a too small value. 8. The length of timer T305/T308 is set to an invalid or too great value. 9. 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. 22. If a repeater is used, the parameter Directly Magnifier Site Flag is set to No.
1. SACCH Multi-Frames This parameter determines whether an uplink radio link is faulty. Each time the BTS fails to decode the measurement report on the SACCH from the MS, the counter decreases by 1. Each time the BTS successfully decodes the measurement report on the SACCH, the counter increases by 2. When the value of this counter is 0, the BTS regards the radio link as faulty. In the traffic measurement, if there are many call drops (M3101A) related to radio link failure, you can infer that the radio propagation conditions are poor. In this case, you can set this parameter to a greater value. 2. Radio Link Timeout This parameter determines whether a downlink radio link is faulty. Each time the BTS fails to decode the measurement report sent over the SACCH by the MS, the counter decreases by 1. Each time the BTS successfully decodes the measurement report sent over the SACCH, the counter increases by 2. When the value of this parameter is 0, the BTS regards the radio link as faulty. In the traffic measurement, if there are many call drops (M3101A) related to radio link failure, you can infer that the radio propagation conditions are poor. In this case, you can set this parameter to a greater value. 3. RXLEV_ACCESS_MIN This parameter specifies the minimum receive level of an MS to access the BSS. If this parameter is set to a too small value, some MSs with low receive levels may access the network and call drops are likely to occur. You can set this parameter to a great value to reduce the TCH call drop rate. The counters such as call setup success rate and the counters related to traffic volume, however, are accordingly affected. 4. RACH Min.Access Level This parameter determines whether an MS can access the network over the RACH. If this parameter is set to a too small value, some MSs with low signal levels may access the network and call drops are likely to occur. You can set this parameter to a great value to reduce the TCH call drop rate. The counters such as call setup success rate and paging success rate, however, are affected. 5. Min DL Power on HO Candidate Cell and Min Access Level Offset The sum of the values of the two parameters specifies the minimum downlink receive level of a candidate neighboring cell for a handover. If this parameter is set to a too great value, some desired cells may be excluded from the candidate cells; if this parameter is set to a too small value, an unwanted cell may become the candidate cell. Both conditions may lead to the increase of call drops. 6. Timer T3103 series Timer T3101 series consists of T3103A, T3103C, and T8. These timers are started to wait for a handover complete message. If the lengths of the timers are set to small values, probably no message is received when timer T3103 series expires. In this case, the BSC considers that the radio link in the originating cell is faulty. Then, the BSC releases the channel in the originating cell. Thus, call drops occur. In the traffic measurement, if many call drops are related to handovers (CM331: Call Drops on Radio Interface in Handover State), you can set this parameter to a greater value. If this parameter is set to a too great value, channel resources are wasted and TCH congestion occurs. 7. Timer T3109 This parameter specifies the period for waiting for a Release Indication message after the BSC sends a Channel Release message to the BTS. If this parameter is set to a too small value, the

link may be released before the Release Indication message is received. As a result, a call drop occurs. You can set this parameter to a greater value to reduce the TCH call drop rate. It is recommended that timer T3109 be set to 12 seconds longer than timer Radio Link Timeout. 8. Timer T3111 This parameter specifies the interval between the time that the main signaling link is disconnected and the time that a channel is deactivated. The purpose is to reserve a period of time for repeated link disconnections. If this timer is set to a too small value, a channel may be deactivated too early. Thus, call drops increase. 9. Timers T305 and T308 Timers T305 and T308 are used on the MSC side. Timer T305 specifies the period during which the MSC monitors the on-hook procedure. Timer T308 specifies the period during which the MSC monitors the resource release procedure. You should set the two parameters when adding BSC data. Note that the modification of the data in the timer table does not take effect. If timers T305 and T308 are set to invalid or great values, the MSC clears the call a long time after the MS hangs up. After the T3103 and Radio Link Timeout timers expire, the number of call drops is increased and thus the TCH call drop rate is significantly affected. 10. TCH Traffic Busy Threshold If the current channel seizure ratio exceeds the value of this parameter, the BSC preferentially assigns a half-rate channel to a dualrate-enabled call. Otherwise, the BSC assigns a full-rate channel to the dualrate-enabled call. Compared with a full-rate channel, a half-rate channel has weak antiinterference capabilities. Therefore, if a large number of half-rate channels are assigned, the TCH call drop rate increases. It is recommended that this parameter should not be set to a too small value if congestion is unlikely to occur. 11. Call Reestablishment Forbidden This parameter specifies whether to allow call reestablishment. In case of burst interference or radio link failure due to blind areas caused by high buildings, call drops occur. In this case, MSs can initiate the call reestablishment procedure to restore communication. To reduce the TCH call drop rate, you can set this parameter to No to allow call reestablishment. In certain conditions, allowing call reestablishment greatly reduces the TCH call drop rate. Call reestablishment lasts for a long time, and therefore some subscribers cannot wait and hang up. This affects user experience. 12. Parameters related to edge handover When the receive level drops greatly, an edge handover cannot be performed in time in any of the following conditions: The parameter Edge HO UL RX_LEV Threshold or Edge HO DL RX_LEV Threshold is set to a small value; the parameter Inter-cell HO Hysteresis is set to a great value; the parameters Edge HO Watch Time and Edge HO AdjCell Watch Time are set to great values; the parameters Edge HO Valid Time and Edge HO AdjCell Valid Time are set to great values. As a result, a call drop occurs. To reduce the TCH call drop rate, you can appropriately set these parameters so that edge handovers can be performed in time to avoid call drops. 13. Parameters related to BQ handover When the signal quality deteriorates, a BQ handover cannot be performed in time in any of the following conditions: The parameters ULQuaLimitAMRFR, ULQuaLimitAMRHR, UL Qual. Threshold, DLQuaLimitAMRFR, DLQuaLimitAMRHR, and DL Qual. Threshold are set to great values; the parameter BQ HO Margin is set to a small value; the parameter Inter-cell HO Hysteresis is set to a great value. As a result, call drops occur. To reduce the TCH call drop rate, you should appropriately set these parameters so that BQ handovers can be performed in time to avoid call drops. 14. Parameters related to interference handover If the parameters RXQUAL1 to RXQUAL12 are set to

great values or if the RXLEVOff parameter is set to a great value, strong interference may occur. In this case, if interference handovers are not performed in time, call drops occur. To reduce the TCH call drop rate, you can appropriately set these parameters so that interference handovers can be performed in time to avoid call drops. If the parameters RXQUAL1 to RXQUAL12 are set to small values, the number of handovers due to other causes increases greatly, thus affecting the handover success rate. 15. Parameters related to concentric cell handover A call at the edge of the overlaid subcell cannot be handed over to the underlaid subcell in any of the following conditions: In the case of a normal concentric cell, the parameters RX_LEV Threshold and RX_LEV Hysteresis are set to great values; in the case of an enhanced concentric cell, the parameter OtoU HO Received Level Threshold is set to a great value. As a result, a call drop is likely to occur. If the Call Drop Ratio on TCH on the TRX in the OverLaid Subcell (RM330a) is high, you can appropriately set these parameters so that calls at the edge of the overlaid subcell can be handed over to the underlaid subcell in time. When a call in the underlaid subcell has interference, the call cannot be handed over to the overlaid subcell if the RX_QUAL for UO HO Allowed parameter is set to Yes and the RX_QUAL Threshold parameter is set to a great value. Thus, a call drop occurs. If the Call Drop Ratio on TCH on the TRX in the Underlaid Subcell (RM330) is high, you can set these parameters properly so that the call can be handed over to the overlaid subcell at the earliest. 16. Parameters related to power control If the power control level and quality threshold are set to small values, call drops are likely to occur because of low signal level or bad voice quality. 17. T200 and N200 If the parameters T200 FACCH/F, T200 FACCH/H, N200 of FACCH/Full rate, and N200 of FACCH/Half rate are set to small values, data links are disconnected too early. Thus, all drops are likely to occur. If call drops occur because of T200 expiry, you can increase the values of T200 and N200 properly. 18. Neighboring cell relations If the neighboring cells configured in the BA2 table are incomplete, call drops are likely to occur in the case of no suitable neighboring cell for handover and progressive deterioration in the voice quality. Neighboring cell relations should be configured completely on the basis of the drive test data and electronic map (for example, Nastar) to minimize the call drops due to no available neighboring cells. 19. MAIO If frequency hopping (FH) is applied in a cell and the MAIO is set inappropriately (for example, different TRXs serving the same cell have the same MAIO), frequency collision may occur during FH. Thus, the TCH call drop rate increases. 20. Disconnect Handover Protect Timer This parameter is a software parameter of the BSC. After receiving a DISCONNECT message from an MS, the BSC cannot hand over the MS within the period specified by this parameter. Therefore, the following case can be avoided: After being handed over to the target cell, the MS cannot be put on hook because it does not receive a release acknowledgement message. You are advised to set this parameter properly. 21. TR1N This parameter should be set on the MSC side. It is used to avoid the retransmission of short messages. When this parameter is set to a too great value, the MSC does not send a CLEAR CMD message if the MS receives a short message during link disconnection. As a result, the MS sends the BTS a DISC message to disconnect layer 2 connection. After receiving the DISC message, the BTS sends a REL_IND message to the BSC. Then, the BSC sends a CLEAR REQ message to the MSC and the number of

call drops is incremented by one. 22. Software Parameter 13 and MAX TA When the parameter Software Parameter 13 is enabled and the parameter MAX TA is set to a too small value, the channel is released when the TA of a call exceeds the MAX TA. In this case, call drops occur. It is recommended that the parameter Software Parameter 13 should not be enabled. 23. Directly Magnifier Site Flag If a BTS is installed with repeaters, the handover between repeaters can only be asynchronous because the distance between repeaters is long. If synchronous handovers are performed, the handovers may fail and thus many call drops occur. Therefore, when a BTS is installed with repeaters, the parameter Directly Magnifier Site Flag should be set to Yes to avoid asynchronous handovers between cells under the same BTS.

Description :

This measurement provides the number of call drops due to various reasons after the MS seizes a traffic channel. The MS seizures a TCH in any of the following conditions: The MS sends an ASS CMP message to the BSC; The MS seizes a TCH and sends an HO CMP message to the BSC.

Measurement Point : When a TCH is seized to carry traffic during a call, this counter is measured in the following situations: 1. The BSC receives an ERROR INDICATION message from the BTS because of the abnormal connection at the radio link layer. For details, refer to GSM Rec. 08.58. 2. The BSC receives a CONNECTION FAILURE INDICATION message from the BTS because of the radio link fault or hardware fault. For details, refer to GSM Rec. 08.58. 3. When receiving a DISC frame on a link layer connection in multi-frame mode, the BTS sends a REL IND message to the BSC. For details, refer to GSM Rec. 08.58. 4. The timer set to wait for an HO CMP message expires during internal intra-cell handover. 5. The timer set to wait for an HO CMP message expires during outgoing internal inter-cell handover. 6. The timer set to wait for an HO CMP message expires during outgoing external inter-cell handover. 7. The timer set to wait for an HO CMP message expires during incoming external inter-cell handover.

8. The BSC does not receive any measurement report within a certain period (by default, five minutes) and sends a CLEAR COMMAND message to the MSC to release the call. 9. The BSC detects a broken RSL and releases all the calls on the RSL. 10. A call drop occurs due to any of the following situations: TRX mutual aid; dynamic modification of cell attributes, TRX frequencies, or TRX FH data; dynamic deletion of cells or TRXs; blocking of cells, TRXs, or channels. 11. The timer set to wait for the outgoing BSC handover command expires, or the clear request message is received from the MSC before the timer expires. 12. A call drop occurs due to call assignment failure during the handover. 13. The MSC cannot send a short message because the data configuration prohibits the downlink short messages or because of flow control and the call is released. 14. A call drop occurs due to software error. 15. After seizing a channel, the MS fails to start a local switching due to terrestrial resource request failure, failures on the BTS side, or timer expiration. 16. During the handover of the call in the local switching state, the BSC releases the call after receiving a HANDOVER DETECT message from the BTS and then a HANDOVER FAILURE message from the MS. 17. After a call is in the BSC or BTS local switching state, if the local switching cannot be proceeded for handover or other reasons, the BSC restores the call to the common call state. If the restoration fails due to terrestrial resource request failure or other reasons, the BSC releases the call. CM33 Call Drop Cause Counter : CM330 : Call Drops on Radio Interface in Stable State (Traffic Channel) 1. Call Drops on TCH in Stable State (Error Indication)

Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (T200 Expired) Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Unsolicited DM Response) Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Sequence Error) Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (T200 Expired)

Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Unsolicited DM Response) Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Sequence Error)

1. Call Drops on Traffic Channel in Stable State (Connection Failure)

Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio Link Failure) Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (HO Access Failure) Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (OM Intervention) Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio Resource Unavailable) Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Other Causes) Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio Link Failure) Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (HO Access Failure) Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (OM Intervention) Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio Resource Unavailable) Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Other Causes)

1. Call Drops on Traffic Channel in Stable State (Release Indication)

Call Drops due to REL IND Received on TCHF (Traffic Channel) Call Drops due to REL IND Received on TCHH (Traffic Channel)

CM331 : Call Drops on Radio Interface in Handover State (Traffic Channel)

Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel) Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHF) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHH) (Traffic Channel)

CM332 : Call Drops due to No MRs from MS for a Long Time (Traffic Channel)

Call Drops due to No MRs from MS for a Long Time (TCHF) (TCH) Call Drops due to No MRs from MS for a Long Time (TCHH) (TCH)

CM333 : Call Drops due to Abis Terrestrial Link Failure (Traffic Channel)

Call Drops due to Abis Terrestrial Link Failure (TCHF) (TCH) Call Drops due to Abis Terrestrial Link Failure (TCHH) (Signaling Channel) Call Drops due to Abis Terrestrial Link Failure (TCHH) (TCH)

CM334 : Call Drops due to Equipment Failure (Traffic Channel)

Call Drops due to Equipment Failure (TCHF) (TCH) Call Drops due to Equipment Failure (TCHH) (TCH)

CM335 : Call Drops due to Forced Handover (Traffic Channel)

Call Drops due to Forced Handover (TCHF) (TCH) Call Drops due to Forced Handover (TCHH) (TCH)

CM397 : Call Drops Due to Loopback Start Failure

Call Drops due to BSC Loopback Start Failure (Terrestrial Resource Request Failure) Call Drops due to BSC Loopback Start Failure (Others) Call Drops due to BTS Loopback Start Failure (Terrestrial Resource Request Failure) Call Drops due to BTS Loopback Start Failure (Failures on the BTS Side) Call Drops due to BTS Loopback Start Failure (Others) Call Drops due to Loopback Start Failure (Timer Expired)

CM385 : Call Drops Due to Failures to Return to Normal Call from Loopback

Call Drops due to Failures to Return to Normal Call from BSC Loopback (Terrestrial Resource Request Failure) Call Drops due to Failures to Return to Normal Call from BTS Loopback (Terrestrial Resource Request Failure) Call Drops due to Failures to Return to Normal Call from BSC Loopback (Others) Call Drops due to Failures to Return to Normal Call from BTS Loopback (Others)

Astt. Manager RF
Alcatel-Lucent Public Company; 10,001+ employees; ALU; Telecommunications industry March 2009 Present (3 years 6 months) Mumbai Area, India

 Presenting weekly KPI status & improvement action plan with CTO on weekly basis. Presenting monthly KPI status & improvement plan with top management panel of ALUMS & RCOM Weekly audit of parameters & action plan for necessary changes. Weekly Neighbor & 2G external neighbor audit & suggest required changes in network. TCH Immediate assignment planning weekly basis based on traffic. BSC reohming planned based on BSC utilization. Managing all BBH contractual KPI on network (TCR, TASR, HOSR, Rx Qual (DL), SD Completion, TCH Congestion etc) Managing NI & NQI for RCOM GSM Path Imbalance, Traffic Balancing , Rx Quality, LU Traffic & Data traffic analysis Report generation & Report study from M-2000 (Huawei report generating tool) HO data, MR data, TA data, alarms & Rx Quality report study with report of M-2000 BSC Level & Cell Level parameter Audit & implementation. HO Parameter & Power control parameter implementation according to necessary & required changes based on traffic . Analysis & Action based on RAN report. NBR & BCCH Planning Changes in the RF database parameters in BSC level & Cell level. NL & BCCH updating on LMT BSC6000 Tool

Project Manager
Telecom Network Solutions India Pvt. Ltd. August 2008 February 2009 (7 months) Chennai Area, India Worked as project manager in TNS for IDEA, TATA DOCOMO, & BSNL WCDMA in Chennai, Tamilnadu circle with huawei as a Project Manager from 1st Augut 2008 to 28th Feb 2009. Done 900 sites RF Survey & Drive Test co-ordination & Project Monitoring for IDEA GSM Tamilnadu & Chennai Circle with in 5 months. Managed 24 teams for several project in Tamilnadu.

Worked in Reliance Communication as a RF Optimization Engineer for CDMA network as RF Optimization Engineer in Jaipur Rajasthan circle from 10th Feb 2008 to 31st July 2008.

Sr. RF Engineer
Reliance Communication Telecommunications industry

February 2008 July 2008 (6 months) Jaipur Area, India KPI monitoring & Improvement with help of Network Performance report. Network Optimization based on customer complaint & KPI. Coverage , Capacity & AOP Site planning for CDMA network. Voice CSSR, HO status, FCI updating. RAN report study Maintain TRAI Quarterly DATA for NHQ. Site Monitoring with Net term. Drive data post processing with Actix. Drive data processing with NTAS Analyzer. Finalizing EVDO drive data with the help of EVDO Drive logs. Co-ordinate with drive test, Cell and MSC teams for resolving network issues. Optimization Team Managing in Rajasthan for CDMA & GSM network in Jaipur.

RF Engineer
Telecom Network Solutions Private Limited Privately Held; 501-1000 employees; Telecommunications industry August 2005 January 2008 (2 years 6 months) India Worked as RF optimization Engineer for various project in Telecom Network Solution as a RF Engineer from 2nd Oct 2005 to 31st Jan 2008. Dimensioning. SDCCH dimensioning. LAC dimensioning based on paging load. Evaluating ongoing Design process and approving the location areas, BSC and RNC areas for optimal utilization of equipment. Dimensioning the interfaces between BSS elements (A, A-bis, A-ter) based on traffic analysis. Monitoring BSC-TRX loading. Monitoring BHCA and Processor Load of important nodes MSC, BSC, TRC & BTS are within safe limits. Designed MSC in POOL architecture for MUMBAI circle. Design Migration Plan (Monolithic to MSS Network) for 3G readiness and development strategy for rollout post award of 3G license RF Planning & Optimization (UMTS/HSPA). Planned 3G sites for Vodafone Mumbai based on current Data Usage, Input from marketing and Coverage requirement. 3G initial tuning and preparation for commercial launch

 Maintain and improvement KPI (Accessibility, Retainability, and Service Integrity) RF troubleshoot (reduce call drop; improve CCSR and CSSR, solve coverage issue, improving throughput and handoff (Intra, Inter and Inter-RAT HO)) Alarm monitoring and analysis Analysis of drive test data (Layer 3 Msgs), identify weak coverage/quality areas, call related issues (CS/PS setup time, Pilot pollution , interference Ec/No , missing neighbor , call drops, RAB Drops , RRC Setup Failure Issues , RAB establishment issues, IRAT Handover Problems , less throughput, rectification) of the same. Neighbour planning for 3G Sites, ensuring efficient plan of 3G-3G, 3G-2G, 2G-3G adjacency definitions, Audit 3G to 2G, 3G to 3G and 2G and 3G neighbour relationship. Perform troubleshoot for problematic cells and perform traces using Ericsson OSS tools which sites have a poor coverage, quality and low statistic performance with MOSHELL, OSS (GPEH,UETR and CTR), Statistic counters, UE Exception W-NCS, W-MRR and plot coverage & quality in MapInfo.

Sr ENGINEER - RNPO
Vodafone India Limited Public Company; 10,001+ employees; VOD; Telecommunications industry June 2008 June 2010 (2 years 1 month) Mumbai Area, India RF Planning & Optimization (GSM). (SOUTH MUMBAI) New sites rollout as per Spectrum limitation, capacity, customer complaints, suburban growth, etc Frequency planning and retune to avert interference and improve quality using FCS, SCHEMA tools. Neighbor and overshooting Analysis and tuning with RNO and SCHEMA tools. Monitor traffic congestion and developing capacity management procedures either by adding new carriers to the cell, by adding new sites after locating Hot Spots or by implementing features like Assignment to Other Cell, CLS, HCS, CHAP etc and forecasting future network expansion requirements for voice and data access network capacity based on Utilization, Marketing Forecasts, Special Events and Traffic Trends. Optimization of dual band cells using SCLD, DTCB, LOL parameters. Monitoring and improving KPI which includes TCR, SCR, UL/DL Quality, TASR, SASR, and HOSR. Optimization RF network using parameters (power control, IHO, locating algorithm) and implementing various features (EHOSR, EAC,), monitoring various alarms to achieve the KPIs. Monitoring and improving GPRS/EDGE KPI by tuning EDGE/GPRS parameters. Determine GPRS/EDGE parameter settings to enhance end-user experience like Single Phase Access for EGPRS, Active Queue Management, and Application Aware Timeslot Allocation. Swap Site (MOTOROLA TO ERICSSON) database preparation & auditing. Tested and implemented Assignment to Other Cell and HCS feature between two different

telecom operators. Implemented and tested BSS features of Motorolas like CR, ITS. Tested ERICSSONS high capacity BSC07B having APZ 212 55.

Deputy Manager
Reliance Communications Public Company; 10,001+ employees; RCOM; Telecommunications industry February 2008 June 2008 (5 months) MUMBAI NETWORK : GSM(1800) VENDORS : HUAWEI Coverage Priority & Antenna Placement Proposal Coverage area survey coordination and Proposal of coverage plan Nominal cell planning. Competitors network analysis and provide planning inputs Provide training on GSM Network Planning & Optimization basics

RF ENGINEER
ADA Cellworks Privately Held; 201-500 employees; Telecommunications industry September 2005 January 2008 (2 years 5 months) NETWORK : GSM(900,1800) OPERATORS : VODAFONE,IDEA,AIRTEL VENDORS : ERICSSON,NOKIA RF Planning & Optimization Responsible for RF Specifications of the sites including type of Antenna, Tower height to meet the coverage objective. Nominal cell planning (Data collection, capacity dimensioning and coverage calculation). Frequency planning using Map Info tool including Frequency hopping specifically Synthesizer Frequency Hopping (SFH), MAIO, HSN, MAL, MS, BCCH & BSIC Planning. Analyzing & rectifying Neighbor discrepancies, non-symmetrical Neighbor, adjacent CoBISC, Co- CH and Adj-CH neighbors. Tuning BSS parameters related to Handover, Power control, Location Update, Frequency, Neighbors relation etc. Taking care of congestion & blocking either by adding new carriers to the cell, by adding new sites after locating Hot Spots areas or by implementing new features like Directed Retry etc.

 Parameter Optimization by analyzing daily and weekly basis Cell Doctor & MML Command logs to meet desired KPIs which include DCR, SDR, Rx Quality for UL/DL, TCH and SD BLOCKING, HOSR etc. Implemented and tested BSS Optional features of Nokias like RF hopping with MAIO step size, C2 reselection etc. Post process Drive logs- Verify, Analyze & Generate Report Carry out Drive test using TEMS INVESTIGATION in idle/dedicated mode. In-Building Coverage Solution Finding the Existing Coverage Walk tests using TEMS Light 4.0.1. Site Survey for Equipment room, Risers, ceilings and Walls for implementation feasibility. Path Loss Considerations and Coverage Pattern description. Identifying & proposal of Priorities of the building. Designing the Link Budget (EIRP Chart) and Design layout. Proposing Antenna types, Locations and RF cables types. Optimized plan for minimizing spillage and Interference. Successfully completed various corporate IBS projects like Reliance industries Hazira Surat plant.

Phuoc Le's Overview

Current

Planing and Optimize for full network from A to Z at VNPT Technology

Past

Planing and Optimize for full network from A to Z at Viettel Group Planing and Optimize for full network from A to Z at Viettel Group

Education

University of Transport and Communication

Connections 97 connections

Phuoc Le's Education

University of Transport and Communication
Telecom Engineer, Electronic and Telecommunication Engineering

2001 2006

Phuoc Le's Summary

Overview knowledge: - Good knowledge, profound knowledge about technology on the mobile networks, mobile systems: GSM, UMTS, WCDMA, 4G, LTE ... - Profound knowledge about SS7 for telecommunication system. - Good knowledge about the structure of the BTS system, the mobile antenna. Experienced the implementation of In-Building systems for mobile broadcast systems. - Experienced product research. - Experienced coordination with customers and partners.

Phuoc Le's Experience

Planing and Optimize for full network from A to Z
VNPT Technology Government Agency; 10,001+ employees; Telecommunications industry December 2011 Present (9 months) Vietnam Team Leader for design&optimize projects: Mobifone, Vinaphone, Vietnamobile.

Planing and Optimize for full network from A to Z

Viettel Group September 2009 December 2011 (2 years 4 months) Vietnam Design and Optimization GSM, WCDMA, LTE Client: Viettel Vendor: Nokia Siemens,Huawei,Alcatel-Lucent,Motorola,Ericsson Resources: 6000 NodeB, 8500 BTS Responsibilities : - Perform the optimize project from A to Z. - Perform Site survey, Site Ranking, Site Acquisition, Technical Site Survey, Drive Test... - Dimensioning BSS(BSC,RNC, BTS, Node B, TRX, CE), Planning Frequency, SC, LAC, CI, RAC - Perform to optimize Pre-Launch and Post-Launch (WCDMA, GSM, GPRS, EDGE, HSDPA, HSUPA). - To Operate BSS HW, NSN, ALU, MT, Eric - Frequency & Scrambling Code planning and AFP strategy implementation. - Traffic dimensioning.

- Network densification. - Radio parameters optimisation , experience with WCDMA, HSDPA, HSUPA, EDGE, GPRS, GSM. - Daily Follow up of QoS indicators(KPI). - Monitor and optimize all the KPIs 2G/3G (CS and PS) relating to network quality in hour/day/week: CSSR, CDR, SDR, TCR, SCR, HOSR, HISR, PSR.... - Implementing necessary modifications to resolve eventual quality problems and improve the KPIs. - Mastery of radio optimisation tools (Example RNO-NPA, Netact, M2000, TESM Investigation, MapInfo, Piano, Planchecker). - Implementation of Follow up trail sessions for the improvement of the QoS and voice quality (HR Thresholds, Averaging window PBGT, Handover Margin, HSN, DR/FDR). - Implementation and Follow up of new features in the network (AMR, TFO, Fast Traffic HO). - Reporting of the results of the optimization sessions and the implementation of new features. - Conducting drive test team for specific and/or global measurements. - Post Processing of drive test log files and recommending changes. - Detailed analysis of log files using L3 messages. - Giving detailed description for call drop, Lost points. - Neighbor list optimization using information extracted from log files, and statics data. - Submitting detailed analysis report , generated using Tems Analyzer Post processing tool. - Guiding new joiners to analyze logs and recommending changes in parameters.

Planing and Optimize for full network from A to Z

Viettel Group August 2006 September 2009 (3 years 2 months) Vietnam Client: Viettel Vendor: Nokia Siemens, Huawei, Alcatel-Lucent, Motorola, Ericsson, ZTE... Resources: 5000 NodeB, 5500BTS Responsibilities : - Perform the planning & optimize project from A to Z. - Perform Site survey, Site Ranking, Site Acquisition, Technical Site Survey, Drive Test... - Dimensioning BSS(BSC,RNC, BTS, Node B, TRX, CE), Planning Frequency, SC, LAC, CI, RAC - Perform to optimze Pre-Launch and Post-Launch (GSM, GPRS, EDGE, WCDMA, HSDPA, HSUPA, LTE) Network. - To Operate BSS Nokia Siemens, Huawei, Alcatel-Lucent, Motorola, Ericsson, ZTE - Checking daily reports from OMCR and Analyzing the worst performing cells based on High drop call rate ,High handover failure ratio, TCH Blocking, Busy hour traffic, Poor call success rate, Poor uplink and downlink Quality in Network/BSC to improve the overall signed KPIs of the area classes (DenUrban, Urban, SubUrban & Rural). - Radio parameters optimisation , experience with EDGE, GPRS, GSM, WCDMA, HSDPA, HSUPA, LTE. - Frequency plan and neighbor list validation using MapInfo and Recommending BCCH

Frequency for the sites. - Planning of GSM/WCDMA Neighbor list addition and deletion using MapInfo, PlanChecker. - Performing Drive test using TEMS drive test tool for post processing and problem identification. - Planning frequency for new sites. - Monitor and optimize all the KPIs 2G/3G (CS and PS) relating to network quality in hour/ day / week: CSSR, CDR, SDR, TCR, SCR, HOSR, HISR, PSR.... - Handling of interference issues during Post-IOS drive test by change of frequency, BTS power control and fine tuning for functioning at optimum levels. C/I Analysis, interference Reduction (Adjacent & Co-channel Interference). - Analysis of drive test data for coverage and quality problems and offering appropriate solution for solving the RF related problems in the network. - Analyzing and optimizing worst performing cells report, KPI report monitoring .

Phuoc Le's Additional Information