UMTS UTRAN Call Flow

UMTS Call Flow Scenarios
An Overview of
Circuit and
Packet Call
Flow Scenarios

UTRAN INTERFACES
MSC SGSN
RNC RNC
Node BNode B
UE
Iu-psIu-cs
Iu-r
Iu-b
Uu
Iu-b
Cell

BASIC CALL SETUP PURPOSE
• To provision a dedicated traffic channel and
a dedicated control channel over every
interface applicable for the call from the
core network to the UE
• To Synchronise the transmissions across
the network
• To provide security to the end user

PART 1
Node B
Initialization and
Cell “Camp on”

PART 1 - NODE B INITIALISATION
Procedure Overview1.1) Audit Procedure: Audit Required Indication Message1.1) Audit Procedure: Audit Required Indication Message
Type: NBAP
Purpose:
After the SSCOP layer is
established via the exchange of
BGN/BGAK PDU’s, the Node B
tells RNC that it has one or
more cells that need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
Type: NBAP
Purpose:
After the SSCOP layer is
established via the exchange of
BGN/BGAK PDU’s, the Node B
tells RNC that it has one or
more cells that need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
Audit Required Indication
UEUE
Node
B
Node
B
RNCRNC MSCMSC
[1]

Procedure Overview1.2) Audit Procedure: Audit Request Message1.2) Audit Procedure: Audit Request Message
Type: NBAP
Purpose:
RNC requests an Audit of the
Node B configuration.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
›Transaction ID
Type: NBAP
Purpose:
RNC requests an Audit of the
Node B configuration.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
›Transaction ID
Audit Request
UEUE
Node
B
Node
B
RNCRNC MSCMSC
[1]

Procedure Overview1.3) Audit Procedure: Audit Response Message1.3) Audit Procedure: Audit Response Message
Type: NBAP
Purpose:
Node B informs the RNC of its
Cell and Channel Configuration
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
›Transaction ID
›Node B Capacity
›Cell ID’s
›Channel Information...
Type: NBAP
Purpose:
Node B informs the RNC of its
Cell and Channel Configuration
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
›Transaction ID
›Node B Capacity
›Cell ID’s
›Channel Information...
Audit Response
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Audit Request
[1]

Procedure Overview1.4) Cell Set-up Procedure: Resource Status Indication1.4) Cell Set-up Procedure: Resource Status Indication
Type: NBAP
Purpose:
Node B informs the
RNC that it has added
a cell(s) and that it
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› No Failure
› Local Cell Added
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› No Failure
› Local Cell Added
Resource Status Indication
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Audit Request Procedure
[1]

Procedure Overview1.5) Cell Set-up Procedure: Cell Set-up Request1.5) Cell Set-up Procedure: Cell Set-up Request
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› Cell & Local Cell ID
› Scrambling Codes
› Sync and Power Info
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› Cell & Local Cell ID
› Scrambling Codes
› Sync and Power Info
Cell Setup Request
UEUE
Node
B
Node
B
RNCRNC MSCMSC
[1]

Procedure Overview1.6) Cell Set-up Procedure: Cell Set-up Response1.6) Cell Set-up Procedure: Cell Set-up Response
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› Cell Setup Success
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Transaction ID
› Cell Setup Success
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Cell Set-Up Response
Cell Setup Request
[1]

Procedure Overview1.7) Cell Set-up Procedure: Block Resource Request1.7) Cell Set-up Procedure: Block Resource Request
Type: NBAP
Purpose:
Node B requests that
the RNC should list this
new cell(s) as blocked
until System Info (MIB
& SIBs) can be
updated and broadcast
on BCH.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Trans & Cell ID
› Priority Indicator (high)
Type: NBAP
Purpose:
Node B requests that
the RNC should list this
new cell(s) as blocked
until System Info (MIB
& SIBs) can be
updated and broadcast
on BCH.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Trans & Cell ID
› Priority Indicator (high)
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Cell Setup Request
Block Resource Request
[1]

Procedure Overview1.8) Cell Set-up Procedure: Block Resource Response1.8) Cell Set-up Procedure: Block Resource Response
Type: NBAP
Purpose:
RNC confirms that the
cell(s) are blocked. For
this example, this is a
new Node B so all the
cells will be blocked.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Trans & Cell ID
Type: NBAP
Purpose:
RNC confirms that the
cell(s) are blocked. For
this example, this is a
new Node B so all the
cells will be blocked.
Channels:
SSCF/SSCOP/AAL5
Main IE’s:
› Trans & Cell ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Cell Setup Request
Block Resource Request
Block Resource Response
[1]

Procedure Overview
1.9) System Information Broadcast Procedure:
System Information Update Request and Response
System Information Update Request and Response
Type: NBAP
Purpose:
RNC updates the System
Information by sending a
series of Sys. Info. Update
Request messages which are
ack’d by the Node B. SIB
blocks are segmented into
246 bit blocks, which are sent
(and ack’d) sequentially.
Main IE’s:
› MIB/SIB info
› Segment Info
Type: NBAP
Purpose:
RNC updates the System
Information by sending a
series of Sys. Info. Update
Request messages which are
ack’d by the Node B. SIB
blocks are segmented into
246 bit blocks, which are sent
(and ack’d) sequentially.
Main IE’s:
› MIB/SIB info
› Segment Info
System Info Update Req.
Segment 1
System Info Update Resp.
Segment 1
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Cell Setup Procedure
Segment 2
Segment 2
Segment 3
Segment 3 . . etc
[1]
[2]
[3]
[4]
[5]
[6]

Procedure Overview
System Information is Broadcast for each cell
System Information is Broadcast for each cell
Type:
BCH over P-CCPCH
Purpose:
The Node B has
received and stored the
System Info for each
cell (from the RNC) and
now broadcasts it
throughout the cell.
Transport Format (BCH):
› TB size: 246 bits
› TTI: 20 ms
› Conv. Encoding: 1/2
rate
› 16 bit CRC
Type:
BCH over P-CCPCH
Purpose:
The Node B has
received and stored the
System Info for each
cell (from the RNC) and
now broadcasts it
throughout the cell.
Transport Format (BCH):
› TB size: 246 bits
› TTI: 20 ms
› Conv. Encoding: 1/2
rate
› 16 bit CRC
BCH: System Info
BCH: System Info
UEUE
Node
B
Node
B
RNCRNC MSCMSC
BCH: System Info
Segment 1
Segment 2
Segment 2
Segment 3
Segment 3 . . etc
Segment 1
[1]
[2]
[3]

Procedure Overview
1.11) Common Transport Channel Set-up Procedure:
Common Transport Channel Set-up Request (PRACH, AICH, RACH)
Common Transport Channel Set-up Request (PRACH, AICH, RACH)
Type: NBAP
Purpose:
Common Transport
Channels are set up in
two parts. First, the
PRACH, AICH, and
RACH are configured
along with the AAL2
Connection for the
RACH Transport
Channel.
Main IE’s:
› RACH info (TF Set)
› AICH info (Codes, SF,
etc)
› PRACH (TFCS, SF, etc)
Type: NBAP
Purpose:
Common Transport
two parts. First, the
PRACH, AICH, and
RACH are configured
along with the AAL2
Connection for the
RACH Transport
Channel.
Main IE’s:
› RACH info (TF Set)
› AICH info (Codes, SF,
etc)
› PRACH (TFCS, SF, etc)
UEUE
Node
B
Node
B
RNCRNC MSCMSC
System Information Update
Common Transport CH
Set-Up Request
[1]

Procedure Overview
Common Transport Channel Set-up Response (PRACH, AICH, RACH)
Common Transport Channel Set-up Response (PRACH, AICH, RACH)
Type: NBAP
Purpose:
The Node B Ack’s the
1st Com Trans Setup
msg which established
the PRACH, AICH, &
RACH/
Main IE’s:
for RACH
›
Binding and Com ID
› Transport layer address
Type: NBAP
Purpose:
1st Com Trans Setup
the PRACH, AICH, &
RACH/
Main IE’s:
for RACH
›
Binding and Com ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
[1]

Procedure Overview
ALCAP Establish Request (with Binding ID for RACH)
ALCAP Establish Request (with Binding ID for RACH)
Type: ALCAP
Purpose:
This message request
the establishment of an
AAL2 path over the IuB
interface for the RACH.
The SUGR parameter
contains the Binding ID
which was returned to
the RNC in the 1st Com
Trans Ch Setup
Response message
Main IE’s:
› OSAID, DSAID + CEID,
› SUGR,
› AAL2 Destination
Address of Node B
Type: ALCAP
Purpose:
This message request
The SUGR parameter
Trans Ch Setup
Response message
Main IE’s:
› SUGR,
Address of Node B
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
ALCAP ERQ
[1]

Procedure Overview
ALCAP Establish Confirm
ALCAP Establish Confirm
Type: ALCAP
Purpose:
This message confirms
Main IE’s:
› OSAID + DSAID
Type: ALCAP
Purpose:
This message confirms
Main IE’s:
› OSAID + DSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP ECF
ALCAP ERQ
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
[1]

Procedure Overview
Synchronisation over RACH -FP (Framing Protocol)
Synchronisation over RACH -FP (Framing Protocol)
Type: RACH- FP
Purpose:
Framing Protocol
Synchronisation
messages are used to
establish precise timing
between the Node B
and RNC for each
channel that is
established over the
IuB interface.
Main IE’s:
› Control messages
contain time stamps to
establish the time the
message was sent and
when it arrived at the
opposite node.
Type: RACH- FP
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
channel that is
established over the
IuB interface.
Main IE’s:
opposite node.
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP ECF
ALCAP ERQ
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
FP DL Synchronisation
FP UL Synchronisation
[1]
[2]

