umts call flow scenarios overview

5/21/2018 Umts Call Flow Scenarios overview

1/161

1

Contents

Introduction Basic stuff..

Call Flow Scenarios Node-B initialization and System Information Broadcast

RRC Connection Establishment and Release

Location/Routing Area Update

Circuit Switch Call Setup and Release

Packet Switch Call Setup and Release

Handovers

Backup Misc..


2/161

2

Introduction

UE Connection States

RNC Cell and UE Contexts

End to End Protocol Stacks (CS and PSDomain)

Handover Scenarios


3/161

3

UE Connection States

GSMConnected

Mode

UTRAN RRC Connected

GPRSPacket

Transfer

Mode

IDLE

Mode

CELL DCH

CELL PCH URA PCH

CELL FACH

Camping on GSM/GPRS Cell

Camping on UTRAN Cell

GPRS Packet

Idle Mode

UMTS to GSM

Inter-System Handover

GSM to UMTS

Inter-System Handover


4/161

4

UE #M

UE #2

UE #1

DTCHs

CELL #N

CELL #2

CELL #1

RLC-TM

RLC-TM

RNCCell and UE Contexts

PHY-Upper

MACd

RLC-UM RLC-AM RLC-AM RLC-AM RLC-AM

RLC-TM

DCH FP DCH FP DCH FP

DCCH DCCH DCCH DCCH DTCH

DCH DCH

RRC

PDCP

GTP IuUP

PS RAB CS RAB

MACc

RRC

SRB

RLC-TM RLC-UMRLC-TM

SRB #0SRB #0

CCCH CCCHPCCH

PCH FP FACH FPRACH FP

FACHPCHRACH

SRB #1 SRB #2 SRB #3 SRB #4

DCHs

MAC-d

MAC-c/sh

Flows


5/161

5

CS DomainEnd to End Protocols

PHY

PHY [E1/T1/STM]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

ALCAP

PHY

PHY-upper

MAC

RLC

RRCCodec

MM

CC

PHY [E1/T1/STM]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2NBAP

ALCAP PHY-upper

MAC

RLC

RRC

IuUP

AAL5

SSCOP

SSCF-NNI

STC.1

ALCAP

MTP3-b

SCCP

RANAP

PHY [E1/T1/STM]

ATM

AAL2

IuUP

AAL5

SSCOP

SSCF-NNI

STC.1

ALCAP

MTP3-b

SCCP

RANAP

Codec

MM

CC

UE Node-B RNC 3G-MSCUu IuB Iu-CS


6/161

6

PS DomainEnd to End Protocols

PHY

PHY [E1/T1]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

ALCAP

PHY

PHY-upper

MAC

RLC

RRCPDCP

GMM

SM

PHY [E1/T1/STM-1]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2NBAP

ALCAP PHY-upper

MAC

RLC

RRC

IP

AAL5

SSCOP

SSCF-NNI

MTP3-b

SCCP

RANAP

PHY [STM-1]

ATM

SSCF-NNI

AAL5

SSCOP

MTP3-b

SCCP

RANAP

GMM

SM

UE Node-B RNC 3G-SGSNUu IuB Iu-PS

IP

PDCP GTP-U

UDP

IP

GTP-U

UDP

GTP-C

L2

L1

IP

GTP-C

UDP

GTP-C

L2

L1

IP

3G-GGSNGn


7/161

7

Handover Scenarios

UTRAN

RNS

Node-BNode-B

RNC

RNS

Node-BNode-B

RNC

Core Network (CN)

UE


8/161

8

Call Flow Scenarios

Node-B initialization

RRC Connection Establishment and Release

Location/Routing Area Update

Circuit Switch Call Setup and Release

Packet Switch Call Setup and Release

Handovers


9/161

9

Node-B Initialization

RNC MSCNode-BUE

Audit Procedure

Cell Setup Procedure

System Information Update

Common TrCH(PRACH, AICH, RACH) Setup

Common TrCH(SCCPCH, PCH/PICH, FACHs) Setup

SIB5 System Information Update

Un-block and Un-barred Cell


10/161

10

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationAudit Procedure:Audit Required Indication MessageDescription: Request the CRNC to perform an audit of the logical resources at the Node B. Node-B initiates this

procedure after the SSCOP layer is established via the exchange of BGN/BGAK PDUs.

Main IEsTransaction ID

Channels

SSCF / SSCOP / AAL5

NBAPNBAPAudit Required Indication

[ Transaction ID ]


11/161

11

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationAudit Procedure:Audit Request MessageDescription: RNC initiates an audit of the Node-B configuration and status of logical resources, using Audit

Request message. A complete audit of a Node B is performed by one or more Audit procedures.


Start of audit sequence ind

Channels

SSCF / SSCOP / AAL5


[ Transaction ID ]

NBAPNBAPAudit Request

[ Transaction ID, Start of Audit Seq Ind ]


12/161

12

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationAudit Procedure:Audit Response MessageDescription: Node-B sends Audit response to RNC, with its current configuration and status of logical resources,

using Audit Response message.


End of audit sequence ind

Cell Info (Configured)

Local Cell Information

Communication Control

Port information

Channels

SSCF / SSCOP / AAL5


[ Transaction ID ]

NBAPNBAPAudit Request

[ Transaction ID, Start of Audit Seq Ind ]

NBAPNBAPAudit Response

[ End of Audit Seq Ind, Local Resource Info ]


13/161

13

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCell Setup Procedure:Resource Status Indication MessageDescription: Node-B sends resource indication message to indicate availability or un-availability of local resource

(e.g. Local Cell, etc), or change in capability, operational state, etc of resource.


No Failure Indication

Local Cell ID

Add/Delete Indicator

Channels

SSCF / SSCOP / AAL5

NBAPNBAPResource Status Indication

[ Local Cell ID, Add/Delete Indicator ]

Audit Procedure


14/161

14

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCell Setup Procedure:Cell Setup Request MessageDescription: RNC initiates Cell Configuration/Setup, which will use resources in Node-B identified by Local Cell

ID, received in Resource Status Indication message.

Main IEsTransaction ID,

Global (C-ID) Cell ID,

Local (Node-B) Cell ID,

DL/UL Frequency,

Maximum Tx Power,

Primary Scrambling Code

P-SCH, S-SCH info,

PCPICH, SCPICH info,

PCCPCH, BCH, etc info..

Channels

