KPI Monitoring and Improvement Guide 20090507 a 1.0

8/20/2019 KPI Monitoring and Improvement Guide 20090507 a 1.0

http://slidepdf.com/reader/full/kpi-monitoring-and-improvement-guide-20090507-a-10 1/82

W-KPI Monitoring and Improvement Guide For Internal Use only

Product Name Confidentiality Level

WCM! "NP For Internal Use #nly

Product $ersion

%otal &' Pages()*

W-KPI Monitoring and Improvement Guide

+For Internal Use only,

Prepared by

u Wensu Date .**&-((-./

Reviewed by

e Fengming0 1i 23u4i0 and Fang Ming Date .**&-((-./

Reviewed by

5in 6an Date .**&-((-./

Approved by

7ie 83i9in Date .**&-((-./

Huawei Technologies Co., td

All Rights Reserved

2009-05-06 ua:ei Confidential Page ! o" #$




Revision History

Date RevisionVersion

Description Author

.**&-((-./ ()* Modifications are made to t3e initial draft according to t3e

revie: comments)u Wensu

2009-05-06 ua:ei Confidential Page % o" #$




Contents

1 Data Collection...........................................................................13

()( #vervie:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))('

(). "eal-%ime 2tatus Monitoring Functions of t3e "NC))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))('

()' Message %racing Functions of t3e "NC)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))('

(); Connection Performance Monitoring Function of t3e "NC))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(;

()< Cell Performance Monitoring Function of t3e "NC))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(;

()= Lin> Performance Monitoring Function of t3e "NC)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(<

()? Message %racing Pat3 of t3e "NC)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(<

()& "NC MML 2cript))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(=

()/ "NC C" Logs)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(=

()(* "NC %raffic 2tatistics File)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(=

()(( @rief 2ummary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(=

2 Analyzing eighbor Cell Proble!s................................................1"

.)( #vervie:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(?

.). Principles for 2etting Neig39or Cells))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(?

.)' Process of #ptimiAation Neig39or Cells)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(&

.); Configuration of Initial Neig39or Cells)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(&

.)< !nalyAing Incorrectly Configured Neig39or Cells Pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))(/

.)= !nalyAing Unnecessary Neig39or Cells Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))(/

.)? !nalyAing Missing Neig39or Cells Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).*

.)& #ptimiAing t3e Priority of Neig39or Cells))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))..

.)/ C3ec>ing #ne-Way Neig39or Cell))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )))..

.)(* #ptimiAing Inter-Fre4uency Neig39or Cells)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )))..

.)(( #ptimiAing Inter-2ystem Neig39or Cells))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).'

.)(. 2ummary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).'

3 Analyzing Accessing Proble!s.....................................................2#

')( #vervie:)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).;

'). efinition of !ccess Failure))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))).;

').)( efinition of Call Failure 9y GBNB7 !ssistant)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).;

').). efinition of !ccess Failure 9y !cti !nalyAer))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).=

').)' efinition of !ccess Failure 9y %BM2))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))).=

')' Flo: and Met3ods for !nalyAing !ccess Failure Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).?

2009-05-06 ua:ei Confidential Page $ o" #$




'); !nalyAing Paging Pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).&

');). Failure in 2ending Paging Message 9y "NC))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).&

');)' #ver Lo: Po:er of PC or PIC)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )))./

');); Cell "eselection 9y UB)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))./

')< !nalyAing ""C Connection 2etup Pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))./

')<)( !fter UB 2end ""C Connection "e4uest Message0 t3e "NC Fails to "eceive It))))))))))))))))))))))) ))))))))))'*

')<). !fter t3e "NC "eceives t3e ""C 2etup "e4uest Message from UB0 It sends t3e ""C Connection

"eDect Message))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'*

')<)' !fter t3e "NC "eceives t3e ""C 2etup "e4uest Message from UB0 It 2ends t3e ""C Connection

2etup Message W3ic3 Is Not "eceived 9y UB)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'(

')<); !fter "eceiving ""C Connection 2etup Message0 t3e UB oes Not 2end 2etup Complete Message) '.

')<)< !fter t3e UB 2ends t3e ""C 2etup Complete Message0 t3e "NC Fails to "eceive It))))))))))))))))))))))))))'.

')= !nalyAing !ut3entication Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )))))))))) ))'.

')=)( M!C Failure)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'.

')=). 2ync Failure))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )''

')? !nalyAing 2ecurity Mode Pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) )))';

')& !nalyAing PP !ctivation Failure Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'<

')/ !nalyAing "!@ or "@ 2etup Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'<

')/)( irect "eDection of "!@ 2etup "e4uest 9y "NC ue to Incorrect Parameter Configuration)))))))))) ))))'<

')/). !dmission "eDection)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'=

')/)' %3e UBEs "esponse of "!@ 2etup Failure due to "@ 2etup Failure)))))))))))))))))))))))))))))))))))))))))))))))))))))'?

')/); "!@ 2etup Failure due to "@ 2etup Failure at !ir Interface)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'&

')(* !nalyAing !ccess Pro9lems in t3e Case of ual9and Net:or>ing))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))'&

')(*)( ""C direct retry and re-direction during setup of t3e ""C)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'/

')(*). %3e "!@ irect "etry))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'/

')(*)' !nalyAing !ccess Pro9lems in t3e Case of ual9and Net:or>ing))))))))))))))))))))))))))))))))))))))))))))))))))))));*

')(( !nalyAing M@M2 service access pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));.

')(()( t3e flo: c3art of 9roadcast model in M@M2)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));.

')((). %3e causes t3at UB cant receive programs))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));'

')(. Processing !ccess elay)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));;

')(.)( Configuration of iscontinuous Cyclic Period uration Factor "7)))))))))))))))))))))))))))))))))))))))))))))))));;

')(.). W3et3er to isa9le !ut3entication and Bncryption Flo:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));<

')(.)' Implementing Barly or Late !ssignment))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));<

')(.); W3et3er t3e ""C Connection Is 2et up on F!C and C)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));<

')(.)< Impact of irect "etry !nd "edirection !lgorit3mon !ccess elay)))))))))))))))))))))))))))))))))))))) )))))))))) ));<

')(' @rife 2ummary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));=

# Analyzing $% Proble!s...............................................................#"

;)( #vervie:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));?

;). !nalyAing 2# Pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));&

;).). Inputting !nalysis ata))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) );&

;).)' #9taining W3en and W3ere t3e Pro9lem #ccurs)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));&

;).); Miss Neig39or Cell)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));/

2009-05-06 ua:ei Confidential Page & o" #$




;).)< Pilot Pollution)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));/

;).)= Improper Configuration of 2# !lgorit3m Parameters)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))<*

;).)? !9normal B4uipment))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<*

;).)& "eperforming rive %est))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<*

;).)/ !dDustment and Implementation)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<(

;)' !nalyse # Pro9lem)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) )<(

;); Inter-"!% andover C5% Flo:)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))<'

;)< %C5% Flo: for 2P! andover))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<<

;)= M@M2 Mo9ility #ptimiAation))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=

;)? @rief summary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<=

& Analyzing Call Drop Proble!s......................................................&"

<)( #vervie:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<?

<). efinition of Call rop))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<?

<)' %C5% #ptimiAation Flo:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<&

<); !nalayAing Wea> Coverage Pro9lem))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) ))</

<)< !nalayAing Interference Pro9lem)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) )=*

<)= !9normality !nalysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))=*

<)? M@M2 C" Pro9lem !nalysis))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))=*

<)& @rief summary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=(

' Anaylzing (rans!ission Proble!..................................................'2

=)( #vervie:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=.

=). "ules for %ransmission Configuration on t3e %ransmission Layer))))))))))))))))))))))))))))))))))))))))))))))))))))) )))))))))) ))=.

=)' 5uerying t3e %ransmission @and:idt3))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))='

=)')( Configuring @and:idt3 of t3e Iu C2 2ignaling Plane)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))='

=)'). 5uerying t3e Configured @and:idt3 of t3e Iu C2 User Plane)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=;

=)')' 5uerying t3e Configured @and:idt3 of t3e Iu P2 2ignaling Plane)))))))))))))))))))))))))))))))))))))))))))))))))))))))=;

=)'); 5uerying t3e Configured @and:idt3 of t3e Iu P2 User Plane))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))=;

=)')< 5uerying t3e Configured @and:idt3s of t3e NCP and CCP))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=<

=)')= 5uerying t3e Configured @and:idt3 of t3e Iu@ %ransmission User Plane)))))))))))))))))))))))))))))))))))))))))))=<

=); Influence of %ransmission Pro9lems on KPIs))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=?

=);)( Influence of %ransmission Pro9lems on t3e 5uality of C2 2ervices))))))))))))))))))))))))))))))))))))))))))))))))))))))=?

=);). Influence of %ransmission Pro9lems on t3e User "ate)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=?

=);)' I Influence of %ransmission Pro9lems on PING elay))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=?

=);); !nalyAing %ransmission Pro9lems of t3e User Plane)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=&

=)< Important IP"!N Configurations))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=&

=)<)( "!N 2ide))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=&

=)<). Node@ 2ide)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=/

=)<)' "estraints on Configuration of IP !ddresses))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))=/

=)= @rief 2ummary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?*

" Per)or!ance Analysis.................................................................."1

?)( 2ummary))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?(

2009-05-06 ua:ei Confidential Page ' o" #$




?). Necessary 2>ills #f Performance !nalysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) ))?(

?).)( 2ignaling Flo: !nd @asic Principles)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?(

?).). FamiliariAation of U%"!N PIs)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?.

?).)' Use of t3e Nastar %ool))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?.

?)' Preparations For Performance !nalysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?.

?)')( Kno:ledge of Net:or> Conditions))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?'

?)'). Preparations for Performance !nalysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))?'

?)')' Met3ods of Performance !nalysis))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?;

?); Met3od of !larm ata !nalysis))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) ))))?<

?)< 5uic> !nalysis of 2ome PIs))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?<

?)<)( 5uic> !nalysis of 2ome PIs)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?<

?)<). Commonly 2een PIs and Corresponding !nalysis Idea))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))?=

?)= procedures of Performance !nalysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) ))))?=

?)=)( #verall analysis of net:or> KPI))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))??

?)=). !nalysis of "NC B4uipment Pro9lem))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))??

?)=)' KPI analysis of %#PN cell)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?&

?)=); Cell e4uipment analysis))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?&

?)=)< !nalysis of cell load pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?&

?)=)= !nalysis of cell interference pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))?/

?)=)? !nalysis of cell coverage pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))?/

?)=)& !nalysis of parameter pro9lems))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))?/

?)? @rief 2ummary)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))&*

* Conclusion..................................................................................*1

+ Re)erences.................................................................................*2

2009-05-06 ua:ei Confidential Page ( o" #$



ist o" )igures

)igure %-! Intra-fre4uency unnecessary neig39or analysis)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).*

)igure %-% Intra-Fre4uency Missing Neig39our !nalysis))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))).*

)igure %-$ Missing neig39or analysis list))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).(

)igure %-& ra: Neig39or Cells on Map))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).(

)igure %-' #ne-:ay neig39or c3ec>)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))..

)igure $-! Flo: of !nalyAing !ccess Failure Pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))) ).?

)igure $-% 2ignaling flo: of originated UB in locating paging pro9lems)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).&

)igure $-$ Flo: for analyAing ""C connection setup pro9lem)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))'*

)igure $-& !ut3entication failure due to M!C Failure)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))''

)igure $-' !ut3entication failure due to 2ync3 Failure))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))''

)igure $-( 2ecurity mode control)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))';

)igure $-* 2ecurity mode reDect))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))';

)igure $-# ""C direct retry and re-direction during setup of t3e ""C connection)))))))))))))))))))))))))))))))))))))))))))))'/

)igure $-+ 2ignaling for service-9ased direct retry of a 2P! su9scri9er))))))))))))))))))))))))))))))))))))))))))))))))) )))))));(

)igure $-! 2ignaling for direct retry of a "// su9scri9er after admission reDection))))))))))))))))))))))))))))))))))))))))));.

)igure $-!! Flo: c3art of 9roadcast model in M@M2)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))));.

)igure &-! s3o:s t3e 2# % data analysis flo:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) );&

)igure &-% s3o:s t3e optimiAation flo: for # C5%)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<.

)igure &-$ Inter-"!% 3andover C5% flo:))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) ))))))))))<'

)igure '-! Flo: c3art for analyAing call drop))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))<&



W-KPI Monitoring and Improvement Guide

Ke wordsH WCM!0 access0 3andover0 call drop0 performance analysis0 KPI0 net:or> optimiAation

/stract0 %3is document descri9es 3o: to locate and resolve pro9lems suc3 as access0 3andover0 call drop0 andnet:or> performance analysis in optimiAation of WCM! net:or>s0 and provides corresponding analysis

processes and solutions)

,ist o) abbreviations and acrony!s-

Abbreviation ull /pelling

!LC!P !ccess Lin> Control !pplication Part

!P2 !%M Protection 2:itc3ing

!%M !sync3ronous %ransfer Mode

C!PB7 Capital Bpense

CCP Communication Control Port

CL Call etail Log

C" Call rop "ate

CB C3annel Blement

C" Call istory "ecord

Cluster %uning Cluster %uning

CN Core Net:or>

CPIC Common Pilot C3annel

C5I C3annel 5uality Indicator

C5% Call 5uality %est

C"NC Controlling "adio Net:or> Controller

" irected "etry ecision

% rive %est

B-!GC B-C !9solute Grant C3annel

B-C Bn3anced uplin> edicated C3annel

B-"GC B-C "elative Grant C3annel

G@P Po:er to meet G@"

G@" Guaranteed @it "ate

GP2 Glo9al Positioning 2ystem

2P! ig3 2peed o:nlin> Pac>et !ccess





2-2C ig3 2peed o:nlin> 23ared C3annel

2-2CC ig3 2peed 23ared Control C3annel

2UP! ig3 2peed Uplin> Pac>et !ccess

ICMP Internet Control Message Protocol

Initial %uning Initial %uning

I#2 Intelligent #ptimiAation 2ystem

IP Internet Protocols

IPo! Internet Protocols #ver !%M

KPI Key Performance Inde

L!N Local !rea Net:or>

M!C Media !ccess Control

Ma "ate Com9ining Ma "ate Com9ining

M@M2 Multimedia @roadcast and Multicast 2ervice

MML Man Mac3ine Language

MP# Measurement Po:er #ffset

M2P Multiple 2ection Protection

M%P'@ Message %ransfer Part

NCP Node@ Control Port

NBMU Node@ Bnvironment Monitor Unit

NIC Net:or> Interface Card

NM#N Node@ Monitor Unit

Node@ Node @

NPI Net:or> Performance Improvement

NPM Net:or> Performance Monitoring

#CN2 #rt3ogonal C3annel Noise 2imulator

#MC #peration maintenance Centre

#n-Going #n-Going

#PB7 #peration Bpense

PC" Performance Call istory "ecord

PP Pac>et data protocol

PI Performance Inde

2009-05-06 ua:ei Confidential Page ! o" #$





PPP Point to Point Protocol

PPPo! PPP over !%M

PPPoB PPP over Bt3ernet

P2 Pac>et-2:itc3ed domain

P%M Point to Multipoint

P$C Permanent $irtual Connection

5o2 5uality of 2ervice

"!@ "adio !ccess @earer

"!M "andom !ccess Memory

"F "adio Fre4uency

"FP "e4uest for Proposal

"IP "outing Information Protocol

"NC "adio Net:or> Controller

""C "adio "esource Control

""U "adio "emote Unit

"2CP "eceived 2ignal Code Po:er

"%WP "eceived %otal Wide9and Po:er

2!!L 2ignaling !%M !daptation Layer

2CCP 2ignaling Connection Control Part

2elective Com9ining 2elective Com9ining

2N" 2ignal to Noise "atio

2oft Com9ining 2oft Com9ining

2% 2tatistics %est

2ystem %uning 2ystem %uning

%@ %ransport @loc>

%CP %ransfer Control Protocol

UP User atagram Protocol

UB User B4uipment

$CI $irtual C3annel Identifier

$IC $ery Important Cell

$IP $ery Important People

2009-05-06 ua:ei Confidential Page !! o" #$





$P $ideo P3one

$PI $irtual Pat3 Identifier

W!N Wide !rea Net:or>

W@2 Wor> @rea>do:n 2tructure

2009-05-06 ua:ei Confidential Page !% o" #$




1 Data Collection

1.1 %verviewata collection is t3e foundation of KPI monitoring and optimiAation) @efore net:or> optimiAation0

t3e parameters of t3e net:or> planning and optimiAation data s3ould 9e arc3ived and maintained

timely) Mean:3ile0 t3e complete operating records s3ould 9e reserved) !s practice proves0standardiAed data arc3ives can greatly reduce performance 3arms for 3uman reasons)

For net:or> optimiAation engineers0 data files involved in t3eir :or> mainly include t3e GBNB7

Pro9e drive test file0 GBNB7 !ssistant analysis data9ase0 GBNB7 Nastar analysis data9ase0 and"!N maintenance console trace file) For data files relevant to t3e GBNB7 soft:are0 refer to t3e

corresponding user manuals a9out t3e GBNB7 tool) %3e follo:ing in t3is c3apter is a s3ort

introduction to t3e "!N maintenance console trace file) For details0 refer to t3e W-B4uipment "oom

#perations Guide and LM% elp File)

1.2 Real0(i!e /tatus onitoring unctions o)the RC

%3e "NC provides t3e follo:ing functions of real-time system status monitoringH

Interface tracing

Location tracing

CPU2P occupation rate monitoring

Connection performance monitoring

Cell performance monitoring

Lin> performance monitoring

1.3 essage (racing unctions o) the RC

%3e "NC provides various functions of message tracing0 consisting ofH

%racing of standard interface messages

%racing of transport layer protocol messages

2009-05-06 ua:ei Confidential Page !$ o" #$




Call tracing

%racing of neig39or cell missing

Cell message tracing

%racing of messages sent and received 9et:een internal modules of t3e system

%racing of redirected serial port messages

IP tracing

C% tracing

Cell% message tracing

Location message tracing

1.# Connection Per)or!ance onitoring

unction o) the RC%3e connection performance monitoring function provided 9y t3e "NC can monitor t3e follo:ing

state of eac3 communication connectionH

%3e connection performance monitoring function provided 9y t3e "NC can monitor t3e follo:ing

status of eac3 communication connectionH

Cell signal to noise ratio +2N", and received signal code po:er

Measured value of t3e uplin> radio lin> set signal-to-interference ratio

Bn3anced function of t3e outer loop po:er control

Measured value of signal-to-interference deviation of t3e uplin> radio lin> set

o:nlin> code transmitter po:er UB transmitter po:er

Uplin> traffic

o:nlin> traffic

Uplin> t3rougout and 9and:idt3

o:nlin> t3roug3put and 9and:idt3

andover delay

!M" mode

1.& Cell Per)or!ance onitoring unction o)the RC

%3e cell performance monitoring function provided 9y t3e "NC can monitor t3e follo:ing status of

a cellH

PCPIC pilot transmitter po:er

Uplin> receiving total :ide9and po:er

o:nlin> carrier transmitter po:er

2009-05-06 ua:ei Confidential Page !& o" #$




Num9er of cell users +consisting of dedicated c3annel users0 common c3annel users0

2P! users0 and 2UP! users,

Node sync3roniAation

Uplin> access decision

o:nlin> access decision

Num9er of uplin> e4uivalent users

Num9er of do:nlin> e4uivalent users

Usage of t3e code tree

2-2C minimum po:er re4uirement

@it rate provided 9y 2-2C

@it rate provided 9y B-C

Uplin> t3roug3put

o:nlin> t3roug3put

1.' ,in Per)or!ance onitoring unction o)the RC

%3e "NC can monitor t3e performance state of t3e follo:ing lin>sH

IM! group

UNI lin>

F"!C !%M lin>

2!!L lin> IPo! P$C

IPP!% 5o2

!!L. P!%

IP P!%

FBGB traffic

PPP lin> traffic

MLPPP group traffic

2C%P lin> traffic

1." essage (racing Path o) the RCIntegrated in t3e LM%0 t3e message tracing function of t3e "NC can 9e used conveniently and

provides effective means of locating pro9lems) %3e "NC also provides a tool for revie:ing t3e

saved trace messages) %3e directory and file name eamples of t3e trace file are descri9ed asfollo:sH

Iu interface tracing

%3e tracing result is saved to t3e MT installation director1client1output123C1MT

so"tware version num/er1trace directory 9y default) %3e default format of file name is

server name_Iu_year-month-day-hour-minute-second.tmf .

2009-05-06 ua:ei Confidential Page !' o" #$




"NC connection performance

%3e monitoring result is saved to t3e MT installation

director1adaptor1clientadaptor123C1MT so"tware version

num/er1output1realmonitor directory 9y default) %3e default format of t3e file name is

connection performance monitoring_ X

_year-month-day-hour-minute-second_IMSI-IMSI value0 in :3ic3 7 indicates t3e corresponding inde name of connection performance0

suc3 as cell SNR and RSCP )

1.* RC , /cript%3e "!N(*)*@*=( and later versions differentiate customiAed parameters and non-customiAed

parameters) %3e list of customer parameters can 9e do:nloaded directly from3ttpHsupport)3ua:ei)com , and t3e complete scripts can 9e output 9y running t3e 45P

I3342C)GMM command)

%3e MML system saves t3e result to t3e MT installation director16M1)TP directory of t3e@!M server 9y default) %3e default format of t3e file name is C!MM"#time.t$t 0 suc3 as

C)GMM-%#'(%&%'.t7t)

1.+ RC C$R ,ogs

%3e C" logs are 3istory records of calls t3at are saved automatically 9y t3e "NC in t3e "NC$.**"**/ and later versions) %3e C" logs can 9e c3ec>ed t3roug3 t3e Nastar0 Insig3t plus0 and

#M2tar tools) %3e result is saved to t3e MT installation director16M1oad8ata1)amog)mt

directory of t3e @!M server 9y default) %3e default format of t3e file name is frame num%er of the

RNC#"og#start time_end time.log.%&'0 suc3 as $og%*!%(!#9%*!%(%$'*!!.log./:%)

1.1 RC (ra4c /tatistics ile%3e "NC traffic statistics file is saved regularly 9y t3e "NC) Usually0 one file is saved every 3alf an3our) %3e result is saved to t3e MT installation director16M1)TP1Meas2esult directory of t3e

@!M server 9y default) %3e default file name is similar to %(%!'.;#-

!;#94M<-3=2M.mr"./:% )

1.11 5rie) /u!!ary%3is section descri9es common trace tas>s of t3e "NC0 and provides common data saving pat3s for

net:or> optimiAation engineers)

For 3o: to register t3e "NC and Node@ traffic statistics tas>s and to o9tain traffic statistics files on

t3e M.***0 refer to relevant sections of t3e !uide to (perations in )-*+uipment Room)

