UMTS Call Flows - 20101020

UMTS Call Flow Scenarios
Overview
Mahesh Khade
(mahesh.khade@alcatel-lucent.com)
All Rights Reserved © Alcatel-Lucent 2010, #####

Contents
Introduction
 UMTS Network Architecture and Interfaces
 End to End Protocols (CS and PS Domain)
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
Backup
 Misc
2 | UMTS Call Flow Scenarios | October 2010 All Rights Reserved © Alcatel-Lucent 2010, #####
Introduction
 UMTS Network Architecture and Interfaces

 CS Domain – End to End Protocols
 PS Domain – End to End Protocols
UMTS Network Architecture and Interfaces
UTRAN Core Network (CN) External

Iu Networks
RNS CS Domain
Node-B PSTN PLMN,
Iu-CS PSTN,
MSC /
IuB GMSC ISDN, etc
RNC VLR
UE D
Node-B Iu-PS F C
ME
HSS HLR H
Cu
Uu IuR Gs EIR
AuC
USIM Gf
Iu-CS Gc
Node-B Gr
Gi Internet
IuB Iu-PS SGSN GGSN
RNC Gn
Node-B
Ga Ga
RNS CGF
PS Domain
CS Domain – End to End Protocols
Uu IuB Iu-CS
UE Node-B RNC 3G-MSC
CC CC
MM MM
Codec RRC RRC Codec
RLC RLC RANAP RANAP
MAC MAC ALCAP ALCAP
PHY-upper ALCAP ALCAP PHY-upper STC.1 SCCP SCCP STC.1
IuUP IuUP
STC.2 NBAP NBAP STC.2 MTP3-b MTP3-b
FP SSCF-UNI SSCF-UNI FP SSCF-NNI SSCF-NNI
SSCOP SSCOP SSCOP SSCOP
PHY PHY
AAL2 AAL5 AAL5 AAL2 AAL5 AAL5 AAL2
ATM ATM ATM
PHY [E1/T1/STM] PHY [E1/T1/STM] PHY [E1/T1/STM]
Control Plane Application Protocol Data Streams NAS Protocols
Access Link Control Application Protocol Data Bearers Application Data
Signalling Bearers Network Transport / Physical Layer Uu Interface Protocols
PS Domain – End to End Protocols
Uu IuB Iu-PS Gn
UE Node-B RNC 3G-SGSN 3G-GGSN
SM SM
IP GMM GMM IP
PDCP RRC RRC PDCP GTP-U GTP-U GTP-C GTP-C GTP-U
RLC RLC RANAP RANAP
UDP UDP UDP
MAC MAC
PHY-upper ALCAP ALCAP PHY-upper SCCP SCCP
STC.2 NBAP NBAP STC.2 MTP3-b MTP3-b
IP IP IP
FP SSCF-UNI SSCF-UNI FP SSCF-NNI SSCF-NNI
SSCOP SSCOP SSCOP SSCOP
PHY PHY
AAL2 AAL5 AAL5 AAL2 AAL5 AAL5
L2 L2
ATM ATM ATM
PHY [E1/T1] PHY [E1/T1/STM-1] PHY [STM-1] L1 L1
Control Plane Application Protocol Data Streams NAS Protocols
Access Link Control Application Protocol Data Bearers Application Data
Signalling Bearers Network Transport / Physical Layer Uu Interface Protocols
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
Node-B Initialization
UE Node-B RNC MSC
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
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.
UE Node-B RNC MSC
Audit Required Indication

NBAP [ Transaction ID ] NBAP
Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5
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.
UE Node-B RNC MSC

Audit Request
NBAP [ Transaction ID, Start of Audit Seq Ind ] NBAP
Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5 Start of audit sequence ind
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.
UE Node-B RNC MSC

Audit Request
NBAP [ Transaction ID, Start of Audit Seq Ind ] NBAP
Audit Response
NBAP [ End of Audit Seq Ind, Local Resource Info ] NBAP
Channels Main IEs

Transaction ID Cell Info (Configured) Communication Control
SSCF / SSCOP / AAL5 End of audit sequence ind Local Cell Information Port information
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.
UE Node-B RNC MSC
Audit Procedure
Resource Status Indication

NBAP [ Local Cell ID, Add/Delete Indicator ] NBAP
Channels Main IEs

Transaction ID Local Cell ID
SSCF / SSCOP / AAL5 No Failure Indication Add/Delete Indicator
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.
UE Node-B RNC MSC
Audit Procedure

Cell Setup Request

NBAP [ Global/Local Cell ID, Physical Config. ] NBAP
Channels Main IEs

Transaction ID, DL/UL Frequency, P-SCH, S-SCH info,
SSCF / SSCOP / AAL5 Global (C-ID) Cell ID, Maximum Tx Power, PCPICH, SCPICH info,
Local (Node-B) Cell ID, Primary Scrambling Code PCCPCH, BCH, etc info..
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)
UE Node-B RNC MSC
Audit Procedure

Cell Setup Request

Cell Setup Response

Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5
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).
UE Node-B RNC MSC
Audit Procedure

Cell Setup Request

Cell Setup Response

Block Resource Request

NBAP [ Transaction ID, Blocking Priority ] NBAP
Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5 Global (C-ID) Cell ID
Blocking Priority (High)
Cell Setup Procedure: Block Resource Response Message
Description: RNC Blocks respective resource (cell), and send successful response to the Node-B.
UE Node-B RNC MSC
Audit Procedure

Cell Setup Request

Cell Setup Response

Block Resource Request

NBAP [ Transaction ID, Blocking Priority ] NBAP
Block Resource Response

Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5
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.
UE Node-B RNC MSC
Audit Procedure
System Information Update Request

NBAP [ SIB segment info. ] NBAP
Channels Main IEs

Transaction ID MIB, SB, SIB info
SSCF / SSCOP / AAL5 Global (C-ID) Cell ID Segment Info
BCCH Modification Time
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.
UE Node-B RNC MSC
Audit Procedure

Segment 1
System Information Update Response
NBAP NBAP

Segment 2
NBAP NBAP
Channels Main IEs

Transaction ID
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.
UE Node-B RNC MSC
Audit Procedure

Segment 1
NBAP NBAP

Segment 2
NBAP NBAP
BCCH: System Information

RRC RRC
RRC RRC
Channels Main IEs

Master Information Block, System Information Block
BCCH / BCH / PCCPCH Scheduling Block,
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.)
UE Node-B RNC MSC
Audit Procedure
Common TrCH Setup Request
NBAP [PRACH, AICH, RACH] NBAP
Channels Main IEs

