Umts call-flow-scenarios overview

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

Introduction

• UE Connection States

• RNC Cell and UE Contexts

• End to End Protocol Stacks (CS and PS Domain)

• Handover Scenarios

3

UE Connection States GSM

Connected Mode

UTRAN RRC Connected

GPRS Packet

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

UE #M

UE #2

UE #1

DTCH’s

CELL #N

CELL #2

CELL #1

RLC-TM RLC-TM

RNC – Cell and UE Contexts

PHY-Upper

MAC–d

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

MAC–c

RRC

SRB

RLC-TM RLC-UM RLC-TM

SRB #0 SRB #0

CCCH CCCH PCCH

PCH FP FACH FP RACH FP

FACH PCH RACH

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

DCH’s

MAC-d MAC-c/sh

Flows

5

CS Domain – End to End Protocols

PHY

PHY [E1/T1/STM]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

ALCAP

PHY

PHY-upper

MAC

RLC

RRC Codec

MM

CC

PHY [E1/T1/STM]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

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-MSC Uu IuB Iu-CS

6

PS Domain – End to End Protocols

PHY

PHY [E1/T1]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

ALCAP

PHY

PHY-upper

MAC

RLC

RRC PDCP

GMM

SM

PHY [E1/T1/STM-1]

ATM

AAL2

FP

AAL5

SSCOP

SSCF-UNI

STC.2 NBAP

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-SGSN Uu 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-GGSN Gn

7

Handover Scenarios

UTRAN

RNS

Node-B Node-B

RNC

RNS

Node-B Node-B

RNC

Core Network (CN)

UE

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

Node-B Initialization

RNC MSC Node-B UE

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

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Audit Procedure: Audit Required Indication Message

Description: 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 PDU’s.

Main IEs Transaction ID

Channels

SSCF / SSCOP / AAL5

NBAP NBAP Audit Required Indication

[ Transaction ID ]

11

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Audit Procedure: Audit Request Message

Description: 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.

Main IEs Transaction ID Start of audit sequence ind

Channels

SSCF / SSCOP / AAL5


[ Transaction ID ]

NBAP NBAP Audit Request

[ Transaction ID, Start of Audit Seq Ind ]

12

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Audit Procedure: Audit Response Message

Description: Node-B sends Audit response to RNC, with its current configuration and status of logical resources, using Audit Response message.

Main IEs Transaction ID End of audit sequence ind

Cell Info (Configured) Local Cell Information

Communication Control Port information

Channels

SSCF / SSCOP / AAL5


[ Transaction ID ]

NBAP NBAP Audit Request

[ Transaction ID, Start of Audit Seq Ind ]

NBAP NBAP Audit Response

[ End of Audit Seq Ind, Local Resource Info ]

13

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Cell Setup Procedure: Resource Status Indication Message

Description: 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.

Main IEs Transaction ID No Failure Indication

Local Cell ID Add/Delete Indicator

Channels

SSCF / SSCOP / AAL5

NBAP NBAP Resource Status Indication

[ Local Cell ID, Add/Delete Indicator ]

Audit Procedure

14

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Cell Setup Procedure: Cell Setup Request Message

Description: RNC initiates Cell Configuration/Setup, which will use resources in Node-B identified by Local Cell ID, received in Resource Status Indication message.

Main IEs Transaction 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

NBAP NBAP Cell Setup Request

[ Global/Local Cell ID, Physical Config. ]

15

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Cell Setup Procedure: Cell Setup Response Message

Description: Node B reserves necessary resources and configure the new cell according to received parameters, and on success sends Cell Setup Response to RNC. (On failure, Cell Setup Failure response will be sent!!)


Channels

SSCF / SSCOP / AAL5



Audit Procedure



NBAP NBAP Cell Setup Response

[ Transaction ID ]

16

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Cell Setup Procedure: Block Resource Request Message

Description: 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).

Main IEs Transaction ID Global (C-ID) Cell ID Blocking Priority (High!!)

Channels

SSCF / SSCOP / AAL5



Audit Procedure




[ Transaction ID ]

NBAP NBAP Block Resource Request

[ Transaction ID, Blocking Priority ]

17

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Cell Setup Procedure: Block Resource Response Message

Description: RNC Blocks respective resource (cell!!), and send successful response to the Node-B.


Channels

SSCF / SSCOP / AAL5



Audit Procedure




[ Transaction ID ]

NBAP NBAP Block Resource Request

[ Transaction ID, Blocking Priority ]

NBAP NBAP Block Resource Response

[ Transaction ID ]

18

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization System Info Update Procedure: System Info Update Request Message

Description: RNC sends System Information, Scheduling Information, System Information Update time, etc of respective configured cell to Node-B using series of System Information Update Request message.

Main IEs Transaction ID Global (C-ID) Cell ID BCCH Modification Time

MIB, SB, SIB info Segment Info

Channels

SSCF / SSCOP / AAL5

Audit Procedure

NBAP NBAP System Information Update Request

[ SIB segment info. ]


19

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization System Info Update Procedure: System Info Update Response Message

Description: Node-B process received System Information, Scheduling Information, System Information Update time, etc and send successful response using System Information Update Response message.

Main IEs Transaction ID Global (C-ID) Cell ID

Channels

SSCF / SSCOP / AAL5

Audit Procedure




NBAP NBAP System Information Update Response




Segment 1

Segment 2

20

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization System Info Update Procedure: RRC System Information Message

Description: 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 IEs Master Information Block, Scheduling Block,

System Information Block

Channels

BCCH / BCH / PCCPCH

Audit Procedure








Segment 1

Segment 2

RRC RRC BCCH: System Information


21

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: Common TrCH Setup Request Message

Description: 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 IEs Transaction 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



NBAP NBAP Common TrCH Setup Request

[PRACH, AICH, RACH]

22

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: Common TrCH Setup Response Message

Description: 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 IEs Transaction ID,

