Nemo L3 AMR Analysis External v04

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 Partner’s 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


© 2005 Nokia


Customized Nemo Workspace & Color Sets • Nemo Workspace for v4.15.24:

v22_rlim_default1_6630_gst_080505_rlim_Voice+PS.wor

v22_rlim_default1_6650_gst_080105_rlim_Voice+PS.wor

• (this may not work for v.25) • Nemo Color Set:

CHT_Thruput_ColorSet.csf

設定軌跡的顏色

• Best practice suggestion –

手機和Scanner的lLog一起開

• 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分析配合著看


© 2005 Nokia


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 有沒有倒台?看什資料...?


© 2005 Nokia


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” • ……….


© 2005 Nokia


Call Setup Failure (CAF) Case Studies • FMT tool related: Nemo CAA=15sec timeout or expired • Missing Neighbour related • Network related • …….


© 2005 Nokia


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


© 2005 Nokia


System Information Block (SIB) Information Block MIB

SB1 SIB1

Description PLMN types & identities Scheduling information SIB references Optional SIB scheduling information

SIB2

NAS information UE timers & counters to be used in idle and connected mode URA identity list

SIB3

Cell selection and re-selection parameters

SIB5

Parameters for common physical channel configuration

SIB7

UL interference level Dynamic persistence level (fast changing parameters) Measurement control information to be used in the cell

SIB11

Neighbour list. SIB18 Company Confidential 8

© 2005 Nokia

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


System Information Block (SIB)


© 2005 Nokia


PLMN Type

SIB Reference

Location Update(LU)

RRC Connection Stage Location Update Request Authentication Stage Location Update Accept RRC Connection Release


© 2005 Nokia


AMR MOC RRC Connection Setup

Authentication Procedure

Radio Bearer Setup Procedure

Call Setup Success

Disconnect and Release Procedure


© 2005 Nokia


AMR MOC UE

RNC

BTS

CS_CN

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

Radio_Bearer_Setup Radio_Bearer_Setup_Complete Alerting Connect Connect_Acknowledge


© 2005 Nokia


MS

BT S

RN C

C S_C N

R R C :R R C C O N NE C T IO N R EQ U E ST

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

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

AMR MOC

L1 synchronisation N BA P:SYN C H R O N IZ AT IO N IN D IC AT IO N

MS

BTS

CS_CN

RNC

RR C :C O N N E CT IO N SET U P C O M PLET E Call established

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 (C M S ervice Accept)

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

RANAP: DIRECT TRANSFER (Release) RRC: UPLINK 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: 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

RRC:CONNECTION RELEASE

N BA P:R AD IO LIN K R EC O NF IG U R AT IO N R EAD Y

RRC:CONNECTION RELEASE COMPLETE

AA L2SIG : ER Q

NBAP:RADIO LINK DELETION REQUEST AAL2S IG : E C F AAL2SIG : E RQ

NBAP:RADIO LINK DELETION RESPONSE AA L2S IG : EC F

AAL2SIG: REL

N BAP:R AD IO LIN K R E CO N F IG U R AT IO N CO M M IT

AAL2SIG: RLC AAL2SIG: REL

R R C : R AD IO BE AR ER SET U P

AAL2SIG: RLC

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)

(A lerting)

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)

Company Confidential

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

13

© 2005 Nokia

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

C all established 2005.11.05 / rlim Nemo_L3_Analysis_v01.ppt/

MTC (AMR)


© 2005 Nokia


MS

RNC

BTS

MTC

CS_CN

RANAP:PAG ING

RRC:PAG ING TYPE 1

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

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

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

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)

RANAP: DIRECT TRANSFER

Company Confidential

(Connect Acknowledge) Call established

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 Company Confidential 16

© 2005 Nokia


PS DATA CALL UE

RNC

BTS

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


© 2005 Nokia


MS

BTS

RNC

PS_CN

RRC:RRC CONNECTION REQUEST

PS DATA CALL

NBAP:RADIO LINK SETUP REQUEST

NBAP:RADIO LINK SETUP RESPONSE AAL2SIG: ERQ AAL2SIG: ECF RRC:RRC CONNECTION SETUP

L1 synchronisation MS

BTS

CS_CN

RNC

NBAP:SYNCHRONIZATION INDICATION PDP Context is active

RRC:CONNECTION SETUP COM PLETE RRC: DT (Deactivate PDP context request)

RRC:INITIAL DIRECT TRANSFER (Attach Request)

RANAP: DT (Deactivate PDP context request)

RANAP:INITIAL UE M ESSAGE

RANAP: RAB ASSIG NM ENT REQ UEST

(Attach Request) (Release)

