L&S UMTS Training Course

8/11/2019 L&S UMTS Training Course

1/369

Prepared & presented bya r e ra am

11th of February 2004

[email protected] : +49 89 722 38222


2/369

AGENDA


3/369

Agenda - Day 1

Introduction

UTRAN Protocol Architecture

UTRAN Channel Model

UMTS Signalling Model

Call Flow

oom ng n o anne s

Logical Channels Mapped in to Transport Channels

Transport Channels Mapped in to Physical Channels

?


4/369

Agenda - Day 2

Ph sical Channel : Ke conce t in the UMTS

Radio channel configuration

Cell search, selection and reselection

Handover

Power control

esource a oca on

Congestion control

Radio bearer control

Restriction control


5/369

Agenda - Day 3

Messa es Flow Anal s is

Siemens UMTS System

RNC Model and Capacity

Connection Admission Control

AAL2 Ownership-CID Allocation

a e ec on an oa a anc ng

VP Shaping

Circuit Emulation Services

?


6/369

PART 1


7/369

Objective of Course is to enable testers to

intelligently use Siemens UMTS UTRAN

and associated simulators and erform L&Stest cases

The intention is to provide some insight intothe theor of o eration as well as hands on

experience.

I first present set of concepts to provide

intellectual context before detailed resentation


8/369

Instructor and Background

Gabriel Abraham

.


9/369


10/369

e story o a a

This is a REVIEW.I was told that

backgrounds.sorry

Butit is good to think about the various

steps a mobile has to go through before

discussin lower level details.


11/369

.

will be discussing them at great length, literately.

---

Each step makes use of the right kind or combination of


12/369

1 .1 M o b i l e O r i g i n a t e d V o i c e C a l l

M o b i le B T S M S CR N C

R R C _ C O N N E C T I O N _ R E Q U E S T (R A C H )

D a t a t r a n sp o r t b e a r e r s y n c

N B A P _ R A D IO _ L IN K _

S E T U P _ R E Q U E S T

N B A P _ R A D IO _ L IN K _S E T U P _ R E S P O N S E

A L C A P D a t a T r a n sp o r t B e a r e r S e t u p

R R C _ C O N N E C T I O N _ S ET U P ( F A C H )

R R C _ C O N N E C T I O N _ S E T U P _ C O M P L E T E ( D C C H )

M o b i l e m o v e s t o

C E L L D C H o r

C E L L F A C H s ta te

C M S ER V IC E R E Q U E ST (D C C H ) 1

R R C _ U E _ C A P A B I L IT Y _ I N F O R M A T I O N (D C C H ) 5

R R C _ U E _ C A P A B I L IT Y _ I N FO R M A T I O N _ C O N F I R M (D C C H )

S E T U P ( D C C H ) 3

C A L L _ P R O C E E D I N G ( D C C H ) 2

N B A P _ R A D IO _ L IN K _R E C O N FIG P R EP A RE

_ _

C M _ S E R V I C E _ A C C E P T (D C C H ) 2

B S S M A P _ A S S I G N M E N T _

R E Q U E S T


R E C O N FIG R E A D Y


A L C A P D a t a T r a n sp o r t B e a r e r S e t u p

D a t a t r a n s p o r t b e a r e r s y n c

B S S M A P _ A S S I G N M E N T _ C O M P L E T E

_ _ _R E C O N FIG C O M M I T

R R C _ R A D I O _ B E A R E R _ S E T U P ( D C C H )

R R C _ R A D I O _ B E A R E R _ S E T U P _ C O M P L E T E ( D C C H )

A L E R T I N G ( D C C H ) 2, 4

N o te s :

C O N N E C T (D C C H )

C O N N E C T _ A C K N O W L E D G E (D C C H 3

A p p l y n e w t r a n s p o r t f o r m a t s e t N o w r e q u i r e c o - o r d i n a t e d s e to f 3 x D C H f o r A M R a n d s e p a r a te D C H ( w i th s e v e r a l l o g ic a l

D C C H s ) f o r R L C . )

M o b i le m o v e s t o

C E L L D C H s ta te

_ _ . . .i n t e r fa c e a s a D T A P m e s s a g e . C M s e r v i c e ty p e = M o b i l e O r i g i n a t in g C a l l E s t a b l i sh m e n t . E r r o r ! R e f e r e n c e s o u r c e n o t f o u n d . S e c t i o n1 0 . 5 . 3 . 3 .

2 T r a n sf er re d o v e r R R C a s a D O W N L I N K _ D IR E C T _ T R A N S F E R (E r r o r ! R e f e r e n c e s o u r c e n o t f o u n d . S e c t i o n 8 . 1 . 9 ) a n d t h e n I u i n t e rf a c ea s a D T A P m e s s ag e .

3 T r a n sf er re d o v e r R R C a s a n U P L I N K _ D IR E C T _ T R A N S F E R ( E r r o r ! R e f e r e n c e s o u r c e n o t f o u n d . S e c t i o n 8 . 1 . 1 0 ) a n d t h e n I u i n t e r f a c e a sa D T A P m e s sa g e .

4 A L E R T I N G i s a sy n c h r o n o u s an d m a y o c c u r an y t im e b e t w e e n C A L L _ P R O C E E D I N G a n d C O N N E C T , o r p o te n t ia l ly n o t a t a l l t h o u g h th a tw o u l d b e u n u s u a l o n a v o i c e c a l l. R N C s h o u l d a l lo w f o r t h i s m e s s a g e a t a n y t im e . It d o e s n o t n e e d t o b e s ta t e b a s e d .


13/369


14/369

UTRAN Access Model (3G TS 25.301section 5.1)

Non-Access Stratum

GC Nt DC GC Nt DC

Relay

GC Nt DC GC Nt DC

RRC RRC

bearer bearer

Access Stratum

Uu Stratum Iu Stratum

RLC / MAC /PHY RLC / MAC /PHY

UE UTRAN CN

Uu i/f Iu i/f


15/369

Protocol stack

Upper layer Transmitted between UE and CN

RANAPRRCRRC protocol

MTP3b

MAC

AAL5AAL2AAL2L1

ATMATM

L1

ATM

PHYPHYPHY

UE Node B RNC


16/369

UTRAN Channel Model

MM

CC

GMM

SM

MM

CC

GMM

SM

[NAS] Higher Layer

RRC [AS] Higher Layer RRC

MAC

RLC

Transport Channel

Logical Channel

MAC

RLC

PHY Physical Channel PHY

UE

Um i/f

Node B RNC

Iub i/f Iu i/f

CN


17/369

WCDMA radio interface protocol

Radio Resource Control(RRC)NetworkLayerL3

Radio Link Control(RLC)

Logicalchannel

DataLinkLayer

Medium Access Control(MAC)

L2

TransportchannelPhysical

Layer

L1


18/369

Establishment, maintenance and

release of an RRC connection

between the UE and UTRAN,

UMTS - Access Stratum

Gc Nt DC

L3

Control PlaneSignaling

ser ane

Information

Establishment, reconfiguration

and release of Radio Access

Bearers,

Routing of higher layer PDUs,BCFE

Routing Function Entity (RFE)

PNFE DCFE

RRC PDCP

TR UM

Transfer Mode Entity (TME) UE measurement reporting and

Outer loop power control,

Initial cell selection and re-

selection in idle modeAM

CRLCError Control, Segmentation & Re-

assembly, In-sequence delivery of

higher layer PDU, Physical Link

Control, Ciphering.

BMC

Ciphering,

Header

Ciphering,

Error Ctrl

Header

L2RLC

Mapping between logical channels

& transport channels, Selection of

appropriate Transport Format for

each Transport Channel depending

Logical

ChannelsCMAC

BCCH PCCH DCCH CCCH CTCH DTCH

on ns an aneous source ra e,

Multiplexing, De-multiplexing

of higher layer PDUs, Dynamic

Transport Channeltype switching.

Transport

-

MACC/shMAC-p

BCH PCH CPCH RACH FACH DCH

-

Error Correction, Measurement

& indication to higher layer,

Multiplexing of transport

channels, De-multiplexing ofAMRCPHY Ph sical La er

Channel Config UE Control Cell search, NW sync

channels & mapping of the

channels on physical channels,Synchronization & Power Ctr

L1Channel Control

Measurement

PC, DTX, L1 sync

Meas ctr, routing


19/369

Radio channel structure

Physical Channel

o e

UE

ranspor anne

Logical Channel

RNC


20/369


21/369


22/369

o e s owere

Needs to find and lock onto a cell

transmittersynchronize for timing/framing Needs to download the local system common parameters

which are used to later listen for control/paging/originating


