課件分析教案

Background2?

NokiaNetworks

2011Dept.

/

Author/

DateCustomer

complained

about

the

much

poorer

experience

in

TokaidoShinkansen

(NSN)

area

compared

to

E///

area,

particularly

in

RNC443coverage

areaRNC443

was

selected

for

the

quality

improvement

project

and

the

wasto

achieve

-user

experience

(particularly user)

on

par

with

orbetter

than

E///

area

by

end

of

Sep’11A

special

task

force

was

setup

withjoint

effort

from

NWS

TS

and

NPO

inAug’11

(with

both

global

and

localpresence)The

troubleshooting

and

optimizationwasconducted

through

UE

and

RNC(Megamon)

logs

and

KPI

ysisRide-test

was

done

regularly

toben ark

both

NSN

and

E///performance

and

to

collect

the

logsfor

ysisTokaido-lineRNC443RNC443RNC413ⅢⅣ333

33223233322

23232222RNC443RNC443Length:

22kmTop

speed:

270km/hTraveling

time:

5

minsNo.

of

cells:

25

–

27Avg

time

per

cell:

~12

sec(someare

just

4

sec)Carrier:

All

with

F1/F2,

some

with

F3

for

HSDPAtraffic

onlyBTS

type:

Mostly

Ultrasiteas

of

Aug’11.to

replace

all

BTS

to

Flexi

by

end

of

Sept’113 ?

Nokia Networks

2011/RNC442RNC444Ⅴ323333232323

333222222322222233222

2323222222233322333

ⅡBTS

Replacement(to

flexi

rel2)AddSystem

ModuleAdd

Iub

BWAddCarrieLocationUpdate

AreaCoverage

holeNumber

of

Carrier2

or

3Problem

Overview

(1/2)Slow

cell

reselectionUE

camps

on

wrong

cell

during

RRC

or

PS

call

setup

causing

poor

PS

performance,especially

in

fast

changing

radio

conditionCell

reselection

time

significantly

slower

thanE///SHO

parameter

optimizationLow

Add/Drop

windows

(6/8dB)

used

previously

causing

large

AS

size,

many

e1c

andpossibly

wrong

cells

in

ASLarge

Cell

Individual

Offset(4-10dB)

used

from

the

previous

optimization

task

causinga

lot

of

initial

RL

sync

failure

for

SHOFrequent

Active

Set

Updates

cause

problem

with

parallel

procedures

=>

impactonHSDPA

SCC

and

hence

HSDP

rformanc3.ing

Procedures

and

SCC

not

fast

enoughFrequent

ASU

and

SCC

due

to

fast

changing

radio

condition

causing

UE

notalwaysusing

the

best

cellOther

RB

proceduressuch

as

code

tree

optimization,

bitrate

upgrade

and

downgrade(TBO

&

FU)

can

happen

undesirablyToo

many

procedures

causes in

ASU

and

SCC,

and

potentially

low

throughputand

drop

callUL

power

esUL

power es

observed

and

the

worst

cells

are

on

the

RNC/LAC

border

duetomany

registrationsHigh

UL

noise

can

potentially

cause

bad

DL

throughput

(high

MAC-hsretransmission)4?

NokiaNetworks

2011Dept.

/

Author

/

DateProblem

Overview

(2/2)Zero/low

HSDPA

throughputContinuous

zero

or

low

HSDPA

throughput

when

HSDPA

is

allocatedPossibly

due

to

high

UL

noise,

orbad

DL

quality

(bad

cell,

Ec/No,

not

enough

HSDPApower,

delay

in

SCC,

etc.)Problem

observed

where

CQI

can

be

high

or

lowApplication

server/client

performance

was

investigatedInter-RNC

mobility

issueNo

HSPA

over

Iur

and

RRC

Release

was

used

for

inter-RNC

mobilityCCH

Setup

feature

was

used

on

RNC

border

cells

to

relieve

congestion

caused

by

toomany

location

update.

However

high

mobility

can

increase

chances

ofregistrationfailure

on

CCH

which

leads

to

UE

unable

toregister

to

the

networkPoor

dominance

causing ponging

