Nemo L3 AMR Analysis External 2G 3G PDF

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
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分析配合著看
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
Information Block Description
MIB PLMN types & identities

Scheduling information
SIB references
SB1 Optional SIB scheduling information
SIB1 NAS information

UE timers & counters to be used in idle and connected mode
SIB2 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)
SIB11 Measurement control information to be used in the cell
Neighbour list.
SIB18 PLMN identities of neighboring cells to be considered in idle mode as well as in
Company Confidential connected mode.
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 BTS RNC 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
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
N BAP :R A DIO LIN K SET U P R EQ U EST

Note: Authentication &
N BAP:R AD IO LIN K S ET U P R ESPO N SE
AAL2S IG : E R Q Security Mode Procedures AMR MOC

AA L2SIG : EC F
Are switched off in this
Reference signalling flow
R R C :R R C C O N N EC T IO N SET UP
L1 synchronisation
N BA P:SYN C H R O N IZ AT IO N IN D IC AT IO N
MS BTS RNC CS_CN
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

RRC: DOW NLINK DIRECT TRANSFER (Disconnect)
(CM Service Request)
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)
(Release)
RR C : U PLIN K D IR EC T T R AN SF ER (Setup) RRC: UPLINK DIRECT TRANSFER (Release)
R AN AP: D IR EC T T R A NS F ER
(Setup)
RRC: DOW NLINK DIRECT TRANSFER (Release complete)

(Release complete)
(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
R R C : R AD IO BEAR E R S ET U P C O M PLET E AAL2SIG: RLC
R AN A P:R AB ASS IG N M E N T R E SPO N SE
Call released
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)
R AN AP: D IR EC T T R A NS F ER
R R C : DO W N LIN K D IR E CT T R A N SF ER (C onnect A cknowledge) (C onnect Acknowledge)
13 © 2005 Nokia Nemo_L3_Analysis_v01.ppt/

C all established 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

Note: Authentication &
Security Mode Procedures
AAL2SIG: ERQ
AAL2SIG: ECF
RRC:RRC CO NNECTION SETUP

Are switched off in this
L1 synchronisation
NBAP:SYNCHRONIZATIO N INDICATION
Reference signalling flow
RRC:CO NNECTION SETUP CO MPLETE
RRC:INITIAL DIRECT TRANSFER (Paging response)
RANAP:INITIAL UE MESSAGE
(Paging response)
(Setup)
RRC: DOW NLINK DIRECT TRANSFER (Setup)
RRC: UPLINK DIRECT TRANSFER (Call confirmed)
(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)
(Alerting)

RRC: DOW NLINK DIRECT TRANSFER (Connect)
(Connect)
RRC: UPLINK DIRECT TRANSFER (Connect Acknowledge)
Company Confidential (Connect Acknowledge)
Call established

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 BTS RNC PS_CN
RRC_Connection_Request
RRC_Connection_Setup
RRC_Connection_Setup_Complete
Attach_Request
Authentication_n_Ciphering Request
Authentication_n_Ciphering Response
Security_Mode_Command
Security_Mode_Complete
Attach_Accept
Attach_Complete
Activate_PDP_Context_Request
Radio_Bearer_Setup
Radio_Bearer_Setup_Complete
Activate_PDP_Context_Accept
Radio_Bearer_Reconfiguration
Radio_Bearer_Reconfiguration_Complete
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 RNC CS_CN
NBAP:SYNCHRONIZATION INDICATION
PDP Context is active

RRC:CONNECTION SETUP COM PLETE
RRC:INITIAL DIRECT TRANSFER (Attach Request) RRC: DT (Deactivate PDP context 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 RANAP: RAB ASSIG NM ENT RESPONSE
RRC: DOW NLINK DIRECT TRANSFER (Attach Accept) 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)
RRC: UPLINK DIRECT TRANSFER (SM :Activate PDP Context request) (Attach Com plete) RRC: DT (Deactivate PDP context accept)

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: RADIO BEARER SETUP RRC: DT(Detach request)
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

(SM : Activate PDP Context accept) AAL2SIG: REL
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 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
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

- Event 1B is triggered
RRC Measurement Report
NBAP: Radio Link Deletion Request
NBAP: Radio Link Deletion Response
SHO_e1c
UE BTS RNC