Procedure Overview
Common Transport Channel Set-up Request (S-CCPCH, FACH, PCH)
Common Transport Channel Set-up Request (S-CCPCH, FACH, PCH)
Type: NBAP
Purpose:
Common Transport
two parts. The 2nd
Com Trans Setup
Request message
specifies the
establishment of the S-
CCPCH, FACH, and
PCH.
Main IE’s:
› FACH info (TF Set)
› PCH info (TF Set)
› S-CCPCH (TFCS, SF,
TFCI, Codes, etc)
Type: NBAP
Purpose:
Common Transport
two parts. The 2nd
Com Trans Setup
Request message
specifies the
establishment of the S-
CCPCH, FACH, and
PCH.
Main IE’s:
› FACH info (TF Set)
› PCH info (TF Set)
› S-CCPCH (TFCS, SF,
TFCI, Codes, etc)
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Common Transport Setup Procedures:
PRACH, AICH and RACH + ALCAP for RACH
Common Transport CH
Set-Up Request
[1]

Procedure Overview
Common Transport Ch. Set-up Response (S-CCPCH, FACH, PCH)
Common Transport Ch. Set-up Response (S-CCPCH, FACH, PCH)
Type: NBAP
Purpose:
2nd Com Trans Setup
the FACH, PCH & S-
CCPCH
Main IE’s:
for PCH and FACH
›
Binding and Com ID
Type: NBAP
Purpose:
2nd Com Trans Setup
the FACH, PCH & S-
CCPCH
Main IE’s:
for PCH and FACH
›
Binding and Com ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
[1]

Procedure Overview
ALCAP Establish Request (with Binding ID for FACH and PCH)
ALCAP Establish Request (with Binding ID for FACH and PCH)
Type: ALCAP
Purpose:
This message request the
establishment of an AAL2
path over the IuB interface
for the FACH. The SUGR
parameter contains the
Binding ID which was
returned to the RNC in the
2nd Com Trans Ch Setup
Response message There
will be separate ALCAP
procedures for the FACH
and the PCH channels.
Main IE’s:
› SUGR,
› AAL2 Dest. Address of
Node B
Type: ALCAP
Purpose:
This message request the
establishment of an AAL2
path over the IuB interface
for the FACH. The SUGR
parameter contains the
Binding ID which was
returned to the RNC in the
2nd Com Trans Ch Setup
Response message There
will be separate ALCAP
procedures for the FACH
and the PCH channels.
Main IE’s:
› SUGR,
› AAL2 Dest. Address of
Node B
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
ALCAP ERQ
[1]

Procedure Overview
ALCAP Establish Confirm (FACH and PCH)
ALCAP Establish Confirm (FACH and PCH)
Type: ALCAP
Purpose:
This message
confirms the
establishment of an
interface for the FACH
and PCH. There will be
separate ALCAP
procedures for the
FACH and the PCH
channels.
Main IE’s:
› OSAID + DSAID
Type: ALCAP
Purpose:
This message
confirms the
establishment of an
interface for the FACH
and PCH. There will be
separate ALCAP
procedures for the
FACH and the PCH
channels.
Main IE’s:
› OSAID + DSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP ECF
ALCAP ERQ
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
[1]

Procedure Overview
Synchronisation over FACH - FP and PCH-FP(Framing Protocol)
Synchronisation over FACH - FP and PCH-FP(Framing Protocol)
Type: FACH-FP
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
channel. There will be
separate sync.
procedures for the
FACH and the PCH
channels.
Main IE’s:
opposite node.
Type: FACH-FP
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
separate sync.
procedures for the
FACH and the PCH
channels.
Main IE’s:
opposite node.
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP ERQ
Common Transport CH
Set-Up Response
Common Transport CH
Set-Up Request
ALCAP ECF
[1]
[2]

Procedure Overview
1.21) Update System Information Procedure:
System Information Update Request (SIB 5 - Channel Updates)
System Information Update Request (SIB 5 - Channel Updates)
Type: NBAP
Purpose:
The RNC announces
the configuration of the
common channels for
each cell by changing
SIB5. This info is
relayed to UE’s via the
BCH.
Main IE’s:
› References to other
SIBs
› PICH Power offset
› AICH Power offset
› P-CCPCH info
› S-CCPCH info
Type: NBAP
Purpose:
The RNC announces
the configuration of the
common channels for
each cell by changing
SIB5. This info is
relayed to UE’s via the
BCH.
Main IE’s:
› References to other
SIBs
› PICH Power offset
› AICH Power offset
› P-CCPCH info
› S-CCPCH info
SIB 5
UEUE
Node
B
Node
B
RNCRNC MSCMSC
PRACH, AICH, S-CCPCH, FACH, PCH and RACH +
ALCAP and FP-Sync. for RACH, FACH and PCH
[1]

Procedure Overview
Resource Status Indication (Service impacting, com ctrl port enabled)
Resource Status Indication (Service impacting, com ctrl port enabled)
Type: NBAP
Purpose:
The Node B has set up
all the common
transport channels and
is ready to unblock the
cell(s). It sends ID
number of the enabled
com control port to the
RNC.
Main IE’s:
› Trans ID
› Com Control Port ID
› Service Impacting
Indication
Type: NBAP
Purpose:
The Node B has set up
all the common
transport channels and
is ready to unblock the
cell(s). It sends ID
number of the enabled
com control port to the
RNC.
Main IE’s:
› Trans ID
› Com Control Port ID
› Service Impacting
Indication
UEUE
Node
B
Node
B
RNCRNC MSCMSC
SIB 5
[1]

Procedure Overview
Unblock Resource Indication Message
Unblock Resource Indication Message
Type: NBAP
Purpose:
The Node B is ready to
unblock the new cell(s).
Main IE’s:
› Trans ID
› Cell ID
› Unblock resource
Type: NBAP
Purpose:
The Node B is ready to
unblock the new cell(s).
Main IE’s:
› Trans ID
› Cell ID
› Unblock resource
UEUE
Node
B
Node
B
RNCRNC MSCMSC
SIB 5
Unblock Resource Ind
[1]

Procedure Overview
System Information Update Request (SIB 3 - Cell Unblocked)
System Information Update Request (SIB 3 - Cell Unblocked)
Type: NBAP
Purpose:
The RNC updates SIB3
to “Unbarred”
Main IE’s:
› Cell ID
› Transaction ID
› SIB 3 Updated to
unbarred
Type: NBAP
Purpose:
to “Unbarred”
Main IE’s:
› Cell ID
› Transaction ID
› SIB 3 Updated to
unbarred
UEUE
Node
B
Node
B
RNCRNC MSCMSC
SIB 5
SIB 3 [1]

Procedure Overview
System Information Update Response
System Information Update Response
Type: NBAP
Purpose:
to “Unbarred”
Main IE’s:
› Transaction ID
Type: NBAP
Purpose:
to “Unbarred”
Main IE’s:
› Transaction ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
SIB 5
SIB 3
[1]

PART 1 - NODE B INITIALISATION -
SUMMARY
UEUE
Node
B
Node
B
RNCRNC MSCMSC
CellSetup Procedure
Common Transport Setup Procedures
for PRACH, AICH, S-CCPCH, FACH,
PCH and RACH + ALCAP and FP-Sync.
for RACH, FACH and PCH
System Information Update Procedure
Request - SIB 5
Update Resources and Unblock Cell
Request - SIB 3

PART 2
UE “Camp On” &
Location Update

PART 2 - UE LOCATION UPDATE
PROCEDURE
2.1) Location Update: Random Access Detection Procedure2.1) Location Update: Random Access Detection Procedure
Type: RACH
Purpose:
The Node B receives
and stores the System
Info for each cell and
broadcasts it throughout
the cell. The UE reads
SIBs from BCH (or
FACH) and using the
access preamble
signature obtained from
the BCH, it broadcasts
an access request on
the RACH. It starts with
a low estimate for
transmit power and
ramps up until it the UE
is detected by the Node
B.
Type: RACH
Purpose:
The Node B receives
and stores the System
Info for each cell and
broadcasts it throughout
the cell. The UE reads
SIBs from BCH (or
FACH) and using the
access preamble
signature obtained from
the BCH, it broadcasts
an access request on
the RACH. It starts with
a low estimate for
transmit power and
ramps up until it the UE
is detected by the Node
B.
UEUE
Node
B
Node
B
RNCRNC MSCMSC
BCH: System Info
BCH: System Info
BCH: System Info
Preamble
Preamble
Preamble
[1]
[2]
[3]
[4]
[5]
[6]

PROCEDURE
2.2) Location Update: Random Access Detection Procedure:
Access Preamble and AICH Indication
2.2) Location Update: Random Access Detection Procedure:
Access Preamble and AICH Indication
Type:
BCH over P-
CCPCH
Purpose:
The Node B detects the
access request from
the UE and returns an
Access indication on
the AICH.
Type:
BCH over P-
CCPCH
Purpose:
The Node B detects the
access request from
the UE and returns an
Access indication on
the AICH.
UEUE
Node
B
Node
B
RNCRNC MSCMSC
BCH: System Info
BCH: System Info
BCH: System Info
AICH: Access Indication
Preamble
Preamble
[1]
Preamble

PROCEDURE
Type: RRC
Channels:
CCCH / RACH
Main IE’s:
› Initial UE ID
› Establishment Cause
› Initial UE capability
Type: RRC
Channels:
CCCH / RACH
Main IE’s:
› Initial UE ID
› Establishment Cause
› Initial UE capability
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC Connection Request
(PRACH)
2.3) Location Update: Radio Signalling Bearer Establish Procedure:
RRC: Connection Request Message
RRC: Connection Request Message
Random Access Detection
[1]