on

RNC

borderDelayed

NBAP

procedure?Counters

show

that

some

BTSs

sufferfrom

long

RL

setup

time

(hourly

avg

up

to700ms).due

to

too

many

RL/s

or

not

enough

Iub

BW

forNBAP

signaling

during

thetime

when

the

train

passes

the

cell

and

all

the

users

aretrying

to

setup

a

call

(mostlylocation

update

and

PS

call)

within

a

few

secondsRF

optimization

issuePoor

dominance,

Ec/No

drops

too

quickly,

very

short

duration

(few

seconds)5?

NokiaNetworks

2011Dept.

/

Author

/

DateInvestigation

and

Solutions6?

NokiaNetworks

2011Dept.

/

Author

/

DateSIB

Priority

OptimizationSIB

scheduling

priority

was

optimized

such

that

the

most

important

SIB

issent

at

the

highest

priority

1

(most

frequent),

the

essential

SIBs

at

the

samepriority

3

and

the

rest

at

the

lowest

priority

4

(least

frequent)Key

improvement

:Reduced

Cell

reselection

timeImproved

CSSR

CS

&

PSImproved

registration

success

rateImproved

end-user

experienceFinal

settingSIBTypePriorityNSNPriority

NSNShinkansen

AreaNewConfiguration12232224332343345323633471111144312444184447?

NokiaNetworks

2011Dept.

/

Author

/

DateSIB

Priority

OptimizationReducedCell

Reselection

Time0.91910RNC

443

&

RNC

444

Reduction

in

Cell

Reselection

is

Evident.[SIB

Priority

changed

on

RNC

443

and

RNC

444

only]Average

Cell

Reselection

is

lower

than

E///on

RNCs

443

&

444Cell

Reselection

TimeNewOriginal00.10.20.30.40.50.60.70.8012345678Duration

/

secondsnsn_areaCell

Reselection

Timesetting8?

NokiaNetworks

2011settingSIB

Priority

OptimizationCell

Reselection

faster

than

E///Average

Cell

Reselection

Time

Excluding

Outliers:E///

Area:

0.72sNSN

Area:

0.45sNSN

Cell

Reselection

is

now

~60%

faster

than

E///Cell

Reselection

Time

[SuccessfulReselections]109876543210Cell

Reselection

Time

/

snsn_areasib_block_duration9?

NokiaNetworks

2011SIB

Priority

OptimizationImprovement

in

CSSR_CS/PS,

PS/RRC

ADR

and

Registration

failurerateCSSR

CS

improved

from

99.235%

to

99.271%CSSR

PS

improved

from

98.533%

to

99.088%8AM4AMThe

average

value

iscalculated

11:00~20:59

in

16th

and

17th

-AUG.10?

NokiaNetworks

2011/PS

&

RRC

ADR

aswell

as

RegistrationFailure

Rate

have

improved

significantlyCCH

SetupPros

and

ConsCCH

Setup

was

enabled

on

RNC

border

cells

to

allow

RRC

Setup

via

CCHfor

Registration

cause

only.Lower

oSRBMapRRC

(from

-8dB

to

-12dB)

than

the

default

value

helpspush

more

registration

attempts

from

DCH

to

CCH share

of

Registration

Att

onCCH

is

about

40-50%Significant

improvement

in

reduction

of

RRC

Connection

Rejection

(mostly

due

toACand

BTS)RRC

Setup

Success

rate

was

improved

(RRC

Setup

phase

only)However,

some

negative

impact

was

observed:Increase

in

RRC

ACC

Failure,

especially

when

using

loweroSRBMapRRCIncrease

of

Cell

Update

over

Iur

due

to

cell

reselection–

Avg

time

required

for

registration

is

3.3

secIncreaseof

NAS

signaling

timeout

due

to

cell

reselection

causing

UE

unable

tocompleteregistration “No

Service”

from

end-user

and

“zero”

throughput11?

NokiaNetworks

2011Dept.

/

Author

/

DateCCH

Setup

Impact

on

KPIF3/F4

loadbalance9

sites

fallback

to

-8dBCCH

Setup