Transaction ID, Cell ID, AICH parameters [ e.g. RACH parameters [ e.g.
SSCF / SSCOP / AAL5 PRACH parameters [ e.g. Channel Codes, Power, etc..] TrCH ID, TFS, etc..]
TFCS, SF, Signatures, etc..]
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).
UE Node-B RNC MSC
Audit Procedure
Common TrCH Setup Response

NBAP [TLA, Binding ID] NBAP
Channels Main IEs

Transaction ID, RACH parameters [ e.g.
SSCF / SSCOP / AAL5 TrCH ID, Transport Layer
Address and Binding ID ]
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.
UE Node-B RNC MSC
Audit Procedure

ALCAP Establish Request (ERQ)

ALCAP [OSAID,DSAID,SUGR,AAL2 Address] ALCAP
Channels Main IEs

OSAID / DSAID CEID (Path ID + CID) SUGR (Binding ID)
STP.2 / SSCF / SSCOP / AAL5 (Originating / Destination AAL2 Destination Address
signalling association ID) of Node-B
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.
UE Node-B RNC MSC
Audit Procedure


ALCAP Establish Confirm (ECF)

ALCAP [OSAID,DSAID] ALCAP
Channels Main IEs

OSAID
STP.2 / SSCF / SSCOP / AAL5 DSAID
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.)
UE Node-B RNC MSC
Audit Procedure
NBAP [ SCCPCH, PCH+PICH, FACH(s) ] NBAP
Channels Main IEs

Transaction ID, Cell ID, PCH parameters [ e.g. ID, FACH(s) parameters [ e.g.
SSCF / SSCOP / AAL5 SCCPCH parameters [e.g. TFS,Window(ToAWS, ToAWE), ID, TFS, Window(ToAWS,
ID, TFCS, SF, Codes, etc..] PICH Code, Max Power, .. ] ToAWE), Max Power, .. ]
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).
UE Node-B RNC MSC
Audit Procedure

NBAP [TLA(s), Binding ID(s)] NBAP
Channels Main IEs

Transaction ID, PCH parameters [ e.g. TrCH FACH(s) parameters [ e.g.
SSCF / SSCOP / AAL5 ID, Transport Layer Address TrCH ID, Transport Layer
and Binding ID ] Address and Binding ID ]
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.
UE Node-B RNC MSC
Audit Procedure


ALCAP ALCAP For PCH & FACH(s) bearers
[OSAID,DSAID,SUGR,AAL2 Address]
Channels Main IEs

OSAID SUGR (Binding ID)
STP.2 / SSCF / SSCOP / AAL5 DSAID + CEID AAL2 Destination Address
of Node-B
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.
UE Node-B RNC MSC
Audit Procedure


For PCH & FACH(s) bearers
Channels Main IEs

OSAID
STP.2 / SSCF / SSCOP / AAL5 DSAID
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.
UE Node-B RNC MSC
Audit Procedure



DL Synchronization
FP FP For PCH & FACH(s) bearers
[ CFN ]
Channels Main IEs

CFN (Connection Frame
FP / AAL2 Number)
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.
UE Node-B RNC MSC
Audit Procedure



DL Synchronization
FP [ CFN ] FP
UL Synchronization For PCH & FACH(s) bearers
FP [ CFN, ToA ] FP
Channels Main IEs

CFN (Connection Frame
FP / AAL2 Number),
ToA [Time of Arrival]
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.
UE Node-B RNC MSC
Audit Procedure

NBAP [ SIB5 segment info. ] NBAP
Channels Main IEs

Transaction ID BCCH Modification Time Segment Info [SIB5 with
SSCF / SSCOP / AAL5 Global (C-ID) Cell ID Reference to other SIBs PRACH info, SCCPCH info,
AICH info, PICH info, etc ..]
Description: Node-B process received SIB5 (and SIB6) System Information, Scheduling Information, System
Information Update time, etc and send successful response to RNC.
UE Node-B RNC MSC
Audit Procedure

NBAP NBAP
Channels Main IEs

Transaction ID
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)
UE Node-B RNC MSC
Audit Procedure

NBAP [ Communication Control port ID ] NBAP
Channels Main IEs

Transaction ID
SSCF / SSCOP / AAL5 Communication Control
Port ID
Description: Node-B sends resource unblock indication message to RNC, to indicate that respective Cell is
operational and can be unblocked.
UE Node-B RNC MSC
Audit Procedure

Unblock Resource Indication
NBAP [ C-ID ] NBAP
Channels Main IEs

Transaction ID
Description: After successful unblocking cell resource, RNC sends updated SIB3 System Information (with cell
status as unbarred) to Node-B.
UE Node-B RNC MSC
Audit Procedure

NBAP [ C-ID ] NBAP

Channels Main IEs

Transaction ID Reference to other SIBs
SSCF / SSCOP / AAL5 Global (C-ID) Cell ID Segment info [ SIB3 with
BCCH Modification Time Cell status unbarred ]
Description: Node-B process received SIB3 System Information, Scheduling Information, System Information
Update time, etc and send successful response to RNC.
UE Node-B RNC MSC
Audit Procedure

NBAP [ C-ID ] NBAP

NBAP NBAP
Channels Main IEs

Transaction ID
Node-B initialization with operational Cell Context..
UE Node-B RNC MSC
Audit Procedure

Un-block and Un-barred Cell
Channels Main IEs
RRC Connection Management
UE Node-B RNC MSC
Random Access Procedure
RRC Connection Request
UE Context Setup
RRC Connection Setup
RRC Connection Release
UE Context Cleanup
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.
UE Node-B RNC MSC

RRC RRC
RRC RRC
Channels Main IEs

Master Information Block, System Information Block
BCCH / BCH / PCCPCH Scheduling Block, [SIB 1, SIB 2, SIB 3, etc..]
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.
UE Node-B RNC MSC

RRC RRC
RRC RRC
Preamble
PHY
Wait for AICH response,
No response, Step-up power!!
Retransmit Preamble
Preamble
PHY
Retransmit Preamble
Preamble
PHY PHY
Channels Main IEs

Signature Sequence
PRACH
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.
UE Node-B RNC MSC

RRC RRC
RRC RRC
Preamble
PHY
Retransmit Preamble
Preamble
PHY
Retransmit Preamble
Preamble
PHY PHY
Access Indication
PHY PHY
Channels Main IEs

AICH Response Sequence
AICH
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.
UE Node-B RNC MSC
CCCH: RRC Connection Request

RRC RRC
RLC
MAC RACH Message RLC
PHY PHY Process received PRACH data; MAC
[ Data, Control (TFCI) ]
Decode it using control info(TFCI);
RACH Data Frame
FP [ CFN, TFI, TB(s), CRCI indicator ] FP
Channels Main IEs

