UMTS Call Flow Scenarios

UMTS Call Flow Scenarios
UMTS Call Flow Scenarios

An Overview of Circuit and
Packet Call Flow Scenarios
08/11/16
Summary of Presentation
UE
Node B
RNC
Part 1
Node B Initialisation and System Information

Broadcast Procedure
Part 2
UE Camp on and Location Update Procedure
Part 3
UE Initiated CS Call Setup Procedure
Part 4
UE Initiated CS Call Tear Down Procedure
Part 5
UE Initiated PS Call Setup Procedure
Part 6
UE Initiated PS Call Tear Down Procedure
08/11/16
CN
Obligatory Stuff UTRAN Interfaces

MSC
SGSN
Iu-cs
No Handover single RL
Iu-ps
S-RNC
Iu-b
Cell
Node B
Uu
UE
08/11/16
Obligatory Stuff UTRAN Interfaces

MSC
SGSN
Iu-cs
Intra-NodeB Softer Handover
Iu-ps
S-RNC
Iu-b
Cell
Node B
Uu
UE
08/11/16
Obligatory Stuff
MSC
SGSN
Iu-cs
UTRAN Interfaces
Intra-RNC Soft Handover
Iu-ps
S-RNC
Cell
Iu-b
Iu-b
Node B
Node B
Uu
UE
08/11/16
Obligatory Stuff
MSC
Inter-RNC Soft Handover
SGSN
Iu-cs
UTRAN Interfaces
Iu-ps
Iu-r
S-RNC
D-RNC
Iu-b
Node B
Iu-b
Cell
Node B
Uu
UE
08/11/16
Obligatory Stuff
Uu
codec
UE / CS CN Protocol Stack
Node
NodeBB
Iub
CM
SM
MM
MM
RRC
RRC
ALCAP
AA
STC.2 NBAP
PHY
SSCF-UNI
SSCOP
AAL2
AAL5
ATM
E1
08/11/16
codec
RRC
RRC
RLC
RLC
FP
Control
Control Plane
Plane
3GMSC
3GMSC
CM
MM
MM
SM
RLC
codec
RLC
MAC
MAC
Phy-up
Phy-up
PHY
PHY
Iucs
RNC
RNC
User
User Plane
Plane
MAC
MAC
ALCAP Phy-up
Phy-up
NBAP STC.2
NBAP ALCAP
FP
SSCF-UNI
SSCF
SSCF
FP
SSCOP
SSCOP SSCOP
AAL2
AAL5
AAL5 AAL5 AAL2
ATM
ATM
STM-1
E1
Transport
Transport Plane
Plane
RANAP
ALCAP
ALCAP
Iu UP
STC.1
SCCP
MTP3-b
SSCF-NNI
SSCOP
AAL2
AAL5
RANAP
Iu UP
SCCP STC.1
SCCP Q2150.1 Iu UP
MTP3B
MTP3B MTP
SSCF-NNI
SSCF
SSCF
SSCOP
SSCOP
AAL5
AAL2
AAL5 AAL5
AAL2
ATM
ATM
STM-1
E1
Common
Common
Obligatory Stuff
Uu
IP
PDCP
UE / PS CN Protocol Stack
Node B
Node B
Iub
SM
SM
PMM
MM
RRC
RRC
Control
Control Plane
Plane
08/11/16
Gn
SGSN
SGSN
SM
MM
PMM
SM
RRC
RRC
RLC
codec RLC
MAC
MAC
Phy-up
Phy-up
PHY
PHY
Iups
RNC
RNC
RLC
RLC
ALCAP
PHY
PHY
STC.2 NBAP
ALCAP NBAP
FP
SSCF-UNI
FP
SSCF SSCF
SSCOP
SSCOP SSCOP
AAL2
AAL5
AAL2
AAL5
AAL5
ATM
ATM
E1/ STM-1
E1
User
User Plane
Plane
ALCAP
MAC
MAC
Phy-up
Phy-up
NBAP STC.2
NBAP ALCAP
FP
SSCF-UNI
SSCF SSCF
FP
SSCOP
SSCOP SSCOP
AAL5
AAL5
ATM
ATM
STM-1
E1
AAL5
AAL2
AAL2
Transport
Transport Plane
Plane
PDCP
GTP-U
UDP
IP
AAL5
AAL2
AAL5
GTP-C
GTP-U
RANAP
FP
RANAP
SCCP
SCCP
SCCP
SCCP
MTP3-b
MTP3B
SSCF-N
SSCF
SSCOP
SSCOP
AAL5
AAL5
ATM
ATM
STM-1
E1
MTP3-b
SSCF-N
SSCF
SSCOP
AAL5
Q2150.1
UDP
Q2150.1
MTP3B
IP
GTP-C
IP
Q2150.
GTP-U
1
UDP
Iu UP
SSCF
Q2150.1
MTP3B
IP
Q2150.1
SSCF
SSCOP
AAL5
GGSN
GGSN
L2
L1
AAL2
SSCOP
L2
AAL5
L1
Common
Common
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
08/11/16
UTRAN Connections
Abstraction
If synchronisation status, dedicated traffic and

dedicated control channels only are shown on a
UTRAN Block Diagram..
UE
NB
RNC
MSC
UTRAN Status
Dedicated Control Channels
Dedicated Traffic Channels
Synchronisation Status
These are the parts of UTRAN that need to be

configured at call setup. A call cannot proceed
without all of these connections and synchronisation
08/11/16
10
UTRAN Connections
Key to Block
Diagram
Using RED to denote configured and

WHITE to denote not configured.
UE
NB
RNC
MSC
UTRAN Status
08/11/16
UE
NB
RNC
MSC
UTRAN Status
Example 1:
No dedicated traffic or control,
Air interface synchronised.
i.e. UE in Idle Mode
Example 2:
Dedicated control between RNC and UE,
No dedicated traffic,
Synchronisation between RNC and UE,
i.e. RRC Connection exists over dedicated
channels
11
Warning
- Please Read
This Presentation Contains Ladder Diagrams. . . .

Lots of them !!!!!
Brain
Body
Ladder Diagram Normal Procedure
View Presentation Request

View Presentation Ack
Ladder Diagram Indication
Enter sleep Mode Request
Sleep mode complete
08/11/16
You have been warned . . . .

12
Call Flow scenarios

For ease of understanding the Call Flow Scenarios will
be split into 6 parts.
1. Node B Initialisation - Appendix A
2. Cell Camp-on / Location Update - Appendix B
3. Circuit Switched Call set-up
4. Circuit Switched Call tear-down
5. Packet Switched Call set-up
6. Packet Switched Call tear-down
08/11/16
13
Part 1
Node B Initialisation and

Cell Camp on for First
Call
Refer to Appendix A
08/11/16
14
Part 2
UE Camp On & Location

Update
Refer to Appendix B
08/11/16
15
Parts 3 - 4
Circuit Switched Calls

Parts 3 & 4
Call Setup and Tear Down Scenarios
08/11/16
16
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)
8. Call Setup Request
9. Radio Link and RAB Configuration
10. Call Connection
08/11/16
17
Part 3

(CS)
Message (1): Connection Request
Procedure Overview
Type:
UE
Node B
RNC
MSC
RRC
RRC Connection Request
Channels:
[1]
(RACH)
CCCH / RACH
Main IEs:
1. Initial
Initial UE ID
ID
Establishment
Establishment Cause
Cause
Initial
Initial UE
UE capability
capability
08/11/16
UE
NB
RNC
MSC
UTRAN Status
18
Part 3

(CS)
Messages (2): Radio Link Set-up Request / Response
Procedure Overview
Type:
UE
Node B
RNC
MSC
NBAP
Main IEs:
(RACH)
1.
1. Cell
Cell ID,
ID, TFS
TFS // TFCS
TFCS
Frequency,
Frequency,
UL
UL Scrambling
Scrambling Code
Code
DL
DL Channelisation
Channelisation Code
Code
Power
Power Control
Control Info
Info
NBAP
RL setup Req.
NBAP
RL setup Resp.
[1]
[2]
2.
2. Transport
Transport Layer
Layer Address
Address Sig.
Sig.
Link
termination
Link termination
DL
DL Channelisation
Channelisation Code
Code
DCH
DCH Binding
Binding ID
ID
08/11/16
UE
NB
RNC
MSC
UTRAN Status
19
Part 3

(CS)
Messages (3): Establish Request (ERQ) / Confirm (ECF)
Procedure Overview
Type:
UE
Node B
RNC
MSC
ALCAP
Main IEs:
(RACH)
Destination address, DSAI,

ALC,
ALC, CEID,
CEID, OSAI,
OSAI, SUGR,
SUGR,
SSISU
SSISU
NBAP
RL setup Req.
NBAP
RL setup Resp.
ALCAP ERQ
ALCAP ECF
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
20
Part 3

(CS)
Messages (4): DCH-FP DL / UL Synchronisation
Procedure Overview
Type:
UE
Node B
RNC
MSC
DCH-FP
Main IEs:
(RACH)
NBAP
RL setup Req.
NBAP
RL setup Resp.
ALCAP ERQ
ALCAP ECF
FP DL Synchronisation
FP UL Synchronisation
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
21
Part 3

(CS)
Procedure Overview
Messages (5): Connection Set-up / Complete

Type:
UE
Node B
RNC
MSC
RRC
Channels:
(RACH)
1. FACH
NBAP
2. DCCH
NBAP
Main IEs:
ALCAP ERQ
RL setup Req.
RL setup Resp.
ALCAP ECF
1.
1. Initial
Initial UE
UE ID,
ID, RNTI,
RNTI,
CapUpReq,
CapUpReq, TFS,
TFS,
TFCS,
TFCS, frequ,
frequ,
DL
DL Scram
Scram ++ Chann
Chann codes,
codes,
Power
Power control
control info.
info.
2.
2. UE
UE Capability,
Capability, Ciphering,
Ciphering,
Integrity
Integrity info
info
08/11/16
UE
NB
RNC
MSC
UTRAN Status
RRC Conn. Setup

RRC Conn. Setup Comp
(DCCH)
(FACH)
[1]
[2]
22

(CS)
Part 3
Messages (6): Initial Direct Transfer + Initial UE message
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RRC
2. RANAP
RRC Connection Setup
Channel:
RRC Initial D T
(CM Service Request.)
DCCH
RANAP Initial UE
[1]
(CM Service Req.)

(SCCP Con Req.)
[2]
Main IEs:
08/11/16
UE
NB
RNC
MSC
UTRAN Status
23
Part 3

(CS)
Messages (7): Connection Confirm + CM Service Accept
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. SCCP / RANAP DT
2. RRC DL DT
3. RANAP DT
RRC Initial DT
4. RRC DL DT
(CM Service Request)
Channel:
RANAP Initial UE
(CM Service Req.)
(SCCP Con Req.)
SCCP Conn Conf
DCCH
RANAP DT
[3]
Main IEs:
RRC DL DT (OPT)
(CM Service Acc)
(CM Service Acc)
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
24

(CS)
Part 3
Procedure Overview
Messages (8): Authentication + Security Mode Commands

Type:
UE
Node B
RNC
MSC
1. RANAP
2. RRC
3. RRC
RRC Initial DT
RANAP Initial UE
(CM Service Req.)
4. RANAP
(SCCP Con Req.)
Channel:
SCCP Conn Conf
DCCH
RANAP DT
Main IEs:
Authentication
RRC
Security Mode Command
UE
NB
RNC
MSC
UTRAN Status
08/11/16
(CM Service Acc)
RRC DL DT (OPT)
(CM Service Acc)
[3]
[2]
RRC
Security Mode Complete
RANAP
RANAP
[1]
[4]
25
Part 3

(CS)
Procedure Overview
Identity, 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 .
08/11/16
UE
Node B
RNC
MSC
Identity
Identity Request
Request Procedure
Procedure
Authentication
Authentication
Security
Security Mode
Mode
26
Part 3

