Layer 3 Analysis

L3 ANALYSIS / OPTIMIZATION EXAMPLES
(Using Nemo Outdoor)

05 November 2005 Nokia Networks OSP, Taiwan Version 0.1 (Internal) / Version 0.3 (External)
Company Confidential
1 2005 Nokia Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim
Objective of Case Studies

Objective of this slideset package is to consolidate all the learnings of L3 analysis / troubleshooting via using Nemo Analyzer or Nemo Outdoor Playback. This package would serve as a practical teaching guide / competence transfer to Partners L3 analyst who would be performing all subsequent L3 analysis for Initial Tunings, Cluster, Sub-Area, Area Tunings etc optimization works. The package is split into 2 main sections:
CAD Case Studies CAF Case Studies
Customized Nemo Workspace & Color Sets

Nemo Workspace for v4.15.24: (this may not work for v.25) Nemo Color Set:
CHT_Thruput_ColorSet.csf v22_rlim_default1_6630_gst_080505_rlim_Voice+PS.wor v22_rlim_default1_6650_gst_080105_rlim_Voice+PS.wor
Best practice suggestion
ScannerlLog
Always open *.dt1 & *.dt2, together with *.fs3 measurement data files. This would let the analyst have a sanity check if the radio environment is affecting both UEs or not e.g. Especially when trying to apply AdjsEcNoOffsets in cases of rapidly degrading CPICH Ec/No quality situations. And the scanner data would be used for missing neighbor detection, pilot pollutions and etc L1 optimization purposes. Always have the RNC Border MI layer opened in the map section. So that the Analyst would have a clear idea of the Inter-RNC SHO cases and in case SRNS relocation failures. Always work with L1 analyst to feedback / cross check with each other.
RNC Layer 1
Information Required for L3 Analysis / Optimization

Nemo measurement data logs (off course) 3G Site Master Configuration Database
IT Assist Tool v7.2
Daily WBTS Block Cell States report from NMC (However, this only provides a static snapshot at the end of the day. Unless the BTS is down for whole day, this report does not show the site being down for a short duration due to whatever problem. Analyst is advised to check Daily BTS Alarm History report for such details) Daily BTS Alarm History reports from NMC
?...?
Drop Call (CAD) Case Studies

Missing Neighbours Interference MR e1x with No ASU Response No MR after Last MC Inter-RNC SRNS Relocation Success Case Inter-RNC SRNS Relocation Failure Case Intra-Frequency Hardhandover (HHO) DL RRC Connection Release with Release Cause Unspecified .
Call Setup Failure (CAF) Case Studies

FMT tool related: Nemo CAA=15sec timeout or expired Missing Neighbour related Network related .
UMTS Basic Call Signaling

System Information Block (SIB) Location Update Voice MOC/MTC PS Data Call Multi RAB SHO
System Information Block (SIB)

Information Block MIB Description PLMN types & identities Scheduling information SIB references Optional SIB scheduling information NAS information UE timers & counters to be used in idle and connected mode URA identity list Cell selection and re-selection parameters Parameters for common physical channel configuration UL interference level Dynamic persistence level (fast changing parameters) Measurement control information to be used in the cell Neighbour list. SIB18
8 2005 Nokia
SB1 SIB1 SIB2 SIB3 SIB5 SIB7
SIB11
PLMN identities of neighboring cells to be considered in idle mode as well as in connected mode.
Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim
System Information Block (SIB)
PLMN Type
SIB Reference
Location Update(LU)
RRC Connection Stage Location Update Request Authentication Stage Location Update Accept RRC Connection Release
AMR MOC
RRC Connection Setup
Authentication Procedure
Radio Bearer Setup Procedure
Call Setup Success
Disconnect and Release Procedure
AMR MOC
UE
RRC_Connection_Request RRC_Connection_Setup RRC_Connection_Setup_Complete CM_Service_Request Authentication_Request Authentication Response Security_Mode_Command Security_Mode_Complete Setup Call_Proceeding
BTS
RNC
CS_CN
Radio_Bearer_Setup Radio_Bearer_Setup_Complete Alerting Connect Connect_Acknowledge
MS R R C :R R C C O N NE C T IO N R EQ U E ST
BT S
RN C
C S_C N
N BAP :R A DIO LIN K SET U P R EQ U EST
N BAP:R AD IO LIN K S ET U P R ESPO N SE AAL2S IG : E R Q AA L2SIG : EC F R R C :R R C C O N N EC T IO N SET UP
Note: Authentication & Security Mode Procedures Are switched off in this Reference signalling flow
MS BTS RNC
Call established
AMR MOC
CS_CN
L1 synchronisation N BA P:SYN C H R O N IZ AT IO N IN D IC AT IO N RR C :C O N N E CT IO N SET U P C O M PLET E R R C :IN IT IAL D IR EC T T R AN SF E R (C M Service Request) R AN A P:IN IT IAL U E M ESS AG E (CM Service Request)
RRC: DOW NLINK DIRECT TRANSFER (Disconnect) RANAP: DIRECT TRANSFER (Disconnect)
R AN AP: D IRE C T T R AN SF ER R R C : D O W N LIN K DIR EC T T R AN S F ER (C M S ervice Accept) (C M S ervice Accept)
RANAP: DIRECT TRANSFER (Release)

RR C : U PLIN K D IR EC T T R AN SF ER (Setup) R AN AP: D IR EC T T R A NS F ER (Setup)
RRC: UPLINK DIRECT TRANSFER (Release) RRC: DOW NLINK DIRECT TRANSFER (Release complete) RANAP: DIRECT TRANSFER (Release complete)
R AN AP: D IRE C T T R AN SF ER (C all Proceeding)
R RC : D O W N LIN K D IR EC T T R AN SF ER (C all Proceeding)
RANAP: Iu RELEASE COMMAND

R A N AP:R AB ASS IG N M EN T R EQ U ES T
RANAP: Iu RELEASE COMPLETE

N BAP :R A DIO LIN K R EC O N F IG U RA T IO N PR EPA R E N BA P:R AD IO LIN K R EC O NF IG U R AT IO N R EAD Y AA L2SIG : ER Q
RRC:CONNECTION RELEASE RRC:CONNECTION RELEASE COMPLETE NBAP:RADIO LINK DELETION REQUEST
AAL2S IG : E C F AAL2SIG : E RQ
NBAP:RADIO LINK DELETION RESPONSE