PROCEDURE
Procedure Overview
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: NBAP
Purpose:
RNC tells Node B to
configure a Radio
Bearer.
Main IE’s:
RL Setup Req
› Cell ID,
› TFS / TFCS
› Frequency
› UL Scrambling Code
› DL Channelisation Code
› Power Control Info
› RL Setup Response
› Transport Layer Add
› Sig. Link termination
› DCH Binding ID
Type: NBAP
Purpose:
RNC tells Node B to
configure a Radio
Bearer.
Main IE’s:
RL Setup Req
› Cell ID,
› TFS / TFCS
› Frequency
› UL Scrambling Code
› Power Control Info
› RL Setup Response
› Transport Layer Add
› Sig. Link termination
› DCH Binding ID
RL Setup Request
RL Setup Response
RL Set-up Request and RL Set-up Response Messages
RL Set-up Request and RL Set-up Response Messages
(PRACH)
[1]
[2]

PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: ALCAP
Purpose:
This message sequence
requests (and confirms)
interface for a DCCH.
The SUGR parameter
Trans Ch Setup
Response message
Main IE’s:
› SUGR,
Address of Node B
Type: ALCAP
Purpose:
This message sequence
requests (and confirms)
interface for a DCCH.
The SUGR parameter
Trans Ch Setup
Response message
Main IE’s:
› SUGR,
Address of Node B
Establish Request (ERQ) and Confirm (ECF) Messages
Establish Request (ERQ) and Confirm (ECF) Messages
RL Setup Request
RL Setup Response
(PRACH)
ALCAP ERQ
ALCAP ECF
[1]
[2]

PROCEDURE
Procedure Overview
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: DCH-FP
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
separate sync.
procedures for all
CCCH and DCCH
channels.
Main IE’s:
opposite node.
Type: DCH-FP
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
separate sync.
procedures for all
CCCH and DCCH
channels.
Main IE’s:
opposite node.
DCH-FP DL / UL Synchronisation Messages
DCH-FP DL / UL Synchronisation Messages
RL Setup Request
RL Setup Response
(PRACH)
ALCAP ERQ
ALCAP ECF
[1]
[2]

PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: RRC
Purpose
RNC informs the UE that the
DCH channel is established.
UE Ack’s by replying on the
DCCH with a Setup
Complete.
Channels:
1. FACH 2. DCCH
Main IE’s:
RRC Con Setup
› Initial UE ID + RNTI,
› CapUpReq,
› TFS, +TFCS,
› frequency + Power control
info.
› DL Scram + Chann codes,
› RRC Con Setup
Complete
› UE Capability,
› Ciphering + Integrity info
Type: RRC
Purpose
RNC informs the UE that the
DCH channel is established.
UE Ack’s by replying on the
DCCH with a Setup
Complete.
Channels:
1. FACH 2. DCCH
Main IE’s:
RRC Con Setup
› Initial UE ID + RNTI,
› CapUpReq,
› TFS, +TFCS,
› frequency + Power control
info.
› DL Scram + Chann codes,
› RRC Con Setup
Complete
› UE Capability,
› Ciphering + Integrity info
RRC Connection Setup
(FACH)
RRC Conn Setup Comp
(DCCH)
RRC Connection Set-up / Complete Messages
RRC Connection Set-up / Complete Messages
RL Setup Request
RL Setup Response
(PRACH)
ALCAP ERQ
ALCAP ECF
[1]
[2]

PROCEDURE
Type: RRC
Purpose
UE initiates a location
update procedure
Channels:
DCCH
Main IE’s:
› Update Type (normal)
› Cipher Key Seq No.
› Location Area Info
› UE Classmark
› UE ID (IMSI or TMSI)
Type: RRC
Purpose
UE initiates a location
update procedure
Channels:
DCCH
Main IE’s:
› UE Classmark
› UE ID (IMSI or TMSI)
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Radio Signalling Bearer Establishment Procedure
2.8) Location Update: Location Update Request Procedure:
RRC: Initial DT [NAS Location Update Request Message]
RRC: Initial DT [NAS Location Update Request Message]
RRC: Initial Direct Transfer
(Location Update Request)
[1]

PROCEDURE
Type: RANAP
Purpose:
RNC relays the
Location Update
message to the
NAS at the CN
Channels:
DCCH
Main IE’s:
› UE Classmark
› UE ID (IMSI/TMSI)
Type: RANAP
Purpose:
RNC relays the
Location Update
message to the
NAS at the CN
Channels:
DCCH
Main IE’s:
› UE Classmark
› UE ID (IMSI/TMSI)
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP: DT
(Location Upd Request)
RANAP: DT [NAS Location Update Request Message]
RANAP: DT [NAS Location Update Request Message]
(Location Update Request) [1]

UEUE
Node
B
Node
B
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PROCEDURE
Type: MAP
Purpose:
The Current MSC/VLR
may or may not have a
record of this UE. If it
doesn’t, it sends a
MAP Send_ID Request
to a Previous VLR to
retrieve IMSI and
authentication data for
this UE.
Channels:
SS7 Signalling
Main IE’s:
Type: MAP
Purpose:
The Current MSC/VLR
may or may not have a
record of this UE. If it
doesn’t, it sends a
MAP Send_ID Request
to a Previous VLR to
retrieve IMSI and
authentication data for
this UE.
Channels:
SS7 Signalling
Main IE’s:
MAP Send_Identification Request
MAP Send_Identification Request
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req
[1]

MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNCUEUE
Node
B
Node
B
PROCEDURE
Type: MAP
Purpose:
The Previous MSC-VLR
replies with the MAP
Identification
Acknowledge
containing the
requested UE
information. The
network may now
decide to initiate the
NAS Identity Request
procedure
Channels:
SS7 Signalling
Main IE’s:
Type: MAP
Purpose:
The Previous MSC-VLR
replies with the MAP
Identification
Acknowledge
containing the
requested UE
information. The
network may now
decide to initiate the
NAS Identity Request
procedure
Channels:
SS7 Signalling
Main IE’s:
MAP Send_Identification Acknowledge
MAP Send_Identification Acknowledge
MAP
Send ID Ack
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req.
[1]

MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PROCEDURE
Type: RANAP
Purpose:
If the CN decides to
initiate the Identity
Request Procedure it
sends a RANAP: DT
Identity Request to the
RNC for forwarding to
the UE (via RRC: DT).
Channels:
AAL5/ATM
Main IE’s:
› ID Type
Type: RANAP
Purpose:
If the CN decides to
initiate the Identity
Request Procedure it
sends a RANAP: DT
Identity Request to the
RNC for forwarding to
the UE (via RRC: DT).
Channels:
AAL5/ATM
Main IE’s:
› ID Type
UEUE
Node
B
Node
B
2.12) Location Update: Identity Request Procedure:
RANAP: Direct Transfer [NAS Identity Request Message]
RANAP: Direct Transfer [NAS Identity Request Message]
RANAP: DT
NAS: Identity Req.
MAP
Send ID Ack
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req.
[1]

MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PROCEDURE
Type: RRC
Purpose:
The RNC forwards the
Identity Request
message to the UE via
RRC: Direct Transfer.
Channels:
DCCH
Main IE’s:
› ID Type
Type: RRC
Purpose:
The RNC forwards the
Identity Request
message to the UE via
RRC: Direct Transfer.
Channels:
DCCH
Main IE’s:
› ID Type
UEUE Node
B
Node
B
RRC: Direct Transfer [NAS Identity Request Message]
RRC: Direct Transfer [NAS Identity Request Message]
RANAP: DT
NAS: Identity Req.RRC: DT DCCH
NAS: Identity Request
MAP
Send ID Ack
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req.
[1]

MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PROCEDURE
Type: RRC
Purpose:
The UE must be
prepared to respond
to an ID Request
message at any time
while an RR
connection exists. It
should reply with an
Identity Response
message which
contains the info
requested by the CN.
Channels:
DCCH
Main IE’s:
› ID Type
Type: RRC
Purpose:
The UE must be
prepared to respond
to an ID Request
message at any time
while an RR
connection exists. It
should reply with an
Identity Response
message which
contains the info
requested by the CN.
Channels:
DCCH
Main IE’s:
› ID Type
UEUE
Node
B
Node
B
RRC: Direct Transfer [NAS Identity Response Message]
RRC: Direct Transfer [NAS Identity Response Message]
RRC: DT DCCH
NAS: Identity Response
RANAP: DT
NAS: Identity Req.RRC: DT DCCH
MAP
Send ID Ack
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req.
[1]

MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PROCEDURE
Type: RANAP
Purpose:
The RNC relays the ID
Response message to
the CN.
Channels:
AAL5/ATM
Main IE’s:
› ID Type
Type: RANAP
Purpose:
The RNC relays the ID
Response message to
the CN.
Channels:
AAL5/ATM
Main IE’s:
› ID Type
UEUE
Node
B
Node
B
RANAP: Direct Transfer [NAS Identity Response Message]
RANAP: Direct Transfer [NAS Identity Response Message]
RANAP: DT
Send ID Response
RRC: DT DCCH
NAS: Send ID Response
RANAP: DT
NAS: Identity Req.
MAP
Send ID Ack
MAP
Send ID Req.
RANAP: DT
Loc. Upd Req.
RRC: DT DCCH
[1]