(CS)
Identity Request Procedure: NAS: Identity Request
Procedure Overview
Type: NAS (PMM)

Purpose:
Identity
Identity Request:
Request: Used
Used by
by the
the
CN
to
request
the
UE
identity.
CN to request the UE identity.
Can
Can be
be of
of type;
type;
[IMSI,
[IMSI, IMEI,
IMEI, IEMISV,
IEMISV, TMSI]
Identity
Identity Response:
Response: UE
UE reply
reply to
to
the
the Identity
Identity request
request can
can be
be of
of
type;
type;
UE
Node B
RNC
MSC
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC UL D T
(Identity Response.)
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
[IMSI,
[IMSI, IMEI,
IMEI, IEMISV,
IEMISV, TMSI]
Main
Main IEs:
IEs:
Req:
Req: Identity
Identity Request
Request Type
Type
Res:
Res: Mobile
Mobile Identity
Identity
Security
Security Mode
Mode
08/11/16
27
Part 3

(CS)
Procedure Overview

Type: NAS (PMM)
Purpose:
UE
UE Authentication
Authentication
Network
Network Authentication
Authentication
Integrity
Integrity Key exchange
Ciphering
Ciphering Key Exchange
Main IEs:
Req:
Req: CK
CK Sequence
Sequence Number
Number
RAND
RAND
AUTN
AUTN
Res:
Res:
CK
CK Sequence
Sequence Number
Number
RES
RES
UE
Node B
RNC
MSC
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
RRC DL DT
(Authentication Request)
RANAP DT
RRC UL D T
(Authentication Response)
RANAP DT
Security
Security Mode
Mode
08/11/16
28
Part 3

(CS)
Procedure Overview

Type:
RANAP DT
RRC DT
Purpose:
Selection
Selection of
of Integrity
Integrity and
and
Ciphering
Ciphering Algorithms (by RNC)
Control
Control Of
Of Integrity
Integrity and
and
Ciphering
Ciphering Operation.
Main IEs:
SM
SM Command:
Command:
1.
1. Algorithm
Algorithm List,
List, IK
IK
2.
Integrity
Check
Info
2. Integrity
Integrity
prot.
mode
info
Integrity
Domain
ID
Domain ID
SM
SM Complete:
Complete:
1.UL
1.UL Integrity
Integrity protection
protection info
info
2.
Chosen
Integrity
2. Chosen Integrity Algorithm
Algorithm
UE
Node B
MSC
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC Initial D T
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT
Security
Security Mode
Mode
RRC
RANAP
RRC
08/11/16
RNC
RANAP
29

(CS)
Part 3
Procedure Overview
Messages (9): Common ID

Type:
UE
Node B
RNC
MSC
1. RANAP
Main IEs:

RRC Initial DT
1. Permanent
Permanent NAS
NAS ID
ID
RANAP Initial UE
(CM Service Req.)
(SCCP Con Req.)
SCCP Conn Conf

RANAP DT
(CM Service Acc)
RRC DL DT (OPT)
(CM Service Acc)
Authentication
RANAP
RRC
UE
NB
RNC
MSC
UTRAN Status

RRC
RANAP
RANAP
Common ID
08/11/16
[1]
30
Part 3

(CS)
Messages (10): Call Setup + Call Proceeding
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RRC UL DT
2. RANAP DT
3. RANAP DT
Service Request / Authentication / Security
4. RRC DL DT
RRC UL DT
(Call Setup)
Main IEs:
1.
1. Calling/Called
Calling/Called Party
Numbers,
Numbers,
Calling/Called
Calling/Called party
party subsubaddress,
address,
bearer
bearer capability
capability
RRC DL DT
(Call Proceeding)
[1]
RANAP DT
(Call Setup)
RANAP DT
[4]
(Call Proceeding)
[2]
[3]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
31

(CS)
Part 3
Messages (11): RAB Assignment Request + Iucs ALCAP Setup
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RANAP
2. ALCAP
3. ALCAP
Main IEs:
1.
1. RAB
RAB Param,
Param, NAS
NAS Bind
Bind Info,
Info,
User
Plane
Mode,
User Plane Mode, Transport
Transport
Add,
Add, IU
IU Transport
Transport Association
Association
2.
2. CEID,
CEID, Destination
Destination address,
address,
DSAID,
DSAID, OSAID
OSAID
3.
3. CEID,
CEID, Destination
address,
DSAID,
DSAID, OSAID
OSAID
RRC UL DT
(Call Setup)
RRC DL DT
(Call Proceeding)
RANAP DT
(Call Setup)
RANAP DT
(Call Proceeding)
RANAP
RAB Assignment Req.
ALCAP
ERQ
ALCAP
08/11/16
[2]
[3]
UE
NB
RNC
MSC
UTRAN Status
ECF
[1]
32
Part 3

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

(CS)
Part 3
Messages (13): RAB - Iub Establish Request / Confirm
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. ALCAP
2. ALCAP
Continued from NBAP RL

Reconfigure Procedure
Main IEs:
1.
1. CEID,
CEID, Destination
address,
DSAID,
DSAID, OSAID
OSAID
ALCAP
2.
2. CEID,
CEID, Destination
address,
DSAID,
DSAID, OSAID
OSAID
ALCAP
ERQ
ECF
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
34

(CS)
Part 3
Messages (14): RAB - Iucs Establish Request / Confirm
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. ALCAP
2. ALCAP

Main IEs:
1.
1. CEID,
CEID, Destination
address,
DSAID,
DSAID, OSAID
OSAID
ALCAP
2.
2. CEID,
CEID, Destination
address,
DSAID,
DSAID, OSAID
OSAID
ALCAP
ERQ
ECF
NBAP
RL Reconfigure Commit
[1]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
35
Part 3

(CS)
Messages (15): RAB - Radio Bearer Setup / Complete
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RRC
2. RRC

Channel
DCCH
ALCAP
Main IEs:
ALCAP
ERQ
ECF
NBAP
RRC Radio Bearer Setup
(DCCH)
RRC RB Setup Comp
(DCCH)
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
36
Part 3

(CS)
Messages (16): RAB Assignment Response
Procedure Overview
Type:
UE
1.
RANAP
2.
IUUP
Node B
RNC
MSC

Main IEs:
ALCAP
ERQ
ALCAP
ECF
NBAP
(DCCH)
RRC RB Setup Comp
(DCCH)
RANAP
RAB Assignment Resp
IUUP
Initialisation
08/11/16
[1]
UE
NB
RNC
MSC
UTRAN Status
[2]
37
Part 3

(CS)
Messages (17): Call Connect
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RANAP DT
2. RRC DT
Channel
DCCH
Call Setup Request and RAB Assignment
Main IEs:
RRC DL DT
(Alerting)
RANAP DT
[2]
(Alerting)
[1]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
38
Part 3

(CS)
Messages (18): Connect / Connect Acknowledge
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RANAP DT
2. RRC DL DT
3. RRC UL DT
4. RANAP DT
Call Setup Request and RAB Assignment
Channel
RANAP DT
RRC DL DT
(Alerting)
DCCH / DCH
Main IEs:
(Alerting)
RANAP DT
RRC DL DT
(CC: Connect)
[2]
RRC UL DT
(CC: Connect Ack)
[3]
(CC: Connect)
RANAP DT
(CC: Connect Ack)
[1]
[4]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
Call Connected
39
Part 4
- UE initiated Call TearDown (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
08/11/16
40
Part 4
Messages (1): CC: Disconnect
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RRC UL DT
Call
Call Connected
Connected
2. RANAP DT
RRC UL DT
(CC: Disconnect)
Channels:
[1]
RANAP DT
(CC: Disconnect)
[2]
DCCH
Main IEs:
08/11/16
UE
NB
RNC
MSC
UTRAN Status
41
Part 4
Messages (2): CC: Release + Release Complete
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RANAP DT
Call
Call Connected
Connected
2. RRC DL DT
RRC UL DT
(CC: Disconnect)
3. RRC UL DT
RANAP DT
(CC: Disconnect)
4. RANAP DT
RRC DL DT
(CC: Release)
Channels:
RRC UL DT
(CC: Release Complete)
DCCH / DCH
RANAP DT
[2]
[3]
(CC: Release)
RANAP DT
(CC: Release Complete )
[1]
[4]
Main IEs:
08/11/16
UE
NB
RNC
MSC
UTRAN Status
42
Part 4
Message (3): Iu Release Command
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RANAP
Call
Call Connected
Connected
2. RANAP
CC: Call Release
Main IEs:
RANAP
1. Cause=Normal
Cause=Normal Release
Release
Iu Release Command
RANAP
Iu Release Complete
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
43
Part 4
Messages (4): RAB - Release Request / Confirm (Iucs)
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. ALCAP
Call
Call Connected
Connected
2. ALCAP
CC: Call Release
Main IEs:
RANAP
1. DSAID,
DSAID, Cause=
Cause= 31,
31, normal
normal
unspecified
unspecified
Iu Release Command
RANAP
Iu Release Complete
ALCAP
Release Request
ALCAP
Release Confirm
[1]
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
44
Part 4
Messages (5): RRC - Connection Release / Complete
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. RRC
Call
Call Connected
Connected
2. RRC
CC: Call Release
Main IEs:
RANAP
Iu Release Command
RANAP
Iu Release Complete
ALCAP
Release Request
RRC
Connection Release
RRC
Con. Release Complete
ALCAP
[1]
Release Confirm
[2]
08/11/16
UE
NB
RNC
MSC
UTRAN Status
45
Part 4
Messages (6): RL Deletion Request / Response
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. NBAP
Call
Call Connected
Connected
2. NBAP
CC: Call Release
Main IEs:
RANAP
Iu Release Command
RANAP
Iu Release Complete
ALCAP
Release Request
ALCAP
RRC
Connection Release
RRC
Release Confirm
NBAP
RL Deletion Request
08/11/16
UE
NB
RNC
MSC
UTRAN Status
NBAP
RL Deletion Response
[1]
[2]
46
Part 4
Messages (7): RAB - Release Request / Confirm (Iub)
Procedure Overview
Type:
UE
Node B
RNC
MSC
1. ALCAP
Call
Call Connected
Connected
2. ALCAP
CC: Call Release
Main IEs:
RANAP
Iu Release Command
1. DSAID,
DSAID, Cause=
Cause= 31,
31, normal
normal
unspecified
unspecified
RANAP
Iu Release Complete
ALCAP
Release Request
ALCAP
RRC
Connection Release
RRC
Release Confirm
NBAP
RL Deletion Request
UE
NB
RNC
MSC
UTRAN Status
NBAP
ALCAP
Release Request
ALCAP
Release Confirm
08/11/16
[1]
[2]
47
Part 4
Messages (7): CS Call Tear Down Complete
Procedure Overview
UE
Node B
RNC
MSC
Call
Call Connected
Connected
CC: Call Release

RRC, RL and Iu Release
CC: Call Release
08/11/16
CS
CS Call
Call Tear
Tear Down
Down
Complete
Complete
48
Parts 5 & 6
Packet Switched Data Sessions

Parts 5 & 6
Call Setup and Tear Down Scenarios
08/11/16
49
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 RABs for the connection
8. Create GTP connections and activate PDP Context at the
GGSN
9. Data Transfer
08/11/16
50

(PS)
Check Point One
Part 5
UE Detached No PDP Contexts
PDN
UE
Node B
UE State:
RRC Idle
Connections:
Signalling :- None
08/11/16
RNC
PMM Detached
SGSN
GGSN
SM Inactive
User :- None
51
Part 5

(PS)
RRC Connection Set-Up:
RRC: RRC Connection Request

Procedure Overview
Description:
This
This message
message is
is sent
sent from
from by
by
the
the UE in
in order
order to
to establish
establish
an
an RRC connection.
connection. Once
Once
RRC
RRC connected
connected the
the UE
UE can
can
use
use the
the signalling
connection
connection to
to carry
carry out
out the
the
necessary
necessary mobility
mobility
procedures
procedures for
for Call
Call set-up.
set-up.
UE
[1]
Node B
RNC
SGSN

(RACH)
Main IEs:
1. Initial
Initial UE ID
ID
Establishment
Establishment Cause
Cause
Initial
Initial UE
UE capability
capability
08/11/16
52
Part 5

(PS)
RRC Connection Set-Up: NBAP: Radio Link Set-up Request / Response
Procedure Overview
Description:
On
On reception
reception of
of the
the RRC
RRC
Connection
Connection Request
Request the
the RNC
RNC
initiates
initiates its
its set-up
set-up by
by
requesting
requesting the
the Node
Node B
B to
to
configure
configure aa Radio
Radio Link.
Link. The
Node
Node B
B sets-up
sets-up the
the
Requested
Requested Link
Link (DCCH)
(DCCH) and
and
returns
returns aa set-up
set-up response
response
indicating
indicating the Link
configuration
configuration and
and the
the Binding
Binding
ID.
ID.
UE
Node B
RNC
SGSN

(RACH)
RL setup Request
RL setup Response
[1]
[2]
Main IEs:
1.
1. Cell
Cell ID,
ID, TFS
TFS // TFCS
TFCS
Frequency,
Frequency,
UL
UL Scrambling
Scrambling Code
Code
DL
DL Channelisation
Channelisation Code
Code
Power
Power Control
Control Info
Info
2.
2. Transport
Transport Layer
Layer Address
Address Sig.
Sig.
Link
termination
Link termination
DL
DL Channelisation
Channelisation Code
Code
DCH
DCH Binding
Binding ID
ID
08/11/16
53
Part 5

(PS)
RRC Connection Set-Up: ALCAP:
Establish Request / Confirm

Procedure Overview
Description:
Once
Once the
the Radio
Radio Link
Link has
has been
been
configured
configured in
in the
the Node
Node B,
B, the
the
RNC
RNC sets-up
sets-up an
an AAL2
AAL2 bearer
bearer
to
to carry
carry it.
it. This is
is done
done using
using
the
the services
services of
of ALCAP.
ALCAP. The
The
RNC
RNC sends
sends aa Establish
Establish
Request
Request to
to the
the Node
Node B,
B,
providing
providing details
details of
of the
the bearer
bearer
configuration
configuration and
and the
the Link
Link
identifiers.
identifiers. ItIt also
also includes
the
the Binding
Binding ID
ID for
for the
the Radio
Radio
Link
Link that
that the
the Node
Node B
B
created.The
created.The Node
Node B
B
responds
responds with
with aa Establish
Establish
confirm
confirm indicating
indicating the
the
Originating
Originating and
and terminating
terminating
references
references
UE
Node B
RNC
SGSN

(RACH)
RL setup Request
RL setup Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
Main IEs:
1. Destination
address,
DSAI,
DSAI, ALC,
ALC, CEID,
CEID, OSAI,
OSAI,
SUGR,
SUGR, SSISU
SSISU
2.
2. DSAID,
DSAID, OSAID
OSAID
08/11/16
54
Part 5

(PS)
RRC Connection Set-Up: FP:
DL / UL Synchronisation
Procedure Overview
Description:
Before
Before use
use the
the new
new DCCH
DCCH
needs
needs to
to be
be synchronised.
synchronised.
This
This procedure
procedure allows
allows the
the
RNC
RNC to
to calculate
calculate and
and adjust
adjust
for
for timing
timing delays
delays in
in the
the DL
DL
direction.
direction. The
The Framing
Framing
Protocol
Protocol DL
DL Synchronisation
Synchronisation
message
message is
is sent
sent to
to the
the Node
Node
B
B indicating
indicating the
the target
target frame
frame
number.
number.
The
The Node B measures the time
of
of arrival
arrival of
of the
the indicated
indicated
frame
frame (wrt
(wrt ToAWE)
ToAWE) and
and
returns
returns this
this value
value in
in an
an UL
UL
synchronisation
synchronisation message.
message.
UE
Node B
RNC
SGSN

(RACH)
RL setup Request
RL setup Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
Main IEs:
1.
1. CFN
CFN
2.
2. CFN,
CFN, ToA
ToA
08/11/16
55
Part 5

(PS)
Procedure Overview
RRC Connection Set-Up: RRC: Connection Set-up / Complete

Description:
Once
Once the
the UTRAN
UTRAN resources are
configured
configured the
the RNC
RNC can
can
instruct
instruct the
the UE
UE to
to set-up
set-up the
the
RRC
RRC connection
connection and
and move
move
from
from RACH
RACH // FACH
FACH to
to
DCCH.
DCCH. This
This is
is done
done via
via aa
RRC
RRC Connection
Connection Set-up
Set-up
message
message sent
sent on
on the
the FACH.
FACH.
UE
Node B
RNC

(RACH)
RL setup Request
RL setup Response
ALCAP ERQ
The
The UE responds with a set-up
complete
complete on
on the
the new
new DCCH.
DCCH.
ALCAP ECF
Main IEs:
1.
1. Initial
Initial UE
UE ID,
ID, RNTI,
RNTI,
CapUpReq,
CapUpReq, TFS,
TFS,
TFCS,
TFCS, frequ,
frequ,
DL
DL Scram
Scram ++ Chann
Chann codes,
codes,
Power
Power control
control info.
info.
2.
2. UE
UE Capability,
Capability, Ciphering,
Ciphering,
Integrity
Integrity info
info
08/11/16
SGSN
RRC Conn. Setup

RRC Conn. Setup Comp
(DCCH)
(FACH)
[1]
[2]
56

(PS)
Check Point Two
Part 5
UE Detached No PDP Contexts RRC Connected
PDN
UE
Node B
RNC
SGSN
GGSN
RRC Connection (DCCH)
UE State:
RRC Connected
Connections:
Signalling :- RRC
08/11/16
PMM Detached
SM Inactive
User :- None
57
Part 5

(PS)
PMM Attach :
RRC: Initial Direct Transfer + RANAP: Initial UE message

Procedure
Overview
Description:
At
At this
this point
point the
the UE
UE is
is RRC
RRC
connected
connected in
in Cell_DCH
Cell_DCH
and
and can
can make
make its
its first
first
NAS
NAS request.
request. In
In this
this
case
case itit sends
sends aa PMM
PMM
Attach
Attach Request (with
follow
follow on
on set),
set), which
which is
is
transported
transported via
via RRC and
RANAP
RANAP Initial
Initial DT
DT
messages.
messages.
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial D T
(PMM Attach Request)
[1]

(SCCP Con Req.)
[2]
Main IEs:
1.
1. Msg
Msg Type,
Type, CN
CN Domain
Domain ID,
ID,
NAS
NAS message
message
2..
2.. LAI,
LAI, SAI, RAC, Sig. Conn.
ID,
ID, RNC
RNC ID,
ID, NAS
NAS -PDU
-PDU
08/11/16
58
Part 5

(PS)
PMM Attach :
PMM: Attach Request

Procedure
Overview
Description:
The
The NAS message carried by
RRC
RRC and
and RANAP
RANAP DT
DT
contains
contains the
the UE
UE Attach
Attach
Request.
Request. This message
message
identifies
identifies the
the UE
UE to
to the
the CN
CN
and
and provides
provides details
details of
of its
its
Network
Network and
and Radio
Radio
Capabilities.
Capabilities.
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial D T
[1]

(SCCP Con Req.)
[2]
Main IEs:
1.
1. UE
UE Network
Network Capability, UE
Radio
Radio Capability,
Capability, P-TMSI
P-TMSI and
and
RAI,
RAI, Attach
Attach Type with follow
on
on bit
bit set.
set. P-TMSI
P-TMSI Signature
Signature
08/11/16
59
Part 5

(PS)
PMM Attach : SCCP: Connection Confirm
Procedure Overview
Description:
Main IEs:
UE
Node B
RNC
SGSN

RRC Initial DT
RANAP Initial UE
(SCCP Con Req.)
SCCP Connection Conf
08/11/16
[1]
60
Part 5

(PS)
PMM Attach : RANAP / RRC: Authentication + Security Mode
Procedure Overview
Description:
For
For First
First Call
Call Authentication
Authentication may
may
not
not be
be done.
done. Manual
Manual
configuration
configuration of
of the
the VLR,
VLR,
USIM
USIM may
may be
be done
done instead.
instead.
The
The Security
Security mode
mode procedure
procedure
is
is only
only partially
partially supported,
supported, the
the
messages
messages will
will be
be exchanged
exchanged
between
between the
the different
different NEs
NEs ,,
but
but No
No Ciphering
Ciphering or Integrity
checking
checking will
will be
be done.
done.
Main IEs:
1.
1. RAND,
RAND, AUTH
AUTH
2.
2. RES
RES
08/11/16
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial DT
(SCCP Con Req.)

Authentication
[2]
[3]
RANAP
RRC

RRC
RANAP
[1]
[4]
61
Part 5

(PS)
Identity Request Procedure: NAS: Identity Request
Procedure Overview
Type: NAS (PMM)

Purpose:
Identity
Identity Request:
Request: Used
Used by
by the
the
CN
to
request
the
UE
identity.
CN to request the UE identity.
Can
Can be
be of
of type;
type;
[IMSI,
[IMSI, IMEI,
IMEI, IEMISV,
IEMISV, TMSI]
Identity
Identity Response:
Response: UE
UE reply
reply to
to
the
the Identity
Identity request
request can
can be
be of
of
type;
type;
UE
Node B
RNC
SGSN
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
[IMSI,
[IMSI, IMEI,
IMEI, IEMISV,
IEMISV, TMSI]
Main
Main IEs:
IEs:
Req:
Req: Identity
Identity Request
Request Type
Type
Res:
Res: Mobile
Mobile Identity
Identity
Security
Security Mode
Mode
08/11/16
62
Part 5

(PS)
Procedure Overview

Type: NAS (PMM)
Purpose:
UE
UE Authentication
Authentication
Network
Network Authentication
Authentication
Integrity
Integrity Key exchange
Ciphering
Ciphering Key Exchange
Main IEs:
Req:
Req: CK
CK Sequence
Sequence Number
Number
RAND
RAND
AUTN
AUTN
Res:
Res:
CK
CK Sequence
Sequence Number
Number
RES
RES
UE
Node B
RNC
SGSN
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC UL D T
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT
Security
Security Mode
Mode
08/11/16
63
Part 5

(PS)
Procedure Overview

Type:
RANAP DT
RRC DT
Purpose:
Selection
Selection of
of Integrity
Integrity and
and
Ciphering
Ciphering Algorithms (by RNC)
Control
Control Of
Of Integrity
Integrity and
and
Ciphering
Ciphering Operation.
Main IEs:
SM
SM Command:
Command:
1.
1. Algorithm
Algorithm List,
List, IK
IK
2.
Integrity
Check
Info
2. Integrity
Integrity
Integrity prot. mode info
Domain
Domain ID
ID
SM
SM Complete:
Complete:
1.UL
1.UL Integrity
Integrity protection
protection info
info
2.
Chosen
Integrity
2. Chosen Integrity Algorithm
Algorithm
UE
Node B
SGSN
Identity
Identity Request
Request Procedure
Procedure
RRC DL DT
(Identity Request)
RRC Initial D T
RANAP DT
(Identity Request)
RANAP DT
(Identity Request)
Authentication
Authentication
RRC DL DT
RANAP DT
RRC UL D T
RANAP DT
Security
Security Mode
Mode
RRC
RANAP
RRC
08/11/16
RNC
RANAP
64
Part 5

(PS)
Procedure Overview
PMM Attach : RANAP: Common ID

Description:
This
This RANAP message is sent to
the
the RNC
RNC from
from the
the CN
CN in
in
order
order to
to establish
establish aa common
common
unique
unique reference
reference to
to the
the UE.
UE.
Main IEs:
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial DT
(SCCP Con Req.)
1.
1. IMSI
IMSI

Authentication
RANAP
RRC

RRC
RANAP
RANAP Common ID
08/11/16
[1]
65
Part 5

(PS)
PMM Attach : PMM: Attach Accept
Procedure Overview
Description:
Once
Once the
the Iu
Iu connection
connection has
has been
been
established
established and
and the
the UE
UE
successfully
successfully authenticated
authenticated
then
then the
the CN
CN sends
sends an
an Attach
Attach
Accept
Accept to
to the
the UE.
UE. This
This
message
message may
may include
include the
the
allocation
allocation of a new P-TMSI.
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial DT
(SCCP Con Req.)
Main IEs:
Authentication
1.
1. Attach
Attach Result,
Result, RAI,
RAI,
P-TMSI
P-TMSI
RANAP
RRC

RRC
RANAP
RANAP Common ID
[2]
08/11/16
RRC DL DT
(PMM Attach Accept)
RANAP DT
(PMM Attach Accept)
[1]
66
Part 5

(PS)
Procedure Overview
PMM Attach : PMM: Attach Complete

Description:
IfIf the
the CN
CN Allocated
Allocated aa new
new PPTMSI
TMSI in
in the
the Attach
Attach Accept
Accept
message
message then
then the
the UE
UE
responds
responds with
with an
an attach
attach
complete
complete message.
message. This
This
confirms
confirms receipt
receipt of
of the
the new
new
temporary
temporary identity.
identity.
UE
Node B
RNC
SGSN

RANAP Initial UE
RRC Initial DT
(SCCP Con Req.)
Main IEs:
Authentication
Attach
Attach Complete
Complete indication
indication
RANAP
RRC

RRC
RANAP
RANAP Common ID
RANAP DT
RRC DL DT
(PMM Attach Accept)
[1]
(PMM Attach Accept)

RRC UL DT
(PMM Attach Complete)
RANAP DT
(PMM Attach Complete)
08/11/16
[2]
67

(PS)
Check Point Three
Part 5
UE Attached No PDP Contexts RRC Connected
PDN
UE
Node B
UE State:
RRC Connected
RNC
SGSN
Iu Connection
PMM Attached
Connections: Signalling :- DCCH RRC Iu

08/11/16
GGSN
SM Inactive
User :- none
68
Part 5

(PS)
SM: Activate PDP Context Request

Procedure Overview
PDP Context Activation:

Description:
The
The UE starts this procedure
RRC
RRC and
and PMM
PMM Connected.
The
The follow
follow on
on flag
flag was
was set
set
during
during the
the attach
attach procedure
procedure
so
so the
the RRC
RRC connection
connection is
is still
still
in
in place.
place. This
This is
is used
used to
to send
send
the
the NAS
NAS SM
SM Activate
Activate PDP
context
context request
request message
message to
to
the
the CN.
CN. This
This message
message
indicates
indicates the
the Context
Context
reference,
reference, the
the requested
requested
QoS,
QoS, PDP
PDP Address
Address and
and APN.
APN.
UE
Node B
RNC
SGSN

PMM Attach Procedure
RRC UL DT
(Activate PDP Context Req)
[1]
RANAP DT
[2]
Main IEs:
Transaction
Transaction ID,
ID,
NSAPI,
NSAPI,
QoS,
QoS,
PDP
PDP Address,
Address,
APN
APN
08/11/16
69
Part 5

(PS)
Procedure Overview
PDP Context Activation: RANAP: RAB Assignment Request

Description:
On
On receipt
receipt of
of the
the request
request the
the
SGSN
SGSN imitates
imitates the
the set-up
set-up of
of
the
the DTCH
DTCH required
required to
to support
support
this
this Context.
Context. ItIt does
does this
this by
by
sending
sending aa RAB
RAB assignment
assignment
request
request to
to the
the RNC
RNC indicating
indicating
the
the RAB
RAB configuration
configuration and
and
also
also passing
passing the
the UL
UL GTP
GTP
tunnel
tunnel Paramaters.
Paramaters.
UE
Node B
RNC
SGSN

RRC UL DT
RANAP DT
RANAP
RAB Assignment Req.
[1]
Main IEs:
RAB
RAB ID,
ID, RAB
RAB Paramaters,
Paramaters, User
User
Plane
Plane Info,
Info, GTP-U
GTP-U IP
IP
Address,
Address, UL
UL TEID
TEID
08/11/16
70
Part 5

(PS)
RL Reconfigure Prepare / Ready

Procedure Overview
PDP Context Activation: NBAP:

Description:
The
The UE already has a Radio Link
set-up,
set-up, this
this procedure
procedure
requires
requires that
that aa DTCH
DTCH be
be
added
added to
to the
the configuration,
configuration,
therefore
therefore the
the RNC
RNC sends
sends aa
RL
RL reconfigure
reconfigure request
request to
to the
the
Node
Node B.
B.
The
The Node B confirms with RL
Reconfigure
Reconfigure Ready,
Ready, but
but does
does
not
not implement
implement the changes
yet.
yet.
UE
Node B
RNC
SGSN

RRC UL DT
[1]
[2]
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP
Main IEs:
DCHs
DCHs to
to add,
add,
Configuration
Configuration Info
Info
FP
FP mode
mode
ToAWS
ToAWS
ToAWE
ToAWE
DCH
DCH ID
ID
TFS
TFS
RL
RL ID
ID
08/11/16
71
Part 5

(PS)
PDP Context Activation: ALCAP: AAL2 Bearer Set-Up
Procedure Overview
Description:
Once
Once the
the RL
RL has
has been
been
reconfigured
reconfigured in
in the
the Node
Node B
B
the
the RNC
RNC sets-up
sets-up the
the AAL2
AAL2
bearer
bearer to
to carry
carry it.
it. As
As before
before
this
this done
done via
via ALCAP
ALCAP
Establish
Establish procedures
procedures and
and is
is
followed
followed by
by FP
FP
synchronisation.
synchronisation.
UE
Node B
RNC
SGSN

RRC UL DT
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP
ALCAP AAL2 Bearer Set-up

and Synchronisation
08/11/16
72
Part 5

(PS)
PDP Context Activation: NBAP: RL Reconfigure Commit
Procedure Overview
Description:
When
When the
the AAL2
AAL2 connection
connection is
is
ready
ready the
the RNC
RNC instructs
instructs the
Node
Node B
B to
to commit
commit the
the
changes
changes itit had
had prepared
prepared in
in
the
the reconfiguration.
reconfiguration.
The
The Commit message indicates
the
the Frame
Frame number
number at
at which
which
the
the change
change should
should occur.
occur.
Main IEs:
Transaction
Transaction Id,
Id, CFN
CFN
UE
Node B
RNC
SGSN

RRC UL DT
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP

and Synchronisation
NBAP
08/11/16
[1]
73
Part 5

(PS)
PDP Context Activation: RRC: Radio Bearer Set-Up
Procedure Overview
Description:
The
The UTRAN has been
configured
configured for
for the
the new
new
DTCH,
DTCH, so
so the
the UE can
can now
now be
be
instructed
instructed to
to set-up
set-up the
the
Radio
Radio Bearer.
Bearer. The
The RNC
RNC
does
does this
this via
via an
an RRC
RRC RB
RB setsetup
up request.
request. This includes
includes the
the
same
same CFN
CFN as
as indicated
indicated to
to
the
the Node
Node B.
B.
UE
Node B

RRC UL DT
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP
Transaction
Transaction ID,
ID, CFN,
CFN, State
State
Indicator,
Indicator,
08/11/16
SGSN
Main IEs:
RB
RB Set-up
Set-up info
info
RAB
RAB ID,
ID, CN
CN Domain
Domain ID,
ID,
PDCP
info,
RLC
PDCP info, RLC Info,
Info, TFC,
TFC,
TFS
TFS
RNC

and Synchronisation
NBAP
(DCCH)
[1]
74
Part 5

(PS)
PDP Context Activation: RRC: Radio Bearer Set-Up Complete
Procedure Overview
Description:
Once
Once the
the UE
UE has
has configured
configured the
the
RB
RB itit returns
returns aa confirmation
confirmation
message
message in
in the
the form
form of
of an
an
RRC
RRC RB
RB set-up
set-up Complete.
Complete.
Main IEs:
UE
Node B
RNC
SGSN

RRC UL DT
Transaction
Transaction ID
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP

and Synchronisation
NBAP
(DCCH)
RRC RB Setup Comp
(DCCH)
08/11/16
[1]
75
Part 5

(PS)
PDP Context Activation: RANAP: RAB Assignment Response
Procedure Overview
Description:
Receipt
Receipt of
of the
the set-up
set-up complete
complete
message
message by
by the
the RNC
RNC
indicates
indicates that
that RAB
RAB
assignment
assignment procedure
procedure is
is
complete,
complete, itit indicates
indicates this
this
back
back to
to the
the SGSN
SGSN via
via aa
RANAP
RANAP RAB
RAB assignment
assignment
response,
response, that
that also
also includes
includes
the
the DL
DL addressing
addressing for
for the
the
GTP-U
GTP-U connection.
connection.
UE
Node B
RNC
SGSN

RRC UL DT
NBAP
RANAP DT
RANAP
RAB Assignment Req.
NBAP
Main IEs:
NSAPI,
NSAPI, RNC
RNC GTP-U
GTP-U IP
IP
Address,
Address, DL
DL TEID
TEID

and Synchronisation
NBAP
(DCCH)
RRC RB Setup Comp
(DCCH)
08/11/16
RANAP
RAB Assignment Resp
[1]
76
Part 5

(PS)
PDP Context Activation: GTP-C: Create PDP Context Request
Procedure Overview
Description:
The
The final part of the connection
can
can now
now be
be established
established this
this
is
is the
the connection
connection to
to the
the AP
AP
indicated
indicated in
in the
the PDP
PDP
activation
activation request. The
SGSN
SGSN identifies
identifies the
the correct
correct
GGSN
GGSN and
and sends
sends itit aa Create
Create
PDP
PDP context
context Request.
Request.
Main IEs:
UE
Node B
RNC
SGSN
GGSN

Context Activation Request and RAB Set-Up
GTP-C
[1]
Create PDP Context Request
IMSI,
IMSI, Restart Counter, Data
TEID,
TEID, Control TEID, Data IP
Addr,
Addr, Control
Control IP
IP Addr,
Addr, NSAPI,
NSAPI,
APN,
APN, QoS
QoS profile,
profile, PDP
PDP
Address
Address
08/11/16
77
Part 5

(PS)
PDP Context Activation: GTP-C: Create PDP Context Response
Procedure Overview
Description:
Once
Once the
the Context
Context has
has been
been
created
created in
in the
the GGSN
GGSN itit
returns
returns aa Create
Create PDP
PDP
Context
Context Response,
Response, indicating
indicating
the
the UL
UL GTP
GTP Paramaters,
Paramaters,
QoS
QoS profile
profile and
and UE
UE PDP
PDP
address
address
Main IEs:
Restart
Restart Counter,
Counter, Data
Data TEID,
TEID,
Control
Control TEID,
TEID, Data
Data IP
IP Addr,
Addr,
Control
Control IP
IP Addr,
Addr, QoS
QoS profile,
profile,
PDP
PDP Address
Address
08/11/16
UE
Node B
RNC
SGSN
GGSN

GTP-C
GTP-C
[1]
Create PDP Context Response
78
Part 5

(PS)
PDP Context Activation: SM: Activate PDP Context Accept
Procedure Overview
Description:
The
The Context s now active and all
the
the transport
transport bearers
bearers are
are in
in
place,
place, the
the SGSN
SGSN can
can
therefore
therefore complete
complete the
the
procedure
procedure by
by sending
sending the
the UE
UE
an
an Activate
Activate PDP
PDP context
Accept.
Accept. This
This message is
also
also used
used to
to inform
inform the
the UE
UE of
of
the
the offered
offered QoS
QoS settings
settings and
and
PDP
PDP Address.
Address.
UE
Node B
RNC
08/11/16
GGSN

GTP-C
GTP-C
Main IEs:
Transaction
Transaction ID,
ID, QoS
QoS
Paramaters,
Paramaters, Radio
Radio Priority,
PDP
PDP Address,
Address,
SGSN
Create PDP Context Response
RANAP DT
[2]
RRC DL DT
(Act PDP Context Acc)
[1]
(Act PDP Context Acc)
79
Part 5

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

GGSN PDP Context Create and UE PDP Context Activation Accept
PS
PS Call
Call Active
Active
08/11/16
80

(PS)
Check Point Four
Part 5
UE Attached One PDP Context
PDN
UE
Node B
RNC
SGSN
Iu Connection
GTP-C Connection
DTCH
GTP-U Connection
GT
P-U Connection
UE State:
RRC Connected
Connections:
GTP-U
Signalling :- DCCH RRC Iu GTP-C
08/11/16
GGSN
PMM Attached
SM Active
User :- DTCH
81
- UE initiated
Call Tear down (PS)
Part 6
Procedure
Overview.
In this Procedure the UE is attached to the Network with a single
PDP Context Active. The call tear down is Mobile Originated (mo)
and is shown in two parts, PDP context deactivate then Detach.
The following steps need to be executed in order for a mo call tear
down to complete;
1. PDP Context Deactivate request from UE
2. Radio Link Setup
3. Iub Transport Bearer Setup
4. DCH-FP Synchronisation
5. Connection Setup
6. Attach Procedure
7. Authentication and Security Procedures
8. PDP Context Activation Procedure
9. Radio Link and RAB Configuration
10. Data Transfer
08/11/16
82
Part 6
- UE initiated Call Tear

down (PS)
PDP Context Deactivation:
SM: Deactivate PDP Context Request

Procedure Overview
Description:
The
The first step in call teardown is
is
to
to deactivate
deactivate the
the PDP
PDP
context.
context. This
This is
is aa Session
Session
Management
Management (NAS)
(NAS)
message
message sent
sent by
by the
the UE
UE and
and
carried
carried by
by DT messages to
the
the Core
Core Network.
Network.
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
[1]
RRC UL DT
(Deact PDP Context Req)
RANAP DT
[2]
Main IEs:
SM:
SM: Deactivate
Deactivate PDP
PDP Context
Context
Request
Request
Transaction
Transaction ID,
ID, Type,
Type, Cause
Cause
08/11/16
83
Part 6

down (PS)
PDP Context Deactivation: GTP-C: Delete PDP Context Request
Procedure Overview
Description:
Once
Once the
the Core
Core Network
Network has
has
received
received the
the deactivate
deactivate
request,
request, itit starts
starts the
the teardown
teardown
procedure
procedure by
by requesting
requesting the
the
GGSN
GGSN to
to delete
delete this
this context.
context.
This
This is
is done
done via
via the
the GTP-C
GTP-C
connection
connection that
that exists
exists for
for this
this
UE.
UE. The
The context
context (normally
(normally
there
there might
might be
be more
more than
than
one)
one) is
is identified
identified by
by its
its
NSAPI.
NSAPI.
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
RRC UL DT
RANAP DT
GTP-C
[1]
Delete PDP Context Request
Main IEs:
UL
UL TEID,
TEID, NSAPI
NSAPI
08/11/16
84
Part 6

down (PS)
PDP Context Deactivation: GTP-C: Delete PDP Context Response
Procedure Overview
Description:
Once
Once the
the GGSN
GGSN has
has deleted
deleted the
the
PDP
PDP context
context for
for the
the UE
UE
associated
associated with
with the GTP-C
connection
connection and
and the
the Context
Context
associated
associated with
with the NSAPI, it
responds
responds to
to the
the SGSN
SGSN with
with
the
the Delete
Delete PDP
PDP context
context
Response.
Response. This
This simply
indicates
indicates that
that the
the request
request has
has
been
been accepted.
accepted.
Main IEs:
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
RRC UL DT
RANAP DT
GTP-C
GTP-C
[1]
Delete PDP Context Response
DL
DL TEID,
TEID, Cause
Cause
08/11/16
85
Part 6

down (PS)
PDP Context Deactivation: PMM: Deactivate PDP Context Accept
Procedure Overview
Description:
The
The SGSN now confirms to the
UE
UE that
that the
the Deactivate
Deactivate PDP
PDP
context
context request
request has
has been
been
accepted.
accepted. This
This is
is done
done via
via aa
Session
Session Management
Management (NAS)
(NAS)
message
message carried
carried in
in DL
DL DT
DT
messages.
messages. The
The Type
Type IE
IE
indicates
indicates aa
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
RRC UL DT
RANAP DT
GTP-C
Main IEs:
GTP-C
Delete PDP Context Response
SM:
SM: Deactivate
Deactivate PDP
PDP Context
Context
Accept;
Accept;
Transaction
Transaction ID,
ID, Type
Type
08/11/16
[2]
RRC DL DT
RANAP DT
(Deact PDP Context Acc)
[1]
(Deact PDP Context Acc)
86
Part 6

down (PS)
PDP Context Deactivation: RANAP: Iu Release Command
Procedure Overview
Description:
Once
Once the
the PDP
PDP context
context has
has been
been
deactivate
deactivate in
in the
the GGSN
GGSN and
and
the
the UE
UE has
has been
been notified
notified the
the
SGSN
SGSN initiates
initiates the release of
the
the associated
associated RABs.
RABs.
Because
Because this
this is
is the
the only
only PDP
PDP
context
context for
for this
this UE
UE the
the Iu
Iu
release
release Procedure
Procedure is
is carried
carried
out
out rather
rather than
than the
the RAB
RAB
Assignment
Assignment (with
(with release)
release)
procedure.
procedure.
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
PDP Context Deactivation Request / Accept and GGSN PDP Context Deletion
RANAP
Iu Release Command
[1]
RANAP
Iu Release Complete
[2]
Main IEs:
1.
1. Message
Message Type,
Type, Cause
Cause
(normal
(normal release)
release)
2.
2. Message
Message Type
Type (successful
(successful
outcome)
outcome)
08/11/16
87
Part 6

down (PS)
PDP Context Deactivation: RRC: RRC Connection Release
Procedure Overview
Description:
The
The RNC responds to the Iu
release
release command,
command, by
by
releasing
releasing the
the RRC
connection
connection to
to the
the UE.
UE. This
This is
is
done
done via
via the
the RRC
RRC
Connection
Connection Release
Release
message..
message.. This
This message
message
indicates
indicates aa Normal
Normal Event
Event
RRC
RRC Connection
Connection release..
release.. It
also
also includes
includes aa Threshold
Threshold
value
value N308,
N308, used
used by
by the
the UE
UE
to
to set
set the
the no
no of
of responses
responses itit
should
should return.
return.
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
RANAP
Iu Release Command
[1]
RRC
RANAP
Iu Release Complete
Connection Release
Main IEs:
Message
Message Type,
Type, Transaction
Transaction ID,
ID,
N308,
N308, Release
Release Cause
Cause
08/11/16
88
Part 6

down (PS)
PDP Context Deactivation: RRC: RRC Connection Release Complete
Procedure Overview
Description:
The
The UE responds to the
connection
connection release
release request
request
with
with one or more RRC
Connection
Connection Release
Release
Complete
Complete messages.
messages.
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
Main IEs:
RANAP
Iu Release Command
Message
Message Type,
Type, Transaction
Transaction ID
ID
RRC
RANAP
Iu Release Complete
Connection Release
[1]
08/11/16
RRC
Conn Release Complete
89
Part 6

down (PS)
PDP Context Deactivation: NBAP: RL Deletion Request / Response
Procedure Overview
Description:
After
After the
the UE
UE has
has confirmed
confirmed the
the
RRC
RRC Connection
Connection Release,
Release,
the
the RNC
RNC indicates
indicates to
to the
the
Node
Node B
B to
to release
release the
the Radio
Radio
Links
Links for
for this
this UE.
UE. This
This is
is an
an
NBAP
NBAP procedure
procedure using
using RL
RL
Deletion
Deletion Request
Request // Response
Response
messages.
messages.
UE
Node B
2.
2. RNC
RNC context
context ID,
ID, Message
Message
Type,
Type, Transaction
Transaction ID
ID
08/11/16
SGSN
GGSN
PDP
PDP Context
Context Active
Active
RANAP
Iu Release Command
Main IEs:
1.
1. Node
Node B
B and
and RNC
RNC context
context
IDs,
IDs, Message
Message Type,
Type,
Transaction
Transaction ID,
ID, RL
RL
Information
Information (RL
(RL IDs)
IDs)
RNC
RRC
RANAP
Iu Release Complete
Connection Release
RRC
NBAP
RL Deletion Request
NBAP
[1]
[2]
90
Part 6

down (PS)
PDP Context Deactivation: ALCAP: Release Request / Confirm
Procedure Overview
Description:
Once
Once the
the Radio
Radio Link
Link has
has been
been
deleted
deleted the
the RNC
RNC needs
needs to
to
remove
remove the
the associate
associate dd AAL2
AAL2
bearers.
bearers. This
This is
is an
an ALCAP
ALCAP
procedure
procedure that
that uses
uses Release
Release
Request
Request and
and Confirm
Confirm
messages.
messages.
UE
Node B
RNC
GGSN
PDP
PDP Context
Context Active
Active
RANAP
Iu Release Command
Main IEs:
1.
1. DSAID,
DSAID, Cause
Cause (normal),
(normal),
Binding
Binding ID
ID
2.
2. DSAID
DSAID
SGSN
RRC
RANAP
Iu Release Complete
Connection Release
RRC
NBAP
RL Deletion Request
NBAP
08/11/16
ALCAP
Release Request
[1]
ALCAP
Release Confirm
[2]
91
Part 6

down (PS)
PDP Context Deactivation: Deactivate PDP Context Complete
Procedure Overview
At
At this
this point;
point;
The
deleted
deleted in
in the
the SGSN,
SGSN, GGSN,
GGSN,
and
and at
at the
the UE
UE
UE
Node B
RNC
SGSN
GGSN
PDP
PDP Context
Context Active
Active
The
The RRC connection has been
released
released
All
All associated
associated Radio
Radio Links
Links have
have
been
been released
released in
in the
the UTRAN
UTRAN
Iu Release Procedure (RAB and RRC Connection Released)
All
All associated
associated AAL2
AAL2 connections
connections
have
been
released
have been released
The
The UE is now SM Inactive,
PMM
PMM Idle
Idle and
and RRC
RRC Idle.
Idle. ItIt is
is
still
still PS
PS attached,
attached, but
but is
is
currently
currently without
without any
any
dedicated
dedicated signalling
signalling or
or user
user
connections,
connections, has
has no
no network
network
recognised
recognised IP
IP address
address and
and
cannot
cannot send
send data.
data.
08/11/16
PDP
PDPContext
ContextDeactivation
DeactivationProcedure
Procedure
Complete
Complete
92
Part 6

down (PS)
PMM Detach: PMM: Detach Request + SCCP Connection set-up
Procedure Overview
Description:
IfIf the
the UE
UE now
now wishes
wishes to
to detach
detach
from
from the
the network
network itit can
can carry
carry
out
out aa detach
detach procedure.
procedure. In
In
order
order to
to do
do this
this itit first
first needs
needs
to
to re-establish
re-establish an
an RRC
RRC
signalling
signalling connection.
connection. This
This
procedure
procedure is
is the
the same
same as
as
that
that outlined
outlined previously.
previously.
Then
Then using
using this
this RRC
RRC
connection
connection itit sends
sends aa PMM
PMM
Detach
Detach Request
Request to
to the
the
SGSN.
SGSN. This
This procedure
procedure also
also
establishes
establishes aa new
new SCCP
SCCP (Iu)
(Iu)
connection.
connection.
UE
Node B
RNC
SGSN
RRC Connection Set-Up Procedure

RRC Initial DT
(PMM Detach Request)
[1]
RANAP Initial UE
SCCP Connection Request
SCCP Connection
Confirm
[2]
[3]
Main IEs:
Message
Message Type,
Type, Detach
Detach Type,
Type, PTMSI
TMSI
08/11/16
93
Part 6

down (PS)
PMM Detach: PMM: Detach Accept
Procedure Overview
Description:
After
After the
the SGSN
SGSN has
has received
received the
the
Detach
Detach request
request itit may
may decide
decide
to
to authenticate
authenticate the
the UE.
UE. For
For
first
first call
call this
this may
may not
not be
be
done.
done. The
The SGSN
SGSN then
then sends
sends
aa PMM:
PMM: Detach
Detach Accept
Accept to
to the
the
UE
UE confirming
confirming the
the detach.
detach.
The
The force
force to
to standby
standby is
is aa
GPRS
GPRS mobility
mobility indicator,
indicator, but
but
is
is mandatory
mandatory for
for both
both GPRS
GPRS
and
and UMTS.
UMTS. For
For UMTS
UMTS itit is
is
set
set to
to Force
Force to
to standby
standby not
not
indicated.
indicated.
UE
Node B
RNC
SGSN

RRC Initial DT
RRC DL DT
(PMM Attach Accept)
RANAP Initial UE
SCCP Connection
Confirm
RANAP Initial UE
(PMM Detach Accept)
Main IEs:
Message
Message Type,
Type, Force
Force to
to standby
standby
indicator
indicator
08/11/16
94
Part 6

down (PS)
PMM Detach: RANAP: Iu Release Command / Complete
Procedure Overview
Description:
The
The Iu and RRC connections
previously
previously configured
configured to
to carry
carry
the
the Detach
Detach request
request can
can now
now
be
be released.
released. This
This is
is initiated
initiated
by
by the
the SGSN
SGSN with
with an
an Iu
Iu
release
release procedure.
procedure.
UE
Node B
2.
2. Message
Message Type
Type (successful
(successful
outcome)
outcome)
08/11/16
SGSN

RRC Initial DT
Main IEs:
1.
1. Message
Message Type,
Type, Cause
Cause
(normal
(normal release)
release)
RNC
RRC DL DT
(PMM Attach Accept)
RANAP Initial UE
SCCP Connection
Confirm
RANAP Initial UE
(PMM Detach Accept)
RANAP
Iu Release Command
RANAP
Iu Release Complete
[1]
[2]
95
Part 6

down (PS)
PMM Detach: RRC: RRC Connection Release / Release Complete
Procedure Overview
Description:
The
The RNC responds to the Iu
release
release command,
command, by
by
releasing
releasing the
the RRC
connection
connection to
to the
the UE.
UE. This
This is
is
done
done via
via the
the RRC
RRC
Connection
Connection Release
Release
message.
message. indicating
indicating aa
Normal
Normal Connection
Connection release..
release..
ItIt also
also includes
includes aa Threshold
Threshold
value
value N308,
N308, used
used by
by the
the UE
UE
to
to set
set the
the maximum
maximum number
number
of
of responses
responses itit should
should return.
return.
The
The UE responds with one or
more
more RRC
RRC Connection
Connection
Release
Release Complete
Complete
messages.
messages.
UE
Node B
RNC
SGSN

RRC Initial DT
RRC DL DT
(PMM Attach Accept)
RANAP Initial UE
SCCP Connection
Confirm
RANAP Initial UE
(PMM Detach Accept)
RANAP
Iu Release Command
[1]
[2]
RRC Connection Release

(DCCH)
RRC Conn Rel Complete
(DCCH)
RANAP
Iu Release Complete
Main IEs:
1.
1. Message
Message Type,
Type, Transaction
Transaction
ID,
ID, N308,
N308, Release
Release Cause
2.
2. Message
Message Type,
Type, Transaction
Transaction
ID
ID
08/11/16
96
Part 6

down (PS)
PMM Detach: NBAP: RL Deletion Request / Deletion Complete
Procedure Overview
Description:
After
After the
the UE
UE has
has confirmed
confirmed the
the
RRC
RRC Connection
Connection Release,
Release,
the
the RNC
RNC indicates
indicates to
to the
the
Node
Node B
B to
to release
release the
the Radio
Radio
Links
Links for
for this
this UE.
UE. This
This is
is an
an
NBAP
NBAP procedure
procedure using
using RL
RL
Deletion
Deletion Request
Request // Response
Response
messages.
messages.
Main IEs:
1.
1. Node
Node B
B and
and RNC
RNC context
context
IDs,
IDs, Message
Message Type,
Type,
Transaction
Transaction ID,
ID, RL
RL
Information
Information (RL
(RL IDs)
IDs)
2.
2. RNC
RNC context
context ID,
ID, Message
Message
Type,
Type, Transaction
Transaction ID
ID
UE
Node B
SGSN

RANAP Initial UE
SCCP Connection
Confirm
RRC Initial DT
RANAP Initial UE
(PMM Detach Accept)
RANAP
RRC DL DT
(PMM Attach Accept)
Iu Release Command
(DCCH)
(DCCH)
RANAP
Iu Release Complete
NBAP
RL Deletion Request
NBAP
RL Deletion Complete
08/11/16
RNC
[1]
[2]
97
Part 6

down (PS)
PMM Detach: ALCAP: Release Request / Release Confirm
Procedure Overview
Description:
Once
Once the
the Radio
Radio Link
Link has
has been
been
deleted
deleted the
the RNC
RNC needs
needs to
to
remove
remove the
the associate
associate dd AAL2
AAL2
bearers.
bearers. This
This is
is an
an ALCAP
ALCAP
procedure
procedure that
that uses
uses Release
Release
Request
Request and
and Confirm
Confirm
messages.
messages.
Main IEs:
1.
1. DSAID,
DSAID, Cause
Cause (normal),
(normal),
Binding
Binding ID
ID
2.
2. DSAID
DSAID
UE
Node B
RNC
SGSN

RANAP Initial UE
SCCP Connection
Confirm
RRC Initial DT
RANAP Initial UE
(PMM Detach Accept)
RANAP
RRC DL DT
(PMM Attach Accept)
Iu Release Command
(DCCH)
(DCCH)
RANAP
Iu Release Complete
NBAP
RL Deletion Request
NBAP
RL Deletion Complete
ALCAP
Release Request
ALCAP
Release Confirm
08/11/16
[1]
[2]
98
Part 6

down (PS)
Messages (14): PS Call Tear Down Complete
Procedure Overview
This
This is the end of the PS call tear
down
down procedure;
UE
The
deleted
deleted
Node B
RNC
PDP
PDP Context
Context Active
Active
The
The UE has been GPRS
detached
detached
PDP Context Deactivate / RAB Release / RRC Connection Release
The
The RRC connection has been
released
released
RRC Connection set-Up / PMM Detach / RRC Connection Release
All
All associated
associated Radio
Radio Links
Links have
have
been
released
in
the
been released in the UTRAN
UTRAN
All
All associated
associated AAL2
AAL2 connections
connections
have
have been
been released
released
SGSN
CC: Call Release
PS
PS Call
Call Tear
Tear Down
Down
Complete
Complete
The
The UE is now SM Inactive,
PMM
PMM Detached
Detached and
and RRC
RRC
Idle.
Idle. ItIt is
is without
without any
any
dedicated
dedicated signalling
signalling or
or user
user
connections,
connections, has
has no
no network
network
recognised
recognised IP
IP address
address and
and
cannot
cannot send
send data.
data.
08/11/16
99
Discussion
Any Questions ?
08/11/16
100
Std
Document
References
References
08/11/16
3GPP TS 25.410
3GPP TS 25.413
3GPP TS 25.420
3GPP TS 25.423
3GPP TS 25.430
3GPP TS 25.433
3GPP TS 25.415
3GPP TS 25.426
3GPP TS 25.007
3GPP TS 25.008
ITU-T I.363.2
ITU-T I.363.5
ITU-T Q.2630.1
Iu Interface
RANAP Protocol
Iur Interface
RNSAP Protocol
Iub Interface
NBAP Protocol
UTRAN Iu Interface User Plane Protocols
Iur & Iub Interface Data Transport Signalling for DCH
Mobile radio interface sig. Layer 3; General Aspects
Mobile radio interface sig. Layer 3; CN Protocols
AAL2 Specification
AAL5 Specification
ALCAP
101
Internal
Document
References
References
08/11/16
SRD-UTRAN-CSU-1 SRD for Call Setup

SRD-UTRAN-CPR-1 SRD for Call Proceeding
SRD-UTRAN-CTD-1 SRD for Call teardown
SRD-UTRAN-POW-1 SRD for Power Control
SRD-UTRAN-RCC-1 SRD for Radio Channel Coding
SRD-UTRAN-HO-1 SRD for Handover
102
Appendices
Appendix A: Part 1 - Node B

Initialisation and Cell Camp On
Appendix B: Part 2 - UE Camp On &
Location Update
08/11/16
103
Appendix A: Part 1
Node B Initialisation and

Cell Camp on
08/11/16
104
Part 1
- Node B Initialisation
1.1) Audit Procedure: Audit Required Indication Message
Procedure Overview
Type: NBAP
Purpose:
After
After the SSCOP
SSCOP layer
layer is
is
established
established via
via the exchange of
BGN/BGAK
BGN/BGAK PDUs,
PDUs, the
the Node
Node B
B
tells
tells RNC
RNC that
that itit has
has one
one or
or
more
more cells
cells that
that need
need to
to be
be
configured.
configured.
UE
Node B
RNC
Audit Required Indication
MSC
[1]
Channels:
SSCF/SSCOP/AAL5
Main IEs:
Transaction ID
08/11/16
105
Part 1
1.2) Audit Procedure: Audit Request Message
Procedure Overview
Type: NBAP
Purpose:
RNC requests an Audit of the
Node B configuration.
Channels:
UE
Node B
RNC
MSC

Audit Request
[1]
SSCF/SSCOP/AAL5
Main IEs:
Transaction ID
08/11/16
106
Part 1
1.3) Audit Procedure: Audit Response Message
Procedure Overview
Type: NBAP
Purpose:
Node B informs the RNC of its
Cell and Channel Configuration
Channels:
SSCF/SSCOP/AAL5
UE
Node B
RNC
MSC

Audit Request
Audit Response
[1]
Main IEs:
Transaction ID
Node B Capacity
Cell IDs
Channel Information...
08/11/16
107
Part 1
1.4) Cell Set-up Procedure: Resource Status Indication
Procedure Overview
Type: NBAP
Purpose:
Node B informs the
RNC that it has added
a cell(s) and that it
(they) need to be
configured.
UE
Node B
RNC
MSC
Audit Request Procedure