AA L2S IG : EC F N BAP:R AD IO LIN K R E CO N F IG U R AT IO N CO M M IT
AAL2SIG: REL AAL2SIG: RLC AAL2SIG: REL AAL2SIG: RLC
R R C : R AD IO BE AR ER SET U P R R C : R AD IO BEAR E R S ET U P C O M PLET E R AN A P:R AB ASS IG N M E N T R E SPO N SE
Call released
R AN AP: D IRE C T T R AN SF ER R R C : D O W N LIN K D IR EC T T R AN SF E R (Alerting) R R C : U P LIN K D IR E CT T R A N SF ER (C onnect) R AN A P: D IR EC T T R AN SF ER (C onnect) (A lerting)
13 2005 Nokia
R AN AP: D IR EC T T R A NS F ER (C onnect Acknowledge)
R R C : DO W N LIN K D IR E CT T R A N SF ER (C onnect A cknowledge)
C all established Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim
MTC (AMR)
MS
BTS
RNC
CS_CN
MTC
RANAP:PAG ING
RRC:PAG ING TYPE 1
RRC:RRC CO NNECTION REQ UEST NBAP:RADIO LINK SETUP REQ UEST
NBAP:RADIO LINK SETUP RESPONSE AAL2SIG: ERQ AAL2SIG: ECF RRC:RRC CO NNECTION SETUP
L1 synchronisation NBAP:SYNCHRONIZATIO N INDICATION RRC:CO NNECTION SETUP CO MPLETE
Note: Authentication & Security Mode Procedures Are switched off in this Reference signalling flow
RRC:INITIAL DIRECT TRANSFER (Paging response) RANAP:INITIAL UE MESSAGE (Paging response)
RANAP: DIRECT TRANSFER (Setup) RRC: DOW NLINK DIRECT TRANSFER (Setup)
RRC: UPLINK DIRECT TRANSFER (Call confirmed) RANAP: DIRECT TRANSFER (Call confirmed) RANAP:RAB ASSIGNMENT REQUEST
NBAP:RADIO LINK RECO NFIGURATION PREPARE
NBAP:RADIO LINK RECO NFIGURATION READY
AAL2SIG: ERQ
AAL2SIG : ECF AAL2SIG: ERQ AAL2SIG : ECF NBAP:RADIO LINK RECONFIG URATION COMMIT RRC: RADIO BEARER SETUP
RRC: RADIO BEARER SETUP COMPLETE
RANAP:RAB ASSIGNMENT RESPONSE RRC: UPLINK DIRECT TRANSFER (Alerting) RANAP: DIRECT TRANSFER (Alerting) RANAP: DIRECT TRANSFER RRC: DOW NLINK DIRECT TRANSFER (Connect) (Connect)
RRC: UPLINK DIRECT TRANSFER (Connect Acknowledge)
Call established
RANAP: DIRECT TRANSFER (Connect Acknowledge)
15
2005 Nokia
PS DATA CALL
RRC 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 CALL
UE
RRC_Connection_Request RRC_Connection_Setup RRC_Connection_Setup_Complete
BTS
RNC
PS_CN
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
MS RRC:RRC CONNECTION REQUEST
BTS
RNC
PS_CN
NBAP:RADIO LINK SETUP REQUEST
NBAP:RADIO LINK SETUP RESPONSE AAL2SIG: ERQ AAL2SIG: ECF RRC:RRC CONNECTION SETUP
PS DATA CALL
MS BTS RNC CS_CN
L1 synchronisation NBAP:SYNCHRONIZATION INDICATION

PDP Context is active
RRC:CONNECTION SETUP COM PLETE

RRC: DT (Deactivate PDP context request) RANAP: DT (Deactivate PDP context request)
RRC:INITIAL DIRECT TRANSFER (Attach Request) RANAP:INITIAL UE M ESSAGE (Attach Request)
RANAP: RAB ASSIG NM ENT REQ UEST (Release)
RANAP: DIRECT TRANSFER RRC: DOW NLINK DIRECT TRANSFER (Attach Accept) (Attach Accept)
NBAP:RL RECONFIG URATIO N PREPARE NBAP:RL RECONFIG URATIO N READY
RANAP: RAB ASSIG NM ENT RESPONSE
RRC: DOW NLINK DIRECT TRANSFER (Attach Com plete) RANAP: DIRECT TRANSFER RRC: UPLINK DIRECT TRANSFER (SM :Activate PDP Context request) (Attach Com plete) RANAP: DIRECT TRANSFER (SM : Activate PDP Context request)
RRC: RADIO BEARER RELEASE RRC: DT (Deactivate PDP context accept) RANAP: DT (Deactivate PDP context accept)
NBAP:RL RECONFIGURATION COM M IT
RANAP:RAB ASSIGNM ENT REQUEST
RRC:RADIO BEARER RELEASE CO M PLETE RRC: DT(Detach request) RANAP: DT(Detach request)
RRC: RADIO BEARER SETUP
RRC: RADIO BEARER SETUP COM PLETE

RANAP: DT(Detach accept)
RANAP:RAB ASSIGNM ENT RESPONSE
RRC: DT(Detach accept)
RANAP: DIRECT TRANSFER (SM : Activate PDP Context accept) RRC: DOWNLINK DIRECT TRANSFER (SM : Activate PDP Context Accept)
NBAP:RL DELETION REQ UEST AAL2SIG: REL NBAP:RL DELETIO N RESPONSE AAL2SIG: RLC
RRC: M EASUREM ENT REPORT
AAL2SIG : REL
NBAP:RADIO LINK RECONFIGURATION PREPARE NBAP:RADIO LINK RECONFIGURATION READY

RRC: RRC CO NNECTION RELEASE
AAL2SIG : RLC RANAP: Iu Release Comm and RANAP: Iu Release Com plete
AAL2SIG: ERQ
RRC: RRC CO NNECTIO N RELEASE CO MPLETE
AAL2SIG: ECF NBAP:RADIO LINK RECONFIGURATION COM M IT RRC: TRANSPORT CHANNEL RECONFIGURATION RRC: TRANSPORT CHANNEL RECONFIGURATION COM PLETE
Uplink and downlink data transfer
18
2005 Nokia
Multi RAB (Simultaneous AMR+PS)
PS Disconnect
AMR
AMR Disconnect
PS
SHO_e1a
UE BTS RNC
Handover tresholds fulfilled (MEHO) - Event 1A is triggered
RRC: Measurement Report
NBAP: Radio Link Addition Request
NBAP
NBAP: Radio Link Addition Response RRC: Active Set Update Request
RRC: Active Set Update Complete
SHO_e1b
UE BTS RNC
Handover tresholds fulfilled (MEHO) - Event 1B is triggered
RRC Measurement Report
RRC: Active Set Update Request
NBAP: Radio Link Deletion Request
NBAP: Radio Link Deletion Response
SHO_e1c
UE BTS RNC
Handover tresholds fulfilled (MEHO) - Event 1C is triggered
RRC: Measurement Report
NBAP: Radio Link Addition Request
NBAP:Radio Link Addition Response
RRC: Active Set Update Request
NBAP: Radio Link Deletion Request
NBAP: Radio Link Deletion Response
Do not always assume that
Missing Neighbours
Description: Missing neighbours. Possible Cause: Human negligence . Poor NB planning. Street canyon effect that requires more than 2 tier NB planning etc.
Missing Neighbour Prior 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 neighbour to 22750 (SC233). How do we know it is a case of missing neighbour? Just take a look at the
Missing Neighbour After Call Drop
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.
Cell Reselection to 13184878 dec = C92F6E hex (RNC ID = C9 = 201, Cell ID = 2F6E = 12142 (SC302)
CAF #1-1 4 x RRC Connection Request

TMSI RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) RN22 / 32897 (312) D5 C2 82 02
Fail Call Category: Category: Radio Related: 4 x RRC Connection Request with no response. Missing neighbour definition. Analysis: Analysis: 4 x RRC Connection Request with no response. After the last drop call (CAD #1), UE did not cell reselect to the best serving cell along that road due to missing neighbour definitions between 32897 (312) & 22835 (309). Solution proposed: proposed: Neighbour ADJS definitions: 32897 (312) 22835 (309).

Fail Call Category: Category: Radio Related: 4 x RRC Connection Request with no response. Missing neighbour definition. Analysis: Analysis: 4 x RRC Connection Request with no response. After the last drop call (CAD #1), UE did not cell reselect to the best serving cell along that road due to missing neighbour definitions between 32897 (312) & 22835 (309). Solution proposed: proposed: Neighbour ADJS definitions: 32897 (312) 22835 (309). RNC ID: 202 RNC ID: 202 Cell ID: 22835 Cell ID: 22835
CAD #1-1 MR e1a with No ASU Response

TMSI RNTI 00 06 B3 E3 RN22: 12 D7 9 (= 77177) 17:12:20.679 RN22 / 22552 (136) RN22 / 22552 (136)
UE RSCP UE RSCP
Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC)
Drop Call Category: Category: RF Related: MR e1a with No ASU response. Missing Neighbour definitions UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with No ASU response. Missing Neighbour definitions between 22552 (136) and 32873 (173).
Solution / Action proposed: proposed: Scanner Scanner ADJS definition: 22552 (136) 32873 (173) Redrive for verification.

UE RSCP UE RSCP

TMSI RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) CD A7 D3 02 RN23:0C594 (=50580) RN24: 09E97 (=40599) 15:46:55.393 RN23 / 32536 (340) RN24 / 12183 (156)
Drop Call Category: Category: Site related: MR e1a with No ASU response. Analysis: Analysis: MR e1a with No ASU response. Site 2335U was down on 23 Feb. See WBTS Cell Status report. Neighbour definition to provide as backup incase of site outage. Solution / Action proposed: proposed: NB Definitions: 12183 (156) 22545 (311) 22395 (151) 12350 (273)