- 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
• 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
Cell Reselection to
Question:
13184878 dec = C92F6E hex
How do we know it is a
(RNC ID = C9 = 201, Cell ID =
case of missing neighbour?
2F6E = 12142 (SC302)
Ans:
Just take a look at the
Ec/No of the Reselected Cell
(12142 SC302) and you can
observe that the Ec/No
jumped from bad to very
good.
CAF #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).
TMSI D5 C2 82 02
RNTI
Time_orig
RNC_orig / CID (SC) RN22 / 32897 (312)
RNC_drop / CID (SC)

Category:
• Analysis:
Analysis:
response.
(312) & 22835 (309).
proposed:
• 32897 (312) ⇔ 22835 (309).
RNC
RNC ID:ID: 202
202
Cell
Cell ID:
ID: 22835
22835
CAD #1-1 – MR e1a with No ASU Response
TMSI 00 06 B3 E3
RNTI RN22: 12 D7 9 (= 77177)
UE Time_orig 17:12:20.679
UE RSCP
RSCP
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:
• ADJS definition:
Scanner
Scanner • 22552 (136) ' 32873 (173)
• Redrive for verification.
TMSI 00 06 B3 E3
RNTI RN22: 12 D7 9 (= 77177)
UE RSCP
RSCP
RNC_orig / CID (SC) RN22 / 22552 (136)
RNC_drop / CID (SC) RN22 / 22552 (136)

Category:
definitions
UE
UE Ec/No
Ec/No • Analysis:
Analysis:
(136) and 32873 (173).

proposed:
Scanner
Scanner • 22552 (136) ' 32873 (173)
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)

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.

proposed:
• NB Definitions:
• 12183 (156) 22395 (151)
• 22545 (311) 12350 (273)
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)

Category:
• Site related: MR e1a with No ASU
response.
• Analysis:
Analysis:
• Site 2335U was down on 23 Feb. See
WBTS Cell Status report.
• Neighbour definition to provide as
backup incase of site outage.

proposed:
• NB Definitions:
• 12183 (156) 22395 (151)
• 22545 (311) 12350 (273)
TMSI CD A7 D3 02
RNTI RN23:0C318 (= 49944)
RN21:03071 (=12401)
UE
UE RSCP
RSCP
Time_orig 12:08:42.226
RNC_orig / CID (SC) RN23 / 12705 (158)
Problem
Problem seemed
seemed to to start
start here.
here. RNC_drop / CID (SC) RN21 / 26009 (333)
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. • Drop Call Category:
Category:
This
This caused
caused unnecessary
unnecessary • UE related: MR e1a with No ASU
AS
AS 325
325 having
having bad
bad Ec/No
Ec/No response.
since
since SC318
SC318 was
was anan
interferer.
interferer.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No
• 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.

proposed:
Scanner
Scanner • Redrive for verification.
05Feb23 120829-v vip-2.zip
RNTI_00003071.zip
TMSI CD A7 D3 02
RNTI RN23:0C318 (= 49944)
RN21:03071 (=12401)
UE
UE RSCP
RSCP
Time_orig 12:08:42.226
RNC_orig / CID (SC) RN23 / 12705 (158)
RNC_drop / CID (SC) RN21 / 26009 (333)

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

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

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

Category:
UE
UE Ec/No
Ec/No Analysis:
• Analysis:
• No MR after last MC.
• After last successful MR e1b with ASUC
to remove intra-
intra-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
proposed:
• UE behaviour.
behaviour. Redrive for verification.
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)

Category:
• Radio Related: No MR after last MC.
Analysis:
• Analysis:
• No MR after last MC. Due to street
canyon effect, 32335 (169) is
Ec/No
Ec/No 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
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 00 08 D6 E3
RNTI RN23: 09 4F 7 (= 38135)
RN24: 05 E6 5 (= 24165)
UE
UE RSCP
RNC_orig / CID (SC) RN23 / 12707 (159)
RNC_drop / CID (SC) RN24 / 22183 (164)

Category:
Analysis:
• Analysis:
UE
UE Ec/No
Ec/No 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
proposed:
• Redrive on 7 June for verification..
CAD #2-2 – No MR after last MC (UE2: PS FTP => No Drop Call Encountered)
TMSI 00 08 D6 E3
RNTI RN23: 09 4F 7 (= 38135)
RN24: 05 E6 5 (= 24165)
UE
UE RSCP
RNC_orig / CID (SC) RN23 / 12707 (159)
RNC_drop / CID (SC) RN24 / 22183 (164)