Resource Status Indication
[1]
Channels:
SSCF/SSCOP/AAL5
Main IEs:
Transaction ID
No Failure
Local Cell Added
08/11/16
108
Part 1
1.5) Cell Set-up Procedure: Cell Set-up Request
Procedure Overview
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
UE
Node B
RNC
MSC

Cell Setup Request
[1]
Channels:
SSCF/SSCOP/AAL5
Main IEs:
Transaction ID
Cell & Local Cell ID
Scrambling Codes
Sync and Power Info
08/11/16
109
Part 1
1.6) Cell Set-up Procedure: Cell Set-up Response
Procedure Overview
Type: NBAP
Purpose:
Node B informs the
(they) need to be
configured.
Channels:
UE
Node B
RNC
MSC

Cell Setup Request
Cell Set-Up Response
[1]
SSCF/SSCOP/AAL5
Main IEs:
Transaction ID
Cell Setup Success
08/11/16
110
Part 1
1.7) Cell Set-up Procedure: Block Resource Request
Procedure Overview
Type: NBAP
UE
Node B
RNC
MSC
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:

Cell Setup Request
Block Resource Request
[1]
SSCF/SSCOP/AAL5
Main IEs:
Trans & Cell ID
Priority Indicator (high)
08/11/16
111
Part 1
1.8) Cell Set-up Procedure: Block Resource Response
Procedure Overview
Type: NBAP
UE
Node B
RNC
MSC
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 IEs:
Trans & Cell ID
08/11/16