(30sites)oSRBMapRRC=

-8dBLower

oSRBMapRRCpushes

more

RRC

setup

on

CCH,

butdegrades

RRC

ACC

COMP

on

CCHLayering

strategy

helps

balanceRRCsetup

attempts

and

hence

improveRRC

ACC

COMPWithoutCCH

SetupCCH

Setup

(30sites)CPIC

oSRBMapRRC=

-1

2dBIt

seems

higher

Ec/No

threshold

forCCH

setup

is

more

preferred

underhigh

speed

condition12?

NokiaNetworks

2011Dept.

/

Author

/

DateCCH

Setup

Impact

on

KPIWithoutCCH

SetupCCH

Setup

(30sites)oSRBMapRRC=

-8dB9

sites

fallback

to-8dBCCH

Setup

(30sites)oSRBMapRRC=

-12dBF3/F4

loadbalanceReg_Success_R

(based

on

service

counter)has

improved

only

at

the

RRCsetup

phase.Significant

reduction

in

RRC_CONN_REJECT13?

NokiaNetworks

2011Dept.

/

Author

/

DateCCH

SetupDecision

was

to

disable

CCH

Setup

on

ShinkansenDespite

the

improvement

observed

from

KPI,

the

major

concern

is

theproblem

of

increasing

chances

of

registration

failure

on

RNC

border

due

tocell

reselection

when

UE

is

moving

at

high

speed

and

the

very

short

time

UEspends

on

the

serving

cell

(<

4

sec)Increase

in

LU

failures

observed

when

UE

performs

Cell

Update

over

IurUE

may

be

temporary

out

of

service

and

end

user

may

not

get

any

DL

throughputIt

was

decided

that

CCH

Setup

was

disabled

at

the

same

time

when

theUltrasite

was

replaced

by

FlexiBased

on

the

fact

the

signaling

procedure

handled

by

Flexi

BTS

is

faster

and

moreBB

capacity es

available

after

the

replacementFurthermore,

channel

type

switching

to

DCH

was

used

for

inter-RNC

mobilityHowever,

it

was

observed

that

at of

the

project

when

all

the

Flexireplacement

was

completed,

those

cells

on

the

RNC

borders

still

sufferedfrom

RRC_CONN_REJECT

and

the

reason

was

mostly

due

to

codecongestion.

This

problem

will

be

tackled

in

the

next

phase

of

the

project.Some

known

problem

of

UE

performing

LU

but

failed

has

some

workaroundsolution

whi ay

help

the

above

problem14?

NokiaNetworks

2011Dept.

/

Author

/

DateUL

PoweresUL

power es

was

high

particularly

on

the

RNC

border

cells

when

thetrain

passes

due

to

many

registration

att

for

location

update

and

PS

callBRM

monitoring

shows

the

burstiness

of

the

UL

power es

which

seemsto

follow

the

schedule

when

the

train

passes

the

cellPower es

last

from

a

couple

of

sec

up

to

10

sec20110926

18:30-19:00

-

WBTS9039Most

parameter mendation

in

TN159

had

been

implemented,

so

thefocus

to

reduce

UL

power es

was

on

the

PRACH

parameter

optimization-105-110-100-90-95-85-70-75-80Prx

[dBm]31332333331432433415?

NokiaNetworks

2011Dept.

/

Author

/

DatePRACH

Parameter

OptimizationNSNSBM

defaultNSNNew

valuesE///(from

SIB5)availableSignature4416availableSFsfpr32sfpr32Sfpr64powerOffsetPp-m2-3-4constantValue-21-21-18powerRampStep331preambleRetransMax8832mmax848nb01Min0200nb01Max50500PtxAICH-6-3-616?

NokiaNetworks

2011PRACH

parameter

change

schedule:13th

Sept

:

5

sitesin

RNC44326th

Sept

:

ALL

sites

in

RNC443

&

RNC444RNC440,441,442

remains

to

use

SBM

default

valuesRidetest

logs

on

2nd

Sept

and

26th

Sept

were

used

for

theafter

comparisonysis

and

before-and-PRACH

performanceysisysed

and

PRACH

info

was