Category:
Analysis:
• Analysis:
UE
UE Ec/No
Ec/No Subsequently, AS (SC164) Ec/No
Ec/No
quality degraded, resulting in high
BLER & call was dropped.
• Here, UE2 performing PS FTP
downloading does not have any drop
call.
FTP
FTP Thruput
Thruput
proposed:
TMSI 00 08 E2 13
RNTI RN21: 02 41 E (= 9246)
RN23: 09 87 4 (= 39028)
UE
UE RSCP
RNC_orig / CID (SC) RN21 / 12188 (327)
RNC_drop / CID (SC) RN23 / 12518 (205)

Category:
Analysis:
• Analysis:
UE
UE Ec/No
Ec/No Subsequently, after approx 3 minutes
of driving, UE AS (SC205) Ec/No
Ec/No quality
degraded, resulting in high BLER &
call was dropped.
• See next slide.
Scanner
Scanner
proposed:
CAD #4-2 – No MR after last MC (UE2: PS FTP => No Drop Call Encountered)
TMSI 00 08 E2 13
RNTI RN21: 02 41 E (= 9246)
RN23: 09 87 4 (= 39028)
UE
UE RSCP
RNC_orig / CID (SC) RN21 / 12188 (327)
RNC_drop / CID (SC) RN23 / 12518 (205)

Category:
Analysis:
• Analysis:
UE
UE Ec/No
Ec/No Subsequently, after approx 3 minutes
of driving, UE AS (SC205) Ec/No
Ec/No quality
degraded, resulting in high BLER &
call was dropped.
• Here, UE2 performing PS FTP
downloading does not have any drop
call.
FTP
FTP Thruput
Thruput

proposed:
CAD – UE Related – No MR after Last MC
TMSI 00 3F E7 C6 (4188102)
RNTI 06 19 2 (24978)
Time_orig 18:29:13.959
UE
UE RSCP
RSCP RNC_orig / CID RN23 / 12700 (133)
(SC)
RNC_drop / CID RN21 / 22716 (306)
(SC)
Drop call category:

• UE related
Analysis:
• UE was not sending any MR which
caused the failure in the softer HO.
UE
UE Ec/No
Ec/No • 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
Scanner
Scanner
TMSI 00 08 83 DB
RNTI RN23: 06 FA 8 (= 28584)
UE
UE RSCP
RNC_orig / CID (SC) RN23 / 12508 (201)
RNC_drop / CID (SC) RN23 / 2508

Category:
Analysis:
• Analysis:
UE
UE Ec/No
Ec/No 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.
• Subsequently, UE did not attempt MR
e1c to replace AS with SC208,
probably due to AS Ec/No
Ec/No quality
Scanner
Scanner already bad.