RACH parameters [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure




[PRACH, AICH, RACH]

NBAP NBAP Common TrCH Setup Response

[TLA, Binding ID]

23

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: ALCAP Establish Request Message

Description: RNC initiates establishment of AAL2 bearer for RACH, using received Transport Layer Address and Binding ID information, in response from Node-B.

Main IEs OSAID / 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




[PRACH, AICH, RACH]


[TLA, Binding ID]

ALCAP ALCAP ALCAP Establish Request (ERQ)

[OSAID,DSAID,SUGR,AAL2 Address]

24

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: ALCAP Establish Confirm Message

Description: Node-B ALCAP verifies received Binding ID; and respond successful establishment of AAL2 bearer using ALCAP confirm message.

Main IEs OSAID DSAID

Channels


Audit Procedure




[PRACH, AICH, RACH]


[TLA, Binding ID]

ALCAP ALCAP ALCAP Establish Confirm (ECF)

[OSAID,DSAID]



25

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: Common TrCH Setup Request Message

Description: 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 IEs Transaction 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





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

26

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: Common TrCH Setup Response Message

Description: 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 IEs Transaction ID,

PCH parameters [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

FACH(s) parameters [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure






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


27

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: ALCAP Establish Request Message

Description: 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 IEs OSAID DSAID + CEID

SUGR (Binding ID!!) AAL2 Destination Address of Node-B

Channels


Audit Procedure







ALCAP ALCAP ALCAP ERQ



For PCH & FACH(s) bearers

28

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: ALCAP Establish Confirm Message

Description: Node-B ALCAP verifies received Binding ID; and respond successful establishment of AAL2 bearer using ALCAP confirm message.

Main IEs OSAID DSAID

Channels


Audit Procedure










[OSAID,DSAID]



29

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: FP DL Synchronization Frame

Description: After successful establishment of AAL2 bearer, at RNC, PCH and FACH(s) FPs initiates L2 synchronization by sending DL synchronization control frame with current CFN.

Main IEs CFN (Connection Frame Number)

Channels

FP / AAL2

Audit Procedure










[OSAID,DSAID]

FP FP DL Synchronization

[ CFN ]



30

Channels Main IEs

RNC MSC Node-B UE

Node-B Initialization Common TrCH Setup Procedure: FP UL Synchronization Frame

Description: 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.

Main IEs CFN (Connection Frame Number), ToA [Time of Arrival]

Channels

FP / AAL2

Audit Procedure










[OSAID,DSAID]


[ CFN ]

FP FP UL Synchronization

[ CFN, ToA ]



31

Channels Main IEs

RNC MSC Node-B UE


Description: 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.


BCCH Modification Time 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

Channels Main IEs

RNC MSC Node-B UE


Description: 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

Channels Main IEs

RNC MSC Node-B UE


Description: 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!!)

Main IEs Transaction ID Communication Control Port ID

Channels

SSCF / SSCOP / AAL5

Audit Procedure





NBAP NBAP Resource Status Indication [ Communication Control port ID ]


34

Channels Main IEs

RNC MSC Node-B UE


Description: 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






NBAP NBAP Unblock Resource Indication

[ C-ID ]


35

Channels Main IEs

RNC MSC Node-B UE


Description: After successful unblocking cell resource, RNC sends updated SIB3 System Information (with cell status as unbarred!!) to Node-B.

Main IEs Transaction ID Global (C-ID) Cell ID BCCH Modification Time

Reference to other SIBs Segment info [ SIB3 with Cell status unbarred!! ]

Channels

SSCF / SSCOP / AAL5

Audit Procedure







[ C-ID ]




36

Channels Main IEs

RNC MSC Node-B UE


Description: 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

Channels Main IEs

RNC MSC Node-B UE

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

Main IEs Channels

Audit Procedure






Un-block and Un-barred Cell

38

RRC Connection Management

RNC MSC Node-B UE

Random Access Procedure

RRC Connection Request

UE Context Setup

RRC Connection Setup

RRC Connection Release

UE Context Cleanup

39

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Random Access Procedure: System Information Broadcast

Description: 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 IEs Master Information Block, Scheduling Block,

System Information Block [SIB 1, SIB 2, SIB 3, etc..]

Channels

BCCH / BCH / PCCPCH



40

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Random Access Procedure: Physical Layer Access attempts

Description: 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 IEs Signature Sequence

Channels

PRACH



PHY PHY Preamble

PHY Preamble

PHY Preamble

Wait for AICH response, No response, Step-up power!! Retransmit Preamble


41

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Random Access Procedure: Physical Layer Access detection

Description: 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 IEs AICH Response Sequence

Channels

AICH



PHY PHY Preamble

PHY Preamble

PHY Preamble



PHY PHY Access Indication

42

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Initial Access Request: RRC Connection Request Message

Description: On successful physical layer access detection, UE transmits RRC Connection Request message to network on RACH : PRACH.

Main IEs Initial 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


RRC RRC CCCH: RRC Connection Request

PHY PHY RACH Message

[ Data, Control (TFCI) ]

FP FP RACH Data Frame

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

RLC

MAC RLC

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

43

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE Context Setup Procedure: Radio Link Setup Request Message

Description: 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 IEs Cell 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

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

44

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE Context Setup Procedure: Radio Link Setup Response Message

Description: On reception Radio Link Setup Request message, Node-B reserves necessary resources and configure new radio link(s) according to received parameters, and respond success to RNC.

Main IEs Transaction ID, Node-B Communication Context ID

DCH parameters [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

Channels

SSCF / SSCOP / AAL5



NBAP NBAP Radio Link Setup Request

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

45

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE Context Setup Procedure: ALCAP Establish Request/Confirm Message

Description: 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 IEs OSAID, DSAID + CEID, SUGR (Binding ID!!), AAL2 destination Address

OSAID, DSAID

Channels

SSCF / SSCOP / AAL5




NBAP NBAP Radio Link Setup Response




[OSAID,DSAID]

46

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE Context Setup Procedure: FP DL/UL Synchronization Frame

Description: At RNC, DCH FP initiates L2 synchronization using DL synchronization Control Frame with CFN. Node-B DCH FP verifies CFN to SFN relationship; & respond back with ToA(required timing adjustment) Info.


CFN (Connection Frame Number), ToA (Time of Arrival)

Channels

FP / AAL2




NBAP NBAP Radio Link Setup Response




[ CFN ]


[ CFN, ToA ]

47

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Initial Access Response: RRC Connection Setup Message

Description: On successful setup of UE context, RNC sends RRC Connection Setup message to UE over CCCH : FACH : SCCPCH, with information about allocated resources/configuration.

Main IEs Received 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

RRC RRC CCCH: RRC Connection Setup

PHY PHY SCCPCH Message [ Data, Control (TFCI) ]

FP FP FACH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MAC RLC

MAC RRC Connection Setup message would be split into several TB(s), hence this sequence will repeat!!

48

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management Initial Access Response: RRC Connection Setup Complete Message

Description: On reception of RRC Connection Setup message, UE configures its L1, L2 according RRC state and respective received parameters, and responds to RNC using RRC Connection Setup Complete message.

Main IEs RRC transaction ID, START List [CS, PS]

Radio Access Capabilities [e.g. Basic, extended, inter-system, etc]

Channels

DCCH : DCH : DPDCH



UE Context Setup

RRC RRC CCCH: RRC Connection Setup

PHY PHY SCCPCH Message [ Data, Control (TFCI) ]

FP FP FACH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MAC RLC

MAC RRC Connection Setup message would be split into several TB(s), hence this sequence will repeat!!

RRC RRC DCCH: RRC Connection Setup Complete

RLC

MAC

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

FP FP DCH Data Frame


RLC

MAC

49

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management RRC Connection Release: RRC Connection Release Message

Description: RNC anytime can release RRC Connection in Cell FACH or Cell DCH state, by sending RRC Connection Release message on DCCH. [exceptionally on CCCH, when UE in Cell FACH state!!]

Main IEs RRC transaction ID,

Release Cause[e.g. normal, inactivity, directed re-establishment, congestion, ..]

Rplmn information

Channels

DCCH : DCH : DPDCH



UE Context Setup


RRC RRC DCCH: RRC Connection Release

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

FP FP DCH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MAC RLC

MAC

50

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management RRC Connection Release: RRC Connection Release Complete Message

Description: On reception of RRC Connection Release message, responds to RNC with RRC Connection Release Complete message on DCCH, terminates RRC Connection and move to idle state.

Main IEs RRC transaction ID

Channels

DCCH : DCH : DPDCH



UE Context Setup



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

FP FP DCH Data Frame(s)

[ CFN, TFI, TB(s) ]

RLC

MAC RLC

MAC

RRC RRC DCCH: RRC Connection Release Complete

RLC

MAC

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

FP FP DCH Data Frame


RLC

MAC

51

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE Context Cleanup: NBAP Radio Link Deletion Request Message

Description: On reception of RRC Connection Release Complete message, RNC initiates cleanup of UE context. If RRC Connection in Cell DCH state, initiate Radio Link Deletion Request towards Node-B.

Main IEs Transaction ID, CRNC Comm Ctxt ID, Node-B Comm Ctxt ID,

RL ID(s)

Channels

SSCF : SSCOP : AAL5



UE Context Setup



NBAP NBAP Radio Link Deletion Request

[ RL ID(s) ]

52

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE 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 Response message to RNC.

Main IEs Transaction ID, CRNC Communication Context ID

Channels

SSCF : SSCOP : AAL5



UE Context Setup




NBAP NBAP Radio Link Deletion Response

[ CRNC Comm Ctxt ID ]

53

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management UE 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 Request message, Node-B ALCAP confirms it with Release Confirm message.

Main IEs DSAID Cause

DSAID

Channels

STC.2 / SSCF / SSCOP / AAL5



UE Context Setup





ALCAP ALCAP ALCAP Release Request

[ DSAID, Cause ]

ALCAP ALCAP ALCAP Release Confirm

[ DSAID ]

54

Channels Main IEs

RNC MSC Node-B UE

RRC Connection Management RRC Connection Established and Released!!..

Main IEs Channels



UE Context Setup



UE Context Cleanup

55

Mobility Management – Location Update

RNC MSC/VLR Node-B UE

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

Channels Main IEs

RNC MSC Node-B UE


Signalling Connection Establishment: RRC Initial Direct Transfer Message

Description: On successful establishment of RRC Connection, UE sends first NAS message, enclosed in RRC Initial Direct Transfer message on DCCH.

Main IEs RRC transaction ID, CN Domain Identity [e.g. CS, PS],

NAS Message [ Encoded – Update Type, Cipher Key Seq No, LAI, Classmark, .. ]

Measurement Results

Channels

DCCH : DCH : DPDCH


RRC RRC DCCH: Initial Direct Transfer

[ CN Domain ID, NAS Message ]

57

Channels Main IEs

RNC MSC Node-B UE


Signalling Connection Establishment: RANAP Initial UE Message

Description: RNC uses received CN domain identity in Initial Direct Transfer Message, and initiate Iu (Iu-CS) connection setup, and transfer of received Initial UE NAS message using RANAP to core network (MSC/VLR).

Main IEs CN Domain ID [CS or PS] Location Info [ e.g. LAI, RAC, SAI, etc..]

NAS–PDU [ Encoded – Update Type, Cipher Key Seq No, LAI, Classmark, .. ]

Global RNC ID Iu Signalling Connection Identifier

Channels

SCCP : MTP3b : SAAL : AAL5




RANAP RANAP Initial UE Message

[ CN Domain ID, LAI, NAS-PDU ]

SCCP SCCP Connection Confirm (CC)

[ SRC/DST References ]

SCCP SCCP Connection 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

Channels Main IEs

RNC MSC Node-B UE


Identification 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 Transfer Message to RNC.

Main IEs NAS–PDU [ Encoded – Identity Request, Identity Type (e.g. IMSI, TMSI, etc)]

Channels




RANAP RANAP Direct Transfer

[ NAS PDU (Identity Request!!) ]

59

Channels Main IEs

RNC MSC Node-B UE


Identification Procedure: 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).

Main IEs RRC Transaction ID, CN Domain ID [CS or PS],

NAS Message [ Encoded – Identity Request, Identity Type (e.g. IMSI, TMSI, etc)]

Channels

DCCH : DCH : DPDCH



RRC RRC DCCH: Downlink Direct Transfer




60

Channels Main IEs

RNC MSC Node-B UE


Identification 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).


NAS Message [ Encoded – Identity Response, Requested Identity Value ]

Channels

DCCH : DCH : DPDCH







RRC RRC DCCH: Uplink Direct Transfer


61

Channels Main IEs

RNC MSC Node-B UE


Identification Procedure: RANAP Direct Transfer Message

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

Main IEs NAS Message [ Encoded – Identity Response, Requested Identity Value ]

Location Info [ e.g. LAI, RAC, SAI, etc..] optional

Channels











[ NAS PDU (Identity Response!!) ]

62

Channels Main IEs

RNC MSC Node-B UE


Authentication 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 Transfer Message to RNC.

Main IEs NAS–PDU [ Encoded – Authentication Request, CKSN, RAND, AUTN, .. ]

Channels





[ NAS PDU (Authentication Request!!) ]

Identification Procedure

63

Channels Main IEs

RNC MSC Node-B UE


Authentication Procedure: RRC Downlink Direct Transfer Message



NAS Message [ Encoded – Authentication Request, CKSN, RAND, AUTN, .. ]

Channels

DCCH : DCH : DPDCH








64

Channels Main IEs

RNC MSC Node-B UE


Authentication 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).