Initial UE identity [ e.g. Establishment Cause [ e.g. Measurement Information
CCCH : RACH : PRACH IMSI, TMSI, P-TMSI, IMEI, Originating or Terminating
etc. ] voice,data..;Emergency, etc]
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.
UE Node-B RNC MSC

RRC Connection Setup Request
Radio Link Setup Request
NBAP [ UL/DL DPCH info, RL info, DCH ] NBAP
Channels Main IEs

Cell ID, Comm Ctxt ID, DCH info [ e.g. TrCH ID, Power Information [ e.g.
SSCF / SSCOP / AAL5 UL/DL DPCH info [ e.g. UL/DL TFS, Window(ToAWS, Initial power, SIR target,
Codes, TFCS, etc ] ToAWE), Priority, etc..] Max/Min DL power, etc ]
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.
UE Node-B RNC MSC

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

Transaction ID, DCH parameters [ e.g.
SSCF / SSCOP / AAL5 Node-B Communication TrCH ID, Transport Layer
Context ID Address and Binding ID ]
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.
UE Node-B RNC MSC

NBAP NBAP
NBAP NBAP


Channels Main IEs

OSAID, DSAID + CEID, OSAID,
SSCF / SSCOP / AAL5 SUGR (Binding ID), DSAID
AAL2 destination Address
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.
UE Node-B RNC MSC

NBAP NBAP
NBAP NBAP

ALCAP ALCAP

ALCAP ALCAP
DL Synchronization
FP [ CFN ] FP
UL Synchronization
FP [ CFN, ToA ] FP
Channels Main IEs

CFN (Connection Frame CFN (Connection Frame
FP / AAL2 Number) Number),
ToA (Time of Arrival)
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.
UE Node-B RNC MSC

UE Context Setup
CCCH: RRC Connection Setup
RRC RRC
RLC
RLC MAC
MAC
FACH Data Frame(s)
FP [ CFN, TFI, TB(s) ] FP RRC Connection Setup message
SCCPCH Message would be split into several TB(s),
PHY [ Data, Control (TFCI) ] PHY hence this sequence will repeat
Channels Main IEs

Received Initial UE ID, SRB info [RLC, mapping], RL info [e.g. Frequency,
CCCH : FACH : SCCPCH RRC State [DCH, FACH] UL/DL DCH info [e.g. ID, Codes, etc]
RNTIs [U-RNTI, C-RNTI] TFS, TFCS, etc..] Power Info, etc..
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.
UE Node-B RNC MSC

UE Context Setup
CCCH: RRC Connection Setup
RRC RRC
RLC
RLC MAC
MAC
FACH Data Frame(s)
FP [ CFN, TFI, TB(s) ] FP RRC Connection Setup message
SCCPCH Message would be split into several TB(s),
PHY [ Data, Control (TFCI) ] PHY hence this sequence will repeat
DCCH: RRC Connection Setup Complete

RRC RRC
RLC
MAC DPCH [DPDCH + DPCCH] RLC
PHY [ Data, Control (TFCI,TFC,Pilot) ] PHY MAC
DCH Data Frame
Channels Main IEs

RRC transaction ID, Radio Access Capabilities
DCCH : DCH : DPDCH START List [CS, PS] [e.g. Basic, extended, inter-
system, etc]
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]
UE Node-B RNC MSC

UE Context Setup
DCCH: RRC Connection Release
RRC RRC
RLC
RLC MAC
MAC
DCH Data Frame(s)
FP [ CFN, TFI, TB(s) ] FP
DPCH [DPDCH + DPCCH]
PHY [ Data, Control (TFCI,TPC,Pilot) ] PHY
Channels Main IEs

RRC transaction ID, Release Cause[e.g. normal, Rplmn information
DCCH : DCH : DPDCH inactivity, directed re-
establishment, congestion, ..]
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.
UE Node-B RNC MSC

UE Context Setup
DCCH: RRC Connection Release
RRC RRC
RLC
RLC MAC
MAC
DCH Data Frame(s)
FP [ CFN, TFI, TB(s) ] FP
DPCH [DPDCH + DPCCH]
PHY [ Data, Control (TFCI,TPC,Pilot) ] PHY
DCCH: RRC Connection Release Complete

RRC RRC
RLC
MAC RLC
DPCH [DPDCH + DPCCH] MAC
PHY [ Data, Control (TFCI,TFC,Pilot) ] PHY
DCH Data Frame
Channels Main IEs

RRC transaction ID
DCCH : DCH : DPDCH
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.
UE Node-B RNC MSC

UE Context Setup
Radio Link Deletion Request
NBAP [ RL ID(s) ] NBAP
Channels Main IEs

Transaction ID, RL ID(s)
SSCF : SSCOP : AAL5 CRNC Comm Ctxt ID,
Node-B Comm Ctxt ID,
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.
UE Node-B RNC MSC

UE Context Setup
NBAP NBAP
Radio Link Deletion Response

NBAP [ CRNC Comm Ctxt ID ] NBAP
Channels Main IEs

Transaction ID,
SSCF : SSCOP : AAL5 CRNC Communication
Context ID
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.
UE Node-B RNC MSC

UE Context Setup
NBAP NBAP

NBAP NBAP
ALCAP Release Request

ALCAP [ DSAID, Cause ] ALCAP
ALCAP Release Confirm

ALCAP [ DSAID ] ALCAP
Channels Main IEs

DSAID DSAID
STC.2 / SSCF / SSCOP / AAL5 Cause
RRC Connection Established and Released..
UE Node-B RNC MSC

UE Context Setup
UE Context Cleanup
Channels Main IEs
Mobility Management – Location Update
UE Node-B RNC MSC/VLR
RRC Connection Establishment
Signalling Connection Establishment (Location Update Request Procedure)
Identification /Authentication / Security Procedure (Optional)
Location Update Accept (Optional TMSI Reallocation) Procedure
Iu Connection Release
UE Context Cleanup
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.
UE Node-B RNC MSC

DCCH: Initial Direct Transfer
RRC [ CN Domain ID, NAS Message ] RRC
Channels Main IEs

RRC transaction ID, NAS Message [ Encoded – Measurement Results
DCCH : DCH : DPDCH CN Domain Identity [e.g. Update Type, Cipher Key Seq
CS, PS], No, LAI, Classmark, .. ]
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).
UE Node-B RNC MSC

Initial UE Message
RANAP RANAP
[ CN Domain ID, LAI, NAS-PDU ]
Iu (Iu-CS) Connection Setup; Connection Request (CR)

SCCP carry RANAP Initial UE Message SCCP SCCP
[ Reference, SRC/DST Add, User Data ]
piggybacked in SCCP CR PDU.
Connection Confirm (CC)
All subsequent RANAP messages will be SCCP SCCP
[ SRC/DST References ]
sent over this established SCCP Connection.
Channels Main IEs