RNCRNC MSCMSCUEUE
Node
B
Node
B
PROCEDURE
Type: RANAP &
RRC
Purpose:
The CN may now elect to
initiate the authentication
procedure (I.e. if the
authentication information
requested from the
Previous MSC/VLR is not
returned in the MAP
Send_ID_ACK Message.
The CN sends the
Authentication Request
message and starts
T3260. The NAS
message is relayed by
the RNC via RRC: DT.
Channels:
AAL5/ATM -> DCCH
Main IE’s:
Type: RANAP &
RRC
Purpose:
The CN may now elect to
initiate the authentication
procedure (I.e. if the
authentication information
requested from the
Previous MSC/VLR is not
returned in the MAP
Send_ID_ACK Message.
The CN sends the
Authentication Request
message and starts
T3260. The NAS
message is relayed by
the RNC via RRC: DT.
Channels:
AAL5/ATM -> DCCH
Main IE’s:
2.16) Location Update: Authentication Procedure:
RANAP: Direct Transfer [NAS Authentication Request Message]
RANAP: Direct Transfer [NAS Authentication Request Message]
RANAP: DT
NAS: Auth. Request
Location Update Request Procedure (RRC/RANAP DT)
Identity Request Procedure (RRC/RANAP DT) Optional
[1]

PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC: Direct Transfer [NAS Authentication Request Message]
RRC: Direct Transfer [NAS Authentication Request Message]
RRC: DT DCCH
NAS: Auth Request
RANAP: DT
NAS: Auth Request[1]

PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs:
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC: Direct Transfer [NAS Authentication Response Message]
RRC: Direct Transfer [NAS Authentication Response Message]
RRC: DT DCCH
NAS: Auth Request
RANAP: DT
NAS: Auth Request
RRC: DT DCCH
NAS: Auth Response
[1]

PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP: DT [NAS Authentication Response Message]
RANAP: DT [NAS Authentication Response Message]
RRC: DT DCCH
NAS: Auth Request
RANAP: DT
NAS: Auth Request
RRC: DT DCCH
NAS: Auth Response RANAP: DT
NAS: Auth Response
[1]

PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Authentication Request Procedure (RRC/RANAP DT) Optional
RANAP: DT
Location Update Accept
2.20) Location Update: Location Update Accept Procedure:
RANAP: Direct Transfer [NAS Location Update Accept Message]
RANAP: Direct Transfer [NAS Location Update Accept Message]
[1]

PROCEDURE
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC: DT
RRC: Direct Transfer [NAS Location Update Accept Message]
RRC: Direct Transfer [NAS Location Update Accept Message]
RANAP: DT
[1]

PROCEDURE
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC: DT
TMSI Reallocation Complete
2.22) Location Update: TMSI Reallocation Complete Procedure:
RRC: Direct Transfer [NAS TMSI Reallocation Complete]
RRC: Direct Transfer [NAS TMSI Reallocation Complete]
RRC: DT
RANAP: DT
[1]

PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP: DT
TMSI Reallocation Accept
RANAP: Direct Transfer [NAS TMSI Reallocation Complete]
RANAP: Direct Transfer [NAS TMSI Reallocation Complete]
RRC: DT
TMSI Reallocation Complete
RRC: DT
RANAP: DT
[1]

PROCEDURE
Type: RRC
Purpose:
This message
originates in the RNC
and informs the UE
that the DCH should
be released. One or
more of these release
messages are sent in
the Unack mode.
Channels:
DCCH
Main IE’s:
› Signalling Flow Info
List
› Flow Identifier
Type: RRC
Purpose:
This message
originates in the RNC
and informs the UE
that the DCH should
be released. One or
more of these release
messages are sent in
the Unack mode.
Channels:
DCCH
Main IE’s:
List
› Flow Identifier
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Location Update Accept Procedure (RRC/RANAP DT)
TMSI Reallocation Complete Procedure (RRC/RANAP DT)
2.24) Location Update: Radio Signalling Bearer Release Procedure:
RRC: Connection Release (Unacknowledged)
RRC: Connection Release (Unacknowledged)
RRC: Connection Release
[1]

PROCEDURE
Type: RRC
Purpose:
This message
originates in the UE
and informs the RNC
that the DCH is
released. One or more
of these release
complete messages
are sent in the Unack
mode.
Channels:
DCCH
Main IE’s:
List
› Flow Identifier
Type: RRC
Purpose:
This message
originates in the UE
and informs the RNC
that the DCH is
released. One or more
of these release
complete messages
are sent in the Unack
mode.
Channels:
DCCH
Main IE’s:
List
› Flow Identifier
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC: Connection Release Complete (Unacknowledged)
RRC: Connection Release Complete (Unacknowledged)
RRC: Connection Complete
RRC: Connection Release
[1]

PROCEDURE
Type: NBAP
Purpose:
These messages
request and confirm
that the Radio Link
resources reserved in
the Node B for the
DCH be released.
Channels:
DCCH
Main IE’s:
› Node B
Communication
Context ID
› Transaction ID
› RL Information
› RL ID
Type: NBAP
Purpose:
These messages
request and confirm
that the Radio Link
resources reserved in
the Node B for the
DCH be released.
Channels:
DCCH
Main IE’s:
› Node B
Communication
Context ID
› Transaction ID
› RL Information
› RL ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
NBAP: RL Deletion Request
NBAP: RL Del Complete
NBAP: RL Deletion Request / Complete
NBAP: RL Deletion Request / Complete
RRC: Release/Release Complete
[1]
[2]

PROCEDURE
Type: ALCAP
Purpose:
These messages
request and confirm
that the AAL2 bearer
over the IuB Interface
for the DCH be
released.
Channels:
AAL2/ATM
Main IE’s:
Release Request
› DSAID + Cause
› Release Confirm
› DSAID
Type: ALCAP
Purpose:
These messages
request and confirm
that the AAL2 bearer
over the IuB Interface
for the DCH be
released.
Channels:
AAL2/ATM
Main IE’s:
Release Request
› DSAID + Cause
› Release Confirm
› DSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP: Release / Release Confirm
ALCAP: Release / Release Confirm
NBAP: RL Deletion/Complete
ALCAP: Release Request
ALCAP: Release Confirm
[1]
[2]

PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP Release Procedure
Summary
NBAP: RL Deletion/Complete

PARTS 3 - 4
Circuit Switched Calls
Parts 3 & 4
Call Setup and Tear Down Scenarios

PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure Overview
In this Procedure the UE is attached to the Network in Idle mode.
The call setup is Mobile Originated (mo).
The following steps need to be executed in order for a mo call to
complete;
1. RRC Connection Setup
2. Service Request
3. Security Procedures (Identity / Authentication / Security mode)
4. Call Setup Request
5. Radio Link and RAB Configuration
6. Call Connection

(CS)
Procedure OverviewMessage (1): Connection RequestMessage (1): Connection Request
Type:
RRC
Channels:
CCCH / RACH
Main IE’s:
1. Initial UE ID
Establishment Cause
Initial UE capability
Type:
RRC
Channels:
CCCH / RACH
Main IE’s:
1. Initial UE ID
Establishment Cause
UEUE
Node
B
Node
B
RNCRNC MSCMSC
(RACH)
[1]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (2): Radio Link Set-up Request / ResponseMessages (2): Radio Link Set-up Request / Response
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
NBAP
Main IE’s:
1. Cell ID, TFS / TFCS
Frequency,
UL Scrambling Code
DL Channelisation Code
Power Control Info
2. Transport Layer Address Sig.
Link termination
DCH Binding ID
Type:
NBAP
Main IE’s:
Frequency,
UL Scrambling Code
Power Control Info
Link termination
DCH Binding ID
NBAP
RL setup Req.
NBAP
RL setup Resp.
(RACH)
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (3): Establish Request (ERQ) / Confirm (ECF)Messages (3): Establish Request (ERQ) / Confirm (ECF)
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
ALCAP
Main IE’s:
Destination address, DSAI,
ALC, CEID, OSAI, SUGR,
SSISU
Type:
ALCAP
Main IE’s:
Destination address, DSAI,
ALC, CEID, OSAI, SUGR,
SSISU
NBAP
RL setup Req.
NBAP
RL setup Resp.
ALCAP
ERQ
ALCAP ECF
(RACH)
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (4): DCH-FP DL / UL SynchronisationMessages (4): DCH-FP DL / UL Synchronisation
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
DCH-FP
Main IE’s:
Type:
DCH-FP
Main IE’s:
ALCAP
ERQ
ALCAP ECF
(RACH)
FP DL
Synchronisation
NBAP
RL setup Req.
NBAP
RL setup Resp.
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (5): Connection Set-up / CompleteMessages (5): Connection Set-up / Complete
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
RRC
Channels:
1. FACH
2. DCCH
Main IE’s:
1. Initial UE ID, RNTI,
CapUpReq, TFS,
TFCS, frequ,
DL Scram + Chann codes,
Power control info.
2. UE Capability, Ciphering,
Integrity info
Type:
RRC
Channels:
1. FACH
2. DCCH
Main IE’s:
CapUpReq, TFS,
TFCS, frequ,
Power control info.
Integrity info
(RACH)
FP DL
Synchronisation
RRC Conn. Setup
(FACH)
RRC Conn. Setup Comp
(DCCH)
ALCAP
ERQ
ALCAP ECF
NBAP
RL setup Req.
NBAP
RL setup Resp.
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (6): Initial Direct Transfer + Initial UE messageMessages (6): Initial Direct Transfer + Initial UE message
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
1. RRC
2. RANAP
Channel:
DCCH
Main IE’s:
Type:
1. RRC
2. RANAP
Channel:
DCCH
Main IE’s:
RANAP Initial
UE
(CM Service Req.)
(SCCP Con Req.)
RRC Initial D T
(CM Service Request.)
[1] [2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (7): Connection Confirm + CM Service AcceptMessages (7): Connection Confirm + CM Service Accept
UEUE
Node
B
Node
B
RNCRNC MSCMSCType:
1. SCCP / RANAP DT
2. RRC DL DT
3. RANAP DT
4. RRC DL DT
Channel:
DCCH
Main IE’s:
Type:
1. SCCP / RANAP DT
2. RRC DL DT
3. RANAP DT
4. RRC DL DT
Channel:
DCCH
Main IE’s:
RANAP Initial
UE
(CM Service Req.)
(SCCP Con Req.)
RRC Initial DT
(CM Service Request)
RRC DL DT (OPT)
(CM Service Acc)
RANAP DT
(CM Service Acc)
SCCP Conn Conf
[1]
[2]
[3]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (8): Authentication + Security Mode CommandsMessages (8): Authentication + Security Mode Commands
Type:
1. RANAP
2. RRC
3. RRC
4. RANAP
Channel:
DCCH
Main IE’s:
Type:
1. RANAP
2. RRC
3. RRC
4. RANAP
Channel:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP Initial
UE
(CM Service Req.)
(SCCP Con Req.)
RRC Initial DT
Authentication
RRC
Security Mode Command
RANAP
RRC
Security Mode Complete RANAP
Security Mode Complete
[1]
[4]
[2]
[3]
SCCP Conn Conf
RRC DL DT (OPT)
(CM Service Acc)
RANAP DT
(CM Service Acc)
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Authentication and Security Mode Commands
Description
The procedures detailed on
the right may be used
together or separately
(note: Security mode
requires that authentication
has already been done at
least one time).
Their presence is
dependant on which
associated procedure is
being carried out and on
Operator requirements.
For First Call there will be
No Identity request, but
there will be authentication
and there will be Security
mode, the latter being MSC
- RNC only .
Description
The procedures detailed on
the right may be used
together or separately
(note: Security mode
requires that authentication
has already been done at
least one time).
Their presence is
dependant on which
associated procedure is
being carried out and on
Operator requirements.
For First Call there will be
No Identity request, but
there will be authentication
and there will be Security
mode, the latter being MSC
- RNC only .
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Identity Request
Procedure
Identity Request
Procedure
AuthenticationAuthentication
Security ModeSecurity Mode

(CS)
Procedure OverviewIdentity Request Procedure: NAS: Identity RequestIdentity Request Procedure: NAS: Identity Request
Type: NAS (PMM)
Purpose:
Identity Request: Used by the
CN to request the UE identity.
Can be of type;
[IMSI, IMEI, IEMISV, TMSI]
Identity Response: UE reply to
the Identity request can be of
type;
Main IE’s:
Req: Identity Request Type
Res: Mobile Identity
Type: NAS (PMM)
Purpose:
Can be of type;
type;
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Identity Request
Procedure
Identity Request
Procedure
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC UL D T
(Identity Response.)
RANAP DT
(Identity Request)

(CS)
Type: NAS (PMM)
Purpose:
UE Authentication
Network Authentication
Integrity Key exchange
Ciphering Key Exchange
Main IE’s:
Req: CK Sequence Number
RAND
AUTN
Res: CK Sequence Number
RES
Type: NAS (PMM)
Purpose:
UE Authentication
Main IE’s:
RAND
AUTN
RES
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Identity Request
Procedure
Identity Request
Procedure
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)
RRC DL DT
(Authentication Request)
RANAP DT
RRC UL D T
(Authentication Response)
RANAP DT