2009-05-06 ua:ei Confidential Page !( o" #$

http://support.huawei.com/





2 Analyzing eighbor Cell

Proble!s

2.1 %verviewIn UM%2 net:or>s0 good neig39or cell relations3ip is an important prere4uisite for net:or> KPIs)

@ecause t3e neig39or cell relations3ip of UM%2 net:or>s is complicated and t3e current

optimiAation tools are not good enoug30 3o: to rapidly and effectively optimiAe neig39or cells 3as 9ecome t3e 9iggest pro9lem faced 9y t3e on-site engineers) @ased on t3e summary of ua:ei

eperience in eisting commercial net:or>s and current tools0 t3is section introduces t3e currently

availa9le and effective solution to neig39or cell optimiAation to t3e on-site engineers)

%3is solution is mainly used for neig39or cell optimiAation after net:or> s:ap or in t3e maintenance

period) 2ome traffic eists in t3ese net:or>s0 and t3e data necessary for neig39or cell optimiAationcan 9e o9tained from t3e net:or> side +mainly t3e "NC,) %3is solution does not involve creation ofneig39or cell data in ne: net:or>s or s:apped net:or>s or optimiAation of neig39or cells during "F

optimiAation of ne: net:or>s) o:ever0 t3e optimiAation principles0 ideas0 met3ods of t3is solution

can serve as reference for creation of neig39or cell data in ne: net:or>s and s:apped net:or>s and

optimiAation of neig39or cells at t3e preliminary stage of "F optimiAation in ne: net:or>s)

For creation of neig39or cell data in ne: net:or>s and s:apped net:or>s0 refer to t3e

latest version of t3e Guide to Planning and esigning W-"adio Net:or>s released at

3ttpHsupport)3ua:ei)com)

For optimiAation of neig39or cells in ne: net:or>s at t3e preliminary stage of "F

optimiAation0 refer to t3e latest version of t3e Guide to #ptimiAing W-"F released at

3ttpHsupport)3ua:ei)com)

2.2 Principles )or /etting eighbor Cells

#verall principles for setting neig39or cellsH

For net:or>s t3at do not use t3e neig39or cell com9ination algorit3m0 configure as many

neig39or cells as possi9le +no more t3an '(, to ensure t3at no neig39or cell is missed in t3e

measurement control message)

For net:or>s t3at use t3e neig39or cell com9ination algorit3m0 do not configure too many

neig39or cells to ensure t3e gain of t3e neig39or cell com9ination algorit3m and to reduce

2009-05-06 ua:ei Confidential Page !* o" #$










t3e compleity of neig39or cell configuration) %3e proper num9er is (<-.* +considering t3emature eperience of t3e radio net:or> optimiAation,)

For neig39or cell configuration in ne: net:or>s0 if t3e neig39or cell com9ination algorit3m

is used0 do not configure t3e priority of neig39or cells at t3e preliminary stage) 2et and

optimiAe t3e priority of neig39or cells according to t3e traffic statistics or PC" after t3enet:or> traffic reac3es a certain scale)

2.3 Process o) %pti!ization eighbor Cells%3e optimiAation of neig39or cells consists of t3e follo:ingH

Configuration of initial neig39or cells

#ptimiAation of incorrectly configured neig39or cells

#ptimiAation of unnecessary neig39or cells

#ptimiAation of missing neig39or cells #ptimiAation of t3e priority of neig39or cells

In addition0 t3ere are intra-fre4uency neig39or cell optimiAation0 inter-fre4uency neig39or celloptimiAation0 and inter-system neig39or cell optimiAation) Unless epressly indicated in t3is c3apter0

neig39or cell optimiAation refers to intra-fre4uency neig39or cell optimiAation) Mean:3ile0 t3e

principles0 ideas0 and met3ods of intra-fre4uency neig39or cell optimiAation can also 9e used ininter-fre4uency neig39or cell optimiAation and inter-system neig39or cell optimiAation)

2.# Con6guration o) 7nitial eighbor Cells

uring t3e setting of initial neig39or cells0 t3e parameters are set mainly t3roug3 t3e CMB soft:are

+2oft:are $ersion 2oft:are Wireless Product Line WCM!-"!N WCM!-"!N

Pu9lic W"!N CMB at 3ttpHsupport)3ua:ei)com,) For operations of t3e CMB soft:are0 refer to

t3e CM* ser Manual released toget3er :it3 t3e CMB soft:are)

%3e input parameters consist of t3e "NC configuration script +7ML, of living net:or>s0 WCM!

cell list +incremental part,0 G2M cell list0 WCM! neig39or cell relations3ip list0 and G2Mneig39or cell list)

Wit3 t3e preceding input parameters0 t3e automatically added scripts of t3e WCM! and G2M

neig39or cells of t3e ne: or s:apped WCM! cell +including t3e added scripts of t3e N"NC andG2M cells, can 9e output t3roug3 t3e CMB soft:are)

%3e configuration procedure is as follo:sH

Prepare t3e data0 :3ic3 consists of t3e @CP files configured 9y t3e "NC +t3e

CM4C"g<nc>iew.:ip file can 9e eported t3roug3 t3e 45P C)G8T command of

t3e M.***) %3e directory is MT installation

director?6M?>ersion?)TP?47portCM4<nc>iew? on t3e server,0 early neig39orcell planning lists including t3e list of s:apped or ne: WCM! cells0 intra-fre4uency

neig39or cell relations3ip list0 inter-fre4uency neig39or cell relations3ip list0 neig39or

"NC cell list +for migrating t3e net:or>s of competitors,0 G2M cell parameter list0 and

G2M cell relations3ip list) Generally0 t3e WCM! cell list and intra-fre4uency neig39or cell relations3ip list must 9e imported0 and t3e ot3er lists can 9e reported as re4uired)

Import t3e "NC @CP file to t3e CMB soft:are +%ools J 2ync3roniAe :it3 @CP File,)

Bnsure t3at t3e CMB soft:are contains t3e "NC data of t3e eisting net:or>)

2009-05-06 ua:ei Confidential Page !# o" #$







Import t3e prepared neig39or cell planning data list as re4uired)

2elect t3e I of t3e WCM! cell to 9e s:apped or created in t3e CMB0 and confirm t3e

default configurations and configuration principles of relevant parameters in t3e

neig39or cell configuration script)

%3e CMB soft:are automatically outputs t3e WCM! and G2M neig39or cellrelations3ip scripts to 9e added)

2.& Analyzing 7ncorrectly Con6gured eighborCells Proble!s

Configuring intra-fre4uency neig39or cells incorrectly is a pro9lem fre4uently encountered on-site0:3ic3 3as great influence on net:or> performance) %3e most common pro9lem is a large amount of

Call drop) %3e on-site engineers mainly depend on drive tests and signal tracing to find and locate

t3ese pro9lems0 :3ic3 results in complicated solutions and lo: efficiency) In fact0 t3ere is a la: for

incorrect configuration of intra-fre4uency neig39or cells as :ell as for t3e cause) %3e net:or>optimiAation engineers can 4uic>ly find and locate pro9lems t3roug3 t3e eisting system information

9y adding a fe: traffic statistics points and analyAing t3e C" 9ased on designated rules)

%3e first cause of incorrect configuration of neig39or cells is inaccurate engineering parameter)In t3e

missing neig39or analysis0Nastar give t3e suggestion of adding unnecessary neig39or cells)%3e

second one is incorrectly configured neig39or cells) Bngineer adds t3e neig39or cell :it3 t3e samescram9le 9ut different cell I cursorily)

%3e symptom of incorrect configuration of intar- fre4uency neig39or cells is t3at0 at soft 3andover0

after sending a command to update t3e active set0 t3e "NC can receive a !ctive 2et UpdateComplete message09ut t3e "L "estore message cannot 9e received and call drop occurs caused 9y

intar- fre4uency interfere) @ecause t3e scram9le is correct 9ut t3e ne: cell cannot 9e sync3roniAed

@ased on t3e a9ove disciplinarian0 Call drop information and information a9out t3e last 3andover

9efore call drop are recorded in performance server solution) 6ou can analyAe t3e last 3andover

9efore call drop in t3e Nastar according to t3e preceding la:s) If t3e analysis result is t3e same as t3e preceding situation0 you can ta>e t3e t:o cells :3ic3 3andover 9efore call drop as t3e o9Dects to 9e

c3ec>ed) %3en0Nastar can analyAe :3et3er t3e intra-fre4uency neig39or cells of t3e ot3er neig39or

cells of t3e current cell contains incorrectly configured cells0 and :3et3er t3ere are ot3er cells :it3

t3e same scram9ler to c3ec> t3e reasona9leness of neig39or cells and find out t3e correct intra-fre4uency neig39or cell relations3ip)

2.' Analyzing 8nnecessary eighbor CellsProble!s

!s a net:or> is s:apped0 epanded0 or created0 t3e intra-fre4uency neig39or cell relations3ipc3anges constantly) %3erefore0 unnecessary neig39or cell relations3ips or full neig39or cell

relations3ips occur fre4uently) In t3is case0 part of t3e intra-fre4uency neig39or cells needs 9e

deleted)

%3e intra-fre4uency neig39or cells need to 9e deleted according to t3e counted num9er of soft

3andovers 9et:een t:o cells) %3erefore0 t3e cells and soft 3andover measurement inde s3ould 9e

registered on t3e M.***) %3e "NC reports t3e num9er of soft 3andovers 9et:een t:o cells and dailytraffic statistic files to t3e M.***)

2009-05-06 ua:ei Confidential Page !+ o" #$




Import t3e Nastar engineering parameter list0 "NC MML script to 9e c3ec>ed0 and traffic statisticsrecording t3e preceding measurement 9et:een t:o cells into t3e Nastar +it is 9etter to record data for

no less t3an a :ee>,0 and use t3e Intra-fre+uency nnecessary Neigh%or nalysis function of t3e

Nastar for analysis0 as s3o:n in Figure ()()

)igure !.! Intra-fre4uency unnecessary neig39or analysis

Keep t3e output result as Bcel format0 select t3e cells :it3 over .< neig39or cells0 arrange t3e

neig39or cells of eac3 cell in descending order of t3e num9er of 3andovers 9et:een t:o cells0 andcalculate t3e cumulative pro9a9ility) elete t3e cells compliant :it3 t3e follo:ing conditionsH

%3e num9er of soft 3andovers 9et:een t:o cells is Aero or t3e cumulative pro9a9ility is

greater t3an /&)

%3e t:o cells are not t3e intra-fre4uency neig39or cells on t3e first layer)

!fter deletion0 o9serve t3e call drop of t3e cells :3ose neig39or cells are deleted) If t3e num9er ofcall drops increases and t3e call drop ratio increases significantly0 recover t3e deleted neig39or cells0

and delete ot3er neig39or cells) #t3er:ise0 do not recover t3e deleted neig39or cells)

2." Analyzing issing eighbor Cells Proble!s%3e non-first-layer intra-fre4uency missing neig39or cells s3ould 9e analyAed according to t3e

strengt3 of signals of t3e active set and detection set recorded in t3e C" data) @esides t3e Nastar

engineering parameter list and "NC MML script to 9e c3ec>ed0 t3e C" data +it is 9etter to 9e over

a :ee>, also needs to 9e imported to t3e Nastar0 and t3en t3e Intra-re+uency Missing Neigh%or nalysis function of t3e Nastar s3ould 9e used to ma>e analysis0 as s3o:n in follo:ing Figure)

)igure !.! Intra-Fre4uency Missing Neig39our !nalysis

!dd neig39or cells or c3ec> :3et3er it is necessary to add some neig39or cells according to t3e

output suggestions +!dding Neig39or or %o @e etermined,0 as s3o:n in Figure ().)

2009-05-06 ua:ei Confidential Page % o" #$




)igure !.% Missing neig39or analysis list

2elect a ro: in Figure ().0 and clic> + ra/ Neigh%or Cells on Map, in t3e upper left corner) %3e

analysis result corresponding to t3e ro: is displayed in t3e form of a map0 as s3o:n in follo:ingFigure)

)igure !.$ ra: Neig39or Cells on Map

In Figure .-;0 t3e 9lue cell is t3e source cell0 and t3e green and red cells are configured and missing

intra-fre4uency neig39or cells respectively) Note t3at t3e Nastar gives suggestions 9ased on t3e

missing scores) !ccording to net:or> optimiAation eperience0 corresponding neig39or cells s3ould 9e added for t3e dding Neigh%or or 0o 1e etermined suggestion)

2009-05-06 ua:ei Confidential Page %! o" #$




2.* %pti!izing the Priority o) eighbor Cells

For net:or>s ena9led :it3 t3e neig39or cell com9ination function0 t3e priority of neig39or cellss3ould 9e set and optimiAed) Improper setting of t3e priority of neig39or cells causes lo: efficiency

of t3e neig39or cell com9ination algorit3m) %3e follo:ing descri9es 3o: to optimiAe t3e priority ofintra-fre4uency neig39or cells 9ased on traffic statistics data)

Principle for optimiAing t3e priority of intra-fre4uency neig39or cellsH ena9le t3e 3andover

measurement s:itc3 9et:een t:o cells on t3e M.***0 collect statistics on t3e num9er of attempts at

soft 3andover 9et:een t:o cells +$2)2#)!tt!2U)N,0 and optimiAe t3e priority of t3e configuredneig39or cells in descending order of t3e num9er)

%3e Intra-fre+uency nnecessary Neigh%or nalysis function of t3e Nastar can 9e used to output t3ese4uence list of t3e num9er of attempts +$2)2#)!tt!2U)N, at soft 3andover 9et:een t:o cells0

and adDust t3e priority of neig39or cells according to t3e se4uence of neig39or cells in t3is list)

Note t3at enoug3 traffic is t3e prere4uisite for optimiAation of t3e priority of neig39or cells 9ased on

traffic statistics) #t3er:ise0 t3e result is incredi9le) !fter collecting statistics for a period0 t3e opened

3andover measurement s:itc3 9et:een t:o cells must 9e disa9led) #t3er:ise0 it affects t3e "NC

performance)

2.+ Checing %ne09ay eighbor CellIn t3e optimiAation of neig39or cells0 if t3e neig39or cell relations3ip of one direction is added only

according to t3e first-layer neig39or relations3ip or t3e num9er of 3andovers and 3andover

pro9a9ility0t3at corresponding reverse neig39or cell relations3ips are missed fre4uently) %3erefore0

t3e one-:ay neig39or cells need 9e c3ec>ed and t3e missing neig39or cells need to 9e added)

%3e Nastar can 9e used in specific operations) Import t3e "NC MML script to 9e c3ec>ed into t3e Nastar0 and ma>e analysis 9y using t3e (ne-/ay Neigh%or Chec2 function of t3e Nastar0 as s3o:n inFigure ()()

)igure !.! #ne-:ay neig39or c3ec>

!ccording to t3e analysis result0 add t3e missing reverse neig39or cells after confirmation +in some

cases0 one-:ay neig39or cells need to 9e configured for special 3andover policies,)

2.1 %pti!izing 7nter0re:uency eighborCells

For optimiAation of inter-fre4uency neig39or cells0 in t3e case of co-siting inter-fre4uency cells0 t3e

inter-fre4uency cell nearest to t3e antenna aAimut3 of t3is cell and all t3e intra-fre4uency neig39or

2009-05-06 ua:ei Confidential Page %% o" #$




cells of t3is inter-fre4uency cell can 9e regarded as t3e inter-fre4uency neig39or cells of t3is cell)%3e intra-fre4uency neig39or cell relations3ip :it3 t3is inter-fre4uency cell s3ould 9e updated

sync3ronously)

%3e missing inter-fre4uency neig39or cells can 9e optimiAed according to t3e follo:ing principlesH

!dd second-layer inter-fre4uency neig39or cell relations3ips as many as possi9le :it3in

t3e entire net:or> according to t3e same optimiAation met3od as t3at of t3e first-layer

inter-fre4uency neig39or cell relations3ips)

!nalyAe %opN call drop cells) For cells :it3 call drop mainly for "F reasons0 add t3ird-

layer inter-fre4uency neig39or cell relations3ips0 or add necessary neig39or cells 9y

referring to t3e intra-fre4uency neig39or cell relations3ips of near9y inter-fre4uencycells)

2.11 %pti!izing 7nter0/yste! eighbor CellsIn t3e case of co-siting G2M cells0 t3e co-siting G2M cell nearest to t3e antenna aAimut3 of t3is cell

and all t3e G2M neig39or cells of t3is G2M cell can 9e regarded as neig39or cells of t3is cell) !ll

neig39or cell relations3ips :it3 t3is cell s3ould 9e updated sync3ronously)

o as follo:s to optimiAe missing inter-system neig39or cellsH

Convert t3e general engineering parameter lists of WCM! and G2M to different

Mapinfo layers t3roug3 t3e Mapinfo plug-in unit)

Mar> t3e sector aAimut3 c3arts of WCM! and G2M on t3e Mapinfo layer :it3

different colors) 1udge :3ic3 G2M cells are first-layer inter-system neig39or cells of t3is

cell according to t3ese c3arts)

Compare t3e neig39or cell relations3ips configured in eisting net:or>s to Dudge

:3et3er t3ere are missing G2M cells) If yes0 configure t3em)

2.12 /u!!ary

%3is section introduces t3e feasi9le and efficient solutions for optimiAing neig39or cells to t3e on-

site engineers 9ased on t3e eperience of eisting ua:ei commercial net:or>s and current tools)

2009-05-06 ua:ei Confidential Page %$ o" #$




3 Analyzing Accessing Proble!s

3.1 %verview%3is document aims to meet t3e re4uirements on solving access pro9lems 9y on-site engineers during "N#)

It details t3e met3ods for evaluating net:or> access performance0 test met3ods0 data analysis met3ods0

F!5s0 and solutions) %3e appendi provides t3e fundamental >no:ledge a9out access pro9lems0 description

of principles0 related parameters0 and data processing tools) It guides engineers to locate and solve access

pro9lems during optimiAing net:or> KPI indees and net:or> #M)

3.2 De6nition o) Access ailureIf a service fails to 9e setup0 t3is is an access failure) In %0 t3e common access failure pro9lems include t3e

follo:ing typesH

$oice call failure

$P call failure

PP activation failure

!ccording to t3e preset Dudgment conditions0 t3e % data analyAers can usually Dudge t3e access failure

pro9lems during test) %3e analyAers include GBNB7 !ssistant and !cti !nalyAer)

3.2.1 De6nition o) Call ailure by ;<<=Assistant

#riginated Call Failure in C2 omainH

Bvent definitionH t3e UB sends a ""C "B5UB2% message) W3erein0 t3e IB esta/lish cause is #riginating

Conversational Call :it3out reception of t3e direct transfer message alerting)

%3e follo:ing events are defined according to t3e stages of failure)

2009-05-06 ua:ei Confidential Page %& o" #$




""C connection setup failureH out of t3e consideration of retransmission times and :aiting

time0 t3e UB fails to receive t3e response from "NC or receives t3e ""C C#NNBC%I#N

"B1BC% message after sending t3e ""C C#NNBC%I#N "B5UB2% message)

Initial direct transfer and security mode setup failureH after t3e UB sends t3e ""C

C#NNBC%I#N 2B%UP C#MPLB%B message0 it fails to send t3e N!2 2B%UP message)

"!@ assignment failureH after t3e UB receives t3e C!LL P"#CBBING message0 it fails

receive t3e "@ 2B%UP message from "NC) #r t3e UB responds "@ 2B%UP F!IL message

after receiving t3e "@ 2B%UP message) #r t3e UB receives t3e I2C#NNBC%I#N message:it3 t3e cause normal release after receiving t3e "@ 2B%UP message0 :3en t3e UB does

not send t3e "@ 2B%UP CMP message)

%3e failure after "!@ assignmentH after t3e UB sends t3e "@ 2B%UP C#MPLB%B messageH

%3e originated UB receives t3e I2C#NNBC%"BLB!2B message from CN

%3e originated UB :aits for t3e C#NNBC% or !LB"%ING message until epiration0 so t3e

call clearing process is originated) !ccording to t3e protocols0 after t3e UB sends t3e CM

2B"$ICB "B5UB2% message0 t3e timer %'*' starts) If t3e UB fails to receive t3eC!LLP"#CBBING0 !LB"%ING0 C#NNBC%0 #" "BLB!2B C#MPLB%B message

9efore epiration of %'*'0 t3e clearing process starts)

@efore receiving alerting message0 t3e UB enters t3e idle state and starts to receive system

information)

!s strictly defined0 after t3e M2 enters t3e CBLLC state and 9efore it receives t3e alerting message0 it must send t3e cell update message :it3 t3e cause 2C unrecovera/le error? 2adio lin@

"ailure)

%a>e t3e greater value of t3e maimum :aiting time configured at "LC layer as default and t3e

sync3roniAation time as t3e Dudgment time) It is unclear t3at t3e UB can report t3e "LC layer message0

so t3e maimum :aiting time is neglected)

%erminated Call Failure in C2 omainH

%3e terminated UB receives t3e paging of type (0 9ut it does not send t3e ""C C#NNBC%I#N

"B5UB2% message :it3 t3e cause Terminating Conversational Call or does not send t3e direct

transfer message alerting to CN)

etailed failure stages includeH

""C connection setup failure

!fter t3e UB sends t3e ""C C#NNBC%I#N "B5UB2% message0 it fails to receive

reply from "NC or receives t3e ""C C#NNBC%I#N "B1BC% message from "NC)

Initial direct transfer and security mode setup failure

!fter t3e UB sends t3e ""C C#NNBC%I#N 2B%UP C#MPLB%B message0 it fails to

receive t3e 2B%UP direct transfer message0 it sends t3e "BLB!2B C#MPLB%B

message0 or t3e UB receives t3e I2C#NNBC% message from CN)

"!@ assignment failure

!fter t3e UB sends t3e C!LL C#NFI"M message0 it fails to receive t3e "@ 2B%UP

message from "NC) #r after it receives t3e "@ 2B%UP message0 it replies "@ 2B%UP

F!IL message) #r after it receives t3e "@ 2B%UP message0 it receives t3e

2009-05-06 ua:ei Confidential Page %' o" #$




I2C#NNBC% message not due to normal release cause0 :3en t3e UB 3as not sendst3e "@ 2B%UP CMP message)

Failure after completion of "!@ assignment

!fter t3e UB sends t3e "@ 2B%UP C#MPLB%B message0 t3e called UB receives t3eI2C#NNBC%"BLB!2B message from CN)

3.2.2 De6nition o) Access ailure by Acti>Analyzer

%3e !cti !nalyAer defines access failure according to t3e follo:ing principlesH after t3e originated

UB sends t3e ""C Connection "e4uest message0 access failure occurs upon any of t3e follo:ing

conditionsH

%3e UB receives t3e ""C Connection "eDect message

It sends or receives t3e ""C Connection "elease message after receiving ""C Connection

setup

It receives any message from @CC during Call setup message