TMSI RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) CD A7 D3 02 RN23:0C594 (=50580) RN24: 09E97 (=40599) 15:46:55.393 RN23 / 32536 (340) RN24 / 12183 (156)
Drop Call Category: Category: Site related: MR e1a with No ASU response. Analysis: Analysis: MR e1a with No ASU response. Site 2335U was down on 23 Feb. See WBTS Cell Status report. Neighbour definition to provide as backup incase of site outage. Solution / Action proposed: proposed: NB Definitions: 12183 (156) 22545 (311) 22395 (151) 12350 (273)

TMSI RNTI CD A7 D3 02 RN23:0C318 (= 49944) RN21:03071 (=12401) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 12:08:42.226 RN23 / 12705 (158) RN21 / 26009 (333)
UE RSCP UE RSCP Problem seemed to start here. Problem seemed to start here. SC318 was not in SC318 was not in UEs NB List. MC did not UEs NB List. MC did not include SC318 although include SC318 although defined in 26009 (325) ADJS. defined in 26009 (325) ADJS. This caused unnecessary This caused unnecessary AS 325 having bad Ec/No AS 325 having bad Ec/No since SC318 was an since SC318 was an interferer. interferer. UE Ec/No UE Ec/No
Drop Call Category: Category: UE related: MR e1a with No ASU response. Analysis: Analysis: MR e1a with No ASU response. However, UE AS 26009 (333) was sending MR e1a to select the worst Ec/No SC in Monitored set instead of Ec/No Best Ec/No SC. Ec/No Subsequently, call was dropped due to UE bad AS SC Ec/No => high BLER. Ec/No Solution / Action proposed: proposed: Scanner Scanner Redrive for verification.
05Feb23 120829-v vip-2.zip
RNTI_00003071.zip

TMSI RNTI CD A7 D3 02 RN23:0C318 (= 49944) RN21:03071 (=12401) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 12:08:42.226 RN23 / 12705 (158) RN21 / 26009 (333)
UE RSCP UE RSCP
Drop Call Category: Category: UE related: MR e1a with No ASU response. UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with No ASU response. However, UE AS 26009 (333) was sending MR e1a to select the worst Ec/No SC in Monitored set instead of Ec/No Best Ec/No SC. Ec/No Subsequently, call was dropped due to UE bad AS SC Ec/No => high BLER. Ec/No Solution / Action proposed: proposed: Scanner Scanner Redrive for verification.
No MR after Last MC
Description: UE did not perform any Measurement Reporting after last successful ASU + ASUC + Measurement Control sent, although the reporting criteria has been reached to perform MR e1a, e1b or e1c. Possible Cause: Since Soft Handover (Soft & Softer) is MEHO (Mobile Evaluated Handover), the decision to send MR is completely relying on UE when reporting criteria has been reached. Could only suggest that it is UE related problem.
CAD #3-1 No MR After last MC

TMSI RNTI DD 05 E4 02 RN23:01 E8 2 (= 7810) RN24:0D3F0 (=54256) RN24:0D3F7 (=54263) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 9:58:25.348 RN23 / 12501 (176) RN24 / 32167 (360)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. UE Ec/No UE Ec/No Analysis: Analysis: No MR after last MC. After last successful MR e1b with ASUC to remove intra-sector SC352 from AS, intrathe UE did not perform any subsequent MR (duration of approx >2mins drive) until call was dropped due to bad AS Ec/No. Ec/No.
Scanner Scanner
Solution / Action proposed: proposed: UE behaviour. Redrive for verification. behaviour.
CAD #3-2 No MR After last MC

TMSI RNTI DD 05 E4 02 RN23:01 E8 2 (= 7810) RN24:0D3F0 (=54256) RN24:0D3F7 (=54263) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 9:58:25.348 RN23 / 12501 (176) RN24 / 32167 (360)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. UE Ec/No UE Ec/No Analysis: Analysis: No MR after last MC. After last successful MR e1b with ASUC to remove intra-sector SC352 from AS, intrathe UE did not perform any subsequent MR (duration of approx >2mins drive) until call was dropped due to bad AS Ec/No. Ec/No.
Scanner Scanner
Solution / Action proposed: proposed: UE behaviour. Redrive for verification. behaviour.
S2N: CAD #1-2 No MR after Last MC

TMSI RNTI 00 01 6F 94 RN21:12 36 E (= 74606) RN24: 13:00:51.674 RN21 / 12745 (297) RN24 / 32335 (169)
RSCP RSCP
Drop Call Category: Category: Radio Related: No MR after last MC. Analysis: Analysis:
Ec/No Ec/No
No MR after last MC. Due to street canyon effect, 32335 (169) is propagating up Fushing Road. This is not a missing neighbour. Suggest to neighbour. reduce CPICH Tx Power of 32335 (169). Problem could be resolved earlier, if we also ensure mutual faster SHO, AdjsEcNoOffset = 4dB is added mutually between 32713 (146) & 12324 (131).
Scanner Scanner
Solution proposed: proposed: Reduce 32335 (169) CPICH Tx Power from 33dBm to 30dBm. Mutual AdjsEcNoOffset: AdjsEcNoOffset: 32713 (146) 12324 (131) = 4dB
S2N: CAD #1-2 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 #2-1 No MR after last MC

TMSI RNTI 00 08 D6 E3 RN23: 09 4F 7 (= 38135) RN24: 05 E6 5 (= 24165) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 13:54:26.467 RN23 / 12707 (159) RN24 / 22183 (164)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. Analysis: Analysis: UE Ec/No UE Ec/No UE Related: No MR after last MC. Subsequently, AS (SC164) Ec/No Ec/No quality degraded, resulting in high BLER & call was dropped. This is UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading. See next slide.
Scanner Scanner
Solution / Action proposed: proposed: Redrive on 7 June for verification..
CAD #2-2 No MR after last MC (UE2: PS FTP => No Drop Call Encountered)
TMSI RNTI 00 08 D6 E3 RN23: 09 4F 7 (= 38135) RN24: 05 E6 5 (= 24165) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 13:54:26.467 RN23 / 12707 (159) RN24 / 22183 (164)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. Analysis: Analysis: UE Ec/No UE Ec/No UE Related: No MR after last MC. Subsequently, AS (SC164) Ec/No Ec/No quality degraded, resulting in high BLER & call was dropped. This is UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading. Here, UE2 performing PS FTP downloading does not have any drop call. FTP Thruput FTP Thruput