extractedUE

logs

from

short

call

test

wereNo.

of

preambles

for

each

PRACH

transmission

cycleTxpower

of

the

last

preambleAICH

status:

0

=

“No

Ack”;

1

=

“Ack(-)”;

2

=

“Ack(+)”UL

interference

from

SIB7Estimated

UL

Rx

level

from

the

last

preamble=Tx

power

of

last

preamble

–

(CPICH

Tx

power

–

CPICH

RSCP)A

successful

RACH

process

is

determined

in

such

way

that

UE

shouldsend

the

preamble

at

the

minimum

power

as

required

by

the

BTS

withminimum

number

of

preamble

transmission,

receive

Ack(+)

in

AICH,

sendthe

RA essage

(e.g.

RRC

Conn

Request),

and

then

BTS

shouldreceive

the

RA essage

successfullyThe

impact

from

the

PRACH

parameters

will

be

studied

by

comparingAverage

UL

interference

as

reported

in

SIB7Difference

between

UL

interference

level

and

est.

UL

Rx

level

(≈

C/I)Locations/cells

with

AICH

“No

Ack”

and

high

UL

interference

will

beinvestigated

separa

y17?

NokiaNetworks

2011Dept.

/

Author

/

DatePRACH

Parameter

OptimizationSBM

default

@

2-Sept

–

RNC443,444101214161820-110-100-90-80-70-60PRACH

info

on

RNC443,444-

0902

SY-NGAvg

EstUL

RxlevelAvg

UL

interferenceDiff

(C/I)-101.33

dBm-96.98

dBm-4.35

dB02468-160-150-140-130-1202011-09-02

16:36:56.0002011-09-02

16:36:58.0002011-09-02

16:37:00.0002011-09-02

16:37:31.0002011-09-02

16:37:38.0002011-09-02

16:38:10.0002011-09-02

16:38:47.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002.0002011-09-02

16:39:42011-09-02

16:40:23011-09-02

16:40:56011-09-02

16:41:38011-09-02

16:42:16011-09-02

16:42:56011-09-02

16:43:31011-09-02

16:43:55011-09-02

16:44:41011-09-02

16:44:46011-09-02

16:45:02011-09-02

16:45:04011-09-02

16:45:06011-09-02

16:45:08011-09-02

16:45:18011-09-02

16:45:49011-09-02

16:46:11011-09-02

16:46:53011-09-02

16:47:12.0002011-09-02

16:47:48.0002011-09-02

16:48:19.0002011-09-02

16:48:36.0002011-09-02

16:48:44.0002011-09-02

16:48:46.0002011-09-02

16:49:22.000Max

of

Cell

Information

UL

Interference

Port

1Max

of

Est

UL

Rx

LevelMax

of

RACH

No.

of

Preambles

Port

1Min

of

AICH

StatusEst.

UL

rx

level

follows

closely

UL

interferenceOften

require

several

preambles

per

cycleHigh

occurrence

of

“No

Ack”18?

NokiaNetworks

2011Dept.

/

Author

/

Date2025303540-110-100-90-70-60availableSignatureavailableSFpowerOffsetPp-m16sfpr64-4constantValuepowerRampStep-181preambleRetransMaxmmax-80

nb01Min3280nb01MaxPtxAICH0-6PRACH

Parameter

OptimizationE///

PRACH ysis

@

2-SeptDiff

(C/I)E///

SYNG

-

2

SeptAvg

EstUL

Rxlevel Avg

UL

interference-113.96

dBm

-99.79

dBm-14.17

dB051015-160-150-140-130-12040788.7176198940788.7179844740788.7185427440788.7190988440788.719739240788.720240140788.7202926040788.7205998640788.7212168940788.7219344940788.7226636540788.7231253540788.7236328140788.7243699340788.7250500940788.7257099840788.7264595940788.7269091740788.7273480940788.7279795940788.7282631540788.7289523640788.7296636240788.729715740788.711895949140788.712697291740788.713182326440788.713672407440788.714195057940788.714570312540788.715181203740788.715710891240788.716249814840788.716600289440788.71730016240788.717301967640788.717386064858923126136242118107748825062684498203499711270640788.730046296340788.730866423640788.73123733840788.732040648140788.732541226940788.733090995440788.733758136640788.734044953740788.734742476940788.7355459606Min