%3e timer epires) Namely0 a period +%'**, after t3e UB sends t3e ""C Connection

"e4uest message0 it fails to receive t3e ""C Connection setup message

3.2.3 De6nition o) Access ailure by (</

%3e %BM2 defines access failure +for originated voice services, according to t3e follo:ing principlesH

"andom access failureH after dialing0 t3e UB fails to send t3e ""C Connection "e4uest

message)

%3e UB fails to receive t3e ""C Connection 2etup messageH after t3e UB send t3e ""C

Connection "e4uest message0 it fails to receive t3e ""C Connection 2etup message)

%3e UB fails to send t3e ""C Connection Complete messageH after t3e UB receive t3e ""C

Connection "e4uest message0 it fails to send t3e ""C Connection 2etup message)

%3e UB receives t3e ""C Connection "eDect messageH t3e UB receives t3e ""C Connection

"eDect message0 and does not resend t3e ""C Connection "e4uest message for try)

%3e UB fails to receive t3e measurement control messageH after t3e UB sends t3e ""C

Connection Complete message0 it fails to receive t3e measurement control message)

%3e UB fails to send t3e CM 2ervice "e4uest messageH after t3e UB receives t3e

measurement control message0 it fails to send t3e CM 2ervice "e4uest message)

%3e UB receives t3e 2ervice "e4uest "eDect message)

%3e UB fails to receive t3e Call Proceeding messageH after t3e UB sends t3e CC 2B%UP

message0 it fails to receive t3e Call Proceeding message)

%3e UB fails to receive t3e "@ 2etup messageH after t3e UB receives t3e Call Proceeding

message0 it fails to receive "@ 2etup message)

%3e UB fails to send t3e "@ 2etup Complete messageH after t3e UB receives t3e "@ 2etup

message0 it fails to send t3e "@ 2etup Complete message)

2009-05-06 ua:ei Confidential Page %( o" #$




%3e UB fails to receive t3e !lerting or Connect messageH after t3e UB sends t3e "@ 2etup

Complete message0 it fails to receive t3e!lert or Connect message)

%3e UB fails to receive t3e Connect !c>no:ledge messageH after t3e UB receives t3e

!lerting or Connect message0 it fails to send t3e Connect !c>no:ledge message)

3.3 low and ethods )or Analyzing Accessailure Proble!s

s3o:s t3e overall flo: for analyAing call failure pro9lemsH

)igure !.! Flo: of !nalyAing !ccess Failure Pro9lems

@y % data analyAing tool0 suc3 as !cti !nalyAer and GBNB7 !ssistant0 determine t3e time for

Call )ail and o9tain t3e follo:ing informationH

Pilot information collected 9y scanner 9efore and after Call )ail

Information a9out active set0 monitor set0 and signaling flo: collected 9y UB

Matc3 t3e signaling collected 9y UB and t3e time of single su9scri9er tracing 9y messages)

Mean:3ile locate t3e points :3en pro9lems occur in single su9scri9er tracing on "NC)

@ased on signaling of single su9scri9er tracing on "NC and UBEs signaling flo:0 determine t3e point

:3ere call fails occurs according to flo: of !nalyAing !ccess Failure Pro9lems) !nalyAe and solve

pro9lems according to follo:ing su9-flo:s) %3e pro9lems includeH

Paging pro9lems

""C setup pro9lems

2009-05-06 ua:ei Confidential Page %* o" #$




"!@ and "@ setup pro9lems

!ut3entication and encryption pro9lems

!9normal e4uipment pro9lems

3.# Analyzing Paging Proble!s

Paging pro9lems usually areH t3e originated UB completes "!@ assignment and CC 2etup and :aits for

lerting message0 :3en it receives t3e 8isconnect direct transfer message from CN) Figure ;-. s3o:s t3e

signaling flo: of originated UB in locating paging pro9lems) !ccording to t3e signaling flo: of called UB0

t3e signaling flo: is normal) It occurred t3at after receiving Paging message it does not originate ""C

connection setup re4uest) !ccording to t3e single su9scri9er tracing of called UB on "NC0 t3e "NC receives

t3e Paging message from CN :it3out follo:ing messages)

)igure !.! 2ignaling flo: of originated UB in locating paging pro9lems

%3e causes of paging pro9lems includeH

%3e "NC does not send t3e Paging message)

%3e po:er of paging c3annel and paging indicator c3annel is lo:)

%3e UB reselects a cell)

2009-05-06 ua:ei Confidential Page %# o" #$




3.#.2 ailure in /ending Paging essage byRC

!fter t3e "NC receives t3e paging message from CN0 t3e UU interface does not send t3e message)

Pro9a9ly t3e capacity of paging c3annel is inade4uate +currently t3e net:or> load is lo:0 so it is less

pro9a9le t3at t3e paging c3annel is congested at UU interface) W3en t3e net:or> load is 3eavy0 it is

pro9a9le, or t3e e4uipment is a9normal

3.#.3 %ver ,ow Power o) PC$ or P7C$

!fter t3e "NC sends a paging message0 t3e UB fails to receive it) For t3is pro9lem0 c3ec> t3e BcIo of t3e

cell :3ere t3e UB camps and t3e cell :3ic3 it monitors) If t3e BcIo of 9ot3 cells is lo:er t3an -(. d@0 t3e

po:er of PC or PIC is over lo: or t3e coverage is :ea>))

3.#.# Cell Reselection by 8<

If t3e signals of t3e cell :3ere t3e UB camps are :ea> :3ile t3e signals of monitored cell are strong0 t3e

pro9lem mig3t 9e due to cell reselection) W3en t3e UB 3as its location area +L!, or route area +"!, updated

upon paging0 t3e paging message is sent to t3e original L! or "!0 so t3e UB fails to receive paging message

3.& Analyzing RRC Connection /etup Proble!s%3e ""C connection setup failure can 9e analyAed t3roug3 UB signaling flo: and single su9scri9ertracing on "NC) %3e ""C connection setup process includes t3e follo:ing stepsH

%3e UB sends ""C Connection "e4uest message on "!C)

%3e "NC sends t3e ""C Connection 2etup message on F!C)

!fter t3e UB sets up do:nlin> C and sync3roniAes :it3 it0 it sends t3e ""C Connection

2etup CMP message on uplin> C)

""C setup fails due to t3e follo:ing causesH

Uplin> "!C pro9lems

o:nlin> F!C po:er allocation ratio Cell reselection parameter pro9lems

#ver lo: transmit po:er of do:nlin> C

Uplin> initial po:er control pro9lems

Congestion

!9normal e4uipment pro9lems

!mong previous pro9lems0 t3e uplin> "!C pro9lem0 do:nlin> F!C po:er allocation ratio pro9lem0

cell reselection parameter pro9lem0 and a9normal e4uipment pro9lem are pro9a9le)

s3o:s t3e flo: for analyAing ""C connection setup pro9lem

2009-05-06 ua:ei Confidential Page %+ o" #$




)igure !.! Flo: for analyAing ""C connection setup pro9lem

3.&.1 A)ter 8< /end RRC Connection Re:uestessage? the RC ails to Receive 7t

If t3e BcIo of do:nlin> CPIC is over lo:0 t3e pro9lem is a9out coverage)

If t3e BcIo of do:nlin> CPIC is not over lo: +suc3 as 3ig3er t3an -(; d@,0 t3e pro9lem is a9out

"!C0 :it3 t3e follo:ing causesH

%3e po:er step of pream9le is small

%3e output po:er of UB is lo:er t3an re4uired)

Node@ is pro9lematic :it3 standing :ave)

%3e parameter of cell radius is improperly configured)

3.&.2 A)ter the RC Receives the RRC /etupRe:uest essage )ro! 8<? 7t sends the RRCConnection Re@ect essage

W3en t3e ""C Connection "eDect message is present0 c3ec> t3e cause values0 :3ic3 include

congestion and unspeci"ied)

2009-05-06 ua:ei Confidential Page $ o" #$




If t3e cause value is congestion0 t3e net:or> is congested) C3ec> t3e net:or> load conditions0including utiliAation of po:er0 code0 and CB resources) etermine t3e type of resource t3at causes

congestion and provide :ays of net:or> epansion) For details0 see )-Net/or2 *$pansion !uide)

%3e admission of ""C connection for 2P! su9scri9ers is consistent :it3 t3at for "//

su9scri9ers0 including po:er0 code0 and CB resources) Pay special attention to code admission) If t3ecode :ord of 2P! su9scri9ers is statically assigned0 and ecessive codes are assigned to 2P!su9scri9ers0 t3e ""C connection of 2P!or "// su9scri9ers fails pro9a9ly) %3is is due to t3at t3e

codes of do:nlin> signaling c3annel for 2P! or "// su9scri9ers are inade4uate)

If t3e cause value is unspeci"ied0 c3ec> t3e logs to determine causes of failure)

3.&.3 A)ter the RC Receives the RRC /etupRe:uest essage )ro! 8<? 7t /ends the RRCConnection /etup essage 9hich 7s otReceived by 8<

%3e causes of t3is pro9lem includeH

Wea> coverage

Improper parameters of cell selection and reselection

C3ec> t3e CPIC BcIo) If it is lo:er t3an -(. d@ +t3e default value is configured 9ased on BcIo as

-(. d@, and

If t3ere is no more 4ualified cell listed in t3e monitor set0 t3e pro9lem is a9out coverage)

If t3ere is more 4ualified cell listed in t3e monitor set0 t3e pro9lem is a9out cell reselection)

2olutions are as 9elo:H

W3en t3e coverage is :ea>H

If conditions permit0 solve coverage pro9lems 9y en3ancing coverage0 suc3 as adding

sites to cover 9lind areas and adDusting engineering parameters) If you cannot en3ance

t3e coverage0 you can increase F!C po:er) !dDust F!C po:er according to t3ecoverage conditions of PCPIC BcIo) For eample0 t3e pilot BcIo in all coverage areas

after net:or> optimiAation is larger t3an -(. d@0 t3e success rate for UB to access from

'G idle mode can 9e guaranteed if t3e common c3annel po:er is allocated on t3e

condition of BcIo e4ual to -(. d@) W3en BcIo is smaller t3an -(; d@0 t3e UB reselectsa G2M cell) %3e success rate of ""C setup in :ea> coverage areas after inter-"!%

reselection 9y UB can 9e guaranteed if t3e common po:er is allocated on t3e condition

of BcIo larger t3an -(; d@)

Cell selection and reselectionH

!dDusting cell selection and reselection parameters accelerates cell selection and

reselection and 3elps solve ""C connection setup failure pro9lems caused 9y improper

parameters of cell selection and reselection)

%3e ""C C#NNBC%I#N 2B%UP message is carried 9y F!C) !fter t3e U%"!N side receives t3e

P"!C pream9le0 t3e UB sends t3e ""C C#NNBC%I#N "B5UB2% message on "!C 9ased oncurrent pream9le po:er) %3e pream9le transmit po:er >eeps increasing until response is received

+restricted 9y maimum retransmission times of pream9le,) %3erefore0 in poor coverage areas0

un9alanced coverage 9y "!C and F!C is pro9a9le) Conse4uently t3e U%"!N side can receive t3e

""C C#NNBC%I#N "B5UB2% message :3ile t3e UB fails to receive t3e ""C C#NNBC%I#N

2B%UP message)

2009-05-06 ua:ei Confidential Page $! o" #$




3.&.# A)ter Receiving RRC Connection /etupessage? the 8< Does ot /end /etupCo!plete essage

If t3e do:nlin> signals are normal0 t3e UB mig3t 9e a9normal) #t3er:ise initial po:er of do:nlin>

C is over lo: so t3e do:nlin> cannot sync3roniAe) 6ou can solve t3e pro9lem 9y adDustinguplin> B9No of t3e service)

3.&.& A)ter the 8< /ends the RRC /etupCo!plete essage? the RC ails to Receive 7t

It seldom occurs 9ecause uplin> initial po:er control leads to increment of UB transmit po:er) Upon

presence of t3e pro9lems0 you can properly raise t3e Constant >alue of C so t3at t3e initial

transmit po:er of uplin> PCC of UB increases)

%3is pro9lem is related to :3et3er t3e initial target value of uplin> 2I" is rational and 3as great

impact on uplin> initial sync3roniAation at t3e 9eginning of lin> setup)

If it is set over large0 t3e uplin> interference from initial lin> setup of su9scri9er 9ecomes

over large)

If it is set over small0 t3e uplin> sync3roniAation time increases0 and conse4uently t3e initial

sync3roniAation fails)

%3is parameter is an "NC-level parameter) It 3as great impact on net:or> performance0 so engineers

must 9e cautious upon adDustment)

%3e ""C Connection 2etup Complete message is sent on uplin> PC) %3e UB calculates t3e initial

po:er of PCC according to received IB PCCPo:eroffest and measured CPIC"2CP)PCCInitialpo:er PCCPo:eroffset - CPIC"2CP

W3erein0 PCCInitialpo:er Primary CPIC L %7 Po:er O UL Interference O Constant $alue

Constant >alue can 9e configured at #MC) If it is set over small0 t3e UB 3as lo:er po:er to send

t3e ""C C#NNBC%I#N 2B%UP C#MPLB%B message t3an re4uired) Current default configuration

of Constant >alue +t3e default value of it in version $('C*'@(<( is .*, usually prevents t3is pro9lem from 3appening)

3.' Analyzing Authentication Proble!sW3en aut3entication fails0 analyAe t3e pro9lem according to t3e cause value provided in t3e aut3entication

failure message replied from UB to t3e net:or>) %:o common cause values include MC )ailure and

<sch )ailure.

3.'.1 AC ailure

C3ec> t3e !U%N parameter in t3e aut3entication re4uest message send 9y net:or> side upon t3e

aut3entication of net:or> 9y UB) If t3e MC information is incorrect0 t3e UB send t3e aut3entication failure

message :it3 t3e cause value MC "ailure：

2009-05-06 ua:ei Confidential Page $% o" #$




)igure !.! !ut3entication failure due to M!C Failure

%3e maDor causes of t3e pro9lem includeH

Unaut3oriAed su9scri9er

U2IM and L" set different Ki and #P +#Pc, for t3e su9scri9er

%3is pro9lem occurs fre4uently :3en a su9scri9er uses a ne: U2IM) %o locate t3is pro9lem0 c3ec> :3et3er t3e Ki and #P +#Pc, value of t3e IM2I are t3e same) %3e U2IM

3as default Ki and #P +#Pc,0 9ut t3e U2IM reader fails to o9tain t3e value) %3erefore0 t3eKi and #P +#Pc, of t3e U2IM must 9e >no:n upon defining a su9scri9er or t3e Ki and #P+#Pc, of U2IM must 9e made t3e same value as in L"

3.'.2 /ync ailure

W3en t3e UB detects t3at t3e 25N of !U%N message is incorrect0 so t3e aut3entication fails) %3e cause

value is <nch "ailure +sync3roniAation failure,：

)igure !.! !ut3entication failure due to 2ync3 Failure

2009-05-06 ua:ei Confidential Page $$ o" #$




%3e causes of t3e pro9lem includeH

!ut3oriAed su9scri9ers

B4uipment pro9lems

3." Analyzing /ecurity ode Proble!suring t3e security mode control process0 t3e net:or> side sends encrypted information to radio access

net:or> +"!N,) uring t3e process0 t3e CN side and "!N negotiate to perform encryption algorit3m on UB

so t3at t3e UB uses t3e encryption algorit3m in t3e su9se4uent transfers) !fter t3e UB performs 3andover0 it

can use t3e encryption algorit3m as possi9le) Namely0 t3e encryption-related parameters are sent to t3e target

"NC

23o:s t3e security mode control：

)igure !.! 2ecurity mode control

23o:s t3e 2ecurity Mode "eDect)：

)igure !.% 2ecurity mode reDect

%3e common causes of security mode reDect includeH

%3e UB is una9le to support configured encryption algorit3m)

%3e encryption model configuration of "NC does not matc3 t3at of CN) For eample0 t3e M2C

configures t3e encryption algorit3m UB!* only 9ut t3e "NC configures UB!( only 。

2009-05-06 ua:ei Confidential Page $& o" #$




3.* Analyzing PDP Activation ailure Proble!s

%3e reason of PP activation failure is t3at :3en UB send !ctivate PP Contet "e4uest0Dust receive

!ctivate PP Contet "eDect)Pro9lems include t:o >indHCore Net:or> Pro9lem or Incorrect 2etting #f "ate

Limit or !PN on UB side)

3.+ Analyzing RA5 or R5 /etup Proble!sW3en t3e "!@ or "@ setup fails0 t3e "NC responds "!@ assignment setup failure in t3e "!@ !ssignment

"esponse message) Locate t3e specific failure causes t3roug3 t3e failure cause value contained in t3e related

cells)

Common "!@"@ setup failure pro9lems includeH

%3e "NC directly reDects "!@ setup re4uest due to incorrect parameter configuration)

!dmission reDection

"!@ setup fails due to response of "@ setup failure from UB

"!@ setup fails due to "@ setup failure at air interface

3.+.1 Direct Re@ection o) RA5 /etup Re:uest byRC Due to 7ncorrect Para!eter Con6guration

It seldom occurs t3at t3e "NC directly reDects "!@ setup re4uest due to incorrect parameter configuration)

%3is occurs due to special operations 9y special su9scri9ers) It occurs :3en t3e "NC directly reDects "!@

setup re4uest 9ecause su9scri9ing information for P2 service in L" eceeds t3e UB capa9ility)

For eample0 t3e traffic for a special su9scri9er is '&;K in uplin> and do:nlin>0 9ut t3e maimum uplin>

capacity is =;K) %3e su9scri9er sets t3e uplin> and do:nlin> maimum rate in 5o2 of activation PP to

'&;K 9y using t3e !% command and UB soft:are +2ony-Bricsson UB soft:are can set 5o2 of activation

re4uest,) W3en t3e "NC receives t3e "!@ assignment re4uest0 it finds t3at t3e re4uested uplin> maimum

rate eceeds t3e UB capa9ility0 so it directly responds "!@ setup failure :it3out originating "@ setup)

!fter t3e "!@ setup fails due to incorrect parameter configuration t3at eceeds UB capa9ility0 t3e 2G2N

:ill renegotiate to originate ne: "!@ assignment until t3e UB can support and t3e system completes "!@

assignment) For su9scri9ers0 t3e PP activation can still 9e successful and t3e maimum rate o9tained from

indicator is t3e maimum rate supported 9y UB) If t3e minimum guaranteed rate re4uested in 5o2 setup in

PP activation re4uest 9y UB eceeds UB capacity0 t3e net:or> accepts t3e PP activation re4uest 9y UB at

a negotiated lo: rateQ 3o:ever0 :3en t3e negotiated rate of net:or> in t3e PP activation acceptance

message0 t3e UB originates deactivation PP re4uest) %3erefore0 PP activation fails finally)

2009-05-06 ua:ei Confidential Page $' o" #$




3.+.2 Ad!ission Re@ection

For non-2P! su9scri9ers0 :3en t3e system resource +po:er0 code0 c3annel code0 Iu9 transmission

resource0 and Credit, is inade4uate0 t3e admission is reDected and conse4uently call setup fails) No: you

must c3ec> t3e uplin> and do:nlin> load0 code resource0 Iu9 transmission resource0 and CB resource0

determine t3e type of resource t3at causes congestion0 and provide corresponding epansion met3ods)

W3en ecessive codes are statically assigned to 2P! su9scri9ers0 t3e admission fails due to inade4uate

do:nlin> c3annel code resource for non-2P! su9scri9ers) W3en t3e system resource is inade4uate and

admission fails0 t3e $()< or 3ig3er "NC conducts different operations according to "!@ o:nsiAing 2:itc3

state) For details0 see t3e description of solving inade4uate lu9 9and:idt3

If t3e 9and:idt3 of t3e lu9 interface is inade4uate0 activation of "// 3ig3-speed data services fails due to

t3e limited 9and:idt3) For eample0 t3e !!L. 9and:idt3 for service on lu9 interfaces in many cells can

support only a '&; K9ps service) If a (.). K9ps voice service already eists0 t3e lu9 interface fails to provide

enoug3 9and:idt3 for a '&; K9ps P2 service) In t3e case of "NC $()'0 t3e "NC returns an 2G2N "!@

assignment failure 9ecause t3e re4uested rate is unavaila9le) %3e 2G2N t3en originates "!@ assignment

t3roug3 re-negotiation) In t3e case of "NC $()< or later versions0 t3e "NC lo:ers t3e rate first if t3e "!@

o:nsiAing s:itc3 is on) If t3e lu9 resource is availa9le after t3e rate is do:n0 t3e "NC sends a "!@

assignment success message to t3e 2G2N) If t3e lu9 resource is not availa9le even t3oug3 t3e rate is do:n to

& K9ps0 t3e "NC returns an 2G2N "!@ assignment failure) %3e 2G2N t3en decides :3et3er or not to

originate renegotiation 9ased on its internal parameters) If t3e "!@ o:nsiAing 2:itc3 is off0 t3e processing

is t3e same as t3at in t3e case of "NC()'

%3e admission control of Node@ Credit resources is similar to t3e po:er admission control) W3et3er t3e

availa9le Credit can support t3e currently re4uested service depends on t3e spreading factor of t3e ne:

su9scri9er) If t3e current Credit is not ade4uate0 t3e "NC performs different processing depending on state of

t3e "!@ o:nsiAing s:itc3 in t3e case of "NC $()< or later versions) For details0 see t3e 3andling in t3e

case of inade4uate 9and:idt3 of t3e lu9 interface as descri9ed earlier in t3is document)

For t3e admission reDection of 2P! su9scri9ers0 consider t3e follo:ing aspectsH

In t3e met3od for statically assigning po:er of 2P! and "// su9scri9ers0 considerH

R 2P! su9scri9ers supported 9y Node@

R 2P! su9scri9ers supported 9y cell

R %otal 9it rate of cell

R %otal guaranteed 9it rate

R W3et3er t3e cell transmit po:er guaranteed 9it rate eceeds t3e prescri9ed t3res3old

In t3e met3od for dynamically assigning po:er of 2P! and "// su9scri9ers0 considerH

R 2P! su9scri9ers supported 9y Node@

R 2P! su9scri9ers supported 9y cell

R W3et3er t3e guaranteed 9it rate eceeds t3e prescri9ed t3res3old

2009-05-06 ua:ei Confidential Page $( o" #$




For 2P! su9scri9ers0 :3en t3e configured 9and:idt3 at lu9 interface is inade4uate0 admission reDection

:ill not occur0 9ut t3e rate 9ecome lo:er) In addition0 t3e !!L.P!% of 2P! and "// is respectively

configured0 and 2P! !!L.P!% must 9e configured to 2P! "% or 2P! N"% type) If t3e 2P!

!!L.P!% is configured to "// !!L.P!% "% or N"% type0 "!@ assignment :ill not fail0 9ut t3e "NC:ill directly set up 2P! service to "// '&;>9ps)

