Data Performance Optimisation Guideline v07

1/82 Document Type
Author
Unit/Dept.
Document Title
Date, Version
For 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, ,irsi
Ter-v-inen, .e**a Ranta
Date( 1!.1.2""!
Version( v.".%
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 2 6827
/opyri0ht 1 2o*ia 3iemens 2et4or*s. This material, inclu'in0 'ocumentation an' any relate' computer
pro0rams, is protecte' 8y copyri0ht controlle' 8y 2o*ia 3iemens 2et4or*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 2o*ia 3iemens 2et4or*s. This material also contains con5i'ential in5ormation 4hich may
not 8e 'isclose' to others 4ithout the prior 4ritten consent o5 2o*ia 3iemens 2et4or*s
2.:/23: /apa8ility ;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 mo8ility..........................................................................................
# .3 RA? @o3 parameters..........................................................................
#.1 3peci5ication...........................................................................................................................
#.2 De5inition o5 .3 RA? @o3 in connection setup.......................................................................
> 2RT .3 RA? per5ormance........................................................................
>.1 Accessi8ility............................................................................................................................
>.2 Retaina8ility............................................................................................................................
H3.A 8earer per5ormance.........................................................................
.1 Accessi8ility............................................................................................................................
.1.1 H3D.A UA Return /hannel.................................................................................................
.1.2 H3U.A Accessi8ility............................................................................................................
.2 H3.A Throu0hput an' RTT....................................................................................................
.2.1 H3D.A Throu0hput .+s.......................................................................................................
.2.2 H3U.A Throu0hput .+s.......................................................................................................
.2.# H3D.A optimise' throu0hput..............................................................................................
.2.> H3U.A optimise' throu0hput..............................................................................................
.# ;o8ility...................................................................................................................................
.> Retaina8ility............................................................................................................................
$ H3.A B R!! 8earer inter4or*in0...............................................................
$.1 .o4er, co'e an' /& 6H3U.A7 sharin0...................................................................................
$.1.1 DA po4er sharin0.................................................................................................................
$.1.2 /hannelisation co'e tree sharin0........................................................................................
$.1.# C?T3 resource sharin0.......................................................................................................
$.2 &55ect o5 H3.A on R!! per5ormance.......................................................................................
Re5erences.....................................................................................................
/opyri0ht 1 2o*ia 3iemens 2et4or*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. H3D.ADH3U.A.......12
Fi0ure %. RR/ states an' transitions. RU1" Direct recon5 D/HE./HF......................................................1>
Fi0ure 8. Transition 5rom /&AAGD/H to /&AAGFA/H 4ith Ra'io ?earer Recon5i0uration proce'ure.......1>
Fi0ure !. Transition 5rom /&AAGFA/H to /&AAG./H 6URAG./H7 4ith Ra'io ?earer Recon5i0uration
proce'ure................................................................................................................................................... 1
Fi0ure 1". Trans5er o5 the U& to /&AAGD/H an' reactivation o5 the 'ata connection 6cause UA 'ata
transmission7.............................................................................................................................................. 1
Fi0ure 11. 3ervin0 H3ED3/H cell chan0e tri00ere' 8y perio'ical &c2o measurements...........................1%
Fi0ure 12. 3ervin0 cell chan0e tri00ere' 8y &vent 1? on the servin0 H3D3/H cell 6no 2?A. si0nallin0
presente'7.................................................................................................................................................. 18
Fi0ure 1#. +nterER2/ servin0 H3ED3/H cell chan0e 4ith har' han'over 6no 2?A. si0nallin0 presente'7.
................................................................................................................................................................... 18
Fi0ure 1> .3 RA? setup 5ailure rate statistics 5rom live net4or*................................................................22
Fi0ure 1. .3 RA? Access 5ailure rate statistics 5rom live net4or*............................................................2#
Fi0ure 1$. 2RT .3 RA? retaina8ility analysis............................................................................................ 2
Fi0ure 1% &=ample o5 .3 2RT RA? Active 5ail chan0e 'ue to ?T3...........................................................2$
Fi0ure 18 H H3D.A Accessi8ility Failure Analysis...................................................................................... 28
Fi0ure 1!. &=ample H3D.A accessi8ility .+s 5rom live net4or*.................................................................2!
Fi0ure 2". &=ample H3D.A accessi8ility 5ailure causes............................................................................ 2!
Fi0ure 21. H3D.A accessi8ility 4ith optimisation....................................................................................... #1
Fi0ure 22. H3D.A acessi8ility 5ailure analysis 4ith optimisation steps......................................................#1
Fi0ure 2#. &55ect o5 .r=Aoa';ar0in;a=D/H on H3D.A return channel accessi8ility................................#2
Fi0ure 2>. Relation 8et4een UA /& usa0e an' H3ED3/H setup 5ailures..................................................##
Fi0ure 2. Activation o5 T?: an' 1$ *8ps return channel.......................................................................... #>
Fi0ure 2$. H3U.A Accessi8ility 5ailure analysis......................................................................................... #$
Fi0ure 2%. &=ample o5 H3U.A selection 5ailure causes 5rom live net4or*.................................................#%
Fi0ure 28. &=ample o5 H3U.A setup 5ailure causes 5rom live net4or*......................................................#%
Fi0ure 2!. Relation 8et4een /& usa0e an' H3U.A setup an' selection 5ailures......................................#8
Fi0ure #". Throu0hput per allocate' H3ED3/H I8J.................................................................................... #!
Fi0ure #1. H3D.A throu0hput measurement 5rom ?T3 an' 'rive test lo0.................................................>1
Fi0ure #2. H3U.A throu0hput .+3 an' 'rive test tool measurement.........................................................>#
Fi0ure ##. H3U.A selections an' throu0hput............................................................................................ >#
Fi0ure #>. H3D.A R/A throu0hput 6application level throu0hput is typically 1"K lo4er7 vs. /ompensate'
/@+............................................................................................................................................................. >
Fi0ure #. H3D.A application level throu0hput 4ith 'i55erent H3D.A cate0ory U&s.................................>
Fi0ure #$. /@+ 'istri8ution 'urin0 testin0 5or 'i55erent U&s........................................................................>$
Fi0ure #%. H3D.A throu0hput an' co'e allocation 4hen 2 simultaneous cate0ory 8 H3D.A U&............>$
Fi0ure #8. H3U.A throu0hput 4ith H3U.A 2 ;8ps 5eature.......................................................................>8
Fi0ure #!. H3U.A /ell UA application level throu0hput 4ith 'i55erent num8er o5 H3U.A U&s an' 4ith
'i55erent .r=Tar0et;a=?T3 values 6chan0e' in case o5 # H3U.A U&7......................................................>!
Fi0ure >". H3U.A user throu0hput 4hen # simultaneous H3U.A U&.......................................................>!
Fi0ure >1. UA application level throu0hput o5 1 H3U.A U& 4hen there is 'i55erent num8er o5 U&s in the
cell.............................................................................................................................................................. "
Fi0ure >2. Uplin* .r=Total 4ith 'i55erent num8er o5 H3U.A U&s..............................................................."
Fi0ure >#. Uplin* Aoa' 4ith 'i55erent num8er o5 H3U.A U&s....................................................................1
Fi0ure >>. ?T3 /& H3U.A Usa0e an' H3U.A ;a=imum ;acE' Throu0hput..........................................2
Fi0ure >. ?T3 resource status counters................................................................................................... 2
Fi0ure >$. H3U.A con0estion control an' HC overloa' // Frame loss counter......................................>
Fi0ure >%. Function o5 +u8 con0estion /ontrol........................................................................................... >
Fi0ure >8. Function o5 +u8 con0estion control 5or throu0hput 4ith 'i55erent sym8ol rate............................
Fi0ure >!. H3U.A con0estion control 'ecrease the H3U.A 8it rate 8y 'ecreasin0 the 3ervin0 0rant 4ith
too hi0h sprea'in0 co'e con5i0uration.......................................................................................................
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e > 6827
Fi0ure ". Uplin* throu0hput 4ith 1 = &1 5or H3.A an' 'i55erent .arameter values..................................$
Fi0ure 1. U& t= .o4er limitation vs. H3U.A throu0hput.......................................................................... %
Fi0ure 2. &=ample o5 3// 5ailure reasons............................................................................................... !
Fi0ure #. H3D.A 3// per5ormance compare' to H3D.A retaina8ility....................................................$"
Fi0ure >. H3.A retaina8ility 5ailure analysis............................................................................................. $1
Fi0ure &=ample o5 H3D.A release types 6K7....................................................................................... $2
Fi0ure $ &=ample o5 'i55erent release reasons 5or H3ED3/H channel.....................................................$#
Fi0ure % &=ample o5 &ED/H release........................................................................................................ $>
Fi0ure 8. &55ect o5 D/H po4er on H3D.A throu0hput.............................................................................. $
Fi0ure !. H3E.D3/H co'e reservation.................................................................................................... $
Fi0ure $". DA po4er sharin0 8et4een H3D.A an' 2RT .3 tra55ic............................................................$$
Fi0ure $1. DA po4er sharin0 analysis........................................................................................................ $%
Fi0ure $2. Avera0e UA an' DA loa' as a 5unction o5 H3D.A po4er...........................................................$8
Fi0ure $#. H3D.A /o'e 'o4n0ra'e 'ue to A;R 4ith H3.D3/H;ar0in3F128L"...................................$!
Fi0ure $>. &=ample o5 H3D.A co'e allocation an' sprea'in0 co'e occupancy I8J...................................%"
Fi0ure $. &=ample o5 H3D.A B 2RT co'e allocation 'uration 4ith 'i55erent U&s....................................%1
Fi0ure $$. /o'e tree occupancy................................................................................................................ %2
Fi0ure $%. /o'e tree 8loc*in0, 4ith co'e 'o4n0ra'e 'ue to con0estion...................................................%#
Fi0ure $8. /o'e 'o4n0ra'e 'ue to 2RT 4ith D./H:verH3.D3/HThreshol'L"....................................%>
Fi0ure $!. 3etup 5ails 4ith D./H:verH3.D3/HThreshol'L"..................................................................%>
Fi0ure %". &=ample o5 C?T3 resource sharin0 4ith H3D.A.....................................................................%%
Fi0ure %1. &=ample o5 C?T3 resource sharin0 4ith H3U.A.....................................................................%8
Fi0ure %2. &55ect o5 increase' H3D.A tra55ic on /3 RA? an' H3.A 8earer per5ormance.........................%!
"ist of Ta!es
Ta8le 1. .ac*et 'ata connection relate' in5ormation elements in RR/ /onnection 3etup Re9uest
messa0e...................................................................................................................................................... 8
Ta8le 2. .ac*et 'ata connection relate' in5ormation elements in RR/ /onnection 3etup messa0e...........8
Ta8le #. .ac*et 'ata connection relate' in5ormation elements in RR/ /onnection 3etup /omplete
messa0e...................................................................................................................................................... !
Ta8le >. .ac*et 'ata connection relate' in5ormation elements in Activate .D. /onte=t Re9uest messa0e
................................................................................................................................................................... 1"
Ta8le . .ac*et 'ata connection relate' in5ormation elements in Ra'io ?earer Recon5i0uration messa0e
................................................................................................................................................................... 12
Ta8le $. U;T3 @o3 attri8utes................................................................................................................... 1!
Ta8le % @o3 ne0otiation at .D. conte=t setup.......................................................................................... 2"
Ta8le 8. @o3 values 5or 'i55erent tra55ic classes......................................................................................... 2"
Ta8le !. Reports an' .+s relate' 2RT .3 RA? accessi8ility......................................................................22
Ta8le 1". Reports an' .+s relate' 2RT .3 RA? retaina8ility.....................................................................2>
Ta8le 11. Reports an' .+s relate' H3D.A accessi8ility............................................................................. 28
Ta8le 12. R2/ parameters relate' to /&AAGD/H state selection an' release..........................................#"
Ta8le 1#. Recommen'e' parameters 5or H3D.A UA D/H optimisation....................................................#>
Ta8le 1>. Reports an' .+s relate' H3U.A accessi8ility............................................................................. #
Ta8le 1. H3D.A tra55ic an' throu0hput ,.+s an' counters.......................................................................>"
Ta8le 1$. H3U.A tra55ic an' throu0hput ,.+s an' counters.......................................................................>1
Ta8le 1%. ;a=. user 8it rates 4ith 'i55erent RA3 5eatures........................................................................... >>
Ta8le 18 +u8 'eman' 5or H3D.A hi0h 8itrates 6AT; siMe 1!$8 e9uals to = &1 an' 281"> to %=&17......>%
Ta8le 1!. H3U.A 8itrates 4ith 'i55erent ;a=TotalUplin*3ym8olRate settin0s............................................>8
Ta8le 2". H3U.A con0estion control /ounters.......................................................................................... #
Ta8le 21. H3.A mo8ility counters an' ,.+s............................................................................................... 8
Ta8le 22. H3.A retaina8ility counters an' ,.+s 6Report( 3ervice/3ession Retaina8ility Analysis
R3RA2"%!7............................................................................................................................................... $1
Ta8le 2#. .+s relate' po4er sharin0 8et4een H3.A an' R!! tra55ic..........................................................$$
Ta8le 2>. .+s relate' to channelisation co'e sharin0 8et4een H3.A an' R!! tra55ic................................$8
Ta8le 2. C?T3 /& reservation o5 D/H 8earers....................................................................................... %
Ta8le 2$ UA/DA /& reservation 5or H3U.A in RA3"$ Fle=i ?T3...............................................................%
Ta8le 2%. .+s relate' po4er sharin0 8et4een H3.A an' R!! tra55ic..........................................................%$
/opyri0ht 1 2o*ia 3iemens 2et4or*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 optimisation
tas*s. The main 5ocus is in H3.A 6H3D.A an' H3U.A7 per5ormance 8ut also inter4or*in0 4ith
Rel!! 2RT services is covere'. ?asic H3.A 5unctionality an' parameters is not 'escri8e' here
8ut in H3.A plannin0 0ui'e I2J. 3ome per5ormance relate' si0nallin0 charts are inclu'e' here
also 8asic @o3 in5ormation, 4hich 4ill 8e up'ate' 4ith RU1" 5eatures later. 2RT 5eature
optimiMation is not 'escri8e' here 8ut in .ac*et 3che'uler :ptimiMation 'ocument I%J. There is
also not in5o a8out 'i55erent H3.A layers 4hich is covere' in H3.A layerin0 0ui'e IJ. +t is
recommen'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', also
5or H3.A.
The structure o5 the 'ocument is 5ollo4in0 the 'ata call 5lo4. +n the 8e0innin0 there is chapter 5or
.3 si0nallin0 sho4in0 'i55erent pac*et call setup cases an' mo8ility 8oth in R2/ level an' at U&
si'e. Then there is a chapter 5or .3 RA? @o3 intro'uction. Then there is chapter 5or 2RT .3
RA? per5ormance coverin0 tra'itional service level ,.+s relate' to 2RT .3 RA?. A5ter that there
is chapter 5or H3.A 8earer per5ormance optimiMation coverin0 accessi8ility, throu0hout, mo8ility
an' retaina8ility relate' to H3D.A an' H3U.A. The last chapter is coverin0 the H3.A an'
Rel!! inter4or*in0 relate' mainly to C?T3 resource sharin0.
The per5ormance ,.+s sho4n in the 'ocument is structure' 8ase' on the ne4 RA3"$ reportin0
suite reports. This is online tool, 8ut ,.+s can 8e analyse' also o55line 4ith Anatom2.
/opyri0ht 1 2o*ia 3iemens 2et4or*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 the
pac*et call. This section 'escri8es the main si0nallin0 in5ormation.
2.1 RR/ 3etup
RR/ connection setup proce'ure is per5orme' 4hen U& moves 5rom +'le mo'e to RR/
/onnecte' mo'e. RR/ connection is re9uire' 5or any si0nallin0 5rom U& to the net4or* an' the
setup in5ormation contains also in5ormation relate' to pac*et 'ata connection. The RR/
connection setup si0nallin0 is presente' in Fi0ure 2.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e % 6827
RR/( RR/ /onnection Re9uest 6RA/H7
U& R2/
2o'e ?
2?A.( Ra'io Ain* 3etup Re9uest
2?A.( Ra'io Ain* 3etup Response
AA/A.( &sta8lish Re9uest
AA/A.( &sta8lish /on5irm
F.( Do4nlin* 3ync
F.( Uplin* 3ync
2?A.( 3ynchronisation +n'ication
RR/( RR/ /onnection 3etup 6FA/H7
A1 3ynchronisation
RR/( RR/ /onnection 3etup /omplete 6D/H7
#igure %. RRC connection setup signa!!ing.
The 5ist messa0e 5rom U& is the RR/ /onnection 3etup Re9uest 4hich mainly in'icates the
R2/ that the U& 4ants to esta8lish si0nallin0 connection 4ith the RA2. This messa0e contains
these in5ormation elements that can 8e relate' to pac*et 'ata connection esta8lishment.
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 R2/ an in'ication o5 the service that the U& is re9uestin0.
&sta8lishment cause 'epen's also on U& implementation. /ause value NRe0istrationO is use' to
initiate <.R3 Attach si0nallin0 an' ;easurement 9uantity a8out the 9uality o5 the pilot si0nal. IE
Access stratum release indicator in'icates the R2/ on the release o5 the speci5ication the U&
supports. Release $ U&s are capa8le o5 sen'in0 also the IE UE capability in'ication to in'icate
the H3D.A an'/or H3U.A capa8ility o5 the U&..
Ta!e $. Packet data connection re!ated information e!ements in RRC Connection Setup Re(uest
message
)nformation e!ement *a!ue Description
&sta8lishment cause Re0istration For <.R3 Attach
:ri0inatin0 Hi0h
.riority 3i0nallin0
For .D. /onte=t 3etup
;easurement @uantity &c/2o L E2> D +& / 2 &c2o use' 5or initial UA an'
DA po4er calculation
Access stratum release
in'icator
6A8sence L R!!7, RelE
> / RelE / RelE$
Release o5 the RR/
5unctionality supporte' 8y U&
U& capa8ility in'ication A8sence L 2o H3.A,
H3ED3/H,
H3D3/HD&D/H
+& availa8le only 5rom R$ U&s
The RRC Connection Setup is receive' 5rom R2/ as reply to the re9uest messa0e. This
messa0e mainly contains the con5i0uration o5 the si0nallin0 ra'io 8earers that 4ill 8e use' 5or
the si0nallin0. +t also contains in5ormation 'e5inin0 the ne=t RR/ state an' a re9uest 5or U&
capa8ility.
Ta!e %. Packet data connection re!ated information e!ements in RRC Connection Setup message
RR/ state in'icator /ellED/H 3i0nallin0 continues al4ays in
D/H channel type in 232
RA2
/apa8ility up'ate re9uirement True 3et NtrueO 5or FDD
UARF/2 uplin* /hannel num8er UA +& is provi'e' i5 the 5re9uency
is chan0e' 6can 8e 'one 'ue
to DRR/ proce'ure7
UARF/2 'o4nlin* /hannel num8er DA +& is provi'e' i5 the 5re9uency
is chan0e' 6can 8e 'one 'ue
to DRR/ proce'ure7
The RRC Connection Setup Complete messa0e contains mainly the U& ra'io access capa8ility
in5ormation. There is ran0e o5 in5ormation relate' to U& 'ata connection capa8ility, e.0. H3D.A
an H3U.A 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!ete
message
H3ED3/H physical layer
/ate0ory
1E$> RelE an' later
&ED/H physical layer
/ate0ory
1E1$ RelE$
U& po4er class 1E>
/opyri0ht 1 2o*ia 3iemens 2et4or*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 esta8lishe' a 'e'icate' communication
lin* 4ith UTRA2, it is in a position to sen' a messa0e to the core net4or* 6.3 core in this case7.
Cith the <.R3 attach the U& esta8lishes a <.R3 mo8ility mana0ement conte=t 4ith 3<32.
#igure /. GPRS 0ttach procedure
The purpose o5 the 3ecurity ;o'e proce'ure is to tri00er the start or cipherin0 5or the ra'io
8earers o5 one core net4or* 'omain an' 5or all si0nallin0 8earers. +t is also use' to start inte0rity
protection 5or all si0nallin0 ra'io 8earers.
The .3 core may optionally re9uest the U& to provi'e its i'entity, e.9. +;&+. This is 'one usin0
the Identity Reuest messa0e.
2.2.2 3ervice Re9uest
The 3ervice Re9uest proce'ure is initiate' prior to .D. conte=t setup to 5orm a secure
connection 8et4een the 3<32 an' the U& 5or user 'ata. This is re9uire' i5 no other si0nallin0
4ith 3<32 has prece'e' the .D. conte=t setup. This coul' 8e the case 4ith ;T pac*et call,
8ut it is not supporte' 8y 232.
#igure 1. Service Re(uest procedure.
2.2.# .D. conte=t setup
.D. conte=t 5orms the user 'ata connection 8et4een 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'es
Ra'io Access ?earer 6RA?7 setup an' Ra'io ?earer setup proce'ures. This is 'one to D/H "/".
/opyri0ht 1 2o*ia 3iemens 2et4or*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 8e use' to re9uest a connection to operator speci5ic services li*e CA.
or to internet i5 this is allo4e' 8y the operator.
Ta!e 1. Packet data connection re!ated information e!ements in 0ctivate PDP Conte't Re(uest
message
Re9ueste' @o3 3ee 3ection #.
Re9ueste' +. a''ress ?y 'e5ault +. a''ress is
allocate' automatically.
Access .oint 2ame Access points are 'e5ine' in
the <<32 con5i0uration an'
U& re9uest a connection
to/via speci5ic access point
Re9ueste' service type an' 9uality is 'e5ine' in the Re9ueste' @o3 in5ormation. 3ection #
'escri8es more in 'etail the @o3 'e5inition parameters an' proce'ure. The .D. conte=t setup
proce'ure is complete' 4ith the Activate !D! Conte"t Accept messa0e, 4hich contains mainly
the 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<32 to start the RA? setup
proce'ure. This is initiate' 4hen 3<32 sen's the RA# Assi$nment Reuest messa0e to the
R2/, this messa0e is sent over the +uE.3 inter5ace an' it contains the @o3 o5 the RA?. The
reception o5 the RA# Assi$nment Reuest messa0e tri00ers the a'mission control 6A/7
proce'ure in R2/ an' the 5ollo4in0 ra'io 8earer setup proce'ure. The A/ al0orithm 'e5ines the
ma=imum 8it rate o5 the ra'io 8earer, tar0et ?A&R an' other 8earer parameters.
+n 232 RA2 the initial 8it rate allocate' in the RA? setup proce'ure o5 the 2RT RA? is al4ays
Mero 6RA? "/"7. Thus there is no nee' 5or resource reservations in this phase. The Ra'io ?earer
3etup messa0e sent 5rom R2/ to U& contains the ne=t state 6in 232 RA2 cellED/H7 some
Ra'io ?earer in5ormation 6RA/, Tr/H7, 8ut no 8it rate allocations. There is also no ra'io lin*
setup 4ith 2o'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 8een esta8lishe' the R2/ sen's a measurement control messa0es to the
U& 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 UA
capacity 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 internally
R2/. Typically U& initiates the connection to the server an' the capacity re9uest comes 5rom
the U&. The 'ata 5lo4 setup involves pac*et sche'ulin0, channel type selection an' resource
reservation 5or the selecte' connection type.
#igure -. Capacity re(uest and resource a!!ocation signa!!ing for packet data ca!!. 4SDP054S.P0
U& sen's the %easurement Report messa0e 5or &vent >A in'icatin0 that there is some 'ata in
the 8u55ers. This measurement report is han'le' as capacity re9uest 8y the pac*et sche'uler in
the R2/, 4hich sche'ules the capacity re9uest. The sche'ulin0 operation starts 4ith channel
type selection proce'ure, 4here the R2/ ma*es a selection 8et4een H3.A, H3D.A, D/H or
common channel usa0e. 3che'ulin0 inclu'es also allocation o5 8it rates 5or D/H 8earers
6allo4e' transport 5ormat set7 8ase' on R2/ parameters an' loa' con'itions.
Message
#i!e -. &'amp!e of 3easurement Report message.
The selecte' ra'io 8earer con5i0uration is sent in the Radio #earer Reconfi$uration messa0e to
the U& an' 4ith the 5ollo4in0 Radio &in' Reconfi$uration !repare messa0e to the 2o'e ?.
Ta!e ,. Packet data connection re!ated information e!ements in Radio 2earer Reconfiguration
message
RR/ state in'icator cellED/H, cellEFA/H The initial 8it rate allocation is
typically 'one to D/H channel
at pac*et call setup
Uplin* transport channel
Type
D/H, RA/H, &ED/H 3electe' UA the channel type
Do4nlin* transport channel
Type
D/H, FA/H, H3E
D3/H, D/H D
H3D3/H
3electe' DA the channel type
;A/E' .DU siMe ##$ or $$ ##$ use' as 'e5ault in 232
RA2, $$ use' 5or hi0her
H3D.A 'ata rates.
;a=imum channelisation co'es s5>, 2s5>, 2s52an'2s5> ;a=imum /hannelisation
co'e con5i0uration 5or
H3U.A.
3ervin0 <rant value "E#%, #8 +nitial 0rant value 5or H3U.A,
#8 means no 0rant. Value is
'e5ine' 8y ?T3 an' si0nalle'
to R2/ an' to U& in this +&.
3prea'in0 5actor 6UA7 >E128 ;inimum sprea'in0 5actor o5
the UA D/H channel.
;easurement .o4er :55set E$..1# '? ;easurement po4er o55set P
in'icatin0 the current availa8le
H3D.A po4er relative to pilot.
U& utilises the value in /@+
reportin0.
UARF/2 uplin* /hannel num8er UA +& is provi'e' i5 the 5re9uency
is chan0e' 6not 'one in
pac*et call setup7
UARF/2 'o4nlin* /hannel num8er DA +& is provi'e' i5 the 5re9uency
is chan0e' 6not 'one in
pac*et call setup7
/opyri0ht 1 2o*ia 3iemens 2et4or*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.
R2/ or'ers the U& 4ith the %easurement Control messa0e to stop the tra55ic volume
measurements, i5 the U& has 8een allocate' the ma=imum availa8le 8it rate o5 H3.A channel
type, as there is no use 5or the U&s to re9uest hi0her 8it rate. +5 the U& is allocate' a lo4er than
ma=imum 8it rate, then the R2/ mo'i5ies the &vent >A reportin0 threshol' accor'in0 to the
allocate' 8it rate 6Fle"ible Up$rade 5eature provi'es possi8ility to 'e5ine 8it rate speci5ic
threshol's7.
A7 RelE U&, initial UA rate ?7 RelE$ U&, H3.A allocate'
Message Message
#i!e 7. &'amp!e of 3easurement Contro! message used to modify8re!ease the .! traffic vo!ume
measurement.
2.2. RR/ state transitions
The R2/ 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. Chen
the U& is trans5erre' 5rom /&AAGD/H to /&AAGFA/H state, the ra'io 8earer is recon5i0ure' to
use common channels 6RA/H/FA/H7 4ith Radio #earer Reconfi$uration proce'ure. The
!hysical &ayer Reconfi$uration proce'ure is use' to trans5er the U& to/5rom the /&AAG./H an'
URAG./H 6RU1" 5eature7 states. +n this proce'ure the physical layer an' transport channel
resources are release' 8ut R? 6coul' 8e 4ith 3R? only7, RA? an' .D. conte=t remain active
to4ar's +uEinter5ace.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 1> 6827
#igure 6. RRC states and transitions. R.$9 Direct reconf DC4+PC4:
The transition o5 the U& 5rom /&AAGD/H to /&AAGFA/H is per5orme' 4ith the Radio #earer
Reconfi$uration messa0e 6see Fi0ure 8 an' File !A7. +t is initiate' 8y the R2/ in 8asis o5 'ata
transmission inactivity 8oth in UA an' DA or lo4 measure' throu0hput. This transition inclu'e'
the release o5 the ?T3 an' +u8 resources reserve' 5or the connection. The common channel
resources are use' in /&AAGFA/H 5or the 'ata an' si0nallin0.
#igure 7. Transition from C&"";DC4 to C&"";#0C4 with Radio 2earer Reconfiguration procedure.
The transition o5 the U& 5rom /&AAGFA/H to /&AAG./H is per5orme' 4ith the .hysical
/hannel Recon5i0uration messa0e 6see Fi0ure ! an' File !?7. +t is initiate' 8y the R2/ in 8asis
o5 'ata transmission inactivity 8oth in UA an' DA. +n /&AAG./H state the U& is receivin0 the
pa0in0 messa0es. Transition to URAG./H is per5orme' 4ith the same si0nallin0 proce'ure.
#igure <. Transition from C&"";#0C4 to C&"";PC4 =.R0;PC4> with Radio 2earer
Reconfiguration procedure.
A7 R? recon5i0uration
5rom /&AAGD/H to /&AAGFA/H
?7 .hysical channel recon5i0uration
5rom /&AAGFA/H to /&AAG./H
Message
FF
Message
#i!e <. &'amp!e of Radio 2earer reconfiguration and Physica! channe! reconfiguration messages
used in the RRC state transitions.
The reEactivation o5 the 'ata connection can 8e initiate' 8y the U& 8y usin0 the Cell Update
messa0e 6cause UA 'ata transmission, see Fi0ure 1" an' File 1"A7 or 8y the R2/ 8y pa0in0
the U&. The R2/ either *eeps the U& in /&AAGFA/H or moves it to /&AAGD/H 4ith the Ra'io
#earer Reconfi$uration proce'ure.
#igure $9. Transfer of the .& to C&"";DC4 and reactivation of the data connection =cause ." data
transmission>.
A7 /ell up'ate ?7 Ra'io 8earer recon5i0uration 5rom /&AAGFA/H to /&AAGD/H6H3D.A7
Message Message
/opyri0ht 1 2o*ia 3iemens 2et4or*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!ume
measurement.
2.2.$ .ac*et 'ata connection mo8ility
The proce'ure use' 5or mo8ility 'epen's on channel type in use. 2ormal D/H channels utilise
the so5t han'over proce'ure an' in /&AAGFA/H//&AAG./H states a cellEreselection proce'ure
is use' to0ether 4ith /ell Up'ates. +n /&AAGD/H 4ith H3.A channels the mo8ility is in most
cases per5orme' 4ith the so5t han'over proce'ure com8ine' 4ith 3ervin0 H3ED3/H cell
chan0e, 4hich is re9uire' as H3D.A 'oes not support so5t han'overs. RA3"$ R2/ supports
also a H3D.A cellEreselection proce'ure, 8ut this is availa8le only 4hen H3U.A is not active
an' servin0 cell chan0e is not activate'.
The 3ervin0 H3ED3/H cell chan0e can 8e tri00ere' 8y multiple 'i55erent tri00ers
U& 8ase' measurements( .erio'ical &c2o measurements, &vent1? or &vent1/ to
remove current 3ervin0 H3ED3/H cell
?T3 3+Rerror measurements on 3ervin0 H3ED3/H cell
Aoss o5 UA synchronisation in'ication 5rom ?T3
The 3ervin0 H3ED3/H cell chan0e proce'ure can 8e 5or8i''en in some cases li*e 4hen interE
R2/ 3H: is not supporte' or the 3ervin0 H3ED3/H cell chan0e is not ena8le'. +n these cases
the chan0e o5 cell is per5orme' via /&AAGFA/H.
An e=ample o5 si0nallin0 5or 3ervin0 H3ED3/H 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 11A7 that is use' to
chan0e the po4er o55set o5 /@+, @/, an' 2A/, 8its in the H3ED.//H, as RA3"$ R2/ uses
'i55erent values 5or sin0le lin* an' 3H: connections. Also the perio'ical &c2o measurements
are activate' 5or all active set cells. The 'ecision 5or the 3// is 'one 8ase' on these perio'ical
measurements.
/opyri0ht 1 2o*ia 3iemens 2et4or*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& a8out the chan0e o5 the
servin0 H3ED3/H cell 6see File 11/7. This in5ormation is in'icate' in the +&( 3ervin0 H3ED3/H
+n'icator 5or RA.
A7 .hysical channel
recon5i0uration to
3H: con5i0uration
?7 .hysical channel
recon5i0uration to
sin0le lin*
con5i0uration
/7 ;easurement control
messa0e use' to activate
the perio'ical &c2o
measurements
D7 Ra'io 8earer
recon5i0uration to
chan0e servin0 H3E
D3/H cell
Message Message Message Message
#i!e $$. &'amp!e of messages used for Serving Ce!! Change procedure.
The 3// can 8e tri00ere' also 8y an &vent 1? to remove the current servin0 H3ED3/H cell
5rom the active set 6see Fi0ure 127. +n this case the Ra'io ?earer Recon5i0uration messa0e is
use' 5irst to chan0e the servin0 H3ED3/H cell an' then the Active 3et Up'ate to remove the
previous servin0 H3ED3/H cell 5rom the active set. +5 there is only one cell in active set a5ter the
up'ate, then the .hysical /hannel Recon5i0uration is use' to chan0e to /@+, 2A/, an' A/,
o55sets to the sin0le lin* values.
#igure $%. Serving ce!! change triggered y &vent $2 on the serving 4SDSC4 ce!! =no N20P
signa!!ing presented>.
The servin0 H3ED3/H cell chan0e can 8e per5orme' 4ith har' han'over 4hen the 3H: is not
possi8le, e.0. in interER2/ mo8ility i5 interER2/ 3H: is not supporte'. Fi0ure 1# presents the
si0nallin0 o5 an interER2/ mo8ility 4ith H3.A. The interER2/ cell chan0e tri00ers also the U&
/apa8ility &n9uiry an' UTRA2 ;o8ility +n5ormation proce'ures.
#igure $/. )nter+RNC serving 4S+DSC4 ce!! change with hard handover =no N20P signa!!ing
presented>.
H3ED3/H +3H: si0nallin0 can 8e seen 8elo4. First there 4ill 8e ra'ioG8earerGrecon5i0uration to
D/H, theen compresse' mo'e 4ith physicalGchannelGrecon5i0uration, cell chan0e or'er 6//:7
to <.R3, then AAU B RAU an' 5inally imme'iate assi0nment to start 'ata 5lo4 in &<.R3.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 1! 6827
# .3 RA? @o3 parameters
#.1 3peci5ication
A set o5 U;T3 8earer attri8utes have 8een 'e5ine' to speci5y the U;T3 service. They are liste'
on the ta8le 8elo4. Chen a U;T3 8earer is esta8lishe', mo'i5ie' or release', aspects such as
the U& capa8ilities, su8scription pro5iles an' net4or* speci5ic @o3 pro5iles have to 8e ta*en
un'er consi'eration.
Ta!e -. .3TS ?oS attriutes.
#.2 De5inition o5 .3 RA? @o3 in connection setup
U& initiates the .3 RA? setup 8y sen'in0 a .D. conte=t re9uest to the 3<32 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<32 compares the reuested (oS to the (oS profile in HAR 63ee Ta8le 87. The @o3 pro5ile is
'e5ine' 5or each su8scri8er per Access .oint 6A.7 in the Home Aocation Re0ister 6HAR7 an'
each .D. conte=t has to ne0otiate its o4n @o3 pro5ile. @o3 pro5iles 5or 'i55erent .D. conte=ts
o5 one su8scri8er can all 8e 'i55erent. +n 2o*ia R!! HAR, @o3 attri8utes are con5i0ura8le.
2o*ia 3<32 'o4n0ra'es the @o3 i5 necessary an' sen's the ne0otiate' @o3 to the <<32. 627
The ne0otiate' @o3 is limite' 8y the appropriate values 'e5ine' 5or each tra55ic class in the
#<.. speci5ication T32#.1"%. The limitations 5or the tra55ic classes are accor'in0 to the
5ollo4in0 Ta8le 8.
Ta!e 7. ?oS va!ues for different traffic c!asses.
+5 a 3ervice 8ase' @o3 control 5eature is use' in 2o*ia <<32 6Rel. 7, the <<32 may restrict
the ne0otiate' @o3 5urther. The <<32 session mana0ement an' a'mission control 5unction
selects the treatment class 6TR&/7 8ase' on use' access point an' service 6service 'etection
an' s4itchin07. The selecte' TR&/ is mappe' to the #<.. @o3 attri8utes in the <<32 5or the
@o3 ne0otiation 4ith the 3<32. <<32 can not allocate hi0her @o3 than re9ueste' 8y 3<32.
6#7
> 2RT .3 RA? per5ormance
+t is 4orth o5 mentionin0 here that RA2 ,.+ 'oes not al4ays mean en' user perception. 3o +5
2RT RA? 'rops it is possi8le that en' user 'oes not see it 'ue to RA? reEesta8lishment
proce'ure, 5or e=ample.
>.1 Accessi8ility
+n normal net4or* con'itions there shoul' not 8e 2RT .3 RA? access 5ailures as there is no
resource reservation 'one in the RA? setup an' access phases 5or 2RT RA?.
The RA? setup proce'ure is starte' 4ith RA? Assi0nment re9uest messa0e 5rom /2 6see
Fi0ure 7. The 2RT .3 RA? setup 'oes not re9uire any resource reservation as no ra'io lin* is
setup at his phase.
Hi0h level RA? ,.+ E R2/G1%a RA? 3etup an' Access /omplete Ratio 5or 2RT 3ervice 5rom
User perspective can 8e use' to monitor RA? accessi8ility 5rom user point o5 vie4. Ao4
per5ormin0 cells can 8e then ran*e' to more 'etail analysis.
%
T_PS_INTER RAB_STP_AT T_PS_BACKG RAB_STP_AT
INTER C_COMP_PS_ RAB_STP_AC BACKG C_COMP_PS_ RAB_STP_AC
100 RNC_156a
+
+
=
The 5ailure reasons 5or 2RT .3 RA? 3etup an' Access are limite' to
The .3 RA? setup attempt is not starte' 'ue to re9ueste' parameters not supporte' 8y
the U& or R2/
/ounters ( ;1""1/28 RA?G3T.GFA+AG.3GU&G/A.A, ;1""1/2%
RA?G3T.GFA+AG.3G2:TG3U..G.AR
The RA? setup attempt counters are not up'ate' in this case
RA? assi0nment 5ails 'ue to A/
/ounters( R2/G#%$aL;1""1/1" RA?G3T.GFA+AG.3G?A/,<GA/,
R2/G#8>aL;1""1/11" RA?G3T.GFA+AG.3G+2T&RGA/
.+s( R2/G1"%#a 6RA? 3etup FR 5or .3 +B? calls 'ue to A/7
There is no chec* o5 air inter5ace resources in 2RT .3 RA? setup
R2/ 'eci'es to reQect the .3 RA? re9uest 'ue to R2/ internal 5ailure
/ounters( R2/G#8%a L ;1""1/112 RA?G3T.GFA+AG.3G?A/,<GR2/, R2/G#%!a
L ;1""1/1"% RA?G3T.GFA+AG.3G+2T&RGR2/
.+s( R2/G1"%$a 6RA? 3etup FR 5or .3 +B? calls 'ue to R2/7
The num8er o5 RA? setup 5ailures cause' 8y on0oin0 relocation or har' han'over 5or .3
'ata interactive.
/ounters(;1""1/1"8GRA?G3T.GFA+AG.3G+2T&RGA2/H,
;1""1/11#GRA?G3T.GFA+AG.3G?A/,<GA2/H
.+s( R2/G1"%>a 6RA? 3etup FR 5or .3 +B? calls 'ue to A2/H7
2o RR/( Ra'io ?earer 3etup /omplete messa0e receive' 5rom the U&
/ounters( R2/G>"#aL;1""1/1#2 RA?GA//GFA+AG.3G+2T&RG;3,
R2/G>">aL;1""1/1#> RA?GA//GFA+AG.3G?A/,<G;3
.+s( R2/G1"%8a 6RA? 3etup Access FR 5or .3 +B? calls 'ue to U&7
Ta8le ! lists the reports an' .+s relate' to 2RT .3 RA? per5ormance monitorin0 an' 5ailure
analysis. The RA? setup 5ailures 'ue to transmission 6R2/G1"%a7 are not relate' to RA?
setup phase 8ut to actual ra'io 8earer resource allocation or mo'i5ication, this .+ or relate'
counters ;1""1/1"$ an' ;1""1/111 are not supporte' in RU1" R2/.
Ta!e <. Reports and P)s re!ated NRT PS R02 accessii!ity
.+ re5 .+ name / A88reviation .+ unit
Report( 3ystem .ro0ram R23RA2"""
R2/G%$' .ac*et 3ervice 3etup 3uccess Ratio 6/33R7 K
R2/G$1$a RA? Attempts .3 +nteractive an' ?ac*0roun' R
R2/G1%a
RA? 3etup an' Access /omplete Ratio 5or 2RT 3ervice 5rom User
perspective K
Report( 3ervice/3ession Accessi8ility Analysis R3RA2"%#
R2/G1"%1a RA? 3etup Attempts 5or .3 +B? calls R
R2/G1"%2a RA? 3etup /omplete' 5or .3 +B? calls R
R2/G1"%#a RA? 3etup FR 5or .3 +B? calls 'ue to A/ K
R2/G1"%>a RA? 3etup FR 5or .3 +B? calls 'ue to A2/H K
R2/G1"%a RA? 3etup FR 5or .3 +B? calls 'ue to TRA23 K
R2/G1"%$a RA? 3etup FR 5or .3 +B? calls 'ue to R2/ K
R2/G1"%%a RA? 3etup FR 5or .3 +B? calls 'ue to FR:S?3 K
R2/G1"%8a RA? 3etup Access FR 5or .3 +B? calls 'ue to U& K
R2/G1"%!a RA? 3etup Access FR 5or .3 +B? calls 'ue to R2/ K
Fi0ure 1> presents an e=ample o5 .3 RA? accessi8ility per5ormance. +t sho4s that the 5ailure
rate are very lo4, typically 8elo4 "."> K an' that the R2/ 5ailures are most typical in this
e=ample. R2/ 5ailures can 8e stu'ie' in more 'etail 4ith R2/ internal +/3U lo00in0. Fi0ure 1
sho4s e=ample o5 RA? access 5ailure statistics.
/opyri0ht 1 2o*ia 3iemens 2et4or*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 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 2> 6827
>.2 Retaina8ility
The 2RT .3 RA? consists o5 +u 8earer an' ra'io 8earer. The ra'io 8earer can utilise multiple
'i55erent channel types 6D/H, H3.A or ///H7. The retaina8ility o5 a 2RT .3 RA? 4ill 'epen'
on the +u 8earer an' ra'io 8earer per5ormance.
RA? active starts 4hen the R2/ sen's a RA2A.( RA# ASSI)*%E*+ RES!,*SE messa0e
to the /2 6see Fi0ure 7. RA? active is complete' 4hen the R2/ receives a RA2A.( RA#
ASSI)*%E*+ RE(UES+ messa0e 5rom the /2 4ith the +&( RA# release, an' then
ac*no4le'0es that 8y sen'in0 a RA2A.( RA# ASSI)*%E*+ RES!,*SE messa0e to the /2.
A5ter that, the R2/ releases RA? resources, that is, RA? active phase en's 8e5ore the release.
RA? active is complete' also 4hen the R2/ receives a RA2A.( IU RE&EASE C,%%A*D
messa0e 5rom the /2, an' then releases RA? resources, that is, RA? active phase en's a5ter
the release.
Hi0h level RA? ,.+ E R2/G%#$a 6RA? 3uccess Ratio, 2RT 3ervices, 5rom User .erspective7
can 8e use' to monitor RA? retaina8ility. Ao4 per5ormin0 cells can 8e then ran*e' to more
'etail analysis.
%
B) & (I failure a!"i#e RAB B) & (I releae a!"i#e RAB B) & (I !$%&le"i$' a!"i#e RAB
B) & (I "a"e PC( i' failure a!"i#e RAB ) B) & (I failure a!"i#e RAB
100 100 RNC_*+6a
+ +
=
RA? active 5ails 4hen an inter5aceErelate' 6+u, +ur, +u8, or Uu7 or R2/ internal 5ailure occurs, an'
the 5ailure causes the release o5 the RA? connection.
/ause' 8y ra'io inter5ace synchronisation
.+( R2/G1"8$a 6RA? Active FR 5or .3 +B? 'ue to RAD+:7
/ounters( ;1""1/18$G RA?GA/TGFA+AG.3G+2T&RGRAD+:, ;1""1/1!2G
RA?GA/TGFA+AG.3G?A/,<GRAD+:
release is re9ueste' 'ue to ra'io inter5ace synchronisation 5ailure
/ause' 8y ?T3 65or e=ample, ra'io lin* setup or recon5i0uration pro8lem7
.+( R2/G1"8%a 6RA? Active FR 5or .3 +B? 'ue to ?T37
/ounters( ;1""1/18%G RA?GA/TGFA+AG.3G+2T&RG?T3, ;1""1/1!#G
RA?GA/TGFA+AG.3G?A/,<G?T3
release is re9ueste' 'ue to ?T3 5ailure
A8normal reason relate' to +uEinter5ace
.+( R2/G1"8a 6RA? Active FR 5or .3 +B? 'ue to +U7
/ounters( ;1""1/18GRA?GA/TGFA+AG.3G+2T&RG+U, ;1""1/1!1G
RA?GA/TGFA+AG.3G?A/,<G+U
/ause' 8y 'ri5t R2/ proce'ures
.+( R2/G1"88a 6RA? Active FR 5or .3 +B? 'ue to +UR7
/ounters( ;1""1/1!"G RA?GA/TGFA+AG.3G+2T&RG+UR, ;1""1/1!>G
RA?GA/TGFA+AG.3G?A/,<G+UR
/ause' 8y U&
.+( R2/G1"!1a 6RA? Active FR 5or .3 +B? 'ue to U&7
/ounters( ;1""1/#!%GRA?GA/TGFA+AG.3G+2T&RGU&,
;1""1/#!8GRA?GA/TGFA+AG.3G?A/,<GU&
8ecause the U& is not respon'in0 to an RR/ messa0e or the U& is respon'in0
4ith such 5ailure messa0e that the connection must 8e release'
/ause' 8y inte0rity chec*
.+( R2/G1"8!a 6RA? Active FR 5or .3 +B? 'ue to +G/H,7
/ounters( ;1""1/18!GRA?GA/TGFA+AG.3G+2T&RG+G/H,,
;1""1/1!GRA?GA/TGFA+AG.3G?A/,<G+G/H,,
This counter is never up'ate'.
3ome reason not covere' 8y the other 5ailure counters
.+( R2/G1"!"a 6RA? Active FR 5or .3 +B? 'ue to R2/7
/ounters( ;1""1/1!"G RA?GA/TGFA+AG.3G+2T&RGR2/, ;1""1/1!$G
RA?GA/TGFA+AG.3G?A/,<GR2/
+t shoul' 8e note' that RA? retaina8ility is not same than R? retaina8ility, 8ecause it is possi8le
to reEesta8lish the R? in si'e RA2 68y settin0 T#1 parameter 0reater than "7 4hen havin0
e=istin0 RA? connection to the core net4or*. +n RU1" it is possi8le to have RA? reE
esta8lishment also 5or Voice.
Ta8le 1" lists the relevant reports an' .+s 5or 2RT .3 RA? retaina8ility monitorin0 an'
trou8leshootin0.
Ta!e $9. Reports and P)s re!ated NRT PS R02 retainai!ity
Report( 3ystem .ro0ram R23RA2"""
R2/G$1$a RA? Attempts .3 +nteractive an' ?ac*0roun' R
R2/G$18 RA? 3uccess Ratio, 2RT 3ervices, 5rom 2et4or* .erspective K
R2/G%#$a RA? 3uccess Ratio, 2RT 3ervices, 5rom User .erspective K
Report( 3ervice/3ession Retaina8ility Analysis R3RA2"%!
R2/G1"8>a RA? 3etup Access /ompletions 5or .3 +B? R
R2/G1"8a RA? Active FR 5or .3 +B? 'ue to +U K
R2/G1"8$a RA? Active FR 5or .3 +B? 'ue to RAD+: K
R2/G1"8%a RA? Active FR 5or .3 +B? 'ue to ?T3 K
R2/G1"88a RA? Active FR 5or .3 +B? 'ue to +UR K
R2/G1"8!a RA? Active FR 5or .3 +B? 'ue to +G/H, K
R2/G1"!"a RA? Active FR 5or .3 +B? 'ue to R2/ K
R2/G1"!1a RA? Active FR 5or .3 +B? 'ue to U& K
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 2$ 6827
#igure $-. NRT PS R02 retainai!ity ana!ysis
?elo4 is one e=ample o5 2RT .3 RA? retaina8ility, it can 8e seen that 5ail 'ue to ?T3 has 8een
'ecrease' 8y intro'ucin0 the 1$ *?its/s UA return channel 'urin0 1.>. This is 8ecause 'ue to
chan0e i5 UA return channel 8itrate there is more channel element 6/&7 capacity in the tar0et
cell to han'le 3H: 5or 2RT.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 2% 6827
Ao4 2RT .3 RA?
retaina8ility 6cell7
/hec* 2RT .3 ra'io 8earer 5ailures 'ue
to ra'io
/hec* ?T3 HC resources, can 8e cause'
8y 5aile' 3// 'ue to H3D.A ret channel
/hec* core net4or* parameter settin0s
+nter R2/ mo8ilityF
R2/ +nternal .ro8lem
6
Terminal .ro8lem
2o Action
2ee'e'
2RT .3 RA?
active 5ail 'ue to
ra'io
2RT .3 RA?
active 5ail 'ue
?T3
2RT .3 RA?
active 5ail 'ue to
+u
ReQections
2RT .3 RA?
active 5ail 'ue to
+ur
2RT .3 RA?
active 5ail 'ue to
R2/
2RT .3 RA?
active 5ail 'ue to
U&
2o
Tes
Tes
Tes
Tes
Tes
Tes
Tes
2o
2o
2o
2o
2o
#igure $6 &'amp!e of PS NRT R02 0ctive fai! change due to 2TS

H3.A 8earer per5ormance
.1 Accessi8ility
H3U.A cannot 8e esta8lishe' 4ithout H3D.AU i5 H3U.A is supporte' the H3D.A UA return
channel is H3U.A instea' o5 R!!. +n 8oth cases, the Hi0h level 3etup proce'ure is the sameU
R2/ starts 8y allocation a "/" *8ps connection an' selection 8et4een D/H an' &ED/H is then
complete' 4hen R2/ receives the uplin* or 'o4nlin* capacity re9uest.
Hi0h level H3D.A ,.+ E R2/G$"a can 8e use' to monitor H3D.A accessi8ility 5rom user point
o5 vie4. Ao4 per5ormin0 cells can 8e then ran*e' to more 'etail analysis.
&(uation $. RNC;-9,a 4SDP0 accessii!ity from user point of view
The H3GD3/H setup an' 3election can 5ail 'ue the many reasons. Chen monitorin0 H3D.A
setup 5ailure counters it is important to un'erstan' root cause o5 the 5ailure. Typically setup
5ailures in'icate resource shorta0e, an' as can 8e seen 5rom 5lo4 chart 8elo4 6Fi0ure 187, these
pro8lems are o5ten relate' to H3D.A UA D/H return channel rather than H3D.A ;acE' 5lo4
itsel5. ?ut i5 there are not enou0h resources to set up H3D.A UA D/H return channel, the
H3D.A ;acE' 5lo4 setup 4ill 5ail also.
#igure $7 @ 4SDP0 0ccessii!ity #ai!ure 0na!ysis
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 2! 6827
Ao4 H3D.A
accessi8ility 6cell7
/hec* 2um8er o5 simultaneous H3D.A
users in ?T3 or cell level 'epen'in0 on the
sche'uler type
/hec* ?H /hannel &lement resource
Usa0e
6Aac* o5 /& 5or UA return /hannel7
/hec* ?H UA .o4er /on0estion
6Aac* o5 Ra'io resources 5or UA return
/h.7
/hec* ?H AAA2 +u8 con0estion
6Aac* o5 +u8 resources 5or UA return /h.7
/hec* R? recon5i0uration 5ailure rate
6Terminal .ro8lem7
6
/hec* R2/ Unit loa' 6D;.<7, ma=
num8er o5 users/R2/, D3. 5ailures an'
5aulty alarms
2o Action
2ee'e'
Too many H3D.A
users reache'
H3D.A 3etup Fail
'ue ?T3
ReQection o5 UA
Return /hannel
ReQections
H3D.A 3etup Fail
+u8 6?oth UA B
DA7
H3D.A 3etup Fail
U&
H3D.A 3etup Fail
R2/ +nternal
2o
Tes
Tes
Tes
Tes
Tes
Tes
Tes
2o
2o
2o
2o
2o

+ +
+ + + +
+ + +
+ + +
+ +
+
=
% 100
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
RNC_605a
BGR DSCH HS IUB FAIL SETUP INT DSCH HS IUB FAIL SETUP
BGR DSCH HS BTS FAIL SETUP INT DSCH HS BTS FAIL SETUP BGR DSCH HS UE FAIL SETUP
INT DSCH HS UE FAIL SETUP BGR DSCH HS RNC FAIL SETUP INT DSCH HS RNC FAIL SETUP
BGR RET DSCH HS REJ INT RET DSCH HS REJ BGR USERS 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 H3D.A accessi8ility pro8lems can 8e also relate' to
+uE.3 or +.E?? capacity pro8lems. H3D.A channel type selection can 8e also 5ail 'ue the
Do4nlin* po4er i5 static po4er allocation is use' instea' o5 Dynamic resource/po4er allocation.
There shoul' 8e also enou0h resource to set up H3G3//H.
Ta8le 11 lists the relevant reports an' .+s 5or H3D.A R? accessi8ility monitorin0 an'
trou8leshootin0. 2ote( H3D.A access 5ailure rate .+s are currently 'e5ine' as K o5 all 5ailures
not all selections.
Ta!e $$. Reports and P)s re!ated 4SDP0 accessii!ity
Report: System !ro$ram R*SRA*---
R2/G!#"a .ac*et 3ession Attempts 65or R!! B H3.A7 R
R2/G!1$a .ac*et 3ession 3etup 3uccess Ratio 5or 2RT 65or R!! B H3.A7 K
R2/G$1>a H3ED3/H selections 65or H3D.A only7 R
R2/G$"a H3D.A Resource Accessi8ility 5or 2RT Tra55ic 6user7 65or H3D.A only7 K
R2/G!2$a H3D.A attempts 65or H3D.A an' H3U.A7 R
R2/G!1>a H3D.A 3etup 3uccess Ratio 5rom user perspective 6H3D.A B H3U.A7 K
Report: Service.Session Retainability Analysis RSRA*-/0 1%2-334 %2--35
R2/G!#"a .ac*et 3ession Attempts 65or R!! D H3.A7 R
R2/G!$%a .3 /all 3etup FR 'ue to A/ 65or R!! DH3.A7 K
R2/G!a .3 /all 3etup FR 'ue to ?T3 65or R!! DH3.A7 K
R2/G1"8"a .3 3etup FR 5or +B? 'ue to lac* o5 D;/U 65or R!! DH3.A7 K
R2/G1"81a .3 3etup FR 5or +B? 'ue to Transport 65or R!! D H3.A7 K
R2/G1"82a .3 3etup FR 5or +B? 'ue to U& 65or R!! DH3.A7 K
R2/G1"8#a .3 3etup FR 5or +B? 'ue to :thers 65or R!! DH3.A7 K
R2/G$1>a H3ED3/H selections 65or H3D.A only7 R
R2/G$$>a H3D.A Access FR 'ue to R2/ 65or H3D.A only7 K
R2/G$%>a H3D.A Access FR 'ue to ?T3 65or H3D.A only7 K
R2/G$$$a H3D.A Access 5ailures 'ue to +u8 65or H3D.A only7 K
R2/G$$8a H3D.A Access FR 'ue to U& 65or H3D.A only7 K
R2/G$$2a H3D.A Access FR 'ue to UA D/H 65or H3D.A only7 K
R2/G$%2a H3D.A Access FR 'ue to A;RDH3.A 65or H3D.A only7 K
R2/G$$"a D/H 3electe' 'ue to too many H3D.A users 65or H3D.A only7 K
Fi0ure 1! presents an e=ample o5 H3D.A accessi8ility .+s 5rom live net4or*. +t sho4s that the
R2/G!1$a, R2/G$"a an' R2/G!1>a 5ollo4 the same tren' an' on other han' the .3 RA?
accessi8ility is 1""K all the time as e=pecte' 6see 3ection >.17.
/opyri0ht 1 2o*ia 3iemens 2et4or*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 H3D.A access 5ailure cause. +n this e=ample the ?T3 5ailures
are most 'ominatin0, 4hich in'icates H3D.A return channel allocation 5ailure 'ue to ?T3 HC
resource shorta0e. There is also si0ni5icant level on R2/ an' +u8 5ailures. H3D.A access 5ailure
rate .+s are currently 'e5ine' as K o5 all 5ailures not all selections.
#igure %9. &'amp!e 4SDP0 accessii!ity fai!ure causes.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e #1 6827
H3D.A setup can 5ail 'ue the num8er o5 simultaneous users reache'. There are t4o main
solutions availa8leU increase the capa8ility o5 the net4or* or 'ecrease' the num8er o5 U&s in
D/H. The net4or* capa8ility can 8e increase' 8y 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 8e consi'erin0 i5 tra55ic 8alancin0 8et4een nei0h8ourin0 sites is possi8le.
Typically cell have amount o5 H3D.A user 4hich 'oes not have any 'ata in the 8u55ers 8ut are
still counte'. This can 8e, 5or e=ample, 'ue the very lon0 inactivity timer. Ao4 utilisation an'
inactivity timer parameter 5or H3D.A an' UA D/H return channel can 8e tune' to increase
H3D.A accessi8ility in case ma=imum amount o5 H3D.A user is reach. Ta8le 12 presents
e=ample parameter sets tar0ete' to 'ecrease H3D.A utilisation. The tra55ic volume relate'
parameters can 8e use' to 'elay the transition 5rom /&AAGFA/H to /&AAGD/H. The ;ADE'
5lo4 throu0hput an' utilisation parameters can 8e use' to release the H3D.A 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 H3D.A accessi8ility 6R2/G$"a7 an' Fi0ure 22 the
correspon'in0 5ailure analysis. The results sho4 that the main accessi8ility 5ailure cause is too
many H3D.A users. This 4as 5irst optimise' 8y 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. The
secon' optimisation action 4as to chan0e the lo4 tra55ic volume threshol' in or'er to
'ecrease/postpone the transitions to /&AAGD/H. This chan0e sho4s a clear improvement in
accessi8ility an' 5ailure rates. The accessi8ility 4as increase' 5urther 8y activatin0 the >8
users/cell in the R2/, thus ena8lin0 hi0her num8er o5 users in cell level. This remove' most o5
the 5ailures 'ue to num8er o5 H3D.A users.
#igure %$. 4SDP0 accessii!ity with optimisation.
#igure %%. 4SDP0 acessii!ity fai!ure ana!ysis with optimisation steps.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e ## 6827
.1.1 H3D.A UA Return /hannel
H3D.A UA return channel reQections 'ue A/ can 8e monitore' 4ith R2/G$$2a E H3D.A access
Failure Rate 'ue the UA D/H. +n RA3"$, UA A/ coul' 8e 8ase' on 8oth throu0hput an' po4er
8ase' .3 call al0orithm 'epen'in0 on the parameter settin0s. !r"&oad%ar$in%a"DC6
parameter 'e5ines inter5erence mar0in 5or the ma=imum UA D/H loa'. Usin0 'e5ault value o5
2'? 6#%K loa'7 can cause H3D.A UA return channel reQections 'ue A/ to increase. +t is
recommen'e' to remove impact o5 this parameter 8y settin0 it to value " '? 6throu0hput 8ase'
A/ al0orithm not in use7, see Fi0ure 2#. This parameter is vali' 5or all R!! .3 8earers, not only
5or H3D.A UA return channel.
#igure %/. &ffect of Pr'"oad3argin3a'DC4 on 4SDP0 return channe! accessii!ity.
H3D.A ?T3 /& resource reservation is al4ays 5i=e', an' cannot 8e use' 5or other purpose 8ut
H3D.A only. This H3D.A ?ase8an' 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. H3D.A 1$
users vs. >8 users7.
Ho4ever, resources are not reserve' 5or H3D.A UA return channel. There have to 8e enou0h
5ree UA /& capacity availa8le to setup H3D.A UA return channel or H3D.A setup 4ill 5ail. +n
RA3"$, the UA D/H 'ata rate o5 1$ *8ps 5or H3D.A return channel is supporte' in a''ition to
currently supporte' $>, 128 an' #8> *8ps 8itrates. 1$ *8ps 5or H3D.A return channel 5eature,
to0ether 4ith .?3 or T?:, can 8e use' to optimise resources 5or H3D.A UA D/H.
&=istin0 RA3" an' RA31 5eatures support the 'ynamic use o5 lo4er D/H 'ata rates 5or
H3D.A UA D/H return channel. The 5ollo4in0 e=istin0 5unctionalities are applie' to the H3D.A
UA return channel 6UA D/H7(
.riority 8ase' sche'ulin0 an' :verloa' control H .?3 can release or 'o4n0ra'e e=istin0
2RT 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=istin0
D/Hs 5rom hi0her 'ata rates to 1$ *8ps one 8y one until the ma=imum num8er o5 users
in the ?T3 is achieve'. /on0estion o5 5ollo4in0 resources can tri00er enhance' priority
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e #> 6827
8ase' sche'ulin0 5unction( DA po4er, UA inter5erence, 'o4nlin* sprea'in0 co'e, ?T3
HC 6/&7 an' +u8 transmission
Throu0hput 8ase' :ptimiMation E T?: o5 .3 Al0orithms 5eature 'o4n0ra'es the D/H 8it
rate 'o4n to 1$ *8ps i5 the hi0h 8it rate D/H is use' ine55iciently 4hich help savin0
resources 6mainly ?T3 /&, transmission an' 'o4nlin* sprea'in0 co'e resources7
Up0ra'e o5 2RT D/H Data Rate 62ormal or Fle=i8le up0ra'e7
RTEoverE2RT
RT over 2RT an' preEemption actions 5or any reason shall not 8e tar0ete' to ;acE' 5lo4.
Ho4ever, RT over 2RT actions can 8e tar0ete' to UA return channel D/H, causin0 also the
release o5 ;A/E' 5lo4.
;ore 'etail 'escription o5 .3? an' T?: can 8e 5oun' 5rom I%J
As can 8e seen 5rom Fi0ure 2> 8elo4, there is clear correlation 8et4een UA /& usa0e an' H3E
D3/H setup 5ailures. Chen ;a=imum use' /& 'rop 8elo4 12> 65rom ma=. 1287, the H3E
3&TU.GFA+AG?T3GH3GD3/HG?<R 'rops si0ni5icantly
#igure %1. Re!ation etween ." C& usage and 4S+DSC4 setup fai!ures
Activation o5 T?: an' H3D.A 1$ *8ps Return channel improves H3D.A accessi8ility 68lue line7
as can 8e seen 5rom Fi0ure 2 8elo4. This is 8ecause o5 improve' UA /& resource usa0e.
#igure %,. 0ctivation of T2O and $- kps return channe!.
1$ *8ps Return channel D/H 'ata rate support 5or H3D.A is RA3"$ optional 5eature, 4hich can
8e activate' 8y the operator 4ith mana0ement parameter 6SD!A278#!SReturnChannel9
;inimum allo4e' 8it rate 5or H3D.A UA return channel is set 4ith parameter
6SD!AminAllowed#itrateU&. Aimitation shoul' 8e 'isa8le' 4ith the parameter
#itRateSet!S*R+9
Chen 1$ *8ps is activate', the throu0hput 8ase' optimisation an' 5le=i8le up0ra'e 5eatures can
8e activate' 5or H3D.A return channel 4ith parameter DynUsa$e6SD!AReturnChannel 6This
re9uire that T?: or/an' FU 5eatures are also activate' in the net4or*79 +able 2: 8elo4 present
recommen'e' parameter settin0s 4hen 1$ *8ps 5eature is use'.
Ta!e $/. Recommended parameters for 4SDP0 ." DC4 optimisation
.arameter 2ame 3cope Ran0e
De5ault
6RA3"$7
Recommen'e'
Value
H3D.A1$,?.3Return/hannel R2/
" 6'isa8le'7
1 6&na8le'7
Disa8le' &na8le'
H3D.AminAllo4e'?itrateUA R2/
1$*8ps 617, $> ,8ps
6#7, 128 *8ps 6>7,
#8>*8ps 6$7
$> 1$
H3D.Ainitial?itrateUA R2/
1$*8ps 617, $> ,8ps
6#7, 128 *8ps 6>7,
#8>*8ps 6$7
$> 1$
?itRate3et.32RT R2/
" 6pre'e5ine' 8it
set not in use7U 1
6pre'e5ine' 8it set in
use7
" "
DynUsa0eH3D.AReturn/hannel :55 6"7, :n 617 2o Tes
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e #$ 6827

.1.2 H3U.A Accessi8ility
H3U.A cannot 8e esta8lishe' 4ithout H3D.A, the UA return channel is H3U.A instea' o5 R!!.
The 'ecision 8et4een D/H an' &ED/H allocation 5or a U& is 8ase' on the service 6RA?
parameters7, resource availa8ility, multiERA? com8ination an' U& capa8ility. .arameter
EDC6(,SClasses 'e5ines 4hether certain tra55ic class an' tra55ic han'lin0 priority is allo4e' to
use 5or H3U.A. H3U.A allocation is not possi8le i5 there is on0oin0 +FH: or +3H:
measurements, the 5inal &D/H active set siMe is not accepta8le, H3D.A mo8ility is 'isa8le' or
H3ED3/H allocation is not possi8le. +5 the allocation o5 H3ED3/H in 'o4nlin* is not possi8le,
the .3 tries to allocate the D/H in 8oth UA an' DA.
Hi0h level H3U.A ,.+ E R2/G!1#a can 8e use' to monitor H3U.A accessi8ility 5rom user point
o5 vie4. Ao4 per5ormin0 cells can 8e then ran*e' to more 'etail analysis
&(uation % @ RNC;<$/a 4S.P0 0ccessii!ity from .ser point of view
H3U.A access is 'one in t4o phases, 5irst H3U.A channel type has to 8e selecte' in channel
type selection proce'ure, i5 this proce'ure 4ill not allo4 H3U.A channel type the H3U.A
selection 5ailure counters are tri00ere'. A5ter H3U.A channel type is selecte' the actual H3U.A
ra'io 8earer setup 4ill ta*e place an' is this 5ails the H3U.A setup 5ailures are tri00ere'.
H3U.A selection an' setup 5ailures reasons are similar to H3D.A. H3U.A selection can also
5ail i5 Active set siMe is not accepta8le. Also, i5 H3D.A ;acE' 5lo4 setup is 5ailin0, 5or e=ample,
'ue the too many simultaneous users, the H3U.A setup 4ill also 5ail.
Ta!e $1. Reports and P)s re!ated 4S.P0 accessii!ity
R2/G!2#a &ED/H selections R
R2/G!1#a H3U.A Resource Accessi8ility 5or 2RT Tra55ic K
R2/G!28a H3U.A attempts R
R2/G!1a H3U.A 3etup 3uccess Ratio 5rom user perspective K
Report: Service.Session Retainability Analysis RSRA*-/0 1%2-334 %2--35
R2/G11"#a &ED/H Allocation FR 'ue to 2A A3 K
R2/G!$8a UA D/H 3electe' 'ue to too many H3U.A users K
R2/G!$!a DA D/H 3electe' 'ue to the H3D.A po4er K
R2/G!%a &ED/H 2ot 3electe' 'ue the ?T3 HC K
R2/G!$a &ED/H 3etup FR 'ue to ?T3 K
R2/G11"a &ED/H 3etup FR 'ue to Transport K
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e #% 6827
% 100
T E,C(_-E_IN ET-P_.AI/_ S 0 GR _E,C(_-E_B SET-P_.AI/ 0 S_INT _E,C(_TRAN SET-P_.AI/
S_BGR _E,C(_TRAN SET-P_.AI/ 0 R_INT _E,C(_OT(E SET-P_.AI/ 0
R_BGR _E,C(_OT(E SET-P_.AI/ INT _E,C(_BTS_ SET-P_.AI/ 0 BGR _E,C(_BTS_ SET-P_.AI/ 0
GR /_BTS_(1_B -/_,C(_SE 0 T _BTS_(1_IN -/_,C(_SE/ A_-SR_INT /_MA2_(S-P -/_,C(_SE 0
A_-SR_BGR /_MA2_(S-P -/_,C(_SE _INT CANC_NA_AS E,C(_A//O_ 0
_BGR CANC_NA_AS E,C(_A//O_ 0 R SS_E,C(_BG A//O_S-CCE 0 T SS_E,C(_IN A//O_S-CCE
R SS_E,C(_BG A//O_S-CCE 0 T SS_E,C(_IN A//O_S-CCE

S-PA_ RNC_31+a_(
+
+
+ +
+
=
ty Accessibli
R2/G11"$a &ED/H 3etup FR 'ue to U& K
R2/G11">a &ED/H 3etup FR 'ue to :ther Failures K
#igure %-. 4S.P0 0ccessii!ity fai!ure ana!ysis
Fi0ure 2% presents e=ample o5 H3U.A selection 5ailures. This e=ample is 5rom the same
net4or* an' time perio' as H3D.A access 5ailure e=ample in Fi0ure 2". ?oth H3D.A an'
H3U.A access is limite' mainly 8y ?T3 HC.
Ao4 H3U.A
accessi8ility
/hec* 2um8er o5 simultaneous H3U.A users
62"/cell, 2>/2o'e? 7
/hec* ?H /hannel element resource usa0e
UA/DA
6?T3 in state that no capacity availa8le 5or
&D/H7
H3U.A is not supporte' in 3H: 8ranch
/hec* ?H /hannel element resource usa0e
UA/DA
/hec* R? recon5i0uration 5ailure rate
6Terminal pro8lem7
/hec* AAA2 connections 6not enou0h /+D7 or
3i0nallin0 pro8lems
2o Action
2ee'e'
Too many H3U.A
users reache'
UA D/H selecte'
'ue ?T3 HC
H3U.A 5ail 'ue
2ot Accepta8le
Active 3et
H3U.A 3etup Fail
?T3
H3U.A 3etup Fail
U&
H3U.A 3etup Fail
TRA23
2o
Tes
Tes
Tes
Tes
Tes
Tes
Tes
2o
2o
2o
2o
2o
2o
<o 5or trou8leshootin0
6 &.0. R2/ internal 5ailures7
H3U.A 3etup Fail
:ther
Tes
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 4S.P0 se!ection fai!ure causes from !ive network.
Fi0ure 28 sho4s an e=ample o5 H3U.A setup 5ailure causes. ;ost 5ailures are 'ue to :ther
reason, 8ut there is also some level o5 transport an' ?T3 5ailures.
#igure %7. &'amp!e of 4S.P0 setup fai!ure causes from !ive network.
D/H is selecte' instea' o5 &D/H i5 ;a=imum amount o5 H3U.A allocations is reache' either in
cell or in ?T3 A/<. ;a=imum amount o5 H3U.A users are limite' either 4ith parameter or
license. A8solute ma=imum value is 'e5ine' 4ith license NH3U.A, ?asic #/12/2> an' parameters
%a"*umberofEDC6Cell an' %a"*umberEDC6&C) 'e5ine ma=imum num8er o5 &ED/H
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e #! 6827
allocations in the cell an' ?T3 A/< respectively. Aimitations are also vali' 5or 3o5t an' so5ter
6cell only7 H: 8ranch a''itions. /ell speci5ic .3 use a value 4hich lo4er than these t4o values
6parameter or license7. .arameter *umberEDC6ReservedS6,#ranchAdditions 1default;35
'e5ines the num8er o5 &ED/H allocations that are reserve' only 5or so5t an' so5ter han'over
8ranch a''itions in the cell an' 5or so5t han'over 8ranch a''itions in the ?T3 A/<. The Value o5
this parameter is su8tracte' 5rom 8oth, the ma=imum num8er o5 &ED/H allocations in the cell
an' the ma=imum num8er o5 &ED/H allocations in ?T3 A/< to achieve correspon'in0ly the
ma=imum num8er o5 ne4 &ED/H allocations in the cell an' ?T3 A/<. The values o5 these
parameters are chec*e' only in &ED/H allocation an' &ED/H 8ranch a''ition phases.
The H3U.A 8ase8an' processin0 re9uirements are symmetric across the UA an' DA 'irections.
The minimum static allocation o5 8 /& 65or 8oth UA an' DA7 is reserve' as soon as H3U.A is
ena8le' at a C?T3. Cith the e=ception o5 the 5irst 8 /&Os, the /& allocation 5or H3U.A is
'ynamic an' 'epen'in0 upon 8oth the num8er o5 H3U.A connections an' loa' 0enerate' 8y
the D/H tra55ic. +n the /& allocation, DH/ has a hi0her priority than H3U.A, D/H capacity
re9uest are a8le to preEempt the set o5 /& allocate' to H3U.A 64ith the e=ception o5 the
minimum static allocation o5 8 /&7. +n a''ition to re9uire' 8 channel elements each active &E
D/H user re9uires channel element capacity. ?T3 in5orms R2/ that &ED/H users can 8e ta*en
in 4hen at least #2 channel elements 6'ynamic reservation7 are reserve' 5or &ED/Hs. +5 there is
not enou0h /& 5or H3U.A, the H3U.A setup 4ill 5ail.
There seems to 8e also correlation 8et4een &D/H setup 5ailures an' ;a=imum /& usa0es. As
H3U.A /& resource reservation is symmetric, 8oth UA an' DA shoul' 8e monitore'.
#igure %<. Re!ation etween C& usage and 4S.P0 setup and se!ection fai!ures
.2 H3.A Throu0hput an' RTT
Throu0hput cannot 8e 0uarantee' 5or .3 2RT +nteractive or ?ac*0roun' class services
inclu'in0 H3.A. ;ost o5 the resources, li*e Air +nter5ace an' +u8, are share' 8et4een the users
causin0 per5ormance 'e0ra'in0 4hen amount o5 users in the cell increase. Chen monitorin0
H3D.A throu0hput 4ith the counters, it is important to monitor num8er o5 simultaneous H3.A
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >" 6827
users as 4ell. Throu0hput measurements to0ether 4ith other counters can 8e use' i'enti5y
possi8le causes 5or lo4 throu0hput. Follo4in0 has impact to user an' cell throu0hputs(
Ra'io /hannel /on'itions
Activate' 5eatures
3horta0e on +u8 User plane or D/H tra55ic too hi0h
+ncorrect +u8 .arameter settin0s
H3D.A po4er parameter settin0s
H3D.A parameters
.ro8lems in core net4or* or application server.
.ro8lem 4ith 'rive test tools 6@o3 pro5ile, T/. +. settin0s etc.7
.2.1 H3D.A Throu0hput .+s
H3D.A selections 6R2/G$1>a7 to0ether 4ith H3D.A 'ata volume 6R2/G$"887 can 8e use' to
monitorin0 possi8le capacity 8ottlenec*s.

+ +
+ + + +
+ + + +
+ + + +
+ + +
=
BGR DSCH HS IUB FAIL SETUP INT DSCH HS IUB FAIL SETUP
BGR DSCH HS BTS FAIL SETUP INT DSCH HS BTS FAIL SETUP BGR DSCH HS UE FAIL SETUP
INT DSCH HS UE FAIL SETUP BGR DSCH HS RNC FAIL SETUP INT DSCH HS RNC FAIL SETUP
BGR RET DSCH HS REJ INT RET DSCH HS REJ BGR USERS 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
2ormally, as can 8e seen 5rom picture 8elo4, the H3D.A selections an' 'ata volume increase
4ith same linearity +.e. similar 4ay. +5 this is not the case, e.0. H3D.A selections increase 8ut
'ata volume remains constant, it in'icates that possi8le capacity 8ottlenec* e=ist some4here.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >1 6827
#igure /9. Throughput per a!!ocated 4S+DSC4 A7B
Ta8le 1 lists the relevant reports an' .+s 5or H3D.A R? throu0hput monitorin0 an'
trou8leshootin0.
Ta!e $,. 4SDP0 traffic and throughput CP)s and counters
R2/G!#"a .ac*et 3ession Attempts R
R2/G$1>a H3ED3/H selections R
R2/G!2$a H3D.A attempts R
R2/G$"88 H3D.A receive' 'ata ;8it
R2/G%228
Active H3ED3/H ;A/E' throu0hput, net4or*
perspective ,8ps
Report: Cell Data <olume and +hrou$hput at R*C RSRA*-// 1%2-3:5
;1"2#/8 H3GD3/HGDATAGV:A ?yte
R2/G!>1a H3D.A ;A/E' avera0e throu0hput at R2/ ,8ps
;1"2#/! 2RTGD/HGH3D.AGUAGDATAGV:A ?yte
R2/G11%a H3D.A UA Return /hannel Throu0hput 6D/H7 ,8ps
Report: Allocated +raffic Amounts 1R00 = 6S!A5 RSRA*-/- 1%2--34 %>---5
R2/G$8#a H3D.A ;A/E' 5lo4 allocations R
R2/G$8>8 H3D.A ;A/E' 5lo4 allocation 'uration ;in
R2/G%2186c7 Avera0e ;A/E' 5lo4 throu0hput *8ps 6;8ps7
R2/G%2286c7
Active H3ED3/H ;A/E' throu0hput, net4or*
perspective *8ps6;8ps7
R2/G$"$c6'7 H3D.A ;A/E' avera0e net throu0hput at ?T3 ,8ps6;8ps7
R2/G!>1a H3D.A ;A/E' avera0e throu0hput at R2/ ,8ps
R2/G$"88 H3D.A receive' 'ata ;8it
R2/G$8$c H3ED3/H return channel allocations, total ,8ps
R2/G1"2%a H3ED3/H return channel allocations, 1$*8it/s ,8ps
R2/G$8%8 H3ED3/H return channel allocations, $>*8it/s ,8ps
R2/G$888 H3ED3/H return channel allocations, 128*8it/s ,8ps
R2/G$8!8 H3ED3/H return channel allocations, #8>*8it/s ,8ps
Report: *umber of 6S!A Users and UE capability RSRA*->2 1%2---4 %2--25
R2/G$>8 Avera0e num8er o5 simultaneous H3D.A users R
R2/G%2$8
Avera0e num8er o5 simultaneous H3D.A users, 'urin0
H3D.A usa0e R
Report: 6S!A !ower Distribution RSRA*-/? 1%>---5
R2/G$2$8 Active H3D.A time share K
Iub based measurements 1%>304 %>:-5
R2/G!"8
AT; inter5ace 8ase' avera0e throu0hput 5or out0oin0
tra55ic 6R2/ si'e7 ;8ps
R2/G%#2a H3D.A AT; V// tra55ic loa' +u8 'o4nlin* /ps
R2/G!8$a .3 Data in DA ;8ps
R2/G%#a Avera0e AT; V// e0ress throu0hput /ps
Iu@!S +hrou$hputs RSRA*-7?
R2/G!#>a +uE.3 incomin0 interactive user 'ata throu0hput in R2/ ,8ps
R2/G!#a +uE.3 incomin0 8ac*0roun' user 'ata throu0hput in
R2/
,8ps
R2/G!12a +uE.3 <T. input tra55ic rate in R2/ ,8ps
Radio Connection !erformance %easurement %2-2/ based
R2/G$1#8 Avera0e 2RT H3ED3/H DA Throu0hput ;8ps
Fi0ure #1 sho4s an e=ample o5 H3D.A throu0hput measurement 5rom multiple throu0hput .+s
6R2/G%22c, R2/G$"$', R2/G!1>a an' R2/G$1#877 an' 'rive test lo0. Throu0hput measure'
5rom 'rive test lo0 is application level throu0hput. +t mainly sho4s that the active throu0hput .+
R2/G%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 8e achieve' 5rom
'i55erent measurements 6/ell throu0hput ;1"2#, ?T3 ;""" an' R/.; ;1"1%7. This 0ives the
5ree'om to choose the .+ 8ase' on the availa8le measurements.
#igure /$. 4SDP0 throughput measurement from 2TS and drive test !og.
.2.2 H3U.A Throu0hput .+s
The H3U.A per5ormance evolution can 8e estimate' 4ith same metho' as H3D.A, 8y
comparin0 the H3U.A selection 6R2/G!2#a7 an' H3U.A 'ata volume 6R2/G!#1a7.
Ta8le 1$ lists the relevant reports an' .+s 5or H3U.A R? throu0hput monitorin0 an'
trou8leshootin0.
Ta!e $-. 4S.P0 traffic and throughput CP)s and counters
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e ># 6827
Report: System !ro$ram R*SRA*--- 1%2--34 %2-334
R2/G!28a H3U.A attempts R
R2/G!#1a 687 H3U.A ;A/Ees 'ata volume at R2/ ;8it
Report: Cell Data <olume and +hrou$hput at R*C RSRA*-// 1%2-3:5
;1"2#/1" 2RTG&D/HGUAGDATAGV:A 8yte
R2/G!2a 687 H3U.A ;A/Ees avera0e throu0hput at R2/ *8ps
Report: Allocated +raffic Amounts 1R00 = 6S!A5 RSRA*-/- 1%2--34 %>---5
R2/G111%a &ED/H allocations R
R2/G1118a &ED/H allocation 'uration ;in
R2/G!2a 687 H3U.A ;A/Ees avera0e throu0hput at R2/ ,8ps
R2/G!#1a 687 H3U.A ;A/Ees 'ata volume at R2/ ;8it
;"""/11 H3U.AG;+2G;A/DGTHR *8it/s
;"""/12 H3U.AG;AVG;A/DGTHR *8it/s
;"""/1# H3U.AGAV&G;A/DGTHR *8it/s
Report: *umber of 6S!A Users and UE capability RSRA*->2 1%2---4 %2--25
R2/G1"#$a Avera0e num8er o5 simultaneous H3U.A users R
R2/G1"#%a
Avera0e num8er o5 simultaneous H3U.A users, 'urin0
H3U.A usa0e R
R2/G!$8a UA D/H 3electe' 'ue to too many H3U.A users K
A+% <CC +raffic &oad RSRA*-A: 1%>:-5
R2/G!1a,8 +u8 UA Avera0e Throu0hput 6R2/ si'e7
R2/G%2a Avera0e AT; V// in0ress throu0hput /ps
Iu@!S +hrou$hputs RSRA*-7?
R2/G!#!a +uE.3 out0oin0 interactive user 'ata throu0hput in R2/ *8ps
R2/G!>"a +uE.3 out0oin0 8ac*0rou' user 'ata throu0hput in R2/ *8ps
R2/G!#$a +uE.3 out0oin0 user 'ata throu0hput in R2/ *8ps
Fi0ure #2 sho4s an e=ample o5 H3U.A throu0hput measurement 5rom multiple throu0hput .+s
6;"""/12, ;"""/1#, R2/G!287 an' 'rive test lo0. ;""";12 sho4 ma=imum H3U.A
;acE' throu0hput. The .+s that measure the avera0e throu0hput 5rom 'i55erent measurements
6/ell throu0hput ;1"2# an' ?T3 ;"""7 sho4 e9ual values. This 0ives the 5ree'om to choose
the .+ 8ase' on the availa8le measurements.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >> 6827
#igure /%. 4S.P0 throughput P)S and drive test too! measurement.
#igure //. 4S.P0 se!ections and throughput.
.2.# H3D.A optimise' throu0hput
Test o5 ma=imum H3D.A throu0hput an' un'erstan'in0 o5 the re9uire' con5i0uration is a
startin0 point 5or H3D.A 5eature per5ormance tests an' per5ormance optimisation, althou0h it
can 8e achieve' only in nominal con'itions commonly not availa8le 5or users. The ma=imum
throu0hput in RA3"$ net4or*s is !.$ ;8ps 5or sin0le users 6/atE! U&7 an' 11.8 ;8ps per cell,
see Ta8le 1% 8elo4 61> ;8ps/user is a RU1" 5eature7. /urrently most common 'ata car's are
cate0ory 8 supportin0 1" co'es an' 0ettin0 ma=imum $.%2 ;8ps throu0hput in RA3"$.
Ta!e $6. 3a'. user it rates with different R0S features.
The ma=imum achieva8le throu0hput has to 8e supporte' 8y the 4hole en'EtoEen' connection,
all inter5aces an' protocol layers. This topic is han'le' in multiple re5erences li*e WRA2 &2&
system per5ormance optimiMation 0ui'eX I11J, WH3.A Ra'io 2et4or* .lannin0 <ui'eX I1J an'
section W/hec*in0 H3D.A 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 8it rate optimisation(
;a=imum H3D.A throu0hput can 8e achieve' only 4ith 0oo' ra'io con'itions. Hi0h H3D.A
8itrates re9uire 0oo' ortho0onality an' hi0h /@+. Fi0ure #> sho4 theoretical H3D.A RA/ level
throu0hput 6application throu0hput is typically 1"K lo4er7 5or H3D.A , 1" an' 1 co'es 4ith
'i55erent /@+ values. Cith H3D.A 1 co'es, /@+ L2% is re9uire' to achieve ma=imum
throu0hput. /@+ value here is compensate' /@+ 6a5ter lin* a'aptation7 not value reporte' 8y
U&. Fiel' measurement tools as 4ell as counter statistic sho4 reporte' /@+, not compensate'
/@+. /ompensate' /@+ has 8een seen to 8e 2E# '? 8etter than reporte' /@+ in RA3"$. Also
there are some 'i55erencies 8et4een terminals relate' to reporte' /@+.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >$ 6827
#igure /1. 4SDP0 RC" throughput =app!ication !eve! throughput is typica!!y $9D !ower> vs.
Compensated C?)
Fi0ure # sho4 DA application level throu0hput 5or /at ! 61 co'e7 an' /at 8 61" co'e7 H3D.A
U&s. ;easurements are 'one un'er RA3"$ 6R2#." @# #.11E"7 4ith 8 C 6#! '?m7 ;etrosite.
/.+/H po4er 4as set to 2$ '?m an' .t=;a=H3D.A to #!'?m. H3U.A 4as 'isa8le' 'urin0
test an' other parameters 4ere set so, that it 4as possi8le to allocate 1 co'es 4as H3D.A.
Test 4as 'one 8y 'o4nloa'in0 1""; 5ile 6FT.7 an' there 4as no other tra55ic in the cell 'urin0
measurements. Cith /ate0ory ! H3D.A U& the ma=imum achieve' application level throu0hput
4as !.18 ;8ps per user an' to0ether 4ith /at! an' /at8, the total cell application level
throu0hput 4as 1".8 ;8ps.
#igure /,. 4SDP0 app!ication !eve! throughput with different 4SDP0 category .&s
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >% 6827
E $ 3it
with C?) $%
'?
/@+
Fi0ure #$ sho4 /@+ 'istri8ution 5rom counters 'urin0 testin0 5or 8oth /at8 an' /at ! U&s
6measurements 'one in 'i55erent hour7. U&s 4ere connecte' 5or 'i55erent laptop 4ith 1E2 meter
'istance 8et4een. ?ase' on results 8elo4, it seems that /ate0ory ! H3D.A U& is reportin0
hi0her /@+ values than /ate0ory 8 U&s. This is no4 reporte' /@+, not compensate' /@+.
#igure /-. C?) distriution during testing for different .&s
Fi0ure #% sho4 throu0hput an' num8er o5 allocate' co'es 4hen there is 2 simultaneous /at 8
H3D.A U&s. As H3D.A 1 co'e an' co'e multiple=in0 is activate', H3D.A U&s are sche'ule'
4ith same TT+ 68 B % co'es7. Cith 2 /at 8 H3D.A U&, the avera0e application throu0hput is
>.$E." ;8ps per User.
#igure /6. 4SDP0 throughput and code a!!ocation when % simu!taneous category 7 4SDP0 .&
?esi'es o5 ra'io con'itions an' use' R2. parameters, 5ollo4in0 U& types an' 2et4or* settin0s
4ere use' 'urin0 testin0 to 0et H3D.A throu0hput values presente' in Fi0ure #.
U& cate0ory an' type( .er5ormance 8et4een the U& types can vary, 5ollo4in0 H3D.A U&s use'
'urin0 testin0.
E 2ovatel :vation ;/!!"D U3?( /at 8 H3D.A H ;a= throu0hput %.2;8ps, /at H3U.A
E 2orm( H3D.A /at! H ;a= throu0hput 1" ;8ps, H3U.A cat E ;a= Throu0hput 2 ;8ps
/ate0ory 8 H3D.A U&s 4ere 8oth connecte' to same 2emo.
/lient 3ettin0s( /lean, hi0hEspec laptop use' instea' o5 232 8uil' laptop. Cith T/. receive
4in'o4 siMe YL2$*? 6unnecessarily hi0h values shoul' 8e avoi'e'7. 2ever set T/. values
manually 8y mo'i5yin0 re0isters 6same parameter can 8e in the several places7, use rea'y ma'e
tools li*e T/. optimiser to chan0e values. /on5orm e.0. 8y usin0 Cireshar* 6&thereal7 that
chan0e is 'one.
3erver 3ettin0s( Fe'ora Ainu= server use', Cith T/. receive 4in'o4 siMe is YL 2$ *?. +n
server si'e, 1 <8ps inter5ace is use' to connect server to /ore net4or*.
+u8 /apacity( Hi0h enou0h +u8 capacity ensures that throu0hput is not limite' 8y +u8. +u8
/apacity can 8e chec*e' 5rom the /:/:. Use' user plane siMe o5 >"""" cps e9uals to
1$.!$;8ps. Dynamic sche'ulin0 5or H3D.A 4as ena8le' 4ith 'e5ault parameter settin0s
Ta8le 18 sho4 +u8 'eman' 5or H3D.A hi0h 8itrates.
Ta!e $7 )u demand for 4SDP0 high itrates =0T3 siFe $<-7, e(ua!s to ,' &$ and %7$91 to 6'&$>
/ore 2et4or*s( Fle=i +32 <<32 6Fle=i #.2 D /D#7 use' as ol' <<32 HC is not vali' 5or
ma=imum throu0hput. /om8i 3<32 6)$ %.2E" 63<$./D%277
.2.> H3U.A optimise' throu0hput
H3U.A throu0hput 'epen's on parameter settin0s, activate' 5eatures, U& capa8ility, ?T3 HC
capacity an' +u8 /apacity. Also air inter5ace start to limit H3U.A throu0hput 4hen several
H3U.A users un'er same cell.
.arameter %a"+otalUplin'SymbolRate 'e5ines ma=imum total UA sym8ol rate o5 the &E
D.D/H6s7 o5 the U& in the cell an' shoul' 8e set to #8>" *8ps 62 = 3F27 i5 H3U.A 2." is
activate'. The lo4est parameter value amon0 the values o5 the parameter o5 the cells that
8elon0s to the &ED/H active set is use' 4hen the &ED/H is allocate'. 3upportin0 H3U.A 2."
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e >! 6827
;8ps means that R2/ is allo4e' to set up the 8it rate 5or the U& 4hen re9ueste' 8y core
net4or* 6in RA? @o37 an' 4hen nee'e' con'itions are met. The nee'e' con'itions are, 5or
instance, suita8le U& cate0ory an' that the 8it rate is supporte' also in the nei0h8ourin0 cells
6no 3H: nee'e'FF7. Chen some con'ition is not 5ul5ille' 'urin0 a call, R2/ may 'o4n0ra'e a
U& 8it rate.
Ta8le 1!. H3U.A 8itrates 4ith 'i55erent ;a=TotalUplin*3ym8olRate settin0s
%a"+otalUplin'SymbolRate T?3
RA/
Throu0hput
3F> !$" %11" ".$%2
23F> 1!2" 1>>8> 8its 1.#8 ;8ps
23F2 #8>" 1!!" 8its 1.8! ;8ps

.arameter FactorEDC6%a"#itRate 'etermines the 5actor 5or calculatin0 the &ED/H ma=imum
8it rate 5rom the ma=imum UA user 8it rate o5 the RA?.
+5 special value o5 " is use', then UA 8it rate is not restricte' 8ase on the uplin*
ma=imum 8it rate o5 the RA?.
+5 value Y " is use', FactorEDC6%a"#itRate multiplie' 8y UA @o3 shoul' 8e superior to
tar0et UA throu0hput
&. 0. 3houl' 8e set to i5 H3U.A2." is activate' an' su8scri8er HAR @o3 pro5ile is set
to #8>*8ps
.arameter +hreshold%a"ED!DC6SR can 8e use' to restrict the ma=imum total Uplin* sym8ol
rate o5 &ED.D/H 8ase' on ma=imum uplin* user 8it rate o5 the RA? 6see I1J7.
The test results is sho4n in Fi0ure " 6en' o5 this chapter7 UA throu0hput values 4ith 'i55erent
settin0 o5 a8ove parameters.
H3U.A 2." ;8ps is license' 5eature, an' 8y achievin0 ma=imum throu0hput the parameter
;a=imum total uplin* sym8ol rate have to 8e set #8>". Fi0ure #8 8elo4 sho4 UA application
60reen line7 level throu0hput 4hen H3U.A 2." 5eature is activate'.
#igure /7. 4S.P0 throughput with 4S.P0 % 3ps feature
Uplin* ra'io resources are share' 8et4een the H3U.A an' R!! users. Fi0ure #! 8elo4 present
cell level UA application throu0hput 4ith 'i55erent num8er o5 H3U.A U&s. ;a=imum achieve'
UA cell level application throu0hput is aroun' # ;8ps 4ith 2 H3U.A U&s. A''in0 more U&s
'oes not increase UA cell level throu0hput 'ue uplin* air inter5ace limitations.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e " 6827
4S.P0 .&$ %'$993
."
.arameter !r"+ar$et%a"#+S 'e5ine ma=imum tar0et 5or receive' total 4i'e 8an' po4er in the
cell 5or ?T3 .ac*et sche'ulin0. As can 8e seen 5rom results 8elo4, chan0in0 this parameter
'oes not improve total uplin* cell throu0hput si0ni5icantly.
#igure /<. 4S.P0 Ce!! ." app!ication !eve! throughput with different numer of 4S.P0 .&s and
with different Pr'Target3a'2TS va!ues =changed in case of / 4S.P0 .&>
Cith 2 simultaneous H3U.A U&, the throu0hput is sli0htly 'ecrease' 65rom 1.$# ; in case o5 1
H3U.A U& to 1.!; 4ith 2 H3U.A U&7.
Fi0ure >" sho4 e=ample o5 one H3U.A user throu0hput 4hen there is # simultaneous H3U.A
users. A''in0 #
r'
H3U.A User the throu0hput o5 each H3U.A user start to 5luctuate an' uplin*
cell level throu0hput 'ecrease. +n case o5 # or more simultaneous H3U.A Users, the cell level
throu0hput is alrea'y limite' 8y air inter5ace as can 8e seen 5rom Fi0ure >".

#igure 19. 4S.P0 user throughput when / simu!taneous 4S.P0 .&
Fi0ure >1 sho4 uplin* application level throu0hput o5 1 H3U.A User, 4hen there is 'i55erent
num8er o5 users in the cell. +n case o5 # H3U.A U&, .r=tar0et;a=?T3 4as chan0e' 5rom $
6'e5ault7 to #".
;a= DA cell
app. throu0hput
4ith 2 H3U.A
U&
!r"+ar$e%a"#+S chan0e'
4S.P0 .&/ %'$993
."
3tart #
r'
U&
#igure 1$. ." app!ication !eve! throughput of $ 4S.P0 .& when there is different numer of .&s in
the ce!!.
Fi0ure >2 sho4 .r=Total 65rom :nline ;onitor7 value 4ith 'i55erent num8er o5 H3U.A Users.
#igure 1%. .p!ink Pr'Tota! with different numer of 4S.P0 .&s
Cith 1 H3U.A U& the uplin* loa' is aroun' #"K, 4ith 2 H3U.A U& close to $"K 8ut not yet
limite' 8y air inter5ace. A''in0 #
r'
U& the loa' increase close to %K 6.r=Tar0et;a=?T3L$7 an'
cell level throu0hput is not increase' any more.
#igure 1/. .p!ink "oad with different numer of 4S.P0 .&s
H3U.A throu0hput can 8e also limite' 8y ?T3 /hannel elements. H3U.A /& allocation is 'one
4ith speci5ic siMes o5 resource steps. The amount o5 resources nee'e' 'epen's on the
throu0hput 6.hysical layer cell level throu0hput7 an' the num8er o5 H3U.A users. +n RA3"$
H3U.A users cannot 8e move' 8et4een C3./s 6or 5le=i su8mo'ules7, so 4e 'onOt 4ant to
ta*e another C3./ to H3U.A use too 5ast, 8ecause i5 that 4oul' nee'e' to 8e ta*en 8ac* to
R!! use, the H3U.A users cannot 8e move' 8ac* to 5irst C3./. This is 0oin0 to 8e chan0e' in
RU1" an' users can 8e move' 8et4een C3./s.
+nsi'e C3./s the H3U.A resource steps are ta*en in use so that each ne4 user 0ets its o4n
resource step 6i5 5ree capacity7 until the 4hole C3./ is occupie'. To 8e a8le to allocate the ne=t
H3U.A resource step, an a''itional 5ree capacity o5 $ /& is nee'e'. The re9uire' si= /&s 5ree
on top o5 the H3U.A resource step is to avoi' a Npin0Epon0O e55ect in reservin0 an' 5reein0
H3U.A resource step.
+5 all the H3U.A users are un'er one cell 6or there is only one cell7, only 5irst C3./ car' or
Fle=i su8mo'ule is use'. Fi0ure >> 8elo4 sho4 ?T3 /& H3U.A usa0e versus H3U.A
;AV/AV& ;acE' throu0hput. There is 5e4 perio's H3U.A throu0hput is limite' 'ue the ?T3 HC
'ue the increase' R!! tra55ic 4hich can 8e seen 5rom Fi0ure >>.
#igure 11. 2TS C& 4S.P0 .sage and 4S.P0 3a'imum 3ac+d Throughput
There is o4n counters to monitor H3U.A /& resource status. These counters can 8e use' to
monitor perio's 4hen H3U.A throu0hput is limite' or H3U.A setup is not possi8le 'ue the ?T3
HC.
;1"""/2$! ?T3 H3U.A HC Aimite' Duration is up'ate' 4hen ?T3 is in H3U.A HC
limite' state. +n this state, R2/ sets up the &ED/H 8ut the ?T3 HC shorta0e may cause
throu0hput to 8e lo4er than e=pecte'.
;1"""/2%" ?T3 H3U.A 2: HC /apacity 'uration is up'ate' 4hen ?T3 reports to 8e
in state that it 'oes not have H3U.A HC capacity availa8le. +n this state, the R2/ 'oes
not set up the &ED/H
Fi0ure > present hours 4hen H3U.A throu0hput is limite' 'ue the lac* o5 ?T3 /& 6'ue the
increase R!! tra55ic 4hich, in case o5 ?T3 /&Os, has priority over H3U.A7, an' i5 4e compare
Fi0ure >> an' Fi0ure >, these are the perio' 4hen ma= use' /& sho4 very hi0h value.
#igure 1,. 2TS resource status counters
H3U.A D R!!
H3U.A
The 5eature H3U.A /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 +u8 in terms o5 transport capa8ilities an' the R2/ in
terms o5 processin0 resources. Follo4in0 ;1"22 counters can 8e use' to monitor +u8 an' R2/
con0estion control.
.+R 2ame Description
;1"22/$! +U?GD&AATG//GD&AATG+2D
+u8 'elay variation 8ase' al0orithm operates
at the typica! working range under !oad.
+u8 usa0e is close to optimal 4hen this
counter contains nonEMero 68ut not lar0e7
value. Ho4ever, lar0e value in this counter is
e=pecte' coinci'ently 4ith the Frame Aoss
/+ counter
;1"22/%2 +U?GD&AATG//GFRA;&GA:33G+2D
+u8 'elay variation 8ase' al0orithm operates
at the high )u !oad range. Ao4 value is
e=pecte' in loa' situation. Hi0h value
represents overloa' +u8 transport an' this
coul' 8e in'ication o5 under dimensioned
transport.
;1"22/%1 +U?GA:33G//GFRA;&GA:33G+2D
Frames are lost in +u8 transport. There is
pro8a8ly somethin0 4ron0 in resource
allocation or 'imensionin0 o5 +u8 i5 this
counter contains hi0h values report a5ter
report. +t coul' also 8e that there e=ist some
physical pro8lem in +u8
;1"22/%"
HCG:V&RAG//GD&AATG+2D
6R2/ HC7
User plane processin0 4G is acting
proactive!y to contro! increasing !oad.
+ncrease in this counter is typical 4hen
system is loa'e'. Ho4ever, lar0er increase
in counter value is an in'ication o5 8ecomin0
HC overloa'
;1"22/%#
HCG:V&RAG//GFRA;&GA:33G+2D
6R2/ HC7
User plane processing 4G is heavi!y
over!oaded. .ro8a8ly somethin0 4ron0 in
resource allocation or 'imensionin0 o5 R2/
i5 this counter contains hi0h values report
a5ter report
;1"22/%> 3U//G&D/HGF.G?RA2/HG3&TU.
;1"22/%% 3U//GR&/G&D/HGFRA;&3 &=act 2um8er o5 successively receive' 'ata
;1"22/%$ D&AAT&DG&D/HGFRA;&3 &=act num8er o5 all the 'elaye' 5rames
;1"22/% ;+33&DG&D/HGFRA;&3 &=act amount o5 lost 5rames
Ta!e %9. 4S.P0 congestion contro! Counters
Fi0ure >$ 8elo4 sho4 success5ully receive' &D/H 5rames an' Frame losses 'ue the R2/ HC.
/ounter HCG:verloa'G//GFrame loss is tri00ere' in case 4hen there is # or > simultaneous
H3U.A U&s in'icatin0 lac* o5 D3./D;.< processin0 capacity. 6/ounters are presente' in
'i55erent scale, ma= 5rame loss 2.$. K 7
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e 6827
#igure 1-. 4S.P0 congestion contro! and 4G over!oad CC #rame !oss counter
Chen the 2o'e ? receives a T2A con0estion in'ication /ontrol Frame it starts to 'ecrease the
H3U.A throu0hput in airE inter5ace. U& 8it rate is 'ecreases 8ecause the .ac*et 3che'uler is
sen'in0 a relative 0rant ND:C2O comman's. The &ED/H .ac*et 3che'uler 'ecreases the U&
8it rate a00ressively i5 receive' con0estion in'ication 4as NFrame AossO, compare' to NDelay
?uil'EupO.
Frame Aoss LY $" ms 8et4een consecutive re'uctions
Delay ?uil'Eup LY 1"" ms 8et4een consecutive re'uctions
:nce the con0estion is over, the /on0estion +n'ication entity sen' an &ED/H F. control 5rame
o5 type N/on0estion +n'icationO an' value N2o T2A /on0estionO to the ?T3.
Receivin0 the N2o T2A /on0estionO in'ication, the &ED/H .ac*et 3che'uler stops sen'in0
ND:C2O comman's to the U& an' recovers 0ra'ually 8ac* to normal operation.
2o'e ? 4aits $" ms 8e5ore reEallocatin0 resources in case con0estion reoccurs
2o'e ? then has 2"" ms to reEallocate resources to the U& 5rom 4hich they 4ere
remove' prior to ma*in0 them 0enerally availa8le to all U&
#igure 16. #unction of )u congestion Contro!
+n case o5 limite' +u8 capacity 6e.0. 1 = &17 the 5ull sym8ol rate allocation 62 = 3F27 can cause
throu0hput 'rops. H3U.A con0estion control 'ecrease the H3U.A 8it rate 8y 'ecreasin0 the
servin0 0rant 4ith too hi0h sprea'in0 co'e con5i0uration. .er5ormance o5 unlimite' 62 = 3F27
con5i0uration is 4orse than limite' 62 = 3F>7 con5i0uration in a site 4ith 1 = &1 +u8, 8ecause
H3U.A con0estion control 5luctuates the 8itrate 6servin0 0rant7. 3olution to this issue is to
N/on0estionO
+n'ication receive'
5rom the R2/
&ER</H
Do4n
$" ms 2"" ms
N2o /on0estionO
+n'ication receive' 5rom
the R2/
Hol'
.erio'
ReEallocate
Resources
Resources 0enerally
availa8le to any
connection
Resources only
availa8le to connection
5rom 4hich they 4ere
remove'
intro'uce cell level sym8ol rate limitation %a"+otalUplin'SymbolRate parameter. This impact
can 8e clearly seen 5rom 5i0ure 8elo4.
#igure 17. #unction of )u congestion contro! for throughput with different symo! rate
#igure 1<. 4S.P0 congestion contro! decrease the 4S.P0 it rate y decreasing the Serving grant
with too high spreading code configuration
H3U.A 8it rate can 8e limite' 8y ?T3 sche'uler 4ith t4o mechanisms 4hich utilise the RA?
ma= 8it rate 6'etail parameter 'escription presente' 8e0innin0 o5 this chapter.7
&ED/H ma=imum 8it rate limitation 4ith RA? @o3 an' FactorEDC6%a"#itRate 6'e5 1.7
6L "7( ;a= &ED/H 8it rate not sent to ?T3
6Y "7( &ED/H ;a= ?itRate L FactorEDC6%a"#itRate Z RA?( ;a= UA 8it rate, sent to
?T3 in 2?A.( RA setup/recon5i0uration messa0e 6+& ( &ED/H ;a=imum ?it Rate7
Total uplin* sym8ol rate o5 &ED.D/H6s7 can 8e limite' 4ith +hreshold%a"ED!DC6SR
RA?( ;a= UA 8it rate [ +hreshold%a"ED!DC6SR07-'bps 6'e5 12 *8ps7 :R
%a"+otalUplin'SymbolRate L !$" 3F> $%2 *8ps
3F>
2=3F> 2=3F2
3F>
2=3F> 2=3F2
RA?( ;a= UA 8it rate [ +hreshold%a"ED!DC6SR203-'bps 6'e5 1"2> *8ps7 :R
%a"+otalUplin'SymbolRate L 1!2" 2 \ 3F> 1#8" *8ps
:ther4ise 6RA?( ;a= UA 8it rate Y +hreshold%a"ED!DC6SR203-'bps A2D
%a"+otalUplin'SymbolRate L #8>"7 2 \ 3F2 1888 *8ps
;a=imum set o5 the &ED.D/Hs sent to ?T3 in 2?A.( RA setup/recon5i0uration
messa0e 6+& ( ;a=imum 3et o5 &ED.D/Hs7 A2D to U& in RR/( Ra'io 8earer
recon5i0uration messa0e 6+&( ;a=imum channelisation co'es7
Fi0ure " sho4 result 5rom H3U.A 8it rate parameter test an' impact o5 +u8 con0estion control.
Test cases an' use' parameter settin0s are liste' 8elo4. Cith 1 = &1, the +u8 con0estion control
is limitin0 throu0hput 4ith hi0h 8itrate settin0s. 6Arro4s in Fi0ure " sho4 cases 4here +u8
con0estion control is limitin0 H3U.A 8itrate7

#igure ,9. .p!ink throughput with $ ' &$ for 4SP0 and different Parameter va!ues
Test 1( &55ect o5 Factor&D/H;a=?itRate
FactorEDC6%a"#itRate ; " 6not set7, 1, 1. an'
RA? ;a= UA 8it rate #8> *8ps
Threshol';a=&D.D/H3R L " 62ot set7
Test 2( &55ect o5 ;a=TotalUplin*3ym8olRate
;a=TotalUplin*3ym8olRate L !$", 1!2", #8>"
Factor&D/H;a=?itRate L " 62ot set7
RA? ;a= UA 8it rate >1#2 *8ps
Test #( &55ect o5 RA? @o3 an' +hreshold%a"ED!DC6SR
RA? ;a= UA 8it rate $>, $>" *8ps
Threshol';a=&D.D/H3R!$"*8ps L 12 *sps an'
Threshol';a=&D.D/H3R1!2"*8ps L 1"2> *sps
Test >( &55ect o5 RA? @o3 only
RA? ;a= UA 8it rate $>, #8> *8ps
." throughput
%<6
/-6
$$$-
71/
,<%
$9$9
7-$
,71
$9/7
7/9
7-6
7,%
17
$9-
%<-
/6,
"."
2""."
>""."
$""."
8""."
1"""."
12""."
k
i
t
8
s
Factor&D/H;a=?itRate
;a=TotalUplin*
3ym8olRate
Threshol';a=&D.
D/H3R
@o3 only
@o3 4ith
Factor&D/H;a=?itRateL1.
Test ( &55ect o5 RA? @o3
RA? ;a= UA 8it rate $>, 128, 2$ *8ps
Factor&D/H;a=?itRate L 1.
H3U.A 'ata rate can 8e limite' 8y
U& T= .o4er H U& is alrea'y usin0 its ma=imum T= po4er
3ervin0 <rant H ;a=imum 0rant is use' alrea'y
Data H U& 8u55er is empty H no ne4 'ata to sen'
Fi0ure 1 8elo4 sho4 situation 4hen U& t= po4er increase an' start to limit throu0hput, there is
more A8solute <rants 0iven to the U&. ?T3 re'uce a00ressively the throu0hput an' there5ore
A< are use'.

#igure ,$. .& t' Power !imitation vs. 4S.P0 throughput
.# ;o8ility
H3.A mo8ility can 8e per5orme' 4ith cell reselection in /&AAGFA/H or servin0 cell chan0e
5unctionality. 3ervin0 cell chan0e 4ith so5t han'over is re9uire' 5or H3U.A,
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e ! 6827
R&DL A<
Tello4 L&ETF/+
?AU&L 3<
6S@DSC6 servin$ cell chan$e can 8e tri00ere' 8y the 8est server &c/2o, UA 3+R error an'
event 1?/1/. The most common tri00erin0 reason is suppose' to 8e perio'ical &c/2o
measurements. 6SD!AServCellBindow 1def 3 d#5 parameter 'etermines the ma=imum
allo4e' 'i55erence 8et4een the 8est cell /.+/H &c/2o an' the servin0 H3ED3/H cell /.+/H
&c/2o. The recommen'ation is to set DropBindow parameter value in H3D.A F;/3 hi0her
than 6SD!AServCellBindow, so that the servin0 cell chan0e 4oul' 8e normally tri00ere' 8y the
&c/2o measurements an' not 8y the event 1?.
AdditionBindow in H3D.A F;/3 is controllin0 the active set siMe o5 the associate' UA
channels. +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 H3D.A
F;/3 than in the RT/2RT F;/3, to have smaller 3H: area 5or H3D.A users.
The H3D.A servin0 cell chan0e per5ormance can 8e measure' 4ith R2/G%##a 6H3D.A
3ervin0 /ell /han0e 3uccess Rate7. The 3// can 8e tri00ere' mainly 8y /.+/H &c2o, UA 3+R
&rror or active set up'ate 6removal o5 servin0 H3E.D3/H cell 5rom A37.
Ao4 success rate can 8e cause' 8y
Failures 'ue to ?T3
Chen the R2/ receives 2?A.( RAD+: A+2, R&/:2F+<URAT+:2 FA+AUR& 'urin0
servin0 H3ED3/H cell chan0e
Failures 'ue to transmission
Chen a servin0 H3ED3/H cell chan0e 5ails 'ue to an +u8 transport setup 5ailure.
Failures 'ue to a'mission control
The num8er o5 H3ED3/H servin0 cell chan0e 5ailures 'ue to a'mission control, 5or
e=ample 8ecause the ma=imum num8er o5 H3D.A users 4ere alrea'y allocate' in
the tar0et cells.
Failures 'oe to other reasons
The num8er o5 H3ED3/H servin0 cell chan0e 5ailures 'ue to other reasons.
Ta8le 21 summarises the H3.A mo8ility relate' ,.+s an' counters.
Ta!e %$. 4SP0 moi!ity counters and CP)s
Report: System !ro$ram RSRA*--
R2/G!"$a H3D.A 3// attempts R
R2/G%##a H3D.A 3ervin0 /ell /han0e 3uccess Rate K
Report: 6S!A Servin$ Cell Chan$e RSRA*-::
R2/G!"$a H3D.A 3// attempts R
R2/G%##a H3D.A 3ervin0 /ell /han0e 3uccess Rate K
;1""8/21# 3//G3TART&DG/.+/HG&/2: +nte0er num8er
;1""8/21> 3//G3TART&DGUAG3+RG&RR:R +nte0er num8er
;1""8/21 3//G3TART&DGA/T+V&G3&TGU.D +nte0er num8er
;1""8/21$ 3//G3TART&DG:TH&RGR&A3:2 +nte0er num8er
;1""8/218 3//GFA+A&DGDU&GT:G?T3 +nte0er num8er
;1""8/21! 3//GFA+A&DGDU&GT:GTRA23; +nte0er num8er
;1""8/22" 3//GFA+A&DGDU&GT:GA/ +nte0er num8er
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e $" 6827
;1""8/221 3//GFA+A&DGDU&GT:G:TH&R +nte0er num8er
;1""8/2># +2T&RGR2/GHH:GATTGH3.AG3// +nte0er num8er
R2/G11$2a H3U.A +nterER2/ 3// 3uccess Rate K
R2/G11$#a H3U.A +nterER2/ 3// Failure Rate K
R2/G11$>a H3U.A +nterER2/ 3// Drop Rate K
?elo4 is typical e=ample o5 H3D.A mo8ility per5ormance ta*en 5rom R3RA2"## report. ;ain
reasons to start 3// is the 'ecrease' /.+/H &c2o an' active set up'ate 6event 18/1c7. There
has 8een some issues 4ith UA 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 capacity
in the tar0et cell the 5ailure can 8e seen 4ith A/, TRA23 an' ?T3 reasons.
#igure ,%. &'amp!e of SCC fai!ure reasons
There seems not to 8e a relation 4ith poor 3// success an' H3D.A retaina8ility, as seen in the
picture 8elo4. 3// success rate 5or H3D.A an' H3U.A is not very accurate in cell level as
'enominator is incremente' in the source cell 6ol' servin0 cell7 an' numerator is incremente' in
the tar0et cell 6ne4 servin0 cell7.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e $1 6827
#igure ,/. 4SDP0 SCC performance compared to 4SDP0 retainai!ity.
+nter R2/ 3// per5ormance seems to 8e a8out 2E> K lo4er than +ntra R2/ 3// 'ue to 3R2/
relocation issues.
.> Retaina8ility
The retaina8ility o5 a H3.A pac*et call 'escri8es the pro8a8ility that the pac*et call is not
'roppe' 4hen the H3.A channel type is use'. The .+ R2/G!2"a 6see Ta8le 227 'escri8es the
retaina8ility 8ase' on tra55ic ;1"22 measurements. This ta*es into account only events 4hen
the D/H connection is a8normally release'. The .+ R2/G$"!a can 8e also use' 5or retaina8ility
measurement, 8ut this .+ is tri00ere' in cell 4here the RA 5ails even i5 there is 4or*in0 RA in
other cell o5 active set an' the pac*et call is s4itche' to that, thus 'oes not necessary present
users vie4 o5 connection 9uality.
The H3.A pac*et call 5ailures are mainly 'ue to RA 5ailuresU ra'io lin* 5ailure, RA/ protocol reset
or uplin* RA/ unrecovera8le error 6/ell Up'ate sent 8y U&7. Fi0ure 2$ presents an e=ample o5
H3.A pac*et call retaina8ility analysis.
#igure ,1. 4SP0 retainai!ity fai!ure ana!ysis
Ta8le 22 lists the relevant reports an' .+s 5or H3D.A R? accessi8ility monitorin0 an'
trou8leshootin0.
Ta!e %%. 4SP0 retainai!ity counters and CP)s =ReportH Service8Session Retainai!ity 0na!ysis
RSR0N96<>
.+ re5 .+ name / A88reviation
.+
unit
Report: System !ro$ram RSRA*---
R2/G!22a .ac*et 3ession 3uccess Ratio 5or 2RT K
R2/G$1>a H3ED3/H selections R
R2/G$"!a H3D.A Resource Retaina8ility 5or 2RT Tra55ic K
R2/G!2$a H3D.A attempts R
R2/G!2"a H3D.A 3uccess Ratio 5rom user perspective 5or 2RT K
R2/G!1!a H3U.A resource Retaina8ility 5or 2RT Tra55ic K
Report: Service.Session Retainability Analysis RSRA*-/0 1%2-335
R2/G1"!2a .ac*et 3ession Rel 5rom H3E&D/H R
R2/G1"!#a .ac*et 3ession Rel 5rom H3ED/H R
R2/G1"!>a .ac*et 3ession Rel 5rom D/HED/H R
R2/G1"!a H3ED3/H/&ED/H .ac*et /all Rel 'ue to RA Failures K
R2/G1"!$a H3ED3/H/D/H .ac*et /all Rel 'ue to RA Failures K
R2/G1"!%a D/H/D/H .ac*et /all Rel 'ue to RA Failures K
R2/G1"!8a H3ED3/H/&ED/H .ac*et /all Rel 'ue to :ther Failures K
R2/G1"!!a H3ED3/H/D/H .ac*et /all Rel 'ue to :ther Failures K
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e $# 6827
R2/G!2"a]
V K
/hec* 3// Failure Rate H Ra'io, +u8, /&
resource con0estion
/hec* 5or R2/ 5ailures an' use R2/ lo00in0 i5
re9uire'
2o Action
2ee'e'
H3.A pac*et call
Ra'iolin* 5ailures
H3.A pac*et call
5ailures E other
2o
Tes
Tes
Tes
2o
/hec* /@+ 'istri8ution an' &cno 'istri8ution 5or
covera0e issue
/hec* H3D.A mo8ility parameter H A''/Drop
4in'o4, 3// parameter
R2/G11""a D/H/D/H .ac*et /all Rel 'ue to :ther Failures K
R2/G11"1a H3ED3/H Allocation Rel R
R2/G$"!a H3D.A Resource Retaina8ility 5or 2RT Tra55ic K
R2/G11"2a H3ED3/H Allocation 'ue to RA Failure K
R2/G$%%a H3D.A Ra'iolin* 5ailures 62RT7 R
R2/G$%a H3D.A 2on H Ra'iolin* 5ailures 62RT7 R
R2/G$%!8 H3ED3/H release 'ue to mo8ility 62RT7 R
R2/G$81a H3ED3/H release 'ue to preEemption 62RT7 R
R2/G%2>a H3ED3/H to D/H s4itch E other 62RT7 R
R2/G11"%a &ED/H Allocation Rel R
R2/G!1!a H3U.A resource Retaina8ility 5or 2RT Tra55ic K
R2/G11"8a &ED/H Rel 'ue to RA Failures K
R2/G111a &ED/H Rel 'ue to H3ED3/H servin0 cell chan0e K
R2/G11"!a &ED/H Rel 'ue to :ther Failures K
Fi0ure sho4s one e=ample a8out H3ED3/H an' D/H release reasons. ?asically it tells the
portion o5 RA 5ailures compare' to other 5ailures 5rom three 'i55erent channel types.
#igure ,, &'amp!e of 4SDP0 re!ease types =D>
Fi0ure $ sho4s one e=ample a8out H3ED3/H 5ailure reasons. They are 8ase' on tra55ic
counters. There is not only mo8ility causin0 the pro8lems 8ut also some lac* o5 capacity.
/opyri0ht 1 2o*ia 3iemens 2et4or*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 H3U.A release the main cause is ra'io lin* 5ailure.
#igure ,6 &'amp!e of &+DC4 re!ease
$ H3.A B R!! 8earer inter4or*in0
Chen o5 R!! an' H3.A 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 D/H po4er
reservation on the H3D.A cell throu0hput. Fi0ure ! presents the e55ect o5 H3E.D3/H co'e
allocation on the co'e tree occupancy an' num8er o5 availa8le 3F#2 co'es use' 5or $>*8ps
connections. This resource sharin0 can cause some per5ormance 'e0ra'ation on 8oth R!! an'
H3.A users
/opyri0ht 1 2o*ia 3iemens 2et4or*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' /& 6H3U.A7 sharin0
$.1.1 DA po4er sharin0
The po4er sharin0 8et4een H3D.A an' D/H tra55ic can 8e monitore' 8ase' on the .t=Total
an' .t=2onH3D.A measurements reporte' 8y the ?T3. 2onEreal time 8earer po4er 6.t=2RT7
can 8e monitore' separatelyU it is calculate' 8y the R2/ as the sum o5 'e'icate' po4er
measurements o5 2RT 8earers receive' 5rom ?T3.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e $% 6827
Fi0ure $" presents an e=ample 6?T3 measurements 5rom :nlineEmonitorin07 o5 po4er sharin0
8et4een H3D.A an' 2RT D/H tra55ic. The 'ynamic resource allocation is active an' all
availa8le po4er is allocate' to H3D.A 6a8out >C is use' 8y ///Hs7 4ith ma=imum o5 1. C.
The H3D.A po4er is avera0e' over the reportin0 perio' an' it 'epen's also on the H3D.A
activity 6TT+ activityK7.
#igure -9. D" power sharing etween 4SDP0 and NRT PS traffic.
The cell level DA po4er measurements are store' to num8er o5 counters an' ,.+s, Ta8le 2#
lists the main counters/,.+s an' relate' measurements 5rom ?T3. H3D.A transmit po4er is
calculate' as .t=Total H .t=2onH3.A.
Ta!e %/. P)s re!ated power sharing etween 4SP0 and R<< traffic
Report: Cell Capacity RSRA*-7/
R2/G1"28 Avera0e R!! Do4nlin* Aoa' '?m
R2/G$!"a Avera0e active nonEH3D.A po4er ratio K
R2/G$!1a Avera0e nonEH3D.A po4er ratio K
;1"""/2#$ ;+2GH3.AGDAG.:C&R '?m
;1"""/2#% ;AVGH3.AGDAG.:C&R '?m
;1"""/2#8 AV&GH3.AGDAG.:C&R '?m
;1"""/2#2 ;+2G.TVGTAR<&TG.3 '?m
;1"""/2## ;AVG.TVGTAR<&TG.3 '?m
;1"""/2#> AV&G.TVGTAR<&TG.3 '?m
R2/G1"18 Avera0e Uplin* R!! Aoa' '?m
R2/G1%%8 2oise 5loor o5 the 3ystem '?m\E1""."
;"""/1> H3U.AGUAG.CRG;+2 '?m
;"""/1 H3U.AGUAG.CRG;AV '?m
;"""/1$ H3U.AGUAG.CRGAV< '?m
Report: *R+ Radio #earer !#S and ,&C RSRA*-2:
;1"""/1>2 R?GD:C2<RGDU&G:A/GTF/G3U?3 R
;1"""/1> R?GD:C2<RGDU&G:A/GRAGR&/:2F R
;1"""/1$$ R?GR&A&A3&GDU&G:A/GRAGR&/:2F R
;1"""/1>% R?GD:C2<RGDU&G.?3G+2T&RF R
;1"""/12 R?GD:C2<RGDU&G.R&G&;.G+2T&RF R
;1"""/1! R?GR&A&A3&GDU&G.?3G+2T&RF R
;1"""/1$> R?GR&A&A3&GDU&G.R&G&;.G+2TF R
The main interest is on the monitorin0 o5 availa8le DA po4er 5or H3D.A an' also ho4 much o5
this po4er is actually use'. The availa8le po4er can 8e measure' 8ase' on the
;1"""/1#8GAV<G2:2GH3D.AG.CR counter or Avera0e DA Aoa' R2/G1"28 ,.+. The
H3D.A po4er utilisation can 8e measure' as ratio o5 avera0e H3D.A po4er
AV&GH3.AGDAG.:C&R an' avera0e availa8le H3D.A po4er.
Ao4 level o5 availa8le H3D.A po4er 4ill have an e55ect on the pea* 'ata rates in the cell.
H3D.A cell throu0hput limitation can 8e 'etecte' 4hen the po4er utilisation increases.
#igure -$. D" power sharing ana!ysis.
?elo4 is one e=ample o5 H3D.A po4er compare' to Avera0e DA/UA loa'. Cith Dynamic po4er
allocation / resource allocation it is possi8le to use all le5t over po4er 5or H3D.A. H3D.A po4er
measurement 4ith avera0e' input values.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e $! 6827
/onsi'er activation o5 2
n'
carrier 5or H3.A
H3D.A DA po4er
availa8ility
AV<G2:2GH3D.
AG.:C&R Y "K
H3D.A po4er
utiliMation Y "K
Tes
2o
2o
/hec* other
resources
#igure -%. 0verage ." and D" !oad as a function of 4SDP0 power
;inimum, avera0e an' ma=imum H3U.A UA physical channel po4er 6;"""/1>E1$7 coul'
8e use' to see ho4 UA po4er is chan0in0 in 'ue to H3U.A. Ri0ht no4 they seem not 0ivin0
reasona8le values 6E112 '?m 'urin0 most o5 the cases7.
$.1.2 /hannelisation co'e tree sharin0
The DA /hannelisation co'e tree is share' 8y the H3D.A tra55ic, D/H tra55ic an' ///Hs. Chen
H3D.A is activate' in the cell it reserves a minimum reservation o5 co'es out o5 1$ 3F1$
co'es. The co'e reservation 5or H3D.A an' R!! tra55ic is controlle' 8y 5ollo4in0 principles an'
monitore' 8y the ,.+s an' counters. Ta8le 2> lists the main .+s relate' to channelisation co'e
tree reservation an' sharin0.
Ta!e %1. P)s re!ated to channe!isation code sharing etween 4SP0 and R<< traffic.
R2/G11#a Avera0e occupancy K
R2/G2"8 ;a= occupancy K
R2/G1!8 ;in occupancy K
;1"""/8# 2?RG3U//G/:D&GTR&&GAAA: R
R2/G!>!a687 3prea'in0 /o'e ?loc*in0 rate in DA K
R2/G128 3F> 8loc*in0 rate K
R2/G1#8 3F8 8loc*in0 rate K
R2/G1>8 3F1$ 8loc*in0 rate K
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %" 6827
R2/G18 3F#2 8loc*in0 rate K
R2/G1$8 3F$> 8loc*in0 rate K
R2/G1%8 3F128 8loc*in0 rate K
R2/G188 3F2$ 8loc*in0 rate K
;1"""/2$$ /HG/:D&GD:C2<GRT R
;1"""/2$% /HG/:D&GD:C2<G2RTGD/H R
;1"""/1>8 R?GD:C2<RGDU&G.?3G3.R&AD R
;1"""/1# R?GD:C2<RGDU&G.R&G&;.G3.R&AD R
;1"""/1$" R?GR&A&A3&GDU&G.?3G3.R&AD R
;1"""/1$ R?GR&A&A3&GDU&G.R&G&;.G3.R&A R
The H3D.A co'e reservation is increase' 4hen the 5irst H3D.A connection is setup to the cell
or perio'ically 4hile the H3D.A is active in the cell, i5 the cell is con5i0ure' 4ith hi0her num8er
o5 co'es than 6up to 17 an' the U& support that also. H3D.A co'e reservation can 8e
increase' until the num8er o5 5ree 3F1$ co'es is less that 6S!DSC6%ar$inSF23A parameter.
This parameter tells ho4 much mar0in is reserve' in the co'e tree. This parameter coul' 8e set
even to Mero, 8ecause RT calls 4ill preEempt or 'o4n0ra'e H3D.A co'es i5 3F1$ co'es are
5ully use'. This can 8e seen in the Fi0ure $#.
#igure -/. 4SDP0 Code downgrade due to 03R with 4SPDSC43arginS#$%7I9
The total co'e occupancy o5 R!!DH3D.A tra55ic can 8e monitore' 4ith R2/G11#a 6Avera0e
occupancy7, R2/G2"8 6;a= occupancy, ;1"""/%7, R2/G1!8 6;in :ccupancy7 an'
H3D.A co'e usa0e counters ;1"""/2>8E28. The 0raph 8elo4 present an e=ample o5 co'e
tree occupancy an' H3D.A co'e usa0e. +n the 8elo4 e=ample the co'e occupancy is lo4 4hen
the H3D.A co'e allocation is at minimum 6 co'es static allocation7, 4hich in'icate' lo4
amount o5 R!! tra55ic. Accor'in0 to co'e tree occupancy calculations, the allocation o5 1" H3E
.D3/H co'es raises co'e occupancy to a8out %"K 4ithout any R!! tra55ic, 4ith H3E.D3/H
/opyri0ht 1 2o*ia 3iemens 2et4or*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 8e allocate' as 4ante' 5rom net4or* point o5 vie4. The 'e5ault set is to use
co'es li*e , 8, 1", 12, 1> an' 1 4ith 1 co'es 5eature. ?ut it is also possi8le to use all co'es
5rom net4or* point o5 vie4 8y chan0in0 Qust the co'e usa0e 8y H3E.D3/H co'e set in R2/.
The picture 8elo4 sho4s that re0ar'less o5 U& cate0ory an' co'e capa8ility, the net4or*
allocates all availa8le co'es 5or H3D.A. Also i5 net4or* allocates possi8le co'es 6li*e 'e5ault
values7 U& can still use other num8er o5 co'es 'epen'in0 on the situation. /at! U& supports 1
co'es, /at8 U& supports 1" co'es an' /at U& $ supports co'es.
#igure -,. &'amp!e of 4SDP0 J NRT code a!!ocation duration with different .&s
The .3 2RT allocation 6up0ra'e or initial 8it rate7 can 5ail i5 there is no 5ree co'e 5or 2RT D/H.
A co'e allocation 5ailure causes typically the pac*et sche'uler to allocate o5 lo4er 8it rate
6hi0her 3F7 i5 possi8le.
The overall co'e 8loc*in0 can 8e monitore' 4ith R2/G!>!8 63prea'in0 /o'e ?loc*in0 rate in
DA7 an' per 3F 4ith ?loc*in0 rate o5 3F 'ue to 2o co'es availa8le( .+s R2/G128ER2/G188,
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 8loc*in0
rate. +t sho4s that 4hen the avera0e co'e occupancy increases a8ove "K, the ma=imum co'e
occupancy reaches 1""K an' co'e tree 8loc*in0 rate increases.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %# 6827
#igure --. Code tree occupancy.
Ao4 amount o5 co'e 8loc*in0 can 8e tolerate' as it is typically 'ue to 2RT D/H allocation
attempts 5or lo4 3F 8earers 63F8 an' 3F1$7. Fi0ure $% presents an' e=ample o5 increase'
co'e tree 8loc*in0 rate an' the 3F6s7 that cause the 8loc*in0.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %> 6827
#igure -6. Code tree !ockingK with code downgrade due to congestion.
An incomin0 RT call 4ill al4ays 'o4n0ra'e 6preEempt7 the H3D.A co'e reservation. Also .3
2RT allocation 6up0ra'e or initial 8it rate7 can 5ail i5 there is co'e con0estion. A co'e allocation
5ailure causes typically the pac*et sche'uler to allocate o5 lo4er 8it rate 6hi0her 3F7 i5 possi8le.
The co'e tree con0estion can cause also that the 2RT R? are 'o4n0ra'e' or release' 8y .?3
or preEemption 'ue to co'e tree con0estion. R? 'o4n0ra'e/release 'ue to co'e con0estion can
8e seen 5rom the R3 R3RA2"1# an' the counters are(
;1"""/1>8GR?GD:C2<RAD&G?TG.?3GDU&GT:G3.R&AD+2<G/:D&G/:2<&3T+
:2
;1"""/1#GR?GD:C2<RAD&G?TG.R&E
&;.T+:2GDU&GT:G3.R&AD+2<G/:D&G/:2<&3T+:2
;1"""/1$"GR?GR&A&A3&G?TG.?3GDU&GT:G3.R&AD+2<G/:D&G/:2<&3T+:2
;1"""/1$GR?GR&A&A3&G?TG.R&E
&;.T+:2GDU&GT:G3.R&AD+2<G/:D&G/:2<&3T+:2
The re9uest 5or 2RT can 'o4n0ra'e the H3D.A allocation only i5 the parameter
D!C6,ver6S!DSC6+hreshold allo4s it. The amount o5 'o4n0ra'es can 8e monitore' 4ith
H3D.A /H /:D& D:C2<RAD& DU& T: RT ;1"""/2$$ an' H3D.A /H /:D&
D:C2<RAD& DU& T: 2RT D/H ;1"""/2$%.
+n case this parameter is set to Mero, there shoul' not 8e room to 'o4n0ra'e H3D.A co'es 5or
2RT. Ho4ever it has 8een teste' that 4hen the parameter D!C6,ver6S!DSC6+hreshold is
set to Mero, it is still possi8le to allocate 2RT calls. /o'e 'o4n0ra'e happens alrea'y 'urin0 RT
si0nallin0 phase. This is seen in the ne=t picture, note the the last 2 samples are 4ith the
parameter value o5 , so more co'e 'o4n0ra'e can 8e seen in that case.
#igure -7. Code downgrade due to NRT with DPC4Over4SPDSC4Thresho!dI9.
Also it 4as 5oun' that 4hen net4or* is allocatin0 all availa8le co'es 5or H3D.A an' there is no
U& capa8ility to 5ully utiliMe those, it is not possi8le to use remainin0 co'es 5or .3 2RT 4hen the
parameter D!C6,ver6S!DSC6+hreshold is set to Mero.
#igure -<. Setup fai!s with DPC4Over4SPDSC4Thresho!dI9.
+t that case 5or e=ample it can 8e seen that re9G.3GreQGDA counter is up'ate' as there is
capacity up0ra'e re9uests 5rom initial 8itrate to ma=imum. This can also seen as
re9G.3GreQGUA an' .3 setup 5ail A/, 4hich is up'ate' only 4hen there is initial capacity
re9uest 5rom D/H "/" or 5rom FA/H. ?oth cases means that there is no DA co'es availa8le.
+t 4ill 8e recommen'e' not to use Mero value 5or this parameter unless H3D.A 4ill 8e the only
service 5or Data service.
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %$ 6827
$.1.# C?T3 resource sharin0
H3D.A has a static reservation 5rom C?T3 resources. This reservation 'epen's on the H3D.A
sche'uler type an' num8er o5 sche'ulers active in the ?T3. The resource reservation o5 R!!
tra55ic 'epen's on the tra55ic level an' can 8e si0ni5icant in share' carrier.
The H3D.A return channel is critical 5rom ?T3 HC availa8ility point o5 vie4 especially in areas
4ith hi0h H3D.A tra55ic. The return channel can utilise 2RT D/H or H3U.A channel type. 2RT
D/H return channel reserves ?T3 resources 5rom the UA channel element pool. Ta8le 2
presents the /& reservation o5 D/H 8earers. The H3D.A return channel 8it rates an' /&
reservations are hi0hli0hte'.
Ta!e %,. G2TS C& reservation of DC4 earers.
?earer 'ata rate /& UA/min 3F /& DA/min 3F
3R? #.>/1#.> *8ps 1/ 3F2$ 1/ 3F2$
A;R 6voice7
17
1/ 3F$> 1/ 3F128
C?EA;R
27
1 / 3F$> 1 / 3F128
/3 $> *8ps > / 3F1$ > / 3F#2
PS $- kps $ 8 S#-1 1 / 3F128
.3 #2 *8ps 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
H3U.A return channel reservation the D/H an' &ED/H resources share the same D3.
resource pool. The D/H has the hi0hest priority, an' 4hen the resources are le5t 5rom the D/H,
the resources are 0iven to the &ED/H. The H3U.A 4ill have a minimum resource allocation o5 8
/&, this can not 8e allocate' to D/H. The ma=imum total num8er o5 H3U.A users an' total
throu0hput 'epen's on the amount o5 availa8le /& resources, e=ample ta8le 5rom RA3"$
8elo4(
Ta!e %- ."8D" C& reservation for 4S.P0 in R0S9- #!e'i 2TS
UA/DA /&
reservation 5or
H3U.A
?ase8an' 'eco'in0 capa8ility, .hysical Aayer
;8ps
R H3U.A 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 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %% 6827
The ?T3 HC resource status can 8e monitore' 4ith C?T3 HC resource counters in the ;""1
counter ta8le. This measurement supports the measurement o5 total availa8le /& capacity
6license'7, /& reservation an' H3U.A speci5ic /& reservation
The total /& reservation can 8e monitore' 4ith ma=imum, minimum an' avera0e use' /&
counters an' R2/ ,.+s li*e R2/G!!a 6;a=imum Use' /&^s ratio7, R2/G%#"a 6Avera0e Ratio
o5 Utilise' /& 5or DA in ?T37 an' R2/G%#1a 6Avera0e Ratio o5 Utilise' /& 5or UA in ?T37.
The H3U.A /& reservation can 8e monitore' 4ith ma=imum an' minimum use' /& counters
an' R2/ ,.+s R2/G!>%a an' R2/G!>8a 6Avera0e ratio o5 utilise' /& 5or DA/UA 5or H3U.A in
?T37.
A H3U.A throu0hput limitation 'ue to lac* o5 /&s is in'icate' 8y the 5ollo4in0 counters(
1"""/2$8 ?T3 H3U.A 2:T HC A+;+T&D DURAT+:2( +n this state, the ?T3 HC 'oes
not limit the H3U.A throu0hput.
1"""/2$! ?T3 H3U.A HC A+;+T&D DURAT+:2( +n this state, the R2/ sets up the &E
D/H 8ut the ?T3 HC shorta0e may cause the throu0hput to 8e lo4er than e=pecte'
1"""/2%" ?T3 H3U.A HC 2: /A.A/+TT DURAT+:2( +n this state, the R2/ 'oes not
set up the &ED/H
The .+s 'iscusse' a8ove to0ether 4ith other ?T3 resource relate' .+s are liste' in ta8le 8elo4.
Ta!e %6. P)s re!ated power sharing etween 4SP0 and R<< traffic
R2/G!a .3 /all 3etup FR 'ue to ?T3 K
R2/G$%>a H3D.A Access FR 'ue to ?T3 K
R2/G!$a &ED/H 3etup FR 'ue to ?T3 K
R2/G!%a &ED/H 2ot 3electe' 'ue the ?T3 HC K
R2/G!8a RA 3etup FR 'ue the ;+3/ K
;1"""/2$8 ?T3GH3U.AGHCG2:TGA+;+T&DGDUR s
;1"""/2$! ?T3GH3U.AGHCGA+;+T&DGDUR s
;1"""/2%" ?T3GH3U.AG2:GHCG/A.AGDUR s
;""1/" ;AVGAVA+AG/& +nte0er num8er
;""1/1 ;+2GAVA+AG/& +nte0er num8er
;""1/2 AV<GAVA+AG/& +nte0er num8er
R2/G8#"a /& situation chan0e in'ication R
;""1/# ;AVGU3&DG/&GDA +nte0er num8er
;""1/> ;AVGU3&DG/&GUA +nte0er num8er
R2/G!!a ;a=imum Use' /&^s ratio K
;""1/ ;+2GU3&DG/&GDA +nte0er num8er
;""1/$ ;+2GU3&DG/&GUA +nte0er num8er
R2/G822a Avera0e 5ree /&s R
R2/G%#"a Avera0e ratio o5 utiliMe' /& 5or DA in ?T3 K
R2/G%#1a Avera0e ratio o5 utiliMe' /& 5or UA in ?T3 K
;""1/! ;AVGH3U.AG/&GUA +nte0er num8er
;""1/12 ;AVGH3U.AG/&GDA +nte0er num8er
;""1/1" ;+2GH3U.AG/&GUA +nte0er num8er
;""1/1# ;+2GH3U.AG/&GDA +nte0er num8er
R2/G!>%a Avera0e ratio o5 utiliMe' /& 5or DA 5or H3U.A in ?T3 K
R2/G!>8a Avera0e ratio o5 utiliMe' /& 5or UA 5or H3U.A in ?T3 K
;1"""/1>$ R?GD:C2<RGDU&G.?3G?T3 R
;1"""/11 R?GD:C2<RGDU&G.R&G&;.G?T3 R
;1"""/18 R?GR&A&A3&GDU&G.?3G?T3 R
;1"""/1$# R?GR&A&A3&GDU&G.R&G&;.G?T3 R
Fi0ure %" 8elo4 presents an e=ample o5 ?T3 resource reservation 4ith H3D.A. The minimum
UA an' DA resource reservation is $ 61$ 5or //Hs, 8 5or H3U.A an' #2 5or H3D.A7. +t also
sho4s that the ma=imum UA reservation is normally hi0her.
#igure 69. &'amp!e of G2TS resource sharing with 4SDP0
/opyri0ht 1 2o*ia 3iemens 2et4or*s 2""8 /ompany con5i'ential .a0e %! 6827
Fi0ure 8elo4 sho4s an e=ample o5 C?T3 resource reservation 4ith H3U.A. Cith hi0h level o5
H3D.A return channel on D/H causes typically hi0h UA reservation. The ma=imum H3U.A
reservation is $>, 4hich is 5or e=ample 'ue to user 4ith Y1.> ;8ps throu0hput in Ultrasite ?T3.
#igure 6$. &'amp!e of G2TS resource sharing with 4S.P0
Aac* o5 ?T3 resources is the most common reason 5or H3D.A an' H3U.A accessi8ility
5ailures. These 5ailures are monitore' 4ith ,.+s( R2/G$%>a 6H3D.A Access FR 'ue the ?T37,
R2/G!$a 6&ED/H 3etup FR 'ue the ?T37, R2/G!%a 6&ED/H 2ot 3electe' 'ue the ?T3
HC7. ;ore a8out the return channel per5ormance in 3ections .1.1 an' .1.2.
$.2 &55ect o5 H3.A on R!! per5ormance
The main concern relate' to e55ect o5 H3.A tra55ic on R!! tra55ic per5ormance is typically relate'
to a''itional inter5erence cause' 8y H3D.A in DA. This is easy to un'erstan' in a case 4hen
the H3D.A 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 pro8lems
an' call 'rops. The 'ecrease' &c/2o can also increase the amount o5 interEsystem han'overs
or cell reEselections to <3;, as the &c/2o is typically use' as the main criteria tri00erin0 the
proce'ures.
Fi0ure %2 presents an e=ample o5 net4or* per5ormance 5or t4o years 5rom the H3D.A launch.
+n this e=ample the A;R call Retaina8ility is even improve' 'espite the increase' H3D.A tra55ic.
The H3D.A accessi8ility an' retaina8ility are sli0htly 'roppe', 8ut still remain in 0oo' level.
#igure 6%. &ffect of increased 4SDP0 traffic on CS R02 and 4SP0 earer performance.
Re5erences
I1J H3.A Ra'io 2et4or* .lannin0 <ui'e
I2J #< Ra'io 2et4or* .lannin0 <ui'elines 5or RA3"$ an' RU1"
https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$#$%$2%
I#J RA3"$ .ro'uct Documentation
I>J ^,.+ 5or H3D.A .lannin0^, 1
st
)anuary 2""%
IJ ;ultilayer 0ui'eline https(//sharenetE
ims.insi'e.no*iasiemensnet4or*s.com/:pen/#8#$2$#8
I$J Fle=i C/D;A ?T3 sales 0ui'e E ?ase8an' 'imensionin0
https(//sharenetE
ims.insi'e.no*iasiemensnet4or*s.com/livelin*/livelin*/0uest/Do4nloa'/#$"111>8
I%J .ac*et 3che'uler optimisation 0ui'e
https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$>!"!!$
I8J /apacity ;ana0ement <ui'e D /apacity Cor*shop Hphase 2, )ussi Reunanen et all.
https(//sharenetEims.insi'e.no*iasiemensnet4or*s.com/:pen/#$#!%2!8#
I!J H3D.A B H3U.A throu0hput an' parameter testin0 in 2T2 https(//sharenetE
ims.insi'e.no*iasiemensnet4or*s.com/:pen/#!8$1!"
I1"J AA; RA3"$ &=periences, .aul Aarsen 12/2""8
I11J RA2 &2& system per5ormance optimiMation 0ui'e
I12J ,.+ list an' tar0ets recommen'ation 'oc https(//sharenetE
ims.insi'e.no*iasiemensnet4or*s.com/:pen/#$>$1$%##


Data Performance Optimisation Guideline v07

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Data Performance Optimisation Guideline v07

Transféré par

Droits d'auteur :

Formats disponibles

1/82 Document Type

Vous aimerez peut-être aussi