Vous êtes sur la page 1sur 29

WCDMA Analysis Guideline

Shenzhen ZTE Project 15-July-2009

Introduction
y

This guild line aims at helping new engineers to identify the root of the problems.The engineer should have some basic on UMTS and familiar with ZTE CNA in order to follow this guide line.

Mobile Originate CS Call Setup

Mobile Originate CS Call Setup :cont

Mobile Originating CS Call release

Mobile originating PDP Context Activation

Mobile originating PDP Context Deactivation

Identify CS CAF problem : example


2

3
No RB reconfiguration from nodeB

1
No Active Set update from nodeB Ue switch to idle, no DL connect -> CAF

1. 2. 3. 4. 5.

Check RRC/L3 message : message incomplete -> NOK !! Check DL RF Condition : Active set RSCP & EcIo meet Threshold -> OK Check UL condition : ULInterference & TxPower < Threshold -> OK Check dedicated channel : BLER <= Threshold -> OK Check Cause matrix : -> non-RF cause => check alarm & supervision & PM

Identify abnormal CAD problem : example


2

1
Ue switch to idle, no UL disconnect -> CAD

1. Check RRC/L3 message : message incomplete -> NOK !! 2. Check DL RF Condition : Active set RSCP & EcIo meet Threshold -> NOK missing adjacency threshold = Drop bad quality due to missing neigboring 3. Check Cause matrix : -> RF cause => MissADJ

Drive Test Problem Cause code Matrix

MAJOR GROUP : RF

RF : Cross Feeder
y y y

Cross sector problem can be quickly identify from best server map using Nemo Analyzer Run cell footprint map (RSCP) of each sector Check site location , map terrain and coverage prediction( if available) to confirm. This to confirm that problem not due to blocking and reflecting signal

sector1

sector2

2. Run Cell foot print of 3 sectors 3. Check with Coverage prediction (if available) 4. Check site location, map& terrain

Best server plot

1. Check Best Server Map => Suspect !!

sector3

RF : Late Cell Reselection


2. Best SC active set RF threshold -> Fail

3. SC monitor set RF threshold -> Pass

1
1. CAF : not complete call setup message 1. 2. This case shows that Ue is moving from SC 221 to direction of SC298 in idle mode Call was setup at SC221 where the radio condition is degrading instead of set up call at SC298, late reselection from SC221 to SC298 when in idle mode => CAF NOK 3. Check measurement 5s before/after event = > confirm Ue camp on SC298 after event 4. Identify matrix cause => RF cause => Late Cell Reselection Note : idle mode parameters detail can be found in basic feature description document, Qoffset2n.

RF : Miss Neighbor
3. Detected SC missing adj. Threshold -> Pass

2. Best SC active set RF threshold -> Fail

4
4. Check map if missing adj. in 1st and 2nd ring from active SC -> Yes

1
1. Identify abnormal CAD

1.To identify missing adjacency , the missing adjacency RF Condition threshold is setup. 2. Check measurement about 5 seconds before event , if the threshold valid during this time 3. Check measurement about 5 seconds after event. Check which sector Ue camp on. 3. Check latest parameter compare with drive test date. Problem could be due to operational/error on test date , not real missing
Note: threshold guild line for quickly identify, not necessary to be rule . The analysis need also engineer field experience

RF : Overshooting
pb area& serving cell

2.SC active set RF threshold -> Fail

4. Bad DL BLER overshooting cell

3. detected set in window range

1. Abnormal CAD : received RRC connection release cause unspecified 1.This case shows similar RF condition to missing adjacency criteria 2. From map , it show problem area is near to serving cell, while detected set SC148, SC316 is shooting from behind of active set cell 3. Run cell foot print from Nemo analyzer to confirm detected set overshooting coverage 4. Check physical antenna configuration if tilting is possible 5. Identify matrix cause => RF => Overshooting ( overshooting where the fix is down tilt to control the spill of the signal)

RF : Poor Coverage
4. Planned site in area ?

3. Dedicated & UL Power Threshold => NOK

2. RF Threshold => NOK for all: active , monitor and detected set

1
1. Identify abnormal CAD 1. This call shows limited of coverage in the area : - None of dl signal is higher than poor coverage threshold, dl dedicated BLER > 1% ( dl limited) - Ue transmit max power ( uplink limited) Check if any planned site in this area ? Identify matrix cause => RF cause => Poor Coverage

2. 3.

Note : in case of coverage limited both RSCP and EcIo always below threshold, identify cause as poor-RSCP instead of poor-Ec/Io is better way to represent coverage limited

RF : Slow HO

1. CAD : AS signal sudden degraded dramatically

3. SC monitor set RF threshold -> Pass

2. Best SC active set RF threshold -> Fail 1. This case shows that Ue is moving from SC 241 to direction of SC152 in dedicated mode 2. Call was setup at SC221 where the radio condition is dramatically degrading where handover from cell SC241 to SC152 which is not fast enough => CAD NOK 3. Check measurement 5s before/after event = > confirm Ue camp on SC152 after event 4. Identify matrix cause => RF cause => Slow HO 5. Suggest to adjust CIO between the two cell to decrease the HO time taken. Note : dedicated mode HO parameters detail can be found in basic feature description document

Drive Test Cause Matrix

MAJOR GROUP : IUR / CORE / NODE-B / OTHER NODE-

Core : PDP-Deactivation PDP2. RF condition threshold->Pass