of

AICHstatusEst.

UL

rx

level

is

constantly

much

lowerthan

UL

interference

as

it

should.Very

high

AICH

Ack

rateMax

of

Cell

Information

UL

Interference

Port

1 Max

of

Est.

UL

Rx

level Max

of

RACHNo.

of

Preambles

Port

119?

NokiaNetworks

2011Dept.

/

Author

/

DatePRACH

Parameter

OptimizationNew

PRACH

values

@

26-Sept

–

RNC443,444101214161820-110-100-90-80-70-60PRACH

info

on

RNC443,444

-

0926

NG-SY

AMR

ShortAvg

EstUL

Rxlevel Avg

UL

interference Diff

(C/I)-117.58

dBm

-100.9

dBm

-16.68

dB02468-160-150-140-130-12026/09/2011

15:02:4926/09/2011

15:02:5326/09/2011

15:03:1426/09/2011

15:03:3626/09/2011

15:03:5726/09/2011

15:03:5926/09/2011

15:04:2226/09/2011

15:04:4426/09/2011

15:04:5226/09/2011

15:04:5426/09/2011

15:05:1226/09/2011

15:05:3126/09/2011

15:05:5026/09/2011

15:06:1226/09/2011

15:06:3326/09/2011

15:06:5526/09/2011

15:07:1526/09/2011

15:07:3726/09/2011

15:07:4926/09/2011

15:08:0426/09/2011

15:08:0526/09/2011

15:08:0726/09/2011

15:08:0926/09/2011

15:08:1126/09/2011

15:08:2026/09/2011

15:08:2126/09/2011

15:08:4426/09/2011

15:08:4626/09/2011

15:09:0226/09/2011

15:09:1126/09/2011

15:09:3226/09/2011

15:09:5326/09/2011

15:10:1326/09/2011

15:10:3226/09/2011

15:10:5226/09/2011

15:11:1526/09/2011

15:11:3526/09/2011

15:11:5726/09/2011

15:11:5926/09/2011

15:12:2026/09/2011

15:12:3826/09/2011

15:13:0026/09/2011

15:13:2026/09/2011

15:13:4126/09/2011

15:14:0326/09/2011

15:14:2226/09/2011

15:14:2426/09/2011

15:14:4526/09/2011

15:15:0726/09/2011

15:15:27Min

of

AICH

statusEst.

UL

rx

level

is

constantly

much

lower

thanUL

interference

as

it

should.Very

high

AICH

Ack

rateMuch

lower

ULinterferenceMax

of

Cell

Information

UL

Interference

Port2 Max

of

Est.

UL

Rx

level Max

of

RACHNo.

of

Preambles

Port

220?

NokiaNetworks

2011Dept.

/

Author

/

DatePRACH

Parameter

OptimizationSummary

of

results21?

NokiaNetworks

2011Test

dateTest

routeAvgest.

UL

Rx

levelAvg

UL

interferenceDifference

(C/I)E///2nd

SeptSY-NG-113.96

dBm-99.79

dBm-14.17

dBNSN

SBM

default2nd

SeptSY-NG

RNC440-442-98.96

dBm-95.04

dBm-3.92

dB2nd

SeptSY-NG

RNC443,444-101.33

dBm-96.98

dBm-4.35

dB26th

SeptNG-SY

RNC440-442-101.71

dBm-91.18

dBm-10.53

dB26th

SeptSY-NG

RNC440-442-107.37

dBm-98.42

dBm-8.95

dB26th

SeptNG-SY

RNC440-442-101.5

dBm-94.93

dBm-6.57

dB26th

SeptSY-NGRNC440-442-103.37

dBm-97.17

dBm-6.20

dBNSN

New

PRACH

values26th

SeptNG-SY

RNC443,444-117.58

dBm-100.9

dBm-16.68

dB26th

SeptSY-NG

RNC443,444-116.38

dBm-100.19

dBm-16.19

dB26th

