Data Performance Optimisation Guideline v07

8/12/2019 Data Performance Optimisation Guideline v07

http://slidepdf.com/reader/full/data-performance-optimisation-guideline-v07 1/82

1/82 Document Type Author Unit/Dept.

Document TitleDate, VersionFor internal use only

Nokia Siemens Networks

Data Performance Optimisation Guide



Revision History

Date Rev. Summary of Change

2.!.2""8 v.".1 Document created 2#.12.2""8 v.".$ First draft for review

1!.1.2""! v.".% Initial reviewed version

&'itor/s()ar**o +t*onen, irsiTer-v-inen, e**a Ranta

Date( 1!.1.2""!

Version( v.".%

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2 6827

opyri0ht o*ia 3iemens et4or*s. This material, inclu'in0 'ocumentation an' any relate' computer pro0rams, is protecte' y copyri0ht controlle' y o*ia 3iemens et4or*s. All ri0hts are reserve'.opyin0, inclu'in0 repro'ucin0, storin0, a'aptin0 or translatin0, any or all o5 this material re9uires the prior 4ritten consent o5 o*ia 3iemens et4or*s. This material also contains con5i'ential in5ormation 4hich maynot e 'isclose' to others 4ithout the prior 4ritten consent o5 o*ia 3iemens et4or*s

:/3: apaility ;ana0ement Date( 1!.1.2""!Data er5ormance :ptimisation <ui'e 5or RA3"$ Version ".%



Ta!e of contents

1 +ntro'uction..................................................................................................

2 3 Data connection si0nallin0.....................................................................

2.1 RR 3etup...............................................................................................................................2.2 ac*et 'ata connection setup.................................................................................................2.2.1 <R3 Attach.......................................................................................................................2.2.2 3ervice Re9uest..................................................................................................................2.2.# D conte=t setup...............................................................................................................2.2.> Data 5lo4 setup....................................................................................................................2.2. RR state transitions...........................................................................................................2.2.$ ac*et 'ata connection moility..........................................................................................

# 3 RA? @o3 parameters..........................................................................

#.1 3peci5ication...........................................................................................................................#.2 De5inition o5 3 RA? @o3 in connection setup.......................................................................

> RT 3 RA? per5ormance........................................................................

>.1 Accessiility............................................................................................................................>.2 Retainaility............................................................................................................................

H3A earer per5ormance.........................................................................

.1 Accessiility.............................................................................................................................1.1 H3DA U Return hannel..................................................................................................1.2 H3UA Accessiility.............................................................................................................2 H3A Throu0hput an' RTT.....................................................................................................2.1 H3DA Throu0hput +s........................................................................................................2.2 H3UA Throu0hput +s........................................................................................................2.# H3DA optimise' throu0hput...............................................................................................2.> H3UA optimise' throu0hput...............................................................................................# ;oility....................................................................................................................................> Retainaility............................................................................................................................

$ H3A B R!! earer inter4or*in0...............................................................$.1 o4er, co'e an' & 6H3UA7 sharin0...................................................................................$.1.1 D po4er sharin0.................................................................................................................$.1.2 hannelisation co'e tree sharin0........................................................................................$.1.# C?T3 resource sharin0.......................................................................................................$.2 &55ect o5 H3A on R!! per5ormance.......................................................................................

Re5erences.....................................................................................................

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e # 6827




"ist of #igures

Fi0ure 1. 3cope o5 the Data er5ormance :ptimisation <ui'e....................................................................$Fi0ure 2. RR connection setup si0nallin0..................................................................................................%

Fi0ure #. <R3 Attach proce'ure................................................................................................................!Fi0ure >. 3ervice Re9uest proce'ure.........................................................................................................1"Fi0ure . D conte=t setup proce'ure.....................................................................................................1"Fi0ure $. apacity re9uest an' resource allocation si0nallin0 5or pac*et 'ata call. H3DAH3UA... ... .12Fi0ure %. RR states an' transitions. RU1" Direct recon5 DHEH......................................................1>Fi0ure 8. Transition 5rom &GDH to &GFAH 4ith Ra'io ?earer Recon5i0uration proce'ure.......1>Fi0ure !. Transition 5rom &GFAH to &GH 6URAGH7 4ith Ra'io ?earer Recon5i0urationproce'ure................................................................................................................................................... 1Fi0ure 1". Trans5er o5 the U& to &GDH an' reactivation o5 the 'ata connection 6cause U 'atatransmission7.............................................................................................................................................. 1Fi0ure 11. 3ervin0 H3ED3H cell chan0e tri00ere' y perio'ical &co measurements...........................1%Fi0ure 12. 3ervin0 cell chan0e tri00ere' y &vent 1? on the servin0 H3D3H cell 6no ?A si0nallin0presente'7.................................................................................................................................................. 18

Fi0ure 1#. +nterER servin0 H3ED3H cell chan0e 4ith har' han'over 6no ?A si0nallin0 presente'7.................................................................................................................................................................... 18Fi0ure 1> 3 RA? setup 5ailure rate statistics 5rom live net4or*................................................................22Fi0ure 1. 3 RA? Access 5ailure rate statistics 5rom live net4or*............................................................2#Fi0ure 1$. RT 3 RA? retainaility analysis............................................................................................2Fi0ure 1% &=ample o5 3 RT RA? Active 5ail chan0e 'ue to ?T3...........................................................2$Fi0ure 18 H3DA Accessiility Failure Analysis......................................................................................28Fi0ure 1!. &=ample H3DA accessiility +s 5rom live net4or*.................................................................2!Fi0ure 2". &=ample H3DA accessiility 5ailure causes............................................................................2!Fi0ure 21. H3DA accessiility 4ith optimisation....................................................................................... #1Fi0ure 22. H3DA acessiility 5ailure analysis 4ith optimisation steps......................................................#1Fi0ure 2#. &55ect o5 r=oa';ar0in;a=DH on H3DA return channel accessiility................................#2Fi0ure 2>. Relation et4een U & usa0e an' H3ED3H setup 5ailures..................................................##

Fi0ure 2. Activation o5 T?: an' 1$ *ps return channel..........................................................................#>Fi0ure 2$. H3UA Accessiility 5ailure analysis.........................................................................................#$Fi0ure 2%. &=ample o5 H3UA selection 5ailure causes 5rom live net4or*.................................................#%Fi0ure 28. &=ample o5 H3UA setup 5ailure causes 5rom live net4or*......................................................#%Fi0ure 2!. Relation et4een & usa0e an' H3UA setup an' selection 5ailures......................................#8Fi0ure #". Throu0hput per allocate' H3ED3H I8J....................................................................................#!Fi0ure #1. H3DA throu0hput measurement 5rom ?T3 an' 'rive test lo0.................................................>1Fi0ure #2. H3UA throu0hput +3 an' 'rive test tool measurement.........................................................>#Fi0ure ##. H3UA selections an' throu0hput............................................................................................>#Fi0ure #>. H3DA R throu0hput 6application level throu0hput is typically 1"K lo4er7 vs. ompensate'@+............................................................................................................................................................. >Fi0ure #. H3DA application level throu0hput 4ith 'i55erent H3DA cate0ory U&s.................................>Fi0ure #$. @+ 'istriution 'urin0 testin0 5or 'i55erent U&s........................................................................>$

Fi0ure #%. H3DA throu0hput an' co'e allocation 4hen 2 simultaneous cate0ory 8 H3DA U&.... .... ....>$Fi0ure #8. H3UA throu0hput 4ith H3UA 2 ;ps 5eature.......................................................................>8Fi0ure #!. H3UA ell U application level throu0hput 4ith 'i55erent numer o5 H3UA U&s an' 4ith'i55erent r=Tar0et;a=?T3 values 6chan0e' in case o5 # H3UA U&7......................................................>!Fi0ure >". H3UA user throu0hput 4hen # simultaneous H3UA U&.......................................................>!Fi0ure >1. U application level throu0hput o5 1 H3UA U& 4hen there is 'i55erent numer o5 U&s in thecell.............................................................................................................................................................. "Fi0ure >2. Uplin* r=Total 4ith 'i55erent numer o5 H3UA U&s..............................................................."Fi0ure >#. Uplin* oa' 4ith 'i55erent numer o5 H3UA U&s....................................................................1Fi0ure >>. ?T3 & H3UA Usa0e an' H3UA ;a=imum ;acE' Throu0hput..........................................2Fi0ure >. ?T3 resource status counters...................................................................................................2Fi0ure >$. H3UA con0estion control an' HC overloa' Frame loss counter......................................>Fi0ure >%. Function o5 +u con0estion ontrol...........................................................................................>

Fi0ure >8. Function o5 +u con0estion control 5or throu0hput 4ith 'i55erent symol rate............................Fi0ure >!. H3UA con0estion control 'ecrease the H3UA it rate y 'ecreasin0 the 3ervin0 0rant 4ithtoo hi0h sprea'in0 co'e con5i0uration.......................................................................................................

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e > 6827




Fi0ure ". Uplin* throu0hput 4ith 1 = &1 5or H3A an' 'i55erent arameter values..................................$Fi0ure 1. U& t= o4er limitation vs. H3UA throu0hput..........................................................................%Fi0ure 2. &=ample o5 3 5ailure reasons...............................................................................................!Fi0ure #. H3DA 3 per5ormance compare' to H3DA retainaility....................................................$"Fi0ure >. H3A retainaility 5ailure analysis.............................................................................................$1

Fi0ure &=ample o5 H3DA release types 6K7.......................................................................................$2Fi0ure $ &=ample o5 'i55erent release reasons 5or H3ED3H channel.....................................................$#Fi0ure % &=ample o5 &EDH release........................................................................................................$>Fi0ure 8. &55ect o5 DH po4er on H3DA throu0hput..............................................................................$Fi0ure !. H3ED3H co'e reservation....................................................................................................$Fi0ure $". D po4er sharin0 et4een H3DA an' RT 3 tra55ic............................................................$$Fi0ure $1. D po4er sharin0 analysis........................................................................................................$%Fi0ure $2. Avera0e U an' D loa' as a 5unction o5 H3DA po4er...........................................................$8Fi0ure $#. H3DA o'e 'o4n0ra'e 'ue to A;R 4ith H3D3H;ar0in3F128L"...................................$!Fi0ure $>. &=ample o5 H3DA co'e allocation an' sprea'in0 co'e occupancy I8J...................................%"Fi0ure $. &=ample o5 H3DA B RT co'e allocation 'uration 4ith 'i55erent U&s....................................%1Fi0ure $$. o'e tree occupancy................................................................................................................%2Fi0ure $%. o'e tree loc*in0, 4ith co'e 'o4n0ra'e 'ue to con0estion...................................................%#Fi0ure $8. o'e 'o4n0ra'e 'ue to RT 4ith DH:verH3D3HThreshol'L"....................................%>Fi0ure $!. 3etup 5ails 4ith DH:verH3D3HThreshol'L"..................................................................%>Fi0ure %". &=ample o5 C?T3 resource sharin0 4ith H3DA..................................................................... %%Fi0ure %1. &=ample o5 C?T3 resource sharin0 4ith H3UA..................................................................... %8Fi0ure %2. &55ect o5 increase' H3DA tra55ic on 3 RA? an' H3A earer per5ormance.........................%!

"ist of Ta!es

Tale 1. ac*et 'ata connection relate' in5ormation elements in RR onnection 3etup Re9uestmessa0e...................................................................................................................................................... 8Tale 2. ac*et 'ata connection relate' in5ormation elements in RR onnection 3etup messa0e...........8

Tale #. ac*et 'ata connection relate' in5ormation elements in RR onnection 3etup ompletemessa0e...................................................................................................................................................... !Tale >. ac*et 'ata connection relate' in5ormation elements in Activate D onte=t Re9uest messa0e................................................................................................................................................................... 1"Tale . ac*et 'ata connection relate' in5ormation elements in Ra'io ?earer Recon5i0uration messa0e................................................................................................................................................................... 12Tale $. U;T3 @o3 attriutes...................................................................................................................1!Tale % @o3 ne0otiation at D conte=t setup..........................................................................................2"Tale 8. @o3 values 5or 'i55erent tra55ic classes.........................................................................................2"Tale !. Reports an' +s relate' RT 3 RA? accessiility......................................................................22Tale 1". Reports an' +s relate' RT 3 RA? retainaility.....................................................................2>Tale 11. Reports an' +s relate' H3DA accessiility.............................................................................28Tale 12. R parameters relate' to &GDH state selection an' release..........................................#"

Tale 1#. Recommen'e' parameters 5or H3DA U DH optimisation....................................................#>Tale 1>. Reports an' +s relate' H3UA accessiility.............................................................................#Tale 1. H3DA tra55ic an' throu0hput +s an' counters.......................................................................>"Tale 1$. H3UA tra55ic an' throu0hput +s an' counters.......................................................................>1Tale 1%. ;a=. user it rates 4ith 'i55erent RA3 5eatures........................................................................... >>Tale 18 +u 'eman' 5or H3DA hi0h itrates 6AT; siMe 1!$8 e9uals to = &1 an' 281"> to %=&17......>%Tale 1!. H3UA itrates 4ith 'i55erent ;a=TotalUplin*3ymolRate settin0s............................................>8Tale 2". H3UA con0estion control ounters.......................................................................................... #Tale 21. H3A moility counters an' +s............................................................................................... 8Tale 22. H3A retainaility counters an' +s 6Report( 3ervice/3ession Retainaility AnalysisR3RA"%!7............................................................................................................................................... $1Tale 2#. +s relate' po4er sharin0 et4een H3A an' R!! tra55ic..........................................................$$Tale 2>. +s relate' to channelisation co'e sharin0 et4een H3A an' R!! tra55ic................................$8Tale 2. C?T3 & reservation o5 DH earers.......................................................................................%Tale 2$ U/D & reservation 5or H3UA in RA3"$ Fle=i ?T3...............................................................%Tale 2%. +s relate' po4er sharin0 et4een H3A an' R!! tra55ic..........................................................%$

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 6827




1 +ntro'uction

The purpose o5 this 0ui'eline is to 0ive 0ui'ance 5or pac*et 'ata per5ormance optimisationtas*s. The main 5ocus is in H3A 6H3DA an' H3UA7 per5ormance ut also inter4or*in0 4ithRel!! RT services is covere'. ?asic H3A 5unctionality an' parameters is not 'escrie' hereut in H3A plannin0 0ui'e I2J. 3ome per5ormance relate' si0nallin0 charts are inclu'e' herealso asic @o3 in5ormation, 4hich 4ill e up'ate' 4ith RU1" 5eatures later. RT 5eatureoptimiMation is not 'escrie' here ut in ac*et 3che'uler :ptimiMation 'ocument I%J. There isalso not in5o aout 'i55erent H3A layers 4hich is covere' in H3A layerin0 0ui'e IJ. +t isrecommen'e' to loo* at separate capacity mana0ement 0ui'e 5or 'etaile' capacity analysis I8J.From + 0uarantee 'ocument I12J main + 'e5initions 4ith tar0et values are e=plaine', also5or H3A.

The structure o5 the 'ocument is 5ollo4in0 the 'ata call 5lo4. +n the e0innin0 there is chapter 5or 3 si0nallin0 sho4in0 'i55erent pac*et call setup cases an' moility oth in R level an' at U&si'e. Then there is a chapter 5or 3 RA? @o3 intro'uction. Then there is chapter 5or RT 3RA? per5ormance coverin0 tra'itional service level +s relate' to RT 3 RA?. A5ter that thereis chapter 5or H3A earer per5ormance optimiMation coverin0 accessiility, throu0hout, moilityan' retainaility relate' to H3DA an' H3UA. The last chapter is coverin0 the H3A an'Rel!! inter4or*in0 relate' mainly to C?T3 resource sharin0.

The per5ormance +s sho4n in the 'ocument is structure' ase' on the ne4 RA3"$ reportin0suite reports. This is online tool, ut +s can e analyse' also o55line 4ith Anatom.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $ 6827




#igure $. Scope of the Data Performance Optimisation Guide

2 3 Data connection si0nallin0

ac*et 'ata connection relate' si0nallin0 in5ormation is e=chan0e' in 'i55erent phases o5 thepac*et call. This section 'escries the main si0nallin0 in5ormation.

2.1 RR 3etup

RR connection setup proce'ure is per5orme' 4hen U& moves 5rom +'le mo'e to RRonnecte' mo'e. RR connection is re9uire' 5or any si0nallin0 5rom U& to the net4or* an' thesetup in5ormation contains also in5ormation relate' to pac*et 'ata connection. The RRconnection setup si0nallin0 is presente' in Fi0ure 2.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e % 6827




RR( RR onnection Re9uest 6RAH7

U& Ro'e ?

?A( Ra'io in* 3etup Re9uest

?A( Ra'io in* 3etup Response

AA( &stalish Re9uest

AA( &stalish on5irm

F( Do4nlin* 3ync

F( Uplin* 3ync

?A( 3ynchronisation +n'ication

RR( RR onnection 3etup 6FAH7

1 3ynchronisation

RR( RR onnection 3etup omplete 6DH7

#igure %. RRC connection setup signa!!ing.

The 5ist messa0e 5rom U& is the RR onnection 3etup Re9uest 4hich mainly in'icates theR that the U& 4ants to estalish si0nallin0 connection 4ith the RA. This messa0e contains

these in5ormation elements that can e relate' to pac*et 'ata connection estalishment.

A7 RelE U& ?7 RelE$ U&

RRC Request RRC Request

#i!e $. &'amp!es of RRC Connection Setup Re(uest messages

IE: Establishment cause 4hich 0ives R an in'ication o5 the service that the U& is re9uestin0.&stalishment cause 'epen's also on U& implementation. ause value NRe0istrationO is use' to

initiate <R3 Attach si0nallin0 an' ;easurement 9uantity aout the 9uality o5 the pilot si0nal. IE Access stratum release indicator in'icates the R on the release o5 the speci5ication the U&supports. Release $ U&s are capale o5 sen'in0 also the IE UE capability in'ication to in'icatethe H3DA an'/or H3UA capaility o5 the U&..

Ta!e $. Packet data connection re!ated information e!ements in RRC Connection Setup Re(uestmessage

)nformation e!ement *a!ue Description

&stalishment cause Re0istration For <R3 Attach

:ri0inatin0 Hi0h

riority 3i0nallin0

For D onte=t 3etup

;easurement @uantity &c/o L E2> +& / 2 &co use' 5or initial U an'D po4er calculation





Access stratum releasein'icator

6Asence L R!!7, RelE> / RelE / RelE$

Release o5 the RR5unctionality supporte' y U&

U& capaility in'ication Asence L o H3A,H3ED3H,

H3D3H&DH

+& availale only 5rom R$ U&s

The RRC Connection Setup is receive' 5rom R as reply to the re9uest messa0e. Thismessa0e mainly contains the con5i0uration o5 the si0nallin0 ra'io earers that 4ill e use' 5or the si0nallin0. +t also contains in5ormation 'e5inin0 the ne=t RR state an' a re9uest 5or U&capaility.

Ta!e %. Packet data connection re!ated information e!ements in RRC Connection Setup message


RR state in'icator ellEDH 3i0nallin0 continues al4ays inDH channel type in 3RA

apaility up'ate re9uirement True 3et NtrueO 5or FDD

UARF uplin* hannel numer U +& is provi'e' i5 the 5re9uencyis chan0e' 6can e 'one 'ueto DRR proce'ure7

UARF 'o4nlin* hannel numer D +& is provi'e' i5 the 5re9uencyis chan0e' 6can e 'one 'ueto DRR proce'ure7

The RRC Connection Setup Complete messa0e contains mainly the U& ra'io access capailityin5ormation. There is ran0e o5 in5ormation relate' to U& 'ata connection capaility, e.0. H3DAan H3UA physical layer cate0ory an' U& po4er class.


Message Message

#i!e %. &'amp!e of RRC Connection Setup Comp!ete message from Re!+, and Re!+- &s.

Ta!e /. Packet data connection re!ated information e!ements in RRC Connection Setup Comp!etemessage


H3ED3H physical layer

ate0ory

1E$> RelE an' later

&EDH physical layer

ate0ory

1E1$ RelE$

U& po4er class 1E>

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e ! 6827




2.2 ac*et 'ata connection setup

2.2.1 <R3 Attach A5ter the RR connection setup proce'ure the U& has estalishe' a 'e'icate' communicationlin* 4ith UTRA, it is in a position to sen' a messa0e to the core net4or* 63 core in this case7.Cith the <R3 attach the U& estalishes a <R3 moility mana0ement conte=t 4ith 3<3.

#igure /. GPRS 0ttach procedure

The purpose o5 the 3ecurity ;o'e proce'ure is to tri00er the start or cipherin0 5or the ra'ioearers o5 one core net4or* 'omain an' 5or all si0nallin0 earers. +t is also use' to start inte0rityprotection 5or all si0nallin0 ra'io earers.

The 3 core may optionally re9uest the U& to provi'e its i'entity, e.9. +;&+. This is 'one usin0the Identity Reuest messa0e.

2.2.2 3ervice Re9uestThe 3ervice Re9uest proce'ure is initiate' prior to D conte=t setup to 5orm a secureconnection et4een the 3<3 an' the U& 5or user 'ata. This is re9uire' i5 no other si0nallin04ith 3<3 has prece'e' the D conte=t setup. This coul' e the case 4ith ;T pac*et call,ut it is not supporte' y 3.

#igure 1. Service Re(uest procedure.

2.2.# D conte=t setupD conte=t 5orms the user 'ata connection et4een the U& an' internet or private net4or*. An+ a''ress is allocate' to the U& in the proce'ure. D onte=t 3etup proce'ure inclu'esRa'io Access ?earer 6RA?7 setup an' Ra'io ?earer setup proce'ures. This is 'one to DH "/".

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1" 6827




#igure ,. PDP conte't setup procedure.

The Activate !D! Conte"t Reuest messa0e inclu'es in5ormation relate' to the re9ueste'

service type an' 9uality, connection en' point 6Access point name7 an' re9ueste' + a''ress. Access point name can e use' to re9uest a connection to operator speci5ic services li*e CAor to internet i5 this is allo4e' y the operator.

Ta!e 1. Packet data connection re!ated information e!ements in 0ctivate PDP Conte't Re(uestmessage


Re9ueste' @o3 3ee 3ection #.

Re9ueste' + a''ress ?y 'e5ault + a''ress isallocate' automatically.

Access oint ame Access points are 'e5ine' inthe <<3 con5i0uration an'U& re9uest a connectionto/via speci5ic access point

Re9ueste' service type an' 9uality is 'e5ine' in the Re9ueste' @o3 in5ormation. 3ection #'escries more in 'etail the @o3 'e5inition parameters an' proce'ure. The D conte=t setupproce'ure is complete' 4ith the Activate !D! Conte"t Accept messa0e, 4hich contains mainlythe ne0otiate' @o3 an' +/D a''ress allocate' 5or the U&.

A7 Activate D onte=t Re9uest ?7 Activate D onte=t Accept

Message Message

#i!e /. &'amp!es of 0ctivate PDP Conte't Re(uest and 0ctivate PDP Conte't 0ccept messages.

The Activate !D! Conte"t Reuest messa0e tri00ers the 3<3 to start the RA? setupproce'ure. This is initiate' 4hen 3<3 sen's the RA# Assi$nment Reuest messa0e to theR, this messa0e is sent over the +uE3 inter5ace an' it contains the @o3 o5 the RA?. Thereception o5 the RA# Assi$nment Reuest messa0e tri00ers the a'mission control 6A7proce'ure in R an' the 5ollo4in0 ra'io earer setup proce'ure. The A al0orithm 'e5ines the

ma=imum it rate o5 the ra'io earer, tar0et ?&R an' other earer parameters.





+n 3 RA the initial it rate allocate' in the RA? setup proce'ure o5 the RT RA? is al4aysMero 6RA? "/"7. Thus there is no nee' 5or resource reservations in this phase. The Ra'io ?earer 3etup messa0e sent 5rom R to U& contains the ne=t state 6in 3 RA cellEDH7 someRa'io ?earer in5ormation 6R, TrH7, ut no it rate allocations. There is also no ra'io lin*

setup 4ith o'e ? at this phase, i.e. no transport an' C3 resources are reserve'.

Message

#i!e 1. &'amp!e of Radio 2earer Setup message.

:nce the RA? has een estalishe' the R sen's a measurement control messa0es to theU& in or'er to initiate the tra55ic volume measurements 6U& internal7 to0ether 4ith intra an' inter 5re9uency measurements. ;easurement control initiates the tra55ic volume measurements an'

'e5ines the reportin0 threshol's 5or tra55ic volume measurements 4hich are use' 5or the Ucapacity re9uests.

Message

#i!e ,. &'amp!e of 3easurement Contro! message.

2.2.> Data 5lo4 setup

The 'ata 5lo4 over the air inter5ace is setup a5ter a capacity re9uest 5rom either U& or internallyR. Typically U& initiates the connection to the server an' the capacity re9uest comes 5romthe U&. The 'ata 5lo4 setup involves pac*et sche'ulin0, channel type selection an' resourcereservation 5or the selecte' connection type.

#igure -. Capacity re(uest and resource a!!ocation signa!!ing for packet data ca!!. 4SDP054SP0

U& sen's the %easurement Report messa0e 5or &vent >A in'icatin0 that there is some 'ata inthe u55ers. This measurement report is han'le' as capacity re9uest y the pac*et sche'uler inthe R, 4hich sche'ules the capacity re9uest. The sche'ulin0 operation starts 4ith channeltype selection proce'ure, 4here the R ma*es a selection et4een H3A, H3DA, DH or





common channel usa0e. 3che'ulin0 inclu'es also allocation o5 it rates 5or DH earers6allo4e' transport 5ormat set7 ase' on R parameters an' loa' con'itions.

Message

#i!e -. &'amp!e of 3easurement Report message.

The selecte' ra'io earer con5i0uration is sent in the Radio #earer Reconfi$uration messa0e tothe U& an' 4ith the 5ollo4in0 Radio &in' Reconfi$uration !repare messa0e to the o'e ?.

Ta!e ,. Packet data connection re!ated information e!ements in Radio 2earer Reconfigurationmessage


RR state in'icator cellEDH, cellEFAH The initial it rate allocation istypically 'one to DH channelat pac*et call setup

Uplin* transport channel

Type

DH, RAH, &EDH 3electe' U the channel type

Do4nlin* transport channel

Type

DH, FAH, H3ED3H, DH H3D3H

3electe' D the channel type

;AE' DU siMe ##$ or $$ ##$ use' as 'e5ault in 3RA, $$ use' 5or hi0her

H3DA 'ata rates.

;a=imum channelisation co'es s5>, 2s5>, 2s52an'2s5> ;a=imum hannelisationco'e con5i0uration 5orH3UA.

3ervin0 <rant value "E#%, #8 +nitial 0rant value 5or H3UA,#8 means no 0rant. Value is'e5ine' y ?T3 an' si0nalle'to R an' to U& in this +&.

3prea'in0 5actor 6U7 >E128 ;inimum sprea'in0 5actor o5the U DH channel.

;easurement o4er :55set E$..1# '? ;easurement po4er o55set P

in'icatin0 the current availaleH3DA po4er relative to pilot.U& utilises the value in @+reportin0.

UARF uplin* hannel numer U +& is provi'e' i5 the 5re9uencyis chan0e' 6not 'one inpac*et call setup7

UARF 'o4nlin* hannel numer D +& is provi'e' i5 the 5re9uencyis chan0e' 6not 'one inpac*et call setup7


opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1# 6827




Message Message

#i!e 6. &'amp!e of Radio 2earer Reconfiguration message.

The U& ac*no4le'0es the Radio #earer Reconfi$uration messa0e 4ith a Radio #earer Reconfi$uration Complete messa0e.

R or'ers the U& 4ith the %easurement Control messa0e to stop the tra55ic volumemeasurements, i5 the U& has een allocate' the ma=imum availale it rate o5 H3A channeltype, as there is no use 5or the U&s to re9uest hi0her it rate. +5 the U& is allocate' a lo4er thanma=imum it rate, then the R mo'i5ies the &vent >A reportin0 threshol' accor'in0 to theallocate' it rate 6Fle"ible Up$rade 5eature provi'es possiility to 'e5ine it rate speci5icthreshol's7.

A7 RelE U&, initial U rate ?7 RelE$ U&, H3A allocate'

Message Message

#i!e 7. &'amp!e of 3easurement Contro! message used to modify8re!ease the ! traffic vo!umemeasurement.

2.2. RR state transitionsThe R can or'er the U& to chan0e the RR state 'urin0 the pac*et call. This is typically

per5orme' 'ue to pac*et connection inactivity or start o5 'ata transmission 6see Fi0ure %7. Chenthe U& is trans5erre' 5rom &GDH to &GFAH state, the ra'io earer is recon5i0ure' touse common channels 6RAH/FAH7 4ith Radio #earer Reconfi$uration proce'ure. The!hysical &ayer Reconfi$uration proce'ure is use' to trans5er the U& to/5rom the &GH an'URAGH 6RU1" 5eature7 states. +n this proce'ure the physical layer an' transport channelresources are release' ut R? 6coul' e 4ith 3R? only7, RA? an' D conte=t remain activeto4ar's +uEinter5ace.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1> 6827






#igure <. Transition from C&"";#0C4 to C&"";PC4 =R0;PC4> with Radio 2earer Reconfiguration procedure.

A7 R? recon5i0uration5rom &GDH to &GFAH

?7 hysical channel recon5i0uration5rom &GFAH to &GH

Message

Message

#i!e <. &'amp!e of Radio 2earer reconfiguration and Physica! channe! reconfiguration messagesused in the RRC state transitions.

The reEactivation o5 the 'ata connection can e initiate' y the U& y usin0 the Cell Updatemessa0e 6cause U 'ata transmission, see Fi0ure 1" an' File 1" A7 or y the R y pa0in0the U&. The R either *eeps the U& in &GFAH or moves it to &GDH 4ith the Ra'io#earer Reconfi$uration proce'ure.

#igure $9. Transfer of the & to C&"";DC4 and reactivation of the data connection =cause " datatransmission>.

A7 ell up'ate ?7 Ra'io earer recon5i0uration 5rom &GFAH to &GDH6H3DA7

Message Message

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1$ 6827




#i!e $9. &'amp!e of 3easurement Contro! message used to modify8re!ease the " traffic vo!umemeasurement.

2.2.$ ac*et 'ata connection moility

The proce'ure use' 5or moility 'epen's on channel type in use. ormal DH channels utilisethe so5t han'over proce'ure an' in &GFAH/&GH states a cellEreselection proce'ureis use' to0ether 4ith ell Up'ates. +n &GDH 4ith H3A channels the moility is in mostcases per5orme' 4ith the so5t han'over proce'ure comine' 4ith 3ervin0 H3ED3H cellchan0e, 4hich is re9uire' as H3DA 'oes not support so5t han'overs. RA3"$ R supportsalso a H3DA cellEreselection proce'ure, ut this is availale only 4hen H3UA is not activean' servin0 cell chan0e is not activate'.

The 3ervin0 H3ED3H cell chan0e can e tri00ere' y multiple 'i55erent tri00ers

− U& ase' measurements( erio'ical &co measurements, &vent1? or &vent1 to

remove current 3ervin0 H3ED3H cell− ?T3 3+Rerror measurements on 3ervin0 H3ED3H cell

− oss o5 U synchronisation in'ication 5rom ?T3

The 3ervin0 H3ED3H cell chan0e proce'ure can e 5ori''en in some cases li*e 4hen interER 3H: is not supporte' or the 3ervin0 H3ED3H cell chan0e is not enale'. +n these casesthe chan0e o5 cell is per5orme' via &GFAH.

An e=ample o5 si0nallin0 5or 3ervin0 H3ED3H cell chan0e 4ith 3H: is presente' in Fi0ure 11.This e=ample starts 4ith Active set up'ate to a'' the ell2 to the active set. The start o5 3H:tri00ers also the hysical hannel Recon5i0uration proce'ure 6see File 11 A7 that is use' to

chan0e the po4er o55set o5 @+, @ an' A its in the H3EDH, as RA3"$ R uses'i55erent values 5or sin0le lin* an' 3H: connections. Also the perio'ical &co measurementsare activate' 5or all active set cells. The 'ecision 5or the 3 is 'one ase' on these perio'icalmeasurements.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1% 6827




#igure $$. Serving 4S+DSC4 ce!! change triggered y periodica! &cNo measurements.

The Ra'io ?earer Recon5i0uration messa0e is use' to in5orm the U& aout the chan0e o5 theservin0 H3ED3H cell 6see File 117. This in5ormation is in'icate' in the +&( 3ervin0 H3ED3H+n'icator 5or R.

A7 hysical channelrecon5i0uration to3H: con5i0uration

?7 hysical channelrecon5i0uration tosin0le lin*con5i0uration

7 ;easurement controlmessa0e use' to activatethe perio'ical &comeasurements

D7 Ra'io earerrecon5i0uration tochan0e servin0 H3ED3H cell

Message Message Message Message

#i!e $$. &'amp!e of messages used for Serving Ce!! Change procedure.

The 3 can e tri00ere' also y an &vent 1? to remove the current servin0 H3ED3H cell5rom the active set 6see Fi0ure 127. +n this case the Ra'io ?earer Recon5i0uration messa0e isuse' 5irst to chan0e the servin0 H3ED3H cell an' then the Active 3et Up'ate to remove theprevious servin0 H3ED3H cell 5rom the active set. +5 there is only one cell in active set a5ter theup'ate, then the hysical hannel Recon5i0uration is use' to chan0e to @+, A an' Ao55sets to the sin0le lin* values.





#igure $%. Serving ce!! change triggered y &vent $2 on the serving 4SDSC4 ce!! =no N20Psigna!!ing presented>.

The servin0 H3ED3H cell chan0e can e per5orme' 4ith har' han'over 4hen the 3H: is notpossile, e.0. in interER moility i5 interER 3H: is not supporte'. Fi0ure 1# presents thesi0nallin0 o5 an interER moility 4ith H3A. The interER cell chan0e tri00ers also the U&apaility &n9uiry an' UTRA ;oility +n5ormation proce'ures.

#igure $/. )nter+RNC serving 4S+DSC4 ce!! change with hard handover =no N20P signa!!ingpresented>.

H3ED3H +3H: si0nallin0 can e seen elo4. First there 4ill e ra'ioGearerGrecon5i0uration toDH, theen compresse' mo'e 4ith physicalGchannelGrecon5i0uration, cell chan0e or'er 6:7to <R3, then AU B RAU an' 5inally imme'iate assi0nment to start 'ata 5lo4 in &<R3.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 1! 6827




# 3 RA? @o3 parameters

#.1 3peci5ication

A set o5 U;T3 earer attriutes have een 'e5ine' to speci5y the U;T3 service. They are liste'on the tale elo4. Chen a U;T3 earer is estalishe', mo'i5ie' or release', aspects such asthe U& capailities, suscription pro5iles an' net4or* speci5ic @o3 pro5iles have to e ta*enun'er consi'eration.

Ta!e -. 3TS ?oS attriutes.

#.2 De5inition o5 3 RA? @o3 in connection setup

U& initiates the 3 RA? setup y sen'in0 a D conte=t re9uest to the 3<3 617. This D

onte=t Re9uest contains the reuested (oS. This initiates the @o3 ne0otiation proce'ure.





Ta!e 6 ?oS negotiation at PDP conte't setup.

3<3 compares the reuested (oS to the (oS profile in HR 63ee Tale 87. The @o3 pro5ile is'e5ine' 5or each suscrier per Access oint 6A7 in the Home ocation Re0ister 6HR7 an'

each D conte=t has to ne0otiate its o4n @o3 pro5ile. @o3 pro5iles 5or 'i55erent D conte=tso5 one suscrier can all e 'i55erent. +n o*ia R!! HR, @o3 attriutes are con5i0urale.

o*ia 3<3 'o4n0ra'es the @o3 i5 necessary an' sen's the ne0otiate' @o3 to the <<3. 627The ne0otiate' @o3 is limite' y the appropriate values 'e5ine' 5or each tra55ic class in the#< speci5ication T32#.1"%. The limitations 5or the tra55ic classes are accor'in0 to the5ollo4in0 Tale 8.

Ta!e 7. ?oS va!ues for different traffic c!asses.

+5 a 3ervice ase' @o3 control 5eature is use' in o*ia <<3 6Rel. 7, the <<3 may restrictthe ne0otiate' @o3 5urther. The <<3 session mana0ement an' a'mission control 5unctionselects the treatment class 6TR&7 ase' on use' access point an' service 6service 'etectionan' s4itchin07. The selecte' TR& is mappe' to the #< @o3 attriutes in the <<3 5or the@o3 ne0otiation 4ith the 3<3. <<3 can not allocate hi0her @o3 than re9ueste' y 3<3.6#7





> RT 3 RA? per5ormance

+t is 4orth o5 mentionin0 here that RA + 'oes not al4ays mean en' user perception. 3o +5 RT RA? 'rops it is possile that en' user 'oes not see it 'ue to RA? reEestalishment

proce'ure, 5or e=ample.

>.1 Accessiility

+n normal net4or* con'itions there shoul' not e RT 3 RA? access 5ailures as there is noresource reservation 'one in the RA? setup an' access phases 5or RT RA?.

The RA? setup proce'ure is starte' 4ith RA? Assi0nment re9uest messa0e 5rom 6seeFi0ure 7. The RT 3 RA? setup 'oes not re9uire any resource reservation as no ra'io lin* issetup at his phase.

Hi0h level RA? + E RG1%a RA? 3etup an' Access omplete Ratio 5or RT 3ervice 5romUser perspective can e use' to monitor RA? accessiility 5rom user point o5 vie4. o4per5ormin0 cells can e then ran*e' to more 'etail analysis.

%T_PS_INTER RAB_STP_ATT_PS_BACKGRAB_STP_AT

INTER C_COMP_PS_ RAB_STP_ACBACKGC_COMP_PS_ RAB_STP_AC100RNC_156a

+

+=

The 5ailure reasons 5or RT 3 RA? 3etup an' Access are limite' to

− The 3 RA? setup attempt is not starte' 'ue to re9ueste' parameters not supporte' y

the U& or R

− ounters ( ;1""128 RA?G3TGFA+G3GU&GAA, ;1""12%RA?G3TGFA+G3G:TG3UGAR

− The RA? setup attempt counters are not up'ate' in this case

− RA? assi0nment 5ails 'ue to A

− ounters( RG#%$aL;1""11" RA?G3TGFA+G3G?A<GA,

RG#8>aL;1""111" RA?G3TGFA+G3G+T&RGA

− +s( RG1"%#a 6RA? 3etup FR 5or 3 +B? calls 'ue to A7

− There is no chec* o5 air inter5ace resources in RT 3 RA? setup

− R 'eci'es to reQect the 3 RA? re9uest 'ue to R internal 5ailure

− ounters( RG#8%a L ;1""1112 RA?G3TGFA+G3G?A<GR, RG#%!a

L ;1""11"% RA?G3TGFA+G3G+T&RGR

− +s( RG1"%$a 6RA? 3etup FR 5or 3 +B? calls 'ue to R7− The numer o5 RA? setup 5ailures cause' y on0oin0 relocation or har' han'over 5or 3

'ata interactive.

− ounters(;1""11"8GRA?G3TGFA+G3G+T&RGAH,

;1""111#GRA?G3TGFA+G3G?A<GAH

− +s( RG1"%>a 6RA? 3etup FR 5or 3 +B? calls 'ue to AH7

− o RR( Ra'io ?earer 3etup omplete messa0e receive' 5rom the U&

− ounters( RG>"#aL;1""11#2 RA?GAGFA+G3G+T&RG;3,

RG>">aL;1""11#> RA?GAGFA+G3G?A<G;3

− +s( RG1"%8a 6RA? 3etup Access FR 5or 3 +B? calls 'ue to U&7

Tale ! lists the reports an' +s relate' to RT 3 RA? per5ormance monitorin0 an' 5ailureanalysis. The RA? setup 5ailures 'ue to transmission 6RG1"%a7 are not relate' to RA?





setup phase ut to actual ra'io earer resource allocation or mo'i5ication, this + or relate'counters ;1""11"$ an' ;1""1111 are not supporte' in RU1" R.

Ta!e <. Reports and P)s re!ated NRT PS R02 accessii!ity

+ re5 + name / Areviation + unit

Report( 3ystem ro0ram R3RA"""

RG%$' ac*et 3ervice 3etup 3uccess Ratio 633R7 K

RG$1$a RA? Attempts 3 +nteractive an' ?ac*0roun'

RG1%aRA? 3etup an' Access omplete Ratio 5or RT 3ervice 5rom Userperspective K

Report( 3ervice/3ession Accessiility Analysis R3RA"%#

RG1"%1a RA? 3etup Attempts 5or 3 +B? calls

RG1"%2a RA? 3etup omplete' 5or 3 +B? calls

RG1"%#a RA? 3etup FR 5or 3 +B? calls 'ue to A K

RG1"%>a RA? 3etup FR 5or 3 +B? calls 'ue to AH K

RG1"%a RA? 3etup FR 5or 3 +B? calls 'ue to TRA3 K

RG1"%$a RA? 3etup FR 5or 3 +B? calls 'ue to R K

RG1"%%a RA? 3etup FR 5or 3 +B? calls 'ue to FR:S?3 K

RG1"%8a RA? 3etup Access FR 5or 3 +B? calls 'ue to U& K

RG1"%!a RA? 3etup Access FR 5or 3 +B? calls 'ue to R K

Fi0ure 1> presents an e=ample o5 3 RA? accessiility per5ormance. +t sho4s that the 5ailurerate are very lo4, typically elo4 "."> K an' that the R 5ailures are most typical in thise=ample. R 5ailures can e stu'ie' in more 'etail 4ith R internal +3U lo00in0. Fi0ure 1sho4s e=ample o5 RA? access 5ailure statistics.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2# 6827




#igure $1 PS R02 setup fai!ure rate statistics from !ive network.

#igure $,. PS R02 0ccess fai!ure rate statistics from !ive network.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2> 6827




>.2 Retainaility

The RT 3 RA? consists o5 +u earer an' ra'io earer. The ra'io earer can utilise multiple'i55erent channel types 6DH, H3A or H7. The retainaility o5 a RT 3 RA? 4ill 'epen'

on the +u earer an' ra'io earer per5ormance.

RA? active starts 4hen the R sen's a RAA( RA# ASSI)*%E*+ RES!,*SE messa0eto the 6see Fi0ure 7. RA? active is complete' 4hen the R receives a RAA( RA# ASSI)*%E*+ RE(UES+ messa0e 5rom the 4ith the +&( RA# release, an' thenac*no4le'0es that y sen'in0 a RAA( RA# ASSI)*%E*+ RES!,*SE messa0e to the . A5ter that, the R releases RA? resources, that is, RA? active phase en's e5ore the release.

RA? active is complete' also 4hen the R receives a RAA( IU RE&EASE C,%%A*Dmessa0e 5rom the , an' then releases RA? resources, that is, RA? active phase en's a5ter the release.

Hi0h level RA? + E RG%#$a 6RA? 3uccess Ratio, RT 3ervices, 5rom User erspective7can e use' to monitor RA? retainaility. o4 per5ormin0 cells can e then ran*e' to more'etail analysis.

failurea!"i#eRABB)&(Ireleaea!"i#eRABB)&(I!$le"i$'a!"i#eRAB

B)&(I"a"ePCi'failurea!"i#eRABB)&(Ifailurea!"i#eRAB100100RNC_*+6a

++−=

RA? active 5ails 4hen an inter5aceErelate' 6+u, +ur, +u, or Uu7 or R internal 5ailure occurs, an'the 5ailure causes the release o5 the RA? connection.

− ause' y ra'io inter5ace synchronisation

− +( RG1"8$a 6RA? Active FR 5or 3 +B? 'ue to RAD+:7

− ounters( ;1""118$G RA?GATGFA+G3G+T&RGRAD+:, ;1""11!2G

RA?GATGFA+G3G?A<GRAD+:

− release is re9ueste' 'ue to ra'io inter5ace synchronisation 5ailure

− ause' y ?T3 65or e=ample, ra'io lin* setup or recon5i0uration prolem7

− +( RG1"8%a 6RA? Active FR 5or 3 +B? 'ue to ?T37

− ounters( ;1""118%G RA?GATGFA+G3G+T&RG?T3, ;1""11!#G

RA?GATGFA+G3G?A<G?T3

− release is re9ueste' 'ue to ?T3 5ailure

− Anormal reason relate' to +uEinter5ace

− +( RG1"8a 6RA? Active FR 5or 3 +B? 'ue to +U7− ounters( ;1""118GRA?GATGFA+G3G+T&RG+U, ;1""11!1G

RA?GATGFA+G3G?A<G+U

− ause' y 'ri5t R proce'ures

− +( RG1"88a 6RA? Active FR 5or 3 +B? 'ue to +UR7

− ounters( ;1""11!"G RA?GATGFA+G3G+T&RG+UR, ;1""11!>G

RA?GATGFA+G3G?A<G+UR

− ause' y U&

− +( RG1"!1a 6RA? Active FR 5or 3 +B? 'ue to U&7

− ounters( ;1""1#!%GRA?GATGFA+G3G+T&RGU&,

;1""1#!8GRA?GATGFA+G3G?A<GU&

− ecause the U& is not respon'in0 to an RR messa0e or the U& is respon'in04ith such 5ailure messa0e that the connection must e release'

− ause' y inte0rity chec*





− +( RG1"8!a 6RA? Active FR 5or 3 +B? 'ue to +GH7

− ounters( ;1""118!GRA?GATGFA+G3G+T&RG+GH,

;1""11!GRA?GATGFA+G3G?A<G+GH,

− This counter is never up'ate'.

− 3ome reason not covere' y the other 5ailure counters

− +( RG1"!"a 6RA? Active FR 5or 3 +B? 'ue to R7

− ounters( ;1""11!"G RA?GATGFA+G3G+T&RGR, ;1""11!$G

RA?GATGFA+G3G?A<GR

+t shoul' e note' that RA? retainaility is not same than R? retainaility, ecause it is possileto reEestalish the R? in si'e RA 6y settin0 T#1 parameter 0reater than "7 4hen havin0e=istin0 RA? connection to the core net4or*. +n RU1" it is possile to have RA? reEestalishment also 5or Voice.

Tale 1" lists the relevant reports an' +s 5or RT 3 RA? retainaility monitorin0 an'

trouleshootin0.

Ta!e $9. Reports and P)s re!ated NRT PS R02 retainai!ity


Report( 3ystem ro0ram R3RA"""

RG$1$a RA? Attempts 3 +nteractive an' ?ac*0roun'

RG$1 RA? 3uccess Ratio, RT 3ervices, 5rom et4or* erspective K

RG%#$a RA? 3uccess Ratio, RT 3ervices, 5rom User erspective K

Report( 3ervice/3ession Retainaility Analysis R3RA"%!

RG1"8>a RA? 3etup Access ompletions 5or 3 +B?

RG1"8a RA? Active FR 5or 3 +B? 'ue to +U K

RG1"8$a RA? Active FR 5or 3 +B? 'ue to RAD+: K

RG1"8%a RA? Active FR 5or 3 +B? 'ue to ?T3 K

RG1"88a RA? Active FR 5or 3 +B? 'ue to +UR K

RG1"8!a RA? Active FR 5or 3 +B? 'ue to +GH K

RG1"!"a RA? Active FR 5or 3 +B? 'ue to R K

RG1"!1a RA? Active FR 5or 3 +B? 'ue to U& K

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2$ 6827




#igure $-. NRT PS R02 retainai!ity ana!ysis

?elo4 is one e=ample o5 RT 3 RA? retainaility, it can e seen that 5ail 'ue to ?T3 has een'ecrease' y intro'ucin0 the 1$ *?its/s U return channel 'urin0 1.>. This is ecause 'ue tochan0e i5 U return channel itrate there is more channel element 6&7 capacity in the tar0etcell to han'le 3H: 5or RT.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2% 6827

o4 RT 3 RA?retainaility 6cell7

hec* RT 3 ra'io earer 5ailures 'ueto ra'io

hec* ?T3 HC resources, can e cause'y 5aile' 3 'ue to H3DA ret channel

hec* core net4or* parameter settin0s

+nter R moility

R +nternal rolem

6

Terminal rolem

o Actionee'e'

RT 3 RA?active 5ail 'ue to

ra'io

RT 3 RA?active 5ail 'ue

?T3


+u

ReQectionsRT 3 RA?active 5ail 'ue to

+ur


R


U&

o

es

es

es

es

es

es

es

o

o

o

o

o




#igure $6 &'amp!e of PS NRT R02 0ctive fai! change due to 2TS





H3A earer per5ormance

.1 Accessiility

H3UA cannot e estalishe' 4ithout H3DA i5 H3UA is supporte' the H3DA U returnchannel is H3UA instea' o5 R!!. +n oth cases, the Hi0h level 3etup proce'ure is the sameR starts y allocation a "/" *ps connection an' selection et4een DH an' &EDH is thencomplete' 4hen R receives the uplin* or 'o4nlin* capacity re9uest.

Hi0h level H3DA + E RG$"a can e use' to monitor H3DA accessiility 5rom user pointo5 vie4. o4 per5ormin0 cells can e then ran*e' to more 'etail analysis.

&(uation $. RNC;-9,a 4SDP0 accessii!ity from user point of view

The H3GD3H setup an' 3election can 5ail 'ue the many reasons. Chen monitorin0 H3DAsetup 5ailure counters it is important to un'erstan' root cause o5 the 5ailure. Typically setup5ailures in'icate resource shorta0e, an' as can e seen 5rom 5lo4 chart elo4 6Fi0ure 187, theseprolems are o5ten relate' to H3DA U DH return channel rather than H3DA ;acE' 5lo4itsel5. ?ut i5 there are not enou0h resources to set up H3DA U DH return channel, theH3DA ;acE' 5lo4 setup 4ill 5ail also.

#igure $7 @ 4SDP0 0ccessii!ity #ai!ure 0na!ysis

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 2! 6827

o4 H3DAaccessiility 6cell7

hec* umer o5 simultaneous H3DAusers in ?T3 or cell level 'epen'in0 on the

sche'uler type

hec* ?H hannel &lement resourceUsa0e6ac* o5 & 5or U return hannel7

hec* ?H U o4er on0estion6ac* o5 Ra'io resources 5or U returnh.7

hec* ?H AA2 +u con0estion6ac* o5 +u resources 5or U return h.7

hec* R? recon5i0uration 5ailure rate6Terminal rolem7

6hec* R Unit loa' 6D;<7, ma=

numer o5 users/R, D3 5ailures an'5aulty alarms

o Actionee'e'

Too many H3DAusers reache'

H3DA 3etup Fail'ue ?T3

ReQection o5 UReturn hannel

ReQections

H3DA 3etup Fail+u 6?oth U B

D7

H3DA 3etup FailU&

H3DA 3etup Fail

R +nternal

o

es

es

es

es

es

es

es

o

o

o

o

o

∑ •

++

++++

+++

+++++

+

=

%100

_ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _

RNC_605a

BGR DSCH HS IUB FAILSETUP INT DSCH HS IUB FAILSETUP

BGR DSCH HS BTS FAILSETUP INT DSCH HS BTS FAILSETUP BGR DSCH HS UE FAILSETUP

INT DSCH HS UE FAILSETUP BGR DSCH HS RNC FAILSETUP INT DSCH HS RNC FAILSETUP

BGR RET DSCH HS REJ INT RET DSCH HS REJ BGRUSERS HSDPA MAX SEL DCH INT USERS HSDPA MAX SEL DCH BGR FLOW DSCH HS ALLO INT FLOW DSCH HS ALLO

BGR FLOW DSCH HS ALLO INT FLOW DSCH HS ALLO




?esi'es o5 reasons liste' in Fi0ure 18, the H3DA accessiility prolems can e also relate' to+uE3 or +E?? capacity prolems. H3DA channel type selection can e also 5ail 'ue theDo4nlin* po4er i5 static po4er allocation is use' instea' o5 Dynamic resource/po4er allocation.

There shoul' e also enou0h resource to set up H3G3H.

Tale 11 lists the relevant reports an' +s 5or H3DA R? accessiility monitorin0 an'trouleshootin0. ote( H3DA access 5ailure rate +s are currently 'e5ine' as K o5 all 5ailuresnot all selections.

Ta!e $$. Reports and P)s re!ated 4SDP0 accessii!ity


Report: System !ro$ram R*SRA*---

RG!#"a ac*et 3ession Attempts 65or R!! B H3A7

RG!1$a ac*et 3ession 3etup 3uccess Ratio 5or RT 65or R!! B H3A7 K

RG$1>a H3ED3H selections 65or H3DA only7

RG$"a H3DA Resource Accessiility 5or RT Tra55ic 6user7 65or H3DA only7 K

RG!2$a H3DA attempts 65or H3DA an' H3UA7

RG!1>a H3DA 3etup 3uccess Ratio 5rom user perspective 6H3DA B H3UA7 K

Report: Service.Session Retainability Analysis RSRA*-/0 1%2-334 %2--35

RG!#"a ac*et 3ession Attempts 65or R!! H3A7

RG!$%a 3 all 3etup FR 'ue to A 65or R!! H3A7 K

RG!a 3 all 3etup FR 'ue to ?T3 65or R!! H3A7 K

RG1"8"a 3 3etup FR 5or +B? 'ue to lac* o5 D;U 65or R!! H3A7 K

RG1"81a 3 3etup FR 5or +B? 'ue to Transport 65or R!! H3A7 K

RG1"82a 3 3etup FR 5or +B? 'ue to U& 65or R!! H3A7 K

RG1"8#a 3 3etup FR 5or +B? 'ue to :thers 65or R!! H3A7 K

RG$1>a H3ED3H selections 65or H3DA only7

RG$$>a H3DA Access FR 'ue to R 65or H3DA only7 K

RG$%>a H3DA Access FR 'ue to ?T3 65or H3DA only7 K

RG$$$a H3DA Access 5ailures 'ue to +u 65or H3DA only7 K

RG$$8a H3DA Access FR 'ue to U& 65or H3DA only7 K

RG$$2a H3DA Access FR 'ue to U DH 65or H3DA only7 KRG$%2a H3DA Access FR 'ue to A;RH3A 65or H3DA only7 K

RG$$"a DH 3electe' 'ue to too many H3DA users 65or H3DA only7 K

Fi0ure 1! presents an e=ample o5 H3DA accessiility +s 5rom live net4or*. +t sho4s that theRG!1$a, RG$"a an' RG!1>a 5ollo4 the same tren' an' on other han' the 3 RA?accessiility is 1""K all the time as e=pecte' 6see 3ection >.17.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #" 6827




#igure $<. &'amp!e 4SDP0 accessii!ity P)s from !ive network.

Fi0ure 2" presents an e=ample o5 H3DA access 5ailure cause. +n this e=ample the ?T3 5ailuresare most 'ominatin0, 4hich in'icates H3DA return channel allocation 5ailure 'ue to ?T3 HCresource shorta0e. There is also si0ni5icant level on R an' +u 5ailures. H3DA access 5ailurerate +s are currently 'e5ine' as K o5 all 5ailures not all selections.

#igure %9. &'amp!e 4SDP0 accessii!ity fai!ure causes.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #1 6827




H3DA setup can 5ail 'ue the numer o5 simultaneous users reache'. There are t4o mainsolutions availale increase the capaility o5 the net4or* or 'ecrease' the numer o5 U&s inDH. The net4or* capaility can e increase' y intro'ucin0 hi0h 3hare 3che'uler 5or ??e55iciency 6ma= >8 users/sche'uler7 or >8 users/cell 5eature, or even secon' sche'uler. +t shoul'

also e consi'erin0 i5 tra55ic alancin0 et4een nei0hourin0 sites is possile.

Typically cell have amount o5 H3DA user 4hich 'oes not have any 'ata in the u55ers ut arestill counte'. This can e, 5or e=ample, 'ue the very lon0 inactivity timer. o4 utilisation an'inactivity timer parameter 5or H3DA an' U DH return channel can e tune' to increaseH3DA accessiility in case ma=imum amount o5 H3DA user is reach. Tale 12 presentse=ample parameter sets tar0ete' to 'ecrease H3DA utilisation. The tra55ic volume relate'parameters can e use' to 'elay the transition 5rom &GFAH to &GDH. The ;ADE'5lo4 throu0hput an' utilisation parameters can e use' to release the H3DA allocation 5aster.

Ta!e $%. RNC parameters re!ated to C&"";DC4 state se!ection and re!ease.

Fi0ure 21 presents an e=ample o5 the H3DA accessiility 6RG$"a7 an' Fi0ure 22 thecorrespon'in0 5ailure analysis. The results sho4 that the main accessiility 5ailure cause is toomany H3DA users. This 4as 5irst optimise' y increasin0 the sche'uler capacity 5rom 1$users/?T3 to >8 users/?T3 61$/cell7, the result 4as a clear 'ecrease in the 5ailure rate. Thesecon' optimisation action 4as to chan0e the lo4 tra55ic volume threshol' in or'er to'ecrease/postpone the transitions to &GDH. This chan0e sho4s a clear improvement inaccessiility an' 5ailure rates. The accessiility 4as increase' 5urther y activatin0 the >8users/cell in the R, thus enalin0 hi0her numer o5 users in cell level. This remove' most o5 the 5ailures 'ue to numer o5 H3DA users.





#igure %$. 4SDP0 accessii!ity with optimisation.

#igure %%. 4SDP0 acessii!ity fai!ure ana!ysis with optimisation steps.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e ## 6827




.1.1 H3DA U Return hannelH3DA U return channel reQections 'ue A can e monitore' 4ith RG$$2a E H3DA accessFailure Rate 'ue the U DH. +n RA3"$, U A coul' e ase' on oth throu0hput an' po4er

ase' 3 call al0orithm 'epen'in0 on the parameter settin0s. !r"&oad%ar$in%a"DC6 parameter 'e5ines inter5erence mar0in 5or the ma=imum U DH loa'. Usin0 'e5ault value o5 2'? 6#%K loa'7 can cause H3DA U return channel reQections 'ue A to increase. +t isrecommen'e' to remove impact o5 this parameter y settin0 it to value " '? 6throu0hput ase' A al0orithm not in use7, see Fi0ure 2#. This parameter is vali' 5or all R!! 3 earers, not only5or H3DA U return channel.

#igure %/. &ffect of Pr'"oad3argin3a'DC4 on 4SDP0 return channe! accessii!ity.

H3DA ?T3 & resource reservation is al4ays 5i=e', an' cannot e use' 5or other purpose utH3DA only. This H3DA ?asean' resource reservation is symmetric 5or uplin* an' 'o4nlin*,an' 'epen's on sche'uler type 6share' or 'e'icate'7 an' activate' 5eatures 6e.0. H3DA 1$users vs. >8 users7.

Ho4ever, resources are not reserve' 5or H3DA U return channel. There have to e enou0h

5ree U & capacity availale to setup H3DA U return channel or H3DA setup 4ill 5ail. +nRA3"$, the U DH 'ata rate o5 1$ *ps 5or H3DA return channel is supporte' in a''ition tocurrently supporte' $>, 128 an' #8> *ps itrates. 1$ *ps 5or H3DA return channel 5eature,to0ether 4ith ?3 or T?:, can e use' to optimise resources 5or H3DA U DH.

&=istin0 RA3" an' RA31 5eatures support the 'ynamic use o5 lo4er DH 'ata rates 5or H3DA U DH return channel. The 5ollo4in0 e=istin0 5unctionalities are applie' to the H3DAU return channel 6U DH7(

− riority ase' sche'ulin0 an' :verloa' control ?3 can release or 'o4n0ra'e e=istin0

RT allocation i5 there is other user re9uestin0 initial capacity in con0este' situation.

This means that 5or e=ample in case o5 & con0estion, the ?3 'o4n0ra'e e=istin0DHs 5rom hi0her 'ata rates to 1$ *ps one y one until the ma=imum numer o5 usersin the ?T3 is achieve'. on0estion o5 5ollo4in0 resources can tri00er enhance' priority

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #> 6827




ase' sche'ulin0 5unction( D po4er, U inter5erence, 'o4nlin* sprea'in0 co'e, ?T3HC 6&7 an' +u transmission

− Throu0hput ase' :ptimiMation E T?: o5 3 Al0orithms 5eature 'o4n0ra'es the DH it

rate 'o4n to 1$ *ps i5 the hi0h it rate DH is use' ine55iciently 4hich help savin0

resources 6mainly ?T3 &, transmission an' 'o4nlin* sprea'in0 co'e resources7− Up0ra'e o5 RT DH Data Rate 6ormal or Fle=ile up0ra'e7

− RTEoverERT

RT over RT an' preEemption actions 5or any reason shall not e tar0ete' to ;acE' 5lo4.Ho4ever, RT over RT actions can e tar0ete' to U return channel DH, causin0 also therelease o5 ;AE' 5lo4.

;ore 'etail 'escription o5 3? an' T?: can e 5oun' 5rom I%J

As can e seen 5rom Fi0ure 2> elo4, there is clear correlation et4een U & usa0e an' H3E

D3H setup 5ailures. Chen ;a=imum use' & 'rop elo4 12> 65rom ma=. 1287, the H3E3&TUGFA+G?T3GH3GD3HG?<R 'rops si0ni5icantly

#igure %1. Re!ation etween " C& usage and 4S+DSC4 setup fai!ures

Activation o5 T?: an' H3DA 1$ *ps Return channel improves H3DA accessiility 6lue line7as can e seen 5rom Fi0ure 2 elo4. This is ecause o5 improve' U & resource usa0e.





#igure %,. 0ctivation of T2O and $- kps return channe!.

1$ *ps Return channel DH 'ata rate support 5or H3DA is RA3"$ optional 5eature, 4hich cane activate' y the operator 4ith mana0ement parameter 6SD!A278#!SReturnChannel9;inimum allo4e' it rate 5or H3DA U return channel is set 4ith parameter 6SD!AminAllowed#itrateU&. imitation shoul' e 'isale' 4ith the parameter #itRateSet!S*R+9

Chen 1$ *ps is activate', the throu0hput ase' optimisation an' 5le=ile up0ra'e 5eatures cane activate' 5or H3DA return channel 4ith parameter DynUsa$e6SD!AReturnChannel 6Thisre9uire that T?: or/an' FU 5eatures are also activate' in the net4or*79 +able 2 elo4 presentrecommen'e' parameter settin0s 4hen 1$ *ps 5eature is use'.

Ta!e $/. Recommended parameters for 4SDP0 " DC4 optimisation

arameter ame 3cope Ran0eDe5ault

6RA3"$7

Recommen'e'

Value

H3DA1$?3Returnhannel R" 6'isale'7

1 6&nale'7Disale' &nale'

H3DAminAllo4e'?itrateU R1$*ps 617, $> ps6#7, 128 *ps 6>7,#8>*ps 6$7

$> 1$

H3DAinitial?itrateU R1$*ps 617, $> ps6#7, 128 *ps 6>7,#8>*ps 6$7

$> 1$

?itRate3et3RT R

" 6pre'e5ine' it

set not in use7 16pre'e5ine' it set inuse7

" "

DynUsa0eH3DAReturnhannel :55 6"7, :n 617 o es

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #$ 6827




.1.2 H3UA AccessiilityH3UA cannot e estalishe' 4ithout H3DA, the U return channel is H3UA instea' o5 R!!.The 'ecision et4een DH an' &EDH allocation 5or a U& is ase' on the service 6RA?parameters7, resource availaility, multiERA? comination an' U& capaility. arameter EDC6(,SClasses 'e5ines 4hether certain tra55ic class an' tra55ic han'lin0 priority is allo4e' touse 5or H3UA. H3UA allocation is not possile i5 there is on0oin0 +FH: or +3H:measurements, the 5inal &DH active set siMe is not acceptale, H3DA moility is 'isale' or H3ED3H allocation is not possile. +5 the allocation o5 H3ED3H in 'o4nlin* is not possile,the 3 tries to allocate the DH in oth U an' D.

Hi0h level H3UA + E RG!1#a can e use' to monitor H3UA accessiility 5rom user pointo5 vie4. o4 per5ormin0 cells can e then ran*e' to more 'etail analysis

&(uation % @ RNC;<$/a 4SP0 0ccessii!ity from ser point of view

H3UA access is 'one in t4o phases, 5irst H3UA channel type has to e selecte' in channel

type selection proce'ure, i5 this proce'ure 4ill not allo4 H3UA channel type the H3UAselection 5ailure counters are tri00ere'. A5ter H3UA channel type is selecte' the actual H3UAra'io earer setup 4ill ta*e place an' is this 5ails the H3UA setup 5ailures are tri00ere'.H3UA selection an' setup 5ailures reasons are similar to H3DA. H3UA selection can also5ail i5 Active set siMe is not acceptale. Also, i5 H3DA ;acE' 5lo4 setup is 5ailin0, 5or e=ample,'ue the too many simultaneous users, the H3UA setup 4ill also 5ail.

Ta!e $1. Reports and P)s re!ated 4SP0 accessii!ity


Report: System !ro$ram R*SRA*---

RG!2#a &EDH selections RG!1#a H3UA Resource Accessiility 5or RT Tra55ic K

RG!28a H3UA attempts

RG!1a H3UA 3etup 3uccess Ratio 5rom user perspective K

Report: Service.Session Retainability Analysis RSRA*-/0 1%2-334 %2--35

RG!2#a &EDH selections

RG11"#a &EDH Allocation FR 'ue to A A3 K

RG!$8a U DH 3electe' 'ue to too many H3UA users K

RG!$!a D DH 3electe' 'ue to the H3DA po4er K

RG!%a &EDH ot 3electe' 'ue the ?T3 HC K

RG!$a &EDH 3etup FR 'ue to ?T3 K

RG11"a &EDH 3etup FR 'ue to Transport K

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #% 6827

%100

TE,C_-E_INET-P_.AI/_ SGR _E,C_-E_BSET-P_.AI/ S_INT _E,C_TRANSET-P_.AI/

S_BGR _E,C_TRANSET-P_.AI/ R_INT _E,C_OTESET-P_.AI/

R_BGR _E,C_OTESET-P_.AI/INT _E,C_BTS_ SET-P_.AI/ BGR _E,C_BTS_ SET-P_.AI/

GR /_BTS__B-/_,C_SET _BTS__IN-/_,C_SE/A_-SR_INT/_MA2_S-P-/_,C_SE

A_-SR_BGR /_MA2_S-P-/_,C_SE _INTCANC_NA_ASE,C_A//O_

_BGR CANC_NA_ASE,C_A//O_ R SS_E,C_BGA//O_S-CCE TSS_E,C_INA//O_S-CCE

R SS_E,C_BGA//O_S-CCETSS_E,C_INA//O_S-CCE

S-PA_ RNC_31+a_

•

+

+

++

+

=

∑

∑ty Accessibli




RG11"$a &EDH 3etup FR 'ue to U& K

RG11">a &EDH 3etup FR 'ue to :ther Failures K

#igure %-. 4SP0 0ccessii!ity fai!ure ana!ysis

Fi0ure 2% presents e=ample o5 H3UA selection 5ailures. This e=ample is 5rom the samenet4or* an' time perio' as H3DA access 5ailure e=ample in Fi0ure 2". ?oth H3DA an'H3UA access is limite' mainly y ?T3 HC.


o4 H3UAaccessiility

hec* umer o5 simultaneous H3UA users62"/cell, 2>/o'e? 7

hec* ?H hannel element resource usa0eU/D6?T3 in state that no capacity availale 5or&DH7

H3UA is not supporte' in 3H: ranch

hec* ?H hannel element resource usa0eU/D

hec* R? recon5i0uration 5ailure rate6Terminal prolem7

hec* AA2 connections 6not enou0h +D7 or3i0nallin0 prolems

o Actionee'e'

Too many H3UAusers reache'

U DH selecte''ue ?T3 HC

H3UA 5ail 'ueot Acceptale

Active 3et

H3UA 3etup Fail?T3

H3UA 3etup FailU&

H3UA 3etup FailTRA3

o

es

es

es

es

es

es

es

o

o

o

o

o

o

<o 5or trouleshootin06 &.0. R internal 5ailures7

H3UA 3etup Fail:ther

es

3 e t u p

5 a i l u r e s

3 e l e c t i o n

5 a i l u r e s




#igure %6. &'amp!e of 4SP0 se!ection fai!ure causes from !ive network.

Fi0ure 28 sho4s an e=ample o5 H3UA setup 5ailure causes. ;ost 5ailures are 'ue to :ther reason, ut there is also some level o5 transport an' ?T3 5ailures.

#igure %7. &'amp!e of 4SP0 setup fai!ure causes from !ive network.

DH is selecte' instea' o5 &DH i5 ;a=imum amount o5 H3UA allocations is reache' either in

cell or in ?T3 <. ;a=imum amount o5 H3UA users are limite' either 4ith parameter or license. Asolute ma=imum value is 'e5ine' 4ith license NH3UA, ?asic #/12/2> an' parameters%a"*umberofEDC6Cell an' %a"*umberEDC6&C) 'e5ine ma=imum numer o5 &EDH

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e #! 6827




allocations in the cell an' ?T3 < respectively. imitations are also vali' 5or 3o5t an' so5ter 6cell only7 H: ranch a''itions. ell speci5ic 3 use a value 4hich lo4er than these t4o values6parameter or license7. arameter *umberEDC6ReservedS6,#ranchAdditions 1default;35'e5ines the numer o5 &EDH allocations that are reserve' only 5or so5t an' so5ter han'over

ranch a''itions in the cell an' 5or so5t han'over ranch a''itions in the ?T3 <. The Value o5 this parameter is sutracte' 5rom oth, the ma=imum numer o5 &EDH allocations in the cellan' the ma=imum numer o5 &EDH allocations in ?T3 < to achieve correspon'in0ly thema=imum numer o5 ne4 &EDH allocations in the cell an' ?T3 <. The values o5 theseparameters are chec*e' only in &EDH allocation an' &EDH ranch a''ition phases.

The H3UA asean' processin0 re9uirements are symmetric across the U an' D 'irections.The minimum static allocation o5 8 & 65or oth U an' D7 is reserve' as soon as H3UA isenale' at a C?T3. Cith the e=ception o5 the 5irst 8 &Os, the & allocation 5or H3UA is'ynamic an' 'epen'in0 upon oth the numer o5 H3UA connections an' loa' 0enerate' ythe DH tra55ic. +n the & allocation, DH has a hi0her priority than H3UA, DH capacityre9uest are ale to preEempt the set o5 & allocate' to H3UA 64ith the e=ception o5 the

minimum static allocation o5 8 &7. +n a''ition to re9uire' 8 channel elements each active &EDH user re9uires channel element capacity. ?T3 in5orms R that &EDH users can e ta*enin 4hen at least #2 channel elements 6'ynamic reservation7 are reserve' 5or &EDHs. +5 there isnot enou0h & 5or H3UA, the H3UA setup 4ill 5ail.

There seems to e also correlation et4een &DH setup 5ailures an' ;a=imum & usa0es. AsH3UA & resource reservation is symmetric, oth U an' D shoul' e monitore'.

#igure %<. Re!ation etween C& usage and 4SP0 setup and se!ection fai!ures

.2 H3A Throu0hput an' RTT

Throu0hput cannot e 0uarantee' 5or 3 RT +nteractive or ?ac*0roun' class servicesinclu'in0 H3A. ;ost o5 the resources, li*e Air +nter5ace an' +u, are share' et4een the userscausin0 per5ormance 'e0ra'in0 4hen amount o5 users in the cell increase. Chen monitorin0H3DA throu0hput 4ith the counters, it is important to monitor numer o5 simultaneous H3A

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >" 6827




users as 4ell. Throu0hput measurements to0ether 4ith other counters can e use' i'enti5ypossile causes 5or lo4 throu0hput. Follo4in0 has impact to user an' cell throu0hputs(

− Ra'io hannel on'itions

− Activate' 5eatures− 3horta0e on +u User plane or DH tra55ic too hi0h

− +ncorrect +u arameter settin0s

− H3DA po4er parameter settin0s

− H3DA parameters

− rolems in core net4or* or application server.

− rolem 4ith 'rive test tools 6@o3 pro5ile, T + settin0s etc.7

.2.1 H3DA Throu0hput +sH3DA selections 6RG$1>a7 to0ether 4ith H3DA 'ata volume 6RG$"87 can e use' tomonitorin0 possile capacity ottlenec*s.

∑

++

++++

++++

++++

+++

=

BGR DSCH HS IUB FAILSETUP INT DSCH HS IUB FAILSETUP

BGR DSCH HS BTS FAILSETUP INT DSCH HS BTS FAILSETUP BGR DSCH HS UE FAILSETUP

INT DSCH HS UE FAILSETUP BGR DSCH HS RNC FAILSETUP INT DSCH HS RNC FAILSETUP

BGR RET DSCH HS REJ INT RET DSCH HS REJ BGRUSERS HSDPA MAX SEL DCH

INT USERS HSDPA MAX SEL DCH BGR FLOW DSCH HS ALLO INT FLOW DSCH HS ALLO

_ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _

RNC_614a

&(uation /. RNC;-$1a 4SDP0 Se!ections

ormally, as can e seen 5rom picture elo4, the H3DA selections an' 'ata volume increase4ith same linearity +.e. similar 4ay. +5 this is not the case, e.0. H3DA selections increase ut'ata volume remains constant, it in'icates that possile capacity ottlenec* e=ist some4here.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >1 6827






RG%#a Avera0e AT; V e0ress throu0hput ps

Iu@!S +hrou$hputs RSRA*-7?

RG!#>a +uE3 incomin0 interactive user 'ata throu0hput in R ps

RG!#a +uE3 incomin0 ac*0roun' user 'ata throu0hput inR ps

RG!12a +uE3 <T input tra55ic rate in R ps

Radio Connection !erformance %easurement %2-2/ based

RG$1# Avera0e RT H3ED3H D Throu0hput ;ps

Fi0ure #1 sho4s an e=ample o5 H3DA throu0hput measurement 5rom multiple throu0hput +s6RG%22c, RG$"$', RG!1>a an' RG$1#77 an' 'rive test lo0. Throu0hput measure'5rom 'rive test lo0 is application level throu0hput. +t mainly sho4s that the active throu0hput +RG%22c sho4s 9uite close the measure' avera0e throu0hput 5rom 'rive test tool. The other

+s measure the avera0e throu0hput an' they sho4 that e9ual values can e achieve' 5rom'i55erent measurements 6ell throu0hput ;1"2#, ?T3 ;""" an' R; ;1"1%7. This 0ives the5ree'om to choose the + ase' on the availale measurements.

#igure /$. 4SDP0 throughput measurement from 2TS and drive test !og.

.2.2 H3UA Throu0hput +sThe H3UA per5ormance evolution can e estimate' 4ith same metho' as H3DA, ycomparin0 the H3UA selection 6RG!2#a7 an' H3UA 'ata volume 6RG!#1a7.

Tale 1$ lists the relevant reports an' +s 5or H3UA R? throu0hput monitorin0 an'trouleshootin0.

Ta!e $-. 4SP0 traffic and throughput P)s and counters

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e ># 6827


http://nop-i.nokiasiemensnetworks.com/formula.php?ne=RNC&formula_id=RNC_934a









Report: System !ro$ram R*SRA*--- 1%2--34 %2-334

RG!#"a ac*et 3ession Attempts

RG!2#a &EDH selections RG!28a H3UA attempts

RG!#1a 67 H3UA ;AEes 'ata volume at R ;it

Report: Cell Data <olume and +hrou$hput at R*C RSRA*-// 1%2-35

;1"2#1" RTG&DHGUGDATAGV: yte

RG!2a 67 H3UA ;AEes avera0e throu0hput at R *ps

Report: Allocated +raffic Amounts 1R00 = 6S!A5 RSRA*-/- 1%2--34 %>---5

RG111%a &EDH allocations

RG1118a &EDH allocation 'uration ;in

RG!2a 67 H3UA ;AEes avera0e throu0hput at R ps

RG!#1a 67 H3UA ;AEes 'ata volume at R ;it

;"""11 H3UAG;+G;ADGTHR *it/s

;"""12 H3UAG;AG;ADGTHR *it/s

;"""1# H3UAGAV&G;ADGTHR *it/s

Report: *umber of 6S!A Users and UE capability RSRA*->2 1%2---4 %2--25

RG1"#$a Avera0e numer o5 simultaneous H3UA users

RG1"#%a Avera0e numer o5 simultaneous H3UA users, 'urin0H3UA usa0e

RG!$8a U DH 3electe' 'ue to too many H3UA users K

A+% <CC +raffic &oad RSRA*- 1%>-5RG!1a, +u U Avera0e Throu0hput 6R si'e7

RG%2a Avera0e AT; V in0ress throu0hput ps

Iu@!S +hrou$hputs RSRA*-7?

RG!#!a +uE3 out0oin0 interactive user 'ata throu0hput in R *ps

RG!>"a +uE3 out0oin0 ac*0rou' user 'ata throu0hput in R *ps

RG!#$a +uE3 out0oin0 user 'ata throu0hput in R *ps

Fi0ure #2 sho4s an e=ample o5 H3UA throu0hput measurement 5rom multiple throu0hput +s

6;"""12, ;"""1#, RG!27 an' 'rive test lo0. ;""";12 sho4 ma=imum H3UA;acE' throu0hput. The +s that measure the avera0e throu0hput 5rom 'i55erent measurements6ell throu0hput ;1"2# an' ?T3 ;"""7 sho4 e9ual values. This 0ives the 5ree'om to choosethe + ase' on the availale measurements.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >> 6827




#igure /%. 4SP0 throughput P)S and drive test too! measurement.

#igure //. 4SP0 se!ections and throughput.

.2.# H3DA optimise' throu0hputTest o5 ma=imum H3DA throu0hput an' un'erstan'in0 o5 the re9uire' con5i0uration is a

startin0 point 5or H3DA 5eature per5ormance tests an' per5ormance optimisation, althou0h itcan e achieve' only in nominal con'itions commonly not availale 5or users. The ma=imumthrou0hput in RA3"$ net4or*s is !.$ ;ps 5or sin0le users 6atE! U&7 an' 11.8 ;ps per cell,





see Tale 1% elo4 61> ;ps/user is a RU1" 5eature7. urrently most common 'ata car's arecate0ory 8 supportin0 1" co'es an' 0ettin0 ma=imum $.%2 ;ps throu0hput in RA3"$.

Ta!e $6. 3a'. user it rates with different R0S features.

The ma=imum achievale throu0hput has to e supporte' y the 4hole en'EtoEen' connection,all inter5aces an' protocol layers. This topic is han'le' in multiple re5erences li*e WRA &2&system per5ormance optimiMation 0ui'eX I11J, WH3A Ra'io et4or* lannin0 <ui'eX I1J an'section Whec*in0 H3DA settin0s in net4or* elementsX in RA3"$ pro'uct 'ocumentation I#J.?elo4 is a summary o5 the latest *no4n issues relate' to the ma=imum it rate optimisation(

;a=imum H3DA throu0hput can e achieve' only 4ith 0oo' ra'io con'itions. Hi0h H3DAitrates re9uire 0oo' ortho0onality an' hi0h @+. Fi0ure #> sho4 theoretical H3DA R levelthrou0hput 6application throu0hput is typically 1"K lo4er7 5or H3DA , 1" an' 1 co'es 4ith'i55erent @+ values. Cith H3DA 1 co'es, @+ L2% is re9uire' to achieve ma=imumthrou0hput. @+ value here is compensate' @+ 6a5ter lin* a'aptation7 not value reporte' yU&. Fiel' measurement tools as 4ell as counter statistic sho4 reporte' @+, not compensate'@+. ompensate' @+ has een seen to e 2E# '? etter than reporte' @+ in RA3"$. Alsothere are some 'i55erencies et4een terminals relate' to reporte' @+.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >$ 6827




#igure /1. 4SDP0 RC" throughput =app!ication !eve! throughput is typica!!y $9 !ower> vs.Compensated C?)

Fi0ure # sho4 D application level throu0hput 5or at ! 61 co'e7 an' at 8 61" co'e7 H3DAU&s. ;easurements are 'one un'er RA3"$ 6R#." @# #.11E"7 4ith 8 C 6#! '?m7 ;etrosite.+H po4er 4as set to 2$ '?m an' t=;a=H3DA to #!'?m. H3UA 4as 'isale' 'urin0test an' other parameters 4ere set so, that it 4as possile to allocate 1 co'es 4as H3DA.Test 4as 'one y 'o4nloa'in0 1""; 5ile 6FT7 an' there 4as no other tra55ic in the cell 'urin0measurements. Cith ate0ory ! H3DA U& the ma=imum achieve' application level throu0hput4as !.18 ;ps per user an' to0ether 4ith at! an' at8, the total cell application levelthrou0hput 4as 1".8 ;ps.

#igure /,. 4SDP0 app!ication !eve! throughput with different 4SDP0 category &s

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >% 6827

E $ 3itwith C?) $%

'?

@+




Fi0ure #$ sho4 @+ 'istriution 5rom counters 'urin0 testin0 5or oth at8 an' at ! U&s6measurements 'one in 'i55erent hour7. U&s 4ere connecte' 5or 'i55erent laptop 4ith 1E2 meter 'istance et4een. ?ase' on results elo4, it seems that ate0ory ! H3DA U& is reportin0hi0her @+ values than ate0ory 8 U&s. This is no4 reporte' @+, not compensate' @+.

#igure /-. C?) distriution during testing for different &s

Fi0ure #% sho4 throu0hput an' numer o5 allocate' co'es 4hen there is 2 simultaneous at 8H3DA U&s. As H3DA 1 co'e an' co'e multiple=in0 is activate', H3DA U&s are sche'ule'

4ith same TT+ 68 B % co'es7. Cith 2 at 8 H3DA U&, the avera0e application throu0hput is>.$E." ;ps per User.

#igure /6. 4SDP0 throughput and code a!!ocation when % simu!taneous category 7 4SDP0 &

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >8 6827




?esi'es o5 ra'io con'itions an' use' R parameters, 5ollo4in0 U& types an' et4or* settin0s4ere use' 'urin0 testin0 to 0et H3DA throu0hput values presente' in Fi0ure #.

U& cate0ory an' type( er5ormance et4een the U& types can vary, 5ollo4in0 H3DA U&s use'

'urin0 testin0.E ovatel :vation ;!!"D U3?( at 8 H3DA ;a= throu0hput %.2;ps, at H3UAE orm( H3DA at! ;a= throu0hput 1" ;ps, H3UA cat E ;a= Throu0hput 2 ;psate0ory 8 H3DA U&s 4ere oth connecte' to same emo.

lient 3ettin0s( lean, hi0hEspec laptop use' instea' o5 3 uil' laptop. Cith T receive4in'o4 siMe YL2$*? 6unnecessarily hi0h values shoul' e avoi'e'7. ever set T valuesmanually y mo'i5yin0 re0isters 6same parameter can e in the several places7, use rea'y ma'etools li*e T optimiser to chan0e values. on5orm e.0. y usin0 Cireshar* 6&thereal7 thatchan0e is 'one.3erver 3ettin0s( Fe'ora inu= server use', Cith T receive 4in'o4 siMe is YL 2$ *?. +nserver si'e, 1 <ps inter5ace is use' to connect server to ore net4or*.

+u apacity( Hi0h enou0h +u capacity ensures that throu0hput is not limite' y +u. +uapacity can e chec*e' 5rom the ::. Use' user plane siMe o5 >"""" cps e9uals to1$.!$;ps. Dynamic sche'ulin0 5or H3DA 4as enale' 4ith 'e5ault parameter settin0s

Tale 18 sho4 +u 'eman' 5or H3DA hi0h itrates.

Ta!e $7 )u demand for 4SDP0 high itrates =0T3 siFe $<-7, e(ua!s to ,' &$ and %7$91 to 6'&$>

ore et4or*s( Fle=i +3 <<3 6Fle=i #.2 D#7 use' as ol' <<3 HC is not vali' 5or ma=imum throu0hput. omi 3<3 6)$ %.2E" 63<$D%277

.2.> H3UA optimise' throu0hputH3UA throu0hput 'epen's on parameter settin0s, activate' 5eatures, U& capaility, ?T3 HCcapacity an' +u apacity. Also air inter5ace start to limit H3UA throu0hput 4hen severalH3UA users un'er same cell.

arameter %a"+otalUplin'SymbolRate 'e5ines ma=imum total U symol rate o5 the &E

DDH6s7 o5 the U& in the cell an' shoul' e set to #8>" *ps 62 = 3F27 i5 H3UA 2." isactivate'. The lo4est parameter value amon0 the values o5 the parameter o5 the cells thatelon0s to the &EDH active set is use' 4hen the &EDH is allocate'. 3upportin0 H3UA 2."

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e >! 6827




;ps means that R is allo4e' to set up the it rate 5or the U& 4hen re9ueste' y corenet4or* 6in RA? @o37 an' 4hen nee'e' con'itions are met. The nee'e' con'itions are, 5or instance, suitale U& cate0ory an' that the it rate is supporte' also in the nei0hourin0 cells6no 3H: nee'e'7. Chen some con'ition is not 5ul5ille' 'urin0 a call, R may 'o4n0ra'e a

U& it rate.

Tale 1!. H3UA itrates 4ith 'i55erent ;a=TotalUplin*3ymolRate settin0s

%a"+otalUplin'SymbolRate T?3R

Throu0hput

3F> !$" %11" ".$%2

2×3F> 1!2" 1>>8> its 1.#8 ;ps

2×3F2 #8>" 1!!" its 1.8! ;ps

arameter FactorEDC6%a"#itRate 'etermines the 5actor 5or calculatin0 the &EDH ma=imum

it rate 5rom the ma=imum U user it rate o5 the RA?.

− +5 special value o5 " is use', then U it rate is not restricte' ase on the uplin*

ma=imum it rate o5 the RA?.

− +5 value Y " is use', FactorEDC6%a"#itRate multiplie' y U @o3 shoul' e superior to

tar0et U throu0hput

− &. 0. 3houl' e set to i5 H3UA2." is activate' an' suscrier HR @o3 pro5ile is set

to #8>*ps

arameter +hreshold%a"ED!DC6SR can e use' to restrict the ma=imum total Uplin* symolrate o5 &EDDH ase' on ma=imum uplin* user it rate o5 the RA? 6see I1J7.

The test results is sho4n in Fi0ure " 6en' o5 this chapter7 U throu0hput values 4ith 'i55erentsettin0 o5 aove parameters.

H3UA 2." ;ps is license' 5eature, an' y achievin0 ma=imum throu0hput the parameter ;a=imum total uplin* symol rate have to e set #8>". Fi0ure #8 elo4 sho4 U application60reen line7 level throu0hput 4hen H3UA 2." 5eature is activate'.

#igure /7. 4SP0 throughput with 4SP0 % 3ps feature

Uplin* ra'io resources are share' et4een the H3UA an' R!! users. Fi0ure #! elo4 presentcell level U application throu0hput 4ith 'i55erent numer o5 H3UA U&s. ;a=imum achieve'

U cell level application throu0hput is aroun' # ;ps 4ith 2 H3UA U&s. A''in0 more U&s'oes not increase U cell level throu0hput 'ue uplin* air inter5ace limitations.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e " 6827

4SP0 &$ %'$993"




arameter !r"+ar$et%a"#+S 'e5ine ma=imum tar0et 5or receive' total 4i'e an' po4er in thecell 5or ?T3 ac*et sche'ulin0. As can e seen 5rom results elo4, chan0in0 this parameter 'oes not improve total uplin* cell throu0hput si0ni5icantly.

#igure /<. 4SP0 Ce!! " app!ication !eve! throughput with different numer of 4SP0 &s andwith different Pr'Target3a'2TS va!ues =changed in case of / 4SP0 &>

Cith 2 simultaneous H3UA U&, the throu0hput is sli0htly 'ecrease' 65rom 1.$# ; in case o5 1H3UA U& to 1.!; 4ith 2 H3UA U&7.

Fi0ure >" sho4 e=ample o5 one H3UA user throu0hput 4hen there is # simultaneous H3UAusers. A''in0 #r' H3UA User the throu0hput o5 each H3UA user start to 5luctuate an' uplin*cell level throu0hput 'ecrease. +n case o5 # or more simultaneous H3UA Users, the cell levelthrou0hput is alrea'y limite' y air inter5ace as can e seen 5rom Fi0ure >".

#igure 19. 4SP0 user throughput when / simu!taneous 4SP0 &

Fi0ure >1 sho4 uplin* application level throu0hput o5 1 H3UA User, 4hen there is 'i55erentnumer o5 users in the cell. +n case o5 # H3UA U&, r=tar0et;a=?T3 4as chan0e' 5rom $6'e5ault7 to #".


;a= D cellapp. throu0hput4ith 2 H3UAU&

!r"+ar$e%a"#+S chan0e'

4SP0 &/ %'$993"

3tart #r' U&




#igure 1$. " app!ication !eve! throughput of $ 4SP0 & when there is different numer of &s inthe ce!!.

Fi0ure >2 sho4 r=Total 65rom :nline ;onitor7 value 4ith 'i55erent numer o5 H3UA Users.

#igure 1%. p!ink Pr'Tota! with different numer of 4SP0 &s

Cith 1 H3UA U& the uplin* loa' is aroun' #"K, 4ith 2 H3UA U& close to $"K ut not yetlimite' y air inter5ace. A''in0 #r' U& the loa' increase close to %K 6r=Tar0et;a=?T3L$7 an'cell level throu0hput is not increase' any more.





#igure 1/. p!ink "oad with different numer of 4SP0 &s

H3UA throu0hput can e also limite' y ?T3 hannel elements. H3UA & allocation is 'one4ith speci5ic siMes o5 resource steps. The amount o5 resources nee'e' 'epen's on thethrou0hput 6hysical layer cell level throu0hput7 an' the numer o5 H3UA users. +n RA3"$H3UA users cannot e move' et4een C3s 6or 5le=i sumo'ules7, so 4e 'onOt 4ant tota*e another C3 to H3UA use too 5ast, ecause i5 that 4oul' nee'e' to e ta*en ac* toR!! use, the H3UA users cannot e move' ac* to 5irst C3. This is 0oin0 to e chan0e' inRU1" an' users can e move' et4een C3s.

+nsi'e C3s the H3UA resource steps are ta*en in use so that each ne4 user 0ets its o4nresource step 6i5 5ree capacity7 until the 4hole C3 is occupie'. To e ale to allocate the ne=tH3UA resource step, an a''itional 5ree capacity o5 $ & is nee'e'. The re9uire' si= &s 5reeon top o5 the H3UA resource step is to avoi' a Npin0Epon0O e55ect in reservin0 an' 5reein0H3UA resource step.

+5 all the H3UA users are un'er one cell 6or there is only one cell7, only 5irst C3 car' or Fle=i sumo'ule is use'. Fi0ure >> elo4 sho4 ?T3 & H3UA usa0e versus H3UA;A/AV& ;acE' throu0hput. There is 5e4 perio's H3UA throu0hput is limite' 'ue the ?T3 HC'ue the increase' R!! tra55ic 4hich can e seen 5rom Fi0ure >>.





#igure 11. 2TS C& 4SP0 sage and 4SP0 3a'imum 3ac+d Throughput

There is o4n counters to monitor H3UA & resource status. These counters can e use' tomonitor perio's 4hen H3UA throu0hput is limite' or H3UA setup is not possile 'ue the ?T3HC.

• ;1"""2$! ?T3 H3UA HC imite' Duration is up'ate' 4hen ?T3 is in H3UA HC

limite' state. +n this state, R sets up the &EDH ut the ?T3 HC shorta0e may causethrou0hput to e lo4er than e=pecte'.

• ;1"""2%" ?T3 H3UA : HC apacity 'uration is up'ate' 4hen ?T3 reports to e

in state that it 'oes not have H3UA HC capacity availale. +n this state, the R 'oesnot set up the &EDH

Fi0ure > present hours 4hen H3UA throu0hput is limite' 'ue the lac* o5 ?T3 & 6'ue theincrease R!! tra55ic 4hich, in case o5 ?T3 &Os, has priority over H3UA7, an' i5 4e compareFi0ure >> an' Fi0ure >, these are the perio' 4hen ma= use' & sho4 very hi0h value.

#igure 1,. 2TS resource status counters


H3UA R!!H3UA




The 5eature H3UA on0estion ontrol consists o5 multiple 'etection entities separate' into'i55erent parts o5 the system. +ntention is to provi'e 5ull covera0e o5 con0estion prevention over the system. The main entities o5 interest are +u in terms o5 transport capailities an' the R interms o5 processin0 resources. Follo4in0 ;1"22 counters can e use' to monitor +u an' R

con0estion control.

+ ame Description

;1"22$! +U?GD&AGGD&AG+D

+u 'elay variation ase' al0orithm operatesat the typica! working range under !oad.+u usa0e is close to optimal 4hen thiscounter contains nonEMero 6ut not lar0e7value. Ho4ever, lar0e value in this counter ise=pecte' coinci'ently 4ith the Frame oss+ counter

;1"22%2 +U?GD&AGGFRA;&G:33G+D

+u 'elay variation ase' al0orithm operatesat the high )u !oad range. o4 value is

e=pecte' in loa' situation. Hi0h valuerepresents overloa' +u transport an' thiscoul' e in'ication o5 under dimensionedtransport.

;1"22%1 +U?G:33GGFRA;&G:33G+D

Frames are lost in +u transport. There isproaly somethin0 4ron0 in resourceallocation or 'imensionin0 o5 +u i5 thiscounter contains hi0h values report a5terreport. +t coul' also e that there e=ist somephysical prolem in +u

;1"22%" HCG:V&RGGD&AG+D6R HC7

User plane processin0 4 is actingproactive!y to contro! increasing !oad.

+ncrease in this counter is typical 4hensystem is loa'e'. Ho4ever, lar0er increasein counter value is an in'ication o5 ecomin0HC overloa'

;1"22%#HCG:V&RGGFRA;&G:33G+D6R HC7

User plane processing 4 is heavi!yover!oaded. roaly somethin0 4ron0 inresource allocation or 'imensionin0 o5 Ri5 this counter contains hi0h values reporta5ter report

;1"22%> 3UG&DHGFG?RAHG3&TU

;1"22%% 3UGR&G&DHGFRA;&3 &=act umer o5 successively receive' 'ata

;1"22%$ D&A&DG&DHGFRA;&3 &=act numer o5 all the 'elaye' 5rames;1"22% ;+33&DG&DHGFRA;&3 &=act amount o5 lost 5rames

Ta!e %9. 4SP0 congestion contro! Counters

Fi0ure >$ elo4 sho4 success5ully receive' &DH 5rames an' Frame losses 'ue the R HC.ounter HCG:verloa'GGFrame loss is tri00ere' in case 4hen there is # or > simultaneousH3UA U&s in'icatin0 lac* o5 D3/D;< processin0 capacity. 6ounters are presente' in'i55erent scale, ma= 5rame loss 2.$. K 7

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e 6827






intro'uce cell level symol rate limitation %a"+otalUplin'SymbolRate parameter. This impactcan e clearly seen 5rom 5i0ure elo4.

#igure 17. #unction of )u congestion contro! for throughput with different symo! rate

#igure 1<. 4SP0 congestion contro! decrease the 4SP0 it rate y decreasing the Serving grantwith too high spreading code configuration

H3UA it rate can e limite' y ?T3 sche'uler 4ith t4o mechanisms 4hich utilise the RA?ma= it rate 6'etail parameter 'escription presente' e0innin0 o5 this chapter.7

− &EDH ma=imum it rate limitation 4ith RA? @o3 an' FactorEDC6%a"#itRate 6'e5 1.7

− 6L "7( ;a= &EDH it rate not sent to ?T3

− 6Y "7( &EDH ;a= ?itRate L FactorEDC6%a"#itRate Z RA?( ;a= U it rate, sent to

?T3 in ?A( R setup/recon5i0uration messa0e 6+& ( &EDH ;a=imum ?it Rate7

− Total uplin* symol rate o5 &EDDH6s7 can e limite' 4ith +hreshold%a"ED!DC6SR − RA?( ;a= U it rate [ +hreshold%a"ED!DC6SR07-'bps 6'e5 12 *ps7 :R

%a"+otalUplin'SymbolRate L !$"è 3F>è $%2 *ps

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e % 6827

3F> 2=3F> 2=3F2

3F>

2=3F> 2=3F2




− RA?( ;a= U it rate [ +hreshold%a"ED!DC6SR203-'bps 6'e5 1"2> *ps7 :R

%a"+otalUplin'SymbolRate L 1!2"è 2 \ 3F>è 1#8" *ps

− :ther4ise 6RA?( ;a= U it rate Y +hreshold%a"ED!DC6SR203-'bps AD

%a"+otalUplin'SymbolRate L #8>"7è 2 \ 3F2è 1888 *ps

− ;a=imum set o5 the &EDDHs sent to ?T3 in ?A( R setup/recon5i0urationmessa0e 6+& ( ;a=imum 3et o5 &EDDHs7 AD to U& in RR( Ra'io earer recon5i0uration messa0e 6+&( ;a=imum channelisation co'es7

Fi0ure " sho4 result 5rom H3UA it rate parameter test an' impact o5 +u con0estion control.Test cases an' use' parameter settin0s are liste' elo4. Cith 1 = &1, the +u con0estion controlis limitin0 throu0hput 4ith hi0h itrate settin0s. 6Arro4s in Fi0ure " sho4 cases 4here +ucon0estion control is limitin0 H3UA itrate7

#igure ,9. p!ink throughput with $ ' &$ for 4SP0 and different Parameter va!ues

− Test 1( &55ect o5 Factor&DH;a=?itRate

− FactorEDC6%a"#itRate ; " 6not set7, 1, 1. an'

− RA? ;a= U it rate #8> *ps

− Threshol';a=&DDH3R L " 6ot set7

− Test 2( &55ect o5 ;a=TotalUplin*3ymolRate

− ;a=TotalUplin*3ymolRate L !$", 1!2", #8>"


− Factor&DH;a=?itRate L " 6ot set7

− RA? ;a= U it rate >1#2 *ps

− Test #( &55ect o5 RA? @o3 an' +hreshold%a"ED!DC6SR

− RA? ;a= U it rate $>, $>" *ps


− Threshol';a=&DDH3R!$"*ps L 12 *sps an'

Threshol';a=&DDH3R1!2"*ps L 1"2> *sps

− Test >( &55ect o5 RA? @o3 only

− RA? ;a= U it rate $>, #8> *ps− Threshol';a=&DDH3R L " 6ot set7



" throughput

%<6/-6

$$$-

71/

,<%

$9$9

7-$

,71

$9/7

7/97-6 7,%

17$9-

%<-

/6,

"."

2""."

>""."

$""."

8""."

1"""."

12""."

k

i t 8 s

Factor&DH;a=?itRate

;a=TotalUplin*

3ymolRate

Threshol';a=&D

DH3R@o3 only

@o3 4ith

Factor&DH;a=?itRateL1.




− Test ( &55ect o5 RA? @o3

− RA? ;a= U it rate $>, 128, 2$ *ps


− Factor&DH;a=?itRate L 1.

H3UA 'ata rate can e limite' y

− U& T= o4er U& is alrea'y usin0 its ma=imum T= po4er

− 3ervin0 <rant ;a=imum 0rant is use' alrea'y

− Data U& u55er is empty no ne4 'ata to sen'

Fi0ure 1 elo4 sho4 situation 4hen U& t= po4er increase an' start to limit throu0hput, there ismore Asolute <rants 0iven to the U&. ?T3 re'uce a00ressively the throu0hput an' there5ore A< are use'.

#igure ,$. & t' Power !imitation vs. 4SP0 throughput

.# ;oility

H3A moility can e per5orme' 4ith cell reselection in &GFAH or servin0 cell chan0e5unctionality. 3ervin0 cell chan0e 4ith so5t han'over is re9uire' 5or H3UA,

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e ! 6827

R&DL A<

ello4 L&ETF+?U&L 3<




6S@DSC6 servin$ cell chan$e can e tri00ere' y the est server &c/o, U 3+R error an'event 1?/1. The most common tri00erin0 reason is suppose' to e perio'ical &c/omeasurements. 6SD!AServCellBindow 1def 3 d#5 parameter 'etermines the ma=imumallo4e' 'i55erence et4een the est cell +H &c/o an' the servin0 H3ED3H cell +H

&c/o. The recommen'ation is to set DropBindow parameter value in H3DA F;3 hi0her than 6SD!AServCellBindow , so that the servin0 cell chan0e 4oul' e normally tri00ere' y the&c/o measurements an' not y the event 1?.

AdditionBindow in H3DA F;3 is controllin0 the active set siMe o5 the associate' Uchannels. +t 'oesnOt have 'irect impact on the servin0 cell chan0e 5unctionality an' tri00erin0.urrent recommen'ation is to use lo4er value 5or AdditionBindow 1closer to - d#5 in H3DAF;3 than in the RT/RT F;3, to have smaller 3H: area 5or H3DA users.

The H3DA servin0 cell chan0e per5ormance can e measure' 4ith RG%##a 6H3DA3ervin0 ell han0e 3uccess Rate7. The 3 can e tri00ere' mainly y +H &co, U 3+R&rror or active set up'ate 6removal o5 servin0 H3ED3H cell 5rom A37.

o4 success rate can e cause' y

− Failures 'ue to ?T3

− Chen the R receives ?A( RAD+: + R&:F+<URAT+: FA+UR& 'urin0

servin0 H3ED3H cell chan0e

− Failures 'ue to transmission

− Chen a servin0 H3ED3H cell chan0e 5ails 'ue to an +u transport setup 5ailure.

− Failures 'ue to a'mission control

− The numer o5 H3ED3H servin0 cell chan0e 5ailures 'ue to a'mission control, 5or

e=ample ecause the ma=imum numer o5 H3DA users 4ere alrea'y allocate' inthe tar0et cells.

− Failures 'oe to other reasons

− The numer o5 H3ED3H servin0 cell chan0e 5ailures 'ue to other reasons.

Tale 21 summarises the H3A moility relate' +s an' counters.

Ta!e %$. 4SP0 moi!ity counters and P)s


Report: System !ro$ram RSRA*--

RG!"$a H3DA 3 attempts

RG%##a H3DA 3ervin0 ell han0e 3uccess Rate K

Report: 6S!A Servin$ Cell Chan$e RSRA*-

RG!"$a H3DA 3 attempts

RG%##a H3DA 3ervin0 ell han0e 3uccess Rate K

;1""821# 3G3TART&DG+HG&: +nte0er numer

;1""821> 3G3TART&DGUG3+RG&RR:R +nte0er numer

;1""821 3G3TART&DGAT+V&G3&TGUD +nte0er numer

;1""821$ 3G3TART&DG:TH&RGR&A3: +nte0er numer

;1""8218 3GFA+&DGDU&GT:G?T3 +nte0er numer ;1""821! 3GFA+&DGDU&GT:GTRA3; +nte0er numer

;1""822" 3GFA+&DGDU&GT:GA +nte0er numer

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $" 6827




;1""8221 3GFA+&DGDU&GT:G:TH&R +nte0er numer

;1""82># +T&RGRGHH:GATTGH3AG3 +nte0er numer

RG11$2a H3UA +nterER 3 3uccess Rate K

RG11$#a H3UA +nterER 3 Failure Rate KRG11$>a H3UA +nterER 3 Drop Rate K

?elo4 is typical e=ample o5 H3DA moility per5ormance ta*en 5rom R3RA"## report. ;ainreasons to start 3 is the 'ecrease' +H &co an' active set up'ate 6event 1/1c7. Therehas een some issues 4ith U sir error tri00er so it is not use'.

The reason 5or hi0h 3 5ailure 'ue to other 6see picture7 is not *no4n. +5 there is not capacityin the tar0et cell the 5ailure can e seen 4ith A, TRA3 an' ?T3 reasons.

#igure ,%. &'amp!e of SCC fai!ure reasons

There seems not to e a relation 4ith poor 3 success an' H3DA retainaility, as seen in thepicture elo4. 3 success rate 5or H3DA an' H3UA is not very accurate in cell level as'enominator is incremente' in the source cell 6ol' servin0 cell7 an' numerator is incremente' inthe tar0et cell 6ne4 servin0 cell7.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $1 6827




#igure ,/. 4SDP0 SCC performance compared to 4SDP0 retainai!ity.

+nter R 3 per5ormance seems to e aout 2E> K lo4er than +ntra R 3 'ue to 3Rrelocation issues.

.> Retainaility

The retainaility o5 a H3A pac*et call 'escries the proaility that the pac*et call is not'roppe' 4hen the H3A channel type is use'. The + RG!2"a 6see Tale 227 'escries theretainaility ase' on tra55ic ;1"22 measurements. This ta*es into account only events 4henthe DH connection is anormally release'. The + RG$"!a can e also use' 5or retainailitymeasurement, ut this + is tri00ere' in cell 4here the R 5ails even i5 there is 4or*in0 R inother cell o5 active set an' the pac*et call is s4itche' to that, thus 'oes not necessary presentusers vie4 o5 connection 9uality.

The H3A pac*et call 5ailures are mainly 'ue to R 5ailures ra'io lin* 5ailure, R protocol resetor uplin* R unrecoverale error 6ell Up'ate sent y U&7. Fi0ure 2$ presents an e=ample o5 H3A pac*et call retainaility analysis.





#igure ,1. 4SP0 retainai!ity fai!ure ana!ysis

Tale 22 lists the relevant reports an' +s 5or H3DA R? accessiility monitorin0 an'trouleshootin0.

Ta!e %%. 4SP0 retainai!ity counters and P)s =ReportH Service8Session Retainai!ity 0na!ysisRSR0N96<>

+ re5 + name / Areviation+unit

Report: System !ro$ram RSRA*---

RG!#"a ac*et 3ession Attempts

RG!22a ac*et 3ession 3uccess Ratio 5or RT K

RG$1>a H3ED3H selections

RG$"!a H3DA Resource Retainaility 5or RT Tra55ic K

RG!2$a H3DA attempts

RG!2"a H3DA 3uccess Ratio 5rom user perspective 5or RT K

RG!2#a &EDH selections

RG!1!a H3UA resource Retainaility 5or RT Tra55ic K

Report: Service.Session Retainability Analysis RSRA*-/0 1%2-335

RG1"!2a ac*et 3ession Rel 5rom H3E&DH

RG1"!#a ac*et 3ession Rel 5rom H3EDH

RG1"!>a ac*et 3ession Rel 5rom DHEDH

RG1"!a H3ED3H/&EDH ac*et all Rel 'ue to R Failures K

RG1"!$a H3ED3H/DH ac*et all Rel 'ue to R Failures K

RG1"!%a DH/DH ac*et all Rel 'ue to R Failures K

RG1"!8a H3ED3H/&EDH ac*et all Rel 'ue to :ther Failures K

RG1"!!a H3ED3H/DH ac*et all Rel 'ue to :ther Failures K

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $# 6827

RG!2"a]

K

hec* 3 Failure Rate Ra'io, +u, &resource con0estion

hec* 5or R 5ailures an' use R lo00in0 i5re9uire'

o Actionee'e'

H3A pac*et callRa'iolin* 5ailures

H3A pac*et call5ailures E other

o

es

es

es

o

hec* @+ 'istriution an' &cno 'istriution 5orcovera0e issue

hec* H3DA moility parameter A''/Drop4in'o4, 3 parameter




RG11""a DH/DH ac*et all Rel 'ue to :ther Failures K

RG11"1a H3ED3H Allocation Rel

RG$"!a H3DA Resource Retainaility 5or RT Tra55ic K

RG11"2a H3ED3H Allocation 'ue to R Failure KRG$%%a H3DA Ra'iolin* 5ailures 6RT7

RG$%a H3DA on Ra'iolin* 5ailures 6RT7

RG$%! H3ED3H release 'ue to moility 6RT7

RG$81a H3ED3H release 'ue to preEemption 6RT7

RG%2>a H3ED3H to DH s4itch E other 6RT7

RG11"%a &EDH Allocation Rel

RG!1!a H3UA resource Retainaility 5or RT Tra55ic K

RG11"8a &EDH Rel 'ue to R Failures K

RG111a &EDH Rel 'ue to H3ED3H servin0 cell chan0e K

RG11"!a &EDH Rel 'ue to :ther Failures K

Fi0ure sho4s one e=ample aout H3ED3H an' DH release reasons. ?asically it tells theportion o5 R 5ailures compare' to other 5ailures 5rom three 'i55erent channel types.

#igure ,, &'amp!e of 4SDP0 re!ease types =>

Fi0ure $ sho4s one e=ample aout H3ED3H 5ailure reasons. They are ase' on tra55iccounters. There is not only moility causin0 the prolems ut also some lac* o5 capacity.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $> 6827




#igure ,- &'amp!e of different re!ease reasons for 4S+DSC4 channe!

Fi0ure % sho4s that also 5or H3UA release the main cause is ra'io lin* 5ailure.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $ 6827




#igure ,6 &'amp!e of &+DC4 re!ease

$ H3A B R!! earer inter4or*in0

Chen o5 R!! an' H3A tra55ic is allocate' in the same cell, they 4ill actively share the ra'io an'lo0ical resources in the cell. Fi0ure 8 presents an' e=ample o5 the e55ect o5 DH po4er reservation on the H3DA cell throu0hput. Fi0ure ! presents the e55ect o5 H3ED3H co'eallocation on the co'e tree occupancy an' numer o5 availale 3F#2 co'es use' 5or $>*psconnections. This resource sharin0 can cause some per5ormance 'e0ra'ation on oth R!! an'H3A users

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $$ 6827




#igure ,7. &ffect of DC4 power on 4SDP0 throughput.

#igure ,<. 4S+PDSC4 code reservation.

$.1 o4er, co'e an' & 6H3UA7 sharin0

$.1.1 D po4er sharin0The po4er sharin0 et4een H3DA an' DH tra55ic can e monitore' ase' on the t=Totalan' t=onH3DA measurements reporte' y the ?T3. onEreal time earer po4er 6t=RT7can e monitore' separately it is calculate' y the R as the sum o5 'e'icate' po4er

measurements o5 RT earers receive' 5rom ?T3.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $% 6827




Fi0ure $" presents an e=ample 6?T3 measurements 5rom :nlineEmonitorin07 o5 po4er sharin0et4een H3DA an' RT DH tra55ic. The 'ynamic resource allocation is active an' allavailale po4er is allocate' to H3DA 6aout >C is use' y Hs7 4ith ma=imum o5 1. C.The H3DA po4er is avera0e' over the reportin0 perio' an' it 'epen's also on the H3DA

activity 6TT+ activityK7.

#igure -9. D" power sharing etween 4SDP0 and NRT PS traffic.

The cell level D po4er measurements are store' to numer o5 counters an' +s, Tale 2#lists the main counters/+s an' relate' measurements 5rom ?T3. H3DA transmit po4er iscalculate' as t=Total t=onH3A.

Ta!e %/. P)s re!ated power sharing etween 4SP0 and R<< traffic


Report: Cell Capacity RSRA*-7/

RG1"2 Avera0e R!! Do4nlin* oa' '?m

RG$!"a Avera0e active nonEH3DA po4er ratio K

RG$!1a Avera0e nonEH3DA po4er ratio K;1"""2#$ ;+GH3AGDG:C&R '?m

;1"""2#% ;AGH3AGDG:C&R '?m

;1"""2#8 AV&GH3AGDG:C&R '?m

;1"""2#2 ;+GTGTAR<&TG3 '?m

;1"""2## ;AGTGTAR<&TG3 '?m

;1"""2#> AV&GTGTAR<&TG3 '?m

RG1"1 Avera0e Uplin* R!! oa' '?m

RG1%% oise 5loor o5 the 3ystem '?m\E1""."

;"""1> H3UAGUGCRG;+ '?m

;"""1 H3UAGUGCRG;A '?m

;"""1$ H3UAGUGCRGAV< '?m





Report: *R+ Radio #earer !#S and ,&C RSRA*-2

;1"""1>2 R?GD:C<RGDU&G:GTFG3U?3

;1"""1> R?GD:C<RGDU&G:GRGR&:F

;1"""1$$ R?GR&&A3&GDU&G:GRGR&:F ;1"""1>% R?GD:C<RGDU&G?3G+T&RF

;1"""12 R?GD:C<RGDU&GR&G&;G+T&RF

;1"""1! R?GR&&A3&GDU&G?3G+T&RF

;1"""1$> R?GR&&A3&GDU&GR&G&;G+TF

The main interest is on the monitorin0 o5 availale D po4er 5or H3DA an' also ho4 much o5 this po4er is actually use'. The availale po4er can e measure' ase' on the;1"""1#8GAV<G:GH3DAGCR counter or Avera0e D oa' RG1"2 +. TheH3DA po4er utilisation can e measure' as ratio o5 avera0e H3DA po4er

AV&GH3AGDG:C&R an' avera0e availale H3DA po4er.

o4 level o5 availale H3DA po4er 4ill have an e55ect on the pea* 'ata rates in the cell.H3DA cell throu0hput limitation can e 'etecte' 4hen the po4er utilisation increases.

#igure -$. D" power sharing ana!ysis.

?elo4 is one e=ample o5 H3DA po4er compare' to Avera0e D/U loa'. Cith Dynamic po4er allocation / resource allocation it is possile to use all le5t over po4er 5or H3DA. H3DA po4er measurement 4ith avera0e' input values.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e $! 6827

onsi'er activation o5 2n' carrier 5or H3A

H3DA D po4eravailaility

AV<G:GH3D AG:C&R Y "K

H3DA po4erutiliMation Y "K

eso

o

hec* otherresources




#igure -%. 0verage " and D" !oad as a function of 4SDP0 power

;inimum, avera0e an' ma=imum H3UA U physical channel po4er 6;"""1>E1$7 coul'e use' to see ho4 U po4er is chan0in0 in 'ue to H3UA. Ri0ht no4 they seem not 0ivin0reasonale values 6E112 '?m 'urin0 most o5 the cases7.

$.1.2 hannelisation co'e tree sharin0The D hannelisation co'e tree is share' y the H3DA tra55ic, DH tra55ic an' Hs. ChenH3DA is activate' in the cell it reserves a minimum reservation o5 co'es out o5 1$ 3F1$co'es. The co'e reservation 5or H3DA an' R!! tra55ic is controlle' y 5ollo4in0 principles an'monitore' y the +s an' counters. Tale 2> lists the main +s relate' to channelisation co'etree reservation an' sharin0.

Ta!e %1. P)s re!ated to channe!isation code sharing etween 4SP0 and R<< traffic.


Report: Cell Capacity RSRA*-7/

RG11#a Avera0e occupancy K

RG2" ;a= occupancy K

RG1! ;in occupancy K

;1"""8# ?RG3UG:D&GTR&&GA:

RG!>!a67 3prea'in0 o'e ?loc*in0 rate in D K

RG12 3F> loc*in0 rate K

RG1# 3F8 loc*in0 rate K

RG1> 3F1$ loc*in0 rate K

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %" 6827




RG1 3F#2 loc*in0 rate K

RG1$ 3F$> loc*in0 rate K

RG1% 3F128 loc*in0 rate KRG18 3F2$ loc*in0 rate K

;1"""2$$ HG:D&GD:C<GRT

;1"""2$% HG:D&GD:C<GRTGDH


;1"""1>8 R?GD:C<RGDU&G?3G3R&AD

;1"""1# R?GD:C<RGDU&GR&G&;G3R&AD

;1"""1$" R?GR&&A3&GDU&G?3G3R&AD

;1"""1$ R?GR&&A3&GDU&GR&G&;G3R&A

The H3DA co'e reservation is increase' 4hen the 5irst H3DA connection is setup to the cellor perio'ically 4hile the H3DA is active in the cell, i5 the cell is con5i0ure' 4ith hi0her numer o5 co'es than 6up to 17 an' the U& support that also. H3DA co'e reservation can eincrease' until the numer o5 5ree 3F1$ co'es is less that 6S!DSC6%ar$inSF23 parameter.This parameter tells ho4 much mar0in is reserve' in the co'e tree. This parameter coul' e seteven to Mero, ecause RT calls 4ill preEempt or 'o4n0ra'e H3DA co'es i5 3F1$ co'es are5ully use'. This can e seen in the Fi0ure $#.

#igure -/. 4SDP0 Code downgrade due to 03R with 4SPDSC43arginS#$%7I9

The total co'e occupancy o5 R!!H3DA tra55ic can e monitore' 4ith RG11#a 6Avera0eoccupancy7, RG2" 6;a= occupancy, ;1"""%7, RG1! 6;in :ccupancy7 an'H3DA co'e usa0e counters ;1"""2>8E28. The 0raph elo4 present an e=ample o5 co'etree occupancy an' H3DA co'e usa0e. +n the elo4 e=ample the co'e occupancy is lo4 4hen

the H3DA co'e allocation is at minimum 6 co'es static allocation7, 4hich in'icate' lo4amount o5 R!! tra55ic. Accor'in0 to co'e tree occupancy calculations, the allocation o5 1" H3ED3H co'es raises co'e occupancy to aout %"K 4ithout any R!! tra55ic, 4ith H3ED3H

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %1 6827




co'es the reservation is minimum #8K. These 5i0ures correspon' 9uite closely the presente'e=ample.

#igure -1. &'amp!e of 4SDP0 code a!!ocation and spreading code occupancy A7B.

o'es E1 can e allocate' as 4ante' 5rom net4or* point o5 vie4. The 'e5ault set is to useco'es li*e , 8, 1", 12, 1> an' 1 4ith 1 co'es 5eature. ?ut it is also possile to use all co'es5rom net4or* point o5 vie4 y chan0in0 Qust the co'e usa0e y H3ED3H co'e set in R.

The picture elo4 sho4s that re0ar'less o5 U& cate0ory an' co'e capaility, the net4or*allocates all availale co'es 5or H3DA. Also i5 net4or* allocates possile co'es 6li*e 'e5aultvalues7 U& can still use other numer o5 co'es 'epen'in0 on the situation. at! U& supports 1co'es, at8 U& supports 1" co'es an' at U& $ supports co'es.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %2 6827




#igure -,. &'amp!e of 4SDP0 J NRT code a!!ocation duration with different &s

The 3 RT allocation 6up0ra'e or initial it rate7 can 5ail i5 there is no 5ree co'e 5or RT DH. A co'e allocation 5ailure causes typically the pac*et sche'uler to allocate o5 lo4er it rate6hi0her 3F7 i5 possile.

The overall co'e loc*in0 can e monitore' 4ith RG!>! 63prea'in0 o'e ?loc*in0 rate inD7 an' per 3F 4ith ?loc*in0 rate o5 3F 'ue to o co'es availale( +s RG12ERG18,counters ;1"""%$E82, ;1"""8!. The total R!! co'e re9uests are 0iven in 3F re9uests;1"""2!E2$. Fi0ure $$ presents an e=ample o5 co'e occupancy an' co'e tree loc*in0rate. +t sho4s that 4hen the avera0e co'e occupancy increases aove "K, the ma=imum co'eoccupancy reaches 1""K an' co'e tree loc*in0 rate increases.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %# 6827




#igure --. Code tree occupancy.

o4 amount o5 co'e loc*in0 can e tolerate' as it is typically 'ue to RT DH allocationattempts 5or lo4 3F earers 63F8 an' 3F1$7. Fi0ure $% presents an' e=ample o5 increase'co'e tree loc*in0 rate an' the 3F6s7 that cause the loc*in0.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %> 6827






si0nallin0 phase. This is seen in the ne=t picture, note the the last 2 samples are 4ith theparameter value o5 , so more co'e 'o4n0ra'e can e seen in that case.

#igure -7. Code downgrade due to NRT with DPC4Over4SPDSC4Thresho!dI9.

Also it 4as 5oun' that 4hen net4or* is allocatin0 all availale co'es 5or H3DA an' there is noU& capaility to 5ully utiliMe those, it is not possile to use remainin0 co'es 5or 3 RT 4hen theparameter D!C6,ver6S!DSC6+hreshold is set to Mero.

#igure -<. Setup fai!s with DPC4Over4SPDSC4Thresho!dI9.

+t that case 5or e=ample it can e seen that re9G3GreQGD counter is up'ate' as there iscapacity up0ra'e re9uests 5rom initial itrate to ma=imum. This can also seen asre9G3GreQGU an' 3 setup 5ail A, 4hich is up'ate' only 4hen there is initial capacityre9uest 5rom DH "/" or 5rom FAH. ?oth cases means that there is no D co'es availale.

+t 4ill e recommen'e' not to use Mero value 5or this parameter unless H3DA 4ill e the only

service 5or Data service.

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %$ 6827




$.1.# C?T3 resource sharin0H3DA has a static reservation 5rom C?T3 resources. This reservation 'epen's on the H3DAsche'uler type an' numer o5 sche'ulers active in the ?T3. The resource reservation o5 R!!tra55ic 'epen's on the tra55ic level an' can e si0ni5icant in share' carrier.

The H3DA return channel is critical 5rom ?T3 HC availaility point o5 vie4 especially in areas4ith hi0h H3DA tra55ic. The return channel can utilise RT DH or H3UA channel type. RTDH return channel reserves ?T3 resources 5rom the U channel element pool. Tale 2presents the & reservation o5 DH earers. The H3DA return channel it rates an' &reservations are hi0hli0hte'.

Ta!e %,. 2TS C& reservation of DC4 earers.

?earer 'ata rate & U/min 3F & D/min 3F

3R? #.>/1#.> *ps 1/ 3F2$ 1/ 3F2$

A;R 6voice7 17 1/ 3F$> 1/ 3F128

C?EA;R 27 1 / 3F$> 1 / 3F128

3 $> *ps > / 3F1$ > / 3F#2

PS $- kps $ 8 S#-1 1 / 3F128

3 #2 *ps 2 / 3F#2 2 / 3F$>

PS -1 kps 1 8 S#$- > / 3F#2

PS $%7 kps 1 8 S#7 > / 3F1$

PS %,- kps 7 8 S#1 8 / 3F8

PS /71 kps $- 8 S#1 1$ / 3F8

H3UA return channel reservation the DH an' &EDH resources share the same D3resource pool. The DH has the hi0hest priority, an' 4hen the resources are le5t 5rom the DH,the resources are 0iven to the &EDH. The H3UA 4ill have a minimum resource allocation o5 8&, this can not e allocate' to DH. The ma=imum total numer o5 H3UA users an' totalthrou0hput 'epen's on the amount o5 availale & resources, e=ample tale 5rom RA3"$elo4(

Ta!e %- "8D" C& reservation for 4SP0 in R0S9- #!e'i 2TS

U/D &reservation 5or H3UA

?asean' 'eco'in0 capaility, hysical ayer ;ps

H3UA U& " ] 1.> 1.> 2.8 >.2 .$

" 8 8 8 8 8 8

1E> 8 #2 #2 $ 8" 112

E8 8 #2 $ $ 8" 112

!E12 8 $ $ 8" 8" 112

1#E1$ 8 $ 8" 112 112 112

1%E2" 8 8" 8" 112 1#$ 1#$

21E2> 8 8" 8" 112 1#$ 1$"

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %% 6827






;""1! ;AGH3UAG&GU +nte0er numer

;""112 ;AGH3UAG&GD +nte0er numer

;""11" ;+GH3UAG&GU +nte0er numer

;""11# ;+GH3UAG&GD +nte0er numer RG!>%a Avera0e ratio o5 utiliMe' & 5or D 5or H3UA in ?T3 K

RG!>8a Avera0e ratio o5 utiliMe' & 5or U 5or H3UA in ?T3 K


;1"""1>$ R?GD:C<RGDU&G?3G?T3

;1"""11 R?GD:C<RGDU&GR&G&;G?T3

;1"""18 R?GR&&A3&GDU&G?3G?T3

;1"""1$# R?GR&&A3&GDU&GR&G&;G?T3

Fi0ure %" elo4 presents an e=ample o5 ?T3 resource reservation 4ith H3DA. The minimumU an' D resource reservation is $ 61$ 5or Hs, 8 5or H3UA an' #2 5or H3DA7. +t alsosho4s that the ma=imum U reservation is normally hi0her.

#igure 69. &'amp!e of 2TS resource sharing with 4SDP0

opyri0ht o*ia 3iemens et4or*s 2""8 ompany con5i'ential a0e %! 6827




Fi0ure elo4 sho4s an e=ample o5 C?T3 resource reservation 4ith H3UA. Cith hi0h level o5 H3DA return channel on DH causes typically hi0h U reservation. The ma=imum H3UAreservation is $>, 4hich is 5or e=ample 'ue to user 4ith Y1.> ;ps throu0hput in Ultrasite ?T3.

#igure 6$. &'amp!e of 2TS resource sharing with 4SP0

ac* o5 ?T3 resources is the most common reason 5or H3DA an' H3UA accessiility5ailures. These 5ailures are monitore' 4ith +s( RG$%>a 6H3DA Access FR 'ue the ?T37,RG!$a 6&EDH 3etup FR 'ue the ?T37, RG!%a 6&EDH ot 3electe' 'ue the ?T3HC7. ;ore aout the return channel per5ormance in 3ections .1.1 an' .1.2.

$.2 &55ect o5 H3A on R!! per5ormance

The main concern relate' to e55ect o5 H3A tra55ic on R!! tra55ic per5ormance is typically relate'to a''itional inter5erence cause' y H3DA in D. This is easy to un'erstan' in a case 4henthe H3DA transmission increases the ?T3 transmit po4er 5rom typical 8 C to ma=imum o5 2"C in matter o5 millisecon's. This increase' level o5 inter5erence can cause call setup prolemsan' call 'rops. The 'ecrease' &c/o can also increase the amount o5 interEsystem han'oversor cell reEselections to <3;, as the &c/o is typically use' as the main criteria tri00erin0 theproce'ures.

Fi0ure %2 presents an e=ample o5 net4or* per5ormance 5or t4o years 5rom the H3DA launch.+n this e=ample the A;R call Retainaility is even improve' 'espite the increase' H3DA tra55ic.The H3DA accessiility an' retainaility are sli0htly 'roppe', ut still remain in 0oo' level.





#igure 6%. &ffect of increased 4SDP0 traffic on CS R02 and 4SP0 earer performance.





Re5erences

I1J H3A Ra'io et4or* lannin0 <ui'eI2J #< Ra'io et4or* lannin0 <ui'elines 5or RA3"$ an' RU1"

https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$#$%$2% I#J RA3"$ ro'uct DocumentationI>J ^+ 5or H3DA lannin0^, 1st )anuary 2""%IJ ;ultilayer 0ui'eline https(//sharenetE

ims.insi'e.no*iasiemensnet4or*s.com/:pen/#8#$2$#8 I$J Fle=i CD;A ?T3 sales 0ui'e E ?asean' 'imensionin0

https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/livelin*/livelin*/0uest/Do4nloa'/#$"111>8

I%J ac*et 3che'uler optimisation 0ui'ehttps(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$>!"!!$

I8J apacity ;ana0ement <ui'e apacity Cor*shop phase 2, )ussi Reunanen et all.https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$#!%2!8#

I!J H3DA B H3UA throu0hput an' parameter testin0 in T https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#!8$1!"

I1"J A; RA3"$ &=periences, aul arsen 12/2""8I11J RA &2& system per5ormance optimiMation 0ui'eI12J + list an' tar0ets recommen'ation 'oc https(//sharenetE

ims.insi'e.no*iasiemensnet4or*s.com/:pen/#$>$1$%##


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/363676257



https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/guest/Download/360111458




















Documents

Data Performance Optimisation Guideline v07