SSCF / SSCOP / AAL5



Audit Procedure

NBAPNBAP Cell Setup Request[ Global/Local Cell ID, Physical Config. ]


15/161

15

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCell Setup Procedure:Cell Setup Response MessageDescription: Node B reserves necessary resources and configure the new cell according to received parameters,

and on success sends Cell Setup Responseto RNC. (On failure, Cell Setup Failureresponse will be sent!!)


Channels

SSCF / SSCOP / AAL5



Audit Procedure


NBAPNBAPCell Setup Response

[ Transaction ID ]


16/161

16

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCell Setup Procedure:Block Resource Request MessageDescription: Node-B request RNC to block (prohibit use of!!) new configured cell until system information (MIB,

SIBs, etc) are updated and broadcast on BCH (i.e. PCCPCH).


Global (C-ID) Cell ID

Blocking Priority (High!!)

Channels

SSCF / SSCOP / AAL5



Audit Procedure



[ Transaction ID ]

NBAPNBAPBlock Resource Request

[ Transaction ID, Blocking Priority ]


17/161

17

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCell Setup Procedure:Block Resource Response MessageDescription: RNC Blocks respective resource (cell!!), and send successful response to the Node-B.


Channels

SSCF / SSCOP / AAL5



Audit Procedure



[ Transaction ID ]

NBAPNBAPBlock Resource Request

[ Transaction ID, Blocking Priority ]

NBAPNBAPBlock Resource Response

[ Transaction ID ]


18/161

18

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: RNC sends System Information, Scheduling Information, System Information Update time, etc of

respective configured cell to Node-B using series of System Information Update Requestmessage.



BCCH Modification Time

MIB, SB, SIB info

Segment Info

Channels

SSCF / SSCOP / AAL5

Audit Procedure

NBAPNBAPSystem Information Update Request

[ SIB segment info. ]



19/161

19

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Response MessageDescription: Node-B process received System Information, Scheduling Information, System Information Update

time, etc and send successful response using System Information Update Responsemessage.



Channels

SSCF / SSCOP / AAL5

Audit Procedure




NBAPNBAPSystem Information Update Response




Segment 1

Segment 2


20/161

20

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:RRC System Information MessageDescription: Node-B store and process received system information; and schedules transmission of each

segment according to scheduling information, on BCCH: BCH: PCCPCH, in Cell.

Main IEsMaster Information Block,

Scheduling Block,

System Information Block

Channels

BCCH / BCH / PCCPCH

Audit Procedure








Segment 1

Segment 2

RRCRRC

BCCH: System Information

RRCRRCBCCH: System Information


21/161

21

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:Common TrCH Setup Request MessageDescription: RNC use this procedure to setup Common transport channel(s), along with associated physical

channels, on which they are mapped, in Node-B. (e.g. One PRACH, AICH, RACH in single message!!.)

Main IEsTransaction ID, Cell ID,

PRACH parameters [ e.g.

TFCS, SF, Signatures, etc..]

AICH parameters [ e.g.

Channel Codes, Power, etc..]

RACH parameters [ e.g.

TrCH ID, TFS, etc..]

Channels

SSCF / SSCOP / AAL5

Audit Procedure



NBAPNBAP Common TrCH Setup Request[PRACH, AICH, RACH]


22/161

22

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:Common TrCH Setup Response MessageDescription: Node B configure and activate indicated PRACH, AICH and associated RACH transport channel, and

sends successful response to RNC (with TLA and Binding ID for RACH IuB AAL2 Bearer!!).