strategies of t3e ""M admission algorit3m c3ange as follo:sH

o:nlin> po:er admission control for 2P! cells is supported) #nly dynamic po:er

assignment is availa9le)

For t3e C service0 consider :3et3er load of t3e non-2P! service +t3e "// service,

eceeds t3e admission t3res3old of t3e non-2P! service +t3at is0 t3e admission t3res3oldof t3e original "// service,) In addition0 consider :3et3er t3e non-2P! po:er and t3e

2P! G@P +Po:er to meet G@", eceed t3e t3res3old of total po:er of t3e cell) For t3e 2P! service0 c3ec> :3et3er t3e 2P! t3roug3put provided 9y t3e cell eceeds

t3e t3res3old of sum of Guaranteed @it "ates +G@", of all su9scri9ers0 or :3et3er t3e G@P

of stream services and 9ac>ground services eceeds t3e 2P! po:er of t3e cell) In

addition0 consider :3et3er t3e non-2P! po:er and t3e 2P! G@P eceed t3e

t3res3old of total po:er of t3e cell)

lu9 interface admissionH

For t3e C service0 t3e admission depends on t3e pea> 9it rate multiplied 9y t3e

activation factor of t3e service)

For t3e 2P! service0 t3e admission depends on t3e G@")

If t3e lu9 interface reac3es t3e congestion t3res3old0 CCC do:nsiAing occurs) If t3e"LC!M re-transmission ratio eceeds t3e specified t3res3old0 run t3e 2B%

C#""M!LG#2WI%C command to ena9le lu9 #ver9oo>ing) In t3is case0 %F of t3e "//occurs or rate of t3e 2P! service decreases 9ased on t3e related factor) "un t3e !

!!L.!1N#B command to set t3e service activation factor and t3e lu9 congestion

t3res3old) "un t3e ! %6P"!@"LC command to set trigger and release t3res3olds of

"LC!M re-transmission)

3.+.3 (he 8<s Response o) RA5 /etup ailure

due to R5 /etup ailure%3e UB responds "@ setup failure due to su9scri9ersE :rong operations)

#ne case is as 9lo:H

W3en su9scri9ers are using a do:nlin> (.&K data service0 t3ey receive t3e "@ setup re4uest of $Pservice +originating or terminating $P,) @ecause most UBs cannot support performing $P and 3ig3

rate P2 service simultaneously0 t3e UB directly responds "@ setup failure due to unsupported

configuration)

%3e ot3er case is as 9elo:H

%3e UB called 9y 'G UB for $P service camps on G2M net:or>0 so it does not support $P service)

%3erefore0 after t3e "NC receives "!@ assignment re4uest0 t3e CN sends t3e isconnect commandafter call proceeding due to @earer capa9ility not aut3oriAed) No: t3e UB 3as Dust received

2009-05-06 ua:ei Confidential Page $* o" #$




"@2B%UP command0 so it 3as not completed "@ setup) !fter receiving t3e isconnect message0 itimmediately responds "@ setup failure0 so t3e "NC responds "!@ setup failure due to failure in

radio interface procedure)

3.+.# RA5 /etup ailure due to R5 /etup ailureat Air 7nter)ace

!not3er "@ setup failure is as 9elo:H

No response to "@ setup is received0 so t3e "NC Dudges t3at "@ setup fails) In details0 no !CK or

"@ setup complete message is received for "@ setup) %3is occurs in :ea> coverage areas0 9ecause

t3e UB does not camp on t3e 9est server and originate access0 or t3e coverage is :ea>)

%3e UB does not originate to access t3e net:or> in t3e 9est server0 so it :is3es t3at t3e 9est server

+s3arp fluctuation of signals leads to s3arp fading of signals in t3e cell on :3ic3 t3e UB camps, can 9e added to t3e active set during "@ setup) %3e flo:s cannot 9e nested +9ot3 t3e net:or> and UB

does not support nested flo:,0 so t3e active set is updated after "@ setup is complete) %3is leads to

"@ setup in :ea> coverage cells0 so "@ setup fails pro9a9ly) For t3is case0 increase t3e t3res3oldand speed for starting selection of intra-fre4uency cells so t3at t3e UB can camp on t3e 9est server as4uic>ly as possi9le) If t3e net:or> load at early stage is lo:0 t3e UB originates to access t3e net:or>

in t3e 9est server0 set t3e t3res3old for starting selection of intra-fre4uency to ; d@ and set

Treselection to () For cells at edge of different L!Cs0 set t3e t3res3old lo:er to decrease signalingtraffic of location area update)

%3e "@ setup failure due to :ea> coverage includes un4ualified uplin> and do:nlin> coverage)

%3e "@ setup failure due to do:nlin> :ea> coverage is as 9elo:H

%3e UB fails to receive t3e "@ setup command) Un4ualified do:nlin> coverage is partially due to

poor demodulation performance of UB) It must 9e solved 9y "F optimiAation)

%3e "@ setup failure due to do:nlin> :ea> coverage is as 9elo:H

%3e UB receives t3e "@ setup command0 9ut t3e "!N fails to receive t3e !CK message or "@

2etup Complete message for "@ setup) %3is is pro9a9ly due to uplin> interference) C3ec> "%WP for t3is)

3.1 Analyzing Access Proble!s in the Case o)Dualband etworing

!t present0 t:o net:or>ing strategies are availa9leH

2trategy ( +f(H "//Q f.H "//O2P!,

2trategy . +f(H "//O2P!Q f.H "//O2P!,

%3e access in t3e case of dual9and net:or>ing involves direct retry and re-direction in t3e ""C connection

stage and "!@ direct retry) "!@ direct retry includes service-9ased direct retry and t3at after admission

failure) %3e direct retry and re-direction algorit3ms are used to increase first put-t3roug3 ratio of t3e UB)

2009-05-06 ua:ei Confidential Page $# o" #$




3.1.1 RRC direct retry and re0direction duringsetup o) the RRC

Functions and process of ""C direct retry and re-direction during setup of t3e ""C connection

)igure !.! ""C direct retry and re-direction during setup of t3e ""C connection

If t3e "NC receives a ""C connection re4uest0 t3e admission algorit3m decides :3et3er a ""C

connection is allo:ed 9et:een t3e UB and t3e current cell 9ased on t3e load over t3e current cell)

If t3e ""C connection is allo:ed0 t3e "NC sends a ""C C=334CTI=3 <4TAP

message to t3e UB0 and t3en t3e UB sets up a ""C connection)

If t3e ""C connection is not allo:ed0 t3e "NC direct retry algorit3m module searc3es

for a cell t3at complies :it3 t3e direct retry algorit3m in t3e UB candidate list)

R If a suita9le target cell eists0 t3e "NC sends t3e target cell data to t3e UB t3roug3 a""C C=334CTI=3 <4TAP message)

R If no suita9le cell eists0 t3e "NC re-direction algorit3m selects anot3er suita9le

fre4uency or radio access system +suc3 as G2M,0 and t3en notifies t3e UB of t3e248I24CTI=3 cell t3roug3 a ""C C=334CTI=3 24B4CT message) %3e UB

originates an access re4uest in t3e specified fre4uency or system)

3.1.2 (he RA5 Direct Retry

If t3e ""C connection is allo:ed0 t3e "NC sends a ""C C=334CTI=3 <4TAP

message to t3e UB0 and t3en t3e UB sets up a ""C connection)

If t3e ""C connection is not allo:ed0 t3e "NC direct retry algorit3m module searc3es

for a cell t3at complies :it3 t3e direct retry algorit3m in t3e UB candidate list)

R If a suita9le target cell eists0 t3e "NC sends t3e target cell data to t3e UB t3roug3 a

""C C=334CTI=3 <4TAP message)

2009-05-06 ua:ei Confidential Page $+ o" #$




R If no suita9le cell eists0 t3e "NC re-direction algorit3m selects anot3er suita9lefre4uency or radio access system +suc3 as G2M,0 and t3en notifies t3e UB of t3e

248I24CTI=3 cell t3roug3 a ""C C=334CTI=3 24B4CT message) %3e UB

originates an access re4uest in t3e specified fre4uency or system)

%3e "!@ direct retry includes service-9ased direct retry and "!@ direct retry after admissionfailure)

2ervice-9ased direct retry

If a "// cell and a 2P! cell are at different fre4uencies 9ut :it3 t3e same coverage0su9scri9ers :3o are re4uesting for t3e "// service are assigned to t3e "// cell and t3ose

:3o are re4uesting for t3e 2P! service are assigned to t3e 2P! cell if possi9le) %3us0

t3e "// service is separated from t3e 2P! service)

irect retry after admission failure

!fter admission failure0 t3e su9scri9er can 9e connected to a cell at anot3er fre4uency

:it3 t3e same coverage0 a C2 cell at anot3er fre4uency0 or a cell in anot3er system +for

t3e !M" service only,)

If admission of t3e 2P! service fails and t3e direct retry fails in all cells0 t3e service

returns to t3e C of t3e local cell and a "!@ connection is set up on t3e C again)

3.1.3 Analyzing Access Proble!s in the Caseo) Dualband etworing

In dual9and scenario (0 t3e services are carried in "// cells as t3e strategy) In t3is case0 t3e real-time

services do not need inter-fre4uency direct retry during call setup) %3us0 t3e impact on real-time

services decreases and t3e 2P! su9scri9ers can access t3e cells t3at support 2P! t3roug3 service-

9ased direct retry) %o ma>e t3e UB reside in F(0 modify t3e cell selection and reselection parameter

o""set%,n of F( to <* d@ and t3at of F. to -<* d@0 or 9ar F.)

In dual9and scenario .0 t3e strategy of random cell residence is used) %3e UB originates serviceaccess in t3e serving cell) !ll cells t3at use t:o carriers adopt t3e default value of t3e o""set%, n

parameter)

In 9ot3 scenarios0 ""C or "!@ direct retry is availa9le for t3e "// service and "!@ direct retry

after admission reDection is availa9le for t3e 2P! service) If t3e direct retry of t3e 2P! service

fails0 t3e service returns to t3e C of t3e local cell and an "!@ connection is set up on t3e C

again)

Bample (H In scenario (0 t3e 2P! data card resides in t3e "// cell) If t3e PP is activated0 t3e

su9scri9er accesses t3e 2P! cell t3roug3 direct retry) Figure ()( s3o:s t3e signaling for aservice-9ased direct retry)

2009-05-06 ua:ei Confidential Page & o" #$




)igure !.! 2ignaling for service-9ased direct retry of a 2P! su9scri9er

2009-05-06 ua:ei Confidential Page &! o" #$




Bample .H In scenario (0 t3e admission t3res3old of t3e "// service is eceeded if several "//

su9scri9ers access t3e cell) If one more "// su9scri9er tries to access t3e cell0 t3e admission is

reDected in t3e "// cells at F() In t3is case0 t3e su9scri9er accesses a "//O2P! cell t3roug3direct retry) Figure (). s3o:s t3e signaling for direct retry after admission reDection)

)igure !.% 2ignaling for direct retry of a "// su9scri9er after admission reDection

3.11 Analyzing 5/ service access proble!s

3.11.1 the Bow chart o) broadcast !odel in5/

M@M2+Multimedia @roadcast and Multicast 2ervice, provides unilateral service from single point to multi-

point) It permits one resource entity transmits data to several receiver entities) M@M2 provides t3ree >inds of

net:or> model0 including @roadcast0 Bn3anced 9roadcast and Multicast)

)igure !.! Flo: c3art of 9roadcast model in M@M2

2009-05-06 ua:ei Confidential Page &% o" #$




If t3e M@M2 cell is activated0 U%"!N :ill transmit M@M2 system information :3ic3 includes sc3eduling

information of MCC and configuration information of MCC radio 9earer on @CC repeatedly)

First0 net:or> announces UB 9y 2M2 or WB@ t3at M@M2 service :ill 9e

9roadcasted) !fter UB decides to receive M@M2 service0 it :ill setup t3e radio 9earer of MCC according to t3e M@M2 system message received 9y UB

+corresponding to <ervice nnouncement,)

!fter "NC receiving t3e M@M2 <ession <tart message from 2G2N0 it :ill setup

IU signaling 9earer and service 9earer related to M@M2 +corresponding to <ession

<tart,)

"NC announces UB t3e c3ange of MCC information 9y MIC c3annel0 UB gets

t3e information of availa9le M@M2 service and M%C-related radio 9earer from

MCC c3annel +corresponding to M6M< 3oti"ication,)

UB monitors M%C0 9egins to receive data +corresponding to 8ata Trans"er,)

1udging t3at no data is transmitted in a period0 @M-2C sends 2ession 2top message

to announce GG2N2G2N"NC to release t3e related net:or> resource

+corresponding to <ession <top,)

For M@M2 serve0t3e process from UB affirming to receive t3e serve to :atc3ing t3e streaming picture is

t3atH

!pplication layer of UB startup function of Streaming Player －JP3ysical layer affirm and active M@M2

serve－JCongfigure MCC c3annel information on UB side－J"ead MCC information（need t3e data of

a repeated period at least）－J2etup M%C c3annel－JCac3e of M%C PU－J2tart to paly streaming

media)

%3e process of “"ead MCC information”and“Cac3e of M%C PU” elapses long time，effected

9y circumstance easyly；t3e ot3er processes 9elong to inner process of UB0 eecut 4uic>ly)

3.11.2 (he causes that 8< cant receiveprogra!s

%3e causes t3at UB cant receive programs include：

() M@M2 service fails in "NC setup0 t3e cause of t3is failure in current cells can 9e searc3ed 9yMML commandH 2P CBLLM@M22B"$ICB)

%3is command can indicate t3e follo:ing causes for M@M2 service failureH

!ccess Failure0 Common C3annel Fault0 PU Lin> 2etup Failure0 #LC "elease0

Preempted0 !dding cell to multigroup Failure0 MCC 2c3eduling Failure0 P! Parameter

Invalid0 "LC Parameter Invalid and Invalid value)

@esides0 :e can c3ec> :3et3er "NC M@M2 ena9le s:itc3 is on 9y MML commandH L2%

M@M22WI%C)

.) If M@M2 service is already setup in "NC0 9ut t3eres no information in cell0 using t3e follo:ing

steps to locate pro9lemH

C3ec> :3et3er t3e cell is in corresponding 2!+2ervice !rea, 9y MML commandHL2% CBLLM@M!2! and L2% M@M22!)

2009-05-06 ua:ei Confidential Page &$ o" #$




C3ec> :3et3er t3e M@M2 is availa9le in t3is cell 9y MML commandH 2P

CBLLM@M22B"$ICB) If M@M2 isnt activated0 activate it 9y !C%

CBLLM@M2)

C3ec> :3et3er t3eres 2CCPC to carry t3is service and :3et3er its activated0 if

not activated0 activate it 9y !C% 2CCPC)

') 2ervice is already setup in cell0 9ut no data is seen sent do:n according to "NC PU)

First0 c3ec> out :3et3er t3eres data in GG2N

C3ec> :3et3er t3e 2G2N user plane address of service is correct)

;) UB >eeps staying in C#NNBC%I#N stateH

%3is indicates t3at UB doesnt read t3e data on M%C) %3is may 9e caused 9y

%@2I8B configuration pro9lem or incorrect MCC configuration in 2B%

M%CF!C)

<) %3e 9uffer of UB is (**0 9ut t3eres only voice :it3out figure)

Usually it is 9ecause t3e rate of program resource is 3ig3er t3an t3e maimum 9earer

rate of c3annel)

=) UB 4uits after several seconds of receiving normal program)

%3e common c3annel priority in 2B% M%CF!C is configured improperly tooverlap t3at in ! F!C)

3.12 Processing Access Delay

%3e access delay is usually affected greatly 9y e4uipment factors0 so optimiAing it is 3ard) If it isgreatly different from default inde0 c3ec> :3et3er t3e parameter configuration is consistent :it3 t3e

default)

! typical process for calls is from sending t3e ""C C#NNBC%I#N "B5UB2% 9y originating UB

to receiving !lerting message 9y UB) In terms of signaling flo:0 t3e follo:ing aspects affect access

delayH

Configuration of discontinuous cyclic period duration factor "7

W3et3er to disa9le aut3entication and encryption

Barly assignment or late assignment

W3et3er t3e ""C connection is set up on F!C or C %3e impact from (')=K and '); K of signaling connection on delay

3.12.1 Con6guration o) Discontinuous CyclicPeriod Duration actor DR=

uring proceeding delay of paging one UB 9y anot3er0 t3e paging delay ta>es t3e maDority) #n t3eone 3and0 if t3e configured po:er of paging c3annel and paging indicator c3annel is so improper

t3at t3e paging message is resent0 t3is increase proceeding delay) #n t3e ot3er 3and0 "7

determines t3e time for sending paging message) !n over3ig3 "7 leads to long delay)

W3en "7 is =0 ?0 and &0 t3e paging period is respectively =;*ms0 (.&*ms0 and .<=*ms) In terms of

statistics pro9a9ility0 if enoug3 UBs originate enoug3 calls0 t3e traffic is in Poisson distri9ution and

2009-05-06 ua:ei Confidential Page && o" #$




t3e average access delay >eeps increasing) !ccording to on-site test result0 :3en "7 is &0 most paging delays are 9et:een (s and ()<s) %3e longest paging delay is even longer t3an .)<s) W3en

"7 is =0 t3e paging delay is evenly distri9uted 9et:een *)'<s and *)/<s) %3erefore0 setting "7 to

= can effectively lo:er proceeding delay)

3.12.2 9hether to Disable Authentication and<ncryption low

!ccording to test result0

For voice calls0 t3e proceeding delay after ena9ling aut3entication and encryption flo: is *)=s

longer t3an proceeding delay after disa9ling aut3entication and encryption)

For $P calls0 t3e proceeding delay after ena9ling aut3entication and encryption flo: is *)?;s

longer t3an proceeding delay after disa9ling aut3entication and encryption)

For net:or> security0 com9ined :ays of multiple aut3entications are used at t3e 9eginning ofnet:or> normal operation) For eample0 (. aut3entication is used for location area update

aut3enticationQ some services0 suc3 as voice0 $P0 and s3ort messages0 use t3e sync3roniAationmet3od 9ased on (. aut3enticationQ ot3er services use t3e !l:ays aut3entication met3od)

3.12.3 7!ple!enting <arly or ,ate Assign!ent

%3e different 9et:een early and late assignment lies in t3e different assignment time for %C：

Barly assignment increases call completion rate) Late assignment avoids occupation of %C resource during

ringing0 so it increases t3e utiliAation of %C resource)

!ccording to test result0 t3e UB receives !lerting message ().&s earlier in early assignment t3an in late

assignment) Using late assignment 3elps to receive response signals +ringing, from net:or> more 4uic>ly0 so

it is more rational) o:ever0 t3e UB mig3t fail to put t3roug30 so late assignment affects call completion rate)

6ou must 9alance t3e advantages and disadvantages 9efore using it。

3.12.# 9hether the RRC Connection 7s /et upon AC$ and DC$

!ccording to test result0 :3en t3e re4uest signaling of ""C connection originated 9y UB is set up on

F!C0 t3e average setup duration of voice calls is *)=*(s s3orter t3an t3at set up on C');K and *);/(s

s3orter t3an t3at set up on C (')=K) %3e signaling of ""C connection set up on C (')=K

comparatively occupy more resource0 it is recommenda9le if t3e resource at early stage of net:or> operation

is ade4uate)

Note t3at after ""C connection setup0 t3e signaling is reconfigured on C');K upon "@ setup)

3.12.& 7!pact o) Direct Retry And RedirectionAlgorith!on Access Delay

%3e direct retry and re-direction algorit3ms can increase t3e first put-t3roug3 ratio of t3e UBQ 3o:ever0 t3ey

prolong t3e access delay)

2009-05-06 ua:ei Confidential Page &' o" #$




If t3e access fails due to cell congestion or failure of resource allocation during t3e ""C

connection setup0 direct retry of t3e ""C connection setup occurs) %3e "NC ena9les t3e UB to

access anot3er cell at anot3er fre4uency t3roug3 )reDuenc in"o and Primar CPICH in"o int3e 22C C=334CTI=3 <4TAP message) %3is prolongs t3e access delay during t3e ""C

connection setup)

If all direct retries of t3e ""C connection setup fails0 ""C re-direction occurs) %3e re-direction

algorit3m leads t3e UB to access a cell at anot3er fre4uency or a cell in t3e G2M systemt3roug3 2edirection in"o in t3e 22C C=334CTI=3 24B4CT message and cell reselection

of t3e UB) Compared :it3 t3e ""C direct retry algorit3m0 t3e re-direction algorit3m needs cell

reselection0 t3oug3 t3ey 3ave t3e same triggering condition) %3us0 t3e su9scri9ers find t3ataccess delay increases in t3e case of t3e re-direction)

In t3e case of "!@ direct retry 9ased on service separation or admission failure0 t3e "NC

ma>es t3e UB to access a cell at anot3er fre4uency t3roug3 )reDuenc in"o and Primar

CPICH in"o in t3e 26 <4TAP message) %3is prolongs t3e access delay during "@ setup) %3e

field test s3o:s t3at t3e "!@ direct retry prolongs t3e access delay 9y ..*ms)

3.13 5ri)e /u!!ary%3is document aims to guide on-site engineers on solving !ccess pro9lem during net:or> optimiAation)

ig3lig3ting analysis flo: and locate pro9lem0 guide engineers to solve pro9lem step 9y step)

@asing on t3e c3ange of "NC edition0 update t3e interrelated analysis met3od and parameter in t3e

follo:ing :or>)

2009-05-06 ua:ei Confidential Page &( o" #$




# Analyzing $% Proble!s

#.1 %verview%3is document aims to meet t3e re4uirements 9y on-site engineers on solving 3andover pro9lems during

net:or> optimiAation) It descri9es t3e met3ods for evaluating net:or> 3andover performance0 testing

met3ods0 trou9les3ooting met3ods0 and fre4uently as>ed 4uestions +F!5s,) It guides engineers to locate and

solve 3andover pro9lems during optimiAing net:or> KPI indees and net:or> #M)

!ctually 3andover is closely relevant to call drop during net:or> optimiAation) andover failure pro9a9ly

leads to call drop) %3erefore 3andover-caused call drop is arranged in 3andover success rate optimiAation

part) %3e C" optimiAation includes all related to call drop ecept 3andover-caused call drop)

% and C5% are important to net:or> evaluation and optimiAation) %C5% KPIs act as standards for

verifying net:or>s) #verall % 3elps to >no: entire coverage0 to locate missing neig39or cells0 and to locate

cross-cell coverage) # and inter-"!% 3andover are used in coverage solutions for special scenarios0 in

:3ile C5% is proper) %3e follo:ing sections descri9e t3e %C5% inde optimiAation flo: in terms of 2#0

#0 and inter-"!% 3andover)

2009-05-06 ua:ei Confidential Page &* o" #$




#.2 Analyzing /$% Proble!s

)igure !.! s3o:s t3e 2# % data analysis flo:)