proposed:
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.
TMSI 00 07 DA BB
This
This is
is aa classic
classic case of MR e1a
RNTIcase of MR e1a
with
with
RN24:
No
01 33No
3 (= 4915)
ASU Response
ASU ResponseTime_origthat is NOT
that is NOT due due to
to Network
Network
18:51:48.476
UE
UE RSCP
RSCP Problem
Problem but but due
due toto rapid
rapid changing
changing RF RF
RNC_orig / CID (SC) RN24 / 32324 (147)
environment
environment (Ec Ec/No
/No quality).
((Ec/No quality). ThisThis can
can be be
RNC_drop / CID (SC) RN23 / 22712 (215)
can be confirmed by observing
can be confirmed by observing if the same if the same
deep
deep fade
fade is is experienced
experienced by by the
the 22nd UE.
nd
UE.
Which in this case
Which in this case it was.it was.
This
This can
can be • optimized
be optimized via
via Individual
Drop Call Category:
Category Individual
: CPICH
CPICH
Ec/No
Ec/No Offset
Ec/No • to
Offset advance
to Related:
RF advance MRthe e1aSHO.
the SHO.
with No ASU
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • 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
proposed:
• Mutually define:
• 22712 (215) ' 12700 (133)
AdjsEcNoOffset = 6dB
TMSI 00 07 DA BB
RNTI RN24: 01 33 3 (= 4915)
Time_orig 18:51:48.476
UE
UE RSCP
RSCP
RNC_orig / CID (SC) RN24 / 32324 (147)
RNC_drop / CID (SC) RN23 / 22712 (215)

Category:
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • 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
proposed:
• Mutually define:
• 22712 (215) ' 12700 (133)
AdjsEcNoOffset = 6dB
CAD #3-1 – MR e1a with No ASU Response – Radio related
TMSI 00 07 F0 93
RNTI RN23: 02 AA 4 (= 10916)
Time_orig 10:24:46.945
UE
UE RSCP
RSCP
RNC_orig / CID (SC) RN23 / 26012 (335)
RNC_drop / CID (SC) RN23 / 32187 (245)

Category:
• Radio Related: MR e1a with No ASU
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • 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

proposed:
• 22367 (234):
• E-ADT = 6deg to 4deg
TMSI DD 58 E5 02
RNTI RN21:05 A8 E (= 23182)
UE RSCP
RSCP
RNC_orig / CID (SC) RN21 / 32779 (150)
RNC_drop / CID (SC) RN21 / 326025 (340)

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
non-
non-optimum, resulting in MR e1a to
other non-
non-optimum MS cells.
Scanner
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 DD ED E4 02
RNTI RN23:01 FB A (= 8122)
RN24: 0D 47 C (= 54396)
UE
UE RSCP
RSCP
Time_orig 11:32:47.821
RNC_orig / CID (SC) RN23 / 32530 (222)
RNC_drop / CID (SC) RN24 / 32700 (149)

Category:
• Network related: MR e1a with No ASU
response.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• 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
Scanner to high BLER.
Scanner
proposed:
• Site 2700U to be rehomed from RN24
to RN23 in Phase 2.
RNTI_00001FBA_0273.zip
RNTI_0000D47C_0175.zip
TMSI DD ED E4 02
RNTI RN23:01 FB A (= 8122)
RN24: 0D 47 C (= 54396)
UE
UE RSCP
RSCP
Time_orig 11:32:47.821
RNC_orig / CID (SC) RN23 / 32530 (222)
RNC_drop / CID (SC) RN24 / 32700 (149)

Category:
• Network related: MR e1a with No ASU
response.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• 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
Scanner to high BLER.
Scanner
proposed:
• Site 2700U to be rehomed from RN24
to RN23 in Phase 2.
TMSI DD 4E A5 02
13 Jan 2005 RNTI

Time_orig
01 E5 0 (= 7760)
RNC_orig / CID (SC) RN21 / 38323 (202)

RNC_drop / CID (SC)

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.
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
14 Jan 2005 – Drive #1 – no drop call RNTI

Time_orig
01 E5 0 (= 7760)
RNC_orig / CID (SC) RN21 / 38323 (202)

RNC_drop / CID (SC)

Category:
this cell.
• Analysis:
Analysis:
• Current EADT of 12520 (182) & 22520
proposed:
• 12520 (182) & 22520 (190) EADT
drop call.
TMSI DD 4E A5 02
14 Jan 2005 – Drive #2 – no drop call RNTI

Time_orig
01 E5 0 (= 7760)
RNC_orig / CID (SC) RN21 / 38323 (202)

RNC_drop / CID (SC)

Category:
this cell.
• Analysis:
Analysis:
• Current EADT of 12520 (182) & 22520
proposed:
• 12520 (182) & 22520 (190) EADT
drop call.
TMSI 00 06 B3 E3
RNTI RN22: 12 D7 9 (= 77177)
UE RSCP
RSCP
RNC_orig / CID (SC) RN22 / 22552 (136)
RNC_drop / CID (SC) RN22 / 22552 (136)

Category:
definitions
UE
UE Ec/No
Ec/No • Analysis:
Analysis:
(136) and 32873 (173).

proposed:
Scanner
Scanner • 22552 (136) ' 32873 (173)
TMSI 00 06 B3 E3
RNTI RN22: 12 D7 9 (= 77177)
UE RSCP
RSCP
RNC_orig / CID (SC) RN22 / 22552 (136)
RNC_drop / CID (SC) RN22 / 22552 (136)

Category:
definitions
UE
UE Ec/No
Ec/No • Analysis:
Analysis:
(136) and 32873 (173).

proposed:
Scanner
Scanner • 22552 (136) ' 32873 (173)
CAD #1-1 – MR e1c with No ASU Response
TMSI F2 41 08 00
RNTI RN26: 01 73 1 (= 5937)
UE RSCP
RSCP
RNC_orig / CID (SC) RN26 / 28132 (280)
RNC_drop / CID (SC) RN26 / 12256 (159)

Category:
• RF Related: MR e1c with No ASU
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No
• 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).