NAS Message [ Encoded – Authentication Response, SRES (UE Calculated!!) ]

Channels

DCCH : DCH : DPDCH










65

Channels Main IEs

RNC MSC Node-B UE


Authentication Procedure: RANAP Direct Transfer Message


Main IEs NAS Message [ Encoded – Authentication Response, SRES (UE Calculated!!) ]


Channels











[ NAS PDU (Authentication Response!!) ]


66

Channels Main IEs

RNC MSC Node-B UE


Security Procedure: RANAP Security Mode Command Message

Description: MSC (optionally!!) initiates Security Procedure, using RANAP Security Mode Command Message to RNC.

Main IEs Integrity Protection Info [e.g. Permitted algorithms, Integrity Protection Key, . ]

Encryption Info [e.g. Permitted Algorithm Set, Encryption Key, . ]

Key Status [Old or New]

Channels




RANAP RANAP Security Mode Command

[ Integrity Protection, Encryption info ]

Identification / Authentication Procedure

67

Channels Main IEs

RNC MSC Node-B UE


Security Procedure: RRC Security Mode Command Message

Description: RNC RRC initiates security procedure, by sending RRC Security Mode Command message to UE on DCCH (SRB-2).

Main IEs CN 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



RRC RRC DCCH: Security Mode Command

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