RANAP: DIRECT TRANSFER RRC: DOW NLINK DIRECT TRANSFER (Attach Accept)

RANAP: RAB ASSIG NM ENT RESPONSE NBAP:RL RECONFIG URATIO N PREPARE

(Attach Accept)

NBAP:RL RECONFIG URATIO N READY

RRC: DOW NLINK DIRECT TRANSFER (Attach Com plete) RANAP: DT (Deactivate PDP context accept)

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

RRC: DT (Deactivate PDP context accept)

(Attach Com plete) RANAP: DIRECT TRANSFER

NBAP:RL RECONFIGURATION COM M IT

(SM : Activate PDP Context request) RRC: RADIO BEARER RELEASE

RANAP:RAB ASSIGNM ENT REQUEST

RRC:RADIO BEARER RELEASE CO M PLETE RRC: DT(Detach request)

RRC: RADIO BEARER SETUP

RANAP: DT(Detach request)

RRC: RADIO BEARER SETUP COM PLETE RANAP: DT(Detach accept) RRC: DT(Detach accept)

RANAP:RAB ASSIGNM ENT RESPONSE

NBAP:RL DELETION REQ UEST

RANAP: DIRECT TRANSFER

AAL2SIG: REL

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

NBAP:RL DELETIO N RESPONSE AAL2SIG: RLC

RRC: M EASUREM ENT REPORT

AAL2SIG : REL

NBAP:RADIO LINK RECONFIGURATION PREPARE

AAL2SIG : RLC RANAP: Iu Release Comm and

NBAP:RADIO LINK RECONFIGURATION READY RRC: RRC CO NNECTION RELEASE

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

Company Confidential Uplink and downlink data transfer

18

© 2005 Nokia


RANAP: Iu Release Com plete

Multi RAB (Simultaneous AMR+PS)

PS Disconnect

AMR AMR Disconnect


© 2005 Nokia


PS

SHO_e1a BTS

UE

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


© 2005 Nokia


SHO_e1b BTS

UE

RNC

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

RRC Measurement Report



NBAP: Radio Link Deletion Request

NBAP: Radio Link Deletion Response


© 2005 Nokia


SHO_e1c BTS

UE

RNC

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

RRC: Measurement Report

NBAP: Radio Link Addition Request

NBAP:Radio Link Addition Response



NBAP: Radio Link Deletion Request

NBAP: Radio Link Deletion Response


© 2005 Nokia


• Do not always assume that


© 2005 Nokia


Missing Neighbours Description: Missing neighbours. Possible Cause: Human negligence . Poor NB planning. Street canyon effect that requires more than 2 tier NB planning etc.


© 2005 Nokia


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


© 2005 Nokia


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.


© 2005 Nokia


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

D5 C2 82 02

RNTI Time_orig RNC_orig / CID (SC)

RN22 / 32897 (312)

RNC_drop / CID (SC)

• 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).


© 2005 Nokia



D5 C2 82 02


RN22 / 32897 (312)

RNC_drop / CID (SC)

• 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 RNC ID: ID: 202 202 Cell Cell ID: ID: 22835 22835


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 06 B3 E3

RNTI

RN22: 12 D7 9 (= 77177)

Time_orig

17:12:20.679

RNC_orig / CID (SC)

RN22 / 22552 (136)

RNC_drop / CID (SC)

RN22 / 22552 (136)

• Drop Call Category: Category: • RF Related: MR e1a with No ASU response. Missing Neighbour definitions UE UE Ec/No 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.


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 06 B3 E3

RNTI

RN22: 12 D7 9 (= 77177)

Time_orig

17:12:20.679

RNC_orig / CID (SC)

RN22 / 22552 (136)

RNC_drop / CID (SC)

RN22 / 22552 (136)






© 2005 Nokia


CAD #4-1 – MR e1a with No ASU Response TMSI

CD A7 D3 02

RNTI

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

Time_orig

15:46:55.393

RNC_orig / CID (SC)

RN23 / 32536 (340)

RNC_drop / CID (SC)

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) 22395 (151) • 22545 (311) 12350 (273)


© 2005 Nokia



CD A7 D3 02

RNTI

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

Time_orig

15:46:55.393

RNC_orig / CID (SC)

RN23 / 32536 (340)

RNC_drop / CID (SC)

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) 22395 (151) • 22545 (311) 12350 (273)


© 2005 Nokia


CAD #3-1 – MR e1a with No ASU Response UE UE RSCP RSCP Problem Problem seemed seemed to to start start here. here. SC318 SC318 was was not not in in UE’s UE’s NB NB List. List. MC MC did did not not include SC318 although include SC318 although defined defined in in 26009 26009 (325) (325) ADJS. ADJS. This This caused caused unnecessary unnecessary AS AS 325 325 having having bad bad Ec/No Ec/No since since SC318 SC318 was was an an interferer. interferer.

