Professional Documents
Culture Documents
Huawei Workshop
Troubleshooting Access Failures
Huawei Confidential
Contents
Call Setup Procedure (step by step & all protocols)
General Causes of failures How to chase and to solve specific access failures:
RRC Access Failure Troubleshooting.
Paging Access Failure Troubleshooting RACH Access Failure Troubleshooting
Huawei Confidential
Page 2
Node B
RNC
MSC / VLR
MGW
1. IAM
NBAP Start RX
NBAP
Here the RNC will perform a DRD decision and CAC decision for RRC
NBAP
NBAP
ALCAP
ALCAP
ALCAP
ALCAP
DCH-FP
9. DOWNLINK SYNCHRONISATION
DCH-FP
Can be either RRC Connection setup (to this cell and or inter freq to another one when DRD) or Reject.
DCH-FP
DCH-FP
Start TX
11. FACH: CCCH: RRC CONNECTION SETUP <UM> RRC L1 12. SYNCH IND L1 RRC
Here the UE will do DL synchronization (using N312=1, T312=1, N313=20 andT313=3) . Then the UE will start UL TX transmission and the Node-B will detect UL SYNCH (based on N_INSYNCIND=8, N_OUTOFSYNCIND=8,TRLFAILURE=20)
13. RADIO LINK RESTORE INDICATION NBAP
NBAP
Huawei Confidential
Page 3
19. SECURITY MODE COMMAND RANAP 20. SECURITY MODE COMMAND RANAP
RRC RRC
RANAP
RANAP
RRC
RRC
RRC
RRC 26. DT [ CALL CONFIRMED ] RANAP RANAP 27. BINDING ID, SPEECH CODE TYPE, B PARTY ROUTE
Here the RNC will perform a DRD decision and CAC decision for RAB
Huawei Confidential
Page 4
MSC / VLR
29. ESTABLISHMENT REQUEST ( AAL2 )
MGW
ALCAP
ALCAP
NBAP
NBAP
NBAP
NBAP
ALCAP
ALCAP
34. ESTABLISHMENT CONFIRM (AAL2) ALCAP 35. RADIO LINK RECONFIG COMMIT ALCAP
NBAP
NBAP
36. DCCH: RADIO BEARER SETUP <AM> RRC RRC 37. RAB ASSIGNMENT RESPONSE RANAP 38. DCCH: RADIO BEARER SETUP COMPLETE <AM> RANAP
RRC
RRC
39. DCCH: ULDT [ ALERTING ] <AM> RRC RRC 40. DT [ ALERTING ] RANAP 42. DCCH: ULDT [ CONNECT ] <AM> RRC RRC RANAP 41. ACM ISUP
43. DT [ CONNECT ] RANAP RANAP 44. OPEN CONNECTION 46. DT [ CONNECT ACK ] RANAP RANAP 47. ANS (CONNECT) RRC ISUP
Huawei Confidential
Page 5
Huawei Confidential
Page 6
Poor DL coverage. The fake coverage phenomenon (the user sees the 3G icon on the screen in
idle but cannot connect to any service). The cause could be overshooting cells but also excessive values of Qqualmin like -22 dB. Solution: Adjust the antenna azimuth and down tilt, add repeaters and RRUs, add micro cells. Any user should get a better signal than EcIo = -18 dB.
Lack of Dominance (no clear Best server): Continuous change of best server leads to
RRC failures and RAB failures.Solution: Establish a best server everywhere. Clear dominance.
Poor UL coverage: The UE has not enough TX power to communicate with Node-B (even when
there is low UL traffic on the cell). Solution: Adjust the antenna azimuth and down tilt, add repeaters, reduce CPICH power.
Strong UL interference: Due to external interference or high UL traffic (the cell shrinking
phenomenon). The UE will not be able to increase to more than 21 dBm for the preamble power and the RACH will fail - or synch will fail later. Solution: Up to operators decision (implement more tilt ,CPICH power reduction, chase external source of interference or increase the number of Node-Bs to cope with traffic)
Strong DL interference: Usually due to overshooting cell, external interference, high DL traffic
on this cell and surrounding cells. The UE will miss the AI message for RACH and will fail to establish a call - or will fail to get synch in DL. Solution: Improve best server area (strong dominance)
Antennas footprint not touching the ground properly: sites with over 120 m height and tilts around 3 degrees. More than 3/4 of the antenna pattern will not be touching the ground with a decent level of signal. Most calls are handled on side lobes. RF jumpers (feeding the antennas with RRU signal) are too long (should be no more than 3 meters, weve seen cases in --- with 10 meters of jumpers). This definitely leads to high noise factors and call setup failures. Also UL and DL coverage is very much limited.
Page 7
User experience: 3G icon, no 3G bar, no service accessibility. User s perception: Very negative.
The Fake coverage phenomenon (user gets the 3G icon on his screen in idle but either cannot pass an RRC or a RAB). Cause is overshooting cells but also excessive values of Qqualmin like -22 dB. Solution: Adjust the antenna azimuth and down tilt, add repeaters and RRUs, add micro cells, improve best server, change Qqualmin. Any user should get a better signal than EcIo=-18 dB. If this level cannot be achieved it is better to display no service on. user screen. User experience: 3G icon,3G signal User experience: 3G icon,3G signal
bar, good service accessibility. User s perception: Positive.
bars, great service accessibility. User s perception: Very Positive.
When -16>EcIo>-2 then RRC_SR>95%
Poor DL coverage.
Qqualmin
PRO
User always see the 3G icon on his phones screen (although its a fake coverage the user does not always attempt to use the service) Maximum traffic possible The user will not always have the 3G Icon on his phones screen (but when icon is present service is 100% accessible) Potential traffic decrease
CONS
Bad customer experience but less NW signalling. Not all call attempts are counted (not a clear perception of accessibility). Great and real customer experience but increased signalling (coverage lost); All Call attempts are counted (better performance perception of accessibility) due to this RRC_SR KPI may (or may not) be improved.
Comments
Will grab all extreme traffic leading quickly into DL Power congestion and accessibility issues.
-22 dB
-18 dB
-20 dB
Huawei Confidential
Page 8
Improper settings of access parameters: No discrepancies found in UCELLACCESSRESTRICT Inappropriate settings of preamble power ramp step and retransmission times: Current set of
parameters is NOK (PREAMBLERETRANSMAX=20, CONSTANTVALUE-20, PowerRampStep=2, Mmax=8).
Inappropriate setting of adjacent cells for UINTRAFREQNCELL: Qoffset1sn, Qoofset2sn out of the
range (-4dB;+4dB). Wrong settings for Sintra (like 0 dB), Sinter( also like 0 dB).
No discrepancies found for UL (DPCCH_Initial_Power = PCPICHPower - CPICH_RSCP + Uplink interference + DefaultConstantValue) and DL initial SIR target
Unsuitable setting of uplink Initial SIR target value of dedicated channel: No discrepancies found for
DL initial SIR Target
Huawei Confidential
Page 9
Transmission issues (fluctuating PATH, high BER, reduced capacity, routers down in the IP cloud). Alarms on cells, on Node-Bs, on RNC, on transmission Planning issues: traffic not properly shared between layers and NodeB, lack of a clear best server( no dominance), paging congestion due to LAC splitting issue. Radio Congestion: CE DL Power UL Power R99 Codes Iub bandwidth SPU bottleneck WMPT board bottleneck
Huawei Confidential
Page 10
Huawei Confidential
Page 11
YES
NO
If one time event, please wait one more day before to conclude. Could be a social event
YES
NO
If event one, go back to that day and see what was changed at that time and reconsider that change
YES
NO
If not, please review its best server area, tilt, azimuth and CPICH power
YES
NO
If no review your targeted coverage and accept current limitations and constraints due to location and/or number of Node-Bs.
YES
NO
If No, please do not expect a good RRC Success rate. If no (and footprint is on a plain terrain) please take immediate actions to increase downtilt. Antenna RF pattern is hardly touching the ground, users are handled on side lobes. DL Power issues will occur. If no, please do not expect a good RRC Success rate.
YES
NO
YES
NO
YES
NO
If no, please do not expect a good RRC Success rate with idleQoffset1sn>4dB
YES
NO
If no, please do not expect a good RRC Success rate with idleQoffset2sn>4dB
YES
NO
If no, please do not expect a good RRC Success rate with idleQhyst1>4dB
YES
NO
If no, please do not expect a good RRC Success rate with idleQhyst2>4dB
Huawei Confidential
Page 12
Sum of VS.RRC.Rej.Redir.Service
Sum of VS.RRC.Rej.ULIUBBand.Cong Sum of VS.RRC.Rej.ULPower.Cong Sum of VS.RRC.Rej.DLPower.Cong Sum of VS.RRC.Rej.DLIUBBand.Cong Sum of VS.RRC.Rej.ULCE.Cong Sum of VS.RRC.Rej.DLCE.Cong Sum of VS.RRC.Rej.Code.Cong Sum of VS.RRC.Rej.RL.Fail Sum of VS.RRC.Rej.TNL.Fail Sum of VS.RRC.FailConnEstab.Cong Sum of VS.RRC.Rej.Sum
0
0 14 135 0 1144 822 12 30 0 2343 2373
0
0 10 118 0 1352 11 41 50 0 1552 1602
0
0 0 1965 0 721 0 372 419 0 3070 3489
0
0 0 290 0 507 0 0 0 0 802 802
Sum of VS.RRC.SetupConnEstab
Sum of VS.RRC.FailConnEstab.NoReply Sum of RRC.SuccConnEstab.sum
Here are most of the RRC failures occurring indicating poor UL coverage (overshooting)
Conclusion: Most RRC failures (over 90%) are due to RRC no reply. For RRC issues, focus on overshooting cells first (to solve No reply), second on congested cells.
Huawei Confidential
Page 13
Identify if RRC failures for a cell are due to SPU : (check ADD NODEB command to find the SPU for a cell/Node-B) . NO
YES
SPU board is the issue when (VS.RRC.SuccConnEstabCPU / VS.RRC.AttConnEstabCPU) <97% (daily stats)
YES
VS.RRC.Rej.ULIUBBand.Cong VS.RRC.Rej.DLIUBBand.Cong
Solution: On the RNC LMT, run the PING IP command to the IP of the NodeB during failing hours. If packet loss rate is greater than 0.1% please contact transmission engineers (to troubleshoot or upgrade)
VS.RRC.Rej.ULPower.Cong
Check configuration(ULTOTALEQUSERNUM=160; NBMULCACALGOSELSWITCH=ALGORITHM_SECOND). Solution: Increase ULTOTALEQUSERNUM to 180. If still failing: add carrier or reduce/balance traffic to other layers/cells.
VS.RRC.Rej.DLPower.Cong
Check configuration :UPCPICH and MAXTXPOWER should be at least 10 dB between the 2 values. DLOLCTRIGTHD=95.DL_UU_OLC=0. Solution1:add carrier or reduce/balance traffic to other layers/cells Solution2: change NBMDLCACALGOSELSWITCH=ALGORITHM_THIRD
Identify if more than 10% of the failures for a cell are due to congestion :
Solution per cell: change ULTTICREDITSFRESTHD from SF8 to 4SF4. CE resources for admission is in congestion status the new admitted 2ms HSUPA terminals will be mapped onto the 10ms TTI radio bearer. 2ms TTI HSUPA users whose bit rate is below the threshold of TTI reconfiguration(800Kbps) will be reconfigured to 10ms TTI Solution per RNC: decrease ULGBR from 32 to 16 for specific services
VS.RRC.Rej.ULCE.Cong
NO
VS.RRC.Rej.DLCE.Cong
Solution per cell: ??? Solution per RNC: decrease DLGBR from 64 to 32 for specific services
VS.RRC.Rej.Code.Cong
Solution per cell is to activate Code reshuffling algo: in object UCELLALGOSWITCH change CELL_CODE_LDR to 1
Identify if more than 10% of failures for a cell are due to RL.Failure : GO TO NEXT SLIDE
VS.RRC.Rej.Rl.Fail
Solution 1: If failures correlated with VS.IUB.FailRLSetup.NoReply then it is WMPT board congestion( add UTRP Board) Solution 2: run the PING IP command on the IP of the NodeB to detect congestion on the IuB. Solution 3: If failures correlated with RLM.FailRLSetupIub.Cong then it is WBBP board congestion
Huawei Confidential
Page 14
YES
VS.RRC.Rej.TNL.Cong
Solution 1: Recheck configuration( IPPATHs of Nodeb has same capacity of transmission one;same for pair one) Solution 2: Run the PING IP command on the IP of the NodeB to detect congestion on the IuB.
YES
Solution 1: (After SPH226) MOD UCELLALGOSWITCH: CellId=xxxxx, RsvdPara1=RSVDBIT5-1; (will improve CS success rate, will degrade PS success rate) Solution 2: Offload traffic
NO
FACH Channel utilisation>80% Solution1: Offload traffic
Identify if more than 10% of failures for a cell are due to VS.RRC.FailConnEstab.NoReply :
YES
VS.MaxRTWP - VS.MeanRTWP > 10 dB
Solution 1: reduce HSUPA traffic Solution 2: Offload traffic Solution 3: Check external interference
Solution 1: Add important Neighbours Solution 2: Increase tilt to avoid risky overlaping footprints Solution 1 per RNC : modify RRC estab type to be on DCH SET URRCESTCAUSE:RRCCAUSE=TERMCAUSEUNKNOWN, SIGCHTYPE=DCH_3.4K_SIGNALLING, EFACHSWITCH=OFF; Take care as this will improve the RRC SR but will increase DL Power Solution 2 per RNC : stop SRB over HSDPA when DRD could be present SET UFRCCHLTYPEPARA, SRBCHLTYPE=HSUPA, SRBCHLTYPERRCEFFECTFLAG=TRUE
NO
If RRC Estab SR for whole RNC<99% and UU no reply is major cause
Please ask for HUAWEI support if after all those steps a cause for poor RRC failure could not be found
Huawei Confidential
Page 15
Top offending cell in xxx area with more than 10.000 RRC attempts per day: cell yyyyy .
Data Sum of VS.RRC.AttConnEstab.Sum Sum of Cell.RRC.Att.Fail Sum of VS.RRC.Rej.Redir.Service Sum of VS.RRC.Rej.ULIUBBand.Cong Sum of VS.RRC.Rej.ULPower.Cong Sum of VS.RRC.Rej.DLPower.Cong Sum of VS.RRC.Rej.DLIUBBand.Cong Sum of VS.RRC.Rej.ULCE.Cong Sum of VS.RRC.Rej.DLCE.Cong Sum of VS.RRC.Rej.Code.Cong Sum of VS.RRC.Rej.RL.Fail Sum of VS.RRC.Rej.TNL.Fail Sum of VS.RRC.FailConnEstab.Cong Sum of VS.RRC.Rej.Sum Sum of VS.RRC.FailConnEstab.NoReply Sum of VS.RRC.SetupConnEstab Sum of RRC.SuccConnEstab.sum RRC_SR
Here are most of the RRC failures occurring indicating poor UL coverage (overshooting)
cellID=yyyyy 73083 17110 0 0 0 163 0 0 0 0 0 0 163 163 16944 72920 55973 76.59%
Huawei Confidential
Page 16
2nd offending cell in xxx area with more than 10.000 RRC attempts per day: cell yyyyy
.
Data cellID=yyyyy Sum of VS.RRC.AttConnEstab.Sum 75048 Sum of Cell.RRC.Att.Fail 5324 Sum of VS.RRC.Rej.Redir.Service 0 Sum of VS.RRC.Rej.ULIUBBand.Cong 0 Sum of VS.RRC.Rej.ULPower.Cong 0 Sum of VS.RRC.Rej.DLPower.Cong 115 Sum of VS.RRC.Rej.DLIUBBand.Cong 0 Sum of VS.RRC.Rej.ULCE.Cong 0 Sum of VS.RRC.Rej.DLCE.Cong 0 Sum of VS.RRC.Rej.Code.Cong 0 Sum of VS.RRC.Rej.RL.Fail 0 Sum of VS.RRC.Rej.TNL.Fail 0 Sum of VS.RRC.FailConnEstab.Cong 115 Sum of VS.RRC.Rej.Sum 115 Sum of VS.RRC.FailConnEstab.NoReply 5208 Sum of VS.RRC.SetupConnEstab 74933 Sum of RRC.SuccConnEstab.sum 69724 RRC_SR 92.91%
Here are most of the RRC failures occurring indicating poor UL coverage (overshooting)
Huawei Confidential
Page 17
3rd offending cell in xxx area with more than 10.000 RRC attempts per day: cell yyyyy .
Data Sum of VS.RRC.AttConnEstab.Sum Sum of Cell.RRC.Att.Fail Sum of VS.RRC.Rej.Redir.Service Sum of VS.RRC.Rej.ULIUBBand.Cong Sum of VS.RRC.Rej.ULPower.Cong Sum of VS.RRC.Rej.DLPower.Cong Sum of VS.RRC.Rej.DLIUBBand.Cong Sum of VS.RRC.Rej.ULCE.Cong Sum of VS.RRC.Rej.DLCE.Cong Sum of VS.RRC.Rej.Code.Cong Sum of VS.RRC.Rej.RL.Fail Sum of VS.RRC.Rej.TNL.Fail Sum of VS.RRC.FailConnEstab.Cong Sum of VS.RRC.Rej.Sum Sum of VS.RRC.FailConnEstab.NoReply Sum of VS.RRC.SetupConnEstab Sum of RRC.SuccConnEstab.sum RRC_SR
Here are most of the RRC failures occurring indicating poor UL coverage (overshooting)
Huawei Confidential
Page 18
4th offending cell in xxxx area with more than 10.000 RRC attempts per day: cell yyyyy .
Data Sum of VS.RRC.AttConnEstab.Sum Sum of Cell.RRC.Att.Fail Sum of VS.RRC.Rej.Redir.Service
Sum of VS.RRC.Rej.ULIUBBand.Cong Sum of VS.RRC.Rej.ULPower.Cong Sum of VS.RRC.Rej.DLPower.Cong Sum of VS.RRC.Rej.DLIUBBand.Cong Sum of VS.RRC.Rej.ULCE.Cong Sum of VS.RRC.Rej.DLCE.Cong Sum of VS.RRC.Rej.Code.Cong Sum of VS.RRC.Rej.RL.Fail Sum of VS.RRC.Rej.TNL.Fail Sum of VS.RRC.FailConnEstab.Cong Sum of VS.RRC.Rej.Sum Sum of VS.RRC.FailConnEstab.NoReply Sum of VS.RRC.SetupConnEstab Sum of RRC.SuccConnEstab.sum RRC_SR
Here are most of the RRC failures occurring indicating poor UL coverage (overshooting)
Huawei Confidential
Page 19
Huawei Confidential
Page 20
2nd SCCPCH
Huawei Confidential
Page 21
Paging ocassion
Paging indicator
Huawei Confidential
PO= {(IMSI div K) mod (DRX cycle length div PBP)} * PBP + n * DRX cycle length + Frame Offset Where n = 0,1,2 as long as SFN is below its maximum value ,for FDD PBP=1 PI = DRX Index mod Np Where DRX Index = IMSI div 8192 If we consider particular settings: DRXcycle=7=>128 frames Frame offset =-7860 chips PBP=1 K=1 (theres only one S-CCPCH that carries PCH) PI=Np=36 PO= (IMSI)mod128+ n* 128 -7860 chips
PI=(IMSI/8192) mod36
Huawei Confidential
More bits inside a PI means a greater probability to decode the paging indicator but less capacity of the paging channel and power consumption for UE. Less bits means a lower probability for the UE to decode the paging indicator but longer battery life of the UE. Best solution is a mid-way one: PI=36.
Huawei Confidential
Huawei Confidential
Huawei Confidential
Page 26
Power_Ramp_Step :
Preamble_Initial_Power :
.
Preamble n
Preamble_Retrans_Max :
Pp-m :
Message part
Uplink/UE/PRACH
Preamble 1
AICH_Transmission_Timing
MMax Parameters for RACH/PRACH: NBO1( 0 NBO1min NBO1 NBO1max ) is the time between 2 ramping power of the preamble within the same preamble cycle. Preamble_Retrans_Max is the maximum number of preamble that can be sent in a cycle. Mmax is the maximum number of preamble cycles. Preamble_Initial_Power = Primary CPICH TX power CPICH_RSCP + UL interference + Constant Value Constant value is an initial value to start the first preamble power usually is -24. UL interference is the latest value broadcasted by the NodeB in SIB7. Ue needs to decode this value before being able to transmit RACH. Power_Ramp_Step is the how much the preamble power should be increased after each No ack received on AICH. Power offset P p-m = Pmessage-control Ppreamble, measured in dB, between the power of the last transmitted preamble and the control part of the random-access message. AICH_Transmission_Timing is the time when the RACH message must be transmitted after positive AICH was received( there are other parameters too) RACH is a common type transport channel in the uplink. RACHs are always mapped one-to-one onto physical channels (PRACHs), i.e. there is no physical layer multiplexing of RACHs, and there can only be one RACH TrCH and no other TrCH in a RACH CCTrCH. Service multiplexing is handled by the MAC layer. In one cell several RACHs/PRACHs may be configured. If more than one PRACH is configured in a cell, the UE performs PRACH selection RACH message mandatory parameters: -UE identity( IMSI,IMSI+LAI, TMSI, IMEI-when no USIM is inserted) -RRC establishment cause (31 causes) -radio bearer ID( AS or NAS, UM or TM or AM) -release5 indicator -measurements results on RACH(like EcNo of the serving cell).
Huawei Confidential
Page 27
Missing neighbours, lack of best server area and poor UL coverage influence a lot the RACH success rate.
Cell radius is now at 29.000 km. Make sure there are no UE from a larger distance(path distance) else will fail on RACH.
Spreaders inside the Node-B are limited. Multipath ( long distance) is not good for resource consumptions and so RACH messages might be missed.
Huawei Confidential
Preliminary conclusions
Most attempt failures are related to planning Plenty of attempts failures not recorded within the performance file (When EcIo is worse than -18 very few RACH reach the Node-Bs)
Huawei Confidential
Page 29
Thank you
www.huawei.com