23/369


24/369

o e tarts to r g nate

Mobile tells system using common channel that it would

like to make a call. UE to RNC using the Access Stratum. RNC sets up a dedicated channel between UE and

MSC using the Access Stratum

UE and MSC get connected directly so they can talk toeach other using the Non Access Stratum.


25/369

Mobile sets up Call with MSC

gna ng over e ca e c anne

Call processing code (NAS) in UE talksdirectly with peer in MSC

Sends information such as: called art ,type of call desired, etc. over dedicated

.


26/369

MSC does its job

MSC does digit analysis, uses HLR/VLR to screen, etc.

MSC sets up a voice path to destination, including

vocoders as needed, including path out via E1s etc.

MSC then tells Mobile that Call is proceeding butdoesnt cut voice path resources through yet.

If voice path is allocated successfully, MSC tells UE to

alert (ring)


27/369


28/369


29/369


30/369

Zooming In: Channels

This set of actions takes place using a variety of tailor

specific use they will be put to.again, to be very efficient

with scarce radio time and channel s ace.

UMTS terminology is a bit complex, but makes sense after

Logical Channels; Transport Channels; Physical Channels

These are mapped from top down, and UMTS allows a fair

amount o ex tywe w scuss eac case n eta .


31/369


32/369

RLC L T t M d


33/369

RLC Layer Transparent Mode

R adio Interface (Uu)UE/UTRAN UTRAN/UE

TM-SAP TM-SAP

Transmitting

TM- RLC

entityTransmission

buffer

Receiving

TM- RLC

entity Reassembly

Segmentation

Reception

buffer

CC CH/DCCH/DTCH/SHCC H UE

BC CH/PCCH/DCC H/DTCH UTRAN

CC CH/DCCH/DTCH/SHCC H UTRAN

BC CH/PCCH/DCC H/DTCH UE

RLC La er Unackno ledged Mode


34/369

RLC Layer Unacknowledged Mode

U M - S A P U M - S A P

R ad i o In t e r face (U u )U E / U T R A N U T R A N / U E

Transmi t t inT ran s mi s s i o n Receiv ing

g

U M R L C

ent i ty

b u ffer U M R L C

ent i ty

S e g m e n t a ti o n &

C o n c a t e n a t i o n

R e m o ve R L C

h ead e r

R e c e p t i o n

b u ffer

C i h erin

A d d R L C h e a d e r

D ec i p h e r i n g

D C C H / D T C H U E D C C H / D T C H U T R A N

RLC Layer Acknowledged Mode


35/369

U E / U T R A N

RLC Layer Acknowledged Mode

A M - S A P

R L C C o n t ro l U n i t

A M R L C e n t it y

S e g m e n t a ti o n / C o n c a te n a t i o n

A d d R L C h e a d e r

P i b a c k e d s t a t u s

R e t r a n s m i s s i o n

b u f f e r &

m a n a g e m e n tReceiv

ackno

R e a s s e m b l y

O p t io n a l

T r a n s m i s s i o n

M U X

dledge

ments

R e c e p t io n b u f f e r

R e m o v e R L C h e a d e r & E x t r a c t

P i g g y b a c k e d in f o r m a t i o n

b u f f e r

S e t f i e l d s i n P D U H e a d e r ( e .g . s e t p o l l

b i t s ) & p i g g y b a c k e d S T A T U S P D U

& R e t r a n s m i s s i o n

m a n a g e m e n t

D e c i p h e r in g

D e m u x / R o u t in g

R e c e iv i n g s id e

C i p h e r i n g ( o n l y fo r A M D P D U )

T r a n s m i t ti n g s i d e

D C C H /

D T C H *

D C C H /

D T C H * *

D C C H /

D T C H * *

D C C H /

D T C H *

D C C H /

D T C H * *

D C C H /

D T C H * *


36/369

MAC header structure while lo ical channels are ma ed to trans ort channels

BCCHPCCH CCCH Logical

Channels

DCCH DTCHCTCH

No Multiplexing

With Multiplexing

MAC SDU

C/T MAC SDU

MAC SDUMAC SDU MAC SDUTCTFTCTF MAC SDU

MAC SDUUE-id Type UE-id

- -

No Multiplexing

With MultiplexingMAC SDUTCTF

UE-id Type MAC SDUC/TTCTF UE-id

DCHCPCHBCHPCH Transport

Channels

FACH RACH


37/369


38/369


39/369


40/369


41/369


42/369

SRNC function


43/369

Node

CN

Iu user

data link

SRNC

NodeB

Iu signaling link


44/369


45/369

Radio Bearers


46/369

Overall Algorithm Relations for Radio Bearer Control and Translation


47/369

UE is switched to the lowest rate regardless of the current RLC buffer status

SRNCCRNC

Translates the RAB QoS parametersinto an initial radio configuration

RB AdmissionProtocol RRC Request

RAB Re uest

Setup/Reconf

Admission

Response

Configure

Activate Congestion

RadioBearer

Congestion

Measurement

Control CongestionIndication

Activate

Deactivate

n ca on

Control

Traffic VolumeMeasurements

- BRA on DTCH

RLC buffer load UE/RNC> Sintrasearch else

hcs_prionhcs_prios Squal


163/369

Hn

= Qmeas,n

- Qhcsn

- TEMP_OFFSETn

W(PENALTY_TIMEN

Tn

)

if HCS_PRIOn HCS_PRIOs(Trigger: Qmeas,n > Qhcsn )

Quality Measure Q:

Qmeas,n = CPICH RSCP / RxLev

Qmeas,n = CPICH Ec/No

if HCS_PRIOn = HCS_PRIOs

an ng o ce s:an ng o ce s:

Rs = Qmeas,s + QhystS

meas,n meas,s s,n


164/369

Rn = Qmeas,n Qoffsets,n - TEMP_OFFSETn * W(PENALTY_TIMEn Tn )

Re-selected cell : Suitable (S > 0)

Hi hest HCS PRIO if H > 0 *_Best Ranked (Highest R)

*) in high mobility state neighbor cells with lower prior ities are selected

Quality MeasureQmeas,n = CPICH RSCP / RxLev Qhyst1ss,n & Qoffset1ss,nQ = CPICH Ec/No Qhyst2s & Qoffset2s, , ,

Load overflow mechanism

RF2


165/369

Overflow

RF1

Cell with High load

Load balancing mechanism

RF2 RF2 RF2

Cell2 balanced load

Cell2 balanced load

Cell2 balanced load


166/369

RF1 RF1 RF1

Cell1 balanced load Cell1 balanced load Cell1 balanced load

NodeB1 NodeB2 NodeB3


167/369

Power onOverall selection process

PLMN Selection

and Reselection

PLMN

F1PLMNselected

PLMNavailable

F1

NRN


168/369

Registrationresponse Cell selection

and

C

Location registration

Registration


169/369

RRC idle and connected mode

RRC service state

Idle ModeCell selection Cam in F1

on a cell RRC connection request

R

C


170/369

RRC connection set up

CellDCH

Cell FACH

ConnectedMode

Cell URA

Initial cell selection

Cell 1Cell 4

S t i f ti


171/369

System information:-PLMN identity-Cell information-

Cell 2

Cell 3

Candidate List: :- Cell Information:Carrier frequency,Scrambling code,etc- Neighboring cells:

Cell 1,cell 3,cell 4Cell 4

New PLMN Selection

NoYes

Idle mode cell selectionand reselection

InitialCell Selection

Storedinformation

Cell Selection No suitable cellfound

Storedinformation

Camped normally

Suitable cellfound

Suitable cellfound

Suitable cellfound

trigger


172/369

Cell ReselectionNo suitable cell

found

Connectedmode

found

eva ua on

No USIMNo suitable cell

found

USIM inserted

Acceptable cellfound

Camped on any cellSuitable cellfound

Connectedmode

Acceptable cellfound

trigger

Cell Reselectionevaluation

No Acceptable cellfound

(EC calls only)

Cell search

Slot Synchronization

(P-SCH)

Frame Synchronization

(S SCH)

(8 sc)


173/369

(S-SCH)

Scrambling code

groupSCGi

(8 sc)512sc

Scrambling Code

Identification

(CPICH)

Scrambling codeSC

Parameter name parameter Sector / Cell value

1 0timing offset of the t_cell

Cell synchronization

2 256

3 512

P-SCH power offset po_psch Urban -3dB

cell

P(t)

CPICH

S-SCH power offset po_ssch urban -3dB

SCH1SCH2 SCH3


174/369

SCH2 SCH3

t

SCH1 SCH

se m ng= se m ng=

SCH3 Sector3