68

Channels Main IEs

RNC MSC Node-B UE


Security 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).

Main IEs RRC Transaction ID, Integrity Check Info [ i.e. MAC, RRC Msg Seq No ]

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








RRC RRC DCCH: Security Mode Complete

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

69

Channels Main IEs

RNC MSC Node-B UE


Security Procedure: RANAP Security Mode Complete Message

Description: RNC send successful response of Security Procedure, using RANAP Security Mode Complete message towards MSC.

Main IEs Chosen Integrity Protection Algorithm [ i. e. UIA1 ]

Chosen Encryption Algorithm [ No Encryption, or, UEA1 ]

Channels











RANAP RANAP Security Mode Complete

[ Chosen Integrity, Encryption Algorithm ]

70

Channels Main IEs

RNC MSC Node-B UE


Security Procedure: RANAP Common ID Message

Description: MSC provide permanent NAS UE identity (i.e. IMSI) to RNC using RANAP Common ID message. RNC use same for paging co-ordination functionality.

Main IEs Permanent NAS UE identity ( i.e. IMSI value )

Channels











RANAP RANAP Security Mode Complete

[ Chosen Integrity, Encryption Algorithm ]

RANAP RANAP Common ID

[ Permanent NAS UE Identity ]

71

Channels Main IEs

RNC MSC Node-B UE


Location Update Accept Procedure: RANAP Direct Transfer Message

Description: Core network MM confirms location update procedure by Location Update Accept message to UE. MSC transfers Location Update Accept, encoded NAS PDU, in RANAP Direct Transfer message to RNC.

Main IEs NAS–PDU [ Encoded – Location Update Accept, LAI, New mobile id(TMSI),]

Channels





[ NAS PDU (Location Update Accept) ]

Identification / Authentication / Security Procedure

72

Channels Main IEs

RNC MSC Node-B UE


Location Update Accept Procedure: RRC Downlink Direct Transfer Message



CN Domain ID [CS or PS] NAS–PDU [ Encoded – Location Update Accept, LAI, New mobile id(TMSI),]

Channels

DCCH : DCH : DPDCH







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

73

Channels Main IEs

RNC MSC Node-B UE


Location 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 Transfer message.


CN Domain ID [CS or PS] NAS–PDU [ Encoded – TMSI Reallocation Complete Message Type ]

Channels

DCCH : DCH : DPDCH










74

Channels Main IEs

RNC MSC Node-B UE


Location Update Accept Procedure: RANAP Direct Transfer Message


Main IEs NAS–PDU [ Encoded – TMSI Reallocation Complete Message Type ]


Channels












[ NAS PDU (TMSI Realloc Complete) ]

75

Channels Main IEs

RNC MSC Node-B UE


Iu 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 Command towards RNC.

Main IEs Cause ( Normal Release!! )

Channels






RANAP RANAP Iu Release Command

[ Cause ]

76

Channels Main IEs

RNC MSC Node-B UE


Iu Connection Release: RANAP Iu Release Complete Message

Description: RNC confirms Iu signalling connection release, using RANAP Iu Release Complete message to CN. It also initiates lower layer (SCCP) connection release, established for respective Iu signalling Connection.

Main IEs Channels







[ Cause ]

RANAP RANAP Iu Release Complete

SCCP SCCP Released

[ SRC/DST References, Cause ]

SCCP SCCP Release Complete [ SRC/DST References ]

triggers

77

Channels Main IEs

RNC MSC Node-B UE


RRC Connection Release: RRC Connection Release Message

Description: RNC initiates RRC connection release, by sending RRC Connection Release message to UE on DCCH (SRB1).

Main IEs RRC transaction ID, Integrity Check Info [ i.e. MAC, RRC Msg Seq No ]

Release Cause[e.g. normal, inactivity, directed re-establishment, congestion, ..]

Rplmn information

Channels

DCCH : DCH : DPDCH







[ Integrity Check info, Release Cause ]

triggers

78

Channels Main IEs

RNC MSC Node-B UE


RRC 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








triggers


[ Integrity Check info ]

79

Channels Main IEs

RNC MSC Node-B UE


UE Context Cleanup: NBAP Radio Link Deletion Request Message

Description: On reception of RRC Connection Release Complete message, RNC initiates cleanup of UE context. If RRC Connection in Cell DCH state, initiate Radio Link Deletion Request towards Node-B.


RL ID(s)

Channels

SSCF : SSCOP : AAL5





Iu Connection Release RRC Connection Release


[ RL ID(s) ]

80

Channels Main IEs

RNC MSC Node-B UE


UE 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 Response message to RNC.

Main IEs Transaction ID, CRNC Communication Context ID,

Channels

SSCF : SSCOP : AAL5







[ RL ID(s) ]



81

Channels Main IEs

RNC MSC Node-B UE


UE 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 Request message, Node-B ALCAP confirms it with Release Confirm message.


DSAID

Channels

STC.2 / SSCF : SSCOP : AAL5







[ RL ID(s) ]




[ DSAID, Cause ]


[ DSAID ]

82

Channels Main IEs

RNC MSC Node-B UE


Location Update Complete!!..

Main IEs Channels






UE Context Cleanup

83

Connection Management – CS Call Setup and Release RNC MSC/VLR Node-B UE


Signalling Connection Establishment (Service Request Procedure)


Call Setup Procedure


UE Context Cleanup


RAB Assignment Procedure ( Iu, IuB, Uu Setups!! )

Call Connect Procedure

Iu Resource Setup IuB Resource Setup

Radio Bearer (Uu) Setup

Call Release Procedure

Call Connected : Voice Transfer!!

84

Channels Main IEs

RNC MSC Node-B UE

Connection Management – CS Call Setup and Release


Description: On successful establishment of RRC Connection, UE MM sends Service Request message, encoded NAS message, enclosed in RRC Initial Direct Transfer message on DCCH.

Main IEs RRC transaction ID, CN Domain Identity [e.g. CS, PS],

NAS Message [ Encoded – CM service request, Service type, CKSN, Classmark, .. ]

Measurement Results

Channels

DCCH : DCH : DPDCH




85

Channels Main IEs

RNC MSC Node-B UE



Description: RNC uses received CN domain identity in Initial Direct Transfer Message, and initiate Iu (Iu-CS) connection setup, and transfer of received Initial UE NAS message using RANAP to core network (MSC/VLR).


NAS–PDU [ Encoded – CM service request, Service type, CKSN, Classmark, .. ]


Channels














86

Channels Main IEs

RNC MSC Node-B UE


Signalling Connection Establishment: RANAP Direct Transfer Message