TMSI RNTI 00 08 E2 13 RN21: 02 41 E (= 9246) RN23: 09 87 4 (= 39028) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 15:19:37.394 RN21 / 12188 (327) RN23 / 12518 (205)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. Analysis: Analysis: UE Ec/No UE Ec/No UE Related: No MR after last MC. Subsequently, after approx 3 minutes of driving, UE AS (SC205) Ec/No quality Ec/No degraded, resulting in high BLER & call was dropped. This is UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading. See next slide.
Scanner Scanner Solution / Action proposed: proposed: Redrive on 7 June for verification..
CAD #4-2 No MR after last MC (UE2: PS FTP => No Drop Call Encountered)
TMSI RNTI 00 08 E2 13 RN21: 02 41 E (= 9246) RN23: 09 87 4 (= 39028) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 15:19:37.394 RN21 / 12188 (327) RN23 / 12518 (205)
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. Analysis: Analysis: UE Ec/No UE Ec/No UE Related: No MR after last MC. Subsequently, after approx 3 minutes of driving, UE AS (SC205) Ec/No quality Ec/No degraded, resulting in high BLER & call was dropped. This is UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading. Here, UE2 performing PS FTP downloading does not have any drop call. FTP Thruput FTP Thruput
CAD UE Related No MR after Last MC

TMSI RNTI 00 3F E7 C6 (4188102) 06 19 2 (24978) 18:29:13.959 RN23 / 12700 (133) RN21 / 22716 (306)
UE RSCP UE RSCP
Drop call category: UE related Analysis: UE was not sending any MR which caused the failure in the softer HO. As Ec/No of SC306 in the AS degraded, Ec/No and Ec/No of SC298 gets stronger in the Ec/No MS, call drop subsequently due to UE not sending MR. UE was hanged for almost 2 min., in which the softer HO should have performed.
UE Ec/No UE Ec/No
Scanner Scanner
Proposed solution

TMSI RNTI 00 08 83 DB RN23: 06 FA 8 (= 28584) 14:26:39.499 RN23 / 12508 (201) RN23 / 2508
UE RSCP UE RSCP
Drop Call Category: Category: UE Related: No MR after last MC. Analysis: Analysis: UE Ec/No UE Ec/No UE Related: No MR after last MC. Subsequently, AS (SC209,217,201) Ec/No quality degraded, resulting in Ec/No high BLER & call was dropped. However, in this case, UE did not perform optimum SHO. In the last MR+ASU, UE did not send MR e1a (208) which is the best monitored candidate cell. Subsequently, UE did not attempt MR e1c to replace AS with SC208, probably due to AS Ec/No quality Ec/No already bad.
Scanner Scanner
MR e1x with No ASU Response

Description: MR e1x (a/b/c) with No ASU Response from Network. Possible Cause: Do no always assume that this is Network related. It could be due to radio or UE related, even Missing Neighbour could cause this : 1) Network / BTS related: 2) UE related: UE did not perform optimum SHO in the earlier MR+ASU+ASUC+MC, thus subsequent MRs could be non-optimum. 3) Radio related: Due to non-dominance etc. Could be improved by optimizing L1 coverage of that stretch. Or due to rapid changing radio environment, AS Ec/No degraded rapidly (should verify with both UEs traces to confirm), should use AdjsEcNoOffset to advance SHO or mutually make more favorable for SHO.

