nemo l3 analysis external v03

1 © 2005 Nokia Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

Company Confidential

L3 ANALYSIS / OPTIMIZATION EXAMPLESL3 ANALYSIS / OPTIMIZATION EXAMPLES(Using (Using NemoNemo Outdoor)Outdoor)

05 November 200505 November 2005Nokia NetworksNokia NetworksOSP, TaiwanOSP, TaiwanVersion 0.1 (Internal) / Version 0.3 (External)Version 0.1 (Internal) / Version 0.3 (External)



Objective of Case StudiesObjective of Case Studies

•• Objective of this Objective of this slidesetslideset package is to consolidate all the package is to consolidate all the learningslearnings of L3 of L3 analysis / troubleshooting via using analysis / troubleshooting via using NemoNemo Analyzer or Analyzer or NemoNemo Outdoor Playback.Outdoor Playback.

•• This package would serve as a practical teaching guide / competeThis package would serve as a practical teaching guide / competence transfer nce transfer to Partnerto Partner’’s L3 analyst who would be performing all subsequent L3 analysis s L3 analyst who would be performing all subsequent L3 analysis for for Initial Tunings, Cluster, SubInitial Tunings, Cluster, Sub--Area, Area Tunings etc optimization works.Area, Area Tunings etc optimization works.

•• The package is split into 2 main sections:The package is split into 2 main sections:•• CAD Case StudiesCAD Case Studies•• CAF Case StudiesCAF Case Studies



Customized Customized NemoNemo Workspace & Color SetsWorkspace & Color Sets

•• NemoNemo Workspace for v4.15.24:Workspace for v4.15.24:•• (this may not work for v.25)(this may not work for v.25)•• NemoNemo Color Set:Color Set:

•• Best practice suggestion Best practice suggestion ––•• Always open *.dt1 & *.dt2, together with *.fs3 measurement data Always open *.dt1 & *.dt2, together with *.fs3 measurement data files. This would let the files. This would let the

analyst have a sanity check if the radio environment is affectinanalyst have a sanity check if the radio environment is affecting both g both UEsUEs or not e.g. or not e.g. Especially when trying to apply Especially when trying to apply AdjsEcNoOffsetsAdjsEcNoOffsets in cases of rapidly degrading CPICH in cases of rapidly degrading CPICH EcEc/No /No quality situations. And the scanner data would be used for missquality situations. And the scanner data would be used for missing neighbor detection, pilot ing neighbor detection, pilot pollutions and etc L1 optimization purposes. pollutions and etc L1 optimization purposes.

•• Always have the RNC Border MI layer opened in the map section. SAlways have the RNC Border MI layer opened in the map section. So that the Analyst would o that the Analyst would have a clear idea of the Interhave a clear idea of the Inter--RNC SHO cases and in case SRNS relocation failures. RNC SHO cases and in case SRNS relocation failures.

•• Always work with L1 analyst to feedback / cross check with each Always work with L1 analyst to feedback / cross check with each other.other.

CHT_Thruput_ColorSet.csf

v22_rlim_default1_6650_gst_080105_rlim_Voice+PS.worv22_rlim_default1_6630_gst_080505_rlim_Voice+PS.wor



Information Required for L3 Analysis / OptimizationInformation Required for L3 Analysis / Optimization

•• NemoNemo measurement data logs (off course)measurement data logs (off course)•• 3G Site Master Configuration Database 3G Site Master Configuration Database •• Daily WBTS Block Cell States report from NMC (However, this onlyDaily WBTS Block Cell States report from NMC (However, this only provides a provides a

static snapshot at the end of the day. Unless the BTS is down fostatic snapshot at the end of the day. Unless the BTS is down for whole day, this r whole day, this report does not show the site being down for a short duration dureport does not show the site being down for a short duration due to whatever e to whatever problem. Analyst is advised to check Daily BTS Alarm History repproblem. Analyst is advised to check Daily BTS Alarm History report for such ort for such details)details)

•• Daily BTS Alarm History reports from NMCDaily BTS Alarm History reports from NMC



Drop Call (CAD) Case StudiesDrop Call (CAD) Case Studies

•• Missing Missing NeighboursNeighbours•• Interference Interference •• MR e1x with No ASU ResponseMR e1x with No ASU Response•• No MR after Last MCNo MR after Last MC•• InterInter--RNC SRNS Relocation RNC SRNS Relocation –– Success CaseSuccess Case•• InterInter--RNC SRNS Relocation RNC SRNS Relocation –– Failure CaseFailure Case•• IntraIntra--Frequency Frequency HardhandoverHardhandover (HHO)(HHO)•• DL RRC Connection Release with Release Cause DL RRC Connection Release with Release Cause ““UnspecifiedUnspecified””•• ………………. .



Call Setup Failure (CAF) Case StudiesCall Setup Failure (CAF) Case Studies

•• FMT tool related: FMT tool related: NemoNemo CAA=15sec timeout or expiredCAA=15sec timeout or expired•• Missing Missing NeighbourNeighbour relatedrelated•• Network relatedNetwork related•• …………..



UMTS Basic Call Signaling

System Information Block (SIB)Location UpdateVoice MOC/MTCPS Data CallMulti RABSHO



System Information Block (SIB)System Information Block (SIB)

Information BlockInformation Block DescriptionDescription

MIBMIB PLMN types & identitiesPLMN types & identitiesScheduling informationScheduling informationSIB referencesSIB references

SB1SB1 Optional SIB scheduling informationOptional SIB scheduling information

SIB1SIB1 NAS informationNAS informationUE timers & counters to be used in idle and connected modeUE timers & counters to be used in idle and connected mode

SIB2SIB2 URA identity listURA identity list

SIB3SIB3 Cell selection and reCell selection and re--selection parametersselection parameters

SIB5SIB5 Parameters for common physical channel configurationParameters for common physical channel configuration

SIB7SIB7 UL interference levelUL interference levelDynamic persistence levelDynamic persistence level(fast changing parameters)(fast changing parameters)

SIB11SIB11 Measurement control information to be used in the cellMeasurement control information to be used in the cellNeighbour list.Neighbour list.

SIB18SIB18 PLMN identities of neighboring cells to be considered in idle moPLMN identities of neighboring cells to be considered in idle mode as well as in de as well as in connected mode.connected mode.



System Information Block (SIB)System Information Block (SIB)



Location Update(LU)Location Update(LU)

RRC Connection Stage

Authentication Stage

Location Update Request

Location Update Accept

RRC Connection Release



AMR MOCAMR MOC

Call Setup Success

Disconnect and Release Procedure

RRC Connection Setup

Authentication Procedure

Radio Bearer Setup Procedure



AMR MOCAMR MOCUE BTS RNC CS_CN

RRC_Connection_Request

RRC_Connection_Setup

RRC_Connection_Setup_Complete

CM_Service_Request

Setup

Call_Proceeding

Radio_Bearer_Setup

Radio_Bearer_Setup_Complete

Alerting

Connect

Connect_Acknowledge

Authentication_Request

Authentication Response

Security_Mode_Command

Security_Mode_Complete



AMR MOCAMR MOC

MS BTS CS_CNRNC

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RRC:RRC CONNECTION SETUP

NBAP:SYNCHRONIZATION INDICATION

RRC:CONNECTION SETUP COMPLETE

RRC:INITIAL DIRECT TRANSFER (CM Service Request)

RANAP:INITIAL UE MESSAGE(CM Service Request)

RANAP:RAB ASSIGNMENT REQUEST

Call established

L1 synchronisation

AAL2SIG: ERQ

AAL2SIG: ECF

RANAP: DIRECT TRANSFER

(CM Service Accept)RRC: DOW NLINK DIRECT TRANSFER (CM Service Accept)

RRC: UPLINK DIRECT TRANSFER (Setup)


(Setup)


(Call Proceeding)RRC: DOW NLINK DIRECT TRANSFER (Call Proceeding)

NBAP:RADIO LINK RECONFIGURATION PREPARE

NBAP:RADIO LINK RECONFIGURATION READY

AAL2SIG: ERQ

AAL2SIG: ECFAAL2SIG: ERQ

AAL2SIG: ECF

NBAP:RADIO LINK RECONFIGURATION COMMIT

RRC: RADIO BEARER SETUP

RRC: RADIO BEARER SETUP COMPLETE

RANAP:RAB ASSIGNMENT RESPONSE


(Alerting)RRC: DOW NLINK DIRECT TRANSFER (Alerting)

RRC: UPLINK DIRECT TRANSFER (Connect)


(Connect)

(Connect Acknowledge)RRC: DOW NLINK DIRECT TRANSFER (Connect Acknowledge)


BTS CS_CNRNC

Call established

NBAP:RADIO LINK DELETION REQUEST

RRC:CONNECTION RELEASE

Call released

AAL2SIG: RLC

AAL2SIG: REL

MS

RRC: DOW NLINK DIRECT TRANSFER (Disconnect)


(Disconnect)


(Release)RRC: UPLINK DIRECT TRANSFER (Release)

RRC: DOW NLINK DIRECT TRANSFER (Release complete)


RANAP: Iu RELEASE COMMAND

(Release complete)

RANAP: Iu RELEASE COMPLETE

RRC:CONNECTION RELEASE COMPLETE

NBAP:RADIO LINK DELETION RESPONSE

AAL2SIG: REL

AAL2SIG: RLC

Note: Authentication & Security Mode Procedures Are switched off in thisReference signalling flow



MTC (AMR)MTC (AMR)



MTCMTCMS BTS CS_CNRNC







RRC:INITIAL DIRECT TRANSFER (Paging response)