Main IEsTransaction ID, RACH parameters [ e.g.

TrCH ID, Transport Layer

Address and Binding ID ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure




NBAPNBAPCommon TrCH Setup Response

[TLA, Binding ID]


23/161

23

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:ALCAP Establish Request MessageDescription: RNC initiates establishment of AAL2 bearer for RACH, using received Transport Layer Address and

Binding ID information, in response from Node-B.

Main IEsOSAID / DSAID (Originating

/ Destination signalling

association ID)

CEID (Path ID + CID) SUGR (Binding ID!!)

AAL2 Destination Address

of Node-B

Channels

STP.2 / SSCF / SSCOP / AAL5

Audit Procedure





[TLA, Binding ID]

ALCAPALCAPALCAP Establish Request (ERQ)

[OSAID,DSAID,SUGR,AAL2 Address]


24/161

24

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:ALCAP Establish Confirm MessageDescription: Node-B ALCAP verifies received Binding ID; and respond successful establishment of AAL2 bearer

using ALCAP confirm message.

Main IEsOSAID

DSAID

Channels


Audit Procedure





[TLA, Binding ID]

ALCAPALCAPALCAP Establish Confirm (ECF)

[OSAID,DSAID]




25/161

25

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:Common TrCH Setup Request MessageDescription: RNC use this procedure to setup Common transport channel(s), along with associated physical

channels, on which they are mapped, in Node-B. (e.g. One SCCPCH, PICH, PCH, FACH(s) in single message!!.)

Main IEsTransaction ID, Cell ID,

SCCPCH parameters [e.g. ID,

TFCS, SF, Codes, etc..]

PCH parameters [ e.g. ID,

TFS,Window(ToAWS, ToAWE),

PICH Code, Max Power, .. ]

FACH(s) parameters [ e.g.

ID, TFS, Window(ToAWS,

ToAWE), Max Power, .. ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure




NBAPNBAPCommon TrCH Setup Request

[ SCCPCH, PCH+PICH, FACH(s) ]


26/161

26

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:Common TrCH Setup Response MessageDescription: Node B configure and activate indicated SCCPCH, PICH, associated PCH and FACH(s) transport

channel, and sends successful response to RNC (with TLA and Binding ID for PCH, FACH IuB AAL2 Bearer!!).

Main IEsTransaction ID, PCH parameters [ e.g. TrCH

ID, Transport Layer Address

and Binding ID ]

FACH(s) parameters [ e.g.



Channels

SSCF / SSCOP / AAL5

Audit Procedure






[TLA(s), Binding ID(s)]



27/161

27

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:ALCAP Establish Request MessageDescription: RNC initiates establishment of AAL2 bearer for PCH and FACH(s), using received respective

Transport Layer Address and Binding ID information, in response from Node-B.

Main IEsOSAID

DSAID + CEID

SUGR (Binding ID!!)


of Node-B

Channels


Audit Procedure







ALCAPALCAPALCAP ERQ



For PCH & FACH(s) bearers


28/161

28

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:ALCAP Establish Confirm MessageDescription: Node-B ALCAP verifies received Binding ID; and respond successful establishment of AAL2 bearer

using ALCAP confirm message.

Main IEsOSAID

DSAID

Channels


Audit Procedure










[OSAID,DSAID]




29/161

29

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:FP DL Synchronization FrameDescription: After successful establishment of AAL2 bearer, at RNC, PCH and FACH(s) FPs initiates L2

synchronization by sending DL synchronizationcontrol frame with current CFN.

Main IEsCFN (Connection Frame

Number)

Channels

FP / AAL2

Audit Procedure










[OSAID,DSAID]

FPFP DL Synchronization[ CFN ]




30/161

30

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationCommon TrCH Setup Procedure:FP UL Synchronization FrameDescription: Node-B RACH FP verifies relationship of SFN with received CFN, and respond back with UL

synchronization control frame, containing Time of Arrival [ToA - required timing adjustment!!] information.


Number),

ToA [Time of Arrival]

Channels

FP / AAL2

Audit Procedure










[OSAID,DSAID]

FPFP DL Synchronization[ CFN ]

FPFPUL Synchronization

[ CFN, ToA ]




31/161

31

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: After successful setup of all common physical and transport channels for a Cell, RNC sends System

Information, Scheduling Information, etc (i.e. SIB5 [& SIB6!!] of respective configured cell) to Node-B.




Reference to other SIBs

Segment Info [SIB5 with

PRACH info, SCCPCH info,

AICH info, PICH info, etc ..]

Channels

SSCF / SSCOP / AAL5

Audit Procedure






[ SIB5 segment info. ]


32/161

32

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: Node-B process received SIB5 (and SIB6!!) System Information, Scheduling Information, System

Information Update time, etc and send successful response to RNC.



Channels

SSCF / SSCOP / AAL5

Audit Procedure









33/161

33

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: Node-B sends resource indication message to indicate that it has successfully change cell capacity

and communication control port operational state (and ready to unblock cell!!)


Communication Control

Port ID

Channels

SSCF / SSCOP / AAL5

Audit Procedure





NBAPNBAPResource Status Indication[ Communication Control port ID ]



34/161

34

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: Node-B sends resource unblock indication message to RNC, to indicate that respective Cell is

operational and can be unblocked.



Channels

SSCF / SSCOP / AAL5

Audit Procedure






NBAPNBAPUnblock Resource Indication

[ C-ID ]



35/161

35

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: After successful unblocking cell resource, RNC sends updated SIB3 System Information (with cell

status as unbarred!!) to Node-B.




Reference to other SIBs

Segment info [ SIB3 with

Cell status unbarred!! ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure







[ C-ID ]





36/161

36

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationSystem Info Update Procedure:System Info Update Request MessageDescription: Node-B process received SIB3 System Information, Scheduling Information, System Information

Update time, etc and send successful response to RNC.



Channels

SSCF / SSCOP / AAL5

Audit Procedure







[ C-ID ]






37/161

37

Channels Main IEs

RNC MSCNode-BUE

Node-B InitializationNode-B initialization with operational Cell Context!!..

Main IEsChannels

Audit Procedure






Un-block and Un-barred Cell


38/161

38

RRC Connection Management

RNC MSCNode-BUE

Random Access Procedure

RRC Connection Request

UE Context Setup

RRC Connection Setup

RRC Connection Release

UE Context Cleanup


39/161

39

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRandom Access Procedure:System Information BroadcastDescription: Node-B transmits system information blocks according to scheduling information, on BCCH: BCH:

PCCPCH, in Cell. UE acquires system information blocks required for initial access in idle mode.

Main IEsMaster Information Block,

Scheduling Block,

System Information Block

[SIB 1, SIB 2, SIB 3, etc..]

Channels

BCCH / BCH / PCCPCH




40/161

40

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRandom Access Procedure:Physical Layer Access attemptsDescription: UE use cell system information to determine common physical channel configuration, initial power,

etc.. It use received PCPICH power, calculates initial uplink power (open loop!!) and initiate access to network.

Main IEsSignature Sequence

Channels

PRACH



PHYPHYPreamble

PHYPreamble

PHYPreamble

Wait for AICH response,

No response, Step-up power!!

Retransmit Preamble



Retransmit Preamble


41/161

41

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRandom Access Procedure:Physical Layer Access detectionDescription: UE use cell system information to determine common physical channel configuration, initial power,

etc.. It use received PCPICH power, calculates initial uplink power (open loop!!) and initiate access to network.

Main IEsAICH Response Sequence

Channels

AICH



PHYPHYPreamble

PHYPreamble

PHYPreamble



Retransmit Preamble



Retransmit Preamble

PHYPHYAccess Indication


42/161

42

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementInitial Access Request:RRC Connection Request MessageDescription: On successful physical layer access detection, UE transmits RRC Connection Request message to

network on RACH : PRACH.

Main IEsInitial UE identity [ e.g.

IMSI, TMSI, P-TMSI, IMEI, etc.

]

Establishment Cause [ e.g.

Originating or Terminating

voice,data..;Emergency, etc]

Measurement Information

Channels

CCCH : RACH : PRACH


RRCRRCCCCH: RRC Connection Request

PHYPHY

RACH Message[ Data, Control (TFCI) ]

FPFPRACH Data Frame

[ CFN, TFI, TB(s), CRCI indicator ]

RLC

MAC RLC

MACProcess received PRACH data;Decode it using control info(TFCI);


43/161

43

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Setup Procedure:Radio Link Setup Request MessageDescription: On reception of RRC Connection Request message, RNC selects L1, L2 parameters according to UE

RRC state and allocate resources. If selected RRC state Cell DCH, initiates RL setup towards Node-B.

Main IEsCell ID, Comm Ctxt ID,

UL/DL DPCH info [ e.g.

Codes, TFCS, etc ]

DCH info [ e.g. TrCH ID,

UL/DL TFS, Window(ToAWS,

ToAWE), Priority, etc..]

Power Information [ e.g.

Initial power, SIR target,

Max/Min DL power, etc ]

Channels

SSCF / SSCOP / AAL5


RRC Connection Setup Request

NBAPNBAPRadio Link Setup Request[ UL/DL DPCH info, RL info, DCH ]


44/161

44

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Setup Procedure:Radio Link Setup Response MessageDescription: On reception Radio Link Setup Requestmessage, Node-B reserves necessary resources and

configure new radio link(s) according to received parameters, and respond success to RNC.


Node-B Communication

Context ID

DCH parameters [ e.g. TrCH

ID, Transport Layer Address

and Binding ID ]

Channels

SSCF / SSCOP / AAL5



NBAPNBAPRadio Link Setup Request

NBAPNBAP Radio Link Setup Response[ Comm Ctxt info, TLA, Binding ID ]


45/161

45

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Setup Procedure:ALCAP Establish Request/Confirm MessageDescription: RNC initiates AAL2 bearer establishment for DCH, using received AAL2 TLA and Binding ID. Node-B

ALCAP verifies received Binding ID; and respond successful establishment with ALCAP Confirm msg.

Main IEsOSAID, DSAID + CEID,

SUGR (Binding ID!!),

AAL2 destination Address

OSAID,

DSAID

Channels

SSCF / SSCOP / AAL5




NBAPNBAP Radio Link Setup Response




[OSAID,DSAID]


46/161

46

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Setup Procedure:FP DL/UL Synchronization FrameDescription: At RNC, DCH FP initiates L2 synchronization using DL synchronizationControl Frame with CFN.

Node-B DCH FP verifies CFN to SFN relationship; & respond back with ToA(required timing adjustment) Info.


Number)

CFN (Connection Frame

Number),

ToA (Time of Arrival)

Channels

FP / AAL2




NBAPNBAP Radio Link Setup Response



FPFPDL Synchronization

[ CFN ]

FPFP UL Synchronization[ CFN, ToA ]


47/161

47

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementInitial Access Response:RRC Connection Setup MessageDescription: On successful setup of UE context, RNC sends RRC Connection Setupmessage to UE over CCCH :

FACH : SCCPCH, with information about allocated resources/configuration.

Main IEsReceived Initial UE ID,

RRC State [DCH, FACH]

RNTIs [U-RNTI, C-RNTI]

SRB info [RLC, mapping],

UL/DL DCH info [e.g. ID, TFS,

TFCS, etc..]

RL info [e.g. Frequency,

Codes, etc]

Power Info, etc..

Channels

CCCH : FACH : SCCPCH



UE Context Setup

RRCRRC CCCH: RRC Connection Setup

PHYPHYSCCPCH Message[ Data, Control (TFCI) ]

FPFPFACH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MACRLC

MAC RRC Connection Setup message

would be split into several TB(s),

hence this sequence will repeat!!


48/161

48

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementInitial Access Response:RRC Connection Setup Complete MessageDescription: On reception of RRC Connection Setupmessage, UE configures its L1, L2 according RRC state and

respective received parameters, and responds to RNC using RRC Connection Setup Completemessage.

Main IEsRRC transaction ID,

START List [CS, PS]

Radio Access Capabilities

[e.g. Basic, extended, inter-

system, etc]

Channels

DCCH : DCH : DPDCH



UE Context Setup

RRCRRC CCCH: RRC Connection Setup

PHYPHYSCCPCH Message[ Data, Control (TFCI) ]

FPFPFACH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MACRLC

MAC RRC Connection Setup message

would be split into several TB(s),

hence this sequence will repeat!!

RRCRRCDCCH: RRC Connection Setup Complete

RLC

MACPHYPHY DPCH [DPDCH + DPCCH]

[ Data, Control (TFCI,TFC,Pilot) ]

FPFPDCH Data Frame


RLCMAC


49/161

49

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRRC Connection Release: RRC Connection Release MessageDescription: RNC anytime can release RRC Connection in Cell FACH or Cell DCH state, by sending RRC Connection

Releasemessage on DCCH. [exceptionally on CCCH, when UE in Cell FACH state!!]

Main IEsRRC transaction ID, Release Cause[e.g. normal,

inactivity, directed re-

establishment, congestion, ..]

Rplmn information

Channels

DCCH : DCH : DPDCH



UE Context Setup


RRCRRCDCCH: RRC Connection Release

PHYPHYDPCH [DPDCH + DPCCH][ Data, Control (TFCI,TPC,Pilot) ]

FPFPDCH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MACRLC

MAC


50/161

50

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRRC Connection Release:RRC Connection Release Complete MessageDescription: On reception of RRC Connection Releasemessage, responds to RNC with RRC Connection Release

Completemessage on DCCH, terminates RRC Connection and move to idle state.

Main IEsRRC transaction ID

Channels

DCCH : DCH : DPDCH



UE Context Setup



PHYPHYDPCH [DPDCH + DPCCH][ Data, Control (TFCI,TPC,Pilot) ]

FPFPDCH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MACRLC

MAC

RRCRRCDCCH: RRC Connection Release Complete

RLC

MAC

PHYPHYDPCH [DPDCH + DPCCH][ Data, Control (TFCI,TFC,Pilot) ]

FPFPDCH Data Frame


RLC

MAC


51/161

51

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Cleanup:NBAP Radio Link Deletion Request MessageDescription: On reception of RRC Connection Release Completemessage, RNC initiates cleanup of UE context. If

RRC Connection in Cell DCH state, initiate Radio Link Deletion Requesttowards Node-B.


CRNC Comm Ctxt ID,

Node-B Comm Ctxt ID,

RL ID(s)

Channels

SSCF : SSCOP : AAL5



UE Context Setup

RRC Connection SetupRRC Connection Release

NBAPNBAPRadio Link Deletion Request

[ RL ID(s) ]


52/161

52

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Cleanup:NBAP Radio Link Deletion Response MessageDescription: On reception Radio Link Deletion Request, Node-B release all resources associated with respective

RL Ids. On success, respond with Radio Link Deletion Responsemessage to RNC.


CRNC Communication

Context ID

Channels

SSCF : SSCOP : AAL5



UE Context Setup



NBAPNBAPRadio Link Deletion Response

[ CRNC Comm Ctxt ID ]


53/161

53

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementUE Context Cleanup:ALCAP Release Request/Confirm MessageDescription: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data stream. RNC ALCAP

request release with Release Requestmessage, Node-B ALCAP confirms it with Release Confirmmessage.

Main IEsDSAID

Cause

DSAID

Channels

STC.2 / SSCF / SSCOP / AAL5



UE Context Setup




ALCAPALCAPALCAP Release Request

[ DSAID, Cause ]

ALCAPALCAPALCAP Release Confirm

[ DSAID ]


54/161

54

Channels Main IEs

RNC MSCNode-BUE

RRC Connection ManagementRRC Connection Established and Released!!..

Main IEsChannels



UE Context Setup


UE Context Cleanup

Mobility Management Location


55/161

55

Mobility ManagementLocation

UpdateRNC MSC/VLRNode-BUE

RRC Connection Establishment

Signalling Connection Establishment (Location Update Request Procedure)

Identification /Authentication / Security Procedure (Optional!!)

Location Update Accept (Optional TMSI Reallocation!!) Procedure


UE Context Cleanup

Iu Connection Release



56/161

56

Channels Main IEs

RNC MSCNode-BUE


UpdateSignalling Connection Establishment:RRC Initial Direct Transfer Message

Description: On successful establishment of RRC Connection, UE sends first NAS message, enclosed in RRC

Initial Direct Transfermessage on DCCH.


CN Domain Identity [e.g. CS,

PS],

NAS Message [ Encoded

Update Type, Cipher Key Seq

No, LAI, Classmark, .. ]

Measurement Results

Channels

DCCH : DCH : DPDCH


RRCRRCDCCH: Initial Direct Transfer

[ CN Domain ID, NAS Message ]



57/161

57

Channels Main IEs

RNC MSCNode-BUE


UpdateSignalling Connection Establishment:RANAP Initial UE Message

Description: RNC uses received CN domain identity in Initial Direct TransferMessage, and initiate Iu (Iu-CS)

connection setup, and transfer of received Initial UE NAS message using RANAP to core network (MSC/VLR).

Main IEsCN Domain ID [CS or PS]

Location Info [ e.g. LAI, RAC,

SAI, etc..]

NASPDU [ Encoded

Update Type, Cipher Key Seq

No, LAI, Classmark, .. ]

Global RNC ID

Iu Signalling Connection

Identifier

Channels

SCCP : MTP3b : SAAL : AAL5




RANAPRANAPInitial UE Message

[ CN Domain ID, LAI, NAS-PDU ]

SCCPSCCPConnection Confirm (CC)

[ SRC/DST References ]

SCCPSCCPConnection Request (CR)

[ Reference, SRC/DST Add, User Data ]

Iu (Iu-CS!!) Connection Setup;

SCCP carry RANAP Initial UE Message

piggybacked in SCCP CR PDU!!

All subsequent RANAP messages will be

sent over this established SCCP Connection!!



58/161

58

Channels Main IEs

RNC MSCNode-BUE


UpdateIdentification Procedure:RANAP Direct Transfer Message

Description: MM (optionally!!) initiates Identification Procedure, with Identity Request message. MSC forwards

Identity Request message, encoded NAS PDU, using RANAP Direct TransferMessage to RNC.

Main IEsNASPDU [ Encoded

Identity Request, Identity

Type (e.g. IMSI, TMSI, etc)]

Channels




RANAPRANAPDirect Transfer

[ NAS PDU (Identity Request!!) ]



59/161

59

Channels Main IEs

RNC MSCNode-BUE


UpdateIdentification Procedure:RRC Downlink Direct Transfer Message

Description: RNC RRC encodes received NAS PDU, in RANAP Direct Transfermessage, into RRC Downlink Direct

Transfermessage and send it to UE on DCCH (SRB-3).

Main IEsRRC Transaction ID,

CN Domain ID [CS or PS],


Identity Request, Identity

Type (e.g. IMSI, TMSI, etc)]

Channels

DCCH : DCH : DPDCH



RRCRRCDCCH: Downlink Direct Transfer






60/161

60

Channels Main IEs

RNC MSCNode-BUE


UpdateIdentification Procedure:RRC Uplink Direct Transfer Message

Description: UE (MM) responds with Identity Response, encoded NAS PDU, in RRC Uplink Direct Transfer

message on DCCH (SRB-3).




Identity Response, Requested

Identity Value ]