UE RSCP UE RSCP
This is a classic case of MR e1a with33 3 (= 4915) This is a classic case of MR e1a with No RNTI RN24: 01 No ASU Response that is NOT due to Network ASU Response that is NOT due to Network Time_orig 18:51:48.476 Problem but due to rapid changing RF Problem but due to rapid changing RF environment RNC_orig / CID (SC) RN24 / 32324 (147) (Ec/No quality). This can be environment (Ec/No quality). This can be (Ec/No RNC_drop / / (215) can be confirmed by CID (SC) RN23if 22712same can be confirmed by observing if the same observing the deep fade is experienced by the 2nd UE. deep fade is experienced by the 2nd UE. Which in this case it was. Which in this case it was. This can be optimized via Individual CPICH Drop Call Category: Category: This can be optimized via Individual CPICH Ec/No Offset to Related: MRthe SHO. No ASU Ec/No Offset RF advance the SHO. to advance e1a with Ec/No
response.
TMSI
00 07 DA BB
UE Ec/No UE Ec/No
Analysis: Analysis: MR e1a with No ASU response. Observed the handover region between SC215 & 133 with rapid degradation of Ec/No quality of SC215, Ec/No due to position of sector 2 antenna and building obstructions. Propose to use ADJS CPICH Ec/No Ec/No Offset to mutually make SC215 & SC133 appear more favourable as SHO candidate.
Scanner Scanner
Solution / Action proposed: proposed: Mutually define: 22712 (215) 12700 (133) AdjsEcNoOffset = 6dB Redrive for verification.

TMSI RNTI 00 07 DA BB RN24: 01 33 3 (= 4915) 18:51:48.476 RN24 / 32324 (147) RN23 / 22712 (215)
UE RSCP UE RSCP
Drop Call Category: Category: RF Related: MR e1a with No ASU response. Analysis: Analysis: MR e1a with No ASU response. Observed the handover region between SC215 & 133 with rapid degradation of Ec/No quality of SC215, Ec/No due to position of sector 2 antenna and building obstructions. Propose to use ADJS CPICH Ec/No Ec/No Offset to mutually make SC215 & SC133 appear more favourable as SHO candidate. Scanner Scanner Solution / Action proposed: proposed: Mutually define: 22712 (215) 12700 (133) AdjsEcNoOffset = 6dB Redrive for verification.
UE Ec/No UE Ec/No
CAD #3-1 MR e1a with No ASU Response Radio related

TMSI RNTI 00 07 F0 93 RN23: 02 AA 4 (= 10916) 10:24:46.945 RN23 / 26012 (335) RN23 / 32187 (245)
UE RSCP UE RSCP
Drop Call Category: Category: Radio Related: MR e1a with No ASU response. Analysis: Analysis: Radio Related: MR e1a with No ASU response, possible due to AS (SC245) Ec/No quality degraded rapidly. Ec/No Possibly DL broken. Weak dominance stretch around Presidential Palace area. Difficulty in getting candidate sites. Try to create dominance using 22367 (234) by changing realtilt E-ADT from 6deg to 4deg. Scanner Scanner Solution / Action proposed: proposed: 22367 (234):
E-ADT = 6deg to 4deg
UE Ec/No UE Ec/No
Redrive on 3 June for verification..

TMSI RNTI DD 58 E5 02 RN21:05 A8 E (= 23182) 15:52:26.428 RN21 / 32779 (150) RN21 / 326025 (340)
UE RSCP UE RSCP
Drop Call Category: Category: Site Related: MR e1a with no ASU. Analysis: Analysis: UE Ec/No UE Ec/No MR e1a with no ASU response. Site 2151U was not transmitting on the day of drive (link problem). Check BTS alarm history of 4 Mar 05. In this case, 12151 (182) was not defined as neighbor with 36025 (340). As such, monitored NB list was non-optimum, resulting in MR e1a to nonother non-optimum MS cells. nonScanner Scanner Solution / Action proposed: proposed: Confirmed from BTS alarm history that site 2151U was down on day of drive. Possibly define: 36025 (340) 12520 (182) as a backup when 2151U is down. Redrive for verificationn when 2151U is transmitting again.

TMSI RNTI DD ED E4 02 RN23:01 FB A (= 8122) RN24: 0D 47 C (= 54396) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 11:32:47.821 RN23 / 32530 (222) RN24 / 32700 (149)
UE RSCP UE RSCP
Drop Call Category: Category: Network related: MR e1a with No ASU response. UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with No ASU response. The last successful MR e1b with ASUC to remove SC311 from AS => SRNC Reloc to RN24, did not receive any MC (possibly due to radio link lost) Subsequent MR e1a with no ASU response resulted in AS SC149 Ec/No Ec/No degraded and call was dropped due to high BLER. Solution / Action proposed: proposed: Site 2700U to be rehomed from RN24 to RN23 in Phase 2. Redrive for verification.
RNTI_00001FBA_0273.zip
Scanner Scanner
RNTI_0000D47C_0175.zip

TMSI RNTI DD ED E4 02 RN23:01 FB A (= 8122) RN24: 0D 47 C (= 54396) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 11:32:47.821 RN23 / 32530 (222) RN24 / 32700 (149)
UE RSCP UE RSCP
Drop Call Category: Category: Network related: MR e1a with No ASU response. UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with No ASU response. The last successful MR e1b with ASUC to remove SC311 from AS => SRNC Reloc to RN24, did not receive any MC (possibly due to radio link lost) Subsequent MR e1a with no ASU response resulted in AS SC149 Ec/No Ec/No degraded and call was dropped due to high BLER. Solution / Action proposed: proposed: Site 2700U to be rehomed from RN24 to RN23 in Phase 2. Redrive for verification.
Scanner Scanner

TMSI DD 4E A5 02 01 E5 0 (= 7760)
13 Jan 2005
RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC)
RN21 / 38323 (202)
Drop Call Category: Category: Site Related: MR e1a with No ASU response. However, this is due to RN23 Site 2530U problem (as would be observed in the subsequent unsuccessful handover attempts to this cell. Analysis: Analysis: UE AS 32151 (197) sends MR e1a 12520 (182) with no ASU response. From MS, 12520 (182) RSCP & Ec/Nno quality was quite low. Current EADT of 12520 (182) & 22520 (190) is 8deg. Propose to uptilt 3deg to improve dominance & quality. Solution proposed: proposed: 12520 (182) & 22520 (190) EADT change from 8deg to 5deg. Redrive for verification on 14 Jan. No drop call.

TMSI DD 4E A5 02 01 E5 0 (= 7760)
14 Jan 2005 Drive #1 no drop call
RN21 / 38323 (202)

TMSI DD 4E A5 02 01 E5 0 (= 7760)
14 Jan 2005 Drive #2 no drop call
RN21 / 38323 (202)

UE RSCP UE RSCP

UE RSCP UE RSCP
CAD #1-1 MR e1c with No ASU Response

TMSI RNTI F2 41 08 00 RN26: 01 73 1 (= 5937) 11:42:04.278 RN26 / 28132 (280) RN26 / 12256 (159)
UE RSCP UE RSCP
Drop Call Category: Category: RF Related: MR e1c with No ASU response. UE Ec/No UE Ec/No Analysis: Analysis: MR e1c with No ASU response. No coverage dominance along this stretch of highway. Dominance would be improved by optimizing electrical tilt of 12256 (159).
Scanner Scanner
Solution / Action proposed: proposed: To implement 12256 (159) E-ADT Euptilt of 2 degs to improve dominance along highway. Redrive for verification.

TMSI RNTI DD 2A F1 02 RN23:01 0B C (= 4284) RN24:00 B9 B (= 2971) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 10:03:26.227 RN23 / 12500 (302) RN24 / 12357 (300)
UE RSCP UE RSCP
Drop Call Category: Category: Network Related: MR e1a with no ASU response. UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with no ASU response. Network problem between MG21 & RN24/23, which started about this timing, caused all calls setups to fail after Call Proceeding, DL RRC Proceeding Connection Release.
Scanner Scanner
Solution / Action proposed: proposed: Troubleshooted realtime and resolved. Subsequent calls under RN23 & RN24 were successful.
CAD #3-1 MR e1a with No ASU Response FMT Tool Problem

Flatliner Tool Flatliner Tool Malfunctioned. Malfunctioned. Both UE traces same. Both UE traces same.
TMSI RNTI 00 09 ED 72 RN23: 11 49 D (= 70813) 11:11:19.305 RN23 / 12501 (176) RN23 / 12160 (203)
UE RSCP UE RSCP
Drop Call Category: Category: Tool related: MR e1a with No ASU response. FMT Tool not responding / malfunctioned. Analysis: Analysis: Tool related: MR e1a with No ASU response. FMT Tool not responding / malfunctioned. As observed from trace, the flatliner of the measurement traces for BOTH UEs indicated that the FMT tool had stopped responding. responding. Scanner Scanner This drop call is not due to network problem. Solution / Action proposed: proposed: Redrive for verification.
UE Ec/No UE Ec/No
CAD #6-1 No MC after Last ASU+ASUC, MR e1a with No ASU Response

TMSI RNTI 00 08 89 E3 RN24: 04 1E 2 15:21:53.990 RN24 / 32132 (217) RN24 / 22573 (311)
UE RSCP UE RSCP
UE Ec/No UE Ec/No
Drop Call Category: Category: Network Related: No MC after last ASU+ASUC, MR e1a with No ASU response. (Note: somehow, Uu log did not record the RRC Conn Setup RNTI for voice call (IMSI: 349), only for PS call (IMSI: 348 => 041E1)) Analysis: Analysis: No MC after last ASU+ASUC, MR e1a with No ASU response. Softer HO failure. However, in this case, UE did not perform optimum SHO. In the last MR+ASU, UE did not send MR e1a (softer 303) which is the best monitored candidate cell (see next slide). Subsequently, UE did not attempt MR e1a to add AS with SC303, probably due to AS Ec/No quality already bad. Ec/No Solution / Action proposed: proposed: Redrive for verification.
Scanner Scanner
CAD #6-2 No MC after Last ASU+ASUC, MR e1a with No ASU Response

TMSI RNTI 00 08 89 E3 RN24: 04 1E 2 15:21:53.990 RN24 / 32132 (217) RN24 / 22573 (311)
UE RSCP UE RSCP
Drop Call Category: Category: Network Related: No MC after last ASU+ASUC, MR e1a with No ASU response. Analysis: Analysis: No MC after last ASU+ASUC, MR e1a with No ASU response. Softer HO failure. However, in this case, UE did not perform optimum SHO. In the last MR+ASU, UE did not send MR e1a (softer 303) which is the best monitored candidate cell (see next slide). => UE malfunctioned?? Subsequently, UE did not attempt MR e1a to add AS with SC303, probably due to AS Ec/No quality already bad. Ec/No Solution / Action proposed: proposed:
UE Ec/No UE Ec/No
Scanner Scanner
Redrive for verification.
CAD #1-1 MR e1a with No ASU Response (BTS / Radio) (02 June 2005)
TMSI RNTI 00 07 F0 93 RN21: 03 79 A (= 14234) RN24: 03 27 9 (= 12921) RN24: 03 28 7 (= 12935) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 14:47:39.503 RN21 / 12188 (327) RN24 / 32324 (147)
UE RSCP UE RSCP
Drop Call Category: Category: BTS Related: MR e1a with No ASU response. Analysis: Analysis: BTS Related: MR e1a with No ASU response, due to AS SC147 bad or rapid fading of Ec/No quality from approx 5dB Ec/No to 25dB. However, it was suspected that the BTS could have some problem at that instant, instead of the Nemo FMT & UE. In any case, would be checking the 2324U detailed BTS alarm history for 02 June to further investigate. Next slide showed same route driven on 01 June, no problem or drop call. Solution / Action proposed: proposed: Check 2324U detailed BTS alarm history for 02 June. WCDMA Cell Out of Use during the above aforesaid period. Redrive for verification.
UE Ec/No UE Ec/No
Scanner Scanner
2324U_0602.log
CAD #1-2 MR e1a with No ASU Response (01 June 2005)

TMSI RNTI 00 07 F0 93 RN21: 03 79 A (= 14234) RN24: 03 27 9 (= 12921) RN24: 03 28 7 (= 12935) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 14:47:39.503 RN21 / 12188 (327) RN24 / 32324 (147)
UE RSCP UE RSCP
Drop Call Category: Category: BTS / Radio Related: MR e1a with No ASU response. UE Ec/No UE Ec/No Analysis: Analysis: BTS / Radio Related: MR e1a with No ASU response, due to AS SC147 bad or rapid fading of Ec/No quality from Ec/No approx 5dB to 25dB. However, it was suspected that the BTS could have some problem at that instant, instead of the Nemo FMT & UE. In any case, would be checking the 2324U detailed BTS alarm history for 02 June to further investigate. Next slide showed same route driven on 01 June, no problem or drop call. Solution / Action proposed: proposed: Check 2324U detailed BTS alarm history for 02 June. Redrive for verification.
Scanner Scanner

Observed from UE that RSCP & Observed from UE that RSCP & Ec/No of ALL AS & Monitored Ec/No of ALL AS & Monitored Set degraded all at same time. Set degraded all at same time. Suggesting that possible BTS or Suggesting that possible BTS or RNC problem. RNC problem. Also, no meas data on Scanner. Also, no meas data on Scanner.
TMSI RNTI 00 08 83 DB RN23: 06 FB 8 (= 28600) 14:29:23.733 RN23 / 22510 (208) RN23 / 16012 (327)
UE RSCP UE RSCP
Drop Call Category: Category: Radio Related: MR e1a with No ASU response. BTS Analysis: Analysis: Radio Related: MR e1a with No ASU response, possible due to AS (SC327) Ec/No quality degraded rapidly. Ec/No Possibly DL broken. Check BTS alarm history for 6012U on 3 June. Need to check RF coverage between 16012 & 26012.
UE Ec/No UE Ec/No
Scanner Scanner
Solution / Action proposed: proposed: Check BTS alarm history for 6012U on 3 June. Redrive on 6 June for verification..

TMSI RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 00 08 83 DB RN23: 06 FB 8 (= 28600) 14:29:23.733 RN23 / 22510 (208) RN23 / 16012 (327)
Drop Call Category: Category: Radio Related: MR e1a with No ASU response. Analysis: Analysis:
Checking Alarm history of 6012U on 03 June 05 Reviewed that Site / all cells were indeed down at That exact time of driving through !!
Radio Related: MR e1a with No ASU response, possible due to AS (SC327) Ec/No quality degraded rapidly. Ec/No Possibly DL broken. Check BTS alarm history for 6012U on 3 June. Need to check RF coverage between 16012 & 26012.
Solution / Action proposed: proposed: Check BTS alarm history for 6012U on 3 June. Alarm history reviewed that Redrive on 6 June for verification..
CAD #3-1 MR e1b with No ASU Response

TMSI RNTI 00 09 7B 32 RN23: 0C D3 3 (= 52531) RN24: 08 05 7 (= 32855) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 12:05:12.811 RN21 / 12188 (327) RN23 / 12518 (205)
UE RSCP UE RSCP
Drop Call Category: Category: Network Related: MR e1b with no ASU response. Analysis: Analysis: Network Related: MR e1b with no ASU response. Subsequently, call was dropped due to AS high BLER. This seemed to be specific UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading. See next slide.
UE Ec/No UE Ec/No
Scanner Scanner Solution / Action proposed: proposed: Redrive for verification..
RRC_Mon_00008057_0CF0.zip
CAD #3-2 MR e1b with No ASU Response

TMSI RNTI 00 09 7B 32 RN23: 0C D3 3 (= 52531) RN24: 08 05 7 (= 32855) Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC) 12:05:12.811 RN21 / 12188 (327) RN23 / 12518 (205)
UE RSCP UE RSCP
Drop Call Category: Category: Network Related: MR e1b with no ASU response. Analysis: Analysis: Network Related: MR e1b with no ASU response. Subsequently, call was dropped due to AS high BLER. This seemed to be specific UE related since for the SHO was successful for the concurrently running UE for PS FTP downloading.
UE Ec/No UE Ec/No
FTP Thruput FTP Thruput Solution / Action proposed: proposed: Redrive for verification..