proposed:
Scanner
Scanner • To implement 12256 (159) E- E-ADT
uptilt of 2 degs to improve dominance
along highway.
TMSI DD 2A F1 02
RNTI RN23:01 0B C (= 4284)
RN24:00 B9 B (= 2971)
UE
UE RSCP
RSCP
Time_orig 10:03:26.227
RNC_orig / CID (SC) RN23 / 12500 (302)
RNC_drop / CID (SC) RN24 / 12357 (300)

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
proposed:
• Troubleshooted realtime and
resolved. Subsequent calls under
RN23 & RN24 were successful.
CAD #3-1 – MR e1a with No ASU Response – FMT Tool Problem
TMSI 00 09 ED 72
Flatliner
Flatliner –– Tool
Tool
Malfunctioned.
Malfunctioned. RNTI RN23: 11 49 D (= 70813)
Both
Both UEUE traces
traces same.
same.
UE
UE RSCP
RNC_orig / CID (SC) RN23 / 12501 (176)
RNC_drop / CID (SC) RN23 / 12160 (203)

Category:
• Tool related: MR e1a with No ASU
response. FMT Tool not responding /
malfunctioned.
UE
UE Ec/No
Ec/No
• 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.
• This drop call is not due to network
Scanner
Scanner problem.
•
proposed:
CAD #6-1 – No MC after Last ASU+ASUC, MR e1a with No ASU Response
TMSI 00 08 89 E3
RNTI RN24: 04 1E 2
Time_orig 15:21:53.990
UE
UE RSCP
RSCP
RNC_orig / CID (SC) RN24 / 32132 (217)
RNC_drop / CID (SC) RN24 / 22573 (311)

Category:
• Network Related: No MC after last
ASU+ASUC, MR e1a with No ASU
response.
• (Note: somehow, Uu log did not
UE
UE Ec/No
Ec/No 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.
MR+ASU, UE did not send MR e1a
(softer 303) which is the best
Scanner monitored candidate cell (see next
Scanner slide).
e1a to add AS with SC303, probably
due to AS Ec/No
Ec/No quality already bad.
•
proposed:
CAD #6-2 – No MC after Last ASU+ASUC, MR e1a with No ASU Response
TMSI 00 08 89 E3
RNTI RN24: 04 1E 2
Time_orig 15:21:53.990
UE
UE RSCP
RSCP
RNC_orig / CID (SC) RN24 / 32132 (217)
RNC_drop / CID (SC) RN24 / 22573 (311)

Category:
• Network Related: No MC after last
ASU+ASUC, MR e1a with No ASU
response.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• No MC after last ASU+ASUC, MR e1a
with No ASU response. Softer HO
failure.
MR+ASU, UE did not send MR e1a
(softer 303) which is the best
monitored candidate cell (see next
Scanner
Scanner slide). => UE malfunctioned??
e1a to add AS with SC303, probably
due to AS Ec/No
Ec/No quality already bad.
•
proposed:
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 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)

Category:
• BTS Related: MR e1a with No ASU
response.
UE
UE Ec/No
Ec/No • 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
Scanner
Scanner 01 June, no problem or drop call.

proposed:
• Check 2324U detailed BTS alarm history
for 02 June. WCDMA Cell Out of Use
during the above aforesaid period.
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)

Category:
• BTS / Radio Related: MR e1a with No
ASU response.
UE
UE Ec/No
Ec/No • 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.
Scanner
Scanner
proposed:
• Check 2324U detailed BTS alarm
history for 02 June.
Observed
Observed from
from UE
UE that
that RSCP
RSCP && TMSI 00 08 83 DB
Ec/No
Ec/No ofof ALL
ALL AS
AS && Monitored
Monitored RNTI RN23: 06 FB 8 (= 28600)
Set
Set degraded
degraded allall at
at same
same time.
time. Time_orig 14:29:23.733
Suggesting
Suggesting that
that possible
possible BTS
BTS or
or UE
UE RSCP
RSCP
RNC
RNC problem.
problem. RNC_orig / CID (SC) RN23 / 22510 (208)
Also,
Also, no
no meas
meas data
data on
on Scanner.
Scanner. RNC_drop / CID (SC) RN23 / 16012 (327)