Channels

DCCH : DCH : DPDCH







RRCRRCDCCH: Uplink Direct Transfer




61/161

61

Channels Main IEs

RNC MSCNode-BUE


UpdateIdentification Procedure:RANAP Direct Transfer Message

Description: RNC forwards received NAS PDU, to Core Network (MSC/VLR), using RANAP Direct Transfer

Message.

Main IEsNAS Message [ Encoded

Identity Response, Requested

Identity Value ]


SAI, etc..] optional

Channels











[ NAS PDU (Identity Response!!) ]



62/161

62

Channels Main IEs

RNC MSCNode-BUE


UpdateAuthentication Procedure:RANAP Direct Transfer Message

Description: MM (optionally!!) initiates Authentication Procedure, with Identity Request message. MSC

forwards Authentication Request message, encoded NAS PDU, using RANAP Direct TransferMessage to RNC.


Authentication Request,

CKSN, RAND, AUTN, .. ]

Channels





[ NAS PDU (Authentication Request!!) ]

Identification Procedure



63/161

63

Channels Main IEs

RNC MSCNode-BUE


UpdateAuthentication Procedure:RRC Downlink Direct Transfer Message






Authentication Request,

CKSN, RAND, AUTN, .. ]

Channels

DCCH : DCH : DPDCH