1. Identify abnormal PAD 1. This case Ue receive downlink deactivate PDP Context request - check deactivation cause Reactivation required - check file transfer not yet complete ( transferring 2.6M of 5M) This case is clearly seen the connection close request by core network but RF condition check is to confirm not related problem with RF cause Identify matrix cause => non-RF => group core => PDP-Deactivation-> need to check signal trace to sort out the reason for PDP deactivation.

2. 3.

NodeB : UL-AlarmNodeB UL2 3


3. Monitor RF threshold => OK 4. Check if UE send MR e1a this SC => OK 5. UL RF threshold => Problem 2. Active set DL RF threshold => NOK

4 5 1
1. Identify abnormal CAD

1. Check RF measurement 5 s before and after event. This case shows quality degrade then drop due to no active set update received 2. Check uplink RF threshold. Ue sent max transmit power when camp on SC171 => NOK 3. Check NodeB alarm &supervision = > RETU&ASC alarm => NOK 4. Check pmAverageRssi report = > NOK ( < -106 dBm) 5. Identify matrix cause => non-RF => nodeB alarm => nodeB cause => UL-AlarmNodeB

Other: Oth-PLMN Oth4. Layer1 report AC UARFCN=10762

1. Ue read master_Info_blck -> PLMN 50219 2. LAU/ RAU request 3. LAU/ RAU reject

Nemo identify this case as PS RUF Protocol error unspecified -> routing area update failure Check RRC/L3 message - Ue request LAU /RAU to network , network reject LAU with cause no suitable cell in LA - Network reject RAU with Protocol error unspecified , consequence of LAU reject - Check RRC Master_Information_Block -> Ue report PLMN= 50219 -> other PLMN network 3. Check Layer1 report show Ue camp on UARFCN = 10762 - > confirm other PLMN network 4. Identify matrix cause => non-RF => Other => Oth-PLMN

1. 2.

Drive Test Problem Cause Matrix

MAJOR GROUP : TOOL / UTRAN / UNKNOWN

Tool : DT-Fail DT-

2. Check layer1 report during gap timer

1. Identify CAF

1. Nemo identify this case as CAF : Test System Failure 2. Check time from last RRC/L3 dedicated channel to idle channel -> 5 minutes different 3. Check Layer1 report during that 5 minutes different -> Layer1 data freeze 4. Identify matrix cause => non-RF => Tool cause => DT-Fail

Tool : DT-User DT1. Check RRC/L3 messages, Identify CAF

Ue receiving SMS

1. Nemo identify this case as CAF : Timeout before connection due to missing of Radio Bearer setup 2. Check establishment cause RRC connection request => originatingConversationalCall ? NOK 3.This case show that the Ue receive SMS during drive test : RRC connection request establishment cause terminatingLowPrioritySignalling 4. Identify matrix cause => non-RF => Tool cause => code DT-User

UTRAN : BLCK

2. No uplink 1. Check RRC/L3 messages, Identify CAF

1. 2. 3.

Check RRC/L3 message : Ue received DL NAS Disconnect during call set up -> CAF NOK!! - check disconnect cause -> No circuit/channel available Check pmNoReqDeniedAdm & pmNoFailRabEstAtt_xx counter during drive test problem Indentify matrix cause => UTRAN => BLCK (call return as congestion or no channel available)

Note: pm procedure is reference in U Mobile Network Statistic KPI(P5) document

UTRAN : No-Rrc No2


2. DL RF Threshold -> pass

3. UL & DCH Threshold -> pass 1. Identify abnormal CAF

3 1

Expected RB_reconfiguration : missing

Expected Active_set update : missing

1. Check RRC/L3 message : CAF NOK!! 2. Check radio condition threshold pilot and dedicated channel -> pass 4. Indentify matrix cause => non-RF => UTRAN => No-Rrc

Unknown: DL1
2. DL RF Threshold -> Pass

3. Dedicated &UL Threshold -> Pass

1. Identify abnormal CAD

1. Check RRC/L3 message : Ue received Downlink RRC Connection release from network -> CAD NOK!! - check connection release cause unspecified 2. Check radio condition threshold pilot and dedicated channel -> pass 3. Check radio condition 5s before/after event , check PM cell availability , check supervision -> pass 4. Indentify matrix cause => non-RF => unknown => DL1

Unknown: Iur-1 Iur1. Identify abnormal CAD

2. Radio Condition -> Pass

3. UE transmit power reached Max -> Failed

4. Identify area, RNC border-> suspect Iur transmission error.

1. Check RRC/L3 message : UE received Downlink RRC Connection release from network -> CAD NOK!! - check connection release cause normal event 2. Check radio condition threshold pilot and dedicated channel -> pass 3. Check radio condition 5s before/after event , check PM cell availability , check supervision -> pass 4. Indentify matrix cause => non-RF => unknown => Iur transmission error.

Unknown: Iur-2 Iur-

1. Identify abnormal CAD

2. Radio Condition -> Pass

3. UE transmit power reached Max -> Failed

4. Identify area, RNC border-> suspect Iur transmission error.

1. Check RRC/L3 message : UE received Downlink RRC Connection release from network -> CAD NOK!! - check connection release cause normal event 2. Check radio condition threshold pilot and dedicated channel -> pass 3. Check radio condition 5s before/after event , check PM cell availability , check supervision -> pass 4. Indentify matrix cause => non-RF => unknown => Iur transmission error.

The End