#.2.2 7nputting Analysis Data

Perform %) Collect % data0 related signaling tracing0 "NC C"0 and "NC MML scripts)

#.2.3 %btaining 9hen and 9here the Proble!%ccurs

uring t3e test0 2#-caused call drop mig3t occur or 2# mig3t fail0 so record t3e location and

time for t3e pro9lem occurrence) %3is prepares for furt3er location and analysis)

2009-05-06 ua:ei Confidential Page &# o" #$




#.2.# iss eighbor Cell

uring t3e early optimiAation0 call drop is usually due to missing neig39or cell) For intra-fre4uency

neig39or cells0 use t3e follo:ing met3ods to confirm intra-fre4uency missing neig39or cell)

C3ec> t3e active set BcIo recorded 9y UB 9efore call drop and @est 2erver BcIorecorded 9y 2canner) C3ec> :3et3er t3e @est 2erver scram9le recorded 9y 2canner is in

t3e neig39or cell list of intra-fre4uency measurement control 9efore call drop) %3e cause

mig3t 9e intra-fre4uency missing neig39or cell if all t3e follo:ing conditions are metH

R %3e BcIo recorded 9y UB is 9ad)

R %3e @est 2erver BcIo is good)

R No @est 2erver scram9le is in t3e neig39or cell list of measurement control)

If t3e UB reconnects to t3e net:or> immediately after call drop and t3e scram9le of t3e

cell t3at UB camps on is different from t3at upon call drop0 missing neig39or cell is

pro9a9le) Confirm it 9y measurement control +searc3 t3e messages 9ac> from call drop

for t3e latest intra-fre4uency measurement control message) C3ec> t3e neig39or cell list

of t3is measurement control message,

UBs mig3t report detected set information) If corresponding scram9le information is in

t3e monitor set 9efore call drop0 t3e cause must 9e missing neig39or cell)

#.2.& Pilot Pollution

Pilot pollution is defined as 9elo:H

Bcessive strong pilots eist at a point0 9ut no one is strong enoug3 to 9e primary pilot)

!ccording to t3e definition0 :3en setting rules for Dudging pilot pollution0 confirm t3e follo:ing

contentH

efinition of strong pilot

W3et3er a pilot is strong depends on t3e a9solute strengt3 of t3e pilot0 :3ic3 is measured

9y "2CP) If t3e pilot "2CP is greater t3an a t3res3old0 t3e pilot is a strong pilot) Namely0

-%solute RSCP 0h RSCP CPIC3

L

L >)

efinition of SecessiveS

W3en Dudging :3et3er ecessive pilots eist at a point0 t3e pilot num9er is t3e Dudgment

criteria) If t3e pilot num9er is more t3an a t3res3old0 t3e pilots at a point are ecessive)

Namely0 N 0h Num%er CPIC3 > L

efinition of Sno 9est server strong enoug3S

W3en Dudging :3et3er a 9est server strong enoug3 eist0 t3e Dudgment criteria is t3e

relative strengt3 of multiple pilots) If t3e strengt3 different of t3e strongest pilot and t3e

No),(+ +

N 0h

strong pilot is smaller t3an a t3res3old0 no 9est server strong enoug3

eists in t3e point) Namely0

lative RSCP th0h st

0h RSCP CPIC3 RSCP CPIC3 N "e L ,(+( , L L + <−+

@ased on previous descriptions0 pilot pollution eists if all t3e follo:ing conditions are metH

%3e num9er of pilots satisfying -%solute RSCP 0h RSCP CPIC3

L

L > is more t3an N

0h)

lative RSCP th0h st

0h RSCP CPIC3 RSCP CPIC3 N

"e L ,(+( , L L + <−+

2009-05-06 ua:ei Confidential Page &+ o" #$




2et d1m0h -%solute RSCP

/< L −= 0 '=

N 0h 0 and d10h

lative RSCP <"e L = 0 t3e Dudgment standards for

pilot pollution areH

%3e num9er of pilots satisfying d1m RSCP CPIC3 /< L −> is larger t3an ')

d1 RSCP CPIC3 RSCP CPIC3 th st

<, L L + ;( <−

#.2.' 7!proper Con6guration o) /$% Algorith!Para!eters

2olve t3e follo:ing t:o pro9lems 9y adDusting 3andover algorit3m parametersH elayed andover

and Png-pong andover

elayed 3andover

!ccording to t3e signaling flo: for C2 services0 t3e UB fails to receive active set update

command +p3ysical c3annel reconfiguration command for intra-fre4uency #, due tot3e follo:ing cause) !fter UB reports measurement message0 t3e BcIo of original cell

signals decreases s3arply) W3en t3e "NC sends active set update message0 t3e UB

po:ers off t3e transmitter due to async3roniAation) %3e UB cannot receive active setupdate message) For P2 services0 t3e UB mig3t also fail to receive active set update

message or perform %"@ reset 9efore 3andover)

elayed 3andover mig3t 9e one of t3e follo:ingH

R %urning corner effectH t3e BcIo of original cell decreases s3arply and t3at of t3e

target cell increases greatly +an over 3ig3 value appears,)

R Needlepoint effectH %3e BcIo of original cell decreases s3arply 9efore it increasesand t3e BcIo of target cell increase s3arply for a s3ort time)

Ping-pong andover

Ping-pong 3andover includes t3e follo:ing t:o forms

R %3e 9est server c3anges fre4uently) %:o or more cells alternate to 9e t3e 9est server)

%3e "2CP of t3e 9est server is strong) %3e period for eac3 cell to 9e t3e 9est server is

s3ort)

R No primary pilot cell eists) Multiple cells eist :it3 little difference of a9normal"2CP) %3e BcIo for eac3 cell is 9ad)

!ccording to t3e signaling flo:0 :3en a cell is deleted0 t3e (! event is immediately

reported) Conse4uently t3e UB fails 9ecause it cannot receive t3e active set update

command)

#.2." Abnor!al <:uip!ent

C3ec> t3e alarm console for a9normal alarms) Mean:3ile analyAe traced message0 locate t3e 2# pro9lem 9y c3ec>ing t3e failure message) For 3elp0 contact local customer service engineers for

confirm a9normal e4uipment)

#.2.* Reper)or!ing Drive (est

If t3e pro9lem is not due to previous causes0 perform % again and collect % data) 2upplement data

from pro9lem analysis)

2009-05-06 ua:ei Confidential Page ' o" #$




#.2.+ Ad@ust!ent and 7!ple!entation

!fter confirming t3e cause to t3e pro9lem0 adDust t3e net:or> 9y using t3e follo:ing pertinent

met3odsH

For 3andover pro9lems caused 9y pilot pollution0 adDust engineering parameters of anantenna so t3at a 9est server forms around t3e antenna) For 3andover pro9lems caused 9y

pilot pollution0 adDust engineering parameters of ot3er antennas so t3at signals from ot3er

antennas 9ecomes :ea>er and t3e num9er of pilots drops) Construct a ne: site to cover

t3is area if conditions permit) If t3e interference is from t:o sectors of t3e same Node@0com9ine t3e t:o cells as one)

For a9normal e4uipment0 consult customer service engineer for a9normal e4uipment and

transport layer on alarm console) If alarms are present on alarm console0 cooperate :it3customer service engineers)

For call drop caused 9y delayed 3andover0 adDust antennas to epand t3e 3andover area0

set t3e 3andover parameters of (a event0 or increase CI# to ena9le 3andover to occur in

advance) %3e sum of CI# and measured value is used in event evaluation process) %3esum of initially measured value and CIP0 as measurement result0 is used to Dudge intra-

fre4uency 3andover of UB and acts as cell 9order in 3andover algorit3m) %3e larger t3e parameter is0 t3e easier t3e 2# is and UBs in 2# state increases0 :3ic3 consumes

resources) If t3e parameter is small0 t3e 2# is more difficult0 :3ic3 mig3t affects

receiving 4uality)

For needle effect or turning corner effect0 setting CI# to < d@ is proper0 9ut t3is increases

3andover ratio)

For call drop caused 9y Ping-pong 3andover0 adDust t3e antenna to form a 9est server or

reduce Ping-pong 3andover 9y setting t3e 3andover parameter of (@ event0 :3ic3

ena9les deleting a cell in active set to 9e more difficult) For details0 increase t3e (@ event

t3res3old0 (@ 3ysteresis0 and (@ delay trigger time)

#.3 Analyse $$% Proble!

$$% (ypes

# includes t3e follo:ing typesH

Intra-fre4uency #

%3e fre4uency of t3e active set cell 9efore # is t3e same as t3at of t3e cell after

#) If t3e cell does not support 2#0 # mig3t occur) # caters for cross-"NC

intra-fre4uency 3andover :it3out lur interface0 limited resources at lur interface0 and3andover controlled 9y P2 service rate t3res3old of 3andover cell) %3e ( event of intra-

fre4uency measurement events determines intra-fre4uency #)

Inter-fre4uency #

%3e fre4uency of t3e active set cell 9efore # is different from t3at of t3e cell after

#) # 3elps to carry out 9alanced load 9et:een carriers and seamless proceeding)

2tart compression mode to perform inter-fre4uency measurement according to UBcapa9ility 9efore inter-fre4uency #) # Dudgment for selecting cell depends on

period measurement report)

@alanced load #

It aims to realiAe 9alanced load of different fre4uencies) Its Dudgment depends on

9alanced load #)

2009-05-06 ua:ei Confidential Page '! o" #$




)igure !.! s3o:s t3e optimiAation flo: for # C5%)

Ad@ust!ent

%3e optimiAation flo: for # is similar :it3 t3at of 2# and t3e difference lies in parameteroptimiAation)For t3e optimiAation of Intra-fre4uency #0t3e primary command is decrease (

3ysteresis0 and ( delay trigger time properly 9ased on :ireless0 in order to ensure t3e 3andover

3appen in time))

Inter-fre4uency coverage usually eists in special scenarios0 suc3 as indoor coverage0 so C5% are

used) Confirming inter-fre4uency missing neig39or cell is similar to t3at of intra-fre4uency) W3en

call drop occurs0 t3e UB does not measure or report inter-fre4uency neig39or cells) !fter call drop0t3e UB re-camps on t3e inter-fre4uency neig39or cell)

# pro9lems usually refer to delayed 3andover and Ping-pong 3andover)

For Ping-pong # pro9lems0 solve t3em 9y increasing # 3ysteresis and delay trigger time)

elayed # usually occurs outdoor0 so call drop occurs :3en t3e UB is moving) %3ere are t3ree

solutionsH

Increase t3e t3res3old for starting compression mode)

%3e compression mode starts 9efore inter-fre4uency or inter-"!% 3andover) Measure t3e4uality of inter-fre4uency or inter-"!% cell 9y compression mode) Compression mode

2009-05-06 ua:ei Confidential Page '% o" #$




starts if t3e CPIC "2CP or BcIo meets t3e conditions) "2CP is usually t3e triggeringcondition) %3erefore t3e re4uirements on starting t3res3old areH 9efore call drop due to

t3e 4uality deterioration of t3e current cell0 t3e signals of t3e target cell must 9e

measured and reporting is complete) %3e stopping t3res3old must 3elp to preventcompression mode from starting and stopping fre4uently)

Increase t3e CI# of t:o inter-fre4uency cells)

ecrease t3e target fre4uency 3andover trigger t3res3old of inter-fre4uency coverage)

#.# 7nter0RA( $andover C( low

low Chat

%3e inter-"!% 3andover C5% flo: is s3o:ed as follo:ing：

)igure !.! Inter-"!% 3andover C5% flo:

Data Con6guration

Inter-"!% 3andover fails due to incomplete configuration data0 so pay attention to t3e follo:ing dataconfiguration)

G2M neig39or configuration is complete on "NC) %3e configuration includesH

2009-05-06 ua:ei Confidential Page '$ o" #$




R Mo9ile country code +MCC,

R Mo9ile net:or> code +MNC,

R Location area code +L!C,

R G2M cell identity +CBLL I,

R Net:or> color code +NCC,

R @ase station color code +@CC,

R Fre4uency 9and indicator +F"B5@!N,

R Fre4uency num9er

R Cell independent offset +CI#,

Guarantee t3e correctness of t3e previous data and G2M net:or>)

!dd location area cell information near .G M2C to location area cell list of 'G M2C)

%3e format of location area identity +L!I, is MCC O MNC O L!C) 2elect L!I as L!I

type) 2elect Near $L" area as L!I class and add t3e corresponding .G M2C$L"

num9er) %3e cell GCI format isH MCC O MNC O L!C O CI) 2elect GCI as L!I type)2elect Near $L" area as L!I class and add t3e corresponding .G M2C$L" num9er)

!dd data of WCM! neig39or cells on G2M @22) %3e data includesH

R o:nlin> fre4uency

R Primary scram9le

R Main indicator

R MCC

R MI22ING NBIG@#" CBLL

R L!C

R "NC I

R CBLL I

!ccording to t3e strategies of unilateral 3andover of inter-"!% 3andover0 if t3e data

configuration is complete0 t3e inter-"!% 3andover pro9lems are due to delayed 3andover) !

fre4uently-used solution is increasing CI#0 increasing t3e t3res3old for starting and stopping

compression mode0 increasing t3e t3res3old to 3and over to G2M)

Causes

%3e causes to call drop due to 'G-.G inter-"!% 3andover are as 9elo:H

!fter t3e .G net:or> modifies its configuration data0 it does not inform t3e 'G net:or>

of modification0 so t3e data configured in t:o net:or>s are inconsistent)

Missing neig39or cell causes call drop)

%3e signals fluctuate fre4uently so call drop occurs)

Ping-pong reselect)

andset pro9lems causes call drop) For eample0 t3e UB fails to 3and over 9ac> or to

report inter-"!% measurement report)

%3e 9est cell c3anges upon P3ysical c3annel reconfiguration)

Improperly configured L!C causes call drop +solve it 9y c3ec>ing data configuration,)

2009-05-06 ua:ei Confidential Page '& o" #$




#.& D(EC( low )or $/DPA $andover

(ype

!ccording to t3e difference of 3andover on PC in 2P! net:or>0 t3e 2P! 3andoverincludesH

2# or softer 3andover of PC0 :it3 2-P2C serving cell update

Intra-fre4uency and inter-fre4uency # of PC0 :it3 2-P2C serving cell

update

!ccording to different tec3nologies used in t3e serving cell 9efore and after 3andover0 2P!3andover includesH

andover in 2P! system

andover 9et:een 2P! and "// cells

andover 9et:een 2P! and GP"2 cells

ethods

For 2P! service coverage test and mo9ility-related test +suc3 as # on PC :it3 2-

P2C serving cell update0 3andover 9et:een 2P! and "//0 and inter-"!% 3andover,0 perform% to >no: t3e net:or> conditions)

For location of 2P! pro9lems and non-mo9ility pro9lems0 perform C5% +in specified point orsmall area,)

%3e pro9lems :it3 3andover of 2P! su9scri9ers are usually caused 9y t3e faulty 3andover of"// net:or>0 suc3 as missing neig39or cell and improper configuration of 3andover parameters)

W3en t3e "// net:or> is normal0 if t3e 3andover of 2P! su9scri9ers is still faulty0 t3e causemig3t 9e improper configuration of 2P! parameters) Bngineers can c3ec> t3e follo:ing aspectsH

W3et3er t3e 2P! function of target cell is ena9led and t3e parameters are correctly

configured) Bngineers mainly c3ec> t3e :ords of cell and :3et3er t3e po:er is ade4uate0:3et3er t3e 2-2CC po:er is lo:) %3ese parameters mig3t not directly cause call drop

in 3andover0 9ut lead to a9normal 3andover and lo:ered t3e user eperience)

W3et3er t3e protection time lengt3 of 2P! 3andover is proper) No: t3e 9aseline

value is *s) 2et it 9y running <4T H=C=MM)

W3et3er t3e t3res3old for "// 3andover is proper) %3e 3andover flo: for 2P! is

greatly different from t3at of "//0 so t3e 3andover of "// service may succeed :3ile t3e2P! 3andover may fail) For eample0 in . 3andover0 :3en t3e UB reports (9

event0 it triggers "@ reconfiguration in t3e original cell0 reconfigures service 9earer to

C0 and updates t3e cell in active set) If t3e signals of t3e original cell deteriorate

4uic>ly no:0 t3e reconfiguration fails)

W3et3er t3e protection time lengt3 of . 3andover is proper) No: t3e 9aseline value is

.s) 2et it 9y running <4T H=C=MM)

2009-05-06 ua:ei Confidential Page '' o" #$




#.' M5/ obility %pti!ization%3e movement of t3e M@M2 UB 9et:een P%M cells is similar to t3e movement of UB performing

P2 services in t3e CBLL-F!C state) %3e UB performs t3e 3andover 9et:een cells t3roug3 cell

reselection and o9tains a gain t3roug3 soft com9ining or selective com9ining 9et:een t:o cells toguarantee t3e receive 4uality of t3e service) UB sends C*"" P0* to notice 2"NC a9out t3e

c3ange of its resident cell in t3e ne: cell after selecting t3e aim cell0and t3en "NC responceC*""

P0* C(NIRM ) %3e UB firstly moves to t3e target cell and t3en sends a CBLL UP!%Bmessage to notify t3e serving radio net:or> controller +2"NC, t3at t3e cell :3ere t3e UB stays is

c3anged) %3e 2"NC returns a CBLL UP!%B C#NFI"M message) %3e UB receives an M@M2

control message from t3e MCC in t3e target cell and determines :3et3er t3e M@M2 radio 9earer

to 9e esta9lis3ed is consistent :it3 t3at of t3e neig39oring cell) If t3ey are consistent0 t3e originalradio 9earer is retained) %3e M@M2 mo9ility optimiAation0 :3ic3 guarantees t3at t3e UB o9tains

9etter 4uality of service at t3e edge of cells0 covers t3e follo:ing aspectsH

#ptimiAe cell reselection parameters to guarantee t3at t3e UB can 9e reselected to t3e

9est cell in time)

Guarantee t3at t3e po:er of t3e F!C in eac3 cell is large enoug3 to meet t3e coverage

re4uirement of t3e M@M2 UB at t3e edge of t3e cells)

Guarantee t3at t3e transmission time difference of t3e UB 9et:een different lin>s meets

t3e re4uirement of soft com9ing or selective com9iningT)

Guarantee t3at t3e po:er0 codes0 transmission0 and CB resources of t3e target cell are not

restricted or faulty0 and t3at t3e M@M2 service is successfully esta9lis3ed)

#." 5rie) su!!ary%3is document aims to guide on-site engineers on solving 3andover pro9lem during net:or> optimiAation)



follo:ing :or>)

2009-05-06 ua:ei Confidential Page '( o" #$




& Analyzing Call Drop Proble!s

&.1 %verview%3is document aims to meet t3e re4uirements 9y on-site engineers on solving call drop pro9lems and

ma>ing t3em 4ualified during net:or> optimiAation) It descri9es t3e met3ods for evaluating net:or>

3andover and call drop performance0 testing met3ods0 trou9les3ooting met3ods0 and fre4uently as>ed

4uestions +F!5s,)

%3is document serves to net:or> KPI optimiAation and operation and maintenance +#M, and 3elps

engineers to locate and call drop pro9lems)

!ctually 3andover is closely relevant to call drop during net:or> optimiAation) andover failure pro9a9ly

leads to call drop) %3erefore 3andover-caused call drop is arranged in 3andover success rate optimiAation

part) %3e C" optimiAation includes all related to call drop ecept 3andover-caused call drop)

&.2 De6nition o) Call Drop!ccording to t3e air interface signaling recorded at t3e UB side0 during connection0 % call drop

occurs :3en t3e UB receivesH

!ny @C message +system information,

%3e ""C "elease message :it3 t3e release cause Not Normal)

!ny of t3e CC isconnect0 CC "elease Complete0 CC "elease message :it3 t3e release

cause Not Normal Clearing0 Not Normal0 or Unspecified)

! generaliAed C" consists of CN C" and U%"!N C") U%"!N0 so t3e follo:ing sections

focus on KPI inde analysis at U%"!N side)

!fter t3e service is set up0 t3e "NC sends CN t3e "!@ "BLB!2B "B5UB2% message)

!fter t3e service is set up0 t3e "NC sends CN t3e IU "BLB!2B "B5UB2% message)

!fter:ards0 it receives t3e IU "BLB!2B C#MM!N sent 9y CN)

2009-05-06 ua:ei Confidential Page '* o" #$




%3e definition of "!N traffic statistics call drop is according to statistics of lu interface signaling0including t3e times of "NCEs originating "!@ release re4uest and lu release re4uest) %3e % call

drop is defined according to t3e com9ination of messages at air interface and from non-access lay

and cause value) %3ey are not all consistent)

&.3 D(EC( %pti!ization low

)igure !.! Flo: c3art for analyAing call drop

7nputting Analysis Data

Perform %) Collect % data0 related signaling tracing0 "NC C"0 and "NC MML scripts)

%btaining 9here the Proble! %ccurs

#9taining t3e location and time for t3e pro9lem occurrence 9y using % data analysed soft0 li>e

!ssistant) %3at also can o9tain data of Pilot frequency recorded 9y 2canner and information a9out act

set and monitor set of UB)

2009-05-06 ua:ei Confidential Page '# o" #$




Pilot Cell Change

!nalyAe t3e follo:ing conditions a9out pilot cell c3anging)

If pilot cell is sta9le correspondingly0 analyAe "2CP and BcIo for more)

If pilot cell c3anges fre4uently0 need to differentiate conditions a9out pilot cell c3anging)

Analyze the R/CP and <c7o o) pilot cell recorded by /cannerand observe the R/CP and <c7o o) best serve cell.

!dDust t3e net:or> 9ased on t3e follo:ing conditionsH

"2CP is 9ad0BcIo is 9ad0it confirmed coverage pro9lem

"2CP is normal0 BcIo is 9ad+eclude caused 9y delayed 3andover and intra-fre4uency

neig39or cell interfere,，it confirmed do:nlin> interfere pro9lem,

"2CP is normal0 BcIo is normal0if cell in act set of UB is inconsistent :it3 t3e 9est cell

recorded 9y 2canner0it may9e caused 9y missing neig39or or delayed 3andover) if cell in actset of UB is consistent :it3 t3e 9est cell recorded 9y 2canner0it may9e caused 9y uplin>

interfere or a9normal)

%3e most reason of call drop is 3andover call drop0li>e missing neig39or0delayed 3andover and Ping-

Pong 3angdover0:3ic3 3as 9een related in nal:ing H= Pro/lems) %3e follo:ing sections

descri9e t3e call drop not due to 3andover)

&.# Analayzing 9ea Coverage Proble!For voice services0 :3en CPIC BcIo is greater t3an -(; d@ and "2CP is greater t3an -(** d@m +a

value measured 9y scanner outside cars,0 t3e call drop is usually not due to :ea> coverage) Wea>coverage usually refers to :ea> "2CP)

