What Are The Optimization Tools You Use?
What Are The Optimization Tools You Use?
What Are The Optimization Tools You Use?
1. UE uses the primary synchronization channel (P-SCH) for slot alignment (TS
synchronization).
UE issue.
o Etc.
Active set – the list of cells which are in soft handover with UE.
Monitored set – the list of cells not in active set but RNC has told UE to
monitor.
6. What are the major differences between GSM and UMTS handover
decision?
GSM:
UMTS:
e1a – a Primary CPICH enters the reporting range, i.e. add a cell to
active set.
e1b – a primary CPICH leaves the reporting range, i.e. removed a cell
from active set.
Events 2a-2d are for inter-frequency handover measurements and events 3a-3d are
for IRAT handover measurements.
e3a: the UMTS cell quality has moved below a threshold and a GSM
cell quality had moved above a threshold.
e3d: there was a change in the order of best GSM cell list.
Etc.
When access failure is high we can try the following to improve RACH performance:
11. What are the conditions you typically set to trigger IRAT handover?
RSCP ≤ -100dBm.
Ec/Io ≤ -16dBm.
12. What are the typical KPIs you use to measure a network and what
criteria?
Call setup time (CS: over 95% of the time < 6-second for mobile-to-
PSTN, 9-second for mobile-mobile. PS: over 95% of the time < 5-second).
Average DL/UL throughput for PSD: 210kbps for loaded, 240kbps for
unloaded.
What are the typical commands you have for CS and PS call?
Do you regularly stop and restart a new log file? Why and when to
stop and start a new file?
How do you stop a log file? Stop command sequence first, wait and
make sure all equipment are in idle mode before stop logging.
Missing 2G relations
Poor 2G Coverage
Missing 3G Relations
18. What is Paging Success Ratio? What is the typical PSR that you have
seen in a UMTS network?
About 90%
Very High ‘Periodic Location Update Timer’ – Keeping UEs in VLR long
time after it moved out of coverage
20. What are the possible causes for a Drop Call on a UMTS network?
Missing Neighbor
SC Collisions
Delayed Handovers
Loss of Synchronization
Fast Fading
Hardware Issues
External Interference
Study the Pilot spillover from the 3rd Tier SC and control its coverage
Even after controlling the coverage, if the spillover is there, Add the
neighbor.
Delayed Handover
Loss of Synchronization
Fast Fading
It can happen in the inter RNC boundaries where there is no Iur link.
24. What is the typical Call Setup Time for a 3G UE to 3G UE Call? What are
the possible RF related causes for a delayed CST in this type of call?
6 to 9 seconds
Typical Values are like 1.7 (Avg Active Set Size) or 35% (Secondary /
Total )
26. What will happen to the Soft Handover Overhead when you apply OCNS
on the network? And Why?
27. What are the possible causes for an Access Failure in UMTS?
Missing Neighbors
Poor Coverage
Hardware Issues
External Interference
System Ref Point for E/// NodeB is at the output of TMA (Between TMA
and Antenna)
3 dB and 5 dB respectively.
31. What will be the impact when you change ‘reportingrange1a’ from 3 to 4
dB and ‘timetotrigger1a’ 100 to 320 ms, without changing any other
parameters?
Related Articles
Every time a SACCH message can not be decoded the radio link time-out counter is
decreased by 1. If the message can be decoded the counter is incremented by 2.
However, the value can not exceed the initial value. The initial value is set by the
parameter RLINKT for radio link time-out in the mobile station and by RLINKUP for
timeout in the BSC. If the mobile moves out of coverage and no measurement
reports are received in the BSC, there will be a radio link time-out and the message
Channel Release (cause: abnormal release, unspecified) is sent to the mobile station
and the SACCH is deactivated in the BTS. A Clear Request message is sent to the
MSC. To be sure that the mobile has stopped transmitting, the BSC now waits
RLINKT SACCH periods before the timeslot is released and a new call can be
established on the channel.
Visit Out Forum For more Optimization Tips
2. Layer 2 Time-Out
If the BTS never get an acknowledge on a Layer 2 message after the time
T200XN200, the BTS will send Error Indication (cause: T200 expired) to the BSC,
which will send Channel Release (cause: abnormal release, timer expired) to the
mobile station and a Clear Request to the MSC. The SACCH is deactivated and the
BSC waits RLINKT SACCH periods before the timeslot is released and a new call can
use the channel. This is only valid if the call is in steady state, i.e. not during
handover or assignment.
3. Release Indication
When the BTS received a layer 2 DISC frame from the mobile it replies with a Layer
2 UA frame to the mobile station and a Release Indication to the BSC. The system
does only react on Release Indication if it is received during a normal disconnection
situation. If such a message is received unexpectedly this will usually cause radio
link time-out or timer T200 expiration as the mobile station stops the transmitting of
measurement reports. It is also possible that the release will be normal depending
on when the Release Indication is received.
4. MSC Time-Out
Normal Release:
If the MSC never received a response on a message (e.g. Identity Request) and
there is no radio link time-out or layer 2 time-out, the MSC will send a Clear
Command to the BSC. The time-out is depending on the message. When receiving
Clear Command, the BSC will send a Channel Release (cause: normal release) and
then deactivates the SACCH.
Reject (only SDCCH):
If the MSC never receives a response on the first message after Establish Indication,
the MSC will send a reject message. If the connection was a Location Update it will
be a Location Update Reject (cause: network failure) and if the connection was a
mobile originating call (CM Service Request) a CM Service Reject (cause: network
failure) will be sent. The MSC will then send a Clear Command to the BSC and the
call is cleared by Channel Release (cause: normal release).
5. Assignment to TCH
Before sending an Assignment Command from the BSC at TCH assignment, the
following two criterion have to be fulfilled:
a. There must be a TCH channel available, i.e. no congestion
b. The locating algorithm must have received at least one valid measurement report.
If either of the criterion is not fulfilled, Assignment Command will not be sent and a
Channel Release (cause: abnormal release, unspecified) will be sent to the mobile
station and a Clear Request to the MSC.
TCH Drop reason (1)
The classification of TCH Drop Reasons are arranged in the order of priority:
1.Excessive Timing Advance
2.Low Signal Strength
3.Bad Quality
4.Sudden Loss of Connection
5.Other Reasons
Action:
Check coverage plots.
Check output power.
Check power balance and link budget.
Check if Omni site.
Check antenna configuration & type.
Check antenna installation.
Perform drive tests & site survey.
Check TRX/TS with high CONERRCNT.
Solution:
Add a repeater to increase coverage in for example a tunnel.
Change to a better antenna (with higher gain) for the base station.
Add a new base station if there are large coverage holes.
Block/Deblock TRX
Solution:
Change BCCH frequency.
Change BSIC.
Change MAIO, HOP, HSN.
Change FHOP.
Record RIR or on-site Frequency Scanning to identify source of interference.
Use available radio features.
Action:
Check BTS Error Logs, Alarms and Fault Codes.
Check CONERRCNT per TRX and TS.
Check Transmission Link (A-bis).
Check for DIP Slips.
Check LAPD Congestion.
Correlate Handover Lost to Drops due to Sudden Loss
Solution:
Fix Hardware Faults and Alarms.
Reset TRX with high CONERRCNT.
Ensure that Synchronization and A-bis Link are stable.
Change RBLT with high DIP Slips.
Change CONFACT or increase Transmission Capacity
Investigate HO Lost Problem
TCH Drop Reasons (5)
TCH Drops due to Other Reasons
TCH drops due to Other Reasons are computed by subtracting the sum of drops due
to Excessive TA, Low SS, Bad Quality and Sudden Loss from the Total TCH Drop
Counts. Drops due to Other Reasons are generally associated with hardware
problems, transmission link problems on A-bis, Ater or Ainterfaces, and sometimes
Handover Lost.
Action:
Check BTS Error Logs.
Check Alarms and Fault Codes.
Check CONERRCNT per TRX and TS.
Check Transmission Link (A-bis).
Check for DIP Slips.
Correlate Handover Lost to Drops due to Other Reasons
Solution:
Fix Hardware Faults and Alarms.
Reset TRX with high CONERRCNT.
Ensure that Synchronization and A-bis Link are stable.
Change RBLT with high DIP Slips.
Investigate HO Lost Problem
Mobile Error
Some old mobiles may cause dropped calls if certain radio network features are
used. Another reason is that the MS is damaged and not working properly.
Action: Check MS fleet.
Solution: Inform operator.
Subscriber Behavior
Poorly educated subscribers could use their handsets incorrectly by not raising
antennas, choosing illadvised locations to attempt calls, etc.
Action: Check customer complaints and their MS.
Battery Flaw
When a subscriber runs out of battery during a conversation, the call will be
registered as dropped call due to low signal strength or others.
Action: Check if MS power regulation is used. Check if DTX uplink is used.
Congestion on TCH
The SDCCH is dropped when congestion on TCH.
Action: Check TCH congestion
Solution: Increase capacity on TCH or using features like Assignment to another
cell, Cell Load Sharing, HCS, Dynamic Half-Rate Allocation and FR-HR Mode
Adaptation etc
http://www.slideshare.net/mvaltonen/achieving-the-maximum-performance-of-baseline-
hsdpa-2590745
RTWP : Receive Total Wideband Power, reflects the total noise level within the UMTS
frequency band of one single cell.
Phenomenon Description : In project V in country B, when a single site is tested, the
HSUPA throughput in many cells cannot reach the required value (more than 500 kbps).
Alarm Information : The alarm RRU Rx Branch RTWP Difference Too High is
raised in some cells.
Cause Analysis : We suspected the RTWP was improper. The analysis is as follows:
HSUPA scheduling is based on the RTWP. The baseline value is –105.9 dBm, and no
interference exists by default. If any interference or other cause leads to the improper
RTWP, the HSUPA throughput is affected.
Handling Process :
1. We checked the RTWP in the cell with an improper HSUPA throughput on the RNC
LMT or NodeB LMT. The main branch and diversity branch are displayed on the NodeB
LMT, and the combination of the main branch and diversity branch is displayed on the
RNC LMT.
2. If the RTWP is greater than –100 dBm, we can basically determine the RWTP causes
the improper HSUPA throughput. If the RTWP is proper, we can, according to the related
guide, find other causes such as parameter configuration, cell state, and transmission
configuration.
3. When the RTWP is greater than –100 dBm, the HSUPA throughput is improper. The
cause is analyzed as follows: According to the current baseline configuration, the
maximum uplink target load is 75%, that is, a rise of 6 dB is allowed for the
background noise. The current baseline of the background noise is 61, the corresponding
RTWP is –105.9 dBm (–112 + 61/10).
Considering a rise of 6 dB, the RTWP is –99.9 dBm. That is, the RTWP reaches the
maximum threshold when no UE is accessed. The LST CELLCAC command can be used
to view the BackgroundNoise value.
4. After confirming the improper RTWP causes a low HUSPA throughput, we enabled the
automatic update switch for background noise with the command: MOD CELLCAC:
CellId=11111, BGNSwitch=ON; This function can automatically update the background
noise in a period every day, for example, 1:00 a.m. to 6:00 a.m. (default value). If the
RTWP is proper before, the automatic update switch for background noise can be enabled
to solve the problem.
5. If the problem is not solved after the automatic update switch for background noise is
enabled, to avoid affecting the project progress or acceptance, the following temporary
solution can be used to ensure that the acceptance of a single site is passed. The
fundamental cause for the problem is that the actual background noise differs from the
configured one. Therefore, it is necessary to manually set them to the same value.
The procedure is as follows:
1) Track the RTWP in the current cell at the RNC to obtain the current RTWP, for
example, CurrentRTWP.
Modify the background noise in the current cell with the following command:
MOD CELLCAC: CellId=11111, BackgroundNoise=(CurrentRTWP+112)*10;
Disable the automatic update switch for background noise.
2) After modification, test the HUSPA throughput at the place near to the cell. Generally,
the problem can be solved.
3) After testing, modify the background noise to the baseline value and enable the
automatic update switch for background noise.
The purpose of the temporary solution is to ensure that the acceptance of a single site can
be passed. The solution for an improper RTWP is the most fundamental, but it usually
takes a very long time.
Suggestions and Summary : After the preceding solution is applied to project V, the
HSUPA throughput is proper.
In practice, some causes may lead to an improper RTWP that affects the HSUPA
throughput. The preceding solution is applicable to such problem.