CN Domain ID [CS or PS] NAS–PDU [ Encoded – Global RNC ID
SCCP : MTP3b : SAAL : AAL5 Location Info [ e.g. LAI, Update Type, Cipher Key Seq Iu Signalling Connection
RAC, SAI, etc..] No, LAI, Classmark, .. ] Identifier
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.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
[ NAS PDU (Identity Request) ]
Channels Main IEs

NAS–PDU [ Encoded –
SCCP : MTP3b : SAAL : AAL5 Identity Request, Identity
Type (e.g. IMSI, TMSI, etc)]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
DCCH: Downlink Direct Transfer
RRC RRC
[ CN Domain ID, NAS Message ]
Channels Main IEs

RRC Transaction ID, NAS Message [ Encoded –
DCCH : DCH : DPDCH CN Domain ID [CS or PS], Identity Request, Identity
Type (e.g. IMSI, TMSI, etc)]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
DCCH: Uplink Direct Transfer

Channels Main IEs

DCCH : DCH : DPDCH CN Domain ID [CS or PS], Identity Response, Requested
Identity Value ]
Identification Procedure: RANAP Direct Transfer Message
Description: RNC forwards received NAS PDU, to Core Network (MSC/VLR), using RANAP Direct Transfer
Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC

Direct Transfer
RANAP RANAP
[ NAS PDU (Identity Response) ]
Channels Main IEs

NAS Message [ Encoded – Location Info [ e.g. LAI,
SCCP : MTP3b : SAAL : AAL5 Identity Response, Requested RAC, SAI, etc..] optional
Identity Value ]
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.
UE Node-B RNC MSC

Identification Procedure
Direct Transfer
RANAP RANAP
[ NAS PDU (Authentication Request) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Authentication Request,
CKSN, RAND, AUTN, .. ]
Authentication Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

DCCH : DCH : DPDCH CN Domain ID [CS or PS], Authentication Request,
CKSN, RAND, AUTN, .. ]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC

Channels Main IEs

DCCH : DCH : DPDCH CN Domain ID [CS or PS], Authentication Response,
SRES (UE Calculated) ]
Authentication Procedure: RANAP Direct Transfer Message
Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC

Direct Transfer
RANAP RANAP
[ NAS PDU (Authentication Response) ]
Channels Main IEs

NAS Message [ Encoded – Location Info [ e.g. LAI,
SCCP : MTP3b : SAAL : AAL5 Authentication Response, RAC, SAI, etc..] optional
SRES (UE Calculated) ]
Security Procedure: RANAP Security Mode Command Message
Description: MSC (optionally) initiates Security Procedure, using RANAP Security Mode Command Message to
RNC.
UE Node-B RNC MSC

Identification / Authentication Procedure
Security Mode Command
RANAP RANAP
[ Integrity Protection, Encryption info ]
Channels Main IEs

Integrity Protection Info Encryption Info [e.g. Key Status [Old or New]
SCCP : MTP3b : SAAL : AAL5 [e.g. Permitted algorithms, Permitted Algorithm Set,
Integrity Protection Key, . ] Encryption Key, . ]
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).
UE Node-B RNC MSC

RANAP RANAP
DCCH: Security Mode Command
RRC RRC
[ CN Domain ID, Integrity Check Info, Integrity Protection/Ciphering Mode Info ]
Channels Main IEs

CN Domain ID [CS or PS], Integrity Prot Mode Info [ Ciphering Mode Info [ e.g.
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Cmd(S/M), Algo, FRESH, DL Cmd(Start/Restart), Algo, DL
MAC, RRC Msg Seq No ] Act time for SRBs ] Act time for all RBs ]
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).
UE Node-B RNC MSC

RANAP RANAP
RRC RRC
DCCH: Security Mode Complete

RRC [ Integrity Check Info, UL Integrity Protection/Ciphering Activation Time ] RRC
Channels Main IEs

RRC Transaction ID, UL Integrity Protection UL Ciphering activation
DCCH : DCH : DPDCH Integrity Check Info [ i.e. activation time for SRBs [ i.e. time for all RBs [ i.e. RLC
MAC, RRC Msg Seq No ] RRC Msg Seq Numbers ] Seq Numbers ]
Security Procedure: RANAP Security Mode Complete Message
Description: RNC send successful response of Security Procedure, using RANAP Security Mode Complete
message towards MSC.
UE Node-B RNC MSC

RANAP RANAP
RRC RRC

Security Mode Complete
RANAP RANAP
[ Chosen Integrity, Encryption Algorithm ]
Channels Main IEs

Chosen Integrity Protection Chosen Encryption
SCCP : MTP3b : SAAL : AAL5 Algorithm [ i. e. UIA1 ] Algorithm [ No Encryption,
or, UEA1 ]
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.
UE Node-B RNC MSC

RANAP RANAP
RRC RRC

Security Mode Complete
RANAP RANAP
[ Chosen Integrity, Encryption Algorithm ]
Common ID
RANAP RANAP
[ Permanent NAS UE Identity ]
Channels Main IEs

Permanent NAS UE identity
SCCP : MTP3b : SAAL : AAL5 ( i.e. IMSI value )
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.
UE Node-B RNC MSC

Identification / Authentication / Security Procedure
Direct Transfer
RANAP RANAP
[ NAS PDU (Location Update Accept) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Location Update Accept, LAI,
New mobile id(TMSI),]
Location Update Accept Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
[ Integrity Check info, CN Domain ID, NAS Message ]
Channels Main IEs

RRC Transaction ID, CN Domain ID [CS or PS] NAS–PDU [ Encoded –
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Location Update Accept, LAI,
MAC, RRC Msg Seq No ] New mobile id(TMSI),]
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.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC

RRC [ Integrity Check info, CN Domain ID, NAS Message ] RRC
Channels Main IEs

RRC Transaction ID, CN Domain ID [CS or PS] NAS–PDU [ Encoded –
DCCH : DCH : DPDCH Integrity Check Info [ i.e. TMSI Reallocation Complete
MAC, RRC Msg Seq No ] Message Type ]
Location Update Accept Procedure: RANAP Direct Transfer Message
Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC

Direct Transfer
RANAP RANAP
[ NAS PDU (TMSI Realloc Complete) ]
Channels Main IEs

NAS–PDU [ Encoded – Location Info [ e.g. LAI,
SCCP : MTP3b : SAAL : AAL5 TMSI Reallocation Complete RAC, SAI, etc..] optional
Message Type ]
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.
UE Node-B RNC MSC

Iu Release Command
RANAP RANAP
[ Cause ]
Channels Main IEs