Cell Setup Request
Block Resource Request
Block Resource Response
[1]
112
Part 1
1.9) System Information Broadcast Procedure:
System Information
Update Request and Response
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
RNC updates the System
Information
Information by
by sending
sending aa
series
series of
of Sys.
Sys. Info.
Info. Update
Update
Request
Request messages
messages which
which are
are
ackd
ackd by
by the
the Node
Node B.
B. SIB
SIB
blocks
blocks are
are segmented
segmented into
into
246
246 bit
bit blocks,
blocks, which
which are
are sent
sent
(and
(and ackd)
ackd) sequentially.
sequentially.
Main IEs:
MIB/SIB info
Segment Info
08/11/16

Cell Setup Procedure
System Info Update Req.
Segment 1
[1]
System Info Update Resp.

Segment 1
[2]

Segment 2
[3]

Segment 2
[4]

Segment 3
[5]

Segment 3 . . etc
[6]
113
Part 1
1.10) System Information Broadcast Procedure:

System Information is Broadcast for each cell
Procedure
Overview
Type:
BCH over P-CCPCH
UE
Node B
Purpose:
MSC
The Node B has

received and stored the
System Info for each
cell (from the RNC) and
now broadcasts it
throughout the cell.

Segment 1
Segment 1
Segment 2
Transport Format (BCH):
TB size: 246 bits
TTI: 20 ms
Conv. Encoding: 1/2