RANAPRANAP

Direct Transfer[ NAS PDU (Authentication Request!!) ]




64/161

64

Channels Main IEs

RNC MSCNode-BUE


UpdateAuthentication Procedure:RRC Uplink Direct Transfer Message

Description: UE (MM) responds with Authentication Response, encoded NAS PDU, in RRC Uplink Direct Transfer

message on DCCH (SRB-3).




Authentication Response,

SRES (UE Calculated!!) ]

Channels

DCCH : DCH : DPDCH





RANAPRANAP







65/161

65

Channels Main IEs

RNC MSCNode-BUE


UpdateAuthentication Procedure:RANAP Direct Transfer Message


Message.

Main IEsNAS Message [ Encoded

Authentication Response,

SRES (UE Calculated!!) ]



Channels






RANAPRANAP





[ NAS PDU (Authentication Response!!) ]




66/161

66

Channels Main IEs

RNC MSCNode-BUE


UpdateSecurity Procedure:RANAP Security Mode Command Message

Description: MSC (optionally!!) initiates Security Procedure, using RANAP Security Mode CommandMessage to

RNC.

Main IEsIntegrity Protection Info

[e.g. Permitted algorithms,

Integrity Protection Key, . ]

Encryption Info [e.g.

Permitted Algorithm Set,

Encryption Key, . ]