Sector2Sector

1

Cell selection criterion: S

ce s su a e u s

u a e ce s:u a e ce s:

FDD cells: Srxlev > 0 AND Squal > 0 Squal => CPICH EC/N0


175/369

FDD cells: Srxlev > 0 AND Squal > 0GSM cells: Srxlev > 0

Squal => CPICH EC/N0

Srxlev => CPICH RSCP

S ual = Q Q ualminSrxlev = Qrxlevmeas - Qrxlevmin Pcompensation *)

*) Pcompensation = max(UE_TXPWR_MAX_RACH - P_MAX, 0)

easuremen o ne g or ce s:easuremen o ne g or ce s:

n ra- requency: qua = intrasearch


176/369

Sintrasearch is not sent

Inter-Frequency: Squal


177/369

R Q , Qoffset ,,

Re-selected cell: Suitable (S Criterion)

Best Rank(Highest R)

Qmeas,s / Qmeas,n = CPICH RSCP / RxLev Qhyst1ss,n & Qoffset1ss,nQmeas,s / Qmeas,n = CPICH Ec/No Qhyst2ss,n & Qoffset2ss,n

FDD: Cell iub csrqm = rscp cell iub qhyst1s & cell aci qoffset1

=


178/369

Radio Channel Configuration


179/369

Radio Channel Configuration

Radio interface channels

Upper LayersULDL

RLC

Logical channelCC

H

CC

H

CC

H

CC

H

TC

H

CC

CH

DC

CH

DT

CH


180/369

MAC

Transport channel

BC

H

FAC

H

PC

H

RA

D

C

DC

H

PHY

H

P-CCPCH

S-CCPCH

CP

ICH

AICH

PICH

S

CH

DP

CH

D

PCCH

P

RACH

D

PDCH

Air interface

Physical Channel

Transport Channel Physical channels

UL Physical Channel DL Physical Channel

DedicatedChannel

Common Channel DedicatedChannel

Common Channel

DedicatedPh i l D t

PhysicalR d

DedicatedPh i l

Common ControlPh i l Ch l


181/369

Physical DataChannel

RandomAccess

PhysicalChannel

Physical Channel(CCPCH)

Channel(PRACH)

Dedicated

Physical Control

SynchronizationChannel

SCHChannel(DPCCH) Common Pilot

Channel(CPICH)

Paging IndicatorChannel

(PICH)

Acquisi tion IndicationChannel

(AICH)

Common and dedicated physical channel configuration

, ~

Data1

Ndata1 bits

TPC

NTPC bits

TFCI

NTFCI bits

Data2

Ndata2 bits

Pilot

Npilot bitsDPCH

DL

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 014


182/369

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 014

1 TS, 2560 chips,10 bits

Pilot

Npilot bits

Transmission PowerControl

(TPC) NTPC bits

FeedbackInformation

(FBI)NFBI bits

Transmission FormatCombination Indicator(TFCI)NTFCI bits

DPCCH

User dataNdata=10x2k (k=0~6)DPDCH


183/369


184/369


185/369

MAC layer Transport channelconfiguration

UL Channel DL Channel

DedicatedChannel

CommonChannel

DedicatedChannel

CommonChannel

DedicatedChannel

RandomA

DedicatedChannel

Broadcast Channel(BCH)


186/369

(DCH)AccessChannel

(DCH)

Transport Channel

(RACH)Forward Access

Channel(FACH)

Common

Paging Channel(PCH)

Packet Channel(CPCH)

Downlink SharedChannel(DSCH)

Physical Channel


187/369

Outline for commands for common channels

Physicalchannels

Cell channel parameters

P-CPICH P-SCH P-CCPCHS-SCH S-CCPCH PICH PRACH AICH


188/369

cell iub dlcc ulcc

BCH PCHFACH RACHTransportchannels

Definition of UL and DL frequency

cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarfcn=9862,10812

max_dltp=43 t_cell=0 sac=0 rac=10 lac=42 nwom=md2 atdt=mnd

tmr cs u=0 t312=10 n312=1 t313=3 n313=50 n315=1 id ura=1 t cu=5_ _t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=0.0 po_psch=-

3 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3 dclc_utran=7

qqualm=-24 poffset=20 pwval_max=7 t316=30 t317=30 ifc_rslct=nalwd

t br=10 h st1s=4 h st2s=4 maut=24 rxlevmin=-115 cio= 0.0 t300=3000_

n300=2 t309=5 t314=12 t315=180 sac_cbs=0 fach_moclc=5

interrat_mind=false iffdd_mind=true


189/369

... ...

200 kHz Fcentre = UARFCN * 200 kHz

- = centre z

DL physical channel data: command format example

cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarcfn=9862,10812

max_dltp=43 t_cell=0 sac=0 rac=10 lac=42 nwom=md2 atdt=mndtmr_cspu=0 t312=10 n312=1 t313=3 n313=50 n315=1 id_ura=1 tpcu=5

t302 4000 302 3 t307 30 i 2 it 33 b h 0 0


190/369

t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=0.0

po_psch=-3 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3

dclc_utran=7 qqualm=-24 poffset=20 pwval_max=7 t316=30 t317=30

ifc_rslct=nalwd t_br=10 qhyst1s=4 qhyst2s=4 maut=24 qrxlevmin=-115 cio=

0.0 t300=3000 n300=2 t309=5 t314=12 t315=180 sac_cbs=0 fach_moclc=5

interrat_mind=false iffdd_mind=true

Transport channel multiplexing

Carrying PCH/FACH

multiplexing(Type2)

Carrying FACH multiplexing

(Type1)

Carrying PCH

(Type0)

S-CCPCH PICHS-CCPCHS-CCPCH PICH


191/369

PCHFACH

FACH

FACHFACHPCH

Command format example

_ _ _ - _ - -sccpch_scd=0


192/369

cre dlcc cellid=10 nodebid=0 id_cch=0 ccho_type=0 po_pch=-3 po_pich=-6 sccpch_scd=0

cre dlcc cellid=10 nodebid=0 id_cch=1 ccho_type=1 mfachp=0 sccpch_scd=0

Command format example

cre ulcc cellid=10 nodebid=0 id_cch=0 sc_wno=0avsgn=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 po_aich=5


193/369

DCH UL Scrambling code

Bit 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

UL Scrambl ing Code


194/369

SC RNC S-RNTI

Command format example: UL scrambling code per RNC

cre rnc rncid=14 mcc=454 mnc=03 a2ea_idi=85263349005

a2ea_dsp=0000000000000000000000 opc=11171 udpp_rnc=2152

ud s sn=2152 nwind s=2 d c s=11140 drxclc s=7_ _ _ _

nwind_cs=2 dpc_cs=11122 drxclc_cs=7 sc_rnc=1 cnodei=false

type_ldc=none opue_ibase=000000000 opue_iofs=0 ho_psrrh=hotr

tmr iubhc=60 ipadr cbc=000 000 000 000


195/369

tmr_iubhc=60 ipadr_cbc=000.000.000.000

Restriction control


196/369

Restriction Control

Restriction control is a feature that will enhance network, ,

maintenance and resource management.

There are two types of restriction control, automatic and


197/369

.

Automatic restriction control is applied by the RNC, byrefusing new requests for servicing when its CPUs are

.

Manual restriction is applied by the OMC/LMT bychanging the office data or issuing a command to the RNC

Measurement of CPU load

For the duration of its uptime, the RNC shall monitor the load of its

CPU(s)

The load is measured as a percentage of the maximum possible load (=100%)


198/369

It is assumed that the basic period is 10 seconds. NumPeriods forautomatic restriction control has to be set to 1 (because any delay inapplying restriction may have hazardous effects on the RNC)

The RNC will perform the actions only for the CPUs that areoverloaded and not for the whole of the RNC

If a CPU that has an RNC-wide role (like the RMP processor) isoverloaded, then restriction shall be applied to all CPUs of the RNC


199/369

Automatic Restriction Control Command Format

xamp e:

- Command format:cre rsta thr1=80 thr_rs1=75 thr2=92 thr_rs2=89 rr2=90 rr1=50

cgc=01 peri=6

- Two severit ies: (1 & 2) are applied:


200/369

Basic period = 10 s Supervision period = multiple of 10 s

Automatic Restriction due to processor overload

xamp e:

- Command format:cre rsta thr1=80 thr_rs1=75 thr2=92 thr_rs2=89 rr1=50 rr2=90

cgc=01 peri=6

Restricted:

- incoming RRC connection requests

- incoming URA updates

- incoming Cell updates

- CTS (FACH to DCH)

- Radio Link setup

- RL addition

-


201/369