rate
16 bit CRC

Segment 2
Segment 3
[1]
[2]
[3]
08/11/16
RNC
BCH: System Info

Segment 3 . . etc
BCH: System Info

BCH: System Info
114
Part 1
1.11) Common Transport Channel Set-up Procedure:
Common Transport
Channel Set-up Request (PRACH, AICH, RACH)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
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.

System Information Update
Common Transport CH
Set-Up Request
[1]
Main IEs:
RACH info (TF Set)

AICH info (Codes, SF,
etc)
PRACH (TFCS, SF, etc)
08/11/16
115
Part 1
Common Transport Channel Set-up Response (PRACH, AICH, RACH)

Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The Node B Acks the
1st Com Trans Setup
msg which established
the PRACH, AICH, &
RACH/
Main IEs:
for RACH
Binding and Com ID
Transport layer address
08/11/16

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
[1]
116
Part 1

ALCAP Establish
Request (with Binding ID for RACH)
Procedure
Overview
Type: ALCAP
UE
Node B
RNC
MSC
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

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
[1]
Main IEs:
OSAID, DSAID + CEID,

SUGR,
AAL2 Destination
Address of Node B
08/11/16
117
Part 1

ALCAP Establish
Confirm
Procedure
Overview
Type: ALCAP
UE
Node B
RNC
MSC
Purpose:
This message confirms
interface for the RACH.
Main IEs:
OSAID + DSAID

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
ALCAP ECF
08/11/16
[1]
118
Part 1