Description: Core network MM confirms CM Service Request acceptance, using CM Service Accept message to UE. MSC transfers CM Service Accept, encoded NAS PDU, in RANAP Direct Transfer message to RNC.

Main IEs NAS–PDU [ Encoded – CM service Accept, Only message type!! ]

Channels















[ NAS PDU (CM Service Accept) ]

87

Channels Main IEs

RNC MSC Node-B UE


Signalling Connection Establishment: RRC Downlink Direct Transfer Message


Main IEs RRC Transaction ID, CN Domain ID (CS!!),

NAS–PDU [ Encoded – CM service Accept, Only message type!! ]

Channels

DCCH : DCH : DPDCH














[ NAS PDU (CM Service Accept) ]



88

Channels Main IEs

RNC MSC Node-B UE


Identification/Authentication/Security Procedure: UE RNC CN Description: After successful establishment of signalling connection, optionally, CN NAS initiates identification, authentication and security procedures.

Main IEs Channels




89

Channels Main IEs

RNC MSC Node-B UE


Call Setup Procedure: RRC Uplink Direct Transfer Message

Description: After service accept and security procedure, UE (CC) UE initiates Call Setup Message, encoded NAS PDU, in RRC Uplink Direct Transfer message on DCCH (SRB-3).


CN Domain ID (CS!!) NAS Msg [ Encoded – Call Setup, Calling/Called Party No, Bearer Capabilities, .. ]

Channels

DCCH : DCH : DPDCH






90

Channels Main IEs

RNC MSC Node-B UE


Call Setup Procedure: RANAP Direct Transfer Message

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

Main IEs NAS-PDU [Encoded – Call Setup, Calling/Called Party No, Bearer Capabilities, .. ]

Channels








[ NAS PDU (Call Setup) ]

91

Channels Main IEs

RNC MSC Node-B UE


Call Setup Procedure: RANAP Direct Transfer Message

Description: MSC Call Control functionality analyze received information in Call Setup message; responds back to UE with Call Proceeding, encoded NAS PDU, using RANAP Direct Transfer Message towards RNC.

Main IEs NAS-PDU [Encoded – Call Proceeding, Chosen Bearer Capabilities, Priority, ..]

Channels










[ NAS PDU (Call Proceeding) ]

92

Channels Main IEs

RNC MSC Node-B UE


Call Setup Procedure: RRC Downlink Direct Transfer Message



CN Domain ID (CS!!) NAS-PDU [Encoded – Call Proceeding, Chosen Bearer Capabilities, Priority, ..]

Channels










[ NAS PDU (Call Proceeding) ]



93

Channels Main IEs

RNC MSC Node-B UE


RAB 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 IEs RAB 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






RANAP RANAP RAB Assignment Request

[ RAB ID, RAB Params, User Plane Info ]

94

Channels Main IEs

RNC MSC Node-B UE


RAB 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.

Main IEs OSAID, DSAID + CEID, SUGR (Binding ID!!), AAL2 Destination Address

OSAID, DSAID

Channels

STC.1 : MTP3b : SAAL : AAL5







ALCAP ALCAP ALCAP Establish Confirm

[ OSAID,DSAID ]

ALCAP ALCAP ALCAP Establish Request

[ OSAID,DSAID,SUGR,AAL2 Address ]

triggers

95

Channels Main IEs

RNC MSC Node-B UE


RAB 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 IEs IuUP Version Number of Sub-flows in evey RFCI

RFCIs, SDU Sizes

Channels

FP: AAL2








[ OSAID,DSAID ]


[ OSAID,DSAID,SUGR,AAL2 Address ]

IuUP IuUP INITIALIZATION ACK

IuUP IuUP INITIALIZATION

[ IuUP Version, RFCIs, SDU Sizes ]

triggers

96

Channels Main IEs

RNC MSC Node-B UE


RAB 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 Prepare Message.

Main IEs NodeB Comm Ctxt ID, UL/DL DPCH info [ e.g. Codes, TFCS, 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) NBAP NBAP

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

97

Channels Main IEs

RNC MSC Node-B UE


RAB 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.

Main IEs Transaction ID, CRNC Comm Ctxt ID, RL IDs

DCH Info Response [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

Channels

SSCF : SSCOP : AAL5





RAB Assignment Procedure ( Iu Setup ) NBAP NBAP


NBAP NBAP RL Reconfiguration Ready

[ TLA, Binding ID ]

98

Channels Main IEs

RNC MSC Node-B UE



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

Channels Main IEs

RNC MSC Node-B UE


RAB Assignment Procedure: FP DL/UL Synchronization Frames

Description: New DCH voice FP initiates L2 synchronization using DL synchronization frame with current CFN. Node-B FP(peer!!) verifies CFN to SFN relationship; & respond back with ToA(required timing adjustment) info



Channels









[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]


[ CFN, ToA ]

100

Channels Main IEs

RNC MSC Node-B UE


RAB 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!!).

Main IEs Transaction ID, Node-B Communication Context ID,

CFN (Connection Frame Number – Activation time for new configuration!!)

Channels









[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]


[ CFN, ToA ]

NBAP NBAP RL Reconfiguration Commit

[ Activation CFN ]

101

Channels Main IEs

RNC MSC Node-B UE


RAB 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 IEs Activation 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, IuB Setup!! )

RRC RRC DCCH: Radio Bearer Setup

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

102

Channels Main IEs

RNC MSC Node-B UE


RAB 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 Complete message to RNC.

Main IEs RRC Transaction ID, Integrity Check Info [ i.e. MAC, RRC Msg Seq no ]

START Value (CS!!) Ciphering Count-C Activation Time (CFN!!)

Channels

DCCH : DCH : DPDCH








RRC RRC DCCH: Radio Bearer Setup Complete

[ RRC Transaction ID, Integrity Check info, START value ]

On activation CFN, Node-B, UE and RNC L1/L2 activates pending new configuration!!.

103

Channels Main IEs

RNC MSC Node-B UE


RAB Assignment Procedure: RANAP RAB Assignment Response Message

Description: On reception of RRC Radio Bearer Setup Complete message, RNC send successful response to RAB Assignment procedure, using RANAP RAB Assignment Response message towards MSC.

Main IEs RAB ID (of successfully established RAB!!)

Assigned (Chosen) RAB Parameters (if RAB QoS negotiation has performed!!)

Channels












RANAP RANAP RAB Assignment Response

[ RAB ID ]

104

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RANAP Direct Transfer Procedure

Description: After called party user reached/alerted, MSC Call Control respond with Alerting message back to UE. Alerting message, encoded NAS PDU, is forwarded using RANAP Direct Transfer Message towards RNC.

Main IEs NAS–PDU [ Encoded – Alerting Message Type, .. ]

Channels






RAB Assignment Procedure ( Iu, IuB, Uu Setup!! )


[ NAS PDU (Alerting) ]

105

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RRC Downlink Direct Transfer Message

Description: RNC RRC transparently 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!!) NAS Message [ Encoded – Alerting Message Type, .. ]

