Professional Documents
Culture Documents
Access Failures Troubleshooting - WorkShop
Access Failures Troubleshooting - WorkShop
Access Failures Troubleshooting - WorkShop
Huawei Workshop
Troubleshooting Access Failures
Huawei Confidential
Contents
Huawei Confidential
Page 2
Node B
RNC
MSC / VLR
ISUP
MGW
1. IAM
2. PAGING
RANAP
RANAP
RRC
4. RACH: CCCH: RRC CONNECTION REQUEST <TM>
RRC
RRC
NBAP
NBAP
Start RX
NBAP
ALCAP
ALCAP
DCH-FP
9. DOWNLINK SYNCHRONISATION
DCH-FP
NBAP
ALCAP
ALCAP
DCH-FP
DCH-FP
Start TX
RRC
12. SYNCH IND
L1
NBAP
NBAP
RRC
Huawei Confidential
Page 3
Node B
RNC
MSC / VLR
MGW
RRC
SCCP
SCCP
17. SCCP CONNECTION CONFIRM
SCCP
SCCP
18. COMMON ID
RANAP
RANAP
RRC
RRC
RANAP
RRC
RRC
RANAP
RANAP
23. DT [ SETUP ]
RANAP
RRC
RRC
RANAP
RRC
RRC
26. DT [ CALL CONFIRMED ]
RANAP
RANAP
27. BINDING ID, SPEECH
CODE TYPE, B PARTY
ROUTE
Huawei Confidential
RANAP
Page 4
Node B
RNC
MSC / VLR
MGW
ALCAP
30. ESTABLISHMENT CONFIRM ( AAL2 )
ALCAP
NBAP
NBAP
ALCAP
ALCAP
NBAP
NBAP
ALCAP
NBAP
ALCAP
35. RADIO LINK RECONFIG COMMIT
NBAP
RRC
37. RAB ASSIGNMENT RESPONSE
RANAP
RRC
RANAP
RRC
RRC
40. DT [ ALERTING ]
RANAP
RANAP
41. ACM
ISUP
RRC
Terminating UEs
are considered to
be in a call after CC
Connect ACK
43. DT [ CONNECT ]
RANAP
RANAP
44. OPEN CONNECTION
46. DT [ CONNECT ACK ]
RANAP
RANAP
RRC
ISUP
Huawei Confidential
Page 5
RF Reasons
Radio Parameter Problems
Miscellaneous causes
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.
Huawei Confidential
Page 7
Poor DL coverage.
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
Qqualmin
PRO
CONS
Comments
-22 dB
-18 dB
-20 dB
Huawei Confidential
Page 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).
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
Should be done daily (automatically and network wide) based on a defined template.
YES
NO
Every morning there should be an email with cells unavailable on previous day and
duration of unavailability.
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
Is this cell having full overlapping with other neighbouring cells? ( i.e.
there's no direction user can move without having good coverage). Is
any user, in any indoor environment within the footprint of this cell,
able to get a decent RSCP and EcIo?
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
YES
NO
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.
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.AttConnEstab.Sum
Sum of Cell.RRC.Att.Fail
46702
73768
87275
12471
Sum of VS.RRC.Rej.Redir.Service
Sum of VS.RRC.Rej.ULIUBBand.Cong
Sum of VS.RRC.Rej.ULPower.Cong
14
10
Sum of VS.RRC.Rej.DLPower.Cong
135
118
1965
290
Sum of VS.RRC.Rej.DLIUBBand.Cong
Sum of VS.RRC.Rej.ULCE.Cong
1144
1352
721
507
Sum of VS.RRC.Rej.DLCE.Cong
822
11
Sum of VS.RRC.Rej.Code.Cong
12
41
372
Sum of VS.RRC.Rej.RL.Fail
30
50
419
Sum of VS.RRC.Rej.TNL.Fail
Sum of VS.RRC.FailConnEstab.Cong
2343
1552
3070
802
Sum of VS.RRC.Rej.Sum
2373
1602
3489
802
Sum of VS.RRC.SetupConnEstab
Sum of VS.RRC.FailConnEstab.NoReply
Sum of RRC.SuccConnEstab.sum
71818
Huawei Confidential
11667
83566
Page 13
YES
NO
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
Identify if more than 10% of the failures for a cell are due
to congestion :
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong
NO
VS.RRC.Rej.Rl.Fail
GO TO NEXT SLIDE
Huawei Confidential
Page 14
YES
VS.RRC.Rej.TNL.Cong
NO
Identify if more than 10% of failures for a cell are due to
FACH congestion :
YES
VS.RRC.AttConnEstab.Msg
>>
VS.RRC.AttConnEstab.Sum
VS.CellFACHUEs>25
VS.CRNCIubBytesFACH.Tx or
VS.CRNCIubBytesPSR99.CCH.Tx
are flat in time( limited)
NO
YES
VS.MaxRTWP - VS.MeanRTWP >
10 dB
NO
If RRC Estab SR for whole
RNC<99% and UU no reply is
major cause
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
Huawei Confidential
Page 16
cellID=yyyyy
73083
17110
0
0
0
163
0
0
0
0
0
0
163
163
16944
72920
55973
76.59%
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%
Huawei Confidential
Page 17
Huawei Confidential
Page 18
cellID=yyyyy
39512
2602
0
0
0
0
0
0
0
0
0
0
0
0
2602
39512
36910
93.41%
cellID=yyyyy
75162
3583
0
Sum of VS.RRC.Rej.ULIUBBand.Cong
Sum of VS.RRC.Rej.ULPower.Cong
Sum of VS.RRC.Rej.DLPower.Cong
0
0
439
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
0
4
0
0
443
443
Sum of VS.RRC.FailConnEstab.NoReply
Sum of VS.RRC.SetupConnEstab
Sum of RRC.SuccConnEstab.sum
RRC_SR
Huawei Confidential
Page 19
3137
74719
71579
95.23%
Huawei Confidential
Page 20
2nd SCCPCH
Huawei Confidential
Page 21
Paging
ocassion
Paging
message
(3 IMSI or
5 TMSI)
Paging
indicator
Huawei Confidential
PI number of paging indicators per radio frame. 3GPP allows values 18,38,72,144. It is broadcasted in Sysinfo5: PI-countperframe
SFN of the P-CCPCH where the PICH frame started. The SFN is known by UE immediately after synchronization with P-CCPCH. SFN range is from 0 to
4096.
K number of S-CCPCH and can be found in Sysinfo5 . Usually 1 or 2 ( same like in GSM combined or non-combined BCCH).
DRX cycle. UE will use the DRX=min (DRXPS,DRXCS). DRX cycle is broadcasted in Sysinfo1: cn-DRX-CycleLengthCoefficient (2 values broadcasted,
one for each CN domain)
Frame offset =Ts-ccpch,k Tpich (see previous slide). Ts-ccpch,k = Tk 256 chip, Tk {0, 1, , 149} and can be found in Sysinfo5: and it is called
timming offset. For particular UTRAN timming offset=0(S-CCPCH and P-CCPCH are time aligned). Tpich = 7680 chips as a fix value forced by 3GPP.
A paging indicator set to 1 indicates that the UE should read the S-CCPCH of the corresponding frame.
Total number of chips in one 10msec radio frame is 38400. PICH channel can transmit (38400/256) 150 indicator modulation symbols or (150X2) 300 bits. Only the
first 288 of these are used, leaving the last 12 bits undefined
More details in 3GPP specs: 25.211-700 and in 25.331-710 RRC protocol specification
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=(IMSI/8192) mod36
Huawei Confidential
A group of bi=1 means theres a paging and UE should read its very first paging occasion.
A group of bi=0 means theres no paging and UE could go back to idle till next paging indicators.
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
Enough performance
counters
Huawei Confidential
Page 26
Power_Ramp_Step :
Preamble_Initial_Power :
Uplink/UE/PRACH
Preamble 1
Pp-m :
Message
part
Preamble n
AICH_Transmission_Timing
Preamble_Retrans_Max :
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
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.
Huawei Confidential
Preliminary conclusions
Huawei Confidential
Page 29
Thank you
www.huawei.com