Cause ( Normal Release )
SCCP : MTP3b : SAAL : AAL5
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.
UE Node-B RNC MSC

Iu Release Command
RANAP RANAP
[ Cause ]
Iu Release Complete
RANAP RANAP
triggers
Released
SCCP SCCP
[ SRC/DST References, Cause ]
Release Complete
SCCP SCCP
Channels Main IEs

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

DCCH: RRC Connection Release triggers
RRC RRC
[ Integrity Check info, Release Cause ]
Channels Main IEs

RRC transaction ID, Release Cause[e.g. normal, Rplmn information
DCCH : DCH : DPDCH Integrity Check Info [ i.e. inactivity, directed re-
MAC, RRC Msg Seq No ] establishment, congestion, ..]
Description: UE responds with RRC Connection Release Complete message on DCCH to RNC, terminates RRC
connection and move to RRC IDLE state.
UE Node-B RNC MSC

RRC RRC

RRC [ Integrity Check info ] RRC
Channels Main IEs

RRC transaction ID,
DCCH : DCH : DPDCH Integrity Check Info [ i.e.
MAC, RRC Msg Seq No ]
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.
UE Node-B RNC MSC

RRC Connection Release Iu Connection Release

Channels Main IEs

RL Ids. On success, respond with Radio Link Deletion Response message to RNC.
UE Node-B RNC MSC



Channels Main IEs

Transaction ID,
SSCF : SSCOP : AAL5 CRNC Communication
Context ID,
Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data stream. RNC ALCAP
UE Node-B RNC MSC




ALCAP [ DSAID, Cause ] ALCAP

Channels Main IEs

DSAID DSAID
STC.2 / SSCF : SSCOP : AAL5 Cause
Location Update Complete..
UE Node-B RNC MSC

UE Context Cleanup
Channels Main IEs
Connection Management – CS Call Setup and Release
UE Node-B RNC MSC/VLR

Signalling Connection Establishment (Service Request Procedure)
Call Setup Procedure
RAB Assignment Procedure ( Iu, IuB, Uu Setups )
IuB Resource Setup Iu Resource Setup
Radio Bearer (Uu) Setup
Call Connect Procedure

Call Connected : Voice Transfer
Call Release Procedure
UE Context Cleanup
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.
UE Node-B RNC MSC

Channels Main IEs

DCCH : DCH : DPDCH CN Domain Identity [e.g. CM service request, Service
CS, PS], type, CKSN, Classmark, .. ]
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).
UE Node-B RNC MSC

Initial UE Message
RANAP RANAP

Channels Main IEs

CN Domain ID [CS or PS] NAS–PDU [ Encoded – CM Global RNC ID
SCCP : MTP3b : SAAL : AAL5 Location Info [ e.g. LAI, service request, Service type, Iu Signalling Connection
RAC, SAI, etc..] CKSN, Classmark, .. ] Identifier
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.
UE Node-B RNC MSC

Initial UE Message
RANAP RANAP

Direct Transfer
RANAP RANAP
[ NAS PDU (CM Service Accept) ]
Channels Main IEs

NAS–PDU [ Encoded – CM
SCCP : MTP3b : SAAL : AAL5 service Accept, Only message
type ]
Signalling Connection Establishment: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Initial UE Message
RANAP RANAP

Direct Transfer
RANAP RANAP
[ NAS PDU (CM Service Accept) ]
RRC RRC
Channels Main IEs

RRC Transaction ID, NAS–PDU [ Encoded – CM
DCCH : DCH : DPDCH CN Domain ID (CS), service Accept, Only message
type ]
Identification/Authentication/Security Procedure: UE  RNC  CN
Description: After successful establishment of signalling connection, optionally, CN NAS initiates identification,
authentication and security procedures.
UE Node-B RNC MSC

Channels Main IEs
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).
UE Node-B RNC MSC

Channels Main IEs

RRC Transaction ID, CN Domain ID (CS) NAS Msg [ Encoded – Call
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Setup, Calling/Called Party
MAC, RRC Msg Seq No ] No, Bearer Capabilities, .. ]
Call Setup Procedure: RANAP Direct Transfer Message
Description: RNC transparently forwards received NAS PDU, to Core Network (MSC/VLR), using RANAP
Direct Transfer Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
[ NAS PDU (Call Setup) ]
Channels Main IEs

NAS-PDU [Encoded – Call
SCCP : MTP3b : SAAL : AAL5 Setup, Calling/Called Party
No, Bearer Capabilities, .. ]
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.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
[ NAS PDU (Call Proceeding) ]
Channels Main IEs

NAS-PDU [Encoded – Call
SCCP : MTP3b : SAAL : AAL5 Proceeding, Chosen Bearer
Capabilities, Priority, ..]
Call Setup Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
[ NAS PDU (Call Proceeding) ]
RRC RRC
Channels Main IEs

RRC Transaction ID, CN Domain ID (CS) NAS-PDU [Encoded – Call
SCCP : MTP3b : SAAL : AAL5 Integrity Check Info [ i.e. Proceeding, Chosen Bearer
MAC, RRC Msg Seq No ] Capabilities, Priority, ..]
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.
UE Node-B RNC MSC

RAB Assignment Request
RANAP RANAP
[ RAB ID, RAB Params, User Plane Info ]
Channels Main IEs

RAB Setup list, RAB ID SDU Params per Sub-flow User Plane Info[mode,ver]
SCCP : MTP3b : SAAL : AAL5 RAB Info [e.g. QoS Info, [BLER, BER, SDU Format Transport Layer Info [ i.e.
Alloc/Ret Priority, ..] info combination(SDU Size)] TLA, Binding ID ]
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.
UE Node-B RNC MSC

RANAP RANAP
triggers
ALCAP Establish Request
ALCAP ALCAP
[ OSAID,DSAID,SUGR,AAL2 Address ]
ALCAP Establish Confirm
ALCAP ALCAP
[ OSAID,DSAID ]
Channels Main IEs

STC.1 : MTP3b : SAAL : AAL5 SUGR (Binding ID), DSAID
AAL2 Destination Address
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.
UE Node-B RNC MSC

RANAP RANAP

ALCAP ALCAP
[ OSAID,DSAID,SUGR,AAL2 Address ]
ALCAP ALCAP
[ OSAID,DSAID ]
triggers
INITIALIZATION
IuUP IuUP
[ IuUP Version, RFCIs, SDU Sizes ]
INITIALIZATION ACK
IuUP IuUP
Channels Main IEs

IuUP Version RFCIs, SDU Sizes
FP: AAL2 Number of Sub-flows in
evey RFCI
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.
UE Node-B RNC MSC

RAB Assignment Procedure (Iu Setup)
RL Reconfiguration Prepare
Channels Main IEs