Uplin> or do:nlin> C po:er 3elps to confirm t3e :ea> coverage is in uplin> or do:nlin> 9y t3e

follo:ing met3ods)

If t3e uplin> transmission po:er reac3es t3e maimum 9efore call drop0 t3e uplin>

@LB" is :ea> or Node@ report "L failure according to single su9scri9er tracingrecorded 9y "NC0 t3e call drop is pro9a9ly due to :ea> uplin> coverage)

If t3e do:nlin> transmission po:er reac3es t3e maimum 9efore call drop and t3e

do:nlin> @LB" is :ea>0 t3e call drop is pro9a9ly due to :ea> do:nlin> coverage)

! simple and direct met3od for confirming coverage is to o9serve t3e data collected 9y scanner) If

t3e "2CP and BcIo of t3e 9est cell is lo:0 t3e call drop is due to :ea> coverage)

Wea> coverage mig3t 9e due to t3e follo:ing causesH

Lac> of Node@s

Incorrectly configured sectors

Node@ failure due to po:er amplifier failure

%3e over great indoor penetration loss causes :ea> coverage) Incorrectly configured sectors or

disa9ling of Node@ :ill occur0 so at t3e call drop point0 t3e coverage is :ea>) 6ou must distinguis3

t3em)

2009-05-06 ua:ei Confidential Page '+ o" #$




&.& Analayzing 7nter)erence Proble!

Wit3out interference0 t3e uplin> and do:nlin> are 9alanced) Namely0 t3e uplin> and do:nlin>transmit po:er 9efore call drop :ill approac3 t3e maimum) W3en do:nlin> interference eists0 t3e

uplin> transmit po:er is lo: or @LB" is convergent) W3en t3e do:nlin> transmit po:er reac3es t3emaimum0 t3e do:nlin> @LB" is not convergent) It is t3e same :it3 uplin> interference) 6ou canuse t3is met3od to distinguis3 t3em)

@ot3 uplin> and do:nlin> interference causes call drop)In do:nlin>0 :3en t3e active set

CPIC "2CP is greater t3an &< d@m and t3e active set BcIo is smaller t3an (' d@0 t3e call

drop is pro9a9ly due to do:nlin> interference +:3en t3e 3andover is delayed0 t3e "2CP mig3t

9e good and BcIo mig3t 9e :ea>0 9ut t3e "2CP of BcIo of cells in monitor set are good,) Ift3e do:nlin> "%WP is (* d@ greater t3an t3e normal value +(*? to (*< d@, and t3e

interference lasts for .s's0 call drop mig3t occur) 6ou must pay attention to t3is)

o:nlin> interference usually refers to pilot pollution) W3en over t3ree cells meets t3e

3andover re4uirements in t3e coverage area0 t3e active set replaces t3e 9est cell or t3e 9est cell

c3anges due to fluctuation of signals) W3en t3e compre3ensive 4uality of active set is 9ad+CPIC BcIo c3anges around (* d@,0 3andover failure usually causes C"+2"@ reset or

%"@ reset,)

Uplin> interference increases t3e UB do:nlin> transmit po:er in connection mode0 so t3e over

3ig3 @LB" causes 2"@ reset0 %"@ reset0 or call drop due to async3roniAation) Uplin>

interference mig3t 9e internal or eternal) Most of scenario uplin> interference is eternal)

&.' Abnor!ality Analysis

If t3e previous causes are ecluded0 t3e call drop mig3t due to pro9lematic e4uipment) 6ou need to

c3ec> t3e logs and alarms of e4uipment for furt3er analysis) %3e causes mig3t 9e as 9elo:H

!n a9normal Node@ causes failure of sync3roniAation0 so lin>s >eeps 9eing added and

deleted)

C" caused 9y a9normal UB)

C" caused 9y "NC inner a9normal flo:)

6ou need to focus on t3e call drop due to a9normal testing UB0 :3ic3 occurs easily during C5%)

Namely0 t3e data recorded in % does not contain t3e information reported 9y UB for a period)

&." 5/ CDR Proble! AnalysisIn 9roadcast mode0 t3e M@M2 receives a control message from t3e MCC to esta9lis3 t3e M@M2service and radio 9earer0 :it3out signaling interaction :it3 t3e "NC) %3erefore0 :e can su9stitute

t3e M@M2 session drop rate for t3e M@M2 call drop rate) %3e M@M2 session drop rate is defined

as follo:sH

M@M2 session drop rate num9er of M@M2 session drop timestotal num9er of successes of

M@M2-on-demand (**

Num9er of M@M2 session drop timesH #ne M@M2 session drop time is counted once t3e

M@M2 service is eceptionally interrupted or t3e UB is in t3e 9uffering state for more t3an oneminute)

2009-05-06 ua:ei Confidential Page ( o" #$




%otal num9er of successes of M@M2 on demandH %otal num9er of successes of M@M2-on-

demand originated 9y t3e UB)

%3e possi9le causes for a 3ig3 M@M2 deactivation rate are as follo:sH

%3e net:or> coverage is poor) %3e "2CP and BcIo in t3e position :3ere t3e UB is located

are 9ot3 lo:) In addition0 a 9loc> error rate +@LB", of t3e F!C of t3e M@M2 service also

eists)

For :ea> coverage0 it can 9e improved 9y "F optimiAation0 adding Node@ and adDusting

antenna)

If :ea> coverage can not 9e improved0 increase t3e c3annel po:er of t3e M@M2 service)

%3e cell is in t3e preliminary congestion state and t3e c3annel po:er of t3e M@M2 service is

reset to t3e minimumQ or t3e cell is in t3e over-congestion state and t3e M@M2 service :it3 a

lo:er priority is released 9y force)

%3e UB is at t3e edge of t3e cells0 and t3e neig39oring cells are not configured for t3e cell in

:3ic3 t3e UB is located) !s a result0 t3e UB is una9le to o9tain a gain t3roug3 soft com9ining

or selective com9ining)

"un t3e 8<P C4M6M<<42>IC4 command to 4uery t3e status of t3e current M@M2

service) If t3e M@M2 service is not esta9lis3ed successfully0 t3e failure cause is displayed)

&.* 5rie) su!!ary%3is document aims to guide on-site engineers on solving C" pro9lem during net:or> optimiAation)



follo:ing :or>)

2009-05-06 ua:ei Confidential Page (! o" #$




' Anaylzing (rans!ission Proble!

'.1 %verviewIn WCM! commercial net:or>s0 net:or> optimiAation engineers usually modify and maintainradio parameters) "!N engineers set and maintain transmission parameters) In t3is accustomed

mode0 t3e >no:ledge of net:or> optimiAation engineers on transmission is relatively poor) In fact0

transmission pro9lems directly affect t3e KPIs of net:or>s) %3is section summariAes transmission

pro9lems occurred in multiple WCM! commercial net:or>s0 analyAes t3e relevance 9et:een t3enet:or> KPI and transmission pro9lems0 descri9es influence of transmission pro9lems on t3e

net:or> KPI and 4uality of service +5#2,0 and summariAes t3e >no:ledge necessary for and

common met3ods of locating transmission pro9lems)

'.2 Rules )or (rans!ission Con6guration onthe (rans!ission ,ayer

%3e #MC maintains t3e parameters of t3e transmission layer in commercial net:or>s) %3e #MC

sets parameters for transmission configuration in conformity :it3 specifications :3ic3 refer torelevant guides)2ome important rules for transmission configuration are summariAed 9ased on

common transmission pro9lems in commercial net:or>s as follo:sH

Common configuration rules for t3e Iu9 interface are as follo:sH

!fter t3e ig3 2peed o:nlin> Pac>et !ccess +2P!, is introduced0 proper NCP

9and:idt3 s3ould 9e configured) Calculation of t3e specific NCP 9and:idt3 is

complicated) !ccording to t3e eperience0 it is recommended t3at t3e NCP 9and:idt3

s3ould 9e no less t3an (** >9its) %3e NCP of eac3 Node@ is set to (** >9its)

%3e received cell rate +"C", on t3e Node@ side must 9e greater t3an or e4ual to t3e 2C"

on t3e "NC side) %3e "C" is used for flo: control on t3e Node@ side) If t3e "C" is set

to 9e smaller0 pac>et loss :ill occur 9ecause t3e Node@ is una9le to receive t3e traffictimely)

If t3e Node@ contains an 2P! cell0 at least one 3SP_R0 or 3SP_NR0 !!L.

P!% must 9e configured on t3e Iu9 interface)

%3e impedance of t3e "NC and t3e B( of a Node@ must 9e matc3ed)

2009-05-06 ua:ei Confidential Page (% o" #$




!%M attri9ute configured for t3e !!L. lin> of net:or> elements +NBs, must 9e

consistent) %3e traffic of corresponding !!L. lin>s must 9e consistent0 too) #t3er:ise0 pac>et loss :ill occur in t3e case of 3eavy traffic)

%3e C$% value of t3e !!L. lin> of t3e Iu@ interface s3ould not 9e too large +(*.;*

9y default,) #t3er:ise0 t3e transmission Ditter :ill increase0 leading to lo:er voice4uality)

%3e cloc>s must 9e sync3roniAed) #t3er:ise0 pac>et loss :ill occur)

For t3e Iu interface0 pay attention to t3e configuration of t3e 2ignaling Connection Control Part

+2CCP, timer) It is recommended to set t3e non-active sending timer to /* seconds and non-active

receiving timer to ?.* seconds) If t3e timer settings are inconsistent :it3 t3e peer end data0 t3e

follo:ing re4uirements s3ould 9e metH %3e duration of t3e local non-active receiving timer s3ould 9e more t3an t:ice longer t3an t3at of t3e non-active sending timer of t3e peer end0 and t3e

duration of t3e non-active receiving timer of t3e peer end s3ould 9e more t3an t:ice longer t3an

t3at of t3e local non-active sending timer)

For t3e Iur interface0 pay attention to t3e follo:ingH

%otal 9and:idt3 of t3e Iur interfaceH Iur traffic total traffic of t3e Iu9 interface (*

Iur user planeH W3en configuring !!L. P!%s for t3e "NCs at 9ot3 ends0 t3e

#WNB"2IP attri9utes of one !LL. P!% cannot 9e t3e same) #t3er:ise0 conflicts

:ill occur in distri9uting CIs to t3e t:o ends of t3e Iur interface) It is recommended to

c3ange t3e #WNB"2IP attri9ute of one end to L#C!L0 and t3at of t3e ot3er end toPBB")

'.3 uerying the (rans!ission 5andwidth

'.3.1 Con6guring 5andwidth o) the 7u C//ignaling Plane

Calculate t3e configured 9and:idt3 of t3e Iu C2 signaling plane in t3e MML script)

5uery t3e P7 of Iu C2H N4PC5P678, PC73988:;<=, S"SMS>7188::,

N*I!31(R7?*S, NM*7@SP8@, PC07ICS, S0P7(, PR(07I00.

5uery t3e 2IGLK27 according to t3e P7H M0P;1">S5SI!">S678, P678,

"N>S"SMS>71::88, *M*R!*NC?7(, M0P;1">SNM*7@M0P;1">S8@ )

5uery :3ic3 2!!LLINKs are configured according to t3e 2IGLK27H

M0P;1"N>5SI!">S678, SI!S"C78, SRN7:, SSN78, S""N>N7:=A,

PRI(RI0?78, 0C"*N7:8, 0C7:48, M0P;1"N>NM*7@M0P;1"N>8SI!S"C8@B

5uery t3e !%M%"F corresponding to t3e 2!!LLNKNH S""N>5SRN7:,

SSN78, S""N>N7:=A, CRR?SR7)RSSC, CRR?PN07P3?SIC",

CRR?SN7', CRR?PN7=, CRR?PI7:8, CRR?CI7:8:, 060R67:8D,

R60R67:8D, S""N>07NNI.

Calculate t3e configured 9and:idt3 according to t3e %"F7H 0M0R50R67:8D,

S07C1R, 0R7N(C"PN(SCR, 07C*""ES, PCR7::4<;.

%3roug3 t3e preceding steps0 t3e 9and:idt3 of t3is 2!!LLINK is ::4<; $ D; $ FE:888 7 D888

2%itEs) %3e sum of 9and:idt3s of all t3e 2!!LLINKs is t3e total configured 9and:idt3 of t3e Iu C2

signaling plane)

2009-05-06 ua:ei Confidential Page ($ o" #$




'.3.2 uerying the Con6gured 5andwidth o)the 7u C/ 8ser Plane

Calculate t3e configured 9and:idt3 of t3e Iu C2 user plane in t3e MML script)

5uery t3e !NI of Iu C2H GN(*5NI7:, NM*7@ICS@, N(*07ICS,

P678, 0RNS070M.

List t3e !!L. P!%s configured for t3e !NIH "'P035NI7:, P03I7=8:,

P07R0, CRR?PI7:8, CRR?CI7A8, 060R67:8', R60R67:8',

()N*RS3IP7"(C",H

5uery t3e configured 9and:idt3 according to t3e %"F7H 0M0R50R67:8',

S07C1R, 07C*""ES, PCR7F'DD, C07:8'=, R*MR>7@I_CS_"'P03@.

%3e configured 9and:idt3 of eac3 !!L.P!% is F'DD $ D; $ FE:888 7 ;D88 2%itEs.

'.3.3 uerying the Con6gured 5andwidth o)

the 7u P/ /ignaling Plane

Calculate t3e configured 9and:idt3 of t3e Iu P2 signaling plane in t3e MML script)

5uery t3e P7 of Iu P2H N4PC5P67', PC739888=8;, S"SMS>718888,

N*I!31(R7?*S, NM*7@0(-S!SN;!=@, PC07IPS, S0P7(N, PR(07I00, 1*R0?P*7M0P;1.

5uery t3e 2IGLK27 according to t3e P7H M0P;1">S5SI!">S67:, P67',

"N>S"SMS>71::::, *M*R!*NC?7(, NM*7@0(-S!SN;!=@.

5uery :3ic3 2!!LLINKs are configured according to t3e 2IGLK27)

M0P;1"N>5SI!">S67:, SI!S"C78, SRN78, SN7', SSN7:, S""N>N78,

PRI(RI0?78, 0C"*N7:8, 0C7:48, NM*7@0(-S!SN;!=@B

5uery t3e !%M%"F corresponding to t3e 2!!LLNKNH S""N>5SRN78, SN7',

SSN7:, S""N>N78, CRR?07NC(P0, CRR?SRN78, CRR?SN7'A,CRR?NC(P0N7:, CRR?PI7', CRR?CI7:F8, 060R67:8:, R60R67:8:, H

Calculate t3e configured 9and:idt3 according to t3e %"F7H 0M0R50R67:8:,

S07C1R, 07C*""ES, PCR7'=:A, C07:8'=, H

%3e 9and:idt3 of t3is 2!!LLINK is '=:A $ D; $ FE:888 7 :8'=.= 2%itEs) %3e sum of 9and:idt3s

of all t3e 2!!LLINKs is t3e total configured 9and:idt3 of t3e Iu P2 signaling plane)

'.3.# uerying the Con6gured 5andwidth o)

the 7u P/ 8ser PlaneCalculate t3e configured 9and:idt3 of t3e Iu P2 user plane in t3e MML script)

5uery t3e IP#!P$Cs configured :it3 P**R07(03*R +ot3er IP#!P$Cs are

configured for t3e Node@,H

IP(PC5IPR7@:8.:;'.'.=A@, P**RIPR7@:8.:;'.'.=D@,CRR?07NC(P0, CRR?PN7:, CRR?PI7;, CRR?CI7:;:, 060R67D8',

R60R67D8', P**R07(03*RB

5uery t3e configured 9and:idt3 t3roug3 t3e !%M%"FH ! !%M%"FH%"F7<*.0

2%U@"0 %"FN#CLPN#2C"C$%0 C$%(*.;0 "BM!"KSIUP2U@"SQ t3e

%"F7<*. is U@") %3ere is no PC" limitation) Calculate t3e availa9le 9and:idt3

2009-05-06 ua:ei Confidential Page (& o" #$




according to t3e capa9ility of t3e p3ysical port) %3e availa9le 9and:idt3 for eac3 p3ysical port is (;/ M9its)

5uery t3e IPP!% 9and:idt3 configured for t3e !NI corresponding to Iu P2) %3e

4uerying result s3o:s t3at a total of t:enty-four (** M IPP!%s are configured for t3e

neig39or node of !NI.(0 and t3e total 9and:idt3 is .;** M9its) GN(*5NI7':, NM*7@IPS@, N(*07IPS, P67', 0RNS070M,0MI!"7', 0MIS"7', 0MI1R7', 0I!"7:A, 0IS"7:A, 0I1R7:ABH

Use t3e minimum value of t3e 9and:idt3s 4ueried t3roug3 t3e !%M%"F and configured for t3e!NI) %3e actual p3ysical 9and:idt3 is (;/ M9its)

'.3.& uerying the Con6gured 5andwidths o)the CP and CCP

Calculate t3e configured 9and:idt3 of t3e NCP in t3e MML script)

5uery NCP and CCP for 2!!LLNKNs of t3e NCP and CCP configured foreac3 Node@

NCP5N(*1NM*7@:8F:@, CRR?"N>07S", S""N>N7:8<B

CCP5N(*1NM*7@:8F:@, PN78, CRR?"N>07S", S""N>N7::8B

Identify t3e frame0 slot0 and su9system of t3e Node@)

N(*15N(*1NM*7@:8F:@, N(*1I7:8F:, SRN78, SN7', SSN78,

0N"1*R*R0?P*70M_0RNS, 0RNS*"?7:8,H

Find t3e %"F7s of t3e 2!!LLNKs corresponding to t3e NCP and CCP according to

2"N*0 2N.0 22N*0 2!!LLNKN(*/ or ((*)

S""N>5SRN78, SN7', SSN78, S""N>N7:8<, CRR?07NC(P0, CRR?SRN78,

CRR?SN7'=, CRR?NC(P0N78, CRR?PI7:;, CRR?CI7A8, 060R67'8;,

R60R67'8;, S""N>07NI, HB

S""N>5SRN78, SN7', SSN78, S""N>N7::8, CRR?07NC(P0, CRR?SRN78,

CRR?SN7'=, CRR?NC(P0N78, CRR?PI7:;, CRR?CI7A:, 060R67'8=,

R60R67'8=, S""N>07NI, HB

Calculate t3e configured 9and:idt3 according to t3e %"F7s)

0M0R50R67'8;, S07C1R, 07C*""ES, PCR7:D:, C07:8'=,

R*MR>7@I1_NCP_'*:@B

0M0R50R67'8=, S07C1R, 07C*""ES, PCR7'AD, C07:8'=, R*MR>7@I1_CCP_'*:@B

%3erefore0 t3e configured 9and:idt3 of t3e NCP is :D: $ D; $ FE:888 7 A=.8' 2%itEs0 and t3at of t3e

CCP is 'AD $ D; $ FE:888 7 ::'.;A 2%itEs)

'.3.' uerying the Con6gured 5andwidth o)the 7u5 (rans!ission 8ser Plane

Calculate t3e configured 9and:idt3 of t3e NCP in t3e MML script)

5uery t3e N(*07I1 in GN(* for t3e !NI corresponding to eac3 Node@H

2009-05-06 ua:ei Confidential Page (' o" #$




GN(*5NI7'=8, NM*7@Node1_:8F:@, N(*07I1, N(*1I7:8F:,0RNS070M, ISR((0N(*7?*S, SRN78, SN7', SSN78, S""N>N7:::,

J"'*R7CS', 0MI!"7:, 0MIS"7:, 0MI1R7:, 0I!"7', 0IS"7', 0I1R7'B

5uery all t3e !!L.P!%s configured for t3e !NI) If C!""6% is e4ual to UNI or

N!C#P%0 find t3e configured 9and:idt3 corresponding to eac3 %"F7 and ta>e t3emaimum value0 and calculate t3e configured 9and:idt3 according to t3e %"F7)

"'P035NI7'=8, P03I7:, P07R0, CRR?07NC(P0, CRR?78, CRR?SN7'=,CRR?NC(P0N78, CRR?PI7:;, CRR?CI7A;, 060R67'A8, R60R67'A8,HB

"'P035NI7'=8, P03I7;, P07NR0, CRR?07NC(P0, CRR?78,CRR?SN7'=, CRR?NC(P0N78, CRR?PI7::;, CRR?CI7AD, 060R67'A:,

R60R67'A:, HB

"'P035NI7'=8, P03I7=, P073SP_R0, CRR?07NC(P0, CRR?78,CRR?SN7'=, CRR?NC(P0N78, CRR?PI7:;, CRR?CI7AA, 060R67'A8,

R60R67'A8, HB

"'P035NI7'=8, P03I7D, P073SP_NR0, CRR?07NC(P0, CRR?78,

CRR?SN7'=, CRR?NC(P0N78, CRR?PI7::;, CRR?CI7A4, 060R67'A:,

R60R67'A:, HB

0M0R50R67'A8, S07R01R, 07C*""ES, PCR7F<4', SCR7F<48, M1S7:888,

C07:8'=, R*MR>7@I1_"'P03_R0_'*:@B

0M0R50R67'A:, S07NR01R, 07C*""ES, PCR7F<4', SCR7F<48, M1S7:888,

C07:8'=, R*MR>7@I1_"'P03_NR0_'*:@B

%3erefore0 t3e configured 9and:idt3 of t3e Iu@ user plane of t3e site is F<48 $ D; $ FE:888 7

;F8;.'F 2%itEs)

If C!""6% is e4ual to IM!0 find out t3e num9er of IM!LINKs in t3e IM! Groupaccording to t3e configured 2"N0 2N0 and IM!G"PN)

"'P035NI7'=8, P03I7:, P07R0, CRR?07IM, CRR?7', CRR?SN7:=,

CRR?IM!RPN7:=, CRR?PI7A, CRR?CI7;D, 060R67:=;, R60R67:=;, HB

"'P035NI7'=8, P03I7', P07NR0, CRR?07IM, CRR?7', CRR?SN7:=,

CRR?IM!RPN7:=, CRR?PI7A, CRR?CI7;A, 060R67:=D, R60R67:=D, HB

"'P035NI7'=8, P03I7;, P073SP_R0, CRR?07IM, CRR?7',

CRR?SN7:=, CRR?IM!RPN7:=, CRR?PI7A, CRR?CI7;4, 060R67:=A, R60R67:=A, HB

"'P035NI7'=8, P03I7=, P073SP_NR0, CRR?07IM, CRR?7',

CRR?SN7:=, CRR?IM!RPN7:=, CRR?PI7A, CRR?CI7;F, 060R67:=4, R60R67:=4, HB

IM"N>5SRN7', SN7:=, IM!RPN7:=, IM"N>N7'=B

IM"N>5SRN7', SN7:=, IM!RPN7:=, IM"N>N7;8B

IM"N>5SRN7', SN7:=, IM!RPN7:=, IM"N>N7;:B

IM"N>5SRN7', SN7:=, IM!RPN7:=, IM"N>N7;4B

Four IM!LINKs are configured in t3e preceding eample) 2o0 t3e configured 9and:idt3 is :<8' $

= 7 4A8F 2%itEs)