RANAP:INITIAL UE MESSAGE(Paging response)


Call established

L1 synchronisation

AAL2SIG: ERQ

AAL2SIG: ECF

RRC: DOW NLINK DIRECT TRANSFER (Setup)

RRC: UPLINK DIRECT TRANSFER (Call confirmed)


(Setup)


(Call confirmed)



AAL2SIG: ERQ

AAL2SIG: ECF

AAL2SIG: ERQ

AAL2SIG: ECF






(Alerting)

RRC: UPLINK DIRECT TRANSFER (Alerting)

RRC: DOW NLINK DIRECT TRANSFER (Connect)RANAP: DIRECT TRANSFER

(Connect)

(Connect Acknowledge)

RRC: UPLINK DIRECT TRANSFER (Connect Acknowledge)


RANAP:PAGINGRRC:PAGING TYPE 1

Note: Authentication & Security Mode Procedures Are switched off in thisReference signalling flow



PS DATA CALLPS DATA CALLRRC Connection Setup

Attach & Authentication Procedure

PDP Context Activation & Radio Bearer Setup Procedure

Radio Bearer Reconfiguration

PDP Context Deactivation Procedure

Detach & Radio Bearer Release Procedure

RRC Connection Release



PS DATA CALLPS DATA CALLUE BTS RNC PS_CN

RRC_Connection_Request

RRC_Connection_Setup

RRC_Connection_Setup_Complete

Attach_Request

Authentication_n_Ciphering Request

Authentication_n_Ciphering Response

Security_Mode_Command

Security_Mode_Complete

Attach_Accept

Attach_Complete

Activate_PDP_Context_Request

Radio_Bearer_Setup

Radio_Bearer_Setup_Complete

Activate_PDP_Context_Accept

Radio_Bearer_Reconfiguration

Radio_Bearer_Reconfiguration_Complete



PS DATA CALLPS DATA CALL

MS BTS PS_CNRNC







RRC:INITIAL DIRECT TRANSFER (Attach Request)

RANAP:INITIAL UE MESSAGE(Attach Request)


Uplink and downlink data transfer

L1 synchronisation

AAL2SIG: ERQ

AAL2SIG: ECF


(Attach Accept)RRC: DOWNLINK DIRECT TRANSFER (Attach Accept)

RRC: UPLINK DIRECT TRANSFER (SM:Activate PDP Context request)


(SM: Activate PDP Context request)


(SM: Activate PDP Context accept)RRC: DOWNLINK DIRECT TRANSFER (SM: Activate PDP Context Accept)



AAL2SIG: ERQ

AAL2SIG: ECF





RRC: TRANSPORT CHANNEL RECONFIGURATION

RRC: MEASUREMENT REPORT

RRC: TRANSPORT CHANNEL RECONFIGURATION COMPLETE

RRC: DOWNLINK DIRECT TRANSFER (Attach Complete)


(Attach Complete)

BTS CS_CNRNC

PDP Context is active

NBAP:RL DELETION REQUEST

AAL2SIG: RLC

AAL2SIG: REL

MS

RRC: DT (Deactivate PDP context request)RANAP: DT (Deactivate PDP context request)

RANAP: DT (Deactivate PDP context accept)

(Release)

RRC: DT (Deactivate PDP context accept)

RRC: RADIO BEARER RELEASE

RANAP: RAB ASSIGNMENT REQUEST

RRC:RADIO BEARER RELEASE COMPLETE

NBAP:RL DELETION RESPONSE

AAL2SIG: REL

AAL2SIG: RLC

NBAP:RL RECONFIGURATION PREPARE

NBAP:RL RECONFIGURATION READY

RANAP: RAB ASSIGNMENT RESPONSE

NBAP:RL RECONFIGURATION COMMIT

RRC: DT(Detach request)

RANAP: DT(Detach request)

RANAP: DT(Detach accept)RRC: DT(Detach accept)

RANAP: Iu Release Command

RANAP: Iu Release CompleteRRC: RRC CONNECTION RELEASE

RRC: RRC CONNECTION RELEASE COMPLETE



Multi RAB (Simultaneous AMR+PS)Multi RAB (Simultaneous AMR+PS)

AMR

PS

PS Disconnect

AMR Disconnect



SHO_e1aSHO_e1a

UE BTS RNC

Handover tresholds fulfilled (MEHO)- Event 1A is triggered

RRC: Active Set Update Request

RRC: Measurement Report

NBAP: Radio Link Addition Response

NBAP: Radio Link Addition Request

RRC: Active Set Update Complete

NBAP



SHO_e1bSHO_e1b

UE BTS RNC

Handover tresholds fulfilled (MEHO)- Event 1B is triggered


RRC Measurement Report


NBAP: Radio Link Deletion Request

NBAP: Radio Link Deletion Response



SHO_e1cSHO_e1c

UE BTS RNC

Handover tresholds fulfilled (MEHO)- Event 1C is triggered


RRC: Measurement Report

NBAP:Radio Link Addition Response

NBAP: Radio Link Addition Request


NBAP: Radio Link Deletion Request

NBAP: Radio Link Deletion Response



•• Do not always assume that Do not always assume that



Missing Neighbours

Description:Description:Missing Missing neighboursneighbours. .

Possible Cause:Possible Cause:Human negligence . Poor NB planning. Street canyon effect that rHuman negligence . Poor NB planning. Street canyon effect that requires more than 2 equires more than 2 tier NB planning etc. tier NB planning etc.



Missing Missing NeighbourNeighbour –– Prior to Call DropPrior to Call Drop

Prior to call drop, the Ec/No of SC233 became degraded due to interference from 12142 (SC302), which was not defined as a neighbourto 22750 (SC233).

How do we know it is a case of missing neighbour? Just take a look at the



Missing Missing NeighbourNeighbour –– After Call DropAfter Call Drop