NodeB Comm Ctxt ID, DCH info [ e.g. TrCH ID, RL Info, [e.g. RL ID, DL
SSCF : SSCOP : AAL5 UL/DL DPCH info [ e.g. UL/DL TFS, Window(ToAWS, Code, Power Information,
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.
UE Node-B RNC MSC

RAB Assignment Procedure ( Iu Setup )
RL Reconfiguration Ready
NBAP [ TLA, Binding ID ] NBAP
Channels Main IEs

Transaction ID, DCH Info Response [ e.g.
SSCF : SSCOP : AAL5 CRNC Comm Ctxt ID, TrCH ID, Transport Layer
RL IDs Address and Binding ID ]
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.
UE Node-B RNC MSC


ALCAP [ OSAID, DSAID, SUGR, AAL2 Address ] ALCAP
ALCAP [ OSAID, DSAID ] ALCAP
Channels Main IEs

STC.2 : SSCF : SSCOP : AAL5 SUGR (Binding ID), DSAID
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
UE Node-B RNC MSC


DL Synchronization
FP [ CFN ] FP
UL Synchronization
FP [ CFN, ToA ] FP
Channels Main IEs

STC.2 : SSCF : SSCOP : AAL5 Number) Number),
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).
UE Node-B RNC MSC


DL Synchronization
FP [ CFN ] FP
UL Synchronization
FP [ CFN, ToA ] FP
RL Reconfiguration Commit
NBAP [ Activation CFN ] NBAP
Channels Main IEs

Transaction ID, CFN (Connection Frame
STC.2 : SSCF : SSCOP : AAL5 Node-B Communication Number – Activation time for
Context ID, new configuration)
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.
UE Node-B RNC MSC

RAB Assignment Procedure ( Iu, IuB Setup )
DCCH: Radio Bearer Setup
RRC RRC
[ Integrity Check Info, Activation CFN, RB Setup info, TrCH info, RL info ]
Channels Main IEs

Activation time (CFN) RRC State (Cell DCH) Radio info[e.g. Frequency,
DCCH : DCH : DPDCH RB info [ RAB ID, CN ID, TrCH info [ UL/DL TFCS, Codes, Power info, etc.. ]
RLC Config, RB mapping ..] DCH IDs, TFS, etc.. ] …
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.
UE Node-B RNC MSC

RRC RRC
On activation CFN, Node-B, UE and RNC

L1/L2 activates pending new configuration.
DCCH: Radio Bearer Setup Complete
RRC [ RRC Transaction ID, Integrity Check info, START value ] RRC
Channels Main IEs

RRC Transaction ID, START Value (CS)
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Ciphering Count-C
MAC, RRC Msg Seq no ] Activation Time (CFN)
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.
UE Node-B RNC MSC

RRC RRC

RAB Assignment Response
RANAP RANAP
[ RAB ID ]
Channels Main IEs

RAB ID (of successfully Assigned (Chosen) RAB
SCCP : MTP3b : SAAL : AAL5 established RAB) Parameters (if RAB QoS
negotiation has performed)
Call Connect Procedure: RANAP Direct Transfer Message
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.
UE Node-B RNC MSC

RAB Assignment Procedure ( Iu, IuB, Uu Setup )
Direct Transfer
RANAP RANAP
[ NAS PDU (Alerting) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Alerting Message Type, .. ]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

RRC Transaction ID, CN Domain ID (CS)
DCCH : DCH : DPDCH Integrity Check Info [ i.e. NAS Message [ Encoded –
MAC, RRC Msg Seq No ] Alerting Message Type, .. ]
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.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Direct Transfer
RANAP RANAP
[ NAS PDU (Connect) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Connect Message Type, .. ]
Call Connect Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

NAS Message [ Encoded –
DCCH : DCH : DPDCH Connect Message Type, .. ]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Direct Transfer
RANAP RANAP
RRC RRC

Channels Main IEs

RRC Transaction ID, CN Domain ID (CS) NAS Message [ Encoded –
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Connect Acknowledge
MAC, RRC Msg Seq No ] Message Type, .. ]
Description: RNC transparently forwards received NAS PDU in RRC Uplink Direct Transfer Message, to Core
Network (MSC/VLR), using RANAP Direct Transfer Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
RRC RRC
Direct Transfer
RANAP RANAP
RRC RRC

Direct Transfer
RANAP RANAP
[ NAS PDU (Connect Acknowledge) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Connect Acknowledge
Message Type, .. ]
Call Connected: Voice Transfer
Description: Once call in connected state, two way voice transfer continues until, either of party initiates Call
Release Procedure.
UE Node-B RNC MSC

Channels Main IEs
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).
UE Node-B RNC MSC

Channels Main IEs

DCCH : DCH : DPDCH Integrity Check Info [ i.e. Disconnect Message Type, ..]
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.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
[ NAS PDU (Disconnect) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Disconnect Message Type, ..]
Description: MSC Call Control functionality responds back to UE with Release, encoded NAS PDU, using
RANAP Direct Transfer Message towards RNC.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
[ NAS PDU (Release) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Release Message Type, ..]
Call Release Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

DCCH : DCH : DPDCH Integrity Check Info [ i.e. Release Message Type, ..]
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).
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

DCCH : DCH : DPDCH Integrity Check Info [ i.e. Release Complete Message
MAC, RRC Msg Seq No ] Type, ..]
Description: RNC transparently forwards received NAS Message received in RRC Uplink Direct Transfer
message, to Core Network (MSC/VLR), using RANAP Direct Transfer Message.
UE Node-B RNC MSC

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
RRC RRC
Direct Transfer
RANAP RANAP
[ NAS PDU (Release Complete) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Release Complete Message
Type, ..]
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.
UE Node-B RNC MSC

Iu Release Command
RANAP RANAP
[ Cause ]
Channels Main IEs

Iu Connection Release Procedure: RANAP Iu Release Complete Message
UE Node-B RNC MSC

Iu Release Command
RANAP RANAP
[ Cause ]
Iu Release Complete
RANAP RANAP
triggers
Released
SCCP SCCP
Release Complete
SCCP SCCP
Channels Main IEs

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).
UE Node-B RNC MSC

triggers
ALCAP ALCAP
[ DSAID, Cause ]
ALCAP ALCAP
[ DSAID ]
Channels Main IEs

DSAID DSAID
STC.1 : MTP3b : SAAL : AAL5 Cause (Normal)
DCCH (SRB1).
UE Node-B RNC MSC

RRC RRC
Channels Main IEs

RRC transaction ID, Release Cause (Normal)
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.
UE Node-B RNC MSC

RRC RRC
Channels Main IEs

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,
UE Node-B RNC MSC