SeptNG-SY

RNC443,444-113.64

dBm-99.16

dBm-14.48

dB26th

SeptSY-NG

RNC443,444-112.76

dBm-100.95

dBm-11.81

dBNew

PRACH

parameter

values

bring:Lower

preamble

power

(lower

C/I)Less

number

of

preamble

transmissionHigher

AICH

Ack

rateLower

UL

interferenceRTWP

improvementSW

Improvementon

Faster

SCC

and

AvoidingProcedure1.

Faster

completion

ofS(1/2)rocedureRNC

includes

‘Delay

restriction

flag’

IE

in

serving

cell

change

RRC:

RB

RECONFIGURATIONmessageUE

will

send

RRC:RB

RECONFIGURATION

COMPLETE

immedia y,

without

waiting

activation

timetoelapseRNC

can

start

other

procedure

immedia y

without

waiting

response

message

until

activation

time‘Delay

restriction

flag’

IE

is

valid

only

for

rel6

UEsHSPA

serving

cell

change

procedure

specific

ATO

value

is

appliedThis

enables

setting

SCC

activation

time

even

more

aggressive,

without

impacting

other

procedures.It

is

estimated

SCC

activation

time

could

be

further

reduced

by

around

300

msPrioritization

of

SCC

and

ASU

over

power

offsetupdateHS-DPCCH

power

offsets

are

updated

when

UE

moves

between

SHO

and

non-SHO

state.Current

implementation

uses

physical

channel

reconfiguration

procedure

makes

the

updateimmedia y

after

active

set

update,

if

state

changes

from

SHO

to

non-SHO

or

vice

versa.New

implementation

delays

the

HS-DPCCH

power

offset

updates

by

predefined

wait

timeThis

means

SCC

(or

ASU)

can

be

triggered

right

after

previous

ASU

is

completed,

without

waiting

forthe

power

offset

update

procedure

to

complete.Also

power

offset

update

procedure

can

be

combined

with

SCC

(or

other

RB

reconfiguration)procedure,

if

RB

reconfiguration

procedure

is

triggered

during

the

predefined

wait

time.SCC

is

triggered

faster

and

signaling

is

reduced

in

fast

changing

radio

environment22?

NokiaNetworks

2011Dept.

/

Author

/

DateSW

Improvementon

Faster

SCC

and

AvoidingProcedure

(2/2)HA3

triggers

bothASU

and

SCC

based

onE1a/E1cIf

an

E1A/E1C

triggered

cell

is

not

included

in

the

latest

measurement

report

(cell

weakens

fast),

theaddition/replacement

for

that

cell

is

not

started

anymoreIf

E1C

is

transformed

to

E1B

(E1C

triggered

by

a

weak

cell),

the

deletion

is

not

done

if

it

will

require

aHSPA

SCC

to

be

performed

(this

will

allow

the

SCC

to

be

done

separa

y

,

and

then

start

thenext

ASU

based

on

fresh

measurement

reports)Aim

to

provide

better

handling

of

ASU

and

faster

SCC

for

fast

moving

UE,

which

in

turn

reduces

dropcall

and

improves

throughput23?

NokiaNetworks

2011Dept.

/

Author

/

DateRNCRRC:

RB

RECONF

(Change

of

serving

cell)UEBTSSCC

is

triggeredNBAP:

RL

RECONF

PREPARE

(Change

of

serving

cell)NBAP:

RL

RECONFRESPONSEUERNCBTSSCC

is

triggeredNBAP:

RL

RECONF

PREPARE(Change

of

serving

cell)NBAP:

RL

RECONF

RESPONSEInitial

Benefit

Evaluation

of

change

1

&

2:Faster

Completionof

SCurrent

implementation:rocedureand

ReducedATONew

implementation:RRC:

RB

RECONF

‘Delayrestriction

flag’

(Change

of

serving

cell)RRC:

RB

RECONFCOMPLETENBAP:

RL

RECONFCOMMITRRC:

RBRECONF

COMPLETENBAP:

RL

RECONF

COMMITUE

sends

RB

reconfigurationcomplete

immedia y

afterreceivingRB