- Paging requests from the SRNC

:

- incoming RRC connection requests

- incoming URA updates

- incoming Cell updates

- CTS (FACH to DCH)

Restriction control Restrict ion level =2 (20%)

xamp e:

- restriction control with pre-defined patterns

cre rstm kind=perset peri=6

cre rstm kind=acccls accrst l=2 cellid=10

-

- e.g. 20 % restriction

AC 1 2 3 4 5 6 7 8 9 10 1 2 3 . . .

15 . . .

14 . . .

pstn


202/369

. . .

12 . . .

11 . . .

10 . . .

. . .8 . . .

7 . . .

6 . . .

5 . . .

4 . . .

3 . . .

2 . . .1 . . .

0 . . .

0 60 120 180 240 300 360 420 480 540 600 660 720 . . .time [s]

Manual Restrict ion with self defined Patterns

= =

Example:

Command format

ptn1=1111111111000100

ptn2=1111111111000100

:

tn10=0111111111000000

restriction control with self-defined patterns cre rstm kind=perset peri=6

cre rstm kind=acccls accrstl=3 cellid=11


203/369


204/369

Cell related Procedures


205/369

System Information Modification

Cell Setup Request

Cell Setup (3G TS 25.433)

Cell Setup Response

Common Transport Channel Setup Request

Initialisation of

P-SCH, S-SCH

P-CPICH, S-CPICH

P-CCPCH (BCH)

, ,

Common Transport Channel Setup Response

Initialisation of

S-CCPCH

ALCAP Data Transport Bearer Setup


PRACH, AICH


I iti li ti f PRACH


206/369



Initialisation of PRACH


, - , -

Initialisation of PCPCH


using Common Transport

System Information Update Request

System Information Update Response

Transmitting of System

Information on BCCH

(same VPI-VCI is used)

RNCNode B IubUuUE

Audit (3G TS 25.433)

Audit Required

er o e rese or

to indicate possible misalignment of

State or Configuration Parameter.

In response to Audit Required orAudit Request to re-sync the Status of logical resources

and Configuration Parameter.

Audit Response


207/369

Node B information

Cell InformationCommon Channel Information

Communication Control Port Information

Local Cell Information

Audit Response

RNCNode B Iub

Modification of System Information (3G TS 25.331)

Update of System

Information

ys em n orma on p a e eques


Transmitting of new System

Information on BCH:BCCH

and FACH:BCCH

CCCH:PCH

Indication towards UE in Idle

Mode, CELL_PCH, URA_PCH

Paging Type 1


208/369

g g yp

MIB Value Tag

RNCNode B IubUuUE

Time Critical Modification of System Information (3G TS 25.331)

Update of System

Information


BCCH Modification Time

Transmitting of new System

Information on BCH:BCCH and

FACH:BCCH at specified time

FACH:BCCHIndication towards UE in

CELL_FACH state

System Information Change Indication


209/369

CCCH:PCH

Indication towards UE in Idle

Mode, CELL_PCH, URA_PCH

MIB Value TagBCCH Modification Time

Paging Type 1

MIB Value TagBCCH Modification Time

RNCNode B IubUuUE

-

Call related Procedures


210/369

RRC and NBAP Dedicated

easurement ontro

Measurement Control


211/369

RRC Measurement Control (3G TS 25.331)

RRC Measurement Control

Comnand: start

Reference, Type, Quantity

Report: Mode = periodi cal

Criteria = amount or interval

RRC Measurement Report

T interval

T interval


RRC Measurement Control

omman : mo y

Reference, Type, Quantity

R t M d t


212/369

Report: Mode = event

Criteria=Time to triggerEvent = true


r gger

Command: release

RNCNode B IubUuUE

NBAP Measurement Reporting (3G TS 25.331)

Measurement Initiation Request

Node B Communication Contect ID

DedicatedCommon

Measurement Procedures

Measurement Initiation Res onse

Dedicated Measurement Object Type ID [RL, RLS, DPCH]

Report Characteristics [On-Demand, Periodic Event x]

additional Parameter [Thrshold, Hysteresis, Requested Time]

Filter Coefficient

Measurement Reporting


213/369

Measurement Reporting

Measurement Termination Request

Measurement Termination Response

RNCNode B Iub

UE Capability


214/369

UE Capability Update after RRC Connection Establishment (3G TS 25.331)

UE Capability Update Requirement = true

System Information 13

UE Capability InformationT 304

V304

RRC Connection Establishment

UE Capability Information Confirm

Radio Access Capability:ICS Version, PDCP, RLC, TrCH,

RF, PhCh, RAT, security, LCS and

MeasurementUE System Specific Capability:

Inter-System Classmark


215/369

CNRNCNode B IuIubUuUE

UE Capability Update during Handover towards GSM (3G TS 25.331, 25.413)

UE Capability Update Requirement = true


RRC Connection

UE Capability Information

UE Capability Information

Confirm

T 304

V304

Radio Access Capability:

ICS Version, PDCP, RLC, TrCH,

RF, PhCh, RAT, security, LCS,


Inter-System Classmark

NAS Connection Establishment


216/369

NAS Connection Establishment

Relocation Required

Classmark 2

Classmark 3 an over eques

Classmark 2

Classmark 3

CNRNCNode B IuIubUuUE BSSA

UE Capability Enquiry (3G TS 25.331)

RRC and/or NAS Connection Connection Establishment

UE Capability Enquiry

UE Capability InformationT 304V304

UE Capability Information Confirm

Radio Access Capability:


217/369

ICS Version, PDCP, RLC, TrCH,

RF, PhCh, RAT, security, LCS and


n er- ys em assmar


3G UMTS

circuit switchedoca on p a e roce ures


218/369

p

Timer

PM Counter

Normal Location Update (3G TS 25.931)