Channels Main IEs

RL Ids, allocated for voice call. On success, respond with Radio Link Deletion Response message to RNC.
UE Node-B RNC MSC

Channels Main IEs

Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data streams. RNC ALCAP
UE Node-B RNC MSC

ALCAP [ DSAID, Cause ] ALCAP Twice, One for Signalling DCH and
ALCAP Release Confirm other for Voice DCH AAL2 bearer Release
Channels Main IEs

DSAID DSAID
CS Call Setup and Released
Description: CS Call Setup, Connected, Voice Transferred, Released, UE back to Idle mode..
UE Node-B RNC MSC

UE Context Cleanup
Channels Main IEs
Session Management – PS Session Setup and Release
UE Node-B RNC SGSN

Signalling Connection Establishment (Attach Request) Procedure
Attach Accept Procedure
PDP Context Activation (Session Establishment) Request Procedure
RAB Assignment Procedure ( Iu, IuB, Uu Setups )
IuB Resource Setup Iu Resource Setup
Radio Bearer (Uu) Setup
PDP Context Activation (Session Establishment) Accept Procedure

Call Connected : Data Transfer
PDP Context De-activation (Session Release) Procedure
UE Context Cleanup
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.
UE Node-B RNC SGSN

Channels Main IEs

DCCH : DCH : DPDCH CN Domain Identity (PS), Attach request, Attach type,
N/w capability, CKSN, .. ]
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.
UE Node-B RNC SGSN

Initial UE Message
RANAP RANAP

Channels Main IEs

CN Domain ID [CS or PS] NAS–PDU [ Encoded – Global RNC ID
SCCP : MTP3b : SAAL : AAL5 Location Info [ e.g. LAI, Attach request, Attach type, Iu Signalling Connection
RAC, SAI, etc..] N/w capability, CKSN, .. ] Identifier
Identification/Authentication/Security Procedure: UE  RNC  CN
Description: After successful establishment of signalling connection, optionally, CN NAS initiates identification,
authentication and security procedures.
UE Node-B RNC SGSN

Channels Main IEs
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
[ NAS PDU (Attach Accept) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Attach accept, Attach result,
RAI, P-TMSI, RA Timer, .. ]
Attach Accept 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).
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
RRC RRC
Channels Main IEs

DCCH : DCH : DPDCH CN Domain ID (CS), Attach accept, Attach result,
RAI, P-TMSI, RA Timer, .. ]
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
RRC RRC

Channels Main IEs

RRC Transaction ID, CN Domain ID (PS) NAS Message [ Encoded –
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Attach Complete Message
MAC, RRC Msg Seq No ] Type ]
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
RRC RRC

Direct Transfer
RANAP RANAP
[ NAS PDU (Attach Complete) ]
Channels Main IEs

SCCP : MTP3b : SAAL : AAL5 Attach Complete Message
Type ]
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).
UE Node-B RNC SGSN

Channels Main IEs

RRC Transaction ID, CN Domain ID (PS) NAS Msg [ Activate PDP
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Context Req, Req N-SAPI,
MAC, RRC Msg Seq No ] QoS, PDP Address, APN, .. ]
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
[ NAS PDU (Activate PDP Context Request) ]
Channels Main IEs

NAS–PDU [ Activate PDP
SCCP : MTP3b : SAAL : AAL5 Context Req, Req N-SAPI,
QoS, PDP Address, APN, .. ]
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.
UE Node-B RNC SGSN

RANAP RANAP
Channels Main IEs

RAB Setup list, RAB ID Max Rate, Guaranteed Rate, Transport Layer Info [ i.e.
SCCP : MTP3b : SAAL : AAL5 RAB Info [e.g. QoS Info, Max SDU Size, etc..] TLA(IP),Binding ID(TEID)]
Alloc/Ret Priority, Delay, SDU Params[BLER, BER]
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.
UE Node-B RNC SGSN

RANAP RANAP
Channels Main IEs

NodeB Comm Ctxt ID, DCH info [ e.g. TrCH ID, RL Info, [e.g. RL ID, DL
SSCF : SSCOP : AAL5 UL/DL DPCH info [ e.g. UL/DL TFS, Window(ToAWS, Code, Power Information,
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.
UE Node-B RNC SGSN

RANAP RANAP
Channels Main IEs

Transaction ID, DCH Info Response [ e.g.
SSCF : SSCOP : AAL5 CRNC Comm Ctxt ID, TrCH ID, Transport Layer
RL IDs Address and Binding ID ]
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.
UE Node-B RNC SGSN

RANAP RANAP
Channels Main IEs

STC.2 : SSCF : SSCOP : AAL5 SUGR (Binding ID), DSAID
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
UE Node-B RNC SGSN

RANAP RANAP
DL Synchronization
FP [ CFN ] FP
UL Synchronization
FP [ CFN, ToA ] FP
Channels Main IEs

FP : AAL2 Number) Number),
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).
UE Node-B RNC SGSN

RANAP RANAP
DL Synchronization
FP [ CFN ] FP
UL Synchronization
FP [ CFN, ToA ] FP
RL Reconfiguration Commit
NBAP [ Activation CFN ] NBAP
Channels Main IEs

Transaction ID, CFN (Connection Frame
SSCF : SSCOP : AAL5 Node-B Communication Number – Activation time for
Context ID, new configuration)
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.
UE Node-B RNC SGSN

RAB Assignment Procedure ( IuB Setup )
RRC RRC
Channels Main IEs

Activation time (CFN) RRC State (Cell DCH) Radio info[e.g. Frequency,
DCCH : DCH : DPDCH RB info [ RAB ID, CN ID, TrCH info [ UL/DL TFCS, Codes, Power info, etc.. ]
RLC Config, RB mapping ..] DCH IDs, TFS, etc.. ] …
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.
UE Node-B RNC SGSN

RRC RRC

Channels Main IEs

RRC Transaction ID, START Value (PS)
MAC, RRC Msg Seq no ]
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.
UE Node-B RNC SGSN

RRC RRC

RAB Assignment Response
RANAP RANAP
[ RAB ID ]
Channels Main IEs

RAB ID (of successfully Assigned (Chosen) RAB Transport Layer Info [ i.e.
SCCP : MTP3b : SAAL : AAL5 established RAB) Parameters (if RAB QoS TLA(IP),Binding ID(TEID)]
negotiation has performed)
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
[ NAS PDU (Active PDP Context Accept) ]
Channels Main IEs

NAS–PDU [Activate PDP
SCCP : MTP3b : SAAL : AAL5 Context Accept, Negotiated
QoS, Priority, PDP address,]
RAB Assignment Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
[ NAS PDU (Active PDP Context Accept) ]
RRC RRC
Channels Main IEs