Cell Reselection to 13184878 dec = C92F6E hex (RNC ID = C9 = 201, Cell ID = 2F6E = 12142 (SC302)

Question:How do we know it is a case of missing neighbour?

Ans: Just take a look at the Ec/No of the Reselected Cell (12142 SC302) and you can observe that the Ec/No jumped from bad to very good.



CAF #1CAF #1--1 1 –– 4 x RRC Connection Request4 x RRC Connection Request

•• Fail Call CategoryFail Call Category::•• Radio Related: 4 x RRC Connection Radio Related: 4 x RRC Connection

Request with no response. Missing Request with no response. Missing neighbourneighbour definition.definition.

•• AnalysisAnalysis::•• 4 x RRC Connection Request with no 4 x RRC Connection Request with no

response.response.•• After the last drop call (CAD #1), UE did After the last drop call (CAD #1), UE did

not cell reselect to the best serving not cell reselect to the best serving cell along that road due to missing cell along that road due to missing neighbourneighbour definitions between 32897 definitions between 32897 (312) & 22835 (309).(312) & 22835 (309).

•• Solution proposedSolution proposed::•• NeighbourNeighbour ADJS definitions:ADJS definitions:•• 32897 (312) 32897 (312) ⇔⇔ 22835 (309).22835 (309).

TMSITMSI D5 C2 82 02 D5 C2 82 02

RNTIRNTI

Time_origTime_orig

RNC_origRNC_orig / CID (SC)/ CID (SC) RN22 / 32897 (312)RN22 / 32897 (312)

RNC_dropRNC_drop / CID (SC)/ CID (SC)










TMSITMSI D5 C2 82 02 D5 C2 82 02

RNTIRNTI

Time_origTime_orig



RNC ID: 202 Cell ID: 22835RNC ID: 202 Cell ID: 22835



CAD #1CAD #1--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU Response

TMSITMSI 00 06 B3 E300 06 B3 E3

RNTIRNTI RN22: 12 D7 9 (= 77177)RN22: 12 D7 9 (= 77177)

Time_origTime_orig 17:12:20.67917:12:20.679


RNC_drop / CID (SC)RNC_drop / CID (SC) RN22 / 22552 (136)RN22 / 22552 (136)

•• Drop Call CategoryDrop Call Category::•• RF Related: MR e1a with No ASU RF Related: MR e1a with No ASU

response. Missing response. Missing NeighbourNeighbourdefinitionsdefinitions

•• AnalysisAnalysis::•• MR e1a with No ASU response. Missing MR e1a with No ASU response. Missing

NeighbourNeighbour definitions between 22552 definitions between 22552 (136) and 32873 (173).(136) and 32873 (173).

•• Solution / Action proposedSolution / Action proposed::•• ADJS definition:ADJS definition:•• 22552 (136) 22552 (136) 32873 (173)32873 (173)•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--2 2 –– MR e1a with No ASU ResponseMR e1a with No ASU Response

TMSITMSI 00 06 B3 E300 06 B3 E3

RNTIRNTI RN22: 12 D7 9 (= 77177)RN22: 12 D7 9 (= 77177)









ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #4CAD #4--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI CD A7 D3 02CD A7 D3 02

RNTIRNTI RN23:0C594 (=50580)RN23:0C594 (=50580)RN24: 09E97 (=40599)RN24: 09E97 (=40599)




•• Drop Call CategoryDrop Call Category::•• Site related: MR e1a with No ASU Site related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response.MR e1a with No ASU response.•• Site 2335U was down on 23 Feb. See Site 2335U was down on 23 Feb. See

WBTS Cell Status report. WBTS Cell Status report. •• NeighbourNeighbour definition to provide as definition to provide as

backup incase of site outage.backup incase of site outage.

•• Solution / Action proposedSolution / Action proposed::•• NB Definitions:NB Definitions:•• 12183 (156) 12183 (156) 22395 (151)22395 (151)•• 22545 (311) 22545 (311) 12350 (273) 12350 (273)




RNTIRNTI RN23:0C594 (=50580)RN23:0C594 (=50580)RN24: 09E97 (=40599)RN24: 09E97 (=40599)




•• Drop Call CategoryDrop Call Category::•• Site related: MR e1a with No ASU Site related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response.MR e1a with No ASU response.•• Site 2335U was down on 23 Feb. See Site 2335U was down on 23 Feb. See

WBTS Cell Status report. WBTS Cell Status report. •• NeighbourNeighbour definition to provide as definition to provide as

backup incase of site outage.backup incase of site outage.

•• Solution / Action proposedSolution / Action proposed::•• NB Definitions:NB Definitions:•• 12183 (156) 12183 (156) 22395 (151)22395 (151)•• 22545 (311) 22545 (311) 12350 (273) 12350 (273)




RNTIRNTI RN23:0C318 (= 49944)RN23:0C318 (= 49944)RN21:03071 (=12401)RN21:03071 (=12401)




•• Drop Call CategoryDrop Call Category::•• UE related: MR e1a with No ASU UE related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response.MR e1a with No ASU response.•• However, UE AS 26009 (333) was However, UE AS 26009 (333) was

sending MR e1a to select the worst sending MR e1a to select the worst EcEc/No SC in Monitored set instead of /No SC in Monitored set instead of Best Best EcEc/No SC./No SC.

•• Subsequently, call was dropped due Subsequently, call was dropped due to UE bad AS SC to UE bad AS SC EcEc/No => high BLER./No => high BLER.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.for verification.ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

Problem seemed to start here.SC318 was not in UE’s NB List. MC did not include SC318 although defined in 26009 (325) ADJS.This caused unnecessaryAS 325 having bad Ec/Nosince SC318 was aninterferer.

Problem seemed to start here.SC318 was not in UE’s NB List. MC did not include SC318 although defined in 26009 (325) ADJS.This caused unnecessaryAS 325 having bad Ec/Nosince SC318 was aninterferer.

RNTI_00003071.zip

05Feb23 120829-v vip-2.zip




RNTIRNTI RN23:0C318 (= 49944)RN23:0C318 (= 49944)RN21:03071 (=12401)RN21:03071 (=12401)




•• Drop Call CategoryDrop Call Category::•• UE related: MR e1a with No ASU UE related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response.MR e1a with No ASU response.•• However, UE AS 26009 (333) was However, UE AS 26009 (333) was

sending MR e1a to select the worst sending MR e1a to select the worst EcEc/No SC in Monitored set instead of /No SC in Monitored set instead of Best Best EcEc/No SC./No SC.

•• Subsequently, call was dropped due Subsequently, call was dropped due to UE bad AS SC to UE bad AS SC EcEc/No => high BLER./No => high BLER.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.for verification.ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



No MR after Last MC

Description:Description:UE did not perform any Measurement Reporting after last successfUE did not perform any Measurement Reporting after last successful ASU + ASUC + ul ASU + ASUC + Measurement Control sent, although the reporting criteria has beMeasurement Control sent, although the reporting criteria has been reached to en reached to perform MR e1a, e1b or e1c. perform MR e1a, e1b or e1c.

Possible Cause:Possible Cause:Since Soft Handover (Soft & Softer) is MEHO (Mobile Evaluated HSince Soft Handover (Soft & Softer) is MEHO (Mobile Evaluated Handover), the andover), the decision to send MR is completely relying on UE when reporting cdecision to send MR is completely relying on UE when reporting criteria has been riteria has been reached. Could only suggest that it is UE related problem.reached. Could only suggest that it is UE related problem.



CAD #3CAD #3--1 1 –– No MR After last MCNo MR After last MCTMSITMSI DD 05 E4 02 DD 05 E4 02

RNTIRNTI RN23:01 E8 2 (= 7810)RN23:01 E8 2 (= 7810)RN24:0D3F0 (=54256)RN24:0D3F0 (=54256)RN24:0D3F7 (=54263)RN24:0D3F7 (=54263)




•• Drop Call CategoryDrop Call Category::•• UE Related: No MR after last MC.UE Related: No MR after last MC.

•• AnalysisAnalysis::•• No MR after last MC.No MR after last MC.•• After last successful MR e1b with ASUC After last successful MR e1b with ASUC

to remove intrato remove intra--sector SC352 from AS, sector SC352 from AS, the UE did not perform any the UE did not perform any subsequent MR (duration of approx subsequent MR (duration of approx >2mins drive) until call was dropped >2mins drive) until call was dropped due to bad AS due to bad AS EcEc/No./No.

•• Solution / Action proposedSolution / Action proposed::•• UE UE behaviourbehaviour. . RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #3CAD #3--2 2 –– No MR After last MCNo MR After last MCTMSITMSI DD 05 E4 02 DD 05 E4 02

RNTIRNTI RN23:01 E8 2 (= 7810)RN23:01 E8 2 (= 7810)RN24:0D3F0 (=54256)RN24:0D3F0 (=54256)RN24:0D3F7 (=54263)RN24:0D3F7 (=54263)




•• Drop Call CategoryDrop Call Category::•• UE Related: No MR after last MC.UE Related: No MR after last MC.

•• AnalysisAnalysis::•• No MR after last MC.No MR after last MC.•• After last successful MR e1b with ASUC After last successful MR e1b with ASUC

to remove intrato remove intra--sector SC352 from AS, sector SC352 from AS, the UE did not perform any the UE did not perform any subsequent MR (duration of approx subsequent MR (duration of approx >2mins drive) until call was dropped >2mins drive) until call was dropped due to bad AS due to bad AS EcEc/No./No.

•• Solution / Action proposedSolution / Action proposed::•• UE UE behaviourbehaviour. . RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



S2N: CAD #1S2N: CAD #1--2 2 –– No MR after Last MCNo MR after Last MCTMSITMSI 00 01 6F 9400 01 6F 94

RNTIRNTI RN21:12 36 E (= 74606)RN21:12 36 E (= 74606)RN24: RN24:




•• Drop Call CategoryDrop Call Category::•• Radio Related: No MR after last MC.Radio Related: No MR after last MC.

•• AnalysisAnalysis::•• No MR after last MC. Due to street No MR after last MC. Due to street

canyon effect, 32335 (169) is canyon effect, 32335 (169) is propagating up propagating up FushingFushing Road. This is Road. This is not a missing not a missing neighbourneighbour. Suggest to . Suggest to reduce CPICH reduce CPICH TxTx Power of 32335 Power of 32335 (169).(169).

•• Problem could be resolved earlier, if Problem could be resolved earlier, if we also ensure mutual faster SHO, we also ensure mutual faster SHO, AdjsEcNoOffsetAdjsEcNoOffset = 4dB is added = 4dB is added mutually between 32713 (146) & mutually between 32713 (146) & 12324 (131).12324 (131).

•• Solution proposedSolution proposed::•• Reduce 32335 (169) CPICH Reduce 32335 (169) CPICH TxTx Power Power

from 33dBm to 30dBm.from 33dBm to 30dBm.•• Mutual Mutual AdjsEcNoOffsetAdjsEcNoOffset::•• 32713 (146) 32713 (146) 12324 (131) = 4dB 12324 (131) = 4dB

RSCPRSCP

Ec/NoEc/No

ScannerScanner



S2N: CAD #1S2N: CAD #1--2 2 –– No MR after Last MC No MR after Last MC

05Apr13 124724_MRT_S2N_CS_PS_Nemo WCDMA Scanner (0)-CPICH_Scan_RSCP_For_SC_169 (dBm)

( Below -100.00 (0)

( >= -100.00 to < -93.00 (0)

( >= -93.00 to < -75.00 (53)

( Above -75.00 (125)



CAD #2CAD #2--1 1 –– No MR after last MCNo MR after last MC

TMSITMSI 00 08 D6 E3 00 08 D6 E3

RNTIRNTI RN23: 09 4F 7 (= 38135)RN23: 09 4F 7 (= 38135)RN24: 05 E6 5 (= 24165)RN24: 05 E6 5 (= 24165)




•• Drop Call CategoryDrop Call Category::•• UE Related: No MR after last MC. UE Related: No MR after last MC.

•• AnalysisAnalysis::•• UE Related: No MR after last MC. UE Related: No MR after last MC.

Subsequently, AS (SC164) Subsequently, AS (SC164) EcEc/No /No quality degraded, resulting in high quality degraded, resulting in high BLER & call was dropped.BLER & call was dropped.

•• This is UE related since for the SHO This is UE related since for the SHO was successful for the concurrently was successful for the concurrently running UE for PS FTP downloading. running UE for PS FTP downloading. See next slide.See next slide.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive on 7 June for verification.. on 7 June for verification..

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #2CAD #2--2 2 –– No MR after last MC (UE2: PS FTP => No Drop Call Encountered)No MR after last MC (UE2: PS FTP => No Drop Call Encountered)

TMSITMSI 00 08 D6 E3 00 08 D6 E3

RNTIRNTI RN23: 09 4F 7 (= 38135)RN23: 09 4F 7 (= 38135)RN24: 05 E6 5 (= 24165)RN24: 05 E6 5 (= 24165)






Subsequently, AS (SC164) Subsequently, AS (SC164) EcEc/No /No quality degraded, resulting in high quality degraded, resulting in high BLER & call was dropped.BLER & call was dropped.

•• This is UE related since for the SHO This is UE related since for the SHO was successful for the concurrently was successful for the concurrently running UE for PS FTP downloading. running UE for PS FTP downloading.

•• Here, UE2 performing PS FTP Here, UE2 performing PS FTP downloading does not have any drop downloading does not have any drop call.call.


FTP ThruputFTP Thruput

UE RSCPUE RSCP

UE Ec/NoUE Ec/No




TMSITMSI 00 08 E2 13 00 08 E2 13

RNTIRNTI RN21: 02 41 E (= 9246)RN21: 02 41 E (= 9246)RN23: 09 87 4 (= 39028)RN23: 09 87 4 (= 39028)






Subsequently, after approx 3 minutes Subsequently, after approx 3 minutes of driving, UE AS (SC205) of driving, UE AS (SC205) EcEc/No quality /No quality degraded, resulting in high BLER & degraded, resulting in high BLER & call was dropped.call was dropped.


•• See next slide.See next slide.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #4CAD #4--2 2 –– No MR after last MC (UE2: PS FTP => No Drop Call Encountered)No MR after last MC (UE2: PS FTP => No Drop Call Encountered)



Subsequently, after approx 3 minutes Subsequently, after approx 3 minutes of driving, UE AS (SC205) of driving, UE AS (SC205) EcEc/No quality /No quality degraded, resulting in high BLER & degraded, resulting in high BLER & call was dropped.call was dropped.


•• Here, UE2 performing PS FTP Here, UE2 performing PS FTP downloading does not have any drop downloading does not have any drop call.call.



UE RSCPUE RSCP

UE Ec/NoUE Ec/No

TMSITMSI 00 08 E2 13 00 08 E2 13

RNTIRNTI RN21: 02 41 E (= 9246)RN21: 02 41 E (= 9246)RN23: 09 87 4 (= 39028)RN23: 09 87 4 (= 39028)






Drop call category:Drop call category:•• UE relatedUE related

Analysis:Analysis:•• UE was not sending any MR which UE was not sending any MR which

caused the failure in the softer HO.caused the failure in the softer HO.•• As As EcEc/No of SC306 in the AS degraded, /No of SC306 in the AS degraded,

and and EcEc/No of SC298 gets stronger in the /No of SC298 gets stronger in the MS, call drop subsequently due to UE not MS, call drop subsequently due to UE not sending MR.sending MR.

•• UE was hanged for almost 2 min., in UE was hanged for almost 2 min., in which the softer HO should have which the softer HO should have performed. performed.

Proposed solutionProposed solution

CAD CAD –– UE Related UE Related –– No MR after Last MCNo MR after Last MCTMSITMSI 00 3F E7 C6 (4188102)00 3F E7 C6 (4188102)

RNTIRNTI 06 19 2 (24978)06 19 2 (24978)


RNC_origRNC_orig / CID / CID (SC)(SC)

RN23 / 12700 (133)RN23 / 12700 (133)

RNC_drop / CID RNC_drop / CID (SC)(SC)

RN21 / 22716 (306)RN21 / 22716 (306)

UE Ec/NoUE Ec/No

ScannerScanner

UE RSCPUE RSCP




TMSITMSI 00 08 83 DB 00 08 83 DB

RNTIRNTI RN23: 06 FA 8 (= 28584)RN23: 06 FA 8 (= 28584)



RNC_drop / CID (SC)RNC_drop / CID (SC) RN23 / 2508 RN23 / 2508



Subsequently, AS (SC209,217,201) Subsequently, AS (SC209,217,201) EcEc/No quality degraded, resulting in /No quality degraded, resulting in high BLER & call was dropped.high BLER & call was dropped.

•• However, in this case, UE did not However, in this case, UE did not perform optimum SHO. In the last perform optimum SHO. In the last MR+ASU, UE did not send MR e1a (208) MR+ASU, UE did not send MR e1a (208) which is the best monitored candidate which is the best monitored candidate cell.cell.

•• Subsequently, UE did not attempt MR Subsequently, UE did not attempt MR e1c to replace AS with SC208, e1c to replace AS with SC208, probably due to AS probably due to AS EcEc/No quality /No quality already bad.already bad.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



MR e1x with No ASU ResponseMR e1x with No ASU Response

Description:Description:MR e1x (a/MR e1x (a/b/cb/c) with No ASU Response from Network. ) with No ASU Response from Network.

Possible Cause:Possible Cause:Do no always assume that this is Network related. It could be duDo no always assume that this is Network related. It could be due to radio or UE e to radio or UE related, even Missing related, even Missing NeighbourNeighbour could cause this : could cause this : 1)1) Network / BTS related:Network / BTS related:2)2) UE related: UE did not perform optimum SHO in the earlier MR+ASUE related: UE did not perform optimum SHO in the earlier MR+ASU+ASUC+MC, thus U+ASUC+MC, thus subsequent subsequent MRsMRs could be noncould be non--optimum.optimum.3)3) Radio related: Due to nonRadio related: Due to non--dominance etc. Could be improved by optimizing L1 dominance etc. Could be improved by optimizing L1 coverage of that stretch. Or due to rapid changing radio environcoverage of that stretch. Or due to rapid changing radio environment, AS ment, AS EcEc/No /No degraded rapidly (should verify with both degraded rapidly (should verify with both UEUE’’ss traces to confirm), should use traces to confirm), should use AdjsEcNoOffsetAdjsEcNoOffset to advance SHO or mutually make more favorable for SHO.to advance SHO or mutually make more favorable for SHO.