2009-05-06 ua:ei Confidential Page (( o" #$




'.# 7nBuence o) (rans!ission Proble!s on FP7s

'.#.1 7nBuence o) (rans!ission Proble!s on

the uality o) C/ /ervices%3ere are many factors t3at affect t3e 4uality of C2 services0 suc3 as air interface 4uality0 encryption

mode0 voice coding mode0 3andover0 and transmission pro9lems) %3e influence of transmission

pro9lems on service 4uality results from pac>et loss during transmission) If t3e end users feel t3att3e voice is insta9le or not continuous0 t3e transmission pro9lems are as follo:sH

%3e transmission is insta9le0 suc3 as micro :ave transmission)

%3e configuration of t3e user plane is incorrect) ifferent services re4uire different user plane

lin>s to 9e configured) If t3e attri9utes or traffic of lin>s are configured inappropriately0 t3e usersensi9ility :ill 9e affected)

Cloc> sync3roniAation)

%ransmission Ditter0 mainly t3e setting of t3e C$% value of t3e !!L. lin>) %3e framesc3eduling of t3e user plane for voice services is .* ms) @igger Ditter is li>ely to cause uneven

distri9ution of voice frames)

'.#.2 7nBuence o) (rans!ission Proble!s onthe 8ser Rate

@ased on t3e location eperience of transmission pro9lems in WCM! commercial net:or>s0 t3emain influence of transmission pro9lems on t3e user rate is as follo:sH

%ransmission 4uality pro9lemsH For eample0 insta9le B( transmission leads to a 3ig3 9it

error rate0 and too many re-transmissions in uplin> and do:nlin> lead to a poor user

t3roug3put)

Inconsistent configuration of transmission attri9utes 9et:een NBsH For eample0 9ecause

t3e "C" configured of t3e Node@ is too small0 t3e 2P! t3roug3put cannot 9e

sc3eduled normally0 or t3e configuration of t3e operating mode of t3e FB interface 9et:een t3e transmission e4uipment is inconsistent)

Limited transmission 9and:idt3H For eample0 t3e limited 9and:idt3 of t3e Iu interface

user plane or IU@ interface user plane >eeps t3e t3roug3put lo:)

'.#.3 7 7nBuence o) (rans!ission Proble!s onP7; Delay

ifferent transmission 9earers :ill affect t3e PING delay) %3e comparison 9et:een t3e IM! modeand UNI mode of t3e Iu@ interface is a typical eample) %3e IM! reverse multipleing lin> uses

multiple lo:-speed p3ysical lin>s to transmit t3e cells of a 3ig3-speed !%M lin>) uring

transmission0 t3e cells are distri9uted to t3e lo:-speed p3ysical lin>s according to t3e cyclical

se4uence) uring receiving0 t3e cells transmitted from t3e lo:-speed p3ysical lin>s form a cellstream again) %3e IM! can overcome t3e 9and:idt3 limitation of lo:-speed lin>s and improve t3e

relia9ility) o:ever0 due to t3e multipleing and demultipleing of cells0 t3e IM! mode is poorer in

delay t3an t3e UNI mode)

Usually0 t3e influence of t3e IM! and UNI modes on delay can 9e ignored) %3is influence is not

o9vious for end users) o:ever0 for competitive tests 9et:een different vendors0 or in t3e case t3att3e customer 3as strict re4uirements for PING delay0 t3e influence of different transmission 9earers

on PING delay s3ould 9e made clear)

2009-05-06 ua:ei Confidential Page (* o" #$




'.#.# Analyzing (rans!ission Proble!s o) the8ser Plane

%3is section descri9es t3e de9ugging met3od of t3e Iu@ interface user plane 9ased on t3e !%M site)

%3ere is a self-detection mec3anism for t3e 2!!L protocol0 9ut none for t3e !!L. P!%)%3erefore0 t3e de9ugging of !!L. P!%s in commercial net:or>s is 9ot3 important and difficult)

! fe: de9ugging met3ods t3at t3e products support are introduced as follo:sH

"(P C"H %3e L##P@!CK of !!L. P!% can 9e initiated 9y running t3e =P >C

command on t3e "NC side) %3e "NC sends a loop9ac> cell to t3e Node@ eac3 time t3e

command is run) If t3e loop9ac> response from t3e Node@ is received :it3in five

seconds0 it is L@UP) #t3er:ise0 it is L@-#WN) If L@-#WN is returned for severalconsecutive times0 t3e pro9lem is usually a9out transmission)

C0 C"CC H !fter activation0 t3e t:o ends send #!M cells regularly) If one end does

not receive any cell :it3in ')< seconds0 it reports t3e !I2 alarm and sends t3e "I alarmto t3e peer end) %3is function re4uires t3at t3e NBs of 9ot3 ends support t3e CC function)

C0 C"PM H !fter activation0 t3e t:o ends :ill send an #!M cell after sending a

certain service of !%M cells to inform t3e peer end of t3e num9er of t3e sent cells) %3us0t3e pac>et loss ratio can 9e calculated at t3e t:o ends) %3e result can 9e 4ueried t3roug3

t3e 8<P >CPM command)

!fter t3e CT >CCC and CT >CPM commands are run0 it indicates t3at t3e P$C

is not connected if t3e 8own status is al:ays displayed)

Currently0 all t3e !!L. P!%s of t3e Iu@ interface support t3ese functions) o:ever0 t3einterconnection :it3 e4uipment of ot3er vendors may not support t3ese functions0 9ut can use t3e

=P >C command for testing)

If t3e B( or %( lin> is suspected to 3ave 4uality pro9lems0 it can 9e c3ec>ed 9y using t3e <T2?<T2

4!T!=3T<T command)

Log in to t3e corresponding Node@ to 9e c3ec>ed0 and run t3e <T2 4!T!=3T<T

command to start t3e test)

Usually0 o9serve t3e test data for over '* minutes0 vie: t3e result of Framing Brror "ate0

and c3ec> :3et3er t3e B( or %( lin> 3as 4uality pro9lems)

"un t3e <TP 4!T!=3T<T command to end t3e test)

'.& 7!portant 7PRA Con6gurations

'.&.1 RA /ide

%3e important configurations relating to IP"!N on t3e "!N side are as follo:sH

2et t3e attri9utes of t3e Bt3ernet interfacesH %3e operating modes of t3e FB and GB

interfaces must 9e consistent) 2et t3e FB interface on t3e FG. 9oard to t3e auto-negotiation mode or t3e mandatory value (** MFULL) 2et t3e GB interface on t3e

G#Ua 9oard to t3e auto-negotiation mode) 2et t3e M%U :it3 t3e default value of (<**

9ytes)

2et t3e mapping 9et:een t3e 2CP and $L!N P"I)

2009-05-06 ua:ei Confidential Page (# o" #$




2et t3e mapping 9et:een t3e 4ueue of t3e IP interface and 2CP valueH Note t3at t3e IP

interfaces consist of t3e Bt3ernet interface0 PPP lin>0 MP group0 and IP logical interface)Bac3 IP interface 3as si service data 4ueues0 :3ic3 3ave different priorities) 5* 3as t3e

3ig3est priority0 and 5< 3as t3e lo:est one) %3e priorities of t3e ot3ers decrease

se4uentially)

2et t3e 2CP value of t3e #!M streamH %3e data of t3e #!M stream does not enter

5*5< for transmission) Instead0 it enters a dedicated 4ueue for transmission)

2et t3e 2CP value corresponding to t3e 2C%P lin> and :3et3er to ena9le t3e $L!N

function)

2et t3e 2CP value corresponding to t3e IPP!% and :3et3er to ena9le t3e $L!N

function)

!dd t3e mapping 9et:een t3e destination IP address and $L!N I)

2et t3e mapping 9et:een P@ and 2CP)

'.&.2 ode5 /ide

%3e important configurations relating to IP"!N on t3e Node@ side are as follo:sH

2et t3e attri9utes of Bt3ernet interfacesH %3e operating modes of FB interfaces must 9e

consistent)

2et t3e priorities of signaling and #M)

2et t3e configuration relations3ip 9et:een t3e 2CP value and $L!N)

%3e $.(* sets t3e $L!N 9ased on net 3op)

'.&.3 Restraints on Con6guration o) 7PAddresses

Currently0 t3e system 3as t3e follo:ing restraints on configuration of IP transmission) %3e data needs

to 9e planned according to t3ese restraints during net:or>ing)

"estraints of net:or> segments on "NC IP addressesH

%3e IP addresses of t3e interface0 user plane0 and control plane cannot 9e *) )T)T)T0

(.?)T)T)T0 .<<).<<).<<).<<0 internal "NC su9net segments0 "NC de9ugging su9netsegments +set to net:or> segment (/. 9y default t3roug3 2B% 2U@NB%,0

internaleternal net:or> segments of t3e @!M0 and M.*** net:or> segments)

%3e IP addresses of all Bt3ernet interfaces +B%IPs, on t3e "NC interface 9oard cannot

9e in one net:or> segment)

%3e B$IPs on one interface 9oard of t3e "NC cannot 9e in one net:or> segment) %3e B$IPs and B%IPs of one interface 9oard of t3e "NC cannot 9e in one net:or>

segment)

%3e B$IP cannot 9e identical to eisting IP addresses in t3e "NC +including t3e IP

addresses of t3e local and peer ends of t3e PPP lin> and of t3e MLPPP group0 B%IPs0

IP address of t3e peer end of t3e IPP!%0 and IP address of t3e peer end of t3e 2C%P

lin>,)

%3e B%IPs cannot 9e identical to t3e eisting IP addresses in t3e "NC +including t3e IP

addresses of t3e local and peer ends of t3e PPP lin> and of t3e MLPPP group0 and

B$IPs,

%3e local IP addresses of t3e MLPPP group and PPPLN> cannot 9e identical to t3e

eisting local IP addresses in t3e "NC or t3e IP addresses of t3e peer end in t3e "NC

2009-05-06 ua:ei Confidential Page (+ o" #$




+suc3 as t3e IP addresses of t3e PPP interface and B%IPs0 B% gate:ays0 and logical IPaddresses,) %3e IP addresses of t3e peer end cannot 9e identical to t3e local IP addresses

in t3e "NC)

"estraints of net:or> segments on Node@ IP addressesH

%3e IP addresses of t3e Node@ interface0 user plane0 control plane0 and maintenance plane cannot 9e *)T)T)T0 (.?)T)T)T0 .<<).<<).<<).<<0 and (*)..)() +internal IP addressof t3e "!N=)* Node@ t3at cannot used eternally,)

#ne interface can 9e configured :it3 a maimum of four IP addresses0 :3ic3 can 9e in

one net:or>,)

%3e IP addresses of different interfaces cannot 9e in one net:or> segment)

%3e interface IP address and maintenance IP address can 9e in one net:or> segment)

%3e IP addresses of peer ends of t3e MLPPP group and PPPLNK cannot 9e identical to

eisting IP addresses on t3e Node@) %3e local IP addresses cannot 9e identical to

interface IP addresses configured on t3e Node@)

'.' 5rie) /u!!ary%3is document aims to guide on-site engineers on solving transmission pro9lem during net:or>

optimiAation) ig3lig3ting analysis flo: and locate pro9lem0 guide engineers to solve pro9lem step 9y step)


follo:ing :or>)

2009-05-06 ua:ei Confidential Page * o" #$




" Per)or!ance Analysis

".1 /u!!ary! commercial net:or> re4uires regular performance analysis 9y using Nastar and o9servation of 5o2 and

running status0 toget3er :it3 a timely early :arning of a9normal or potential ris>s) @ased on ua:eiEs

performance analysis practice in multiple commercial UM%2 net:or>s and t3e analysis eperiences of t3e

Performance ept) and t3e %ool ept)0 t3is document epounds t3e flo:s and procedures of performance

analysis and 4uality early :arning0 toget3er :it3 ot3er related precautions)

%3e performance analysts can easily analyAe t3e running 4uality and performance of a net:or> simply 9y

4uerying traffic statistics KPIs) @y epounding t3e general ideas and necessary procedures of performance

analysis0 t3e document normaliAes net:or> analysis and early :arning actions and corrects net:or>

monitoring mista>es0 to improve t3e efficiency of performance analysis and 4uality early :arning)

".2 ecessary /ills %) Per)or!ance Analysis%3e necessary s>ills of performance analysis include 9eing familiar :it3 signaling flo: and 9asic

principles0 >no:ing a9out traffic statistics PIs of product implementation0 and mastering eac3

function of t3e Nastar tool) %3e follo:ing epounds t3ese s>ills one 9y one0 9ut t3e emp3asis is laidon t3e etent of mastery and t3e met3ods of a 4uic> mastery)

".2.1 /ignaling low And 5asic Principles

%o sum up0 t3e mastery of signaling flo:s and 9asic principles is necessitated 9y t3e follo:ingH

(, !9normality location and analysis can 3ave a definite o9Dect in vie:) We can 4uic>ly searc3for ot3er related indees 9ased on flo:s and 9asic principles and ma>e an auiliary analysis)

., Getting familiar :it3 flo:s and principles 3elps associate a9normal PIs :it3 net:or>

pro9lems +suc3 as coverage and interference, and roug3ly determine t3e nature of pro9lems

according to a9normal PIs0 to select corresponding special topic functions +coverage andinterference, of t3e Nastar tool for an in-dept3 analysis)

', %3e mastery of signaling flo:s and 9asic principles 3elps analyAe C") !lt3oug3 C" is t3e

implementation of product internal modules0 a good >no:ledge of signaling and 9asic principles 3elps 4uic>ly get involved in C" analysis)

2009-05-06 ua:ei Confidential Page *! o" #$




Performance analysis re4uires t3at engineers s3ould master 9asic signaling flo:s0 get familiar :it3 protocol stac>s of standard interfaces and >no: a9out related algorit3ms for product

implementation) For numerous ""M algorit3ms0 engineers need to >no: a9out t3eir concepts even

if t3ey cannot ac4uire a good >no:ledge of t3em) If t3e analyAed commercial net:or>s contain somealgorit3ms0 engineers need to learn t3em :ell)

".2.2 a!iliarization o) 8(RA P7s

!fter you 3ave mastered 9asic signaling flo:s0 you need to >no: a9out t3e statistics of t3e performance indees of t3e current product) Performance analysis is directly 9ased on t3ese PIs

provided 9y t3e product) In performance analysis0 engineers need to >eep referrefering to《"!N

Performance Counter "eference》、《"!N Feature escription》) We must 9e familiar :it3 common

performance indees and measurement points) #nly in t3is :ay can t3e second 4uery of traffic

statistics or auiliary 4uery of PIs 3ave a definite o9Dect)

".2.3 8se o) the astar (ool

%3e most essential functions of t3e Nastar tool are Performance 5uery and Performance "eport)Performance analysts mastery of t3e Nastar tool includes t3e follo:ing t3ree levelsH

Provide performance analysis results at t3e level of traffic statistics PIs) Ma>e a special topic

analysis of eac3 service flo: 9ased on t3e familiariAation of signaling flo:s and t3e U%"!N KPI0

and find out a9normal o9servation points in a net:or>))

!nalyAe t3e relations 9et:een traffic statistics PIs and net:or> pro9lems) efine t3e nature of suc3

pro9lems)

!nalyAe real net:or> pro9lems 9y com9ining t3e advanced functions of t3e Nastar)

In an in-dept3 performance analysis0 t3e follo:ing functions of t3e Nastar tool need to 9e usedH

(, CustomiAation and second 4uery of PI., #ptimiAation solution to Intra-fre4uency adDacent cell

', P ilot pollution solution) In pilot pollution analysis0 no I#2 data needs to 9e imported0 9ut

PC"0 PB"Fengineering parameters and configuration files s3ould 9e imported)

;, Coverage analysis solutions) W3en traffic statistics analysis s3o:s t3at t3ere is t3e pro9lem of coverage :it3in a cell0 :e need to ma>e I#2 tracing and import t3e traced I#2 data to Nastar

for coverage analysis) %3is coverage analysis includes common do:nlin> pilot c3annel

coverage analysis0 lin> 4uality analysis0 and overs3oot analysis)<, Interference analysis solutions) Interference analysis 3elps effectively find out eternal

interference or internal pro9lems of e4uipment) @y means of main-diversity signal strengt3

analysis and according to certain algorit3ms0 :e can locate multiple possi9le causes of radio

interference or a9normal signal)

=, Configuration verification?, C" analysis means

%3e advanced functions of t3e Nastar :ill not 9e descri9ed furt3er in t3is document) If you need

t3em0 please 4uery t3e elp of t3e Nastar tool and master eac3 function t3roug3 repeated practices)

".3 Preparations or Per)or!ance AnalysisPerformance monitoring re4uires t3at t3e same emp3asis s3ould 9e laid upon daily report analysis

and :ee>ly report analysis) aily report analysis 3elps eliminate 9urst influence0 suc3 as 9ase station

reset and intermittent transmission failures) Wee>ly report analysis 3elps locate net:or> coverage

pro9lems and interference pro9lems)For comparative c3ec> of :3ole-net:or> parameters0 c3ec> of

2009-05-06 ua:ei Confidential Page *% o" #$




:3ole-net:or> unidirectional adDacent cells0 and c3ec> of :3ole-net:or> missing adDacent cells and pilot pollution) %3ese actions are periodically eecuted) %3e period can 9e flei9ly set according to

t3e fre4uency of net:or> parameter modifications or operations) 5uality early :arning actions may

9e fully eecuted once a mont3 or a 4uarter)

Preparations for Performance !nalysis contain Kno:ledge of Net:or> Conditions and preparationof Master ata)

".3.1 Fnowledge o) etwor Conditions

@efore ma>ing performance analysis0 :e need to ac4uire a good >no:ledge of present net:or>

conditions0 including early net:or> performance indees0 modification records of net:or> parameters0 and operation 3istory of net:or>s)

!n analysis and comparison of performance indees s3ould 9e 9ased on early records of t3isnet:or>) We s3ould not simply ma>e a lateral comparison :it3 ot3er net:or>s or apply 9aseline

indees mec3anically) %3e 9aseline indees defined 9y ua:ei are only for reference or final

standard re4uirements) !t present0 eac3 net:or> 3as respective coverage and capacity) !ccurate

analysis and 3ig3-4uality early :arning must 9e 9ased on t3e present conditions of t3is net:or>)

Parameter revision during net:or> optimiAation re4uires clear records) %3e impact of parameter

revision on net:or>s can 9e analyAed 9y com9ining revision 3istory and performance indees oftraffic statistics) If traffic is not 3eavy0 t3e impact of regional parameter revision on KPI may 9e

unapparent0 nor can it 9e easily o9served) @ut :3en traffic rises suddenly some day0 if early

parameters are unreasona9le0 t3e 9ad impact of parameter revision on KPI :ill 9e clearly seen) !complete record of parameter revision may contri9ute to net:or> performance analysis)

Net:or> operation records include t3e cutover of Node@0 t3e upgrade of "NC and Node@0 and

transmission epansion) %3ey aim to 3elp a comparative analysis of traffic statistics inde and a4uic> analysis of net:or> performance)

".3.2 Preparations )or Per)or!ance Analysis

%3e master data of performance analysis must 9e accurate0 timely and integral) !ccuracy means t3at

Nastar engineering parameters must 9e very accurate and :ill 9e updated along :it3 "F adDustment

of net:or>) %imeliness means t3at traffic statistics data of net:or> needs to 9e uploaded as soon as possi9le) ata integrity means t3at no traffic statistics data s3ould 9e omitted) #t3er:ise0 t3ere may

9e relatively fe:er call attempts and call drop times of a net:or> or a cell0 :3ic3 cannot fully reflect

net:or> 4uality)

2pecifically spea>ing0 master data includesH

I. Nastar engineering parameters) Multiple analysis functions of t3e Nastar tool0 suc3 as missing

adDacent cell analysis0 interference analysis0 and coverage analysis0 are closely related toengineering parameters) %3e accuracy of engineering parameters determines t3e credi9ility of related analysis results of t3e Nastar tool)

II. %raffic statistics data

III. Configuration data

I>. C" data) It is not used only for C" analysis of t3e Nastar tool) In missing adDacent cell

analysis and unidirectional adDacent cell analysis0 C" data is needed) If C" data is only used

for a9normal flo: location analysis0 :e may selectively import C" data according to t3eframe num9er of a cell to 9e analyAed)

>. "%WP data +optional,) It is c3iefly used for interference analysis) It may 9e omitted if

interference analysis is definitely unnecessary)

>I. I#2 data +optional,) It is used for an in-dept3 location analysis of many net:or> a9normality

pro9lems0 suc3 as coverage)

2009-05-06 ua:ei Confidential Page *$ o" #$




>II. General sc3edule of engineering parameters +optional,) It is re4uired for geograp3ic analysis)

NotesH

PC" data records t3e information generated during a call) It :ill 9e recorded in t3e call logs of t3esystem if some conditions are satisfied) It may record t3e signaling flo: status 9efore t3e call drop of a mo9ile p3one0 measurement report information reported 9y a mo9ile p3one 9efore call drop and

signal condition :3en a mo9ile p3one is accessed) In summary0 C" is oriented to all users involved

in 'G services and records t3e contet information of a mo9ile p3one in a conversation) It is output:3en preset conditions are satisfied)

I#2 sampling tracing is to start measurement oriented to one or more users :it3in a cell according to preset conditions) 2ample data can 9e set) I#2 sampling tracing is active data collection initiated 9y

users) It may re4uire t3at a mo9ile p3one s3ould actively report t3e measurement reports on t3e

mo9ile p3one side0 suc3 as do:nlin> pilot "2CP and BcIo0 or re4uire t3at Node@ and "NC s3ould

report special measurement information)

In contrast0 C" data traces all t3e users :it3in a "NC t3at satisfies tracing conditions) It covers alarge scope) I#2 traces one or more users :it3in a specific cell) It covers a small scope0 9ut goesdeeper)

".3.3 Methods o) Per)or!ance Analysis

For different net:or> pro9lems0 t3ere are different met3ods of performance analysis) !c4uire a good

>no:ledge of t3e running status and pro9lems of eisting net:or>0 and t3en select one or more

proper analytical met3ods) %3e commonly used met3ods of performance analysis are as follo:sH

I. %#PN :orst cell

!ccording to traffic statistics indees suc3 as call drop rate0 connection success rate0 and soft

3andover failure rate0 get t3e 9usy-3our average or all-day average as re4uired0 find out t3e :orst N

cells0 and ma>e t3em as t3e emp3asis of fault analysis and optimiAation) #r you may determine t3e priority order of optimiAation 9ased on t3is)

II. %ime trend figure

%rend figure of traffic statistics inde is a commonly used met3od of traffic analysis) !nalysis