TMSI

CD A7 D3 02

RNTI

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

Time_orig

12:08:42.226

RNC_orig / CID (SC)

RN23 / 12705 (158)

RNC_drop / CID (SC)

RN21 / 26009 (333)

• Drop Call Category: Category: • UE related: MR e1a with No ASU response. UE UE Ec/No 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 Ec/No SC in Monitored set instead of Best Ec/No Ec/No SC. • Subsequently, call was dropped due to UE bad AS SC Ec/No Ec/No => high BLER. • Solution / Action proposed: proposed:

Scanner Scanner

• Redrive for verification.

05Feb23 120829-v vip-2.zip


© 2005 Nokia


RNTI_00003071.zip

CAD #3-2 – MR e1a with No ASU Response UE UE RSCP RSCP

TMSI

CD A7 D3 02

RNTI

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

Time_orig

12:08:42.226

RNC_orig / CID (SC)

RN23 / 12705 (158)

RNC_drop / CID (SC)

RN21 / 26009 (333)

• Drop Call Category: Category: • UE related: MR e1a with No ASU response. UE UE Ec/No 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 Ec/No SC in Monitored set instead of Best Ec/No Ec/No SC. • Subsequently, call was dropped due to UE bad AS SC Ec/No Ec/No => high BLER. • Solution / Action proposed: proposed:

Scanner Scanner


© 2005 Nokia



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.


© 2005 Nokia


CAD #3-1 – No MR After last MC TMSI

DD 05 E4 02

RNTI

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

UE UE RSCP RSCP

RN24:0D3F7 (=54263) Time_orig

9:58:25.348

RNC_orig / CID (SC)

RN23 / 12501 (176)

RNC_drop / CID (SC)

RN24 / 32167 (360)

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

• Analysis: Analysis: • No MR after last MC. • After last successful MR e1b with ASUC to remove intraintra-sector SC352 from AS, the 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. behaviour. Redrive for verification.


© 2005 Nokia


CAD #3-2 – No MR After last MC TMSI

DD 05 E4 02

RNTI

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

UE UE RSCP RSCP

RN24:0D3F7 (=54263) Time_orig

9:58:25.348

RNC_orig / CID (SC)

RN23 / 12501 (176)

RNC_drop / CID (SC)

RN24 / 32167 (360)

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

• Analysis: Analysis: • No MR after last MC. • After last successful MR e1b with ASUC to remove intraintra-sector SC352 from AS, the 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. behaviour. Redrive for verification.


© 2005 Nokia


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

00 01 6F 94

RNTI

RN21:12 36 E (= 74606) RN24:

RSCP RSCP

Time_orig

13:00:51.674

RNC_orig / CID (SC)

RN21 / 12745 (297)

RNC_drop / CID (SC)

RN24 / 32335 (169)

• 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. neighbour. Suggest to 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


© 2005 Nokia


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)


© 2005 Nokia


CAD #2-1 – No MR after last MC

UE UE RSCP RSCP

TMSI

00 08 D6 E3

RNTI

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

Time_orig

13:54:26.467

RNC_orig / CID (SC)

RN23 / 12707 (159)

RNC_drop / CID (SC)

RN24 / 22183 (164)

• Drop Call Category: Category: • UE Related: No MR after last MC. • Analysis: Analysis: UE UE Ec/No 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..


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 08 D6 E3

RNTI

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

Time_orig

13:54:26.467

RNC_orig / CID (SC)

RN23 / 12707 (159)

RNC_drop / CID (SC)

RN24 / 22183 (164)


• 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 FTP Thruput Thruput



© 2005 Nokia



UE UE RSCP RSCP

TMSI

00 08 E2 13

RNTI

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

Time_orig

15:19:37.394

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN23 / 12518 (205)


• UE Related: No MR after last MC. Subsequently, after approx 3 minutes of driving, UE AS (SC205) 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..


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 08 E2 13

RNTI

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

Time_orig

15:19:37.394

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN23 / 12518 (205)


• UE Related: No MR after last MC. Subsequently, after approx 3 minutes of driving, UE AS (SC205) 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 FTP Thruput Thruput



© 2005 Nokia


CAD – UE Related – No MR after Last MC

UE UE RSCP RSCP

TMSI

00 3F E7 C6 (4188102)

RNTI

06 19 2 (24978)

Time_orig

18:29:13.959

RNC_orig / CID (SC)

RN23 / 12700 (133)

RNC_drop / CID (SC)

RN21 / 22716 (306)

Drop call category: • UE related

UE UE Ec/No Ec/No