Synchronisation
over RACH -FP (Framing Protocol)
Procedure
Overview
Type: RACH- FP
UE
Node B
RNC
MSC
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 IEs:
Control messages
contain time stamps to
establish the time the
message was sent and
when it arrived at the
opposite node.
08/11/16

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
119
Part 1
Common Transport
Channel Set-up Request (S-CCPCH, FACH, PCH)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
Common Transport
Channels are set up in
two parts. The 2nd
Com Trans Setup
Request message
specifies the
establishment of the SCCPCH, FACH, and
PCH.

Common Transport Setup Procedures:
PRACH, AICH and RACH + ALCAP for RACH
Common Transport CH
Set-Up Request
[1]
Main IEs:
FACH info (TF Set)

PCH info (TF Set)
S-CCPCH (TFCS, SF,
TFCI, Codes, etc)
08/11/16
120
Part 1
Common Transport
Ch. Set-up Response (S-CCPCH, FACH, PCH)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The Node B Acks the
2nd Com Trans Setup
msg which established
the FACH, PCH & SCCPCH
Main IEs:
for PCH and FACH
Binding and Com ID

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
[1]
Transport layer address
08/11/16
121
Part 1
ALCAP Establish
Request (with Binding ID for FACH and PCH)
Procedure
Overview
Type: ALCAP
UE
Node B
RNC
MSC
Purpose:
This
This message
message request
request the
the
establishment
establishment of an AAL2
path
path over
over the
the IuB
IuB interface
interface
for
for the FACH.
FACH. The
The SUGR
SUGR
parameter
parameter contains
contains the
the
Binding
Binding ID which was
was
returned
returned to
to the
the RNC
RNC in
in the
2nd
2nd Com
Com Trans
Trans Ch
Ch Setup
Setup
Response
Response message
message There
will
will be
be separate
separate ALCAP
ALCAP
procedures
procedures for
for the
the FACH
FACH and
and
the
the PCH
PCH channels.
channels.
Main IEs:

SUGR,

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
[1]
AAL2 Dest. Address of

Node B
08/11/16
122
Part 1

ALCAP Establish
Confirm (FACH and PCH)
Procedure
Overview
Type: ALCAP
UE
Node B
RNC
MSC
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 IEs:
OSAID + DSAID
08/11/16

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
ALCAP ECF
[1]
123
Part 1
Synchronisation
over FACH - FP and PCH-FP(Framing Protocol)
Procedure
Overview
Type: FACH-FP
UE
Node B
RNC
MSC
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 IEs:
Control messages
opposite node.
08/11/16

Common Transport CH
Set-Up Request
Common Transport CH
Set-Up Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
124
Part 1
1.21) Update System Information Procedure:
System Information
Update Request (SIB 5 - Channel Updates)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The RNC announces
the configuration of the
common channels for
each cell by changing
SIB5. This info is
relayed to UEs via the
BCH.
Main IEs:
References to other
SIBs
PICH Power offset

PRACH, AICH, S-CCPCH, FACH, PCH and RACH +
ALCAP and FP-Sync. for RACH, FACH and PCH
SIB 5
[1]
AICH Power offset

P-CCPCH info
S-CCPCH info
08/11/16
125
Part 1
Resource Status
Indication (Service impacting, com ctrl port enabled)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
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 IEs:
Trans ID
Com Control Port ID

SIB 5
[1]
Service Impacting
Indication
08/11/16
126
Part 1

Unblock Resource
Indication Message
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The Node B is ready to
unblock the new cell(s).

Main IEs:
Trans ID
Cell ID
Unblock resource

SIB 5
Unblock Resource Ind
08/11/16
[1]
127
Part 1
System Information
Update Request (SIB 3 - Cell Unblocked)
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The RNC updates SIB3
to Unbarred
Main IEs:
Cell ID
Transaction ID
SIB 3 Updated to
unbarred

SIB 5
SIB 3
08/11/16
[1]
128
Part 1

System Information
Update Response
Procedure
Overview
Type: NBAP
UE
Node B
RNC
MSC
Purpose:
The RNC updates SIB3
to Unbarred
Main IEs:
Transaction ID

SIB 5
SIB 3
08/11/16
[1]
129
Part 1
- Node B Initialisation Summary

UE
Node B
RNC
MSC

CellSetup Procedure
System Information Update Procedure
Common Transport Setup Procedures
for PRACH, AICH, S-CCPCH, FACH,
PCH and RACH + ALCAP and FP-Sync.
for RACH, FACH and PCH
Request - SIB 5
Update Resources and Unblock Cell
Request - SIB 3
08/11/16
130
Appendix B: Part 2
UE Camp On & Location

Update
08/11/16
131
- UE Camp On &
Location Update
Part 2
08/11/16
The UE searches for the Primary SCH, which has the same 256-chip
code in every cell.
Tuning for a maximum on the P-SCH allows the Secondary SCH to be
found.
The S-SCH uses 1 of 16 codes which identify the base station.
Once the Secondary SCH code word has been identified, the UE
achieves frame and slot synchronisation.
The UE then finds the primary scrambling codes which belong to the
SCHs code group.
Both SCHs are time multiplexed on the Primary Common Control
Physical Channel, which also carries the BCH.
The BCH provides UTRAN or Cell-specific information such as Random
Access codes and slots for the RACH.
The BCH also carries the MIB and SIBs which were described in the
Initialisation Section.
The UE now has all the information it needs to access the RACH to
initiate the Location Update Procedure (Step 2) or Call Set-up (Step 3)
132
Part 2
08/11/16
- UE Location Update
Procedure
Random Access Detection Procedure

Radio Signalling Bearer Establish Procedure
Location Update Request Procedure
Identity Request Procedure
Authentication Procedure
Location Update Accept/Reject Procedure
TMSI Reallocation Procedure
Radio Signalling Bearer Release Procedure
133
Procedure
2.1) Location Update: Random Access Detection Procedure
Part 2
Type: RACH
UE
Node B
RNC
MSC
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.
08/11/16
BCH: System Info
[1]
BCH: System Info

[2]
BCH: System Info
Preamble
Preamble
Preamble
[3]
[4]
[5]
[6]
134
Procedure
2.2) Location Update: Random Access Detection Procedure:
Part 2
Access Preamble and AICH Indication

Type:
BCH over PCCPCH
Purpose:
The Node B detects the
access request from
the UE and returns an
Access indication on
the AICH.
UE
Node B
RNC
MSC
BCH: System Info

BCH: System Info
BCH: System Info
Preamble
Preamble
Preamble
AICH: Access Indication
[1]
08/11/16
135
Procedure
2.3) Location Update: Radio Signalling Bearer Establish Procedure:
Part 2
RRC: Connection Request Message

Type: RRC
Channels:
CCCH / RACH
UE
Node B
RNC
MSC
Random Access Detection

(PRACH)
[1]
Main IEs:
Initial UE ID
Establishment Cause
Initial UE capability
08/11/16
136
Procedure
Part 2
RL Set-up Request and RL Set-up Response Messages

Procedure
Overview
Type: NBAP
Purpose:
RNC tells Node B to
configure a Radio
Bearer.
Main IEs:
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
DL Channelisation Code
DCH Binding ID
08/11/16
UE
Node B
RNC
MSC

(PRACH)
RL Setup Request
RL Setup Response
[1]
[2]
137
Procedure
Part 2
Establish Request (ERQ) and Confirm (ECF) Messages

Type: ALCAP
Purpose:
This message sequence
requests (and confirms)
interface for a DCCH.
The SUGR parameter
contains the Binding ID
which was returned to
the RNC in the 1st Com
Trans Ch Setup
Response message
UE
Node B
RNC
MSC

(PRACH)
RL Setup Request
RL Setup Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
Main IEs:

SUGR,
AAL2 Destination
Address of Node B
08/11/16
138
Procedure
Part 2
DCH-FP DL / UL Synchronisation Messages

Procedure
Overview
Type: DCH-FP
UE
Node B
RNC
MSC
Purpose:
Framing Protocol
Synchronisation
between the Node B
and RNC for each
channel. There will be
separate sync.
procedures for all
CCCH and DCCH
channels.
Main IEs:
Control messages
opposite node.
08/11/16