Channels

DCCH : DCH : DPDCH










106

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RANAP Direct Transfer Message

Description: After called party user accept the Call, MSC Call Control respond with Connect message back to UE. Connect message, encoded NAS PDU, is forwarded using RANAP Direct Transfer Message towards RNC.

Main IEs NAS–PDU [ Encoded – Connect Message Type, .. ]

Channels












[ NAS PDU (Connect) ]

107

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RRC Downlink Direct Transfer Message


Main IEs NAS Message [ Encoded – Connect Message Type, .. ]

Channels

DCCH : DCH : DPDCH














108

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RRC Uplink Direct Transfer Message

Description: On reception of Connect message, UE NAS (CC) responds it with Connect Acknowledge message, encoded NAS PDU, in RRC Uplink Direct Transfer Message on DCCH (SRB-3).


CN Domain ID (CS!!) NAS Message [ Encoded – Connect Acknowledge Message Type, .. ]

Channels

DCCH : DCH : DPDCH
















109

Channels Main IEs

RNC MSC Node-B UE


Call Connect Procedure: RANAP Direct Transfer Message

Description: RNC transparently forwards received NAS PDU in RRC Uplink Direct Transfer Message, to Core Network (MSC/VLR), using RANAP Direct Transfer Message.

Main IEs NAS Message [ Encoded – Connect Acknowledge Message Type, .. ]

Channels


















[ NAS PDU (Connect Acknowledge) ]

110

Channels Main IEs

RNC MSC Node-B UE


Call Connected: Voice Transfer!!

Description: Once call in connected state, two way voice transfer continues until, either of party initiates Call Release Procedure.

Main IEs Channels








111

Channels Main IEs

RNC MSC Node-B UE


Call Release Procedure: RRC Uplink Direct Transfer Message

Description: When calling user disconnects call, UE NAS (CC) initiates Disconnect Message, encoded NAS PDU, in RRC Uplink Direct Transfer message on DCCH (SRB-3).


CN Domain ID (CS!!) NAS Message [ Encoded – Disconnect Message Type, ..]

Channels

DCCH : DCH : DPDCH










112

Channels Main IEs

RNC MSC Node-B UE


Call Release Procedure: RANAP Direct Transfer Message

Description: RNC transparently forwards received NAS PDU in RRC Uplink Direct Transfer, to Core Network (MSC/VLR), using RANAP Direct Transfer Message.

Main IEs NAS Message [ Encoded – Disconnect Message Type, ..]

Channels












[ NAS PDU (Disconnect) ]

113

Channels Main IEs

RNC MSC Node-B UE



Description: MSC Call Control functionality responds back to UE with Release, encoded NAS PDU, using RANAP Direct Transfer Message towards RNC.

Main IEs NAS Message [ Encoded – Release Message Type, ..]

Channels














[ NAS PDU (Release) ]

114

Channels Main IEs

RNC MSC Node-B UE


Call Release Procedure: RRC Downlink Direct Transfer Message



CN Domain ID (CS!!) NAS Message [ Encoded – Release Message Type, ..]

Channels

DCCH : DCH : DPDCH
















115

Channels Main IEs

RNC MSC Node-B UE


Call Release Procedure: RRC Uplink Direct Transfer Message

Description: On reception of Release message, UE NAS (CC) responds with Disconnect Message, encoded NAS PDU, in RRC Uplink Direct Transfer message on DCCH (SRB-3).


CN Domain ID (CS!!) NAS Message [ Encoded – Release Complete Message Type, ..]

Channels

DCCH : DCH : DPDCH


















116

Channels Main IEs

RNC MSC Node-B UE



Description: RNC transparently forwards received NAS Message received in RRC Uplink Direct Transfer message, to Core Network (MSC/VLR), using RANAP Direct Transfer Message.

Main IEs NAS Message [ Encoded – Release Complete Message Type, ..]

Channels




















[ NAS PDU (Release Complete) ]

117

Channels Main IEs

RNC MSC Node-B UE


Iu Connection Release Procedure: RANAP Iu Release Command Message

Description: On successful completion of Call Release procedure, CN initiate Iu (Signalling!!) Connection Release procedure, using RANAP Iu Release Command towards RNC.


Channels











[ Cause ]

118

Channels Main IEs

RNC MSC Node-B UE


Iu Connection Release Procedure: RANAP Iu Release Complete Message


Main IEs Channels











[ Cause ]


triggers

SCCP SCCP Released



119

Channels Main IEs

RNC MSC Node-B UE


Iu Connection Release Procedure: ALCAP Release Request/Confirm Message

Description: Iu Connection Release Procedure, also initiates release of AAL2 bearers allocated over Iu (for Voice flow!!).

Main IEs DSAID Cause (Normal!!)

DSAID

Channels

STC.1 : MTP3b : SAAL : AAL5











[ DSAID ]


[ DSAID, Cause ]

triggers

120

Channels Main IEs

RNC MSC Node-B UE





Release Cause (Normal!!)

Channels

DCCH : DCH : DPDCH









Iu Connection Release triggers



121

Channels Main IEs

RNC MSC Node-B UE



Description: UE responds with RRC Connection Release Complete message on DCCH to RNC, release resources allocated for voice RAB, RB, etc.. terminates RRC connection and move to RRC IDLE state.


Channels

DCCH : DCH : DPDCH














122

Channels Main IEs

RNC MSC Node-B UE



Description: On reception of RRC Connection Release Complete message, RNC initiates cleanup of UE context, to release resources allocated for voice RAB, RB, etc.. initiate Radio Link Deletion Request towards Node-B,


RL ID(s)

Channels

SSCF : SSCOP : AAL5











[ RL ID(s) ]

123

Channels Main IEs

RNC MSC Node-B UE



Description: On reception Radio Link Deletion Request, Node-B release all resources associated with respective RL Ids, allocated for voice call. On success, respond with Radio Link Deletion Response message to RNC.


RL ID(s)

Channels

SSCF : SSCOP : AAL5











[ RL ID(s) ]



124

Channels Main IEs

RNC MSC Node-B UE



Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data streams. RNC ALCAP request release with Release Request message, Node-B ALCAP confirms it with Release Confirm message.


DSAID

Channels












[ RL ID(s) ]




[ DSAID, Cause ]


[ DSAID ]

Twice!!, One for Signalling DCH and other for Voice DCH AAL2 bearer Release!!

125

Channels Main IEs

RNC MSC Node-B UE


CS Call Setup and Released!!

Description: CS Call Setup, Connected, Voice Transferred, Released, UE back to Idle mode!!..

Main IEs Channels










UE Context Cleanup

126

Session Management – PS Session Setup and Release RNC SGSN Node-B UE


Signalling Connection Establishment (Attach Request) Procedure


PDP Context Activation (Session Establishment) Request Procedure


UE Context Cleanup