Scanner Scanner


© 2005 Nokia


Analysis: • UE was not sending any MR which caused the failure in the softer HO. • As Ec/No Ec/No of SC306 in the AS degraded, and Ec/No Ec/No of SC298 gets stronger in the 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.

Proposed solution


UE UE RSCP RSCP

TMSI

00 08 83 DB

RNTI

RN23: 06 FA 8 (= 28584)

Time_orig

14:26:39.499

RNC_orig / CID (SC)

RN23 / 12508 (201)

RNC_drop / CID (SC)

RN23 / 2508


• UE Related: No MR after last MC. Subsequently, AS (SC209,217,201) Ec/No Ec/No quality degraded, resulting in 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.

Scanner Scanner

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



© 2005 Nokia


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 UE’s traces to confirm), should use AdjsEcNoOffset to advance SHO or mutually make more favorable for SHO. Company Confidential 46

© 2005 Nokia



UE UE RSCP RSCP

00 07 DA BB

This case of MR e1a with No This is is aa classic classic with RNTIcase of MR e1a RN24: 01 33No 3 (= 4915) ASU Response that is NOT due to Network ASU ResponseTime_orig that is NOT due to Network 18:51:48.476 Problem Problem but but due due to to rapid rapid changing changing RF RF RNC_orig / CID (SC) RN24 / 32324 (147) environment Ec/No /No quality). ((Ec/No environment (Ec quality). This This can can be be RNC_drop / CID (SC) RN23 / 22712 (215) can be confirmed by observing if the same can be confirmed by observing if the same nd deep deep fade fade is is experienced experienced by by the the 22nd UE. UE. Which in this case it was. Which in this case it was. This via CPICH • optimized Drop Call Category: : Category This can can be be optimized via Individual Individual CPICH Ec/No /No Offset advance Ec • to RF MRthe e1aSHO. with No ASU Ec/No Offset to Related: advance the SHO. response.

UE UE Ec/No Ec/No

• Analysis: Analysis: • MR e1a with No ASU response. Observed the handover region between SC215 & 133 with rapid degradation of Ec/No Ec/No quality of SC215, 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.


© 2005 Nokia



TMSI

00 07 DA BB

RNTI

RN24: 01 33 3 (= 4915)

Time_orig

18:51:48.476

RNC_orig / CID (SC)

RN24 / 32324 (147)

RNC_drop / CID (SC)

RN23 / 22712 (215)

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

UE UE Ec/No Ec/No

• Analysis: Analysis: • MR e1a with No ASU response. Observed the handover region between SC215 & 133 with rapid degradation of Ec/No Ec/No quality of SC215, 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.


© 2005 Nokia


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

TMSI

00 07 F0 93

RNTI

RN23: 02 AA 4 (= 10916)

Time_orig

10:24:46.945

RNC_orig / CID (SC)

RN23 / 26012 (335)

RNC_drop / CID (SC)

RN23 / 32187 (245)

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

UE UE Ec/No Ec/No

• Analysis: Analysis: • Radio Related: MR e1a with No ASU response, possible due to AS (SC245) Ec/No Ec/No quality degraded rapidly. 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

• Redrive on 3 June for verification..


© 2005 Nokia



TMSI

DD 58 E5 02

RNTI

RN21:05 A8 E (= 23182)

Time_orig

15:52:26.428

RNC_orig / CID (SC)

RN21 / 32779 (150)

RNC_drop / CID (SC)

RN21 / 326025 (340)

• Drop Call Category: Category: • Site Related: MR e1a with no ASU. • Analysis: Analysis: UE UE Ec/No 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 nonnon-optimum, resulting in MR e1a to other nonnon-optimum MS cells.

Scanner 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.


© 2005 Nokia



TMSI

DD ED E4 02

RNTI

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

Time_orig

11:32:47.821

RNC_orig / CID (SC)

RN23 / 32530 (222)

RNC_drop / CID (SC)

RN24 / 32700 (149)

• Drop Call Category: Category: • Network related: MR e1a with No ASU response. UE UE Ec/No 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)

Scanner Scanner

• 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


© 2005 Nokia


RNTI_0000D47C_0175.zip


TMSI

DD ED E4 02

RNTI

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

Time_orig

11:32:47.821

RNC_orig / CID (SC)

RN23 / 32530 (222)

RNC_drop / CID (SC)

RN24 / 32700 (149)

• Drop Call Category: Category: • Network related: MR e1a with No ASU response. UE UE Ec/No 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)

Scanner Scanner

• 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.


© 2005 Nokia


CAD #5-1 – MR e1a with No ASU Response 13 Jan 2005

TMSI

DD 4E A5 02

RNTI