Key Status [Old or New]

Channels




RANAPRANAP

Security Mode Command[ Integrity Protection, Encryption info ]

Identification / Authentication Procedure



67/161

67

Channels Main IEs

RNC MSCNode-BUE


UpdateSecurity Procedure:RRC Security Mode Command Message

Description: RNC RRC initiates security procedure, by sending RRC Security Mode Commandmessage to UE on

DCCH (SRB-2).

Main IEsCN Domain ID [CS or PS],

Integrity Check Info [ i.e.

MAC, RRC Msg Seq No ]

Integrity Prot Mode Info [

Cmd(S/M), Algo, FRESH, DL

Act time for SRBs ]

Ciphering Mode Info [ e.g.

Cmd(Start/Restart), Algo, DL

Act time for all RBs ]

Channels

DCCH : DCH : DPDCH



RRCRRCDCCH: Security Mode Command

[ CN Domain ID, Integrity Check Info, Integrity Protection/Ciphering Mode Info ]

RANAPRANAP





68/161

68

Channels Main IEs

RNC MSCNode-BUE


UpdateSecurity Procedure:RRC Security Mode Complete Message

Description: UE RRC send successful response of security procedure, by sending RRC Security Mode Complete

message to RNC on DCCH (SRB-2).




UL Integrity Protection

activation time for SRBs [ i.e.

RRC Msg Seq Numbers ]

UL Ciphering activation time

for all RBs [ i.e. RLC Seq

Numbers ]

Channels

DCCH : DCH : DPDCH





RANAPRANAP



RRCRRCDCCH: Security Mode Complete

[ Integrity Check Info, UL Integrity Protection/Ciphering Activation Time ]



69/161

69

Channels Main IEs

RNC MSCNode-BUE


UpdateSecurity Procedure:RANAP Security Mode Complete Message

Description: RNC send successful response of Security Procedure, using RANAP Security Mode Complete

message towards MSC.

Main IEsChosen Integrity Protection

Algorithm [ i. e. UIA1 ]

Chosen Encryption

Algorithm [ No Encryption, or,

UEA1 ]

Channels






RANAPRANAP





RANAPRANAPSecurity Mode Complete

[ Chosen Integrity, Encryption Algorithm ]



70/161

70

Channels Main IEs

RNC MSCNode-BUE


UpdateSecurity Procedure:RANAP Common ID Message

Description: MSC provide permanent NAS UE identity (i.e. IMSI) to RNC using RANAP Common IDmessage. RNC

use same for paging co-ordination functionality.

Main IEsPermanent NAS UE identity

( i.e. IMSI value )

Channels






RANAPRANAP





RANAPRANAPSecurity Mode Complete

[ Chosen Integrity, Encryption Algorithm ]

RANAPRANAP

Common ID[ Permanent NAS UE Identity ]



71/161

71

Channels Main IEs

RNC MSCNode-BUE


UpdateLocation Update Accept Procedure:RANAP Direct Transfer Message

Description: Core network MM confirms location update procedure by Location Update Acceptmessage to UE.

MSC transfers Location Update Accept, encoded NAS PDU, in RANAP Direct Transfermessage to RNC.


Location Update Accept, LAI,

New mobile id(TMSI),]

Channels




RANAPRANAP

Direct Transfer[ NAS PDU (Location Update Accept) ]

Identification / Authentication / Security Procedure



72/161

72

Channels Main IEs

RNC MSCNode-BUE


UpdateLocation Update Accept Procedure:RRC Downlink Direct Transfer Message






CN Domain ID [CS or PS] NASPDU [ Encoded

Location Update Accept, LAI,

New mobile id(TMSI),]

Channels

DCCH : DCH : DPDCH



RANAPRANAP




[ Integrity Check info, CN Domain ID, NAS Message ]



73/161

73

Channels Main IEs

RNC MSCNode-BUE


UpdateLocation Update Accept Procedure:RRC Uplink Direct Transfer Message

Description: (Optionally!!) If TMSI has been reallocated as part of Location Update Accept Message, UE (MM)

responds with TMSI Reallocation Complete, encoded NAS PDU, in RRC Uplink Direct Transfermessage.




CN Domain ID [CS or PS] NASPDU [ EncodedTMSI

Reallocation Complete

Message Type ]

Channels

DCCH : DCH : DPDCH



RANAPRANAP









74/161

74

Channels Main IEs

RNC MSCNode-BUE


UpdateLocation Update Accept Procedure:RANAP Direct Transfer Message


Message.

Main IEsNASPDU [ EncodedTMSI

Reallocation Complete

Message Type ]



Channels




RANAPRANAP








[ NAS PDU (TMSI Realloc Complete) ]



75/161

75

Channels Main IEs

RNC MSCNode-BUE


UpdateIu Connection Release:RANAP Iu Release Command Message

Description: On successful completion of Location Update procedure, CN initiate Iu (Signalling!!) Connection

Release procedure, using RANAP Iu Release Commandtowards RNC.

Main IEsCause ( Normal Release!! )

Channels






RANAPRANAPIu Release Command

[ Cause ]



76/161

76

Channels Main IEs

RNC MSCNode-BUE


UpdateIu Connection Release:RANAP Iu Release Complete Message

Description: RNC confirms Iu signalling connection release, using RANAP Iu Release Completemessage to CN. It

also initiates lower layer (SCCP) connection release, established for respective Iu signalling Connection.

Main IEsChannels






RANAPRANAPIu Release Command

[ Cause ]

RANAPRANAPIu Release Complete

SCCPSCCPReleased

[ SRC/DST References, Cause ]

SCCPSCCPRelease Complete[ SRC/DST References ]

triggers



77/161

77

Channels Main IEs

RNC MSCNode-BUE


UpdateRRC Connection Release:RRC Connection Release Message

Description: RNC initiates RRC connection release, by sending RRC Connection Releasemessage to UE on DCCH

(SRB1).




Release Cause[e.g. normal,

inactivity, directed re-

establishment, congestion, ..]

Rplmn information

Channels

DCCH : DCH : DPDCH







[ Integrity Check info, Release Cause ]

triggers



78/161

78

Channels Main IEs

RNC MSCNode-BUE


UpdateRRC Connection Release:RRC Connection Release Complete Message