RAB Assignment Procedure ( Iu, IuB, Uu Setups!! )

PDP Context Activation (Session Establishment) Accept Procedure

Iu Resource Setup IuB Resource Setup

Radio Bearer (Uu) Setup

PDP Context De-activation (Session Release) Procedure

Call Connected : Data Transfer!!

Attach Accept Procedure

127

Channels Main IEs

RNC SGSN Node-B UE

Session Management – PS Session Setup and Release


Description: On successful establishment of RRC Connection, UE MM sends Attach Request message, encoded NAS message, enclosed in RRC Initial Direct Transfer message on DCCH.

Main IEs RRC transaction ID, CN Domain Identity (PS),

NAS Message [ Encoded – Attach request, Attach type, N/w capability, CKSN, .. ]

Measurement Results

Channels

DCCH : DCH : DPDCH




128

Channels Main IEs

RNC SGSN Node-B UE



Description: RNC uses received CN domain identity in Initial Direct Transfer Message, and initiate Iu (Iu-PS) connection setup, and transfer of received Initial UE NAS message using RANAP Initial UE Message to CN.


NAS–PDU [ Encoded – Attach request, Attach type, N/w capability, CKSN, .. ]


Channels














129

Channels Main IEs

RNC SGSN Node-B UE


Identification/Authentication/Security Procedure: UE RNC CN Description: After successful establishment of signalling connection, optionally, CN NAS initiates identification, authentication and security procedures.

Main IEs Channels




130

Channels Main IEs

RNC SGSN Node-B UE


Attach Accept Procedure: RANAP Direct Transfer Message

Description: Core network confirms Attach Request acceptance, using Attach Accept message to UE. SGSN transfers Attach Accept, encoded NAS PDU, in RANAP Direct Transfer message to RNC.

Main IEs NAS–PDU [ Encoded – Attach accept, Attach result, RAI, P-TMSI, RA Timer, .. ]

Channels




[ NAS PDU (Attach Accept) ]



131

Channels Main IEs

RNC SGSN Node-B UE


Attach Accept Procedure: RRC Downlink Direct Transfer Message


Main IEs RRC Transaction ID, CN Domain ID (CS!!),

NAS Message [ Encoded – Attach accept, Attach result, RAI, P-TMSI, RA Timer, .. ]

Channels

DCCH : DCH : DPDCH








132

Channels Main IEs

RNC SGSN Node-B UE


Attach Accept Procedure: RRC Uplink Direct Transfer Message

Description: (Optionally!!) If TMSI/P-TMSI has been reallocated as part of Attach Accept Message, UE (GMM) responds with Attach Complete, encoded NAS PDU, in RRC Uplink Direct Transfer message.


CN Domain ID (PS) NAS Message [ Encoded – Attach Complete Message Type ]

Channels

DCCH : DCH : DPDCH










133

Channels Main IEs

RNC SGSN Node-B UE


Attach Accept Procedure: RANAP Direct Transfer Message

Description: RNC forwards received NAS Message in RRC Uplink Direct Transfer message, to Core Network (SGSN), using RANAP Direct Transfer Message.

Main IEs NAS Message [ Encoded – Attach Complete Message Type ]

Channels












[ NAS PDU (Attach Complete) ]

134

Channels Main IEs

RNC SGSN Node-B UE


Session Setup Request Procedure: RRC Uplink Direct Transfer Message

Description: After attach accept procedure, UE (SM) UE initiates PDP Context Activation, using Activate PDP Context Request Message, encoded NAS PDU, in RRC Uplink Direct Transfer message on DCCH (SRB-3).


CN Domain ID (PS!!) NAS Msg [ Activate PDP Context Req, Req N-SAPI, QoS, PDP Address, APN, .. ]

Channels

DCCH : DCH : DPDCH







135

Channels Main IEs

RNC SGSN Node-B UE


Session Setup Request Procedure: RANAP Direct Transfer Message

Description: RNC transparently forwards received NAS PDU in RRC Uplink Direct Transfer message, to Core Network (SGSN), using RANAP Direct Transfer Message.

Main IEs NAS–PDU [ Activate PDP Context Req, Req N-SAPI, QoS, PDP Address, APN, .. ]

Channels









[ NAS PDU (Activate PDP Context Request) ]

136

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: RANAP RAB Assignment Request Message

Description: On reception of Active PDP Context Request, SGSN initiates resource reservation according to requested Service, QoS type, etc in CN, and towards UTRAN, using RANAP RAB Assignment Request message.

Main IEs RAB Setup list, RAB ID RAB Info [e.g. QoS Info, Alloc/Ret Priority, Delay,

Max Rate, Guaranteed Rate, Max SDU Size, etc..] SDU Params[BLER, BER]

Transport Layer Info [ i.e. TLA(IP),Binding ID(TEID)]

Channels









137

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: NBAP RL Reconfiguration Prepare Message

Description: On receipt of RAB Assignment Request, RNC reserves additional radio resources, according to new RAB requirement and initiates resource allocation over IuB, using NBAP RL Reconfiguration Prepare Message.

Main IEs NodeB Comm Ctxt ID, UL/DL DPCH info [ e.g. Codes, TFCS, etc ]



RL Info, [e.g. RL ID, DL Code, Power Information, Max/Min DL power, etc ]

Channels

SSCF : SSCOP : AAL5








NBAP NBAP RL Reconfiguration Prepare

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

138

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: NBAP RL Reconfiguration Ready Message

Description: Node B reserves necessary resources for new configuration of Radio Link(s), packet service DCH transport channel, etc.., according to received parameters; and send success response to RNC.

Main IEs Transaction ID, CRNC Comm Ctxt ID, RL IDs

DCH Info Response [ e.g. TrCH ID, Transport Layer Address and Binding ID ]

Channels

SSCF : SSCOP : AAL5











[ TLA, Binding ID ]

139

Channels Main IEs

RNC SGSN Node-B UE



Description: RNC initiates AAL2 bearer establishment for voice DCH, using received AAL2 TLA & Binding ID. Node-B ALCAP establish required bearer; and respond successful establishment with ALCAP Confirm message.


OSAID, DSAID

Channels












[ TLA, Binding ID ]




[ OSAID, DSAID ]

140

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: FP DL/UL Synchronization Frames

Description: New PS DCH FP initiates L2 synchronization using DL synchronization frame with current CFN. Node-B FP(peer!!) verifies CFN to SFN relationship; & respond back with ToA(required timing adjustment) info



Channels

FP : AAL2











[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]


[ CFN, ToA ]

141

Channels Main IEs

RNC SGSN Node-B UE


RAB 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!!).

Main IEs Transaction ID, Node-B Communication Context ID,

CFN (Connection Frame Number – Activation time for new configuration!!)

Channels

SSCF : SSCOP : AAL5











[ TLA, Binding ID ]




[ OSAID, DSAID ]


[ CFN ]


[ CFN, ToA ]

NBAP NBAP RL Reconfiguration Commit