01 E5 0 (= 7760)

Time_orig RNC_orig / CID (SC)

RN21 / 38323 (202)

RNC_drop / CID (SC)

• 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.


© 2005 Nokia


CAD #5-2 – MR e1a with No ASU Response 14 Jan 2005 – Drive #1 – no drop call

TMSI

DD 4E A5 02

RNTI

01 E5 0 (= 7760)


RN21 / 38323 (202)

RNC_drop / CID (SC)



© 2005 Nokia


CAD #5-3 – MR e1a with No ASU Response 14 Jan 2005 – Drive #2 – no drop call

TMSI

DD 4E A5 02

RNTI

01 E5 0 (= 7760)


RN21 / 38323 (202)

RNC_drop / CID (SC)



© 2005 Nokia



TMSI

00 06 B3 E3

RNTI

RN22: 12 D7 9 (= 77177)

Time_orig

17:12:20.679

RNC_orig / CID (SC)

RN22 / 22552 (136)

RNC_drop / CID (SC)

RN22 / 22552 (136)






© 2005 Nokia



TMSI

00 06 B3 E3

RNTI

RN22: 12 D7 9 (= 77177)

Time_orig

17:12:20.679

RNC_orig / CID (SC)

RN22 / 22552 (136)

RNC_drop / CID (SC)

RN22 / 22552 (136)






© 2005 Nokia


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

TMSI

F2 41 08 00

RNTI

RN26: 01 73 1 (= 5937)

Time_orig

11:42:04.278

RNC_orig / CID (SC)

RN26 / 28132 (280)

RNC_drop / CID (SC)

RN26 / 12256 (159)

• Drop Call Category: Category: • RF Related: MR e1c with No ASU response. UE UE Ec/No 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) EE-ADT uptilt of 2 degs to improve dominance along highway. • Redrive for verification.


© 2005 Nokia



TMSI

DD 2A F1 02

RNTI

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

Time_orig

10:03:26.227

RNC_orig / CID (SC)

RN23 / 12500 (302)

RNC_drop / CID (SC)

RN24 / 12357 (300)

• Drop Call Category: Category: • Network Related: MR e1a with no ASU response. UE UE Ec/No 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” Proceeding”, DL RRC Connection Release.

Scanner Scanner

• Solution / Action proposed: proposed: • Troubleshooted realtime and resolved. Subsequent calls under RN23 & RN24 were successful.


© 2005 Nokia


CAD #3-1 – MR e1a with No ASU Response – FMT Tool Problem Flatliner Flatliner –– Tool Tool Malfunctioned. Malfunctioned. Both Both UE UE traces traces same. same.

UE UE RSCP RSCP

TMSI

00 09 ED 72

RNTI

RN23: 11 49 D (= 70813)

Time_orig

11:11:19.305

RNC_orig / CID (SC)

RN23 / 12501 (176)

RNC_drop / CID (SC)

RN23 / 12160 (203)

• Drop Call Category: Category:

UE UE Ec/No Ec/No

• 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.


© 2005 Nokia


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

UE UE RSCP RSCP

UE UE Ec/No Ec/No

Scanner Scanner


© 2005 Nokia


TMSI

00 08 89 E3

RNTI

RN24: 04 1E 2

Time_orig

15:21:53.990

RNC_orig / CID (SC)

RN24 / 32132 (217)

RNC_drop / CID (SC)

RN24 / 22573 (311)

• 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 Ec/No quality already bad. • • Solution / Action proposed: proposed: • Redrive for verification.

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

UE UE RSCP RSCP

TMSI

00 08 89 E3

RNTI

RN24: 04 1E 2

Time_orig

15:21:53.990

RNC_orig / CID (SC)

RN24 / 32132 (217)

RNC_drop / CID (SC)

RN24 / 22573 (311)

• Drop Call Category: Category:

UE UE Ec/No Ec/No

• 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.

Scanner Scanner

• 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 Ec/No quality already bad. • • Solution / Action proposed: proposed:


© 2005 Nokia



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

00 07 F0 93

RNTI

RN21: 03 79 A (= 14234) RN24: 03 27 9 (= 12921)

UE UE RSCP RSCP

UE UE Ec/No Ec/No

Scanner Scanner

RN24: 03 28 7 (= 12935) Time_orig

14:47:39.503

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN24 / 32324 (147)

•

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 Ec/No quality from 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. WCDMA Cell Out of Use during the above aforesaid period.

•

Redrive for verification.


© 2005 Nokia


2324U_0602.log

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

00 07 F0 93

RNTI

RN21: 03 79 A (= 14234) RN24: 03 27 9 (= 12921)

UE UE RSCP RSCP