CAD #1CAD #1--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI 00 07 DA BB 00 07 DA BB

RNTIRNTI RN24: 01 33 3 (= 4915)RN24: 01 33 3 (= 4915)





response. response.

•• AnalysisAnalysis::•• MR e1a with No ASU response. MR e1a with No ASU response.

Observed the handover region Observed the handover region between SC215 & 133 with rapid between SC215 & 133 with rapid degradation of degradation of EcEc/No quality of SC215, /No quality of SC215, due to position of sector 2 antenna due to position of sector 2 antenna and building obstructions.and building obstructions.

•• Propose to use ADJS CPICH Propose to use ADJS CPICH EcEc/No /No Offset to mutually make SC215 & Offset to mutually make SC215 & SC133 appear more SC133 appear more favourablefavourable as SHO as SHO candidate.candidate.

•• Solution / Action proposedSolution / Action proposed::•• Mutually define:Mutually define:•• 22712 (215) 22712 (215) 12700 (133) 12700 (133)

AdjsEcNoOffsetAdjsEcNoOffset = 6dB= 6dB•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

This is a classic case of MR e1a with NoASU Response that is NOT due to Network Problem but due to rapid changing RFenvironment (Ec/No quality). This can be can be confirmed by observing if the samedeep fade is experienced by the 2nd UE.Which in this case it was.This can be optimized via Individual CPICH Ec/No Offset to advance the SHO.

This is a classic case of MR e1a with NoThis is a classic case of MR e1a with NoASU Response that is ASU Response that is NOTNOT due to Network due to Network Problem but due to rapid changing RFProblem but due to rapid changing RFenvironment (environment (EcEc/No quality). This can be /No quality). This can be can be confirmed by observing if the samecan be confirmed by observing if the samedeep fade is experienced by the 2deep fade is experienced by the 2ndnd UE.UE.Which in this case it was.Which in this case it was.This can be optimized via Individual CPICH This can be optimized via Individual CPICH EcEc/No Offset to advance the SHO./No Offset to advance the SHO.



CAD #1CAD #1--2 2 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI 00 07 DA BB 00 07 DA BB

RNTIRNTI RN24: 01 33 3 (= 4915)RN24: 01 33 3 (= 4915)





response. response.

•• AnalysisAnalysis::•• MR e1a with No ASU response. MR e1a with No ASU response.

Observed the handover region Observed the handover region between SC215 & 133 with rapid between SC215 & 133 with rapid degradation of degradation of EcEc/No quality of SC215, /No quality of SC215, due to position of sector 2 antenna due to position of sector 2 antenna and building obstructions.and building obstructions.

•• Propose to use ADJS CPICH Propose to use ADJS CPICH EcEc/No /No Offset to mutually make SC215 & Offset to mutually make SC215 & SC133 appear more SC133 appear more favourablefavourable as SHO as SHO candidate.candidate.

•• Solution / Action proposedSolution / Action proposed::•• Mutually define:Mutually define:•• 22712 (215) 22712 (215) 12700 (133) 12700 (133)

AdjsEcNoOffsetAdjsEcNoOffset = 6dB= 6dB•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #3CAD #3--1 1 –– MR e1a with No ASU Response MR e1a with No ASU Response –– Radio relatedRadio relatedTMSITMSI 00 07 F0 93 00 07 F0 93

RNTIRNTI RN23: 02 AA 4 (= 10916)RN23: 02 AA 4 (= 10916)




•• Drop Call CategoryDrop Call Category::•• Radio Related: MR e1a with No ASU Radio Related: MR e1a with No ASU

response. response.

•• AnalysisAnalysis::•• Radio Related: MR e1a with No ASU Radio Related: MR e1a with No ASU

response, possible due to AS (SC245) response, possible due to AS (SC245) EcEc/No quality degraded rapidly. /No quality degraded rapidly. Possibly DL broken.Possibly DL broken.

•• Weak dominance stretch around Weak dominance stretch around Presidential Palace area. Difficulty in Presidential Palace area. Difficulty in getting candidate sites.getting candidate sites.

•• Try to create dominance using 22367 Try to create dominance using 22367 (234) by changing (234) by changing realtiltrealtilt EE--ADT from ADT from 6deg to 4deg.6deg to 4deg.

•• Solution / Action proposedSolution / Action proposed::•• 22367 (234): 22367 (234):

•• EE--ADT = 6deg to 4degADT = 6deg to 4deg