Category:
response. BTS
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • Radio Related: MR e1a with No ASU
Ec/No
Possibly DL broken.
• Check BTS alarm history for 6012U on
3 June.
• Need to check RF coverage between
16012 & 26012.
Scanner
proposed:
3 June.
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)

Category:
response.
• Analysis:
Analysis:
Checking Alarm history of 6012U on 03 June 05 Ec/No
Possibly DL broken.
Reviewed that Site / all cells were indeed down at • Check BTS alarm history for 6012U on
3 June.
That exact time of driving through !! • Need to check RF coverage between
16012 & 26012.

proposed:
3 June. Alarm history reviewed that
CAD #3-1 – MR e1b with No ASU Response
TMSI 00 09 7B 32
RNTI RN23: 0C D3 3 (= 52531)
RN24: 08 05 7 (= 32855)
UE
UE RSCP
RNC_orig / CID (SC) RN21 / 12188 (327)
RNC_drop / CID (SC) RN23 / 12518 (205)

Category:
• Network Related: MR e1b with no ASU
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • 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
proposed:
• Redrive for verification..
RRC_Mon_00008057_0CF0.zip
CAD #3-2 – MR e1b with No ASU Response
TMSI 00 09 7B 32
RNTI RN23: 0C D3 3 (= 52531)
RN24: 08 05 7 (= 32855)
UE
UE RSCP
RNC_orig / CID (SC) RN21 / 12188 (327)
RNC_drop / CID (SC) RN23 / 12518 (205)

Category:
• Network Related: MR e1b with no ASU
response.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No • 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
proposed:
• Redrive for verification..
TMSI F2 5C 08 00
RNTI RN26: 01 8B A (= 6330)
UE RSCP
RSCP
RNC_orig / CID (SC) RN26 / 38041 (268)
RNC_drop / CID (SC) RN23 / 22500 (310)

Category:
response. Site 8002U related.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• 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”
failure” and site
was blocked due to “LI”
LI” (RNC time:
2.42pm~2.52pm). Call was dropped
Scanner due to poor Ec/No.
Ec/No.
Scanner

proposed:
• Investigate site bts alarm history.
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)

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)
• Site subsequently recovered around
Scanner 2.52 and subsequent call attempt
Scanner
made on SC259 was successful.

proposed:
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 inter-
RNC Soft Handover is not possible
CN CN
• No Iur between RNCs
• Iur congestion or failure
Iu Iu Iu Iu
• Intra-frequency hard Handover is lossless RNC RNC RNC RNC

for NRT radio bearer but it causes short Iur Iur
disconnection of RT radio bearer.
• Intra-frequency hard handover decisions
made by the RNC are based on the intra-
frequency 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)
• 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
Company for Average EcNo
Confidential (-6…6 dB, default=1 dB)
AveEcNoDownlink ++ HHOMarginAveEcNo
AveEcNoDownlink HHOMarginAveEcNo << AveEcNoNcell
AveEcNoNcell
EcNoDownlink ++ HHOMarginPeakEcNo
EcNoDownlink HHOMarginPeakEcNo << EcNONcell
EcNONcell
Ec/Io HHOMarginAverageEcNo
3 HHOMarginPeakEcNo
P CPICH 1
2
Reporting
range P CPICH 2
P CPICH 3
Time
1
1A (AdditionTime = 0) 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 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
RN26
RN26
RNC_orig / CID (SC) RN26 / 22952 (258)
RNC_End / CID (SC) RN27 / 32242 (264)
RN27
RN27
• Handover Category:
Category:
• Iur Failure - Inter-
Inter-RNC SRNC Relocation
failure => Triggering Inter-
Inter-RNC, Intra-
Intra-
Iur
Iur Failure
Failure !! Frequency HHO.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• Iur failure was simulated / purposely
disabled via blocking AAL2 User Plane,
to invoke Inter-
Inter-RNC, Intra-
Intra-Frequency
HHO.

proposed:
Scanner
Scanner
TMSI 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
RN26
RN26
RNC_orig / CID (SC) RN26 / 22952 (258)
RNC_End / CID (SC) RN27 / 32242 (264)
RN27
RN27
Category:
Inter-RNC, Intra-
Intra-
Frequency HHO.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
to invoke Inter-
Inter-RNC, Intra-
Intra-Frequency
HHO.

proposed:
Scanner
Scanner
Problem Cause:
• Error Alarm from MGW25
• HST (54474) 2U4MG25 1A002-00-