RN24: 03 28 7 (= 12935) Time_orig

14:47:39.503

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN24 / 32324 (147)

• Drop Call Category: Category: • BTS / Radio Related: MR e1a with No ASU response. UE UE Ec/No Ec/No

Scanner Scanner


© 2005 Nokia


• Analysis: Analysis: • BTS / Radio Related: MR e1a with No ASU response, due to AS SC147 bad or rapid fading of Ec/No Ec/No quality from 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.

CAD #3-1 – MR e1a with No ASU Response – Radio related Observed Observed from from UE UE that that RSCP RSCP && Ec/No Ec/No of of ALL ALL AS AS && Monitored Monitored Set Set degraded degraded all all at at same same time. time. Suggesting Suggesting that that possible possible BTS BTS or or RNC RNC problem. problem. Also, Also, no no meas meas data data on on Scanner. Scanner.

UE UE RSCP RSCP

TMSI

00 08 83 DB

RNTI

RN23: 06 FB 8 (= 28600)

Time_orig

14:29:23.733

RNC_orig / CID (SC)

RN23 / 22510 (208)

RNC_drop / CID (SC)

RN23 / 16012 (327)

• Drop Call Category: Category: • Radio Related: MR e1a with No ASU response. BTS

UE UE Ec/No Ec/No

• Analysis: Analysis: • Radio Related: MR e1a with No ASU response, possible due to AS (SC327) Ec/No Ec/No quality degraded rapidly. Possibly DL broken. • Check BTS alarm history for 6012U on 3 June. • Need to check RF coverage between 16012 & 26012.

Scanner Scanner

• Solution / Action proposed: proposed: • Check BTS alarm history for 6012U on 3 June. • Redrive on 6 June for verification..


© 2005 Nokia


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

00 08 83 DB

RNTI

RN23: 06 FB 8 (= 28600)

Time_orig

14:29:23.733

RNC_orig / CID (SC)

RN23 / 22510 (208)

RNC_drop / CID (SC)

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 Ec/No quality degraded rapidly. 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..


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 09 7B 32

RNTI

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

Time_orig

12:05:12.811

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN23 / 12518 (205)

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

UE UE Ec/No Ec/No

• 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.

Scanner Scanner • Solution / Action proposed: proposed: • Redrive for verification..

RRC_Mon_00008057_0CF0.zip


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 09 7B 32

RNTI

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

Time_orig

12:05:12.811

RNC_orig / CID (SC)

RN21 / 12188 (327)

RNC_drop / CID (SC)

RN23 / 12518 (205)

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

UE UE Ec/No Ec/No

• 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.

FTP FTP Thruput Thruput • Solution / Action proposed: proposed: • Redrive for verification..


© 2005 Nokia



TMSI

F2 5C 08 00

RNTI

RN26: 01 8B A (= 6330)

Time_orig

14:52:26.242

RNC_orig / CID (SC)

RN26 / 38041 (268)

RNC_drop / CID (SC)

RN23 / 22500 (310)

• Drop Call Category: Category: • Site Related: MR e1a with No ASU response. Site 8002U related. UE UE Ec/No Ec/No

• Analysis: Analysis: • MR e1a with No ASU response. • This whole stretch of WenHwa Road is served by 28002 (259).

Scanner Scanner

• However, on the day & period of drive, Site 8002U BTS alarm history indicated “NBAP link failure” failure” and site was blocked due to “LI” LI” (RNC time: 2.42pm~2.52pm). Call was dropped due to poor Ec/No. Ec/No.

• Solution / Action proposed: proposed: • Investigate site bts alarm history. • Redrive for verification.


© 2005 Nokia


CAF #4 –RRC Connection Reject with cause ‘Unspecified’ TMSI

F2 5C 08 00

RNTI

UE UE RSCP RSCP

Time_orig

14:54:17.291

RNC_orig / CID (SC)

RN26 / 28002 (259)

RNC_drop / CID (SC)

• Fail Call Category: Category: • Site Related related: related: RRC Connection Reject with cause ‘unspecified’ unspecified’. UE UE Ec/No Ec/No