•• RedriveRedrive on 3 June for verification.. on 3 June for verification..

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI DD 58 E5 02 DD 58 E5 02

RNTIRNTI RN21:05 A8 E (= 23182)RN21:05 A8 E (= 23182)




•• Drop Call CategoryDrop Call Category::•• Site Related: MR e1a with no ASU.Site Related: MR e1a with no ASU.

•• AnalysisAnalysis::•• MR e1a with no ASU response.MR e1a with no ASU response.•• Site 2151U was not transmitting on Site 2151U was not transmitting on

the day of drive (link problem). Check the day of drive (link problem). Check BTS alarm history of 4 Mar 05.BTS alarm history of 4 Mar 05.

•• In this case, 12151 (182) was not In this case, 12151 (182) was not defined as neighbor with 36025 defined as neighbor with 36025 (340). As such, monitored NB list was (340). As such, monitored NB list was nonnon--optimum, resulting in MR e1a to optimum, resulting in MR e1a to other nonother non--optimum MS cells. optimum MS cells.

•• Solution / Action proposedSolution / Action proposed::•• Confirmed from BTS alarm history that Confirmed from BTS alarm history that

site 2151U was down on day of drive. site 2151U was down on day of drive. •• Possibly define:Possibly define:•• 36025 (340) 36025 (340) 12520 (182) as a 12520 (182) as a

backup when 2151U is down.backup when 2151U is down.•• RedriveRedrive for for verificationnverificationn when 2151U when 2151U

is transmitting again.is transmitting again.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #6CAD #6--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI DD ED E4 02DD ED E4 02

RNTIRNTI RN23:01 FB A (= 8122)RN23:01 FB A (= 8122)RN24: 0D 47 C (= 54396)RN24: 0D 47 C (= 54396)




•• Drop Call CategoryDrop Call Category::•• Network related: MR e1a with No ASU Network related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response. MR e1a with No ASU response. •• The last successful MR e1b with ASUC The last successful MR e1b with ASUC

to remove SC311 from AS => SRNC to remove SC311 from AS => SRNC RelocReloc to RN24, did not receive any MC to RN24, did not receive any MC (possibly due to radio link lost)(possibly due to radio link lost)

•• Subsequent MR e1a with no ASU Subsequent MR e1a with no ASU response resulted in AS SC149 response resulted in AS SC149 EcEc/No /No degraded and call was dropped due degraded and call was dropped due to high BLER.to high BLER.

•• Solution / Action proposedSolution / Action proposed::•• Site 2700U to be Site 2700U to be rehomedrehomed from RN24 from RN24

to RN23 in Phase 2.to RN23 in Phase 2.•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RNTI_00001FBA_0273.zip

RNTI_0000D47C_0175.zip



CAD #6CAD #6--2 2 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI DD ED E4 02DD ED E4 02

RNTIRNTI RN23:01 FB A (= 8122)RN23:01 FB A (= 8122)RN24: 0D 47 C (= 54396)RN24: 0D 47 C (= 54396)




•• Drop Call CategoryDrop Call Category::•• Network related: MR e1a with No ASU Network related: MR e1a with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with No ASU response. MR e1a with No ASU response. •• The last successful MR e1b with ASUC The last successful MR e1b with ASUC

to remove SC311 from AS => SRNC to remove SC311 from AS => SRNC RelocReloc to RN24, did not receive any MC to RN24, did not receive any MC (possibly due to radio link lost)(possibly due to radio link lost)

•• Subsequent MR e1a with no ASU Subsequent MR e1a with no ASU response resulted in AS SC149 response resulted in AS SC149 EcEc/No /No degraded and call was dropped due degraded and call was dropped due to high BLER.to high BLER.

•• Solution / Action proposedSolution / Action proposed::•• Site 2700U to be Site 2700U to be rehomedrehomed from RN24 from RN24

to RN23 in Phase 2.to RN23 in Phase 2.•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #5CAD #5--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI DD 4E A5 02 DD 4E A5 02

RNTIRNTI 01 E5 0 (= 7760)01 E5 0 (= 7760)

Time_origTime_orig



•• Drop Call CategoryDrop Call Category::•• Site Related: MR e1a with No ASU Site Related: MR e1a with No ASU