CR: Initial UE Message ((Loc Update Req)Initial Direct Transfer (Loc Update Req)

Cause: normal Location update

CC

MM Procedures (Authentication, Identification, Ciphering)


219/369

DT1: Direct Transfer ((Loc Update Accept)DL Direct Transfer ((Loc Update Acc)

Release initiated by the Network


Periodic Location Update (3G TS 24.008, 25.331, 25.931)

UE Switch on


ys em n orma on

T3212


MM Procedures Authentication Identification Ci herin

CC

DT1: Direct Transfer ((Loc Update Accept)DL Direct Transfer ((Loc Update Acc)

Release initiated by the Network

, ,


T3212


220/369

T3212

Expiry

T3212



Cause: periodic Location update

CC


circuit switched

Call Handling Procedures


221/369

Timer, PM Counter


222/369

Mobile Originated Call (3GPP TS 25.931)

onnec on s a s men

CR: Initial UE Message (CM Service Req)Initial Direct Transfer (CM Service Req)

MO Cause

MM Procedures (Authentication, Identification, Ciphering)

CC: DT1: Direct Transfer (Service Accept)DL Direct Transfer (Service Accept)

DT1 : Direct Transfer (Call Proceeding)DL Direct Transfer (Call Proceeding)

UL Direct Transfer (Setup) DT1 : Direct Transfer (Setup)

RB, RAB Establishment

DT1 Di t T f (Al ti )DL Di t T f (Al ti )


223/369

DT1 : Direct Transfer (Connect)DL Direct Transfer (Connect)

DT1 : Direct Transfer (Alerting)DL Direct Transfer (Alerting)

UL Direct Transfer (Connect Ack)

Ongoing Mobile - Network Call carry dedicated resources (e.g. AMR)

DT1 : Direct Transfer (Connect Ack)

Call Release initiated by the Network or Mobile


Network Initiated Call Release (3G TS 25.931)

RRC RANAP

NAS NAS

SCCP

DT1 : Direct Transfer (Release)DL Direct Transfer (Release)

DT1 : Direct Transfer (Release Complete)UL Direct Transfer (Release Complete)

Connection Release of Dedicated Channel


224/369


Mobile Initiated Call Release (3G TS 25.931)

RRC RANAP

NAS NAS

SCCP

DT1 : Direct Transfer (Release Complete)DL Direct Transfer (Release Complete)

DT1 : Direct Transfer (Release)UL Direct Transfer (Release)



225/369


3G-UMTS

packet switcheda an ng roce ures


226/369

Timer, PM Counter

Mobile Initiated Data Transfer


227/369

Pa in for UE in Idle or Connected Mode

Network initiated Data Transfer (3GPP TS 23.060)


CR: Initial UE Message (Paging Response)Initial Direct Transfer (Paging Response)

GMM Procedures (Authentication, Identification, Ciphering)

DT1 : Direct TransferDL Direct Transfer

CC

UL Direct Transfer

(Activate PDP Context Request)

DT1 : Direct Transfer


(Request PDP Context Activation)

(Request PDP Context Activation)




228/369

(Activate PDP Context Accept)(Activate PDP Context Accept)

UE or Network initiated PDP Context Deactivation

Ongoing Network - Mobile Data Transfer

RB, RAB Release

CNRNCNode BUE


Mobile initiated Data Transfer (3GPP TS 23.060)

GMM Procedures (Authentication, Identification, Ciphering)

CR: Initial UE Message (Service Request)Initial Direct Transfer (Service Request)

CC: DT1: Direct Transfer (Service Accept)DL Direct Transfer (Service Accept)


UL Direct Transfer




DT1 : Direct Transfer(Activate PDP Context Accept)

DL Direct Transfer(Activate PDP Context Accept)


229/369

Ongoing Mobile - Network Data Transfer

UE or Network initiated PDP Context Deactivation

,

CNRNCNode BUE


230/369

Network initiated Data Transfer Release (3G TS 25.931)

RRC RANAP

NAS NAS

SCCP


(Deactivate PDP Context Request)

DL Direct Transfer


DT1 : Direct TransferUL Direct Transfer

eac va e on ex ccepeac va e on ex ccep



231/369

CNRNCNode BUE

Mobile initiated Data Transfer Release (3G TS 25.931)

RRC RANAP

NAS NAS

SCCP




UL Direct Transfer


eac va e on ex ccepeac va e on ex ccep



232/369

CNRNCNode BUE

Service Request Procedures


233/369


234/369

Service Request initiated by MS Procedure having already active PDP Context

(UE requested Re-establishment of RAB's)

PMM-Idle

SM-Active


PMM-Connected

data

Service Request

PMM-Connected

SM-Active

ecur y unc ons


SGSN initiated PDP Context Modification


235/369

Up-Link PDU

RNCNode BUE SGSN HLR

Service Request initiated by Network Procedure not having active PDP Context

(Network requested PDP Context Activation Procedure)

Send Routing Infofor GPRS Response

Send Routing Info

for GPRS Request

Down-Link PDU

PMM-Idle

SM-Inactive

Paging

PDU Notification Response

PDU Notification Request

PMM-Connected

Service Request


- nac ve

Security Functions

Request PDP Context Activation


236/369

T3385

PMM-Connected

SM-Active

PDP Context Activation

RNCNode BUE SGSN HLR GGSN PDN

unsuccessful Network requested PDP Context Activation Procedure

cause = MS GPRS Detached


Down-Link PDUSend Routing Info

for GPRS Request




Failure Report

Response

Failure Report

Request


237/369



cause = IMSI Not Known


Down-Link PDUSend Routing Info

for GPRS Request

cause = IMSI not known



Send Routing Info

for GPRS Response

Send Routing Info

for GPRS Request

Failure Report

Request

If same SGSN address


238/369

Request

Failure ReportResponse



cause = no Paging Response


Send Routing Info

for GPRS Request

Down-Link PDU

PMM-Idle

SM-Inactive

Paging



PDU Notification Reject Request

PDU Notification Reject Response


set MNRG


239/369



cause = UE refuse


Send Routing Info

for GPRS Request

Down-Link PDU

PMM-Idle

SM-Inactive

Paging



PMM-Connected

Service Request


- nac ve

Security Functions

Request PDP Context Activation

T3385


240/369

T3385

Request PDP Context Activation Reject

PDU Notification Reject Request


cause = MS refuse

causes:

#26: insufficient resources

#31: activation rejected (unspecified)#40: feature not supported

#95-111: protocol errors


Service Request initiated by Network Procedure having already active PDP Context

(Network requested Re-establishment of RAB's)

SM-Active

PMM-Connected

Down-Link PDU

Paging

Service Request


Security Functions

PMM-Connected

SM-Active



241/369


Down-Link PDU


Procedures


242/369

PDP Context Activation Procedure (3G TS 23.060)

SM-Inactive

Activate PDP Context Re uest


CAMEL_GPRS_PDP_Context_Establishment

Invoke Trace

Create PDP Context Request

T3380

Activate PDP Context Accept

Create PDP Context Response

CAMEL_GPRS_PDP_Context_Establishment_AcknowledgementSM-Active


243/369

RNCUE SGSN GGSN PDN

IPv6 Stateless Address Auto configuration Procedure (3G TS 23.060)

PDP Context Activation

Router Solicitation

Router Advertisment

GGSN Initiated PDP Context Modification


244/369

RNCUE SGSN GGSN PDN

Secondary PDP Context Activation Procedure (3G TS 23.060)

SM-Active

Activate Secondar PDP Context Re uest



Invoke Trace


T3380



CAMEL_GPRS_PDP_Context_Establishment_Acknowledgement


245/369

RNCUE SGSN GGSN PDN

PDP Context Activation for Non-transparent Access (3G TS 23.060, 29.061)

AT-Commands

-

Activate PDP Context Request

CHAP / PAP Authentication

Configuration Request


Invoke Trace


T3380

PPP-IPCP


Access Request

Access AcceptRADIUS

Discover

Offer

RequestDHCP


246/369



CAMEL_GPRS_PDP_Context_Establishment_AcknowledgementConfiguration Ack

ISP

Itranet

UE MTTE SGSN GGSN PDNRNC

PDP Context Activation with Mobile IP Registration (3G TS 23.060, 29.061)

AT-Commands

-

Activate PDP Context Request

CHAP / PAP Authentication

Configuration Request

PPP-IPCPRB, RAB Establishment

Invoke Trace


T3380




Configuration Ack

_ _ _ on ex _ s a s men _ c now e emen

Agent Advertisement ICMP

Registration Request


247/369



Registration Replay

Registration Replay

MIP

ISP

Itranet

SGSN initiated PDP Context Modification Procedure

UE MTTE SGSN GGSN PDNRNC

Procedures


248/369

UE initiated PDP Context Modification Procedure (3G TS 23.060)

Modify PDP Context Request

Update PDP Context Request

Update PDP Context ResponseT3381


Invoke Trace

Modify PDP Context Accept

CAMEL_GPRS_Change_Of_QoS


249/369

RNCUE SGSN GGSN PDN

SGSN initiated PDP Context Modification Procedure (3G TS 23.060)



Update PDP Context Response


T3386


Invoke Trace



250/369

RNCUE SGSN GGSN PDN

GGSN initiated PDP Context Modification Procedure (3G TS 23.060)



T3386

, s a s men


Invoke Trace

Update PDP Context Response



251/369

RNCUE SGSN GGSN PDN


252/369

UE initiated PDP Context Deactivation Procedure (3G TS 23.060)

Deactivate PDP Context Request

CAMEL_GPRS_PDP_Context_Disconnection

Delete PDP Context Request

Delete PDP Context ResponseT3390

RB, RAB Release

Deactivate PDP Context Accept


253/369

RNCUE SGSN GGSN PDN

RAB Release-Initiated Local PDP Context Modification Procedure (3G TS 23.060)

RB, RAB Release



254/369

RNCUE SGSN GGSN PDN

SGSN initiated PDP Context Deactivation Procedure (3G TS 23.060)



Delete PDP Context Response


RB, RAB Release



255/369

RNCUE SGSN GGSN PDN

GGSN initiated PDP Context Deactivation Procedure (3G TS 23.060)




T3395

, e ease


Delete PDP Context Response


256/369

RNCUE SGSN GGSN PDN

Preservation Procedures


257/369

RAB Release Procedure triggered by UTRAN (3G TS 23.060)

RAB Release Request

RAB Assignment Request

RB Release

data


258/369

RNCUE SGSN GGSN PDN

Iu Release Procedure triggered by UTRAN (3G TS 23.060)

Iu Release Request

Iu Release Command

RB Release

signalling + data


259/369

RNCUE SGSN GGSN PDN


260/369


261/369

GPRS Attach at same RAI/LAI using known P-TMSI (3G TS 23.060)

Attach Request

Authentication

T3310

IMEI Check

Update Location

clear MNRG

Ready For SM Gr

Gr

Note MS

GPRS Present

clear MNRG

SMS Alert Procedure

clear MNRG

Location Update Request

GPRS attach while IMSI attached

Combined GPRS/IMSI attach

Gs

Location Update Accept Gs


262/369

Attach Accept

Attach Complete

TMSI Reallocation Complete

CAMEL_GPRS_ATTACHED

T3350

Gs

RNS sameSGSNUE GGSN HLR sameVLREIRIuUu SMSCGc

GPRS Attach at new RAI/LAI using known P-TMSI (3G TS 23.060)

Attach Request Identification

Request

SEC.AttIdentityReqFromPsgsn

Identification

Response

Authentication

SEC.SuccIdentityReqFromPsgsn

T3310

IMEI CheckUpdate Location

Cancel Location

Cancel Location Acknowledge

Update Location Acknowledge

Insert Subscriber Data Acknowledge

Insert Subscriber Data

oca on p a e eques

Cancel Location

Update Location




s




263/369

Location Update Accept

Update Location

Gs

Attach Accept

Attach Complete


CAMEL_GPRS_ATTACHED

T3350

Gs

RNS newSGSNUE GGSN HLR oldSGSN newVLR oldVLREIRIuUu Gc

GPRS Attach at new RAI/LAI using unknown P-TMSI (3G TS 23.060)

Attach Request Identification

Request

SEC.AttIdentityReqFromPsgsn

Identification

ResponseIdentity Request

Identity Response

Authentication

SEC.SuccIdentityReqFromPsgsn

T3310

IMEI CheckUpdate Location

Cancel Location


Update Location Acknowledge



oca on p a e eques

Cancel Location

Update Location




s




264/369

Location Update Accept

Update Location

Gs

Attach Accept

Attach Complete


CAMEL_GPRS_ATTACHED

T3350

Gs

RNS new SGSNUE GGSN HLR old SGSN new VLR old VLREIRIuUu Gc

Detach Procedures


265/369

UE initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)

Detach Type

GPRS detach only

IMSI detached only

Combined GPRS/IMSI detach

Switch off

Detach Request

T3321

Delete PDP

Contect Request

Delete PDP

Contect Response


IMSI Detach

GPRS Detach

CAMEL_GPRS_Detach

Gs

Detach Accept

If Not Detach Type=switch off

se se se

RB, Iu Release


266/369

Pur e Procedure

RNSUE HLR VLR SGSN GGSN

SGSN initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)

Detach Request

T3322

Delete PDP

Contect Request

Delete PDP

Contect Response

GPRS Detach


CAMEL_GPRS_Detach

Gs

Detach Accept

se se se

RB, Iu Release


267/369

Pur e Procedure


SGSN initiated (implicit) Detach Procedure (3G TS 23.060, 24.008)

, ,

a configuration-dependent time after the mobile reachable timer expired,

or after an irrecoverable radio error causes disconnection of the logical link.

Delete PDP

Contect Request

Delete PDP

Contect Response

GPRS Detach


CAMEL_GPRS_Detach

Gs

se se se


268/369

Pur e Procedure


HLR initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)

Detach Request

T3322

Cancel Location

Delete PDP

Contect Request

Delete PDP

Contect Response

GPRS Detach


CAMEL_GPRS_Detach

Gs

Detach Accept

se se se


RB, Iu Release


269/369

Pur e Procedure



270/369

Purge Procedure (3G TS 23.060, 24.008)

the MM and PDP contexts of a detached MS.

The SGSN may, as an implementation option, delete the MM and PDP contexts

of an MS immediately after the implicit or explicit detach of the MS.

Alternatively, the SGSN may keep for some time the MM and PDP contexts and

the authentication triplets of the detached MS, so that the contexts can be reused at a

later GPRS attach without accessing the HLR.

urge

Purge MS Acknowledge

set MS_Purged_for_GPRS


271/369


Security Procedures


272/369

P-TMSI Reallocation (3G TS 23.060, 33.102)

P-TMSI Reallocation Command

P-TMSI Reallocation Complete


273/369

RNSUE EIR SGSN


274/369


275/369

IMEI Identification (3G TS 23.060, 33.102)

Identity Request

SEC.AttIdentityReqImsi

T3370

Identity Response

Check IMEI Request

IMEI or IMEISV SEC.SuccIdentityRequest

Check IMEI Response


276/369

RNSUE EIR SGSN Gf


277/369

Handover Procedures

Flow Charts, Timer, PM Counter


278/369

, ,

Soft Handover

ranc on

Branch Deletion

Branch Addition & Deletion simultaneously


279/369

Soft Handover: Radio Link Addition (3G TS 25.331, 25.433)

Radio Link Addition RequestRadio Link Setup Request

RNSAPNBAP

Radio Link Addition Res onse

Radio Link Setup Response

ALCAP Data Transport Bearer

Setup

.


SHO.SuccRLAddUTRANSide

SHO.FailRLAddUTRANSide

Setup

DCCH RRC

c ve e p a e: n on

Active Set Update Complete

SHO.AttRLAddUESide


280/369

SHO.SuccRLAddUESide

servingdriftdrift

SHO.FailRLAddUESide.Cause

sRNCdRNCdNodeB IurIubUuUE

Soft Handover: Radio Link Deletion (3G TS 25.331, 25.433)

Active Set Update: Link Deletion

DCCHRRC


SHO.AttRLDelUESide

SHO.SuccRLDelUESide

Radio Link Deletion RequestRadio Link Deletion Request

NBAP

SHO.AttRLDelUTRANSide

Radio Link Deletion Response



Release


Release

SHO.SuccRLDelUTRANSide


281/369

servingdriftdriftsRNCdRNCdNodeB IurIubUuUE

Radio Link Addition Request

Soft Handover: Radio Link Addition and Deletion simultaneously (3G TS 25.331, 25.433)

a o n e up eques



Setup


Setup

Start RX

DCCH

Downlink Synchronization

Uplink Synchronization

Start TX

Active Set Update: Link Deletion/ Addition


Deactivate old DL branch

Activate new DL branch

Radio Link Deletion Request



282/369


Release

servingdriftdrift servingsRNCdRNCdNodeBUu sNodeBUE

Backward Hard Handover

con ro e

CN controlled


283/369

Radio Link Setup RequestRadio Link Setup Request

Hard Handover via Iur-i/f (3GTS 25.331)




Setup

Ph sical Channel Reconfi uration

DCCH

ALCAP Data Transport BearerSetup

Physical Channel Reconfiguration Complete




a o n e e on esponse

ALCAP Data Transport BearerRelease


284/369

Release

servingtargettarget sourcesourcesRNCRNCNode B RNCNode BUE


285/369

Hard Handover cases (3G TS 25.331)

serv ngsourcearge

Soft HO

Hard HO

sourcetarget

Hard HO

tragetsource

Soft HO

Hard HO


286/369

RNCRNC RNC

Relocation RequiredTrelocprep

Hard Handover with switching in the CN: UE connected to two CN nodes (3G TS 25.331)

Relocation Request

Treloccalloc Treloccalloc

Radio Link Setup Request


Relocation Request Acknowledge



Setup

Physical Channel Reconfiguration

DCCH

Relocation Command

Relocation Detect

TreloccomplTreloccomplTrelocoverall


Radio Link Failure Indication

Relocation Complete

IU Release Command

Release Complete

Radio Link Deletion



287/369

target sourcetarget source

Bearer ReleaseALCAP Data Transport Bearer

Release

CNRNC RNC CNNode B Node BUE

Radio Link Setup Request

Hard Handover with switching in the CN: UE connected to one CN nodes (3G TS 25.331)

- - e up-

CPHY-TrCH-Setup-R

CPHY-RL-Setup-CNF

DCCH

CPHY-TrCH-Setup-CNF


Start TX/RX

Physical Channel Reconfiguration

Relocation Command

CPHY-RL-Release-REQ

Stop old TX/RXCPHY-RL-Setup-REQ

CPHY-Sync-IND

Start new TX/RX

CPHY-Sync-IND


Relocation Detect

Data Frame Synchronization


288/369

CNRRCL1 RRCL1RLCRRC

Forward Hard Handover

e p a e, p a e


289/369


290/369

CCCH

Cell Update via Iur without SRNS Relocation with C-RNTI Relocation (3G TS 25.331)

Uplink Signaling Transfer Indication

Cell Update

new C-RNTI

UL message

Common Transport Channel

Resource Request

Common Trans ort Channel

Cell Update Confirm

DCCH

Resource Response


Setup

RNTI Relocation Complete

Common Transport Channel

esource e ease

old C-RNTI


291/369

servingtargetsource

sRNCdRNCdRNC IurIubUuUE

Cell Update with SRNS Relocation (3G TS 25.331)


new C-RNTI

UL message

Relocation Required

Cell Update

Relocation Request


CCCH


Relocation Command

Relocation Comit

Cell Update Confirm

DCCH

S-RNTI and new S-RNTI

SRNC-ID and new SRNS-ID

new C-RNTI

Relocation Complete e oca on omp e e

IU Release Command



292/369

servingtarget

IU Release Complete

CNsRNCRNC IuIurUuUE

Inter-RNS URA Update via Iur with SRNS Relocation (3G TS 25.331)


C-RNTI

UL messa e Relocation Required

URA Update

Relocation Request


URA Update Confirm

CCCH


Relocation Command

Relocation Comit


DCCH

S-RNTI and new S-RNTI

SRNC-ID and new SRNS-ID

Relocation Complete

IU Release Command


Release


293/369

servingtarget

IU Release Complete

CNsRNCRNC IuIurUuUE

Inter-RNS URA Update via Iur without SRNS Relocation (3G TS 25.331)


-

URA Update

UL message

URA Update Confirm

CCCH

Downlink Signaling Transfer Request

C-RNTI

UL message


DCCH


294/369

servingtarget

CNsRNCRNC IuIurUuUE

Inter-System Handover

rom an o


295/369

RRC BSSMAPRANAP

Handover from UTRAN to GSM (3G TS 25.331)

Prepare HO

Relocation Required

Prepare HO Response

HO Request Acknowledge

HO Request

Relocation Command

HO Command

DCCH RRC

RR

HO Complete

HO Complete

HO Detect

en n gna eques

IU Release Command

ALCAP Data Transport

Bearer Release


296/369

Send End Signal Response

IU Release Complete

MSCBSSRNC CNUE

RRC BSSMAPRANAP

Handover from GSM to UTRAN (3G TS 25.331)

Prepare HO

HO Required

Relocation Request

Relocation Re uest Ack


Bearer Setup

Prepare HO Response

HO Command

DCCH RR

HO Command

HO Complete

Relocation Detect

RRC

e oca on omp e e

Send End Signal Request

Clear Command


297/369

Send End Signal Response

Clear Complete

MSCBSSRNC CNUE

ac e w c e


298/369

SRNS Relocation with Iur-Interface (3GTS 23.060, 25.413, 29.060)

Relocation Request

Relocation RequiredForward

Relocation Request

old SGSN address C-plane (old SGSN-UE)

old SGSN GTP-TEID

Target ID of RNC, Transparent Container

MM and PDP Context

(GGSN address U-Plane,

NSAPI QoS, UL-TEID C-/U-plane etc.)

IP for U-plane

GTP-TEID for C-plane

Transparent Container

RAB ID = NSAPIv


Forward

Relocation ResponseRelocation Command

Data

ForwardingIP for U-plane

GTP-TEI D for C-plane

Transparent Containerold SGSN address C-plane (new SGSN-UE)

new SGSN GTP-TEID

Target ID of RNC

Transparent Container

Data forwarding timer

SRNS ContextRelocation Commit

Relocation DetectUpdate PDP Context

RequestRNTI Reallocation

Forward DL Data

= - ,

Copy of DL Data send

through (GTP) Iu to target RNC

GTP-U / PDCP PDU sequence #

Relocation Complete

Update PDP ContextResponseRNTI Reallocation Complete

orwar e oca on

Complete

Forward RelocationComplete Acknowledge

Iu Release Command

Iu Release Complete



299/369

servingtargetsource old new


Bearer Release

GGSNRNCRNCUE SGSN SGSN

Access Stratum - Air Interface

Control Plane

Signaling

User Plane

Information

c t

L3

c t

BCFE PNFE DCFE

PDCPRRC

Transfer Mode Entity (TME)

CRLC

BMC

L2

RLC

RLC

BCCH PCCH DCCH CCCH CTCH DTCH

MAC-b

MAC-dC/shMACMAC-p

PHYPCH CPCH RACH FACH


300/369

CPHY ys ca ayer L1


301/369

Utran issues RRC Connection Setup 25.331 8.1.3.3 onFACH. Information sent to UE in 25.331 10.2.42. Values

needed to setup direct connection

UE changes to dedicated channel per 25.331 8.1.3.4according to RB (radio bearer mapping info from previous)

UE sen s RRC CONNECTION SETUP COMPLETE

message over DCCH. (also 8.1.3.4)

.s pp ngsome capa y n o ra e e ween

RRC/RRC

. .

24.008


302/369

https://mcscn.siemens.at/umts/

https://ims.icn.siemens.de/


303/369

-

Handover Procedures


304/369

Specifications

3GPP TS 10.89/50.089 GSM to other Systems Handover and Cell Selection/Reselection

3GPP TS 03.09/23.09 Handover procedures

3GPP TS 22.129 Handover requirements between UTRAN and GERAN or other radio systems

3GPP TS 25.841 DSCH power control improvement in soft handover

3GPP TS 25.832 Manifestations of Handover and SRNS relocation

3GPP TS 25.936 Handover for real-time services from PS-domain

3GPP TS 25.922 Radio Resource Management Strategies

3GPP TS 25.936 Handover for realtime services from PS-domain

3GPP TS 25.849 DSCH power control improvement in soft handover

3GPP TS 33.108 3G security: Handover interface for Lawful Interception (LI)


305/369

Intra-Frequency Handover


306/369

Active Set (AS)

The UE is communication via Radio Links (RL) towards the UTRAN.

A Radio Link describes all necessary parameter (PhCH, TrCH, LoCH) to make that communication working.

The UE may have multiple RL at the same time. In UL, the RLs will have the same parameters (like SC, CC),

where in DL different parameters are applied. The DL-RL may come from the same sector, cell, Node B, RNC

or from different one in any combination.

The Active Set contains this RLs which are currently in use.

One new RL is established between UE-UTRAN and therefore inserted to the active set.

Link Addition

One RL is released between UE-UTRAN and therefore removed from the the active set.

Link Deletion

One RL out of the active set is deleted and a new RL is added at the same time.

Link Replacement


307/369

Active Set Size (ASS)

.

Question: what happens in case on cell has ASS = 2 and the other ASS = 3? How to select? The highest?

The same applies for O&M parameter restricting HO execution, like ISHO allowed in one cell, but in another not.

How to decide? If it is allowed in at least one cell than its allowed?

Field trials showed that increasing ASS will not improve quality significantly.

This is also different for cs- and ps-Services.

Capacity planning has to proper calculate the needed channel element resources any additional link in AS

during soft handover.

maxASS for CS-Service = 3

maxASS for CS-Service = 2

Proposal


308/369

Intra-Frequency Handover Algorithm (3G TS 25.922, Siemens)

Qmeas

CPICH 1

TTT 1A TTT 1C TTT 1B

R1A-H1A H1C

R1B + H1B

R

CPICH 2

CPICH 3

Report 1A Report 1CStart 1A,1B,1C Report 1B

Remove Cell 1

, ,


309/369

R : Replacement threshold

H : Hysteresis

(condition has to be fulfilled for that time before event will be reported)

-

IFHO


310/369

Inter-Frequency Handover (IFHO) (Siemens)

Blind handover Intra RNC - Intra Node B Intra Antenna

Without neighbour cell measurements the RNC may decide to send the UE to a new cell one the other frequency

based on the adjacent cells configured by O&M.

Applicable when target cell is within the Node B of the source cell (and same antenna configuration is used).

The internal information of frame offsets between cells is used to calculate the necessary information

to provide frame and chip offset for the new radio links.

Timing maintained handover Intra RNC - Inter Node B, Intra RNC - Intra Node B

Timing re-initialised handover Inter RNC

,with NBAP or if necessary with RNSAP.

The received neighbouring cell info, either in the RL Setup Response or internally, is stored.

The RNC provides the DOFF value to the UE and sets the IE Timing Indication to initialise to force the UE

to calculate a new CFN after readin the new SFN.

The number of radio links established on the new frequency layer de end on the latest measurement,

in case the measurement provides information to hand over into a new active set, this information can be used

to setup or add more than one radio link. If this information is not available only one radio link is established.


311/369

p y

After establishing the common intra-frequency RRM more links would be added, using the common procedures.

Control of Compressed Frame Mode for Inter-Frequency Measurements (Siemens)

Inter-Frequency Measurements are activated using the RRC Measurement Control procedure.After the start of the compressed mode operation, the UE will attempts to find and synchronise

to the IS-FDD cells given in the neighbour cell list, and will provide the required measurements reports.

The reporting can be event triggered or periodic using: Events 2D, which triggers activation of compressed

frame mode and start of 2A, 2B, 2A and Event 2F, which triggers deactivation of compressed frame mode.

While the UE is in compressed mode, the RNC shall update the list of IF-FDD neighbour cells storedin the UE and the requested measurements stored in the UE every time the active set is updated,

by sending subsequent measurement control messages.

Qmeas

Inter-Frequency Handover (ISHO)

(Blind, timing maintained /

re-initialised)

1

FDD f2

FDD f3

time

Compressed Frame Mode

eport eporttart , ,

b tt f


312/369

FDD < threshold FDD > threshold better frequency

current < threshold

-

ISHO


313/369

Inter-System Handover (ISHO) to UTRAN (Siemens)

UE Initiated Inter-System Cell Re-Selection PS forward

Will result in a RRC Connection establishment with a establishment cause Inter System cell re-selection,

which indicates that the former RAT was different to the current.

The relevant parameters for Inter-System cell reselection are given via GSM radio access network.

The Inter-System cell reselection is used for PS services only and is signalled by a RRC Connection Establishment

Network Initiated Inter-System Cell Change

.

PS backward

Will result in a RRC Connection establishment with a establishment cause Inter System Cell Change,

w c n cates t at t e ormer was erent to t e current.

The relevant parameters for Inter-System cell reselection are given via GSM radio access network.

The Inter-System cell reselection is used for PS services only and is signalled by a RRC Connection Establishment

and following NAS signalling.

If a backward inter system HO is triggered by a RANAP procedure towards the target RNC,

the UE is configured with the RRC message HO To UTRAN. This RRC message is assembled in the target RNC

and sent via si nallin on RANAP RRC information tar et RNC to source s stem to the ori inatin RAT

Inter-System Handover CS backward

and forwarded to the UE.

If the UTRAN receives a Handover To UTRAN Complete on a SRB in AM mode the inter system procedureindicates the success to the originating entity.

The other RAT must request necessary UE capabilities from the UE before starting the HO To UTRAN

.

After establishing optional AS security, the RNC shall immediately invoke a UTRAN Mobility Information

procedure, in order to provide a complete S-RNTI to the UE and the UE timer and constants..


314/369

If the RNC receives an indication from the originating RAT that the HO failed, all radio resources shall be released.

Control of Compressed Frame Mode for Inter-System Measurements

used for Inter-System Handover (ISHO) (Siemens)

Inter-System (GSM) Measurements are activated using the RRC Measurement Control procedure.After the start of the compressed mode operation, the UE will attempts to find and synchronise

to the GSM cells given in the neighbour cell list, and will provide the required measurements reports.


frame mode and start of 3A and Event 2F, which triggers deactivation of compressed frame mode.

While the UE is in compressed mode, the RNC shall update the list of GSM neighbour cells storedin the UE and the requested measurements stored in the UE every time the active set is updated,

by sending subsequent measurement control messages.

QmeasInter-System Handover (ISHO)

FDD

GSM A

GSM B

timeCompressed Frame Mode

FDD < threshold FDD > threshold GSM B >

GSM A

eport eporteporttart


315/369

GSM A


316/369

SBHO


317/369

Overview

The intention is to er orm an Inter-S stem Handover to the GSM s stem based on actual used Service

which is offered at GSM with the same quality as at UMTS (e.g. Speech) or for Services which are not yet

supported at UMTS (e.g. CS Data Services).

The UTRAN is aided in its decision to erform Service Based Handover b the Service Handover arameter

received from the Core Node, indicating whether from the Core Nodes point of view,

the RAB in question should be transferred to GSM or not.

Whereby the RAB Assignment is rejected, using the cause value Directed Retry and

subsequently a Relocation Required message is sent also including the cause value Directed Retry

rec e e ry rom o

.

Subsequent Inter-System Handover

The RAB may be accepted in the RNC and a subsequent Intersystem Handover is triggered,

CS

o ow ng measurement reports rom t e .

Subsequent Inter-System Cell Change PS

,

following measurement reports from the UE.


318/369

IE Service Handover

, ,

with the RAB context for the duration of the RAB.

The actions of the RNC after receipt of a RANAP RAB Assignment Request will depend on:

-

- the RAB parameters

- current RNC load situation

- whether the UE already has an active RAB.

RAB Assignment Request

Handover to GSM should be performed RAB should be handed over to GSM as soon as possible although the final

decision whether to perform a handover to GSM is still made in UTRAN

Handover to GSM shall not be performed

Handover to GSM should not be performed

whether to perform a handover to GSM is still made in UTRAN

RAB shall never be handed over to GSM.

This means that UTRAN shall not initiate handover to GSM for the UE

with the normal release procedures.


319/369


320/369

SBHO special cases (Siemens)

s ou e opera or con gura e w e er can e r ggere w en a es or

is assigned to the UE. The resultant intersystem change will generally result in suspension of the

PS service in GPRS, unless the UE is also a Class A GPRS equipment.

It should be operator configurable whether SBHO can be triggered when a PS Streaming RAB

u u y u .

In the case that there are multiple RABs, and one of those is a CS RAB not marked

Handover to GSM shall not be performed should the other RAB be released and Intersystem Handover

Release due to UTRAN Generated Reason.

Service Based Handover may be triggered by load/service considerations when the Service Handover

.

If the admission control function in the UMTS System rejects a RAB Assignment Request,

whose Service Handover parameter value is Should not be handed over to GSM,

or the requested RAB is not supported in the RNC, then Service Based Handover can still be triggered

.

It should be noted that this option is to be taken after all attempts to set up the RAB in the UTRAN have failed,

as the intention of the Service Handover parameter value Should not be handed over to GSM is that the RABshould, where possible, remain in the UMTS world.

.


321/369

SBHO control by O&M (Siemens)

Service Based Handover

Speech Service Based HandoverDirected Retry

Yes

RAB Request = Speech

will trigger Directed Retry + SBHO or

will lead to RAB assi nment before SBHO

w tc es t e w o e unct ona ty on or o ce as s

Service Based Handover TypeBlind

SBHO will be based on Blind Handover or

on Inter-System Measurements

a licable for Directed Retr and RAB assi nment followin SBHO

o recte etry

ompresse o e

Load Service Based Handover Yes / NoRAB Request not supported or rejected will trigger or will not trigger SBHO

Exception: Not possible if Compressed Mode is needed. (load reduction)

Existing Best Effort PS RAB Yes / No

Existing Streaming PS RAB Yes / No

will trigger or will not trigger SBHO if there is already a Best Effort PS RAB present

will trigger or will not trigger SBHO if there is already a Streaming PS RAB present


322/369

Timing Control of Inter-Frequency Measurements (Siemens)

Select first IS-Target CellEvent 3C with suitable cell

Directed Activate IF- MeasurementsExpiry of TInterMeasDirRetry

RAB

time

InterMeasDirRetry

Proceed CallEvent 3C with suitable cell

Trigger ISHO

Activate IF- Measurements

Start TInterMeas

Expiry of TInterMeasDeactivate IF- Measurements

RAB

Assignment

RAB

Request

time

TInterMeasDirRetryStart: After initiating Intersystem Measurements.

Stop: Reception of Measurement Report Event 3C indicating a suitable GSM Cell.

TInterMeas

xp ry: o su ta e ce as een oun w t t e m n mum requ re ua ty eve or on a ure ur ng

Compressed Mode activation. Select first target cell from the Adjacent GSM Cell list and trigger ISHO.

Start: After initiating Intersystem Measurements.

Stop: Reception of Measurement Report Event 3C indicating a suitable GSM Cell.

x : op measuremen repor ng an procee e ca .

If the activation of Compressed mode fails the procedure ends.

ISHO Failure: If an attempted ISHO fails then the RNC will report this to the CN with the RANAP message


323/369

ISHO Failure: If an attempted ISHO fails then the RNC will report this to the CN with the RANAP message

, .

SBHO and RRC states (3G TS 25.331, Siemens)

may e r ggere n e _ or e _ s a e,

but the Uu message Handover from UTRAN Command can only be sent in Cell_DCH state.

[The procedure is initiated when UTRAN orders a UE in CELL_DCH state, to make a handover to a

radio access technology other than UTRAN, e.g. GSM. 3G TS 25.331v3.7.0]

Thus a state transition to Cell_DCH will be necessary.

This is applies regardless of whether Intersystem Measurements are required or using Blind HO.

e - o- s ou e one e er e ore e n a on o ompresse o e or

before initiating Blind HO,

thus before the RANAP message Relocation Required is sent to the MSC.


324/369

Control of Compressed Frame Mode for Inter-System Measurements

used for Service Based Handover (SBHO) (Siemens)

Inter-System (GSM) Measurements are activated using the RRC Measurement Control procedure.After the start of the compressed mode operation, the UE will attempts to find and synchronise

to the GSM cells given in the neighbour cell list, and will provide the required measurements reports.


frame mode and start of 3A and Event 2F, which triggers deactivation of compressed frame mode.

While the UE is in compressed mode, the RNC shall update the list of GSM neighbour c

Documents

L&S UMTS Training Course