• Analysis: Analysis: • Site Related related: related: RRC Connection Reject with cause ‘unspecified’ unspecified’. • However, on the day & period of drive, Site 8002U BTS alarm history indicated “NBAP link failure” failure” and site was blocked due to “LI” LI” (RNC time: 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.


© 2005 Nokia


Intra-Frequency HardHandover (HHO) Case Description: Intra-Frequency HardHandover (HHO) Case. Possible Cause:


© 2005 Nokia


HardHandover (HHO) – Iur Congestion Case


© 2005 Nokia


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

• 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 73

© 2005 Nokia


CN

CN

• No Iur between RNCs • Iur congestion or failure

Iu

Iu

Iu

RNC

RNC

Iur

Iu

RNC

RNC

Iur

Inter-RNC intra-frequency Hard Handover (HHO) • 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

( YES/NO, default = YES )

• HHO margin for Peak EcNo

(-6…6 dB, default =2 dB)

• HH Margin for Average EcNo Company Confidential

(-6…6 dB, default=1 dB)

74

© 2005 Nokia


Inter-RNC intra-frequency Hard Handover (HHO) AveEcNoDownlink AveEcNoDownlink ++ HHOMarginAveEcNo HHOMarginAveEcNo << AveEcNoNcell AveEcNoNcell EcNoDownlink EcNoDownlink ++ HHOMarginPeakEcNo HHOMarginPeakEcNo << EcNONcell EcNONcell Ec/Io

3

HHOMarginAverageEcNo HHOMarginPeakEcNo P CPICH 1

2 Reporting range

P CPICH 2

P CPICH 3

Time 1

1A (AdditionTime = 0) Company Confidential 75

© 2005 Nokia


AdditionReportingInterval

HardHandover (HHO) – Iur Congestion Case • Case #1: • Problem: • MGW Iur Nodal Function AAL2_ANALYSIS_TREE setting wrong. Resulting in AAL2 UP


© 2005 Nokia


Case #1-1 – Inter-RNC, Intra-Frequency Hardhandover (HHO) TMSI

00 01 86 55

RNTI

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

UE UE RSCP RSCP RN26 RN26

Time_orig

15:21:45.882

RNC_orig / CID (SC)

RN26 / 22952 (258)

RNC_End / CID (SC)

RN27 / 32242 (264)

RN27 RN27 • Handover Category: Category:

UE UE Ec/No Ec/No

Iur Iur Failure Failure !!

• Iur Failure - InterInter-RNC SRNC Relocation failure => Triggering InterInter-RNC, IntraIntraFrequency HHO. • Analysis: Analysis: • Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke InterInter-RNC, IntraIntra-Frequency HHO.



© 2005 Nokia



00 01 86 55

RNTI

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

UE UE RSCP RSCP RN26 RN26

Time_orig

15:21:45.882

RNC_orig / CID (SC)

RN26 / 22952 (258)

RNC_End / CID (SC)

RN27 / 32242 (264)


UE UE Ec/No Ec/No




© 2005 Nokia


Problem Cause: • Error Alarm from MGW25 • HST (54474) 2U4MG25

1A0021A002-0000-3

20052005-0303-21 11:47:02.62

COMM

•

DISTUR ISUISU-0

•

1205 USER PLANE CONNECTION SETUP FAILURE

•

UCNPRB ISUISU-0

•

01 02 14 49 20 63 20 6F FF FF FF FF FF FF FF FF

• Cause of Problem: Check PRFile and wrong setting for AAL2 Digit Analysis Tree settings • PARAMETER CLASS: 7

CALL_CONTROL

• IDENTIFIER NAME OF PARAMETER • 00127

AAL2_ANALYSIS_TREE

VALUE

CHANGE POSSIBILITY

0001

YES

VALUE

CHANGE POSSIBILITY

• After changing value= 3 then working. • PARAMETER CLASS: 7

CALL_CONTROL

• IDENTIFIER NAME OF PARAMETER


• 00127 © 2005 Nokia

AAL2_ANALYSIS_TREE 2005.11.050003 Nemo_L3_Analysis_v01.ppt/ / rlim

YES

HardHandover (HHO) – Iur Congestion Case • Case #2: • Problem:


© 2005 Nokia



00 01 86 55

RNTI

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

UE UE RSCP RSCP

Time_orig

15:21:45.882

RNC_orig / CID (SC)

RN26 / 22952 (258)

RNC_End / CID (SC)

RN27 / 32242 (264)


UE UE Ec/No Ec/No

Iur Iur Failure Failure !! RN21 RN21




© 2005 Nokia


MR MR e1a e1a with with no no ASU ASU Response Response due due to to Iur Iur Failure Failure


00 01 86 55

RNTI

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

UE UE RSCP RSCP

Time_orig

15:21:45.882

RNC_orig / CID (SC)

RN26 / 22952 (258)

RNC_End / CID (SC)

RN27 / 32242 (264)


UE UE Ec/No Ec/No

Iur Iur Failure Failure !! RN21 RN21


• Solution / Action proposed: proposed: Scanner Scanner Immediate Immediate AS AS SC SC Change Change from from RN23 RN23 12320 12320 (301) (301) to to RN21 RN21 22558 22558 (305) (305)


© 2005 Nokia


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.


© 2005 Nokia


CAD #1-1 – DL RRC Conn Rel after RB Reconfig Complete UE UE RSCP RSCP

TMSI

DD 61 E5 02

RNTI

RN21:05 AA 0 (= 23200)

Time_orig

15:59:31.349

RNC_orig / CID (SC)

RN21 / 38323 (220)

RNC_drop / CID (SC)

• Drop Call Category: Category: • Network: DL RRC Connection Release after RB Reconfig Complete. UE UE Ec/No Ec/No

• Analysis: Analysis: • DL RRC Connection Release after RB Reconfig Complete. • From ICSU log, transmissionNetwork : iuiu-transporttransport-connectionconnection-failedfailed-totoestablish.



© 2005 Nokia


CAD #1-1 – DL RRC Conn Rel after RB Reconfig Complete UE UE RSCP RSCP

TMSI

DD 61 E5 02

RNTI

RN21:00 61 B (= 1563)

Time_orig

15:59:31.349

RNC_orig / CID (SC)

RN21 / 38323 (220)

RNC_drop / CID (SC)

• Drop Call Category: Category: • Network: DL RRC Connection Release after RB Reconfig Complete. UE UE Ec/No Ec/No

• Analysis: Analysis: • DL RRC Connection Release after RB Reconfig Complete. • From ICSU log, transmissionNetwork : iuiu-transporttransport-connectionconnection-failedfailed-totoestablish.



© 2005 Nokia


Call Setup Failure (CAF) Case Studies Description: Call Setup Failures. Possible Cause:


© 2005 Nokia



D5 C2 82 02


RN22 / 32897 (312)

RNC_drop / CID (SC)

• 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).