(PRACH)
RL Setup Request
RL Setup Response
ALCAP ERQ
ALCAP ECF
[1]
[2]
139
Procedure
Part 2
RRC Connection Set-up / Complete Messages

Type: RRC
Purpose
RNC
RNC informs
informs the
the UE that
that the
the
DCH
DCH channel
channel is
is established.
established.
UE
UE Acks
Acks by
by replying
replying on
on the
the
DCCH
DCCH with
with aa Setup
Setup
Complete.
Complete.
UE
Node B

(PRACH)
ALCAP ERQ
ALCAP ECF
RRC Con Setup
Initial
Initial UE
UE ID
ID ++ RNTI,
RNTI,
CapUpReq,
CapUpReq,
TFS,
TFS, +TFCS,
+TFCS,
frequency
frequency ++ Power
Power control
control
info.
info.
DL
DL Scram
Scram ++ Chann
Chann codes,
codes,
RRC Con Setup

Complete
UE
UE Capability,
Capability,
Ciphering
Ciphering ++ Integrity
Integrity info
08/11/16
RL Setup Request
RL Setup Response
2. DCCH
Main IEs:
MSC
Channels:
1. FACH
RNC
(FACH)
RRC Conn Setup Comp

(DCCH)
[1]
[2]
140
Procedure
2.8) Location Update: Location Update Request Procedure:
Part 2
RRC: Initial DT [NAS Location Update Request Message]

Type: RRC
UE
Node B
RNC
MSC
Purpose
UE initiates a location
update procedure
Channels:
DCCH

Radio Signalling Bearer Establishment Procedure
RRC: Initial Direct Transfer
(Location Update Request)
[1]
Main IEs:
Update Type (normal)

Cipher Key Seq No.
Location Area Info
UE Classmark
UE ID (IMSI or TMSI)
08/11/16
141
Procedure
Part 2
RANAP: DT [NAS Location Update Request Message]

Type: RANAP
UE
Node B
RNC
MSC
Purpose:
RNC relays the
Location Update
message to the
NAS at the CN
Channels:

RANAP: DT
(Location Upd Request)
[1]
DCCH
Main IEs:
Update Type (normal)

Cipher Key Seq No.
Location Area Info
UE Classmark
UE ID (IMSI/TMSI)
08/11/16
142
Procedure
Part 2
MAP Send_Identification Request

Type: MAP
Purpose:
The Current MSC/VLR
may or may not have a
record of this UE. If it
doesnt, it sends a
MAP Send_ID Request
to a Previous VLR to
retrieve IMSI and
authentication data for
this UE.
UE
Node B
RNC
MSC/V
LR
P-MSC/
VLR

RANAP: DT
Loc. Upd Req
MAP
Send ID Req.
[1]
Channels:
SS7 Signalling
Main IEs:
08/11/16
143
Procedure
Part 2
MAP Send_Identification Acknowledge

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
UE
Node B
RNC
MSC/V
LR
P-MSC/
VLR

RANAP: DT
Loc. Upd Req.
MAP
Send ID Req.
MAP
Send ID Ack
[1]
Channels:
SS7 Signalling
Main IEs:
08/11/16
144
Procedure
2.12) Location Update: Identity Request Procedure:
Part 2
RANAP: Direct Transfer [NAS Identity Request Message]

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 IEs:
UE
Node B
RNC
MSC/V
LR
P-MSC/
VLR

RANAP: DT
Loc. Upd Req.
MAP
Send ID Req.
MAP
RANAP: DT Send ID Ack

[1]
NAS: Identity Req.
ID Type
08/11/16
145
Procedure
Part 2
RRC: Direct Transfer [NAS Identity Request Message]

Type: RRC
Purpose:
The RNC forwards the
Identity Request
message to the UE via
RRC: Direct Transfer.
UE
Node B
RNC
MSC/V
LR

Channels:
RANAP: DT
Loc. Upd Req.
DCCH
MAP
ID Type
RANAP: DT
[1]
08/11/16
MAP
Send ID Req.
Main IEs:
P-MSC/
VLR
Send ID Ack
RRC: DT DCCH NAS: Identity Req.

NAS: Identity Request
146
Procedure
Part 2
RRC: Direct Transfer [NAS Identity Response Message]

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
UE
Node B
RNC
MSC/V
LR
P-MSC/
VLR

RANAP: DT
Loc. Upd Req.
MAP
Send ID Req.
MAP
RANAP: DT
Send ID Ack

[1]
RRC: DT DCCH
NAS: Identity Response
Main IEs:
ID Type
08/11/16
147
Procedure
Part 2
RANAP: Direct Transfer [NAS Identity Response Message]

Type: RANAP
Purpose:
The RNC relays the ID
Response message to
the CN.
Channels:
AAL5/ATM
UE
Node B
RNC
MSC/V
LR

RANAP: DT
Loc. Upd Req.
MAP
Main IEs:
Send ID Req.
ID Type
MAP
P-MSC/
VLR
RANAP: DT
Send ID Ack

RRC: DT DCCH
NAS: Send ID Response
RANAP: DT
Send ID Response
08/11/16
[1]
148
Procedure
2.16) Location Update: Authentication Procedure:
Part 2
RANAP: Direct Transfer [NAS Authentication Request Message]

Type: RANAP & RRC UE
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.
Node B
RNC
MSC

Location Update Request Procedure (RRC/RANAP DT)
Identity Request Procedure (RRC/RANAP DT) Optional
RANAP: DT
NAS: Auth. Request
[1]
Channels:
AAL5/ATM -> DCCH
Main IEs:
08/11/16
149
Procedure
Part 2
RRC: Direct Transfer [NAS Authentication Request Message]

Type: RANAP
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH

Main IEs
[1]
08/11/16
RANAP: DT
RRC: DT DCCH NAS: Auth Request
NAS: Auth Request
150
Procedure
Part 2
RRC: Direct Transfer [NAS Authentication Response Message]

Type: RANAP
UE
Node B
RNC
MSC
Purpose:
Channels:
DCCH
Main IEs:
[1]
08/11/16
RRC: DT DCCH
NAS: Auth Response
RANAP: DT
NAS: Auth Request
151
Procedure
Part 2
RANAP: DT [NAS Authentication Response Message]

Type:
RANAP
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH

Main IEs:
RRC: DT DCCH
NAS: Auth Response
08/11/16
RANAP: DT
NAS: Auth Request
RANAP: DT
NAS: Auth Response
[1]
152
Procedure
2.20) Location Update: Location Update Accept Procedure:
Part 2
RANAP: Direct Transfer [NAS Location Update Accept Message]

Type: RANAP
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH
Main IEs:

Authentication Request Procedure (RRC/RANAP DT) Optional
RANAP: DT
Location Update Accept
08/11/16
[1]
153
Procedure
2.21) Location Update: Location Update Accept Procedure:
Part 2
RRC: Direct Transfer [NAS Location Update Accept Message]

Type: RRC
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH
Main IEs:

[1]
08/11/16
RANAP: DT
RRC: DT
154
Procedure
2.22) Location Update: TMSI Reallocation Complete Procedure:
Part 2
RRC: Direct Transfer [NAS TMSI Reallocation Complete]

Type: RRC
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH
Main IEs:

RANAP: DT
RRC: DT
[1]
08/11/16
RRC: DT
TMSI Reallocation Complete
155
Procedure
2.23) Location Update: TMSI Reallocation Complete Procedure:
Part 2
RANAP: Direct Transfer [NAS TMSI Reallocation Complete]

Type: RANAP
Purpose:
UE
Node B
RNC
MSC

Channels:
DCCH
Main IEs:

RANAP: DT
RRC: DT
RRC: DT
TMSI Reallocation Complete
08/11/16
RANAP: DT
TMSI Reallocation Accept
[1]
156
Procedure
2.24) Location Update: Radio Signalling Bearer Release Procedure:
Part 2
RRC: Connection Release (Unacknowledged)

Type: RRC
UE
Node B
RNC
MSC
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:

Location Update Accept Procedure (RRC/RANAP DT)
TMSI Reallocation Complete Procedure (RRC/RANAP DT)
DCCH
Main IEs:
[1]
RRC: Connection Release
Signalling Flow Info

List
Flow Identifier
08/11/16
157
Procedure
Part 2
RRC: Connection Release Complete (Unacknowledged)

Type: RRC
UE
Node B
RNC
MSC
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:

RRC: Connection Release
DCCH
Main IEs:
[1]
RRC: Connection Complete
Signalling Flow Info

List
Flow Identifier
08/11/16
158
Procedure
Part 2
NBAP: RL Deletion Request / Complete

Type: NBAP
UE
Node B
RNC
MSC
Purpose:
These messages
request and confirm
that the Radio Link
resources reserved in
the Node B for the
DCH be released.
Channels:
DCCH
Main IEs:
Node B
Communication
Context ID
Transaction ID

RRC: Release/Release Complete
NBAP: RL Deletion Request
NBAP: RL Del Complete
[1]
[2]
RL Information
RL ID
08/11/16
159
Procedure
Part 2
ALCAP: Release / Release Confirm

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 IEs:
Release Request
DSAID + Cause
Release Confirm
DSAID
08/11/16
UE
Node B
RNC
MSC

NBAP: RL Deletion/Complete
ALCAP: Release Request
ALCAP: Release Confirm
[1]
[2]
160
Procedure
Summary
Part 2
UE
Node B
RNC
MSC

NBAP: RL Deletion/Complete
ALCAP Release Procedure
08/11/16
161

UMTS Call Flow Scenarios

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UMTS Call Flow Scenarios

Caricato da

Copyright:

Formati disponibili

UMTS Call Flow Scenarios

UMTS Call Flow Scenarios

Node B Initialisation and System Information

UE Camp on and Location Update Procedure

UE Initiated CS Call Setup Procedure

UE Initiated CS Call Tear Down Procedure

UE Initiated PS Call Setup Procedure

UE Initiated PS Call Tear Down Procedure

Obligatory Stuff UTRAN Interfaces

Obligatory Stuff UTRAN Interfaces

Intra-NodeB Softer Handover

Intra-RNC Soft Handover

Inter-RNC Soft Handover

Basic Call Setup Purpose

If synchronisation status, dedicated traffic and

These are the parts of UTRAN that need to be

Using RED to denote configured and

This Presentation Contains Ladder Diagrams. . . .

Ladder Diagram Normal Procedure

View Presentation Request

You have been warned . . . .

Call Flow scenarios

Node B Initialisation and

UE Camp On & Location

Circuit Switched Calls

- UE initiated Call Set-Up

In this Procedure the UE is attached to the Network in Idle mode.

- UE initiated Call Set-Up

Message (1): Connection Request

- UE initiated Call Set-Up

Messages (2): Radio Link Set-up Request / Response

- UE initiated Call Set-Up

Messages (3): Establish Request (ERQ) / Confirm (ECF)

Destination address, DSAI,

- UE initiated Call Set-Up

Messages (4): DCH-FP DL / UL Synchronisation

- UE initiated Call Set-Up

Messages (5): Connection Set-up / Complete

RRC Conn. Setup

- UE initiated Call Set-Up

Messages (6): Initial Direct Transfer + Initial UE message

RRC Connection Setup

(CM Service Req.)

- UE initiated Call Set-Up

Messages (7): Connection Confirm + CM Service Accept

RRC Connection Setup

(CM Service Request)

SCCP Conn Conf

(CM Service Acc)

- UE initiated Call Set-Up

Messages (8): Authentication + Security Mode Commands

RRC Connection Setup

(CM Service Request)

(SCCP Con Req.)

SCCP Conn Conf

(CM Service Acc)

- UE initiated Call Set-Up

Identity, Authentication and Security Mode Commands

- UE initiated Call Set-Up

Identity Request Procedure: NAS: Identity Request

Type: NAS (PMM)

- UE initiated Call Set-Up

Identity, Authentication and Security Mode Commands

- UE initiated Call Set-Up