1A002-00-3 COMM 2005-03-
2005-03-21 11:47:02.62
• ISU-0
DISTUR ISU-
• 1205 USER PLANE CONNECTION SETUP FAILURE
• ISU-0
UCNPRB ISU-
• 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 VALUE CHANGE POSSIBILITY
• 00127 AAL2_ANALYSIS_TREE 0001 YES
• After changing value= 3 then working.
• PARAMETER CLASS: 7 CALL_CONTROL
• IDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY

79 • 00127
© 2005 Nokia AAL2_ANALYSIS_TREE 2005.11.050003
Nemo_L3_Analysis_v01.ppt/ / rlim YES
• Case #2:
• Problem:
TMSI 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)
RN23
RN23
Category:
Inter-RNC, Intra-
Intra-
Iur
Iur Failure
UE
UE Ec/No
Ec/No RN21
RN21
• Analysis:
Analysis:
to invoke Inter-
Inter-RNC, Intra-
Intra-Frequency
HHO.

proposed:
Scanner
Scanner
MR
MR e1a
e1a with
with no
no
ASU
ASU Response
Response
due
due to
to Iur
Iur
Failure
Failure
TMSI 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)
RN23
RN23
Category:
Inter-RNC, Intra-
Intra-
Iur
Iur Failure
UE
UE Ec/No
Ec/No RN21
RN21
• Analysis:
Analysis:
to invoke Inter-
Inter-RNC, Intra-
Intra-Frequency
HHO.

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)
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 DD 61 E5 02
RNTI RN21:05 AA 0 (= 23200)
UE RSCP
RSCP
RNC_orig / CID (SC) RN21 / 38323 (220)
RNC_drop / CID (SC)

Category:
• Network: DL RRC Connection Release
after RB Reconfig Complete.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No
• DL RRC Connection Release after RB
Reconfig Complete.
• From ICSU log, transmissionNetwork :
iu-
iu-transport-
transport-connection-
connection-failed-
failed-to-
to-
establish.

proposed:
Scanner
Scanner
CAD #1-1 – DL RRC Conn Rel after RB Reconfig Complete
TMSI DD 61 E5 02
RNTI RN21:00 61 B (= 1563)
UE RSCP
RSCP
RNC_orig / CID (SC) RN21 / 38323 (220)
RNC_drop / CID (SC)

Category:
• Network: DL RRC Connection Release
after RB Reconfig Complete.
• Analysis:
Analysis:
UE
UE Ec/No
Ec/No
• DL RRC Connection Release after RB
Reconfig Complete.
• From ICSU log, transmissionNetwork :
iu-
iu-transport-
transport-connection-
connection-failed-
failed-to-
to-
establish.

proposed:
Scanner
Scanner
Call Setup Failure (CAF) Case Studies
Description:
Call Setup Failures.
Possible Cause:
TMSI D5 C2 82 02
RNTI
Time_orig
RNC_orig / CID (SC) RN22 / 32897 (312)
RNC_drop / CID (SC)

Category:
• Analysis:
Analysis:
response.
(312) & 22835 (309).
proposed:
• 32897 (312) ⇔ 22835 (309).
TMSI D5 C2 82 02
RNTI
Time_orig
RNC_orig / CID (SC) RN22 / 32897 (312)
RNC_drop / CID (SC)

Category:
• Analysis:
Analysis:
response.
(312) & 22835 (309).
proposed:
• 32897 (312) ⇔ 22835 (309).
RNC
RNC ID:ID: 202
202
Cell
Cell ID:
ID: 22835
22835
CAF #1 – UL “CM Service Abort” due to Nemo CAA=15sec Timed Out
TMSI 00 07 DB 53
RNTI RN23: 02 24 5 (= 8773)
Time_orig 18:59:55.248
UE
UE RSCP
RSCP
RNC_orig / CID (SC) RN23 / 12583 (157)
RNC_drop / CID (SC)

Category:
• UE / Tool related: UL “CM Service
Abort”
Abort” due to Nemo CAA=15sec timed
out.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• UE / Tool related: UL “CM Service
Abort”
Abort” due to Nemo CAA=15sec timed
out. Call setup procedure was actually
on-
on-going.
• 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
Scanner
Scanner was on-
on-going. Nemo FMT issued
command to UE to abort.