response. However, this is due to response. However, this is due to RN23 Site 2530U problem (as would RN23 Site 2530U problem (as would be observed in the subsequent be observed in the subsequent unsuccessful handover attempts to unsuccessful handover attempts to this cell.this cell.

•• AnalysisAnalysis::•• UE AS 32151 (197) sends MR e1a UE AS 32151 (197) sends MR e1a

12520 (182) with no ASU response. 12520 (182) with no ASU response. From MS, 12520 (182) RSCP & From MS, 12520 (182) RSCP & Ec/NnoEc/Nnoquality was quite low. quality was quite low.

•• Current EADT of 12520 (182) & 22520 Current EADT of 12520 (182) & 22520 (190) is 8deg. Propose to (190) is 8deg. Propose to uptiltuptilt 3deg 3deg to improve dominance & quality.to improve dominance & quality.

•• Solution proposedSolution proposed::•• 12520 (182) & 22520 (190) EADT 12520 (182) & 22520 (190) EADT

change from 8deg to 5deg.change from 8deg to 5deg.•• RedriveRedrive for verification on 14 Jan. No for verification on 14 Jan. No

drop call. drop call.

13 Jan 200513 Jan 2005




RNTIRNTI 01 E5 0 (= 7760)01 E5 0 (= 7760)

Time_origTime_orig











14 Jan 2005 – Drive #1 – no drop call14 Jan 2005 – Drive #1 – no drop call




RNTIRNTI 01 E5 0 (= 7760)01 E5 0 (= 7760)

Time_origTime_orig











14 Jan 2005 – Drive #2 – no drop call14 Jan 2005 – Drive #2 – no drop call



CAD #1CAD #1--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI 00 06 B3 E300 06 B3 E3

RNTIRNTI RN22: 12 D7 9 (= 77177)RN22: 12 D7 9 (= 77177)









ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--2 2 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI 00 06 B3 E300 06 B3 E3

RNTIRNTI RN22: 12 D7 9 (= 77177)RN22: 12 D7 9 (= 77177)









ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--1 1 –– MR e1c with No ASU ResponseMR e1c with No ASU ResponseTMSITMSI F2 41 08 00 F2 41 08 00

RNTIRNTI RN26: 01 73 1 (= 5937)RN26: 01 73 1 (= 5937)




•• Drop Call CategoryDrop Call Category::•• RF Related: MR e1c with No ASU RF Related: MR e1c with No ASU

response.response.

•• AnalysisAnalysis::•• MR e1c with No ASU response.MR e1c with No ASU response.•• No coverage dominance along this No coverage dominance along this

stretch of highway.stretch of highway.•• Dominance would be improved by Dominance would be improved by

optimizing electrical tilt of 12256 optimizing electrical tilt of 12256 (159).(159).

•• Solution / Action proposedSolution / Action proposed::•• To implement 12256 (159) ETo implement 12256 (159) E--ADT ADT

uptiltuptilt of 2 of 2 degsdegs to improve dominance to improve dominance along highway.along highway.

•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #3CAD #3--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI DD 2A F1 02 DD 2A F1 02

RNTIRNTI RN23:01 0B C (= 4284)RN23:01 0B C (= 4284)RN24:00 B9 B (= 2971)RN24:00 B9 B (= 2971)




•• Drop Call CategoryDrop Call Category::•• Network Related: MR e1a with no ASU Network Related: MR e1a with no ASU

response.response.

•• AnalysisAnalysis::•• MR e1a with no ASU response.MR e1a with no ASU response.•• Network problem between MG21 & Network problem between MG21 &

RN24/23, which started about this RN24/23, which started about this timing, caused all calls setups to fail timing, caused all calls setups to fail after after ““Call ProceedingCall Proceeding””, DL RRC , DL RRC Connection Release.Connection Release.

•• Solution / Action proposedSolution / Action proposed::•• TroubleshootedTroubleshooted realtimerealtime and and

resolved. Subsequent calls under resolved. Subsequent calls under RN23 & RN24 were successful. RN23 & RN24 were successful.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #3CAD #3--1 1 –– MR e1a with No ASU Response MR e1a with No ASU Response –– FMT Tool Problem FMT Tool Problem

TMSITMSI 00 09 ED 72 00 09 ED 72

RNTIRNTI RN23: 11 49 D (= 70813)RN23: 11 49 D (= 70813)




•• Drop Call CategoryDrop Call Category::•• Tool related: MR e1a with No ASU Tool related: MR e1a with No ASU

response. FMT Tool not responding / response. FMT Tool not responding / malfunctioned.malfunctioned.

•• AnalysisAnalysis::•• Tool related: MR e1a with No ASU Tool related: MR e1a with No ASU

response. FMT Tool not responding / response. FMT Tool not responding / malfunctioned.malfunctioned.

•• As observed from trace, the As observed from trace, the flatlinerflatlinerof the measurement traces for of the measurement traces for BOTH BOTH UEsUEs indicated that the FMT indicated that the FMT tool had stopped respondingtool had stopped responding..

•• This drop call is not due to network This drop call is not due to network problem.problem.

•••• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

Flatliner – ToolMalfunctioned.Both UE traces same.

Flatliner – ToolMalfunctioned.Both UE traces same.



CAD #6CAD #6--1 1 –– No MC after Last ASU+ASUC, MR e1a with No ASU ResponseNo MC after Last ASU+ASUC, MR e1a with No ASU Response

TMSITMSI 00 08 89 E3 00 08 89 E3

RNTIRNTI RN24: 04 1E 2RN24: 04 1E 2




•• Drop Call CategoryDrop Call Category::•• Network Related: No MC after last Network Related: No MC after last

ASU+ASUC, MR e1a with No ASU ASU+ASUC, MR e1a with No ASU response. response.

•• (Note: somehow, (Note: somehow, UuUu log did not log did not record the RRC record the RRC ConnConn Setup RNTI for Setup RNTI for voice call (IMSI: 349), only for PS call voice call (IMSI: 349), only for PS call (IMSI: 348 => 041E1))(IMSI: 348 => 041E1))

•• AnalysisAnalysis::•• No MC after last ASU+ASUC, MR e1a No MC after last ASU+ASUC, MR e1a

with No ASU response. Softer HO with No ASU response. Softer HO failure. failure.

•• However, in this case, UE did not However, in this case, UE did not perform optimum SHO. In the last perform optimum SHO. In the last MR+ASU, UE did not send MR e1a MR+ASU, UE did not send MR e1a (softer 303) which is the best (softer 303) which is the best monitored candidate cell (see next monitored candidate cell (see next slide).slide).

•• Subsequently, UE did not attempt MR Subsequently, UE did not attempt MR e1a to add AS with SC303, probably e1a to add AS with SC303, probably due to AS due to AS EcEc/No quality already bad./No quality already bad.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #6CAD #6--2 2 –– No MC after Last ASU+ASUC, MR e1a with No ASU ResponseNo MC after Last ASU+ASUC, MR e1a with No ASU Response

TMSITMSI 00 08 89 E3 00 08 89 E3

RNTIRNTI RN24: 04 1E 2 RN24: 04 1E 2




•• Drop Call CategoryDrop Call Category::•• Network Related: No MC after last Network Related: No MC after last

ASU+ASUC, MR e1a with No ASU ASU+ASUC, MR e1a with No ASU response. response.

•• AnalysisAnalysis::•• No MC after last ASU+ASUC, MR e1a No MC after last ASU+ASUC, MR e1a

with No ASU response. Softer HO with No ASU response. Softer HO failure. failure.

•• However, in this case, UE did not However, in this case, UE did not perform optimum SHO. In the last perform optimum SHO. In the last MR+ASU, UE did not send MR e1a MR+ASU, UE did not send MR e1a (softer 303) which is the best (softer 303) which is the best monitored candidate cell (see next monitored candidate cell (see next slide). => UE malfunctioned??slide). => UE malfunctioned??

•• Subsequently, UE did not attempt MR Subsequently, UE did not attempt MR e1a to add AS with SC303, probably e1a to add AS with SC303, probably due to AS due to AS EcEc/No quality already bad./No quality already bad.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--1 1 –– MR e1a with No ASU Response (BTS / Radio) (02 June 2005) MR e1a with No ASU Response (BTS / Radio) (02 June 2005)

TMSITMSI 00 07 F0 93 00 07 F0 93

RNTIRNTI RN21: 03 79 A (= 14234)RN21: 03 79 A (= 14234)RN24: 03 27 9 (= 12921)RN24: 03 27 9 (= 12921)RN24: 03 28 7 (= 12935)RN24: 03 28 7 (= 12935)




•• Drop Call CategoryDrop Call Category::•• BTS Related: MR e1a with No ASU BTS Related: MR e1a with No ASU

response. response.

•• AnalysisAnalysis::•• BTS Related: MR e1a with No ASU BTS Related: MR e1a with No ASU

response, due to AS SC147 bad or rapid response, due to AS SC147 bad or rapid fading of fading of EcEc/No quality from approx /No quality from approx ––5dB 5dB to to ––25dB. 25dB.

•• However, it was suspected that the BTS However, it was suspected that the BTS could have some problem at that instant, could have some problem at that instant, instead of the instead of the NemoNemo FMT & UE. In any case, FMT & UE. In any case, would be checking the 2324U detailed BTS would be checking the 2324U detailed BTS alarm history for 02 June to further alarm history for 02 June to further investigate. investigate.

•• Next slide showed same route driven on Next slide showed same route driven on 01 June, no problem or drop call.01 June, no problem or drop call.

•• Solution / Action proposedSolution / Action proposed::•• Check 2324U detailed BTS alarm history Check 2324U detailed BTS alarm history

for 02 June. for 02 June. WCDMA Cell Out of Use WCDMA Cell Out of Use during the above aforesaid period.during the above aforesaid period.

•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

2324U_0602.log



CAD #1CAD #1--2 2 –– MR e1a with No ASU Response (01 June 2005) MR e1a with No ASU Response (01 June 2005)

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

TMSITMSI 00 07 F0 93 00 07 F0 93

RNTIRNTI RN21: 03 79 A (= 14234)RN21: 03 79 A (= 14234)RN24: 03 27 9 (= 12921)RN24: 03 27 9 (= 12921)RN24: 03 28 7 (= 12935)RN24: 03 28 7 (= 12935)




•• Drop Call CategoryDrop Call Category::•• BTS / Radio Related: MR e1a with No BTS / Radio Related: MR e1a with No

ASU response. ASU response.

•• AnalysisAnalysis::•• BTS / Radio Related: MR e1a with No BTS / Radio Related: MR e1a with No

ASU response, due to AS SC147 bad or ASU response, due to AS SC147 bad or rapid fading of rapid fading of EcEc/No quality from /No quality from approx approx ––5dB to 5dB to ––25dB. 25dB.

•• However, it was suspected that the However, it was suspected that the BTS could have some problem at that BTS could have some problem at that instant, instead of the instant, instead of the NemoNemo FMT & UE. FMT & UE. In any case, would be checking the In any case, would be checking the 2324U detailed BTS alarm history for 2324U detailed BTS alarm history for 02 June to further investigate. 02 June to further investigate.

•• Next slide showed same route driven Next slide showed same route driven on 01 June, no problem or drop call.on 01 June, no problem or drop call.

•• Solution / Action proposedSolution / Action proposed::•• Check 2324U detailed BTS alarm Check 2324U detailed BTS alarm

history for 02 June.history for 02 June.•• RedriveRedrive for verification.for verification.



CAD #3CAD #3--1 1 –– MR e1a with No ASU Response MR e1a with No ASU Response –– Radio relatedRadio related

TMSITMSI 00 08 83 DB 00 08 83 DB

RNTIRNTI RN23: 06 FB 8 (= 28600)RN23: 06 FB 8 (= 28600)





response. BTS response. BTS



•• Check BTS alarm history for 6012U on Check BTS alarm history for 6012U on 3 June.3 June.

•• Need to check RF coverage between Need to check RF coverage between 16012 & 26012.16012 & 26012.

•• Solution / Action proposedSolution / Action proposed::•• Check BTS alarm history for 6012U on Check BTS alarm history for 6012U on

3 June.3 June.•• RedriveRedrive on 6 June for verification.. on 6 June for verification..

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

Observed from UE that RSCP & Ec/No of ALL AS & Monitored Set degraded all at same time. Suggesting that possible BTS or RNC problem. Also, no meas data on Scanner.

Observed from UE that RSCP & Ec/No of ALL AS & Monitored Set degraded all at same time. Suggesting that possible BTS or RNC problem. Also, no meas data on Scanner.



CAD #3CAD #3--2 2 –– MR e1a with No ASU Response MR e1a with No ASU Response –– Radio relatedRadio related

TMSITMSI 00 08 83 DB 00 08 83 DB

RNTIRNTI RN23: 06 FB 8 (= 28600)RN23: 06 FB 8 (= 28600)





response. response.



•• Check BTS alarm history for 6012U on Check BTS alarm history for 6012U on 3 June.3 June.

•• Need to check RF coverage between Need to check RF coverage between 16012 & 26012.16012 & 26012.

•• Solution / Action proposedSolution / Action proposed::•• Check BTS alarm history for 6012U on Check BTS alarm history for 6012U on

3 June. Alarm history reviewed that 3 June. Alarm history reviewed that •• RedriveRedrive on 6 June for verification.. on 6 June for verification..

Checking Alarm history of 6012U on 03 June 05Reviewed that Site / all cells were indeed down atThat exact time of driving through !!

Checking Alarm history of 6012U on 03 June 05Reviewed that Site / all cells were indeed down atThat exact time of driving through !!



CAD #3CAD #3--1 1 –– MR e1b with No ASU ResponseMR e1b with No ASU Response

TMSITMSI 00 09 7B 32 00 09 7B 32

RNTIRNTI RN23: 0C D3 3 (= 52531)RN23: 0C D3 3 (= 52531)RN24: 08 05 7 (= 32855)RN24: 08 05 7 (= 32855)




•• Drop Call CategoryDrop Call Category::•• Network Related: MR e1b with no ASU Network Related: MR e1b with no ASU

response. response.

•• AnalysisAnalysis::•• Network Related: MR e1b with no ASU Network Related: MR e1b with no ASU

response. Subsequently, call was response. Subsequently, call was dropped due to AS high BLER.dropped due to AS high BLER.

•• This seemed to be specific UE related This seemed to be specific UE related since for the SHO was successful for since for the SHO was successful for the concurrently running UE for PS FTP the concurrently running UE for PS FTP downloading. downloading.

•• See next slide.See next slide.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.. for verification..

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RRC_Mon_00008057_0CF0.zip



CAD #3CAD #3--2 2 –– MR e1b with No ASU ResponseMR e1b with No ASU Response

TMSITMSI 00 09 7B 32 00 09 7B 32

RNTIRNTI RN23: 0C D3 3 (= 52531)RN23: 0C D3 3 (= 52531)RN24: 08 05 7 (= 32855)RN24: 08 05 7 (= 32855)




•• Drop Call CategoryDrop Call Category::•• Network Related: MR e1b with no ASU Network Related: MR e1b with no ASU

response. response.

•• AnalysisAnalysis::•• Network Related: MR e1b with no ASU Network Related: MR e1b with no ASU

response. Subsequently, call was response. Subsequently, call was dropped due to AS high BLER.dropped due to AS high BLER.

•• This seemed to be specific UE related This seemed to be specific UE related since for the SHO was successful for since for the SHO was successful for the concurrently running UE for PS FTP the concurrently running UE for PS FTP downloading. downloading.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.. for verification..


UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #4CAD #4--1 1 –– MR e1a with No ASU ResponseMR e1a with No ASU ResponseTMSITMSI F2 5C 08 00 F2 5C 08 00

RNTIRNTI RN26: 01 8B A (= 6330)RN26: 01 8B A (= 6330)





response. Site 8002U related.response. Site 8002U related.

•• AnalysisAnalysis::•• MR e1a with No ASU response.MR e1a with No ASU response.•• This whole stretch of This whole stretch of WenHwaWenHwa Road is Road is

served by 28002 (259). served by 28002 (259). •• However, on the day & period of drive, However, on the day & period of drive,

Site 8002U BTS alarm history Site 8002U BTS alarm history indicated indicated ““NBAP link failureNBAP link failure”” and site and site was blocked due to was blocked due to ““LILI”” (RNC time: (RNC time: 2.42pm~2.52pm). Call was dropped 2.42pm~2.52pm). Call was dropped due to poor due to poor EcEc/No./No.

•• Solution / Action proposedSolution / Action proposed::•• Investigate site Investigate site btsbts alarm history.alarm history.•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAF #4 CAF #4 ––RRC Connection Reject with cause RRC Connection Reject with cause ‘‘UnspecifiedUnspecified’’TMSITMSI F2 5C 08 00 F2 5C 08 00

RNTIRNTI



RNC_drop / CID (SC)RNC_drop / CID (SC)

•• Fail Call CategoryFail Call Category::•• Site Related Site Related relatedrelated: RRC Connection : RRC Connection

Reject with cause Reject with cause ‘‘unspecifiedunspecified’’..

•• AnalysisAnalysis::•• Site Related Site Related relatedrelated: RRC Connection : RRC Connection

Reject with cause Reject with cause ‘‘unspecifiedunspecified’’..•• However, on the day & period of drive, However, on the day & period of drive,

Site 8002U BTS alarm history Site 8002U BTS alarm history indicated indicated ““NBAP link failureNBAP link failure”” and site and site was blocked due to was blocked due to ““LILI”” (RNC time: (RNC time: 2.42pm~2.52pm)2.42pm~2.52pm)

•• Site subsequently recovered around Site subsequently recovered around 2.52 and subsequent call attempt 2.52 and subsequent call attempt made on SC259 was successful. made on SC259 was successful.

•• Solution / Action proposedSolution / Action proposed::•• RedriveRedrive for verification.for verification.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



IntraIntra--Frequency Frequency HardHandoverHardHandover (HHO) Case(HHO) Case

Description:Description:IntraIntra--Frequency Frequency HardHandoverHardHandover (HHO) Case. (HHO) Case.

Possible Cause:Possible Cause:



HardHandoverHardHandover (HHO) (HHO) –– IurIur Congestion CaseCongestion Case



InterInter--RNC intraRNC intra--frequency Hard Handover (HHO)frequency Hard Handover (HHO)

•• IntraIntra--frequency hard handover is required frequency hard handover is required to ensure handover between cells to ensure handover between cells controlled by different controlled by different RNCsRNCs when an interwhen an inter--RNC Soft Handover is not possibleRNC Soft Handover is not possible

•• No No IurIur between between RNCsRNCs•• IurIur congestion or failurecongestion or failure

•• IntraIntra--frequency hard Handover is lossless frequency hard Handover is lossless for NRT radio bearer but it causes short for NRT radio bearer but it causes short disconnection of RT radio bearer.disconnection of RT radio bearer.

•• IntraIntra--frequency hard handover decisions frequency hard handover decisions made by the RNC are based on the intramade by the RNC are based on the intra--frequency measurement results, which are frequency measurement results, which are usually applied to the SHO procedureusually applied to the SHO procedure

•• Also Also Enable InterEnable Inter--RNC SHORNC SHO parameter in parameter in intraintra--frequency HO path defines whether frequency HO path defines whether intraintra--frequency HO from the serving cell to frequency HO from the serving cell to a specified neighbour cells is performed as a specified neighbour cells is performed as soft of hardsoft of hard

•• Mobile evaluated Handover (MEHO)Mobile evaluated Handover (MEHO)

CN

RNCRNC

Iu Iu

Iur

CN

RNCRNC

Iu Iu

Iur



InterInter--RNC intraRNC intra--frequency Hard Handover (HHO)frequency Hard Handover (HHO)•• If RNC is not able to add (Event 1A) to or replace (Event 1C) anIf RNC is not able to add (Event 1A) to or replace (Event 1C) an NcellNcell from the AS, UE sends periodic from the AS, UE sends periodic

measurement reports (measurement reports (AdditionReportingIntervalAdditionReportingInterval/ / ReplacementReportingIntervalReplacementReportingInterval) until;) until;•• NcellNcell is added/replaced in to ASis added/replaced in to AS•• NcellNcell leaves reporting rangeleaves reporting range•• HO no longer required (e.g. different HO no longer required (e.g. different NcellNcell enters AS)enters AS)

•• RNC may not be able to add/replace RNC may not be able to add/replace NcellNcell due to (a) due to (a) IurIur congestion or (b) intercongestion or (b) inter--RNC SHO is RNC SHO is prevented due to setting of prevented due to setting of EnableInterRNCshoEnableInterRNCsho (HOPS) (point1 on next slide)(HOPS) (point1 on next slide)

•• If CPICH EIf CPICH ECC/N/NOO of nonof non--active active NcellNcell continues to increase it will cause additional interference duecontinues to increase it will cause additional interference due to to a nona non--optimal connection (point 2)optimal connection (point 2)

•• To avoid excessive uplink interference, RNC will perform an intrTo avoid excessive uplink interference, RNC will perform an intraa--frequency hard handover to the frequency hard handover to the NcellNcell (CPICH3) if either of the following criteria are met (point 3);(CPICH3) if either of the following criteria are met (point 3);

AveEcNoDownlinkAveEcNoDownlink + + HHOMarginAveEcNoHHOMarginAveEcNo < < AveEcNoNcellAveEcNoNcellEcNoDownlinkEcNoDownlink + + HHOMarginPeakEcNoHHOMarginPeakEcNo < < EcNONcellEcNONcell

Parameters :Parameters :

•• Enable InterEnable Inter--RNC Soft Handover RNC Soft Handover ( YES/NO, default = YES )( YES/NO, default = YES )

•• HHO margin for Peak EcNoHHO margin for Peak EcNo ((--66……6 dB, default =2 dB)6 dB, default =2 dB)

•• HH Margin for Average EcNoHH Margin for Average EcNo ((--66……6 dB, default=1 dB)6 dB, default=1 dB)



Time

Ec/Io

P CPICH 3

P CPICH 1

P CPICH 2Reporting

range

AdditionReportingInterval

1

2

HHOMarginAverageEcNoHHOMarginPeakEcNo

1A (AdditionTime = 0)

AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcellEcNoDownlink + HHOMarginPeakEcNo < EcNONcellAveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcellEcNoDownlink + HHOMarginPeakEcNo < EcNONcell

3

InterInter--RNC intraRNC intra--frequency Hard Handover (HHO)frequency Hard Handover (HHO)




•• Case #1: Case #1: •• Problem: Problem:

•• MGW MGW IurIur Nodal Function AAL2_ANALYSIS_TREE setting wrong. Resulting in ANodal Function AAL2_ANALYSIS_TREE setting wrong. Resulting in AAL2 UP AL2 UP



Case #1Case #1--1 1 –– InterInter--RNC, IntraRNC, Intra--Frequency Frequency HardhandoverHardhandover (HHO)(HHO)TMSITMSI 00 01 86 55 00 01 86 55

RNTIRNTI RN26:00 57 8 (= 1400)RN26:00 57 8 (= 1400)RN27: 02 2E 6 (= 8934)RN27: 02 2E 6 (= 8934)



RNC_EndRNC_End / CID (SC)/ CID (SC) RN27 / 32242 (264)RN27 / 32242 (264)

•• Handover CategoryHandover Category::•• IurIur Failure Failure -- InterInter--RNC SRNC Relocation RNC SRNC Relocation

failure => Triggering Interfailure => Triggering Inter--RNC, IntraRNC, Intra--Frequency HHO.Frequency HHO.

•• AnalysisAnalysis::•• IurIur failure was simulated / purposely failure was simulated / purposely

disabled via blocking AAL2 User Plane, disabled via blocking AAL2 User Plane, to invoke Interto invoke Inter--RNC, IntraRNC, Intra--Frequency Frequency HHO.HHO.

•• Solution / Action proposedSolution / Action proposed::ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RN26RN26

RN27RN27

Iur Failure !Iur Failure !













UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RN26RN26

RN27RN27



Problem Cause:Problem Cause:

•• Error Alarm from MGW25Error Alarm from MGW25

•• HST (54474) 2U4MG25 1A002HST (54474) 2U4MG25 1A002--0000--3 COMM 20053 COMM 2005--0303--21 11:47:02.6221 11:47:02.62•• DISTUR ISUDISTUR ISU--0 0 •• 1205 USER PLANE CONNECTION SETUP FAILURE 1205 USER PLANE CONNECTION SETUP FAILURE •• UCNPRB ISUUCNPRB ISU--0 0 •• 01 02 14 49 20 63 20 6F FF 01 02 14 49 20 63 20 6F FF FFFF FFFF FFFF FFFF FFFF FFFF FFFF

•• Cause of Problem: Check Cause of Problem: Check PRFilePRFile and wrong setting for AAL2 Digit Analysis Tree settingsand wrong setting for AAL2 Digit Analysis Tree settings

•• PARAMETER CLASS: 7 CALL_CONTROL PARAMETER CLASS: 7 CALL_CONTROL

•• IDENTIFIER NAME OF PARAMETERIDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITYVALUE CHANGE POSSIBILITY

•• 00127 AAL2_ANALYSIS_TREE 00127 AAL2_ANALYSIS_TREE 00010001 YES YES

•• After changing value= 3 then working.After changing value= 3 then working.

•• PARAMETER CLASS: 7 CALL_CONTROL PARAMETER CLASS: 7 CALL_CONTROL

•• IDENTIFIER NAME OF PARAMETER IDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITYVALUE CHANGE POSSIBILITY

•• 00127 AAL2_ANALYSIS_TREE 00127 AAL2_ANALYSIS_TREE 00030003 YES YES




•• Case #2: Case #2: •• Problem: Problem:













UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RN23RN23

RN21RN21Iur Failure !Iur Failure !

MR e1a with noASU Response due to IurFailure

MR e1a with noASU Response due to IurFailure













UE RSCPUE RSCP

UE Ec/NoUE Ec/No

RN23RN23

RN21RN21Iur Failure !Iur Failure !

Immediate AS SC Change from RN23 12320 (301) toRN21 22558 (305)

Immediate AS SC Change from RN23 12320 (301) toRN21 22558 (305)



DL RRC Connection Release with Release Cause “Unspecified”

Description:Description:DL RRC Connection Release with Release Cause DL RRC Connection Release with Release Cause ““UnspecifiedUnspecified””. . Note: These are only some of the possible problems and does not Note: These are only some of the possible problems and does not imply same imply same problem whenever encountering RRC Connection Release with Releasproblem whenever encountering RRC Connection Release with Release Cause e Cause ““UnspecifiedUnspecified””. Just for information since you will not be able to view the ba. Just for information since you will not be able to view the backend ckend logs.logs.Need to put as to investigate further.Need to put as to investigate further.

Possible Cause:Possible Cause:RNC internal.RNC internal.



CAD #1CAD #1--1 1 –– DL RRC DL RRC ConnConn RelRel after RB after RB ReconfigReconfig CompleteCompleteTMSITMSI DD 61 E5 02 DD 61 E5 02

RNTIRNTI RN21:05 AA 0 (= 23200)RN21:05 AA 0 (= 23200)




•• Drop Call CategoryDrop Call Category::•• Network: DL RRC Connection Release Network: DL RRC Connection Release

after RB after RB ReconfigReconfig Complete.Complete.

•• AnalysisAnalysis::•• DL RRC Connection Release after RB DL RRC Connection Release after RB

ReconfigReconfig Complete.Complete.•• From ICSU log, From ICSU log, transmissionNetworktransmissionNetwork : :

iuiu--transporttransport--connectionconnection--failedfailed--toto--establish.establish.

•• Solution / Action proposedSolution / Action proposed::

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAD #1CAD #1--1 1 –– DL RRC DL RRC ConnConn RelRel after RB after RB ReconfigReconfig CompleteCompleteTMSITMSI DD 61 E5 02 DD 61 E5 02

RNTIRNTI RN21:00 61 B (= 1563)RN21:00 61 B (= 1563)




•• Drop Call CategoryDrop Call Category::•• Network: DL RRC Connection Release Network: DL RRC Connection Release

after RB after RB ReconfigReconfig Complete.Complete.

•• AnalysisAnalysis::•• DL RRC Connection Release after RB DL RRC Connection Release after RB

ReconfigReconfig Complete.Complete.•• From ICSU log, From ICSU log, transmissionNetworktransmissionNetwork : :

iuiu--transporttransport--connectionconnection--failedfailed--toto--establish.establish.

•• Solution / Action proposedSolution / Action proposed::

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



Call Setup Failure (CAF) Case StudiesCall Setup Failure (CAF) Case Studies

Description:Description:Call Setup Failures. Call Setup Failures.

Possible Cause:Possible Cause:










TMSITMSI D5 C2 82 02 D5 C2 82 02

RNTIRNTI

Time_origTime_orig












TMSITMSI D5 C2 82 02 D5 C2 82 02

RNTIRNTI

Time_origTime_orig



RNC ID: 202 Cell ID: 22835RNC ID: 202 Cell ID: 22835



CAF #1 CAF #1 –– UL UL ““CM Service AbortCM Service Abort”” due to due to NemoNemo CAA=15sec Timed OutCAA=15sec Timed Out

TMSITMSI 00 07 DB 53 00 07 DB 53

RNTIRNTI RN23: 02 24 5 (= 8773)RN23: 02 24 5 (= 8773)




•• Fail Call CategoryFail Call Category::•• UE / Tool related: UL UE / Tool related: UL ““CM Service CM Service

AbortAbort”” due to due to NemoNemo CAA=15sec timed CAA=15sec timed out.out.

•• AnalysisAnalysis::•• UE / Tool related: UL UE / Tool related: UL ““CM Service CM Service

AbortAbort”” due to due to NemoNemo CAA=15sec timed CAA=15sec timed out. Call setup procedure was actually out. Call setup procedure was actually onon--going.going.

•• As seen from Events window, that As seen from Events window, that NemoNemo FMT sent CAA command but UE FMT sent CAA command but UE only sent only sent ““RRC Connection RequestRRC Connection Request””almost 15secs later. Resulting in CAA almost 15secs later. Resulting in CAA timed out timed out eventhougheventhough the call setup the call setup was onwas on--going. going. NemoNemo FMT issued FMT issued command to UE to abort.command to UE to abort.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAF #2 CAF #2 –– UL CM Service Abort UL CM Service Abort -- NemoNemo CAA Call Attempt=15secs TimedCAA Call Attempt=15secs Timed--out out –– Call Setup OnCall Setup On--goinggoing

TMSITMSI 2A 68 3F 03 2A 68 3F 03

RNTIRNTI RN22: 09 80 5 (= 38917)RN22: 09 80 5 (= 38917)




•• Fail Call CategoryFail Call Category::•• Tool related: UL CM Service Abort due Tool related: UL CM Service Abort due

to to NemoNemo CAA attempt timed out after CAA attempt timed out after 15secs.15secs.

•• AnalysisAnalysis::•• Tool related: UL CM Service Abort due Tool related: UL CM Service Abort due

to to NemoNemo CAA attempt timed out after CAA attempt timed out after 15secs. Call setup was actually on15secs. Call setup was actually on--going. After last going. After last cAFcAF under poor under poor coverage area, UE was receiving BCCH coverage area, UE was receiving BCCH of 22046 (not optimal cell). of 22046 (not optimal cell). NemoNemo sent sent CAA but 1CAA but 1stst RRC Connection Request RRC Connection Request was sent only 12secs later. Thus, while was sent only 12secs later. Thus, while call setup was oncall setup was on--going, going, NemoNemo tool tool CAA timer=15sec expired and call was CAA timer=15sec expired and call was aborted.aborted.


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAF #3 CAF #3 –– 2 x RRC Connection Request with No Response2 x RRC Connection Request with No ResponseTMSITMSI F2 5C 08 00 F2 5C 08 00

RNTIRNTI




•• Fail Call CategoryFail Call Category::•• Network related: 2 x RRC Connection Network related: 2 x RRC Connection

Request with no Response.Request with no Response.


Response.Response.•• Not a site problem since the Not a site problem since the

subsequent call setup on 12044 (179) subsequent call setup on 12044 (179) was successful.was successful.

•• Note: Note: NemoNemo PB does not count this as PB does not count this as a Call Setup Failure (CAF). However, a Call Setup Failure (CAF). However, since the time duration from the 1since the time duration from the 1stst

RRC Connection Request to the 3RRC Connection Request to the 3rdrd RRC RRC ConnConn ReqReq was >8secs, this would be was >8secs, this would be interpreted as a CAF by interpreted as a CAF by ActixActix..


ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No



CAF #1CAF #1--#4 #4 –– Call Setup Failed after Call Setup Failed after ““Call ProceedingCall Proceeding””–– DL RRC Connection ReleaseDL RRC Connection Release

TMSITMSI DD 58 E5 02 DD 58 E5 02

RNTIRNTI RN24:00 BA 9 (= 2985)RN24:00 BA 9 (= 2985)




•• Fail Call CategoryFail Call Category::•• Network related: Call setup failed after Network related: Call setup failed after

““Call ProceedingCall Proceeding”” –– DL RRC Connection DL RRC Connection Release.Release.

•• AnalysisAnalysis::•• Network problem between MG21 & Network problem between MG21 &

RN24/23, which started about this RN24/23, which started about this timing, caused all calls setups to fail timing, caused all calls setups to fail after after ““Call ProceedingCall Proceeding””, DL RRC , DL RRC Connection Release.Connection Release.

•• Solution / Action proposedSolution / Action proposed::•• TroubleshootedTroubleshooted realtimerealtime and and

resolved. Subsequent calls under resolved. Subsequent calls under RN23 & RN24 were successful.RN23 & RN24 were successful.

ScannerScanner

UE RSCPUE RSCP

UE Ec/NoUE Ec/No

nemo l3 analysis external v03

Documents