Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
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 a...
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 Procedu...
PART 1 - NODE B INITIALISATION
Procedure Overview1.2) Audit Procedure: Audit Request Message1.2) Audit Procedure: Audit Re...
PART 1 - NODE B INITIALISATION
Procedure Overview1.3) Audit Procedure: Audit Response Message1.3) Audit Procedure: Audit R...
PART 1 - NODE B INITIALISATION
Procedure Overview1.4) Cell Set-up Procedure: Resource Status Indication1.4) Cell Set-up Pr...
PART 1 - NODE B INITIALISATION
Procedure Overview1.5) Cell Set-up Procedure: Cell Set-up Request1.5) Cell Set-up Procedure...
PART 1 - NODE B INITIALISATION
Procedure Overview1.6) Cell Set-up Procedure: Cell Set-up Response1.6) Cell Set-up Procedur...
PART 1 - NODE B INITIALISATION
Procedure Overview1.7) Cell Set-up Procedure: Block Resource Request1.7) Cell Set-up Proced...
PART 1 - NODE B INITIALISATION
Procedure Overview1.8) Cell Set-up Procedure: Block Resource Response1.8) Cell Set-up Proce...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.9) System Information Broadcast Procedure:
System Information Update R...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.10) System Information Broadcast Procedure:
System Information is Broa...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.11) Common Transport Channel Set-up Procedure:
Common Transport Channe...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.12) Common Transport Channel Set-up Procedure:
Common Transport Channe...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.13) Common Transport Channel Set-up Procedure:
ALCAP Establish Request...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.14) Common Transport Channel Set-up Procedure:
ALCAP Establish Confirm...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.15) Common Transport Channel Set-up Procedure:
Synchronisation over RA...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.16) Common Transport Channel Set-up Procedure:
Common Transport Channe...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.17) Common Transport Channel Set-up Procedure:
Common Transport Ch. Se...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.18) Common Transport Channel Set-up Procedure:
ALCAP Establish Request...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.19) Common Transport Channel Set-up Procedure:
ALCAP Establish Confirm...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.20) Common Transport Channel Set-up Procedure:
Synchronisation over FA...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.21) Update System Information Procedure:
System Information Update Req...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.22) Update System Information Procedure:
Resource Status Indication (S...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.23) Update System Information Procedure:
Unblock Resource Indication M...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.24) Update System Information Procedure:
System Information Update Req...
PART 1 - NODE B INITIALISATION
Procedure Overview
1.25) Update System Information Procedure:
System Information Update Res...
PART 1 - NODE B INITIALISATION -
SUMMARY
UEUE
Node
B
Node
B
RNCRNC MSCMSC
Audit Request Procedure
CellSetup Procedure
Comm...
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 ...
PART 2 - UE LOCATION UPDATE
PROCEDURE
2.2) Location Update: Random Access Detection Procedure:
Access Preamble and AICH In...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Channels:
CCCH / RACH
Main IE’s:
› Initial UE ID
› Establishment Cause
› I...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Procedure Overview
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: NBAP
Purpose:
RNC tells Nod...
PART 2 - UE LOCATION UPDATE
PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: ALCAP
Purpose:
This message sequence
requests ...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Procedure Overview
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: DCH-FP
Purpose:
Framing Pro...
PART 2 - UE LOCATION UPDATE
PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSCType: RRC
Purpose
RNC informs the UE that the
DCH ch...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose
UE initiates a location
update procedure
Channels:
DCCH
Main IE’s:...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
RNC relays the
Location Update
message to the
NAS at the CN
Cha...
UEUE
Node
B
Node
B
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: MAP
Purpos...
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNCUEUE
Node
B
Node
B
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: MAP
Purpose...
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
If the CN deci...
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
The RNC forwards...
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
The UE must be
p...
MSC/
VLR
MSC/
VLR
P-
MSC/
VLR
P-
MSC/
VLR
RNCRNC
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
The RNC relays...
RNCRNC MSCMSCUEUE
Node
B
Node
B
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP &
RRC
Purpose:
The CN may now elect to
i...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs
Type: RANAP
Purpose:
Channels:
DCCH
Mai...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IEs:
Type: RANAP
Purpose:
Channels:
DCCH
Ma...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
M...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
M...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
Type: RRC
Purpose:
Channels:
DCCH
Main ...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
Channels:
DCCH
Main IE’s:
Type: RRC
Purpose:
Channels:
DCCH
Main ...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RANAP
Purpose:
Channels:
DCCH
Main IE’s:
Type: RANAP
Purpose:
Channels:
DCCH
M...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
This message
originates in the RNC
and informs the UE
that the DC...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: RRC
Purpose:
This message
originates in the UE
and informs the RNC
that the DC...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: NBAP
Purpose:
These messages
request and confirm
that the Radio Link
resources...
PART 2 - UE LOCATION UPDATE
PROCEDURE
Type: ALCAP
Purpose:
These messages
request and confirm
that the AAL2 bearer
over th...
PART 2 - UE LOCATION UPDATE
PROCEDURE
UEUE
Node
B
Node
B
RNCRNC MSCMSC
ALCAP Release Procedure
Summary
Random Access Detec...
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...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessage (1): Connection RequestMessage (1): Connection Request
Ty...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (2): Radio Link Set-up Request / ResponseMessages (2): R...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (3): Establish Request (ERQ) / Confirm (ECF)Messages (3)...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (4): DCH-FP DL / UL SynchronisationMessages (4): DCH-FP ...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (5): Connection Set-up / CompleteMessages (5): Connectio...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (6): Initial Direct Transfer + Initial UE messageMessage...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (7): Connection Confirm + CM Service AcceptMessages (7):...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (8): Authentication + Security Mode CommandsMessages (8)...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Auth...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewIdentity Request Procedure: NAS: Identity RequestIdentity Request...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Auth...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Auth...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (9): Common IDMessages (9): Common ID
Type:
1. RANAP
Mai...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (10): Call Setup + Call ProceedingMessages (10): Call Se...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (11): RAB Assignment Request + Iucs ALCAP SetupMessages ...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure Overview
Messages (12): RL Reconfigure Prepare / ReadyMessages (12): RL R...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (13): RAB - Iub Establish Request / ConfirmMessages (13)...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (14): RAB - Iucs Establish Request / ConfirmMessages (14...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (15): RAB - Radio Bearer Setup / CompleteMessages (15): ...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (16): RAB Assignment ResponseMessages (16): RAB Assignme...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (17): Call ConnectMessages (17): Call Connect
Type:
1. R...
PART 3 - UE INITIATED CALL SET-UP
(CS)
Procedure OverviewMessages (18): Connect / Connect AcknowledgeMessages (18): Connec...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure Overview.
In this Procedure the UE is attached to the Network in Call...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (1): CC: DisconnectMessages (1): CC: Disconnect
Type...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (2): CC: Release + Release CompleteMessages (2): CC:...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessage (3): Iu Release CommandMessage (3): Iu Release Comman...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (4): RAB - Release Request / Confirm (Iucs)Messages ...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (5): RRC - Connection Release / CompleteMessages (5)...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (6): RL Deletion Request / ResponseMessages (6): RL ...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (7): RAB - Release Request / Confirm (Iub)Messages (...
PART 4 - UE INITIATED CALL TEAR-
DOWN (CS)
Procedure OverviewMessages (7): CS Call Tear Down CompleteMessages (7): CS Call...
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...
PART 5 - UE INITIATED CALL SET-UP
(PS)Check Point One
UE Detached – No PDP Contexts
UEUE
Node
B
Node
B
RNCRNC SGSNSGSN GGS...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewRRC Connection Set-Up: RRC: RRC Connection RequestRRC Connection ...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewRRC Connection Set-Up: NBAP: Radio Link Set-up Request / Response...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewRRC Connection Set-Up: ALCAP: Establish Request / ConfirmRRC Conn...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewRRC Connection Set-Up: FP: DL / UL SynchronisationRRC Connection ...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewRRC Connection Set-Up: RRC: Connection Set-up / CompleteRRC Conne...
PART 5 - UE INITIATED CALL SET-UP
(PS)Check Point Two
UE Detached – No PDP Contexts – RRC Connected
UEUE
Node
B
Node
B
RNC...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : RRC: Initial Direct Transfer + RANAP: Initial UE mes...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : PMM: Attach RequestPMM Attach : PMM: Attach Request
...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : SCCP: Connection ConfirmPMM Attach : SCCP: Connectio...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : RANAP / RRC: Authentication + Security ModePMM Attac...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewIdentity Request Procedure: NAS: Identity RequestIdentity Request...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Auth...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Auth...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : RANAP: Common IDPMM Attach : RANAP: Common ID
Descri...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : PMM: Attach AcceptPMM Attach : PMM: Attach Accept
De...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPMM Attach : PMM: Attach CompletePMM Attach : PMM: Attach Complet...
PART 5 - UE INITIATED CALL SET-UP
(PS)Check Point Three
UE Attached – No PDP Contexts – RRC Connected
UEUE
Node
B
Node
B
R...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: SM: Activate PDP Context RequestPDP Conte...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: RANAP: RAB Assignment RequestPDP Context ...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: NBAP: RL Reconfigure Prepare / ReadyPDP C...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: ALCAP: AAL2 Bearer Set-UpPDP Context Acti...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: NBAP: RL Reconfigure CommitPDP Context Ac...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: RRC: Radio Bearer Set-UpPDP Context Activ...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: RRC: Radio Bearer Set-Up CompletePDP Cont...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: RANAP: RAB Assignment ResponsePDP Context...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: GTP-C: Create PDP Context RequestPDP Cont...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: GTP-C: Create PDP Context ResponsePDP Con...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: SM: Activate PDP Context AcceptPDP Contex...
PART 5 - UE INITIATED CALL SET-UP
(PS)
Procedure OverviewPDP Context Activation: Procedure CompletePDP Context Activation:...
PART 5 - UE INITIATED CALL SET-UP
(PS)Check Point Four
UE Attached – One PDP Context
UE State: RRC Connected PMM Attached ...
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
UMTS UTRAN Call Flow
Upcoming SlideShare
Loading in …5
×

UMTS UTRAN Call Flow

It discusses about the 3G call flow scenarios for both the Circuit Switched (CS) and Packet Switched (PS). Calls are mobile originated. Call making and call tear down both are discussed.

  • Login to see the comments

UMTS UTRAN Call Flow

  1. 1. UMTS Call Flow Scenarios An Overview of Circuit and Packet Call Flow Scenarios
  2. 2. UTRAN INTERFACES MSC SGSN RNC RNC Node BNode B UE Iu-psIu-cs Iu-r Iu-b Uu Iu-b Cell
  3. 3. 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
  4. 4. PART 1 Node B Initialization and Cell “Camp on”
  5. 5. 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]
  6. 6. PART 1 - NODE B INITIALISATION 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 Audit Required Indication [1]
  7. 7. PART 1 - NODE B INITIALISATION 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 Audit Required Indication [1]
  8. 8. PART 1 - NODE B INITIALISATION 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 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 Resource Status Indication UEUE Node B Node B RNCRNC MSCMSC Audit Request Procedure [1]
  9. 9. PART 1 - NODE B INITIALISATION 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 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 › Cell & Local Cell ID › Scrambling Codes › Sync and Power Info 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 › Cell & Local Cell ID › Scrambling Codes › Sync and Power Info Cell Setup Request UEUE Node B Node B RNCRNC MSCMSC Resource Status Indication [1] Audit Request Procedure
  10. 10. PART 1 - NODE B INITIALISATION 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 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 › Cell Setup Success 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 › Cell Setup Success UEUE Node B Node B RNCRNC MSCMSC Cell Set-Up Response Cell Setup Request Resource Status Indication [1] Audit Request Procedure
  11. 11. PART 1 - NODE B INITIALISATION 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 Set-Up Response Cell Setup Request Resource Status Indication Block Resource Request [1] Audit Request Procedure
  12. 12. PART 1 - NODE B INITIALISATION 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 Set-Up Response Cell Setup Request Resource Status Indication Block Resource Request Block Resource Response [1] Audit Request Procedure
  13. 13. PART 1 - NODE B INITIALISATION Procedure Overview 1.9) System Information Broadcast Procedure: System Information Update Request and Response 1.9) System Information Broadcast Procedure: 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 System Info Update Req. Segment 2 System Info Update Resp. Segment 2 System Info Update Req. Segment 3 System Info Update Resp. Segment 3 . . etc [1] [2] [3] [4] [5] [6] Audit Request Procedure
  14. 14. PART 1 - NODE B INITIALISATION Procedure Overview 1.10) System Information Broadcast Procedure: System Information is Broadcast for each cell 1.10) System Information Broadcast Procedure: 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 Cell Setup Procedure System Info Update Resp. Segment 1 System Info Update Req. Segment 2 System Info Update Resp. Segment 2 System Info Update Req. Segment 3 System Info Update Resp. Segment 3 . . etc System Info Update Req. Segment 1 [1] [2] [3] Audit Request Procedure
  15. 15. PART 1 - NODE B INITIALISATION Procedure Overview 1.11) Common Transport Channel Set-up Procedure: Common Transport Channel Set-up Request (PRACH, AICH, RACH) 1.11) Common Transport Channel Set-up Procedure: 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 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) UEUE Node B Node B RNCRNC MSCMSC System Information Update Common Transport CH Set-Up Request Cell Setup Procedure Audit Request Procedure [1]
  16. 16. PART 1 - NODE B INITIALISATION Procedure Overview 1.12) Common Transport Channel Set-up Procedure: Common Transport Channel Set-up Response (PRACH, AICH, RACH) 1.12) Common Transport Channel Set-up Procedure: 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: 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 UEUE Node B Node B RNCRNC MSCMSC Common Transport CH Set-Up Response Common Transport CH Set-Up Request System Information Update Cell Setup Procedure Audit Request Procedure [1]
  17. 17. PART 1 - NODE B INITIALISATION Procedure Overview 1.13) Common Transport Channel Set-up Procedure: ALCAP Establish Request (with Binding ID for RACH) 1.13) Common Transport Channel Set-up Procedure: 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 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 UEUE Node B Node B RNCRNC MSCMSC Common Transport CH Set-Up Response Common Transport CH Set-Up Request ALCAP ERQ System Information Update Cell Setup Procedure Audit Request Procedure [1]
  18. 18. PART 1 - NODE B INITIALISATION Procedure Overview 1.14) Common Transport Channel Set-up Procedure: ALCAP Establish Confirm 1.14) Common Transport Channel Set-up Procedure: ALCAP Establish Confirm Type: ALCAP Purpose: This message confirms the establishment of an AAL2 path over the IuB interface for the RACH. Main IE’s: › OSAID + DSAID Type: ALCAP Purpose: This message confirms the establishment of an AAL2 path over the IuB interface for the RACH. 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 System Information Update Cell Setup Procedure Audit Request Procedure [1]
  19. 19. PART 1 - NODE B INITIALISATION Procedure Overview 1.15) Common Transport Channel Set-up Procedure: Synchronisation over RACH -FP (Framing Protocol) 1.15) Common Transport Channel Set-up Procedure: 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 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. 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 System Information Update Cell Setup Procedure Audit Request Procedure [1] [2]
  20. 20. PART 1 - NODE B INITIALISATION Procedure Overview 1.16) Common Transport Channel Set-up Procedure: Common Transport Channel Set-up Request (S-CCPCH, FACH, PCH) 1.16) Common Transport Channel Set-up Procedure: Common Transport Channel Set-up Request (S-CCPCH, FACH, PCH) Type: NBAP Purpose: Common Transport Channels are set up in 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 Channels are set up in 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 System Information Update Cell Setup Procedure Audit Request Procedure [1]
  21. 21. PART 1 - NODE B INITIALISATION Procedure Overview 1.17) Common Transport Channel Set-up Procedure: Common Transport Ch. Set-up Response (S-CCPCH, FACH, PCH) 1.17) Common Transport Channel Set-up Procedure: Common Transport Ch. Set-up Response (S-CCPCH, FACH, PCH) Type: NBAP Purpose: The Node B Ack’s the 2nd Com Trans Setup msg which established the FACH, PCH & S- CCPCH Main IE’s: for PCH and FACH › Binding and Com ID › Transport layer address Type: NBAP Purpose: The Node B Ack’s the 2nd Com Trans Setup msg which established the FACH, PCH & S- CCPCH Main IE’s: for PCH and FACH › Binding and Com ID › Transport layer address UEUE Node B Node B RNCRNC MSCMSC Common Transport CH Set-Up Response Common Transport CH Set-Up Request System Information Update Cell Setup Procedure Audit Request Procedure Common Transport Setup Procedures: PRACH, AICH and RACH + ALCAP for RACH [1]
  22. 22. PART 1 - NODE B INITIALISATION Procedure Overview 1.18) Common Transport Channel Set-up Procedure: ALCAP Establish Request (with Binding ID for FACH and PCH) 1.18) Common Transport Channel Set-up Procedure: 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: › OSAID, DSAID + CEID, › 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: › OSAID, DSAID + CEID, › 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 System Information Update Cell Setup Procedure Audit Request Procedure Common Transport Setup Procedures: PRACH, AICH and RACH + ALCAP for RACH [1]
  23. 23. PART 1 - NODE B INITIALISATION Procedure Overview 1.19) Common Transport Channel Set-up Procedure: ALCAP Establish Confirm (FACH and PCH) 1.19) Common Transport Channel Set-up Procedure: ALCAP Establish Confirm (FACH and PCH) Type: ALCAP Purpose: This message confirms the establishment of an AAL2 path over the IuB 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 AAL2 path over the IuB 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 System Information Update Cell Setup Procedure Audit Request Procedure Common Transport Setup Procedures: PRACH, AICH and RACH + ALCAP for RACH [1]
  24. 24. PART 1 - NODE B INITIALISATION Procedure Overview 1.20) Common Transport Channel Set-up Procedure: Synchronisation over FACH - FP and PCH-FP(Framing Protocol) 1.20) Common Transport Channel Set-up Procedure: Synchronisation over FACH - FP and PCH-FP(Framing Protocol) Type: FACH-FP Purpose: Framing Protocol Synchronisation messages are used to establish precise timing 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: › Control messages contain time stamps to establish the time the message was sent and when it arrived at the opposite node. Type: FACH-FP Purpose: Framing Protocol Synchronisation messages are used to establish precise timing 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: › Control messages contain time stamps to establish the time the message was sent and when it arrived at the opposite node. UEUE Node B Node B RNCRNC MSCMSC ALCAP ERQ Common Transport CH Set-Up Response Common Transport CH Set-Up Request FP DL Synchronisation FP UL Synchronisation System Information Update Cell Setup Procedure Audit Request Procedure Common Transport Setup Procedures: PRACH, AICH and RACH + ALCAP for RACH ALCAP ECF [1] [2]
  25. 25. PART 1 - NODE B INITIALISATION Procedure Overview 1.21) Update System Information Procedure: System Information Update Request (SIB 5 - Channel Updates) 1.21) Update System Information Procedure: 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 System Info Update Req. SIB 5 UEUE Node B Node B RNCRNC MSCMSC Common Transport Setup Procedures: PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FP-Sync. for RACH, FACH and PCH System Information Update Cell Setup Procedure Audit Request Procedure [1]
  26. 26. PART 1 - NODE B INITIALISATION Procedure Overview 1.22) Update System Information Procedure: Resource Status Indication (Service impacting, com ctrl port enabled) 1.22) Update System Information Procedure: 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 Common Transport Setup Procedures: PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FP-Sync. for RACH, FACH and PCH System Information Update Cell Setup Procedure Audit Request Procedure System Info Update Req. SIB 5 Resource Status Indication [1]
  27. 27. PART 1 - NODE B INITIALISATION Procedure Overview 1.23) Update System Information Procedure: Unblock Resource Indication Message 1.23) Update System Information Procedure: 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 Common Transport Setup Procedures: PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FP-Sync. for RACH, FACH and PCH System Information Update Cell Setup Procedure Audit Request Procedure System Info Update Req. SIB 5 Resource Status Indication Unblock Resource Ind [1]
  28. 28. PART 1 - NODE B INITIALISATION Procedure Overview 1.24) Update System Information Procedure: System Information Update Request (SIB 3 - Cell Unblocked) 1.24) Update System Information Procedure: 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: The RNC updates SIB3 to “Unbarred” Main IE’s: › Cell ID › Transaction ID › SIB 3 Updated to unbarred UEUE Node B Node B RNCRNC MSCMSC Common Transport Setup Procedures: PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FP-Sync. for RACH, FACH and PCH System Information Update Cell Setup Procedure Audit Request Procedure System Info Update Req. SIB 5 Resource Status Indication Unblock Resource Ind System Info Update Req. SIB 3 [1]
  29. 29. PART 1 - NODE B INITIALISATION Procedure Overview 1.25) Update System Information Procedure: System Information Update Response 1.25) Update System Information Procedure: System Information Update Response Type: NBAP Purpose: The RNC updates SIB3 to “Unbarred” Main IE’s: › Transaction ID Type: NBAP Purpose: The RNC updates SIB3 to “Unbarred” Main IE’s: › Transaction ID UEUE Node B Node B RNCRNC MSCMSC Common Transport Setup Procedures: PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FP-Sync. for RACH, FACH and PCH System Information Update Cell Setup Procedure Audit Request Procedure System Info Update Req. SIB 5 Resource Status Indication Unblock Resource Ind System Info Update Req. SIB 3 System Info Update Resp. [1]
  30. 30. PART 1 - NODE B INITIALISATION - SUMMARY UEUE Node B Node B RNCRNC MSCMSC Audit Request Procedure 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 System Information Update Request - SIB 5 Update Resources and Unblock Cell System Information Update Request - SIB 3
  31. 31. PART 2 UE “Camp On” & Location Update
  32. 32. 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]
  33. 33. PART 2 - UE LOCATION UPDATE 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
  34. 34. PART 2 - UE LOCATION UPDATE 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 2.3) Location Update: Radio Signalling Bearer Establish Procedure: RRC: Connection Request Message Random Access Detection [1]
  35. 35. PART 2 - UE LOCATION UPDATE 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 › DL Channelisation Code › 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 › DL Channelisation Code › Power Control Info › RL Setup Response › Transport Layer Add › Sig. Link termination › DL Channelisation Code › DCH Binding ID RL Setup Request RL Setup Response 2.4) Location Update: Radio Signalling Bearer Establish Procedure: RL Set-up Request and RL Set-up Response Messages 2.4) Location Update: Radio Signalling Bearer Establish Procedure: RL Set-up Request and RL Set-up Response Messages Random Access Detection RRC Connection Request (PRACH) [1] [2]
  36. 36. PART 2 - UE LOCATION UPDATE PROCEDURE UEUE Node B Node B RNCRNC MSCMSCType: ALCAP Purpose: This message sequence requests (and confirms) the establishment of an AAL2 path over the IuB 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 Main IE’s: › OSAID, DSAID + CEID, › SUGR, › AAL2 Destination Address of Node B Type: ALCAP Purpose: This message sequence requests (and confirms) the establishment of an AAL2 path over the IuB 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 Main IE’s: › OSAID, DSAID + CEID, › SUGR, › AAL2 Destination Address of Node B Random Access Detection 2.5) Location Update: Radio Signalling Bearer Establish Procedure: Establish Request (ERQ) and Confirm (ECF) Messages 2.5) Location Update: Radio Signalling Bearer Establish Procedure: Establish Request (ERQ) and Confirm (ECF) Messages RL Setup Request RL Setup Response RRC Connection Request (PRACH) ALCAP ERQ ALCAP ECF [1] [2]
  37. 37. PART 2 - UE LOCATION UPDATE PROCEDURE Procedure Overview UEUE Node B Node B RNCRNC MSCMSCType: DCH-FP Purpose: Framing Protocol Synchronisation messages are used to establish precise timing between the Node B and RNC for each channel. There will be separate sync. procedures for all CCCH and DCCH channels. 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: DCH-FP Purpose: Framing Protocol Synchronisation messages are used to establish precise timing between the Node B and RNC for each channel. There will be separate sync. procedures for all CCCH and DCCH channels. Main IE’s: › Control messages contain time stamps to establish the time the message was sent and when it arrived at the opposite node. Random Access Detection 2.6) Location Update: Radio Signalling Bearer Establish Procedure: DCH-FP DL / UL Synchronisation Messages 2.6) Location Update: Radio Signalling Bearer Establish Procedure: DCH-FP DL / UL Synchronisation Messages FP DL Synchronisation FP UL Synchronisation RL Setup Request RL Setup Response RRC Connection Request (PRACH) ALCAP ERQ ALCAP ECF [1] [2]
  38. 38. PART 2 - UE LOCATION UPDATE 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) Random Access Detection 2.7) Location Update: Radio Signalling Bearer Establish Procedure: RRC Connection Set-up / Complete Messages 2.7) Location Update: Radio Signalling Bearer Establish Procedure: RRC Connection Set-up / Complete Messages FP DL Synchronisation FP UL Synchronisation RL Setup Request RL Setup Response RRC Connection Request (PRACH) ALCAP ERQ ALCAP ECF [1] [2]
  39. 39. PART 2 - UE LOCATION UPDATE 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: › Update Type (normal) › Cipher Key Seq No. › Location Area Info › 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] 2.8) Location Update: Location Update Request Procedure: RRC: Initial DT [NAS Location Update Request Message] Random Access Detection RRC: Initial Direct Transfer (Location Update Request) [1]
  40. 40. PART 2 - UE LOCATION UPDATE PROCEDURE Type: RANAP Purpose: RNC relays the Location Update message to the NAS at the CN Channels: DCCH Main IE’s: › Update Type (normal) › Cipher Key Seq No. › Location Area Info › 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: › Update Type (normal) › Cipher Key Seq No. › Location Area Info › UE Classmark › UE ID (IMSI/TMSI) UEUE Node B Node B RNCRNC MSCMSC RANAP: DT (Location Upd Request) 2.9) Location Update: Location Update Request Procedure: RANAP: DT [NAS Location Update Request Message] 2.9) Location Update: Location Update Request Procedure: RANAP: DT [NAS Location Update Request Message] Random Access Detection Radio Signalling Bearer Establishment Procedure RRC: Initial Direct Transfer (Location Update Request) [1]
  41. 41. UEUE Node B Node B MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNC PART 2 - UE LOCATION UPDATE 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: 2.10) Location Update: Location Update Request Procedure: MAP Send_Identification Request 2.10) Location Update: Location Update Request Procedure: MAP Send_Identification Request Random Access Detection Radio Signalling Bearer Establishment Procedure MAP Send ID Req. RANAP: DT Loc. Upd Req RRC: Initial Direct Transfer (Location Update Request) [1]
  42. 42. MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNCUEUE Node B Node B PART 2 - UE LOCATION UPDATE 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: 2.11) Location Update: Location Update Request Procedure: MAP Send_Identification Acknowledge 2.11) Location Update: Location Update Request Procedure: MAP Send_Identification Acknowledge Random Access Detection Radio Signalling Bearer Establishment Procedure MAP Send ID Ack MAP Send ID Req. RANAP: DT Loc. Upd Req. RRC: Initial Direct Transfer (Location Update Request) [1]
  43. 43. MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNC PART 2 - UE LOCATION UPDATE 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] 2.12) Location Update: Identity Request Procedure: RANAP: Direct Transfer [NAS Identity Request Message] Random Access Detection Radio Signalling Bearer Establishment Procedure RANAP: DT NAS: Identity Req. MAP Send ID Ack MAP Send ID Req. RANAP: DT Loc. Upd Req. RRC: Initial Direct Transfer (Location Update Request) [1]
  44. 44. MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNC PART 2 - UE LOCATION UPDATE 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 2.13) Location Update: Identity Request Procedure: RRC: Direct Transfer [NAS Identity Request Message] 2.13) Location Update: Identity Request Procedure: RRC: Direct Transfer [NAS Identity Request Message] Random Access Detection Radio Signalling Bearer Establishment Procedure RANAP: DT NAS: Identity Req.RRC: DT DCCH NAS: Identity Request MAP Send ID Ack MAP Send ID Req. RANAP: DT Loc. Upd Req. RRC: Initial Direct Transfer (Location Update Request) [1]
  45. 45. MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNC PART 2 - UE LOCATION UPDATE 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 2.14) Location Update: Identity Request Procedure: RRC: Direct Transfer [NAS Identity Response Message] 2.14) Location Update: Identity Request Procedure: RRC: Direct Transfer [NAS Identity Response Message] Random Access Detection Radio Signalling Bearer Establishment Procedure RRC: DT DCCH NAS: Identity Response RANAP: DT NAS: Identity Req.RRC: DT DCCH NAS: Identity Request MAP Send ID Ack MAP Send ID Req. RANAP: DT Loc. Upd Req. RRC: Initial Direct Transfer (Location Update Request) [1]
  46. 46. MSC/ VLR MSC/ VLR P- MSC/ VLR P- MSC/ VLR RNCRNC PART 2 - UE LOCATION UPDATE 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 2.15) Location Update: Identity Request Procedure: RANAP: Direct Transfer [NAS Identity Response Message] 2.15) Location Update: Identity Request Procedure: RANAP: Direct Transfer [NAS Identity Response Message] Random Access Detection Radio Signalling Bearer Establishment Procedure 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: Initial Direct Transfer (Location Update Request) RRC: DT DCCH NAS: Identity Request [1]
  47. 47. RNCRNC MSCMSCUEUE Node B Node B PART 2 - UE LOCATION UPDATE 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] 2.16) Location Update: Authentication Procedure: RANAP: Direct Transfer [NAS Authentication Request Message] Random Access Detection Radio Signalling Bearer Establishment Procedure RANAP: DT NAS: Auth. Request Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional [1]
  48. 48. PART 2 - UE LOCATION UPDATE PROCEDURE Type: RANAP Purpose: Channels: DCCH Main IEs Type: RANAP Purpose: Channels: DCCH Main IEs UEUE Node B Node B RNCRNC MSCMSC 2.17) Location Update: Authentication Procedure: RRC: Direct Transfer [NAS Authentication Request Message] 2.17) Location Update: Authentication Procedure: RRC: Direct Transfer [NAS Authentication Request Message] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional RRC: DT DCCH NAS: Auth Request RANAP: DT NAS: Auth Request[1]
  49. 49. PART 2 - UE LOCATION UPDATE PROCEDURE Type: RANAP Purpose: Channels: DCCH Main IEs: Type: RANAP Purpose: Channels: DCCH Main IEs: UEUE Node B Node B RNCRNC MSCMSC 2.18) Location Update: Authentication Procedure: RRC: Direct Transfer [NAS Authentication Response Message] 2.18) Location Update: Authentication Procedure: RRC: Direct Transfer [NAS Authentication Response Message] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional RRC: DT DCCH NAS: Auth Request RANAP: DT NAS: Auth Request RRC: DT DCCH NAS: Auth Response [1]
  50. 50. PART 2 - UE LOCATION UPDATE PROCEDURE Type: RANAP Purpose: Channels: DCCH Main IE’s: Type: RANAP Purpose: Channels: DCCH Main IE’s: UEUE Node B Node B RNCRNC MSCMSC 2.19) Location Update: Authentication Procedure: RANAP: DT [NAS Authentication Response Message] 2.19) Location Update: Authentication Procedure: RANAP: DT [NAS Authentication Response Message] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional RRC: DT DCCH NAS: Auth Request RANAP: DT NAS: Auth Request RRC: DT DCCH NAS: Auth Response RANAP: DT NAS: Auth Response [1]
  51. 51. PART 2 - UE LOCATION UPDATE 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] 2.20) Location Update: Location Update Accept Procedure: RANAP: Direct Transfer [NAS Location Update Accept Message] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional [1]
  52. 52. PART 2 - UE LOCATION UPDATE 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 Location Update Accept 2.21) Location Update: Location Update Accept Procedure: RRC: Direct Transfer [NAS Location Update Accept Message] 2.21) Location Update: Location Update Accept Procedure: RRC: Direct Transfer [NAS Location Update Accept Message] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional RANAP: DT Location Update Accept [1]
  53. 53. PART 2 - UE LOCATION UPDATE 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] 2.22) Location Update: TMSI Reallocation Complete Procedure: RRC: Direct Transfer [NAS TMSI Reallocation Complete] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional RRC: DT Location Update Accept RANAP: DT Location Update Accept [1]
  54. 54. PART 2 - UE LOCATION UPDATE 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 2.23) Location Update: TMSI Reallocation Complete Procedure: RANAP: Direct Transfer [NAS TMSI Reallocation Complete] 2.23) Location Update: TMSI Reallocation Complete Procedure: RANAP: Direct Transfer [NAS TMSI Reallocation Complete] Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional RRC: DT TMSI Reallocation Complete RRC: DT Location Update Accept RANAP: DT Location Update Accept [1]
  55. 55. PART 2 - UE LOCATION UPDATE 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: › Signalling Flow Info 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) 2.24) Location Update: Radio Signalling Bearer Release Procedure: RRC: Connection Release (Unacknowledged) Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional RRC: Connection Release [1]
  56. 56. PART 2 - UE LOCATION UPDATE 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: › Signalling Flow Info 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: › Signalling Flow Info List › Flow Identifier UEUE Node B Node B RNCRNC MSCMSC 2.25) Location Update: Radio Signalling Bearer Release Procedure: RRC: Connection Release Complete (Unacknowledged) 2.25) Location Update: Radio Signalling Bearer Release Procedure: RRC: Connection Release Complete (Unacknowledged) Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional Location Update Accept Procedure (RRC/RANAP DT) TMSI Reallocation Complete Procedure (RRC/RANAP DT) RRC: Connection Complete RRC: Connection Release [1]
  57. 57. PART 2 - UE LOCATION UPDATE 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 2.26) Location Update: Radio Signalling Bearer Release Procedure: NBAP: RL Deletion Request / Complete 2.26) Location Update: Radio Signalling Bearer Release Procedure: NBAP: RL Deletion Request / Complete Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional Location Update Accept Procedure (RRC/RANAP DT) TMSI Reallocation Complete Procedure (RRC/RANAP DT) RRC: Release/Release Complete [1] [2]
  58. 58. PART 2 - UE LOCATION UPDATE 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 RRC: Release/Release Complete 2.27) Location Update: Radio Signalling Bearer Release Procedure: ALCAP: Release / Release Confirm 2.27) Location Update: Radio Signalling Bearer Release Procedure: ALCAP: Release / Release Confirm Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional Location Update Accept Procedure (RRC/RANAP DT) TMSI Reallocation Complete Procedure (RRC/RANAP DT) NBAP: RL Deletion/Complete ALCAP: Release Request ALCAP: Release Confirm [1] [2]
  59. 59. PART 2 - UE LOCATION UPDATE PROCEDURE UEUE Node B Node B RNCRNC MSCMSC ALCAP Release Procedure Summary Random Access Detection Radio Signalling Bearer Establishment Procedure Location Update Request Procedure (RRC/RANAP DT) Identity Request Procedure (RRC/RANAP DT) Optional Authentication Request Procedure (RRC/RANAP DT) Optional Location Update Accept Procedure (RRC/RANAP DT) TMSI Reallocation Complete Procedure (RRC/RANAP DT) RRC: Release/Release Complete NBAP: RL Deletion/Complete
  60. 60. PARTS 3 - 4 Circuit Switched Calls Parts 3 & 4 Call Setup and Tear Down Scenarios
  61. 61. 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
  62. 62. PART 3 - UE INITIATED CALL SET-UP (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 Initial UE capability UEUE Node B Node B RNCRNC MSCMSC RRC Connection Request (RACH) [1] MSC RNC NB UE UTRAN Status
  63. 63. PART 3 - UE INITIATED CALL SET-UP (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 DL Channelisation Code DCH Binding ID Type: 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 DL Channelisation Code DCH Binding ID NBAP RL setup Req. NBAP RL setup Resp. RRC Connection Request (RACH) [1] [2] MSC RNC NB UE UTRAN Status
  64. 64. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Request (RACH) [1] [2] MSC RNC NB UE UTRAN Status
  65. 65. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Request (RACH) FP DL Synchronisation FP UL Synchronisation NBAP RL setup Req. NBAP RL setup Resp. [1] [2] MSC RNC NB UE UTRAN Status
  66. 66. PART 3 - UE INITIATED CALL SET-UP (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: 1. Initial UE ID, RNTI, CapUpReq, TFS, TFCS, frequ, DL Scram + Chann codes, Power control info. 2. UE Capability, Ciphering, Integrity info RRC Connection Request (RACH) FP DL Synchronisation FP UL 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
  67. 67. PART 3 - UE INITIATED CALL SET-UP (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.) RRC Connection Setup [1] [2] MSC RNC NB UE UTRAN Status
  68. 68. PART 3 - UE INITIATED CALL SET-UP (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 Connection Setup RRC DL DT (OPT) (CM Service Acc) RANAP DT (CM Service Acc) SCCP Conn Conf [1] [2] [3] MSC RNC NB UE UTRAN Status
  69. 69. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Setup (CM Service Request) Authentication RRC Security Mode Command RANAP Security Mode Command 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
  70. 70. PART 3 - UE INITIATED CALL SET-UP (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
  71. 71. PART 3 - UE INITIATED CALL SET-UP (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; [IMSI, IMEI, IEMISV, TMSI] Main IE’s: Req: Identity Request Type Res: Mobile Identity 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; [IMSI, IMEI, IEMISV, TMSI] Main IE’s: Req: Identity Request Type Res: Mobile Identity UEUE Node B Node B RNCRNC MSCMSC Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC UL D T (Identity Response.) RANAP DT (Identity Request)
  72. 72. PART 3 - UE INITIATED CALL SET-UP (CS) Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Authentication and Security Mode Commands 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 Network Authentication Integrity Key exchange Ciphering Key Exchange Main IE’s: Req: CK Sequence Number RAND AUTN Res: CK Sequence Number RES UEUE Node B Node B RNCRNC MSCMSC Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC UL D T (Identity Response.) RANAP DT (Identity Request) RRC DL DT (Authentication Request) RANAP DT (Authentication Request) RRC UL D T (Authentication Response) RANAP DT (Authentication Response)
  73. 73. PART 3 - UE INITIATED CALL SET-UP (CS) Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Authentication and Security Mode Commands 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: 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 UEUE Node B Node B RNCRNC MSCMSC Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC Initial D T (Identity Response.) RANAP DT (Identity Request) RRC DL DT (Authentication Request) RANAP DT (Authentication Request) RRC UL D T (Authentication Response) RANAP DT (Authentication Response)
  74. 74. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Setup (CM Service Request) Authentication RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete 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
  75. 75. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Setup 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
  76. 76. PART 3 - UE INITIATED CALL SET-UP (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 3. CEID, Destination address, 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 2. CEID, Destination address, DSAID, OSAID 3. CEID, Destination address, DSAID, OSAID UEUE Node B Node B RNCRNC MSCMSC RRC Connection Setup Service Request / Authentication / Security RRC DL DT (Call Proceeding) RRC UL DT (Call Setup) RANAP DT (Call Setup) RANAP DT (Call Proceeding) RANAP RAB Assignment Req. ALCAP ERQ ALCAP ECF [1] [2] [3] MSC RNC NB UE UTRAN Status
  77. 77. PART 3 - UE INITIATED CALL SET-UP (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 Connection Setup Service Request / Authentication / Security RRC DL DT (Call Proceeding) RRC UL DT (Call Setup) RANAP 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
  78. 78. PART 3 - UE INITIATED CALL SET-UP (CS) Procedure OverviewMessages (13): RAB - Iub Establish Request / ConfirmMessages (13): RAB - Iub Establish Request / Confirm Type: 1. ALCAP 2. ALCAP Main IE’s: 1. CEID, Destination address, DSAID, OSAID 2. CEID, Destination address, DSAID, OSAID Type: 1. ALCAP 2. ALCAP Main IE’s: 1. CEID, Destination address, DSAID, OSAID 2. CEID, Destination address, 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
  79. 79. PART 3 - UE INITIATED CALL SET-UP (CS) Procedure OverviewMessages (14): RAB - Iucs Establish Request / ConfirmMessages (14): RAB - Iucs Establish Request / Confirm Type: 1. ALCAP 2. ALCAP Main IE’s: 1. CEID, Destination address, DSAID, OSAID 2. CEID, Destination address, DSAID, OSAID Type: 1. ALCAP 2. ALCAP Main IE’s: 1. CEID, Destination address, DSAID, OSAID 2. CEID, Destination address, DSAID, OSAID UEUE Node B Node B RNCRNC MSCMSC Continued from NBAP RL Reconfigure Procedure ALCAP ERQ ALCAP ECF NBAP RL Reconfigure Commit [1] MSC RNC NB UE UTRAN Status
  80. 80. PART 3 - UE INITIATED CALL SET-UP (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 RL Reconfigure Commit Continued from NBAP RL Reconfigure Procedure [1] [2] MSC RNC NB UE UTRAN Status
  81. 81. PART 3 - UE INITIATED CALL SET-UP (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 RRC Radio Bearer Setup (DCCH) RRC RB Setup Comp (DCCH) RANAP RAB Assignment Resp ALCAP ERQ ALCAP ECF NBAP RL Reconfigure Commit Continued from NBAP RL Reconfigure Procedure [1] MSC RNC NB UE UTRAN Status IUUP Initialisation [2]
  82. 82. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Setup Service Request / Authentication / Security Call Setup Request and RAB Assignment RRC DL DT (Alerting) RANAP DT (Alerting) [1] [2] MSC RNC NB UE UTRAN Status
  83. 83. PART 3 - UE INITIATED CALL SET-UP (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 RRC Connection Setup Service Request / Authentication / Security 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
  84. 84. 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
  85. 85. PART 4 - UE INITIATED CALL TEAR- 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 Call ConnectedCall Connected RRC UL DT (CC: Disconnect) RANAP DT (CC: Disconnect) [1] [2] MSC RNC NB UE UTRAN Status
  86. 86. PART 4 - UE INITIATED CALL TEAR- 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 Call ConnectedCall Connected 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
  87. 87. PART 4 - UE INITIATED CALL TEAR- 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 Call ConnectedCall Connected RANAP Iu Release Command CC: Call Release RANAP Iu Release Complete [1] [2] MSC RNC NB UE UTRAN Status
  88. 88. PART 4 - UE INITIATED CALL TEAR- 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: 1. DSAID, Cause= 31, normal unspecified UEUE Node B Node B RNCRNC MSCMSC Call ConnectedCall Connected 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
  89. 89. PART 4 - UE INITIATED CALL TEAR- 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 Call ConnectedCall Connected 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
  90. 90. PART 4 - UE INITIATED CALL TEAR- 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 Call ConnectedCall Connected CC: Call Release RANAP Iu Release Command ALCAP Release Request ALCAP Release Confirm RRC Connection Release RRC Con. Release Complete NBAP RL Deletion Request NBAP RL Deletion Response RANAP Iu Release Complete [1] [2] MSC RNC NB UE UTRAN Status
  91. 91. PART 4 - UE INITIATED CALL TEAR- 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: 1. DSAID, Cause= 31, normal unspecified Type: 1. ALCAP 2. ALCAP Main IE’s: 1. DSAID, Cause= 31, normal unspecified UEUE Node B Node B RNCRNC MSCMSC Call ConnectedCall Connected 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 Con. Release Complete RANAP Iu Release Complete [1] [2] MSC RNC NB UE UTRAN Status
  92. 92. PART 4 - UE INITIATED CALL TEAR- DOWN (CS) Procedure OverviewMessages (7): CS Call Tear Down CompleteMessages (7): CS Call Tear Down Complete UEUE Node B Node B RNCRNC MSCMSC Call ConnectedCall Connected CC: Call Release CC: Call ReleaseCS Call Tear Down Complete CS Call Tear Down Complete RRC, RL and Iu Release
  93. 93. PARTS 5 & 6 Packet Switched Data Sessions Parts 5 & 6 Call Setup and Tear Down Scenarios
  94. 94. 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
  95. 95. PART 5 - UE INITIATED CALL SET-UP (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
  96. 96. PART 5 - UE INITIATED CALL SET-UP (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 Initial UE capability 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 Initial UE capability UEUE Node BNode B RNCRNC SGSNSGSN RRC Connection Request (RACH) [1]
  97. 97. PART 5 - UE INITIATED CALL SET-UP (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: 1. Cell ID, TFS / TFCS Frequency, UL Scrambling Code DL Channelisation Code Power Control Info 2. Transport Layer Address Sig. Link termination DL Channelisation Code 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: 1. Cell ID, TFS / TFCS Frequency, UL Scrambling Code DL Channelisation Code Power Control Info 2. Transport Layer Address Sig. Link termination DL Channelisation Code DCH Binding ID RL setup Request RL setup Response RRC Connection Request (RACH) [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  98. 98. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Request (RACH) [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  99. 99. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Request (RACH) FP DL Synchronisation FP UL Synchronisation [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  100. 100. PART 5 - UE INITIATED CALL SET-UP (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: 1. Initial UE ID, RNTI, CapUpReq, TFS, TFCS, frequ, DL Scram + Chann codes, Power control info. 2. UE Capability, Ciphering, 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: 1. Initial UE ID, RNTI, CapUpReq, TFS, TFCS, frequ, DL Scram + Chann codes, Power control info. 2. UE Capability, Ciphering, Integrity info RL setup Request RL setup Response ALCAP ERQ ALCAP ECF RRC Connection Request (RACH) FP DL Synchronisation FP UL Synchronisation RRC Conn. Setup (FACH) RRC Conn. Setup Comp (DCCH) [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  101. 101. PART 5 - UE INITIATED CALL SET-UP (PS)Check Point Two UE Detached – No PDP Contexts – RRC Connected UEUE Node B Node B RNCRNC SGSNSGSN GGSNGGSN 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)
  102. 102. PART 5 - UE INITIATED CALL SET-UP (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) RRC Connection Setup RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  103. 103. PART 5 - UE INITIATED CALL SET-UP (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 Connection Setup RRC Initial D T (PMM Attach Request) RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  104. 104. PART 5 - UE INITIATED CALL SET-UP (PS) Procedure OverviewPMM Attach : SCCP: Connection ConfirmPMM Attach : SCCP: Connection Confirm Description: Main IE’s: Description: Main IE’s: RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) RRC Initial DT (PMM Attach Request) RRC Connection Setup SCCP Connection Conf [1] UEUE Node BNode B RNCRNC SGSNSGSN
  105. 105. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup Authentication RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete (PMM Attach Request) RRC Initial DT RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) SCCP Connection Conf [1] [4] [2] [3] UEUE Node BNode B RNCRNC SGSNSGSN
  106. 106. PART 5 - UE INITIATED CALL SET-UP (PS) 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; [IMSI, IMEI, IEMISV, TMSI] Main IE’s: Req: Identity Request Type Res: Mobile Identity 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; [IMSI, IMEI, IEMISV, TMSI] Main IE’s: Req: Identity Request Type Res: Mobile Identity Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC UL D T (Identity Response.) RANAP DT (Identity Request) UEUE Node BNode B RNCRNC SGSNSGSN
  107. 107. PART 5 - UE INITIATED CALL SET-UP (PS) Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Authentication and Security Mode Commands 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 Network Authentication Integrity Key exchange Ciphering Key Exchange Main IE’s: Req: CK Sequence Number RAND AUTN Res: CK Sequence Number RES Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC UL D T (Identity Response.) RANAP DT (Identity Request) RRC DL DT (Authentication Request) RANAP DT (Authentication Request) RRC UL D T (Authentication Response) RANAP DT (Authentication Response) UEUE Node BNode B RNCRNC SGSNSGSN
  108. 108. PART 5 - UE INITIATED CALL SET-UP (PS) Procedure OverviewIdentity, Authentication and Security Mode CommandsIdentity, Authentication and Security Mode Commands 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: 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 Identity Request Procedure Identity Request Procedure AuthenticationAuthentication Security ModeSecurity Mode RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete RRC DL DT (Identity Request) RANAP DT (Identity Request) RRC Initial D T (Identity Response.) RANAP DT (Identity Request) RRC DL DT (Authentication Request) RANAP DT (Authentication Request) RRC UL D T (Authentication Response) RANAP DT (Authentication Response) UEUE Node BNode B RNCRNC SGSNSGSN
  109. 109. PART 5 - UE INITIATED CALL SET-UP (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 Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete RANAP Common ID (PMM Attach Request) RRC Initial DT RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) SCCP Connection Conf [1] UEUE Node BNode B RNCRNC SGSNSGSN RRC Connection Setup
  110. 110. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup Authentication RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete RANAP Common ID RRC DL DT (PMM Attach Accept) RANAP DT (PMM Attach Accept) (PMM Attach Request) RRC Initial DT RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) SCCP Connection Conf [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  111. 111. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup Authentication RRC Security Mode Command RANAP Security Mode Command RRC Security Mode Complete RANAP Security Mode Complete 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) (PMM Attach Request) RRC Initial DT RANAP Initial UE (PMM Attach Request) (SCCP Con Req.) SCCP Connection Conf [2] [1] UEUE Node BNode B RNCRNC SGSNSGSN
  112. 112. PART 5 - UE INITIATED CALL SET-UP (PS)Check Point Three UE Attached – No PDP Contexts – RRC Connected UEUE Node B Node B RNCRNC SGSNSGSN GGSNGGSN 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
  113. 113. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup PMM Attach Procedure RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req)[1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  114. 114. PART 5 - UE INITIATED CALL SET-UP (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 Connection Setup PMM Attach Procedure RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) RANAP RAB Assignment Req. [1] UEUE Node BNode B RNCRNC SGSNSGSN
  115. 115. PART 5 - UE INITIATED CALL SET-UP (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 Connection Setup PMM Attach Procedure RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready [1] [2] UEUE Node BNode B RNCRNC SGSNSGSN
  116. 116. PART 5 - UE INITIATED CALL SET-UP (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. RRC Connection Setup PMM Attach Procedure RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) UEUE Node BNode B RNCRNC SGSNSGSN ALCAP AAL2 Bearer Set- up and Synchronisation
  117. 117. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup PMM Attach Procedure RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready NBAP RL Reconfigure Commit RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) [1] UEUE Node BNode B RNCRNC SGSNSGSN ALCAP AAL2 Bearer Set- up and Synchronisation
  118. 118. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup PMM Attach Procedure RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready NBAP RL Reconfigure Commit RRC Radio Bearer Setup (DCCH) RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) [1] UEUE Node BNode B RNCRNC SGSNSGSN ALCAP AAL2 Bearer Set- up and Synchronisation
  119. 119. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup PMM Attach Procedure RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready NBAP RL Reconfigure Commit RRC Radio Bearer Setup (DCCH) RRC RB Setup Comp (DCCH) RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) [1] UEUE Node BNode B RNCRNC SGSNSGSN ALCAP AAL2 Bearer Set- up and Synchronisation
  120. 120. PART 5 - UE INITIATED CALL SET-UP (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 RRC Connection Setup PMM Attach Procedure RANAP RAB Assignment Req. NBAP RL Reconfigure Prepare NBAP RL Reconfigure Ready NBAP RL Reconfigure Commit RRC Radio Bearer Setup (DCCH) RRC RB Setup Comp (DCCH) RRC UL DT (Activate PDP Context Req) RANAP DT (Activate PDP Context Req) RANAP RAB Assignment Resp [1] UEUE Node BNode B RNCRNC SGSNSGSN ALCAP AAL2 Bearer Set- up and Synchronisation
  121. 121. PART 5 - UE INITIATED CALL SET-UP (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 RNCRNC SGSNSGSN GGSNGGSN GTP-C Create PDP Context Request [1] RRC Connection Setup PMM Attach Procedure Context Activation Request and RAB Set-Up
  122. 122. PART 5 - UE INITIATED CALL 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 RNCRNC SGSNSGSN GGSNGGSN GTP-C Create PDP Context Request GTP-C Create PDP Context Response [1] RRC Connection Setup PMM Attach Procedure Context Activation Request and RAB Set-Up
  123. 123. PART 5 - UE INITIATED CALL SET-UP (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 RNCRNC SGSNSGSN GGSNGGSN GTP-C Create PDP Context Request GTP-C Create PDP Context Response [1] [2] RANAP DT (Act PDP Context Acc)RRC DL DT (Act PDP Context Acc) RRC Connection Setup PMM Attach Procedure Context Activation Request and RAB Set-Up
  124. 124. PART 5 - UE INITIATED CALL SET-UP (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 RNCRNC SGSNSGSN GGSNGGSN GGSN PDP Context Create and UE PDP Context Activation Accept RRC Connection Setup PMM Attach Procedure Context Activation Request and RAB Set-Up PS Call ActivePS Call Active
  125. 125. PART 5 - UE INITIATED CALL SET-UP (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 RNCRNC SGSNSGSN GGSNGGSN PDN DTCH GTP-U Connection GT P-U Connection

×