Description: UE responds with RRC Connection Release Complete message on DCCH to RNC, terminates RRC

connection and move to RRC IDLE state.




Channels

DCCH : DCH : DPDCH







[ Integrity Check info, Release Cause ]

triggers

RRCRRCDCCH: RRC Connection Release Complete

[ Integrity Check info ]



79/161

79

Channels Main IEs

RNC MSCNode-BUE


UpdateUE Context Cleanup:NBAP Radio Link Deletion Request Message

Description: On reception of RRC Connection Release Completemessage, RNC initiates cleanup of UE context. If

RRC Connection in Cell DCH state, initiate Radio Link Deletion Requesttowards Node-B.


CRNC Comm Ctxt ID,

Node-B Comm Ctxt ID,

RL ID(s)

Channels

SSCF : SSCOP : AAL5





Iu Connection ReleaseRRC Connection Release


[ RL ID(s) ]



80/161

80

Channels Main IEs

RNC MSCNode-BUE


UpdateUE Context Cleanup:NBAP Radio Link Deletion Response Message

Description: On reception Radio Link Deletion Request, Node-B release all resources associated with respective

RL Ids. On success, respond with Radio Link Deletion Responsemessage to RNC.


CRNC Communication

Context ID,

Channels

SSCF : SSCOP : AAL5







[ RL ID(s) ]





81/161

81

Channels Main IEs

RNC MSCNode-BUE


UpdateUE Context Cleanup:ALCAP Release Request/Confirm Message

Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data stream. RNC ALCAP

request release with Release Requestmessage, Node-B ALCAP confirms it with Release Confirmmessage.

Main IEsDSAID

Cause

DSAID

Channels

STC.2 / SSCF : SSCOP : AAL5







[ RL ID(s) ]



ALCAPALCAPALCAP Release Request

[ DSAID, Cause ]

ALCAPALCAPALCAP Release Confirm

[ DSAID ]



82/161

82

Channels Main IEs

RNC MSCNode-BUE


UpdateLocation Update Complete!!..

Main IEsChannels






UE Context Cleanup

Connection Management CS Call


83/161

83

Connection Management CS Call

Setup and ReleaseRNC MSC/VLRNode-BUERRC Connection Establishment

Signalling Connection Establishment (Service Request Procedure)

Identification /Authentication / Security Procedure (Optional!!)

Call Setup Procedure


UE Context Cleanup


RAB Assignment Procedure ( Iu,IuB,UuSetups!! )

Call Connect Procedure

Iu Resource SetupIuB Resource Setup

Radio Bearer (Uu) Setup

Call Release Procedure

Call Connected : Voice Transfer!!

Connection ManagementCS Call


84/161

84

Channels Main IEs

RNC MSCNode-BUE

o ect o a age e t S a

Setup and ReleaseSignalling Connection Establishment:RRC Initial Direct Transfer Message

Description: On successful establishment of RRC Connection, UE MM sends Service Request message, encoded

NAS message, enclosed in RRC Initial Direct Transfermessage on DCCH.


CN Domain Identity [e.g. CS,

PS],


CM service request, Service

type, CKSN, Classmark, .. ]

Measurement Results

Channels

DCCH : DCH : DPDCH






85/161

85

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseSignalling Connection Establishment:RANAP Initial UE Message

Description: RNC uses received CN domain identity in Initial Direct TransferMessage, and initiate Iu (Iu-CS)

connection setup, and transfer of received Initial UE NAS message using RANAP to core network (MSC/VLR).

Main IEsCN Domain ID [CS or PS]


SAI, etc..]

NASPDU [ EncodedCM

service request, Service type,

CKSN, Classmark, .. ]

Global RNC ID

Iu Signalling Connection

Identifier

Channels









SCCPSCCP Connection Request (CR)[ Reference, SRC/DST Add, User Data ]Iu (Iu-CS!!) Connection Setup;







86/161

86

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseSignalling Connection Establishment:RANAP Direct Transfer Message

Description: Core network MM confirms CM Service Request acceptance, using CM Service Acceptmessage to

UE. MSC transfers CM Service Accept, encoded NAS PDU, in RANAP Direct Transfermessage to RNC.

Main IEsNASPDU [ EncodedCM

service Accept, Only message

type!! ]

Channels















[ NAS PDU (CM Service Accept) ]



87/161

87

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseSignalling Connection Establishment:RRC Downlink Direct Transfer Message

Description: RNC RRC encodes received NAS PDU, in RANAP Direct Transfer message, into RRC Downlink Direct

Transfer message and send it to UE on DCCH (SRB-3).


CN Domain ID (CS!!),

NASPDU [ EncodedCM

service Accept, Only message

type!! ]

Channels

DCCH : DCH : DPDCH














[ NAS PDU (CM Service Accept) ]





88/161

88

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseIdentification/Authentication/Security Procedure:UE RNC CN

Description: After successful establishment of signalling connection, optionally, CN NAS initiates identification,

authentication and security procedures.

Main IEsChannels






89/161

89

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseCall Setup Procedure:RRC Uplink Direct Transfer Message

Description: After service accept and security procedure, UE (CC) UE initiates Call SetupMessage, encoded NAS

PDU, in RRC Uplink Direct Transfermessage on DCCH (SRB-3).




CN Domain ID (CS!!) NAS Msg [ EncodedCall

Setup, Calling/Called Party

No, Bearer Capabilities, .. ]

Channels

DCCH : DCH : DPDCH








90/161

90

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseCall Setup Procedure:RANAP Direct Transfer Message

Description: RNC transparently forwards received NAS PDU, to Core Network (MSC/VLR), using RANAP Direct

TransferMessage.

Main IEsNAS-PDU [EncodedCall

Setup, Calling/Called Party

No, Bearer Capabilities, .. ]

Channels







RANAPRANAP Direct Transfer[ NAS PDU (Call Setup) ]



91/161

91

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseCall Setup Procedure:RANAP Direct Transfer Message

Description: MSC Call Control functionality analyze received information in Call Setupmessage; responds back to

UE with Call Proceeding, encoded NAS PDU, using RANAP Direct TransferMessage towards RNC.

Main IEsNAS-PDU [EncodedCall

Proceeding, Chosen Bearer

Capabilities, Priority, ..]

Channels









[ NAS PDU (Call Proceeding) ]



92/161

92

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseCall Setup Procedure:RRC Downlink Direct Transfer Message