engineers may dra: t3e c3ange trend figure of one or more indees of t3e :3ole net:or>0 Cluster or a single cell 9y 3our0 day or :ee> and find t3e c3ange la: of traffic statistics indees)

III. "egion location

%3e c3ange of net:or> performance inde al:ays ta>es place in some regions) %raffic increase0

traffic model c3ange0 radio environment c3ange0 9ase station faults or uplin>do:nlin> interferenceleads to t3e inde variation of t3ese regions) %3e inde variation affects performance indees of t3e

:3ole net:or>) We may compare t3e net:or> performance indees 9efore and after t3e variation0

mar> t3e 9ase station or sector :it3 t3e greatest net:or> performance variation on an electronic

map0 and ma>e a detailed analysis of pro9lematic regions)

I>. Contrast

! traffic statistics inde is al:ays affected 9y multiple factors) 2ome factors c3ange :3ile ot3ers

may not) We may properly select comparison o9Dects0 confirm t3e eistence of pro9lems and analyAe

2009-05-06 ua:ei Confidential Page *& o" #$




t3e causes) W3en o9serving indees0 :e s3ould not focus on only t3eir a9solute values0 9ut on t3eirrelative values)

".# ethod o) Alar! Data AnalysisPerformance analysis is made 9y using t3e Nastar tool :3ile alarm analysis is made 9y using t3e

#mstar) In t3e course of performance analysis0 :3et3er at t3e "NC level or at t3e cell level0 it is

recommended to analyAe alarm data first and confirm :3et3er any related e4uipment alarm affects

PI) If e4uipment and transmission are 9ot3 normal0 an in-dept3 analysis of specific PIs may greatlyimprove efficiency)

!larm analysis met3ods must 9e used toget3er :it3 KPI analysis) !n independent analysis ismeaningless0 nor can it solve net:or> 4uality pro9lems effectively) Generally spea>ing0 t3e KPIs in

our daily concern are traffic0 access performance0 "!@ esta9lis3ment success rate0 3andover0 and

call drop) W3at alarms can t3ese KPIs 9e related to We 3ave simply classified service-relatedalarms as follo:sH

Performance of trafficH transmission congestion alarm0 9ro>en lin> alarm0 and CB resource

congestion +2P a9normality alarm,

""C access performanceH related to congestion alarm0 suc3 as CN congestion0 CPU congestion0

9ase station 9ase9and congestion0 and IU@ interface transmission congestion

"!@ esta9lis3ment success rateH related to transmission congestion and "F coverage

andover performanceH related to cloc> or resource congestion

Call drop rateH Call drop caused 9y "F and 9y unavaila9ility of a cell or a 9ase station

In alarm analysis0:e can found t3at multi-alarms may affect t3e 4uality of net:or>0and same ot3ersare incidental alarm)%3e only :ay to locat t3e root cause is to distinguis3 primaryalarm andincidental alarm)

".& uic Analysis o) /o!e P7s

".&.1 uic Analysis o) /o!e P7s

!ccording to t3e values of indees0 :e can 4uic>ly analyAe net:or> performance 9ased on t3efollo:ing PIsH

Capacity PIs0 suc3 as do:nlin> capacity0 uplin> capacity0 effective utiliAation of codes0 and

9and:idt3 utiliAation %ransmission inde0 suc3 as aal.pat3 Cell unavaila9ility duration $2)Cell)Unavail%ime)#M

@efore using t3e Nastar tool for an in-dept3 analysis0 :e may eport t3e a9ove-mentionedcommonly seen PIs and Dudge :3et3er t3ere is any pro9lem :it3 net:or>) %3is analysis met3od may

greatly improve efficiency0 9ut is not systematic enoug3)

2009-05-06 ua:ei Confidential Page *' o" #$




".&.2 Co!!only /een P7s and CorrespondingAnalysis 7dea

I. !mong t3e causes of call drop0 if $2)"!@)Loss)C2)"F)"LC"st0 $2)"!@)Loss)C2)"F)UL2ync0

$2)"!@)Loss)C2)"F)L2ync0 and $2)"!@)Loss)C2)"F)UuNo"eply ta>e a large proportion0

:e s3ould first analyAe "F pro9lems)

II. 1udge :3et3er overload leads to a9normal release)

If S.R1.RelRe+CS.R1Preempt leads to call drop for many times0 it can 9e confirmed t3at

t3e cell load 3as reac3ed t3e admission t3res3old) If congestion ma>es many users released0 itcan 9e confirmed t3at t3e load of t3is cell 3as reac3ed t3e congestion t3res3old) We may also

ma>e an analysis 9y associating call drop times :it3 t3e do:nlin> load of a cell) If t3e

do:nlin> load of a cell is 3ig3 :it3in t3e period :it3 muc3 call drop +9y vie:ing t3e indeesS.Mean0CP, S.Min0CP, and S.Ma$0CP 0 or starting t3e do:nlin> transmit po:er

measurement of t3is cell,0 start load pro9lem analysis)

III. If call drop rate of t3e :3ole net:or> suddenly 9ecomes relatively 3ig30 generally t3e follo:ing

factors may lead to t3is and :e need to ma>e t3e follo:ing c3ec>H

Iu interface transmission analysisH analyAe alarms to see :3et3er t3ere is any pro9lem :it3

t3e transmission for t3e Iu C2 interface and t3e Iu P2 interface)

"NC e4uipment analysisH analyAe alarms to see :3et3er "NC 9oards reset and :3et3er t3ere

is any e4uipment fault)

:3ole-net:or> traffic analysisH Find out :3et3er sudden increase in registered users and

traffic leads to t3e increase in call drop rate and c3ec> :3et3er t3e system is upgraded or

patc3ed)

".' procedures o) Per)or!ance Analysis%3e performance analysis flo: is not completely a one-:ay process) From t3e perspective of time0

performance analysis is also a day-after-day process of gradual analysis0 repeated optimiAation and

continuous o9servation) !fter a pro9lem is analyAed0 possi9ly t3ere is need to adDust parameters0 increase

transmission and solve e4uipment pro9lems) Upon finis3ing net:or> optimiAation and net:or> maintenance0

continue o9serving net:or> indees0 contrastively adDust traffic statistics performance0 and confirm t3e

effects after t3e c3ange)

2009-05-06 ua:ei Confidential Page *( o" #$




".'.1 %verall analysis of network KPI

2tep ( of performance analysis and 4uality early :arning is to ma>e an overall analysis of

net:or> KPIs) %3e KPIs include0 9ut are not limited to traffic0 call completion rate0 3andover

success rate0 and call drop rate0 s3o:n as follo:s) For t3ose :3ic3 contain specific services0 suc3as 2P! and CM@0 or specific algorit3ms0 :e also need to o9serve t3e integral indees of

corresponding KPIs)

!nalyAe t3e KPI of daily report or :ee>ly report as re4uired) From WCM! PerformanceMonitoring "eport output 9y t3e Nastar tool0 :e can also o9tain a visual overall analysis)

%3e Dudgment of :3et3er t3e KPI is a9normal must 9e 9ased on t3e comparison :it3 early

3istory) We may o9serve t3e etent of relative c3ange instead of t3e a9solute value of t3e KPI)

W3en t3ere is no apparent c3ange in t3e KPI0 t3ere are t:o processing modesH Bnd t3e current

performance analysis and analyAe %#PN cell) W3en t3ere are a large num9er of net:or> cells0 t3e performance deterioration of very fe: 9ase stations may not apparently affect t3e overall net:or>

KPI) %3ese a9normal cells can 9e found out 9y contrasting %#PN analysis)

W3en t3e relative value of t3e KPI is not apparently c3anged 9ut its a9solute value al:ays cannot

reac3 standards and no analysis conclusion 3as 9een dra:n0 :e need to analyAe specific causes

according to traffic statistics data and conduct 4uality early :arning)

".'.2 Analysis of RNC Equipment Problem

"NC e4uipment pro9lem contain follo:ing status：

"NC e4uipment pro9lem and IU" interface transmission pro9lem may affect t3e :3ole-net:or> KPI)

IU interface transmission pro9lem and core net:or> pro9lem :ill affect t3e :3ole-net:or>

KPI directly)

If t3e performance indees of net:or> cells are universally deteriorated0 9asic causes are

related to t3e "NC 9oard reset and restricted IU interface transmission) B4uipment pro9lems

and intermittent transmission failure can 9e c3ec>ed 9y t3e #mstar tool) %ransmission 9and:idt3 restricted can 9e c3ec>ed 9y o9serving transmission-related PIs from traffic

statistics)

!not3er case of affecting t3e overall KPI of "NCH "NC-level parameter c3ange) If t3e

:3ole-net:or> KPI 9ecomes apparently a9normal0 :e need to ma>e sure :3et3er any "NC-level parameter c3ange 3as 9een made recently and carefully c3ec> t3e impact of t3is parameter on t3e net:or>)

2009-05-06 ua:ei Confidential Page ** o" #$




".'.3 KPI analysis of TOPN cell

%3e num9er of %#PN cells can 9e increased according to t3e net:or> scale) %3e num9er of t3e

Nastar tools is (* 9y default) If t3ere are too fe: %#PN cells0 some cells :it3 a9normal

performance may 9e ignored)

%3e WCM! Performance Monitoring "eport output 9y t3e Nastar tool lists t3e %#PN :it3

normal KPIs) !ccording to t3is report0 :e may pic> out important cells from %#PN cells and ma>e

an in-dept3 analysis)

! comparison of t3e indees of %#PN cells :it3 t3ose of 3istory %#PN cells 3elps Dudge :3et3ercell performance indees are normal) It is recommended to use t3e a9ove-mentioned trend analysis

figure for comparison) Ma>e sure :3et3er %#PN cell Id c3anges and :3at t3e amplitude of

c3ange in %#PN cell KPI is) %3is is simple 9ut visual)

%#PN cell pro9lems must 9e analyAed toget3er :it3 cell traffic) For eample0 a pure o9servationof t3e call drop rate of a cell is meaningless) If a cell 3as one call drop0 9ut t3ere is only one call

attempt0 t3e call drop rate is (**)

".'.# Cell equipment analysis

Cell e4uipment analysis means analyAing t3e e4uipment of %#PN cells of last step) Li>e:ise0su9se4uent load pro9lem analysis and interference pro9lem analysis are oriented to %#PN cells)

%3e e4uipment t3at affects cell performance KPI includes t3e antenna feeder e4uipment and t3e

uplin>do:nlin> processing 9oard of a 9ase station) Generally0 related e4uipment alarms can 9e

o9served eit3er on t3e Node@ side or on t3e "NC side)

%3e transmission restricted and intermittent transmission failure of a 9ase station :ill affect related

cell indees) Intermittent transmission failure is o9served 9y using t3e #mstar tool) We ma>e anauiliary analysis 9y using t3e cell unavaila9ility PI +$2)Cell)Unavail%ime)#M, provided 9y t3e

Nastar tool)

".'.& Analysis of cell loa problems

%3e indees directly related to cell load include average uplin>do:nlin> occupied CB of a cell

+$2)LC)ULCreditUsed)CBLL.0 $2)LC)LCreditUsed)CBLL, and t3e maimumuplin>do:nlin> occupied CB +$2)LC)ULCreditUsed)CBLL)Ma.0

$2)LC)LCreditUsed)CBLL)Ma,) W3en t3e maimum uplin>do:nlin> occupied CBapproac3es (.& or t3e average occupied CB is around =*0 epansion s3ould 9e considered)

Causes for cell load pro9lems includeH c3ange of traffic modelQ t3e main coverage service of t3iscell is designed to 9e $P=;0 9ut actually t3ere are a large num9er of '&;> services) uring

3olidays0 relatively concentrated population leads to t3e increase in traffic)

ig3 load may cause CB congestion0 po:er congestion0 code congestion0 and transmission

congestion) We s3ould ma>e an analysis 9y o9serving corresponding PI)

2009-05-06 ua:ei Confidential Page *# o" #$




In load pro9lem analysis0 :3en muc3 po:er congestion occurs0 actual load is not necessarily very3ig3) In t3is case0 :e need to analyAe admission strategy and Dudge :3et3er admission parameters

are properly set)

".'.' Analysis of cell interference problemsCauses of interferenceH UB self-correlation interference) If t3ere are many UBs in a conversation:it3in a cell0 interference :ill increase) Interference is also caused 9y eternal interference source

and 9y pilot pollution)

W3et3er t3ere is any uplin> interference :it3in a cell can 9e Dudged 9y o9serving t3e "%WP

indees in traffic statistics0 t3at is0 t3e average "%WP of a cell and t3e maimum "%WP of a cell)

If t3e average "%WP of a cell is as 3ig3 as -/< d@m or 3ig3er0 it is possi9le t3at t3ere is uplin>interference) #9serve t3e maimum "%WP) If "%WP pea>0 suc3 as -?* d@m0 is often seen0 t3e

cause may 9e t3e po:er of access process or 3andover process)

!n in-dept3 interference analysis re4uires t3at t3e interference analysis function of t3e Nastar

s3ould 9e started) If a cell 3as severe interference0 :e need to trace its "%WP data) Import t3e"%WP data0 configuration data and engineering parameter to t3e Nastar tool0 and start t3e

interference analysis function) In t3is :ay0 :e can effectively find eternal interference or internal

e4uipment pro9lems) %3is function locates multiple possi9le causes of radio interference or

a9normal signals 9y analyAing main-diversity signal strengt3 and according to certain algorit3mcategoriAation)

".'." Analysis of cell covera!e problems

Coverage pro9lems include poor coverage0 ecessive coverage0 pilot pollution0 and missing

configuration of adDacent cells)

Poor coverage leads to poor performance of an air interface) In traffic statistics0 a large

num9er of PIs0 suc3 as "F)"LC"st0 "F)UL2ync and UuNo"eply0 are related to poor

coverage)

For an in-dept3 analysis of poor coverage and ecessive coverage0 :e need to provide t3e

I#2 data of t3e analyAed cell and ena9le t3e coverage analysis function of t3e Nastar to ma>e

a statistical analysis of t3e coverage strengt3 of t3e pilot and t3e lin> 4uality of service)

Pilot pollution analysis does not need any I#2 data) %3e pilot pollution analysis function of

t3e Nastar tool needs C" data0 engineering parameter0 configuration data0 and trafficstatistics data) %3e principles of pilot pollution analysis are to ma>e statistics according to (Cmeasurement reports and signal 4uality of active set and monitoring set :3en (C reports are

reported0 toget3er :it3 t3e num9er of 9ranc3es of cell po:er splitting output in engineering

configuration parameters)

%3e intra-fre4uency adDacent cell c3ec> of t3e Nastar tool can 9e fully used to find t3ose

adDacent cells t3at miss configuration) In using t3is function0 :e need to turn on t3e detection

set reporting s:itc3) %3e principles of t3is function are to Dudge :3et3er any adDacent cellmisses configuration 9y ma>ing statistics of detection set reports and cell signal strengt3

reported)

".'.* Analysis of parameter problems

2009-05-06 ua:ei Confidential Page *+ o" #$




If t3e KPI deterioration of a cell is not closely related to e4uipment0 load0 interference or coverage0:e need to c3ec> cell parameters carefully)

We need to ma>e sure :3et3er t3e 3istory of net:or> operations contains any parameter

adDustment related to t3is cell0 including adDustment of adDacent cell relations3ip and "F parameteradDustment) If cell parameter adDustment 3as 9een made recently0 :e need to ma>e a carefulanalysis) Mean:3ile0 t3e impact of early parameter adDustment on t3e recent KPI s3ould not 9e

eliminated) We also need to c3ec> :3et3er t3ere is a 9ig increase in t3e traffic of t3is cell) If traffic

increases s3arply0 t3e unreasona9leness of cell parameters :ill 9e easily found)

%3e configuration verification function of t3e Nastar tool can 3elp 4uic>ly c3ec> t3e parameter

c3anges of t3e same version made on a different day)

!nalysis of C" process and terminal performance pro9lems

%3e prere4uisite to net:or> planning performance analysis is sta9le product performance and

normal e4uipment) @ut t3e 9ug of actual net:or>s and products al:ays eists) We need to define:3et3er t3e pro9lem lies in product implementation t3roug3 performance analysis)

In cell performance analysis0 sometimes a9normal access or call drop still occurs even if t3ere is no

3ig3 load0 a cell 3as normal signal coverage and t3ere is correct parameter configuration) In t3iscase0 :e need to ena9le t3e C" analysis function of t3e Nastar tool and use signaling process to

ma>e an analysis) %3e dot information of C" involves t3e implementation of a product internal

module) C" analysis does not aim to accurately locate a pro9lem0 9ut to determine t3e scope of

t3e pro9lem and failure location of a9normal processes) %3en0 feed9ac> t3e result to product " personnel to provide auiliary information a9out t3e location 9y t3e " personnel)

@esides "!N e4uipment pro9lem0 terminal pro9lems cannot 9e ecluded in performance analysis)Many of t3em 3ave 9een found in an actual net:or>) 2ometimes0 a terminal transmits at a fied

po:er and t3e conditions t3at a terminal satisfies measurement reports fail to 9e reported in time)For t3e sa>e of 4uery0 terminal pro9lems found in eisting net:or> can 9e classified and included

in a list)

"!N e4uipment pro9lems and terminal pro9lems seldom appear0 t3erefore t3ey are put at t3e end

of performance analysis) In analyAing a9normal PIs0 after ecluding multiple possi9le causes0 :e

s3ould dare to dou9t e4uipment pro9lems and give reasona9le evidence 9ased on C")

"." 5rie) /u!!ary

Performance analysis and 4uality early :arning is t3e pivotal moment for discover pro9lem eactly and

timely0It is also t3e foundation of in-dept3 analysis and 4ualification of constituting latter sc3eme)%3e

c3apter introduce t3e procedures and met3ods of performance !nalysis0aim to provide reference for analysis

operations and improve t3e efficiency of UM%2 net:or> performance anal)

2009-05-06 ua:ei Confidential Page # o" #$




* Conclusion

!s t3e mo9ile communication tec3nology develops0 t3e limits 9et:een related tec3nologies 9ecomeo9scure) %3e functions of t3e 9ase station controller +@2C, and t3e 9ase station overlap0 and +radio,

net:or> planning and optimiAation integrates :it3 radio product functions) %3ere is a commono9Dect0 t3at is0 to improve t3e mar>et adapta9ility and net:or>ing capa9ility of radio products and

t3e 4uality of radio net:or>s)

%3e radio system features t3e mo9ility of users and cellular net:or>ing structure) %3e net:or>

planning and optimiAation engineers need to 3ave a deep understanding of t3e compleity and

association of macro radio cellular net:or>ing0 and to s3o: insig3t to customersE re4uirements andt3e potential c3anges in radio net:or>s)

In addition to paying attention to t3e principles and means of radio net:or> optimiAation0 t3enet:or> planning and optimiAation engineers need to understand de9ugging of radio e4uipment andcore net:or>0 and summariAe eperience and ac4uire more t3eoretical >no:ledge t3roug3 actual

net:or> optimiAation practices and 9y studying cases at 3ttpHsupport)3ua:ei)com to 9ecome

ecellent engineers)

%3e )-"PI Monitoring and (ptimi&ation !uide summariAes t3e overall idea and necessary

procedure of common KPI analysis in optimiAation of radio net:or>s) ue to t3e current conditions0some descriptions in t3is !uide are not perfect0 re4uiring studies and accumulations in su9se4uent

practices)

Pay attention to t3e follo:ing in revising later versionsH

Update relevant analysis met3ods and indees according to t3e c3ange in "!N versions) !dd t3e latest optimiAation tec3nologies and met3ods according to t3e latest practice)

@ecause PC" is availa9le since .**&0 add relevant cases in lig3t of t3e PC"

applications in revising t3e later versions of t3is !uide)

Feed 9ac> t3e comments on revision of t3is !uide at http5EEgcrms.hua/ei.com.

2009-05-06 ua:ei Confidential Page #! o" #$


http://gcrms.huawei.com/


http://gcrms.huawei.com/




+ Re)erences

Bcept 'GPP from t3e 'GPP organiAation0 t3e follo:ing references are internal documents ofua:ei)

'GPP .()/*< $oca9ulary for 'GPP 2pecifications

'GPP .<)/'( U%"!N Functions Bamples on 2ignaling Procedures

'GPP .<)''( "adio "esource Control

'GPP .<);'' Iu9 interface N@!P 2ignaling

'GPP .<);.' Iur interface "N2!P 2ignaling

'GPP .<);(' Iu interface "!N!P 2ignaling

'GPP .<)(*; @2 %ransmission and "eception

'GPP .<)(*( UB %ransmission and "eception

Guide to W-KPI Monitoring and #ptimiAation #ptimiAation of P2 2ervice Pro9lems

W-"F #ptimiAing Guide

W-%C5% %ests Guide

Guide to #perations in W-B4uipment "oom

W-Interference !nalysis Guide

"!N 2ignaling !nalysis Guide

"!N Performance Counter "eference

"!N Feature escription WCM! Performance - "adio !ccess Net:or> KPI efinition Manual

Function !cceptance %est 2pecification for KPI %est

UM%2 Net:or> KPI @aseline

@2C=&(* $.**"*(* Product escription

UM%2 Net:or> Bvaluation #ptimiAation etailed Instructions #n $(**"**(

$(**"**(－ Net:or> Performance

UM%2 Net:or> Bvaluation #ptimiAation etailed Instructions #n $(**"**(－"esouce

and capa9ility

UM%2 Performance !dvance 2erve Proposal #n 2erve Procedure $**."**(

2009-05-06 ua:ei Confidential Page #% o" #$




UM%2 "adio Net:or> urative #ptimiAation 2erve Proposal #n 2erve Procedure

$**."**(

2P! Performance !dvance 2erve Proposal #n 2erve Procedure $(**"**.

GBNB7 Pro9e User Manual

GBNB7 !ssistant User Manual

GBNB7 Nastar WCM! User Manual

W-!ccessi9ility Pro9lem #ptimiAation Guide-.**?(.*<-!-')'

W-Neig39or Pro9lem #ptimiAation-.**?(*(*-!-().

W-andeover !nd Call rop Pro9lem #ptimiAation Guide -.**?(.('-!-')'

W-Net:or> Performance !nalysis Guide-.**=((*/-!-')*

W-%ransmission Pro9lem !nalysis Guide-.**&*'*<-!-')'

W-2P! "ate Pro9lem Location Guide -!-()*

WCM! "NC C" !nalysis Guide

"!N(* IP"!N eployment Guide-.**&*&.<-!-.)*

"!N(* M@M2 eployment Guide-.**&*&.(-!-()'

"!N(* 2P! eployment Guide-.**&*&.(-!-.)*

"!N(* 2UP! eployment Guide-.**&*&.(-!-.)*

KPI Monitoring and Improvement Guide 20090507 a 1.0

Documents

Transcript of KPI Monitoring and Improvement Guide 20090507 a 1.0