[ Activation CFN ]

142

Channels Main IEs

RNC SGSN Node-B UE


RAB 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 PS RAB, with selected configuration and allocated resource information.

Main IEs Activation 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





PDP Context Activation (Session Establishment) Request Procedure RAB Assignment Procedure ( IuB Setup!! )



143

Channels Main IEs

RNC SGSN Node-B UE


RAB 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 Complete message to RNC.

Main IEs RRC Transaction ID, Integrity Check Info [ i.e. MAC, RRC Msg Seq no ]

START Value (PS!!)

Channels

DCCH : DCH : DPDCH











144

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: RANAP RAB Assignment Response Message

Description: On reception of RRC Radio Bearer Setup Complete message, RNC send successful response to RAB Assignment procedure, using RANAP RAB Assignment Response message towards SGSN.

Main IEs RAB ID (of successfully established RAB!!)

Assigned (Chosen) RAB Parameters (if RAB QoS negotiation has performed!!)

Transport Layer Info [ i.e. TLA(IP),Binding ID(TEID)]

Channels












RANAP RANAP RAB Assignment Response

[ RAB ID ]

145

Channels Main IEs

RNC SGSN Node-B UE


Session Setup Accept Procedure: RANAP Direct Transfer Message

Description: After successful RAB setup in UTRAN and GTP Tunnel setup towards GGSN, SGSN SM respond with Activate PDP Context Accept message back, which is forwarded using RANAP Direct Transfer Message.

Main IEs NAS–PDU [Activate PDP Context Accept, Negotiated QoS, Priority, PDP address,]

Channels






PDP Context Activation (Session Establishment) Request Procedure RAB Assignment Procedure ( Iu, IuB, Uu Setup!! )


[ NAS PDU (Active PDP Context Accept) ]

146

Channels Main IEs

RNC SGSN Node-B UE


RAB Assignment Procedure: RRC Downlink Direct Transfer Message



CN Domain ID (PS!!) NAS–PDU [Activate PDP Context Accept, Negotiated QoS, Priority, PDP address,]

Channels

DCCH : DCH : DPDCH







[ NAS PDU (Active PDP Context Accept) ]



147

Channels Main IEs

RNC SGSN Node-B UE


Session Established: Data Transfer!!

Description: Once session is established, data transfer continues until, either of side initiates Session Release (PDP context deactivation!!) Procedure.

Main IEs Channels







Session Established : Data Transfer!!

148

Channels Main IEs

RNC SGSN Node-B UE


Session Release Procedure: RRC Uplink Direct Transfer Message

Description: Either MS or n/w NAS (SM) can initiate session release!! e.g.UE NAS (SM) initiates session release using De-activate PDP Context Request message, encoded NAS PDU, in RRC Uplink Direct Transfer message.


CN Domain ID (PS!!) NAS–PDU [De-activate PDP Context Request, SM Cause, Teardown Indicator]

Channels

DCCH : DCH : DPDCH










149

Channels Main IEs

RNC SGSN Node-B UE


Session Release Procedure: RANAP Direct Transfer Message

Description: RNC transparently forwards received NAS PDU in RRC Uplink Direct Transfer, to Core Network (MSC/VLR), using RANAP Direct Transfer Message.

Main IEs NAS–PDU [De-activate PDP Context Request, SM Cause, Teardown Indicator]

Channels












[ NAS PDU (De-activate PDP Context Request) ]

150

Channels Main IEs

RNC SGSN Node-B UE


Session Release Procedure: RANAP Direct Transfer Message

Description: SGSN SM, preserves or initiate release of CN resources as per teardown indicator, responds back to UE with De-activate PDP Context Accept message, encoded NAS PDU, using RANAP Direct Transfer message.

Main IEs NAS–PDU [ De-activate PDP Context Accept Msg type, Transaction ID ]

Channels














[ NAS PDU (De-activate PDP Context Accept) ]

151

Channels Main IEs

RNC SGSN Node-B UE


Session Release Procedure: RRC Downlink Direct Transfer Message



CN Domain ID (PS!!) NAS–PDU [ De-activate PDP Context Accept Msg type, Transaction ID ]

Channels

DCCH : DCH : DPDCH













[ NAS PDU (De-activate PDP Context Accept) ]



152

Channels Main IEs

RNC SGSN Node-B UE


Iu Connection Release Procedure: RANAP Iu Release Command Message

Description: On successful completion of Session Release (PDP context de-activation) procedure, SGSN initiate Iu (Signalling!!) Connection Release procedure, using RANAP Iu Release Command towards RNC.


Channels









PDP Context De-activation (Session Release!!) Procedure


[ Cause ]

153

Channels Main IEs

RNC SGSN Node-B UE


Iu Connection Release Procedure: RANAP Iu Release Complete Message


Main IEs Channels











[ Cause ]


triggers

SCCP SCCP Released



154

Channels Main IEs

RNC SGSN Node-B UE





Release Cause (Normal!!)

Channels

DCCH : DCH : DPDCH












155

Channels Main IEs

RNC SGSN Node-B UE



Description: UE responds with RRC Connection Release Complete message on DCCH to RNC, release resources allocated for PS RAB, RB, etc.. terminates RRC connection and move to RRC IDLE state.


Channels

DCCH : DCH : DPDCH














156

Channels Main IEs

RNC SGSN Node-B UE



Description: On reception of RRC Connection Release Complete message, RNC initiates cleanup of UE context, to release resources allocated for PS RAB, RB, etc.. initiate Radio Link Deletion Request towards Node-B.


RL ID(s)

Channels

SSCF : SSCOP : AAL5











[ RL ID(s) ]

157

Channels Main IEs

RNC SGSN Node-B UE



Description: On reception Radio Link Deletion Request, Node-B release all resources associated with respective RL Ids, allocated for PS call. On success, respond with Radio Link Deletion Response message to RNC.

Main IEs Transaction ID, CRNC Comm Ctxt ID,

Channels

SSCF : SSCOP : AAL5











[ RL ID(s) ]



158

Channels Main IEs

RNC SGSN Node-B UE



Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data streams. RNC ALCAP request release with Release Request message, Node-B ALCAP confirms it with Release Confirm message.


DSAID

Channels












[ RL ID(s) ]




[ DSAID, Cause ]


[ DSAID ]

Twice!!, One for Signalling DCH and other for PS DCH AAL2 bearer Release!!

159

Channels Main IEs

RNC SGSN Node-B UE


PS Session Setup and Released!!

Description: PS Session Established, Packet data Transferred, Session Released, UE back to Idle mode!!..

Main IEs Channels








PDP Context De-activation (Session Release) Procedure


UE Context Cleanup

Thank You!!..

Mahesh Khade ([email protected])

Flextronics Software Systems, Bangalore

161

Backup!!..

• Misc..

Umts call-flow-scenarios overview

Technology

Transcript of Umts call-flow-scenarios overview