© 2005 Nokia



D5 C2 82 02


RN22 / 32897 (312)

RNC_drop / CID (SC)

• 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 RNC ID: ID: 202 202 Cell Cell ID: ID: 22835 22835


© 2005 Nokia


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

UE UE RSCP RSCP

TMSI

00 07 DB 53

RNTI

RN23: 02 24 5 (= 8773)

Time_orig

18:59:55.248

RNC_orig / CID (SC)

RN23 / 12583 (157)

RNC_drop / CID (SC)

• Fail Call Category: Category:

UE UE Ec/No Ec/No

• UE / Tool related: UL “CM Service Abort” Abort” due to Nemo CAA=15sec timed out. • Analysis: Analysis: • UE / Tool related: UL “CM Service Abort” Abort” due to Nemo CAA=15sec timed out. Call setup procedure was actually onon-going.

Scanner Scanner

• 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 onon-going. Nemo FMT issued command to UE to abort. • Solution / Action proposed: proposed: • Redrive for verification.


© 2005 Nokia


CAF #2 – UL CM Service Abort - Nemo CAA Call Attempt=15secs Timed-out – Call Setup On-going UE UE RSCP RSCP

TMSI

2A 68 3F 03

RNTI

RN22: 09 80 5 (= 38917)

Time_orig

16:41:13.800

RNC_orig / CID (SC)

RN22 / 22046 (259)

RNC_drop / CID (SC)


UE UE Ec/No Ec/No

• Tool related: UL CM Service Abort due to Nemo CAA attempt timed out after 15secs. • Analysis: Analysis:

Scanner Scanner

• 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 onon-going, Nemo tool CAA timer=15sec expired and call was aborted. • Solution / Action proposed: proposed: • Redrive for verification.


© 2005 Nokia


CAF #3 – 2 x RRC Connection Request with No Response TMSI

F2 5C 08 00

RNTI

UE UE RSCP RSCP

Time_orig

14:43:28.939

RNC_orig / CID (SC)

RN26 / 12044 (179)

RNC_drop / CID (SC)

• Fail Call Category: Category: • Network related: 2 x RRC Connection Request with no Response. UE UE Ec/No 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.

Scanner Scanner

• 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.


© 2005 Nokia


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

TMSI

DD 58 E5 02

RNTI

RN24:00 BA 9 (= 2985)

Time_orig

10:22:18.455

RNC_orig / CID (SC)

RN24 / 12359 (182)

RNC_drop / CID (SC)


UE UE Ec/No Ec/No

• Network related: Call setup failed after “Call Proceeding” Proceeding” – DL RRC Connection Release. • Analysis: Analysis: • Network problem between MG21 & RN24/23, which started about this timing, caused all calls setups to fail after “Call Proceeding” Proceeding”, DL RRC Connection Release.

Scanner Scanner

• Solution / Action proposed: proposed: • Troubleshooted realtime and resolved. Subsequent calls under RN23 & RN24 were successful.


© 2005 Nokia


Nemo L3 AMR Analysis External v04

Recommend Documents