(CS)
Type:
RANAP DT
RRC DT
Purpose:
Selection of Integrity and
Ciphering Algorithms (by RNC)
Control Of Integrity and
Ciphering Operation.
Main IE’s:
SM Command:
1. Algorithm List, IK
2. Integrity Check Info
Integrity prot. mode info
Domain ID
SM Complete:
1.UL Integrity protection info
2. Chosen Integrity Algorithm
Type:
RANAP DT
RRC DT
Purpose:
Main IE’s:
SM Command:
Domain ID
SM Complete:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Identity Request
Procedure
Identity Request
Procedure
RRC
RANAP
Security Mode
Command
RRC
RANAP
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC Initial D T
RANAP DT
(Identity Request)
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT

(CS)
Procedure OverviewMessages (9): Common IDMessages (9): Common ID
Type:
1. RANAP
Main IE’s:
1. Permanent NAS ID
Type:
1. RANAP
Main IE’s:
1. Permanent NAS ID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP Initial
UE
(CM Service Req.)
(SCCP Con Req.)
RRC Initial DT
Authentication
RRC
RANAP
RRC
RANAP
Common ID
[1]
SCCP Conn Conf
RANAP DT
(CM Service Acc)RRC DL DT (OPT)
(CM Service Acc)
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (10): Call Setup + Call ProceedingMessages (10): Call Setup + Call Proceeding
Type:
1. RRC UL DT
2. RANAP DT
3. RANAP DT
4. RRC DL DT
Main IE’s:
1. Calling/Called Party
Numbers,
Calling/Called party sub-
address,
bearer capability
Type:
1. RRC UL DT
2. RANAP DT
3. RANAP DT
4. RRC DL DT
Main IE’s:
1. Calling/Called Party
Numbers,
Calling/Called party sub-
address,
bearer capability
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Service Request / Authentication / Security
RRC UL DT
(Call Setup) RANAP DT
(Call Setup)
RRC DL DT
(Call Proceeding)
RANAP DT
(Call Proceeding)
[2]
[3]
[1]
[4]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (11): RAB Assignment Request + Iucs ALCAP SetupMessages (11): RAB Assignment Request + Iucs ALCAP Setup
Type:
1. RANAP
2. ALCAP
3. ALCAP
Main IE’s:
1. RAB Param, NAS Bind Info,
User Plane Mode, Transport
Add, IU Transport
Association
2. CEID, Destination address,
DSAID, OSAID
DSAID, OSAID
Type:
1. RANAP
2. ALCAP
3. ALCAP
Main IE’s:
1. RAB Param, NAS Bind Info,
User Plane Mode, Transport
Add, IU Transport
Association
DSAID, OSAID
DSAID, OSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC DL DT
(Call Proceeding)
RRC UL DT
(Call Setup)
RANAP DT
(Call Proceeding)
RANAP
RAB Assignment Req.
ALCAP
ERQ
ALCAP
ECF
[1]
[2]
[3]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure Overview
Messages (12): RL Reconfigure Prepare / ReadyMessages (12): RL Reconfigure Prepare / Ready
Type:
1. NBAP
2. NBAP
Main IE’s:
1. TFS ; TFCS; power control
info, Transaction ID
2. Transaction ID, DL Chan
code, Transport Layer addr.
Type:
1. NBAP
2. NBAP
Main IE’s:
1. TFS ; TFCS; power control
info, Transaction ID
2. Transaction ID, DL Chan
code, Transport Layer addr.
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC DL DT
(Call Proceeding)
RRC UL DT
(Call Setup)
RANAP DT
(Call Proceeding)
RANAP
RAB Assignment Req.
NBAP
RL Reconfigure Prepare
NBAP
RL Reconfigure Ready
ALCAP
ERQ
ALCAP
ECF[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (13): RAB - Iub Establish Request / ConfirmMessages (13): RAB - Iub Establish Request / Confirm
Type:
1. ALCAP
2. ALCAP
Main IE’s:
DSAID, OSAID
DSAID, OSAID
Type:
1. ALCAP
2. ALCAP
Main IE’s:
DSAID, OSAID
DSAID, OSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Continued from NBAP RL
Reconfigure Procedure
ALCAP
ERQ
ALCAP
ECF
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (14): RAB - Iucs Establish Request / ConfirmMessages (14): RAB - Iucs Establish Request / Confirm
Type:
1. ALCAP
2. ALCAP
Main IE’s:
DSAID, OSAID
DSAID, OSAID
Type:
1. ALCAP
2. ALCAP
Main IE’s:
DSAID, OSAID
DSAID, OSAID
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP
ERQ
ALCAP
ECF
NBAP
RL Reconfigure Commit
[1]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (15): RAB - Radio Bearer Setup / CompleteMessages (15): RAB - Radio Bearer Setup / Complete
Type:
1. RRC
2. RRC
Channel
DCCH
Main IE’s:
Type:
1. RRC
2. RRC
Channel
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC Radio Bearer Setup
(DCCH)
RRC RB Setup Comp
(DCCH)
ALCAP
ERQ
ALCAP
ECF
NBAP
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (16): RAB Assignment ResponseMessages (16): RAB Assignment Response
Type:
1. RANAP
2. IUUP
Main IE’s:
Type:
1. RANAP
2. IUUP
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
(DCCH)
RRC RB Setup Comp
(DCCH)
RANAP
RAB Assignment Resp
ALCAP
ERQ
ALCAP
ECF
NBAP
[1]
MSC
RNC
NB
UE
UTRAN Status
IUUP
Initialisation
[2]

(CS)
Procedure OverviewMessages (17): Call ConnectMessages (17): Call Connect
Type:
1. RANAP DT
2. RRC DT
Channel
DCCH
Main IE’s:
Type:
1. RANAP DT
2. RRC DT
Channel
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Call Setup Request and RAB Assignment
RRC DL DT
(Alerting)
RANAP DT
(Alerting)
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

(CS)
Procedure OverviewMessages (18): Connect / Connect AcknowledgeMessages (18): Connect / Connect Acknowledge
Type:
1. RANAP DT
2. RRC DL DT
3. RRC UL DT
4. RANAP DT
Channel
DCCH / DCH
Main IE’s:
Type:
1. RANAP DT
2. RRC DL DT
3. RRC UL DT
4. RANAP DT
Channel
DCCH / DCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Call Setup Request and RAB Assignment
RRC DL DT
(Alerting)
RANAP DT
(Alerting)
RRC DL DT
(CC: Connect)
RANAP DT
(CC: Connect)
RRC UL DT
(CC: Connect Ack)
RANAP DT
(CC: Connect Ack)
Call ConnectedCall Connected
[1]
[4]
[2]
[3]
MSC
RNC
NB
UE
UTRAN Status

PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure Overview.
In this Procedure the UE is attached to the Network in Call
Processing mode. The call tear-down is Mobile Originated (mo).
The following steps need to be executed in order for the mobile to
tear-down the call;
1. Initiate Call Release
2. Initiate Iu Release Procedure
3. Release Iu Connection to MSC for UE
4. Release RRC Connection to UE
5. Delete Radio Link Resources in UTRAN
6. Release RAB on Iub for UE

DOWN (CS)
Procedure OverviewMessages (1): CC: DisconnectMessages (1): CC: Disconnect
Type:
1. RRC UL DT
2. RANAP DT
Channels:
DCCH
Main IE’s:
Type:
1. RRC UL DT
2. RANAP DT
Channels:
DCCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC UL DT
(CC: Disconnect) RANAP DT
(CC: Disconnect)
[1] [2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (2): CC: Release + Release CompleteMessages (2): CC: Release + Release Complete
Type:
1. RANAP DT
2. RRC DL DT
3. RRC UL DT
4. RANAP DT
Channels:
DCCH / DCH
Main IE’s:
Type:
1. RANAP DT
2. RRC DL DT
3. RRC UL DT
4. RANAP DT
Channels:
DCCH / DCH
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RRC UL DT
(CC: Disconnect) RANAP DT
(CC: Disconnect)
RRC DL DT
(CC: Release)
RANAP DT
(CC: Release)
RRC UL DT
(CC: Release Complete) RANAP DT
(CC: Release Complete )
[1]
[4]
[2]
[3]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessage (3): Iu Release CommandMessage (3): Iu Release Command
Type:
1. RANAP
2. RANAP
Main IE’s:
1. Cause=Normal Release
Type:
1. RANAP
2. RANAP
Main IE’s:
1. Cause=Normal Release
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP
Iu Release Command
CC: Call Release
RANAP
Iu Release Complete
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (4): RAB - Release Request / Confirm (Iucs)Messages (4): RAB - Release Request / Confirm (Iucs)
Type:
1. ALCAP
2. ALCAP
Main IE’s:
1. DSAID, Cause= 31, normal
unspecified
Type:
1. ALCAP
2. ALCAP
Main IE’s:
unspecified
UEUE
Node
B
Node
B
RNCRNC MSCMSC
RANAP
Iu Release Command
CC: Call Release
ALCAP
Release Request
ALCAP
Release Confirm
RANAP
Iu Release Complete
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (5): RRC - Connection Release / CompleteMessages (5): RRC - Connection Release / Complete
Type:
1. RRC
2. RRC
Main IE’s:
Type:
1. RRC
2. RRC
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
CC: Call Release
RANAP
Iu Release Command
ALCAP
Release Request
ALCAP
Release Confirm
RRC
Connection Release
RRC
Con. Release Complete
RANAP
Iu Release Complete
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (6): RL Deletion Request / ResponseMessages (6): RL Deletion Request / Response
Type:
1. NBAP
2. NBAP
Main IE’s:
Type:
1. NBAP
2. NBAP
Main IE’s:
UEUE
Node
B
Node
B
RNCRNC MSCMSC
CC: Call Release
RANAP
Iu Release Command
ALCAP
Release Request
ALCAP
Release Confirm
RRC
Connection Release
RRC
NBAP
RL Deletion Request
NBAP
RL Deletion Response
RANAP
Iu Release Complete
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (7): RAB - Release Request / Confirm (Iub)Messages (7): RAB - Release Request / Confirm (Iub)
Type:
1. ALCAP
2. ALCAP
Main IE’s:
unspecified
Type:
1. ALCAP
2. ALCAP
Main IE’s:
unspecified
UEUE
Node
B
Node
B
RNCRNC MSCMSC
CC: Call Release
ALCAP
Release Request
ALCAP
Release Confirm
RANAP
Iu Release Command
ALCAP
Release Request
ALCAP
Release Confirm
NBAP
RL Deletion Request
NBAP
RL Deletion Response
RRC
Connection Release
RRC
RANAP
Iu Release Complete
[1]
[2]
MSC
RNC
NB
UE
UTRAN Status

DOWN (CS)
Procedure OverviewMessages (7): CS Call Tear Down CompleteMessages (7): CS Call Tear Down Complete
UEUE
Node
B
Node
B
RNCRNC MSCMSC
CC: Call Release
CC: Call ReleaseCS Call Tear Down
Complete
CS Call Tear Down
Complete
RRC, RL and Iu Release

PARTS 5 & 6
Packet Switched Data Sessions
Parts 5 & 6
Call Setup and Tear Down Scenarios

PART 5 - UE INITIATED CALL SET UP
(PS)
Procedure Overview.
At the start of this Procedure the UE is RRC Idle, PMM Detached
and SM Inactive. The call setup is Mobile Originated (mo).
The following steps need to be executed in order for a mo call to
complete;
1. Establish an RRC connection to the UTRAN
2. Establish an Iu connection to the CN
3. Make an Attach Request
4. Carry out Security Procedures
5. Complete the Attach
6. Request PDP context activation
7. Set-up RAB’s for the connection
8. Create GTP connections and activate PDP Context at the
GGSN
9. Data Transfer

(PS)Check Point One
UE Detached – No PDP Contexts
UEUE
Node
B
Node
B
RNCRNC SGSNSGSN GGSNGGSN
PDN
UE State: RRC Idle PMM Detached SM Inactive
Connections: Signalling :- None User :- None
UE State: RRC Idle PMM Detached SM Inactive
Connections: Signalling :- None User :- None

(PS)
Procedure OverviewRRC Connection Set-Up: RRC: RRC Connection RequestRRC Connection Set-Up: RRC: RRC Connection Request
Description:
This message is sent from by
the UE in order to establish
an RRC connection. Once
RRC connected the UE can
use the signalling
connection to carry out the
necessary mobility
procedures for Call set-up.
Main IE’s:
1. Initial UE ID
Establishment Cause
Description:
This message is sent from by
the UE in order to establish
an RRC connection. Once
RRC connected the UE can
use the signalling
connection to carry out the
necessary mobility
procedures for Call set-up.
Main IE’s:
1. Initial UE ID
Establishment Cause
UEUE Node BNode B RNCRNC SGSNSGSN
(RACH)
[1]

(PS)
Procedure OverviewRRC Connection Set-Up: NBAP: Radio Link Set-up Request / ResponseRRC Connection Set-Up: NBAP: Radio Link Set-up Request / Response
Description:
On reception of the RRC
Connection Request the RNC
initiates its set-up by
requesting the Node B to
configure a Radio Link. The
Node B sets-up the
Requested Link (DCCH) and
returns a set-up response
indicating the Link
configuration and the Binding
ID.
Main IE’s:
Frequency,
UL Scrambling Code
Power Control Info
Link termination
DCH Binding ID
Description:
On reception of the RRC
Connection Request the RNC
initiates its set-up by
requesting the Node B to
configure a Radio Link. The
Node B sets-up the
Requested Link (DCCH) and
returns a set-up response
indicating the Link
configuration and the Binding
ID.
Main IE’s:
Frequency,
UL Scrambling Code
Power Control Info
Link termination
DCH Binding ID
RL setup Request
RL setup Response
(RACH)
[1]
[2]

(PS)
Procedure OverviewRRC Connection Set-Up: ALCAP: Establish Request / ConfirmRRC Connection Set-Up: ALCAP: Establish Request / Confirm
Description:
Once the Radio Link has been
configured in the Node B, the
RNC sets-up an AAL2 bearer
to carry it. This is done using
the services of ALCAP. The
RNC sends a Establish
Request to the Node B,
providing details of the bearer
configuration and the Link
identifiers. It also includes
the Binding ID for the Radio
Link that the Node B
created.The Node B
responds with a Establish
confirm indicating the
Originating and terminating
references
Main IE’s:
1. Destination address,
DSAI, ALC, CEID, OSAI,
SUGR, SSISU
2. DSAID, OSAID
Description:
Once the Radio Link has been
configured in the Node B, the
RNC sets-up an AAL2 bearer
to carry it. This is done using
the services of ALCAP. The
RNC sends a Establish
Request to the Node B,
providing details of the bearer
configuration and the Link
identifiers. It also includes
the Binding ID for the Radio
Link that the Node B
created.The Node B
responds with a Establish
confirm indicating the
Originating and terminating
references
Main IE’s:
1. Destination address,
DSAI, ALC, CEID, OSAI,
SUGR, SSISU
2. DSAID, OSAID
RL setup Request
RL setup Response
ALCAP
ERQ
ALCAP ECF
(RACH)
[1]
[2]

(PS)
Procedure OverviewRRC Connection Set-Up: FP: DL / UL SynchronisationRRC Connection Set-Up: FP: DL / UL Synchronisation
Description:
Before use the new DCCH
needs to be synchronised.
This procedure allows the
RNC to calculate and adjust
for timing delays in the DL
direction. The Framing
Protocol DL Synchronisation
message is sent to the Node
B indicating the target frame
number.
The Node B measures the time
of arrival of the indicated
frame (wrt ToAWE) and
returns this value in an UL
synchronisation message.
Main IE’s:
1. CFN
2. CFN, ToA
Description:
Before use the new DCCH
needs to be synchronised.
This procedure allows the
RNC to calculate and adjust
for timing delays in the DL
direction. The Framing
Protocol DL Synchronisation
message is sent to the Node
B indicating the target frame
number.
The Node B measures the time
of arrival of the indicated
frame (wrt ToAWE) and
returns this value in an UL
synchronisation message.
Main IE’s:
1. CFN
2. CFN, ToA
RL setup Request
RL setup Response
ALCAP
ERQ
ALCAP ECF
(RACH)
FP DL
Synchronisation
[1]
[2]

(PS)
Procedure OverviewRRC Connection Set-Up: RRC: Connection Set-up / CompleteRRC Connection Set-Up: RRC: Connection Set-up / Complete
Description:
Once the UTRAN resources are
configured the RNC can
instruct the UE to set-up the
RRC connection and move
from RACH / FACH to
DCCH. This is done via a
RRC Connection Set-up
message sent on the FACH.
The UE responds with a set-up
complete on the new DCCH.
Main IE’s:
CapUpReq, TFS,
TFCS, frequ,
Power control info.
Integrity info
Description:
Once the UTRAN resources are
configured the RNC can
instruct the UE to set-up the
RRC connection and move
from RACH / FACH to
DCCH. This is done via a
RRC Connection Set-up
message sent on the FACH.
The UE responds with a set-up
complete on the new DCCH.
Main IE’s:
CapUpReq, TFS,
TFCS, frequ,
Power control info.
Integrity info
RL setup Request
RL setup Response
ALCAP
ERQ
ALCAP ECF
(RACH)
FP DL
Synchronisation
RRC Conn. Setup
(FACH)
RRC Conn. Setup Comp
(DCCH)
[1]
[2]

(PS)Check Point Two
UE Detached – No PDP Contexts – RRC Connected
UEUE
Node
B
Node
B
PDN
UE State: RRC Connected PMM Detached SM Inactive
Connections: Signalling :- RRC User :- None
UE State: RRC Connected PMM Detached SM Inactive
Connections: Signalling :- RRC User :- None
RRC Connection (DCCH)

(PS)
Procedure OverviewPMM Attach : RRC: Initial Direct Transfer + RANAP: Initial UE messagePMM Attach : RRC: Initial Direct Transfer + RANAP: Initial UE message
Description:
At this point the UE is RRC
connected in Cell_DCH
and can make its first
NAS request. In this
case it sends a PMM
Attach Request (with
follow on set), which is
transported via RRC and
RANAP Initial DT
messages.
Main IE’s:
1. Msg Type, CN Domain ID,
NAS message
2.. LAI, SAI, RAC, Sig. Conn.
ID, RNC ID, NAS -PDU
Description:
At this point the UE is RRC
connected in Cell_DCH
and can make its first
NAS request. In this
case it sends a PMM
Attach Request (with
follow on set), which is
transported via RRC and
RANAP Initial DT
messages.
Main IE’s:
1. Msg Type, CN Domain ID,
NAS message
2.. LAI, SAI, RAC, Sig. Conn.
ID, RNC ID, NAS -PDU
RRC Initial D T
(PMM Attach Request)
RANAP Initial UE
(SCCP Con Req.)
[1] [2]

(PS)
Procedure OverviewPMM Attach : PMM: Attach RequestPMM Attach : PMM: Attach Request
Description:
The NAS message carried by
RRC and RANAP DT
contains the UE Attach
Request. This message
identifies the UE to the CN
and provides details of its
Network and Radio
Capabilities.
Main IE’s:
1. UE Network Capability, UE
Radio Capability, P-TMSI and
RAI, Attach Type with follow
on bit set. P-TMSI Signature
Description:
The NAS message carried by
RRC and RANAP DT
contains the UE Attach
Request. This message
identifies the UE to the CN
and provides details of its
Network and Radio
Capabilities.
Main IE’s:
1. UE Network Capability, UE
Radio Capability, P-TMSI and
RAI, Attach Type with follow
on bit set. P-TMSI Signature
RRC Initial D T
RANAP Initial UE
(SCCP Con Req.)
[1] [2]

(PS)
Procedure OverviewPMM Attach : SCCP: Connection ConfirmPMM Attach : SCCP: Connection Confirm
Description:
Main IE’s:
Description:
Main IE’s:
RANAP Initial UE
(SCCP Con Req.)
RRC Initial DT
SCCP Connection Conf
[1]

(PS)
Procedure OverviewPMM Attach : RANAP / RRC: Authentication + Security ModePMM Attach : RANAP / RRC: Authentication + Security Mode
Description:
For First Call Authentication may
not be done. Manual
configuration of the VLR,
USIM may be done instead.
The Security mode procedure
is only partially supported, the
messages will be exchanged
between the different NE’s ,
but No Ciphering or Integrity
checking will be done.
Main IE’s:
1. RAND, AUTH
2. RES
Description:
For First Call Authentication may
not be done. Manual
configuration of the VLR,
USIM may be done instead.
The Security mode procedure
is only partially supported, the
messages will be exchanged
between the different NE’s ,
but No Ciphering or Integrity
checking will be done.
Main IE’s:
1. RAND, AUTH
2. RES
Authentication
RRC
RANAP
RRC
RRC Initial DT RANAP Initial UE
(SCCP Con Req.)
[1]
[4]
[2]
[3]

(PS)
Procedure OverviewIdentity Request Procedure: NAS: Identity RequestIdentity Request Procedure: NAS: Identity Request
Type: NAS (PMM)
Purpose:
Can be of type;
type;
Main IE’s:
Type: NAS (PMM)
Purpose:
Can be of type;
type;
Main IE’s:
Identity Request
Procedure
Identity Request
Procedure
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)

(PS)
Type: NAS (PMM)
Purpose:
UE Authentication
Main IE’s:
RAND
AUTN
RES
Type: NAS (PMM)
Purpose:
UE Authentication
Main IE’s:
RAND
AUTN
RES
Identity Request
Procedure
Identity Request
Procedure
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT

(PS)
Type:
RANAP DT
RRC DT
Purpose:
Main IE’s:
SM Command:
Domain ID
SM Complete:
Type:
RANAP DT
RRC DT
Purpose:
Main IE’s:
SM Command:
Domain ID
SM Complete:
Identity Request
Procedure
Identity Request
Procedure
RRC
RANAP
Security Mode
Command
RRC
RANAP
RRC DL DT
(Identity Request)
RANAP DT
(Identity Request)
RRC Initial D T
RANAP DT
(Identity Request)
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT

(PS)
Procedure OverviewPMM Attach : RANAP: Common IDPMM Attach : RANAP: Common ID
Description:
This RANAP message is sent to
the RNC from the CN in
order to establish a common
unique reference to the UE.
Main IE’s:
1. IMSI
Description:
This RANAP message is sent to
the RNC from the CN in
order to establish a common
unique reference to the UE.
Main IE’s:
1. IMSI
Authentication
RRC
RANAP
RRC
RANAP Common ID
(SCCP Con Req.)
[1]

(PS)
Procedure OverviewPMM Attach : PMM: Attach AcceptPMM Attach : PMM: Attach Accept
Description:
Once the Iu connection has been
established and the UE
successfully authenticated
then the CN sends an Attach
Accept to the UE. This
message may include the
allocation of a new P-TMSI.
Main IE’s:
1. Attach Result, RAI,
P-TMSI
Description:
Once the Iu connection has been
established and the UE
successfully authenticated
then the CN sends an Attach
Accept to the UE. This
message may include the
allocation of a new P-TMSI.
Main IE’s:
1. Attach Result, RAI,
P-TMSI
Authentication
RRC
RANAP
RRC
RANAP Common ID
RRC DL DT
(PMM Attach Accept)
RANAP DT
(PMM Attach Accept)
(SCCP Con Req.)
[1]
[2]

(PS)
Procedure OverviewPMM Attach : PMM: Attach CompletePMM Attach : PMM: Attach Complete
Description:
If the CN Allocated a new P-
TMSI in the Attach Accept
message then the UE
responds with an attach
complete message. This
confirms receipt of the new
temporary identity.
Main IE’s:
Attach Complete indication
Description:
If the CN Allocated a new P-
TMSI in the Attach Accept
message then the UE
responds with an attach
complete message. This
confirms receipt of the new
temporary identity.
Main IE’s:
Attach Complete indication
Authentication
RRC
RANAP
RRC
RANAP Common ID
RRC DL DT
(PMM Attach Accept)
RANAP DT
(PMM Attach Accept)
RRC UL DT
(PMM Attach Complete) RANAP DT
(PMM Attach Complete)
(SCCP Con Req.)
[2]
[1]

(PS)Check Point Three
UE Attached – No PDP Contexts – RRC Connected
UEUE
Node
B
Node
B
PDN
UE State: RRC Connected PMM Attached SM Inactive
Connections: Signalling :- DCCH RRC Iu User :- none
UE State: RRC Connected PMM Attached SM Inactive
Connections: Signalling :- DCCH RRC Iu User :- none
RRC Connection (DCCH) Iu Connection

(PS)
Procedure OverviewPDP Context Activation: SM: Activate PDP Context RequestPDP Context Activation: SM: Activate PDP Context Request
Description:
The UE starts this procedure
RRC and PMM Connected.
The follow on flag was set
during the attach procedure
so the RRC connection is still
in place. This is used to send
the NAS SM Activate PDP
context request message to
the CN. This message
indicates the Context
reference, the requested
QoS, PDP Address and APN.
Main IE’s:
Transaction ID,
NSAPI,
QoS,
PDP Address,
APN
Description:
The UE starts this procedure
RRC and PMM Connected.
The follow on flag was set
during the attach procedure
so the RRC connection is still
in place. This is used to send
the NAS SM Activate PDP
context request message to
the CN. This message
indicates the Context
reference, the requested
QoS, PDP Address and APN.
Main IE’s:
Transaction ID,
NSAPI,
QoS,
PDP Address,
APN
PMM Attach Procedure
RRC UL DT
(Activate PDP Context Req)
RANAP DT
(Activate PDP Context Req)[1] [2]

(PS)
Procedure OverviewPDP Context Activation: RANAP: RAB Assignment RequestPDP Context Activation: RANAP: RAB Assignment Request
Description:
On receipt of the request the
SGSN imitates the set-up of
the DTCH required to support
this Context. It does this by
sending a RAB assignment
request to the RNC indicating
the RAB configuration and
also passing the UL GTP
tunnel Paramaters.
Main IE’s:
RAB ID, RAB Paramaters, User
Plane Info, GTP-U IP
Address, UL TEID
Description:
On receipt of the request the
SGSN imitates the set-up of
the DTCH required to support
this Context. It does this by
sending a RAB assignment
request to the RNC indicating
the RAB configuration and
also passing the UL GTP
tunnel Paramaters.
Main IE’s:
RAB ID, RAB Paramaters, User
Plane Info, GTP-U IP
Address, UL TEID
RRC UL DT
RANAP DT
RANAP
RAB Assignment Req.
[1]

(PS)
Procedure OverviewPDP Context Activation: NBAP: RL Reconfigure Prepare / ReadyPDP Context Activation: NBAP: RL Reconfigure Prepare / Ready
Description:
The UE already has a Radio Link
set-up, this procedure
requires that a DTCH be
added to the configuration,
therefore the RNC sends a
RL reconfigure request to the
Node B.
The Node B confirms with RL
Reconfigure Ready, but does
not implement the changes
yet.
Main IE’s:
DCH’s to add,
Configuration Info
FP mode
ToAWS
ToAWE
DCH ID
TFS
RL ID
Description:
The UE already has a Radio Link
set-up, this procedure
requires that a DTCH be
added to the configuration,
therefore the RNC sends a
RL reconfigure request to the
Node B.
The Node B confirms with RL
Reconfigure Ready, but does
not implement the changes
yet.
Main IE’s:
DCH’s to add,
Configuration Info
FP mode
ToAWS
ToAWE
DCH ID
TFS
RL ID
RRC UL DT
RANAP DT
RANAP
RAB Assignment Req.
NBAP
NBAP
[1]
[2]

(PS)
Procedure OverviewPDP Context Activation: ALCAP: AAL2 Bearer Set-UpPDP Context Activation: ALCAP: AAL2 Bearer Set-Up
Description:
Once the RL has been
reconfigured in the Node B
the RNC sets-up the AAL2
bearer to carry it. As before
this done via ALCAP
Establish procedures and is
followed by FP
synchronisation.
Description:
Once the RL has been
reconfigured in the Node B
the RNC sets-up the AAL2
bearer to carry it. As before
this done via ALCAP
Establish procedures and is
followed by FP
synchronisation.
RANAP
RAB Assignment Req.
NBAP
NBAP
RRC UL DT
RANAP DT
ALCAP AAL2 Bearer Set-
up and Synchronisation

(PS)
Procedure OverviewPDP Context Activation: NBAP: RL Reconfigure CommitPDP Context Activation: NBAP: RL Reconfigure Commit
Description:
When the AAL2 connection is
ready the RNC instructs the
Node B to commit the
changes it had prepared in
the reconfiguration.
The Commit message indicates
the Frame number at which
the change should occur.
Main IE’s:
Transaction Id, CFN
Description:
When the AAL2 connection is
ready the RNC instructs the
Node B to commit the
changes it had prepared in
the reconfiguration.
The Commit message indicates
the Frame number at which
the change should occur.
Main IE’s:
Transaction Id, CFN
RANAP
RAB Assignment Req.
NBAP
NBAP
NBAP
RRC UL DT
RANAP DT
[1]

(PS)
Procedure OverviewPDP Context Activation: RRC: Radio Bearer Set-UpPDP Context Activation: RRC: Radio Bearer Set-Up
Description:
The UTRAN has been
configured for the new
DTCH, so the UE can now be
instructed to set-up the
Radio Bearer. The RNC
does this via an RRC RB set-
up request. This includes the
same CFN as indicated to
the Node B.
Main IE’s:
Transaction ID, CFN, State
Indicator,
RB Set-up info
RAB ID, CN Domain ID,
PDCP info, RLC Info, TFC,
TFS
Description:
The UTRAN has been
configured for the new
DTCH, so the UE can now be
instructed to set-up the
Radio Bearer. The RNC
does this via an RRC RB set-
up request. This includes the
same CFN as indicated to
the Node B.
Main IE’s:
Transaction ID, CFN, State
Indicator,
RB Set-up info
RAB ID, CN Domain ID,
PDCP info, RLC Info, TFC,
TFS
RANAP
RAB Assignment Req.
NBAP
NBAP
NBAP
(DCCH)
RRC UL DT
RANAP DT
[1]

(PS)
Procedure OverviewPDP Context Activation: RRC: Radio Bearer Set-Up CompletePDP Context Activation: RRC: Radio Bearer Set-Up Complete
Description:
Once the UE has configured the
RB it returns a confirmation
message in the form of an
RRC RB set-up Complete.
Main IE’s:
Transaction ID
Description:
Once the UE has configured the
RB it returns a confirmation
message in the form of an
RRC RB set-up Complete.
Main IE’s:
Transaction ID
RANAP
RAB Assignment Req.
NBAP
NBAP
NBAP
(DCCH)
RRC RB Setup Comp
(DCCH)
RRC UL DT
RANAP DT
[1]

(PS)
Procedure OverviewPDP Context Activation: RANAP: RAB Assignment ResponsePDP Context Activation: RANAP: RAB Assignment Response
Description:
Receipt of the set-up complete
message by the RNC
indicates that RAB
assignment procedure is
complete, it indicates this
back to the SGSN via a
RANAP RAB assignment
response, that also includes
the DL addressing for the
GTP-U connection.
Main IE’s:
NSAPI, RNC GTP-U IP
Address, DL TEID
Description:
Receipt of the set-up complete
message by the RNC
indicates that RAB
assignment procedure is
complete, it indicates this
back to the SGSN via a
RANAP RAB assignment
response, that also includes
the DL addressing for the
GTP-U connection.
Main IE’s:
NSAPI, RNC GTP-U IP
Address, DL TEID
RANAP
RAB Assignment Req.
NBAP
NBAP
NBAP
(DCCH)
RRC RB Setup Comp
(DCCH)
RRC UL DT
RANAP DT
RANAP
RAB Assignment Resp
[1]

(PS)
Procedure OverviewPDP Context Activation: GTP-C: Create PDP Context RequestPDP Context Activation: GTP-C: Create PDP Context Request
Description:
The final part of the connection
can now be established this
is the connection to the AP
indicated in the PDP
activation request. The
SGSN identifies the correct
GGSN and sends it a Create
PDP context Request.
Main IE’s:
IMSI, Restart Counter, Data
TEID, Control TEID, Data IP
Addr, Control IP Addr,
NSAPI, APN, QoS profile,
PDP Address
Description:
The final part of the connection
can now be established this
is the connection to the AP
indicated in the PDP
activation request. The
SGSN identifies the correct
GGSN and sends it a Create
PDP context Request.
Main IE’s:
IMSI, Restart Counter, Data
TEID, Control TEID, Data IP
Addr, Control IP Addr,
NSAPI, APN, QoS profile,
PDP Address
UEUE
Node
B
Node
B
GTP-C
Create PDP Context Request
[1]
Context Activation Request and RAB Set-Up

(PS)
Procedure OverviewPDP Context Activation: GTP-C: Create PDP Context ResponsePDP Context Activation: GTP-C: Create PDP Context Response
Description:
Once the Context has been
created in the GGSN it
returns a Create PDP
Context Response, indicating
the UL GTP Paramaters,
QoS profile and UE PDP
address
Main IE’s:
Restart Counter, Data TEID,
Control TEID, Data IP Addr,
Control IP Addr, QoS profile,
PDP Address
Description:
Once the Context has been
created in the GGSN it
returns a Create PDP
Context Response, indicating
the UL GTP Paramaters,
QoS profile and UE PDP
address
Main IE’s:
Restart Counter, Data TEID,
Control TEID, Data IP Addr,
Control IP Addr, QoS profile,
PDP Address
UEUE
Node
B
Node
B
GTP-C
GTP-C
Create PDP Context Response
[1]

(PS)
Procedure OverviewPDP Context Activation: SM: Activate PDP Context AcceptPDP Context Activation: SM: Activate PDP Context Accept
Description:
The Context s now active and all
the transport bearers are in
place, the SGSN can
therefore complete the
procedure by sending the UE
an Activate PDP context
Accept. This message is
also used to inform the UE of
the offered QoS settings and
PDP Address.
Main IE’s:
Transaction ID, QoS
Paramaters, Radio Priority,
PDP Address,
Description:
The Context s now active and all
the transport bearers are in
place, the SGSN can
therefore complete the
procedure by sending the UE
an Activate PDP context
Accept. This message is
also used to inform the UE of
the offered QoS settings and
PDP Address.
Main IE’s:
Transaction ID, QoS
Paramaters, Radio Priority,
PDP Address,
UEUE
Node
B
Node
B
GTP-C
GTP-C
Create PDP Context Response
[1]
[2]
RANAP DT
(Act PDP Context Acc)RRC DL DT
(Act PDP Context Acc)

(PS)
Procedure OverviewPDP Context Activation: Procedure CompletePDP Context Activation: Procedure Complete
At this point;
The PDP context has been
created in the SGSN, GGSN,
and at the UE
The UE is now SM Active, PMM
Attached and RRC
Connected. It has dedicated
signalling and user plane
connections, and an IP
address. Data transfer can
now begin
At this point;
The PDP context has been
created in the SGSN, GGSN,
and at the UE
The UE is now SM Active, PMM
Attached and RRC
Connected. It has dedicated
signalling and user plane
connections, and an IP
address. Data transfer can
now begin
UEUE
Node
B
Node
B
GGSN PDP Context Create and UE PDP Context Activation Accept
PS Call ActivePS Call Active

(PS)Check Point Four
UE Attached – One PDP Context
UE State: RRC Connected PMM Attached SM Active
Connections: Signalling :- DCCH RRC Iu GTP-C User :- DTCH GTP-
U
UE State: RRC Connected PMM Attached SM Active
Connections: Signalling :- DCCH RRC Iu GTP-C User :- DTCH GTP-
U
RRC Connection (DCCH) Iu Connection GTP-C Connection
UEUE
Node
B
Node
B
PDN
DTCH GTP-U Connection GT
P-U Connection

UMTS UTRAN Call Flow

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to UMTS UTRAN Call Flow

Similar to UMTS UTRAN Call Flow (20)

Recently uploaded

Recently uploaded (20)

UMTS UTRAN Call Flow

Editor's Notes