CN Domain ID (CS!!) NAS-PDU [EncodedCall

Proceeding, Chosen Bearer

Capabilities, Priority, ..]

Channels









[ NAS PDU (Call Proceeding) ]





93/161

93

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseRAB Assignment Procedure:RANAP RAB Assignment Request Message

Description: After accepting call setup request, MSC initiates RAB setup, using RANAP RAB Assignment Request

message towards RNC.

Main IEsRAB Setup list, RAB ID

RAB Info [e.g. QoS Info,

Alloc/Ret Priority, ..]

SDU Params per Sub-flow

[BLER, BER, SDU Format info

combination(SDU Size)]

User Plane Info[mode,ver]

Transport Layer Info [ i.e.

TLA, Binding ID ]

Channels






RANAPRANAP RAB Assignment Request[ RAB ID, RAB Params, User Plane Info ]



94/161

94

Channels Main IEs

RNC MSCNode-BUE

g

Setup and ReleaseRAB Assignment Procedure:ALCAP Establish Request/Confirm Message

Description: RNC initiates AAL2 bearer establishment towards MSC, using received AAL2 TLA & Binding ID. MSC

ALCAP verifies received Binding ID; and respond successful establishment with ALCAP ECF Message.




OSAID,

DSAID

Channels

STC.1 : MTP3b : SAAL : AAL5






ALCAPALCAPALCAP Establish Confirm

[ OSAID,DSAID ]

ALCAPALCAPALCAP Establish Request

[ OSAID,DSAID,SUGR,AAL2 Address ]

triggers



95/161

95

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:IuUP INIT and INIT ACK Frame

Description: After successful AAL2 bearer creation, RNC IuUP initiates initialization procedure with peer IuUP in

MSC, to negotiate IuUP version and supported RFCIs (i.e. SDU Sizes, Inter-Frame Time, etc) for this Call.

Main IEsIuUP Version

Number of Sub-flows in

evey RFCI

RFCIs, SDU Sizes

Channels

FP: AAL2







[ OSAID,DSAID ]


[ OSAID,DSAID,SUGR,AAL2 Address ]

IuUPIuUPINITIALIZATION ACK

IuUPIuUPINITIALIZATION

[ IuUP Version, RFCIs, SDU Sizes ]

triggers



96/161

96

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:NBAP RL Reconfiguration Prepare Message

Description: After (or along with!!) Iu resource allocation, RNC reserves additional radio resources, according to

RAB requirement and initiates resource allocation over IuB, using NBAP RL Reconfiguration PrepareMessage.

Main IEsNodeB Comm Ctxt ID,

UL/DL DPCH info [ e.g.

Codes, TFCS, etc ]

DCH info [ e.g. TrCH ID,

UL/DL TFS, Window(ToAWS,

ToAWE), Priority, etc..]

RL Info, [e.g. RL ID, DL Code,

Power Information, Max/Min

DL power, etc ]

Channels

SSCF : SSCOP : AAL5





RAB Assignment Procedure (Iu Setup)NBAPNBAP

RL Reconfiguration Prepare[ UL/DL DPCH info, RL info, DCH ]



97/161

97

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:NBAP RL Reconfiguration Ready Message

Description: Node B reserves necessary resources for new configuration of Radio Link(s), Coordinated DCH for

Voice, etc according to received parameters; and send success response to RNC.


CRNC Comm Ctxt ID,

RL IDs

DCH Info Response [ e.g.



Channels

SSCF : SSCOP : AAL5





RAB Assignment Procedure ( IuSetup )NBAPNBAP


NBAPNBAPRL Reconfiguration Ready

[ TLA, Binding ID ]



98/161

98

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:ALCAP Establish Request/Confirm Message

Description: RNC initiates AAL2 bearer establishment for voice DCH, using received AAL2 TLA & Binding ID.

Node-B ALCAP verifies received Binding ID; and respond successful establishment with ALCAP Confirm Msg.




OSAID,

DSAID

Channels

STC.2 : SSCF : SSCOP : AAL5








[ TLA, Binding ID ]


[ OSAID, DSAID, SUGR, AAL2 Address ]


[ OSAID, DSAID ]



99/161

99

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:FP DL/UL Synchronization Frames

Description: New DCH voice FP initiates L2 synchronization using DL synchronizationframe with current CFN.

Node-B FP(peer!!) verifies CFN to SFN relationship; & respond back with ToA(required timing adjustment) info


Number)


Number),

ToA (Time of Arrival)

Channels









[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]




100/161

100

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:NBAP RL Reconfiguration Commit Message

Description: After successful Iu, IuB Resource setup (and User Plane, L1/L2 at RNC!!), RNC calculates CFN,

activation time, for this synchronized procedure; and provide same to Node-B (and UE along with RB Setup!!).


Node-B Communication

Context ID,


NumberActivation time for

new configuration!!)

Channels









[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]


NBAPNBAPRL Reconfiguration Commit

[ Activation CFN ]



101/161

101

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:RRC Radio Bearer Setup Message

Description: On successful Iu, IuB resource (and User Plane, L1/L2 at RNC!!), RNC initiates Radio Bearer Setup

towards UE on DCCH, for requested voice RAB, with selected configuration and allocated resource information.

Main IEsActivation time (CFN!!)

RB info [ RAB ID, CN ID, RLC

Config, RB mapping ..]

RRC State (Cell DCH!!)

TrCH info [ UL/DL TFCS, DCH

IDs, TFS, etc.. ]

Radio info[e.g. Frequency,

Codes, Power info, etc.. ]

Channels

DCCH : DCH : DPDCH





RAB Assignment Procedure ( Iu,IuBSetup!! )

RRCRRCDCCH: Radio Bearer Setup

[ Integrity Check Info, Activation CFN, RB Setup info, TrCH info, RL info ]



102/161

102

Channels Main IEs

RNC MSCNode-BUE

Setup and ReleaseRAB Assignment Procedure:RRC Radio Bearer Setup Complete Message

Description: UE RRC validates, received RB setup configuration, stores it and activates the same at specified

activation CFN. After activation of new configuration, it sends Radio Bearer Setup Completemessage to RNC.



MAC, RRC Msg Seq no ]

START Value (CS!!)

Ciphering Count-C

Activation Time (CFN!!)

Channels

DCCH : DCH : DPDCH


Signalling Connection Establishment (Ser

umts call flow scenarios overview

Documents