RRC Transaction ID, CN Domain ID (PS) NAS–PDU [Activate PDP
DCCH : DCH : DPDCH Integrity Check Info [ i.e. Context Accept, Negotiated
MAC, RRC Msg Seq No ] QoS, Priority, PDP address,]
Session Established: Data Transfer
Description: Once session is established, data transfer continues until, either of side initiates Session Release
(PDP context deactivation) Procedure.
UE Node-B RNC SGSN

Session Established : Data Transfer
Channels Main IEs
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.
UE Node-B RNC SGSN

Channels Main IEs

RRC Transaction ID, CN Domain ID (PS) NAS–PDU [De-activate
DCCH : DCH : DPDCH Integrity Check Info [ i.e. PDP Context Request, SM
MAC, RRC Msg Seq No ] Cause, Teardown Indicator]
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
[ NAS PDU (De-activate PDP Context Request) ]
Channels Main IEs

NAS–PDU [De-activate
SCCP : MTP3b : SAAL : AAL5 PDP Context Request, SM
Cause, Teardown Indicator]
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.
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
[ NAS PDU (De-activate PDP Context Accept) ]
Channels Main IEs

NAS–PDU [ De-activate
SCCP : MTP3b : SAAL : AAL5 PDP Context Accept Msg
type, Transaction ID ]
Session Release Procedure: RRC Downlink Direct Transfer Message
UE Node-B RNC SGSN

Direct Transfer
RANAP RANAP
Direct Transfer
RANAP RANAP
[ NAS PDU (De-activate PDP Context Accept) ]
RRC RRC
Channels Main IEs

RRC Transaction ID, CN Domain ID (PS) NAS–PDU [ De-activate
DCCH : DCH : DPDCH Integrity Check Info [ i.e. PDP Context Accept Msg
MAC, RRC Msg Seq No ] type, Transaction ID ]
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.
UE Node-B RNC SGSN

Iu Release Command
RANAP RANAP
[ Cause ]
Channels Main IEs

Iu Connection Release Procedure: RANAP Iu Release Complete Message
UE Node-B RNC SGSN

Iu Release Command
RANAP RANAP
[ Cause ]
Iu Release Complete
RANAP RANAP
triggers
Released
SCCP SCCP
Release Complete
SCCP SCCP
Channels Main IEs

DCCH (SRB1).
UE Node-B RNC SGSN

RRC RRC
Channels Main IEs

RRC transaction ID, Release Cause (Normal)
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.
UE Node-B RNC SGSN

RRC RRC

Channels Main IEs

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.
UE Node-B RNC SGSN

Channels Main IEs

RL Ids, allocated for PS call. On success, respond with Radio Link Deletion Response message to RNC.
UE Node-B RNC SGSN

Channels Main IEs

Transaction ID,
Description: After RL deletion, RNC initiate AAL2 bearer release allocated for DCH data streams. RNC ALCAP
UE Node-B RNC SGSN

ALCAP [ DSAID, Cause ] ALCAP Twice, One for Signalling DCH and
ALCAP Release Confirm other for PS DCH AAL2 bearer Release
Channels Main IEs

DSAID DSAID
PS Session Setup and Released
Description: PS Session Established, Packet data Transferred, Session Released, UE back to Idle mode..
UE Node-B RNC SGSN

UE Context Cleanup
Channels Main IEs
Thank You..
Mahesh Khade
(mahesh.khade@alcatel-lucent.com)
All Rights Reserved © Alcatel-Lucent 2010, #####

Backup
 Misc..
RNC – Cell and UE Contexts
CELL #N UE #M
CELL #2 UE #2
CELL #1 UE #1
PS RAB CS RAB
RRC RRC
GTP IuUP
SRB SRB #0 SRB #1 SRB #2 SRB #3 SRB #4

SRB #0 PDCP
RLC-TM
RLC-TM
RLC-TM RLC-TM RLC-UM RLC-UM RLC-AM RLC-AM RLC-AM RLC-AM RLC-TM
PCCH CCCH CCCH DCCH DCCH DCCH DCCH DTCH DTCH’s
MAC-d
MAC–c MAC-c/sh MAC–d
Flows
DCH DCH DCH’s
PCH FACH PHY-Upper

RACH
PCH FP RACH FP FACH FP DCH FP DCH FP DCH FP
Handover Scenarios
Core Network (CN)
UTRAN
RNS RNS
RNC RNC
Node-B Node-B Node-B Node-B
UE
UE Connection States
UTRAN RRC Connected GSM to UMTS

Inter-System Handover GSM
CELL PCH URA PCH UMTS to GSM Connected
Inter-System Handover Mode
GPRS
Packet
CELL DCH CELL FACH Transfer
Mode
GPRS Packet
Camping on UTRAN Cell IDLE Idle Mode
Mode Camping on GSM/GPRS Cell

UMTS Call Flows - 20101020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UMTS Call Flows - 20101020

Uploaded by

Copyright:

Available Formats

UMTS Call Flow Scenarios

All Rights Reserved © Alcatel-Lucent 2010, #####

Call Flow Scenarios

 UMTS Network Architecture and Interfaces

UTRAN Core Network (CN) External

Control Plane Application Protocol Data Streams NAS Protocols

Access Link Control Application Protocol Data Bearers Application Data

Signalling Bearers Network Transport / Physical Layer Uu Interface Protocols

Control Plane Application Protocol Data Streams NAS Protocols

Access Link Control Application Protocol Data Bearers Application Data

Signalling Bearers Network Transport / Physical Layer Uu Interface Protocols

UE Node-B RNC MSC

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

UE Node-B RNC MSC

Audit Required Indication

Channels Main IEs

UE Node-B RNC MSC

Audit Required Indication

Channels Main IEs

UE Node-B RNC MSC

Audit Required Indication

Channels Main IEs

UE Node-B RNC MSC

Resource Status Indication

Channels Main IEs

UE Node-B RNC MSC

Resource Status Indication

Cell Setup Request

Channels Main IEs

UE Node-B RNC MSC

Resource Status Indication

Cell Setup Request

Cell Setup Response

Channels Main IEs

UE Node-B RNC MSC

Resource Status Indication

Cell Setup Request

Cell Setup Response

Block Resource Request

Channels Main IEs

UE Node-B RNC MSC

Resource Status Indication

Cell Setup Request

Cell Setup Response

Block Resource Request

Block Resource Response

Channels Main IEs

UE Node-B RNC MSC

System Information Update Request

Channels Main IEs

UE Node-B RNC MSC

System Information Update Request

System Information Update Request

Channels Main IEs

UE Node-B RNC MSC

System Information Update Request

System Information Update Request

BCCH: System Information