reconfigurationDelay

Restriction

Flag

allows

the

use

ofa

shorter

Activation

Time

Offset

hence

reducingtheoverall

timerequired

tomake

SCC.

This

ensures

that

the

UE

use

the

most

suitablecells

fasterand

reduce

the

probability

of

mobility

procedure

.UE

waits

activationtime

to

elapse,

upto

~600

ms24?

NokiaNetworks

2011Delay

Restriction

Flag

is

included

in

25.331

REL

6

and

not

be

used

in

theconditiondescribed

below,

therefore

it

can

not

reduce

the

duration

of

all

SCCs.Reduction

in

SCCduration

(includingNBAP

and

RRC)between

thebeginning

and

theend

of

the

activitycan

be

see

in

thegraph

thereforepossible

impact

of

delayed

NBAP

procedure

is

included.Evaluation

inRNC443

Time

between

HA3

SCCTrigger

and

p25?

NokiaNetworks

2011Prioritisation

of

SCC

and

ASU

over

poweroffsetupdate26?

NokiaNetworks

2011HS-DPCCH

power

offsets

are

updated

when

UE

moves

between

SHO

(2or

3

cells

in

Active

Set)

and

non-SHO

state

(1

cell

in

Active

Set).Current

implementation

uses

Physical

Channel

Reconfiguration

proceduremakes

the

update

immedia y

after

active

set

update,

if

state

changesfrom

SHO

to

non-SHO

or

vice

versa.New

implementation

delays

the

HS-DPCCH

power

offset

updates

bypredefined

wait

time

(3

seconds

currently

used).This

meansSCC

(or

ASU)canbe

triggeredrightafterprevious

ASUiscompleted,

without

waiting

for

the

power

offset

update

procedure

to

becompleted.

Reduction

of

Mobility

Procedure

.Also

power

offset

update

procedure

can

be

combined

with

SCC

(or

otherRB

reconfiguration)

procedure,

if

RB

reconfiguration

procedure

istriggered

during

the

predefined

wait

time.Reduction

in

number

of

Physical

Channel

Reconfiguration.SCC

is

triggered

faster

and

signaling

is

reduced

in

fast

changing

radioenvironment.Dept.

/

Author

/

DateSW

ActivationEvaluationin

RNC443

of

the

reduction

in

numberof

Physical

Channel

ReconfigurationClear

Reduction

in

number

of

RRC

Physical

Channel

Reconfiguration.PhysicalChannel

Reconfiguration

is

also

used

for

Compress

Mode

Activation,CodeOptimisation,

Transitionto

Cell_PCH Decrease

in

number

of

procedure

toupdate

the

Power

Offset

is

larger

than

showed

in

these

slides

possibly

exceeding50%

reduction.27?

NokiaNetworks

2011RRC:

MEASUREMENT

REPORT

(event1a)ASU

is

triggered,

UE

willbe

moved

to

SHO

stateUE

BTS

RNCUE

ishaving

PS

call

on

HSPA,

non-SHO

(1

branch)Current

implementation:

New

implementation:RRC:

ACTIVE

SET

UPDATENBAP:

RL

SETUP

RESPONSENBAP:

RL

SETUP

REQUESTRRC:ACTIVE

SET

UPDATECOMPLETEUERNCBTSUE

ishaving

PS

call

on

HSPA,

non-SHO

(1

branch)RRC:

MEASUREMENT

REPORT

(event1a)ASU

andSCC

istriggered

UEwill

be

moved

to

SHO

stateRRC:

ACTIVE

SET

UPDATENBAP:

RL

SETUP

RESPONSENBAP:

RL

SETUP

REQUESTRRC:ACTIVE

SET

UPDATECOMPLETEBenefitofchange

1,

2

&

3combined:Consecutive

ASU+SCC,

SHO

state

changedRRC:

RB

RECONF

Change

of

serving

cell

Delay

restriction

flag,

power

offset

update~1.3

s

(0.6s+0.3s+0.4s)

faster

serving

cell

change

after

active

set

updateRNC

triggers

HS-DPCCH

poweroffset

updateRRC:

PHYSI