proposed:
CAF #2 – UL CM Service Abort - Nemo CAA Call Attempt=15secs Timed-out
– Call Setup On-going
TMSI 2A 68 3F 03
RNTI RN22: 09 80 5 (= 38917)
UE RSCP
RSCP
RNC_orig / CID (SC) RN22 / 22046 (259)
RNC_drop / CID (SC)

Category:
• Tool related: UL CM Service Abort due
to Nemo CAA attempt timed out after
15secs.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
• Tool related: UL CM Service Abort due
to Nemo CAA attempt timed out after
15secs. Call setup was actually on-
on-
going. 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
Scanner
Scanner call setup was on-
on-going, Nemo tool
CAA timer=15sec expired and call was
aborted.

proposed:
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)

Category:
• Network related: 2 x RRC Connection
Request with no Response.
UE
UE Ec/No
Ec/No
• Analysis:
Analysis:
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
Scanner RRC Connection Request to the 3rd RRC
Scanner
Conn Req was >8secs, this would be
interpreted as a CAF by Actix.
Actix.

proposed:
CAF #1-#4 – Call Setup Failed after “Call Proceeding”
– DL RRC Connection Release
TMSI DD 58 E5 02
RNTI RN24:00 BA 9 (= 2985)
UE
UE RSCP
RSCP
Time_orig 10:22:18.455
RNC_orig / CID (SC) RN24 / 12359 (182)
RNC_drop / CID (SC)

Category:
• Network related: Call setup failed after
“Call Proceeding”
Proceeding” – DL RRC Connection
Release.
UE
UE Ec/No
Ec/No
• 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
proposed:
• Troubleshooted realtime and
resolved. Subsequent calls under
RN23 & RN24 were successful.

Nemo L3 AMR Analysis External 2G 3G PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nemo L3 AMR Analysis External 2G 3G PDF

Uploaded by

Copyright:

Available Formats

L3 ANALYSIS / OPTIMIZATION EXAMPLES

(Using Nemo Outdoor)

• Objective of this slideset package is to consolidate all the learnings of L3

• (this may not work for v.25)

• Best practice suggestion – 手機和Scanner的lLog一起開

• Nemo measurement data logs (off course)

• FMT tool related: Nemo CAA=15sec timeout or expired

System Information Block (SIB)

Information Block Description

MIB PLMN types & identities

SIB1 NAS information

SIB3 Cell selection and re-selection parameters

SIB5 Parameters for common physical channel configuration

SIB7 UL interference level

RRC Connection Stage

Location Update Request

Location Update Accept

RRC Connection Release

RRC Connection Setup

Radio Bearer Setup Procedure

Call Setup Success

Disconnect and Release

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

AAL2S IG : E R Q Security Mode Procedures AMR MOC

R AN A P:IN IT IAL U E M ESS AG E

RANAP: DIRECT TRANSFER

RANAP: Iu RELEASE COMMAND

R R C : R AD IO BEAR E R S ET U P C O M PLET E AAL2SIG: RLC

R AN A P:R AB ASS IG N M E N T R E SPO N SE

R R C : D O W N LIN K D IR EC T T R AN SF E R (Alerting) (A lerting)

13 © 2005 Nokia Nemo_L3_Analysis_v01.ppt/

RRC:RRC CO NNECTION REQ UEST

NBAP:RADIO LINK SETUP REQ UEST

NBAP:RADIO LINK SETUP RESPONSE

RRC:RRC CO NNECTION SETUP

RRC:INITIAL DIRECT TRANSFER (Paging response)

RANAP: DIRECT TRANSFER

RRC: UPLINK DIRECT TRANSFER (Call confirmed)

RANAP: DIRECT TRANSFER

RANAP:RAB ASSIGNMENT REQUEST

NBAP:RADIO LINK RECO NFIGURATION PREPARE

NBAP:RADIO LINK RECO NFIGURATION READY

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

RANAP: DIRECT TRANSFER

RRC: UPLINK DIRECT TRANSFER (Connect Acknowledge)

RANAP: DIRECT TRANSFER

Company Confidential (Connect Acknowledge)

15 © 2005 Nokia Nemo_L3_Analysis_v01.ppt/ 2005.11.05 / rlim

Attach & Authentication Procedure

PDP Context Activation & Radio Bearer

Radio Bearer Reconfiguration

PDP Context Deactivation Procedure

Detach & Radio Bearer Release Procedure

RRC Connection Release

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RRC:RRC CONNECTION SETUP

PDP Context is active