TMSI RNTI F2 5C 08 00 RN26: 01 8B A (= 6330) 14:52:26.242 RN26 / 38041 (268) RN23 / 22500 (310)
UE RSCP UE RSCP
Drop Call Category: Category: Site Related: MR e1a with No ASU response. Site 8002U related. UE Ec/No UE Ec/No Analysis: Analysis: MR e1a with No ASU response. This whole stretch of WenHwa Road is served by 28002 (259). However, on the day & period of drive, Site 8002U BTS alarm history indicated NBAP link failure and site failure was blocked due to LI (RNC time: LI 2.42pm~2.52pm). Call was dropped due to poor Ec/No. Ec/No.
Scanner Scanner
Solution / Action proposed: proposed: Investigate site bts alarm history. Redrive for verification.
CAF #4 RRC Connection Reject with cause Unspecified

TMSI RNTI F2 5C 08 00
UE RSCP UE RSCP
14:54:17.291 RN26 / 28002 (259)
Fail Call Category: Category: Site Related related: RRC Connection related: Reject with cause unspecified. unspecified UE Ec/No UE Ec/No Analysis: Analysis: Site Related related: RRC Connection related: Reject with cause unspecified. unspecified However, on the day & period of drive, Site 8002U BTS alarm history indicated NBAP link failure and site failure was blocked due to LI (RNC time: LI 2.42pm~2.52pm) Scanner Scanner Site subsequently recovered around 2.52 and subsequent call attempt made on SC259 was successful. Solution / Action proposed: proposed: Redrive for verification.
Intra-Frequency HardHandover (HHO) Case

Description: Intra-Frequency HardHandover (HHO) Case. Possible Cause:
HardHandover (HHO) Iur Congestion Case
Inter-RNC intra-frequency Hard Handover (HHO)

Intra-frequency hard handover is required to ensure handover between cells controlled by different RNCs when an interRNC Soft Handover is not possible
No Iur between RNCs Iur congestion or failure
CN CN
Iu
RNC
Iu
RNC RNC
Iu
Iu
RNC
Intra-frequency hard Handover is lossless for NRT radio bearer but it causes short disconnection of RT radio bearer. Intra-frequency hard handover decisions made by the RNC are based on the intrafrequency measurement results, which are usually applied to the SHO procedure Also Enable Inter-RNC SHO parameter in intra-frequency HO path defines whether intra-frequency HO from the serving cell to a specified neighbour cells is performed as soft of hard Mobile evaluated Handover (MEHO) Company Confidential
Iur
Iur

If RNC is not able to add (Event 1A) to or replace (Event 1C) an Ncell from the AS, UE sends periodic measurement reports (AdditionReportingInterval/ ReplacementReportingInterval) until;
Ncell is added/replaced in to AS Ncell leaves reporting range HO no longer required (e.g. different Ncell enters AS)
RNC may not be able to add/replace Ncell due to (a) Iur congestion or (b) inter-RNC SHO is prevented due to setting of EnableInterRNCsho (HOPS) (point1 on next slide) If CPICH EC/NO of non-active Ncell continues to increase it will cause additional interference due to a non-optimal connection (point 2) To avoid excessive uplink interference, RNC will perform an intra-frequency hard handover to the Ncell (CPICH3) if either of the following criteria are met (point 3); AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcell EcNoDownlink + HHOMarginPeakEcNo < EcNONcell Parameters : Enable Inter-RNC Soft Handover HHO margin for Peak EcNo HH Margin for Company Confidential Average EcNo
( YES/NO, default = YES ) (-66 dB, default =2 dB) (-66 dB, default=1 dB)

AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcell AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcell EcNoDownlink + HHOMarginPeakEcNo < EcNONcell EcNoDownlink + HHOMarginPeakEcNo < EcNONcell
Ec/Io
3 2 Reporting range
HHOMarginAverageEcNo HHOMarginPeakEcNo
P CPICH 1
P CPICH 2
P CPICH 3 1 1A (AdditionTime = 0)
Time
AdditionReportingInterval

Case #1:
Problem:
MGW Iur Nodal Function AAL2_ANALYSIS_TREE setting wrong. Resulting in AAL2 UP
Case #1-1 Inter-RNC, Intra-Frequency Hardhandover (HHO)

TMSI RNTI 00 01 86 55 RN26:00 57 8 (= 1400) RN27: 02 2E 6 (= 8934) 15:21:45.882 RN26 / 22952 (258) RN27 / 32242 (264)
UE RSCP UE RSCP RN26 RN26
Time_orig RNC_orig / CID (SC) RNC_End / CID (SC)
RN27 RN27 Handover Category: Category: Iur Failure - Inter-RNC SRNC Relocation Interfailure => Triggering Inter-RNC, IntraInterIntraFrequency HHO. Analysis: Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke Inter-RNC, Intra-Frequency InterIntraHHO.
UE Ec/No UE Ec/No
Iur Failure !! Iur Failure
Solution / Action proposed: proposed: Scanner Scanner

TMSI RNTI 00 01 86 55 RN26:00 57 8 (= 1400) RN27: 02 2E 6 (= 8934) 15:21:45.882 RN26 / 22952 (258) RN27 / 32242 (264)
UE RSCP UE RSCP RN26 RN26
Time_orig RNC_orig / CID (SC) RNC_End / CID (SC)
RN27 RN27 Handover Category: Category: Iur Failure - Inter-RNC SRNC Relocation Interfailure => Triggering Inter-RNC, IntraInterIntraFrequency HHO. Analysis: Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke Inter-RNC, Intra-Frequency InterIntraHHO.
UE Ec/No UE Ec/No
Problem Cause:
Error Alarm from MGW25 HST (54474) 2U4MG25 DISTUR ISU-0 ISU1205 USER PLANE CONNECTION SETUP FAILURE UCNPRB ISU-0 ISU01 02 14 49 20 63 20 6F FF FF FF FF FF FF FF FF 1A002-00-3 1A002- 00COMM 2005-03-21 11:47:02.62 2005- 03-
Cause of Problem: Check PRFile and wrong setting for AAL2 Digit Analysis Tree settings PARAMETER CLASS: 7 CALL_CONTROL VALUE 0001 YES CHANGE POSSIBILITY
IDENTIFIER NAME OF PARAMETER 00127 AAL2_ANALYSIS_TREE
After changing value= 3 then working. PARAMETER CLASS: 7 CALL_CONTROL VALUE CHANGE POSSIBILITY YES
IDENTIFIER NAME OF PARAMETER
79
Nokia 200500127
AAL2_ANALYSIS_TREE Nemo_L3_Analysis_v01.ppt/ 2005.11.050003 / rlim

Case #2:
Problem:

TMSI RNTI 00 01 86 55 RN26:00 57 8 (= 1400) RN27: 02 2E 6 (= 8934) Time_orig RNC_orig / CID (SC) RNC_End / CID (SC) 15:21:45.882 RN26 / 22952 (258) RN27 / 32242 (264)
UE RSCP UE RSCP
RN23 RN23 Handover Category: Category:
UE Ec/No UE Ec/No

RN21 RN21
Iur Failure - Inter-RNC SRNC Relocation Interfailure => Triggering Inter-RNC, IntraInterIntraFrequency HHO. Analysis: Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke Inter-RNC, Intra-Frequency InterIntraHHO.
Solution / Action proposed: proposed: Scanner Scanner MR e1a with no MR e1a with no ASU Response ASU Response due to Iur due to Iur Failure Failure

TMSI RNTI 00 01 86 55 RN26:00 57 8 (= 1400) RN27: 02 2E 6 (= 8934) Time_orig RNC_orig / CID (SC) RNC_End / CID (SC) 15:21:45.882 RN26 / 22952 (258) RN27 / 32242 (264)
UE RSCP UE RSCP
RN23 RN23 Handover Category: Category:
UE Ec/No UE Ec/No

RN21 RN21
Iur Failure - Inter-RNC SRNC Relocation Interfailure => Triggering Inter-RNC, IntraInterIntraFrequency HHO. Analysis: Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke Inter-RNC, Intra-Frequency InterIntraHHO.
Solution / Action proposed: proposed: Scanner Scanner Immediate AS SC Change from Immediate AS SC Change from RN23 12320 (301) to RN23 12320 (301) to RN21 22558 (305) RN21 22558 (305)
DL RRC Connection Release with Release Cause Unspecified

Description: DL RRC Connection Release with Release Cause Unspecified. Note: These are only some of the possible problems and does not imply same problem whenever encountering RRC Connection Release with Release Cause Unspecified. Just for information since you will not be able to view the backend logs. Need to put as to investigate further. Possible Cause: RNC internal.
CAD #1-1 DL RRC Conn Rel after RB Reconfig Complete

TMSI RNTI DD 61 E5 02 RN21:05 AA 0 (= 23200) 15:59:31.349 RN21 / 38323 (220)
UE RSCP UE RSCP
Drop Call Category: Category: Network: DL RRC Connection Release after RB Reconfig Complete. UE Ec/No UE Ec/No Analysis: Analysis: DL RRC Connection Release after RB Reconfig Complete. From ICSU log, transmissionNetwork : iu-transport-connection-failed-toiu- transport- connection- failed- toestablish.
CAD #1-1 DL RRC Conn Rel after RB Reconfig Complete

TMSI RNTI DD 61 E5 02 RN21:00 61 B (= 1563) 15:59:31.349 RN21 / 38323 (220)
UE RSCP UE RSCP
Drop Call Category: Category: Network: DL RRC Connection Release after RB Reconfig Complete. UE Ec/No UE Ec/No Analysis: Analysis: DL RRC Connection Release after RB Reconfig Complete. From ICSU log, transmissionNetwork : iu-transport-connection-failed-toiu- transport- connection- failed- toestablish.
Call Setup Failure (CAF) Case Studies

Description: Call Setup Failures. Possible Cause:

Fail Call Category: Category: Radio Related: 4 x RRC Connection Request with no response. Missing neighbour definition. Analysis: Analysis: 4 x RRC Connection Request with no response. After the last drop call (CAD #1), UE did not cell reselect to the best serving cell along that road due to missing neighbour definitions between 32897 (312) & 22835 (309). Solution proposed: proposed: Neighbour ADJS definitions: 32897 (312) 22835 (309).

Fail Call Category: Category: Radio Related: 4 x RRC Connection Request with no response. Missing neighbour definition. Analysis: Analysis: 4 x RRC Connection Request with no response. After the last drop call (CAD #1), UE did not cell reselect to the best serving cell along that road due to missing neighbour definitions between 32897 (312) & 22835 (309). Solution proposed: proposed: Neighbour ADJS definitions: 32897 (312) 22835 (309). RNC ID: 202 RNC ID: 202 Cell ID: 22835 Cell ID: 22835
CAF #1 UL CM Service Abort due to Nemo CAA=15sec Timed Out

TMSI RNTI 00 07 DB 53 RN23: 02 24 5 (= 8773) 18:59:55.248 RN23 / 12583 (157)
UE RSCP UE RSCP
Fail Call Category: Category: UE / Tool related: UL CM Service Abort due to Nemo CAA=15sec timed Abort out. Analysis: Analysis: UE / Tool related: UL CM Service Abort due to Nemo CAA=15sec timed Abort out. Call setup procedure was actually on-going. on As seen from Events window, that Nemo FMT sent CAA command but UE only sent RRC Connection Request Request almost 15secs later. Resulting in CAA timed out eventhough the call setup was on-going. Nemo FMT issued oncommand to UE to abort. Solution / Action proposed: proposed: Redrive for verification.
UE Ec/No UE Ec/No
Scanner Scanner
CAF #2 UL CM Service Abort - Nemo CAA Call Attempt=15secs Timed-out Call Setup On-going
TMSI RNTI 2A 68 3F 03 RN22: 09 80 5 (= 38917) 16:41:13.800 RN22 / 22046 (259)
UE RSCP UE RSCP
Fail Call Category: Category: Tool related: UL CM Service Abort due to Nemo CAA attempt timed out after 15secs. Analysis: Analysis: Tool related: UL CM Service Abort due to Nemo CAA attempt timed out after 15secs. Call setup was actually onongoing. After last cAF under poor coverage area, UE was receiving BCCH of 22046 (not optimal cell). Nemo sent CAA but 1st RRC Connection Request was sent only 12secs later. Thus, while call setup was on-going, Nemo tool onCAA timer=15sec expired and call was aborted. Solution / Action proposed: proposed: Redrive for verification.
UE Ec/No UE Ec/No
Scanner Scanner
CAF #3 2 x RRC Connection Request with No Response

TMSI RNTI F2 5C 08 00
UE RSCP UE RSCP
14:43:28.939 RN26 / 12044 (179)
Fail Call Category: Category: Network related: 2 x RRC Connection Request with no Response. UE Ec/No UE Ec/No Analysis: Analysis: 2 x RRC Connection Request with no Response. Not a site problem since the subsequent call setup on 12044 (179) was successful. Note: Nemo PB does not count this as a Call Setup Failure (CAF). However, since the time duration from the 1st RRC Connection Request to the 3rd RRC Conn Req was >8secs, this would be interpreted as a CAF by Actix. Actix. Solution / Action proposed: proposed: Redrive for verification.
Scanner Scanner
CAF #1-#4 Call Setup Failed after Call Proceeding DL RRC Connection Release
UE RSCP UE RSCP
TMSI RNTI Time_orig RNC_orig / CID (SC) RNC_drop / CID (SC)
DD 58 E5 02 RN24:00 BA 9 (= 2985) 10:22:18.455 RN24 / 12359 (182)
Fail Call Category: Category: Network related: Call setup failed after Call Proceeding DL RRC Connection Proceeding Release. Analysis: Analysis: Network problem between MG21 & RN24/23, which started about this timing, caused all calls setups to fail after Call Proceeding, DL RRC Proceeding Connection Release.
UE Ec/No UE Ec/No
Scanner Scanner
Solution / Action proposed: proposed: Troubleshooted realtime and resolved. Subsequent calls under RN23 & RN24 were successful.

Layer 3 Analysis

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Layer 3 Analysis

Загружено:

Авторское право:

Доступные форматы

L3 ANALYSIS / OPTIMIZATION EXAMPLES

(Using Nemo Outdoor)

Objective of Case Studies

Customized Nemo Workspace & Color Sets

CHT_Thruput_ColorSet.csf v22_rlim_default1_6630_gst_080505_rlim_Voice+PS.wor v22_rlim_default1_6650_gst_080105_rlim_Voice+PS.wor

Best practice suggestion

Information Required for L3 Analysis / Optimization

Drop Call (CAD) Case Studies

Call Setup Failure (CAF) Case Studies

UMTS Basic Call Signaling

System Information Block (SIB)

SB1 SIB1 SIB2 SIB3 SIB5 SIB7

Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

System Information Block (SIB)

Radio Bearer Setup Procedure

Call Setup Success

Disconnect and Release Procedure

Radio_Bearer_Setup Radio_Bearer_Setup_Complete Alerting Connect Connect_Acknowledge

N BAP :R A DIO LIN K SET U P R EQ U EST

N BAP:R AD IO LIN K S ET U P R ESPO N SE AAL2S IG : E R Q AA L2SIG : EC F R R C :R R C C O N N EC T IO N SET UP

R AN AP: D IRE C T T R AN SF ER R R C : D O W N LIN K DIR EC T T R AN S F ER (C M S ervice Accept) (C M S ervice Accept)

RANAP: DIRECT TRANSFER (Release)

R RC : D O W N LIN K D IR EC T T R AN SF ER (C all Proceeding)

RANAP: Iu RELEASE COMMAND

RANAP: Iu RELEASE COMPLETE

RRC:CONNECTION RELEASE RRC:CONNECTION RELEASE COMPLETE NBAP:RADIO LINK DELETION REQUEST

NBAP:RADIO LINK DELETION RESPONSE

AAL2SIG: REL AAL2SIG: RLC AAL2SIG: REL AAL2SIG: RLC

R R C : R AD IO BE AR ER SET U P R R C : R AD IO BEAR E R S ET U P C O M PLET E R AN A P:R AB ASS IG N M E N T R E SPO N SE

R AN AP: D IRE C T T R AN SF ER R R C : D O W N LIN K D IR EC T T R AN SF E R (Alerting) R R C : U P LIN K D IR E CT T R A N SF ER (C onnect) R AN A P: D IR EC T T R AN SF ER (C onnect) (A lerting)

R AN AP: D IR EC T T R A NS F ER (C onnect Acknowledge)

R R C : DO W N LIN K D IR E CT T R A N SF ER (C onnect A cknowledge)

C all established Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

RRC:PAG ING TYPE 1

RRC:RRC CO NNECTION REQ UEST NBAP:RADIO LINK SETUP REQ UEST

L1 synchronisation NBAP:SYNCHRONIZATIO N INDICATION RRC:CO NNECTION SETUP CO MPLETE

RRC:INITIAL DIRECT TRANSFER (Paging response) RANAP:INITIAL UE MESSAGE (Paging response)

NBAP:RADIO LINK RECO NFIGURATION PREPARE

NBAP:RADIO LINK RECO NFIGURATION READY

RRC: RADIO BEARER SETUP COMPLETE

RRC: UPLINK DIRECT TRANSFER (Connect Acknowledge)

RANAP: DIRECT TRANSFER (Connect Acknowledge)

Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

Attach & Authentication Procedure

MS RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP REQUEST

L1 synchronisation NBAP:SYNCHRONIZATION INDICATION

RRC:CONNECTION SETUP COM PLETE

RRC:INITIAL DIRECT TRANSFER (Attach Request) RANAP:INITIAL UE M ESSAGE (Attach Request)

RANAP: RAB ASSIG NM ENT REQ UEST (Release)

RANAP: RAB ASSIG NM ENT RESPONSE

NBAP:RL RECONFIGURATION COM M IT

RANAP:RAB ASSIGNM ENT REQUEST

RRC: RADIO BEARER SETUP

RRC: RADIO BEARER SETUP COM PLETE

RANAP:RAB ASSIGNM ENT RESPONSE

RRC: DT(Detach accept)

RRC: M EASUREM ENT REPORT

NBAP:RADIO LINK RECONFIGURATION PREPARE NBAP:RADIO LINK RECONFIGURATION READY

Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

Multi RAB (Simultaneous AMR+PS)

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

RRC: Measurement Report

NBAP: Radio Link Addition Request