4g-3g Comparison Mo Cs Call Flow

Signalling Flow:
AMR Call
Establishment
Summary of AMR Call Establishment

The UE starts by searching for candidate cells
by correlating the RSSI with the code defining
the primary SCH
The UE then achieves radio frame

synchronisation and reads the BCCH logical
channel
UE is
powered
up
Cell search
Radio frame
synchronisation
Read BCCH
The BCCH provides system information

including the cell selection criteria
Cell selection
If the cell passes the cell selection criteria then

the UE establishes an RRC connection and
registers with the core network
Having registered with the core network the UE

returns to the RRC idle mode state and is ready
to originate an AMR speech call
An originating AMR speech call is made and

handovers are completed as and when
required
Finally the AMR speech call is released and the
Register with
core network
Originating
AMR speech
call
Handovers
Release of AMR
speech call
Protocol Stacks
Communication between the UE, RNC and circuit switched core
makes use of
Uu interface protocol stack

Iub interface protocol stack
Iu,cs interface protocol stack
A interface protocol stack
Multimedia
Gateway
RNC
Node B
Uu
Iub
Protocol stacks include both user and control planes
Iu,c
s
3G
MSC
Cell Search
The UE keeps a record of the previously used carrier. The cell
search procedure starts by scanning this carrier
The cell search procedure is completed by correlating RSSI

against the known Primary SCH code
UE is
powered
up
Cell search
Radio frame
synchronisation
Peaks in the correlation result indicate the presence of a cell

Read BCCH
Correlation
Peaks
Correlation
result
Register with
core network
time
Once the UE has identified a cell the UE attempts to synchronise

with that cell
Cell selection
Originating
AMR speech
call
Handovers
Release of AMR
speech call
Radio Frame Synchronisation

The UE completes the three step radio frame synchronisation
UE is
powered
up
Cell search
process
Step 1: Primary SCH identification and slot synchronisation

(completed during cell search)
Step 2: Code group identification and frame synchronisation
Radio frame
synchronisation
using the Secondary SCH

Read BCCH
Step 3: Scrambling code identification using the CPICH

Having completed these three steps the UE is able to decode the
Primary CCPCH -> BCH -> BCCH
Slot 1
Cell selection
Slot 2
Slot 15
Slot 1
Cp
Primary SCH
Cp
Cp
Cs1
Secondary SCH
Cs2
Cs1
256
chips
Register with
core network
Primary CCPCH
Originating
AMR speech
call
2560 - 256
chips
Handovers
Primary CPICH
Release of AMR
speech call
Radio Frame Synchronization ..

Three Steps
1. Slot Synchronization
2.Frame Synchronization
3. Primary Scrambling code Identification
Channels used for Synchronization
Primary synchronization channel (PSCH)
Secondary synchronization channel (SSCH)
Common Pilot Channel (CPICH)
Slot synchronization
Slot Synchronization
PSC : Primary synchronization code
256 chip sequence transmitted in each slot interval
Same for all cells and slot intervals
Mobile Station uses the PSC to acquire slot synchronization
PSCH
The sot timing of the cell can be obtained

by detecting
TS Boundary
peak values in the matched filter
Matched filter
Stored PSCH
2560 chips
Frame Synchronization
SSC: Secondary synchronization code
256 chip sequence transmitted in parallel with PSC.

In general different for different cells and slot intervals
16 different 256 chip sequence ( 16 secondary synch code)
Code word of 15 consecutive SSC indicates cell scrambling
code group
There are 64 such code groups

UE checks in each slot 16 possible SSC sequences and select
which gives the highest correlation value => 15 codes are
selected
The cyclic shift is unique and gives the frame synchronization and
the scrambling code group
Slot No.
Group1
Group2
Group3
SSC1
SSC1
SSC1
SSC1
SSC1
2
SSC2
14
..
SSC16
SSC5
..
SSC10
SSC2
SSC1
SSC12
SSC12
SSC10
SSC10
..
..
Group64
SSC9
SSC Allocation for S-SCH
scrambling
code group
slot number
0
group 00 1
group 01 1
group 02 1
group 03 1
8
1
6
1
group 04 1
group 05 1
3
1
6
4
group 62
1
1
1
2
1
2
1
0
group 63 9
11
5
1
1
0
3
1
5
1
4
1
8
1
6
1
6
1
1
1
1
5
1
5
1
2
1
3
9
1
4
15
1
6
1
6
7
5
3
1
1
6
2
7
4
1
5
2
6
4
1
2
8
1
4
1
1
1
0
1
1
1
6
1
3
1
5
1
2
1
4
1
6
1
6
1
0
1
0
3
1
6
1
0
1
2
5
1
5
5
6
2
5
5
1
2
3
1
3
9
1
3
1
4
1
1
1
5
1
3
7
1
2
1
1
2
1
5
1
4
1
1
8
1
1
0
1
1
2
5
2
7
1
2
1
1
4
1
6
1
0
1
2
8
I
monitor
the SSCH
Scrambling codes summary

1) Long Scrambling code :262143 Codes
2) To speed up the cell search => only 8192 codes
3) 8192 code grouping: 512 groups of 16 codes each ( 512*16 = 8192)
4) 16 codes in each group => first code is Primary scrambling code
and 15 codes are Secondary scrambling codes

5) Again 512 codes are further divided into 64 groups of 8 codes
6) These 64 groups map to the 64 scrambling code group used at
stage 2 during frame synchronization
That way UE limits its Primary Scrambling code search to just 8 codes
At this stage max 8 attempts to find out the Primary Scrambling code of the cell
7) Each cell is allocated one Primary scrambling code ( Carrying PCPICH, PCCPCH, PICH, AICH and S-CCPCH)
8) Other channels can use Primary scrambling code or secondary
scrambling codes from the same group
Timing Relationship
Slot 1
Slot 2
Slot 15
Slot 1
Cp
Primary SCH
Cp
Cp
Cs1
Secondary SCH
Cs2
Cs1
Primary CCPCH
256
chips
2560 - 256
chips
Primary CPICH
Cell Search Procedure Summary
Read BCCH
The BCCH encapsulates the System Information message which
includes the Master Information Block (MIB), Scheduling Blocks
(SB) and System Information Blocks (SIB)
SIB1, SIB2 .SIB18
UE is
powered
up
Cell search
Radio frame
synchronisation
Read BCCH
SB
SIBs
Cell selection
Register with
core network
MIB
SIBs
Originating
AMR speech
call
Handovers
Release of AMR
speech call
System Information
System Information (
UTRAN
NBAP: BCCH Information
RNC
UE
Node B
MIB
value tag M
SB1
SIB 1
SIB 2
SIB 11
Cell Selection
Cell selection is standardised process ( 25.304)
Cell selection is based upon the S-criteria
Srxlev > 0
Squal > 0
UE is
powered
up
Cell search
Radio frame
synchronisation
UE extracts the S-criteria parameters from SIB 3

QqualMin
Read BCCH
QrxlevMin
UE_TXPWR_MAX_RACH
Cell selection
Register with
core network
Originating
AMR speech
call
Handovers
Release of AMR
speech call
Cell Selection (II)

Both Squal and Srxlev must be positive for the UE to camp
upon the cell
UE is
powered
up
Cell search
Radio frame
synchronisation
Squal = Qqualmeas QqualMin

Read BCCH
Srxlev = Qrxlevmeas QrxlevMin Pcompensation

Cell selection
where, Pcompensation =
Max(UE_TXPWR_MAX_RACH P_MAX,
0)
Default values:
QqualMin is 20 dB CPICH Ec/Io
QrxlevMin is 115 dBm CPICH RSCP
UE_TXPWR_MAX_RACH is 21 dBm
Register with
core network
Originating
AMR speech
call
Handovers
Release of AMR
speech call
Register with the Core Network

The UE registers with the CS core domain
CS domain registering is an IMSI attach
Registering is achieved by establishing an RRC connection
UE is
powered
up
Cell search
Radio frame
synchronisation
and sending NAS messages to the CS core
The non-access stratum message is encapsulated within a
Read BCCH
Location Update Request message

Cell selection
RRC CONNECTION ESTABLISHMENT

LOCATION UPDATING PROCEDURE
Register with
core network
Originating
AMR speech
call
Handovers
Release of AMR
speech call
RRC Modes
UTRA RRC Connected Mode
URA_PCH
CELL_PCH
GSM-UMTS Handover
GSM
Connected
UTRA: Inter-RAT HandoverMode
Release RR
Connection
CELL_DCH
Release RRC
Connection
CELL_FACH
Release RRC
Connection
Establish RRC
Connection
GPRS Packet
Transfer
Cell
Mode
Resele-
ction
Release
of a
TBF
Establish RRC
Connection
(UE camps on UTRAN cell)
Idle Mode
Initiation
of a TBF
Establish R
Connection
(MS in GPRS
Packet Idle Mode)
(MS camps on a GERAN cell)
(adopted from TS 25.331 V
CELL_DCH State
DCCH and if configured
DTCH
Dedicate physical channel
in use
UE location known on
active set cell level
UE responsible for
measurement reporting
Cell system information
on BCCH
active set
RRC messages on
DCCH
cell
active set
cell
CELL_FACH State
DCCH and if configured
DTCH
FACH used for higher layer
data transfer,
UE monitors FACH
permanently
Uplink transmission on
RACH
UE location known on
serving cell level
UE performs cell reselection
UE responsible for
measurement reporting
Cell system information on
BCCH
RRC messages on BCCH,
CCCH and DCCH
serving
cell
CELL_PCH and URA_PCH State

no DCCH and DTCH
Before uplink transmission UE moves to
CELL_FACH
UE must be paged
RRC messages on BCCH and PCCH
In CELL_PCH
- UE location known on cell level
- UE performs cell re-selection and cell
updates
In URA_PCH
- UE location known on URA level
- UE performs cell re-selection and URA
updates
URA UTRAN Registration Area
UTRAN Specific Signalling Protocols
RNS
Iub
Node B : NB
AP
UE
RNC
Iu-
P
ANA
R
:
CS
3G-MSC/VLR
RRC
IuP
S:
RA
NA
P
3G-SGSN
Iur: RNSAP
RNC
RNS
Register with the Core Network

The UE registers with the CS core domain
CS domain registering is an IMSI attach
Registering is achieved by establishing an RRC connection
UE is
powered
up
Cell search
Radio frame
synchronisation
and sending NAS messages to the CS core
The non-access stratum message is encapsulated within a
Read BCCH
Location Update Request message

Cell selection
RRC CONNECTION ESTABLISHMENT

LOCATION UPDATING PROCEDURE
Register with
core network
Originating
AMR speech
call
Handovers
Release of AMR
speech call
RRC Connection Establishment

UE
Node B
[RACH] RRC Connection Request
Radio Link Setup
RNC
accep
ted
[FACH] RRC Connection Setup

L1 Synchronisation
[DCH] RRC Connection Setup Complete
RNC
UE
[RACH] RRC Connection Request
reject
ed
[FACH] RRC Connection Reject

If the cell from which the BCCH has been read is suitable to camp upon then the UE follows the
instructions in SIB1 to complete an IMSI attach with the CS core network
To complete an IMSI attach the UE must first establish an RRC connection

The RRC Connection Request message is sent to the RNC on RACH
UE
Node B
RRC CONNECTION REQUEST

LCH:CCCH
TCH:RACH
PCH:PRACH
LCH:CCCH
TCH: FACH
PCH: S-CCPH
LCH: DCCH
TCH:DCH
PCH: DPCH
RRC CONNECTION SETUP
RRC CONNECTION SETUP COMPLETE
RNC
RRC Connection Request

UE
Node B
RRC: RRC Connection Request (RACH)
The RRC Connection Request message is sent to the RNC on RACH
RRC CONNECTION REQUES: When UE wants to make a

call or register to the network after power on, the first
thing it should do is establish an RRC connection.
Applicable UE State(s)
Idle mode
Logical Channel Used : CCH
Transport Channel Used: RACH
Physical Channel Used: PRACH
Msg contains:
UE Identity, Establishment cause etc.
RNC
NBAP: Radio Link Setup Request

UE
Node B
RNC
RRC: RRC Connection Request

(RACH)
Once the RNC has received the RRC Connection Request message it sends a Common
NBAP: Radio Link Setup Request to the Node B
The Common NBAP: Radio Link Setup Request includes uplink and downlink
configuration data for the radio link that the Node B is being requested to support
The radio link refers only to the communication link between the Node B and UE. It
does not include Iub communication
NBAP: Radio Link Setup Response

The Node B acknowledges the Common NBAP: Radio Link Setup Request message
with a Common NBAP: Radio Link Setup Response message
UE
Node B
RNC

ALCAP and FP Signalling for Iub

Connection
Node B
UERRC: RRC Connection Request (RACH)
RNC
ALCAP and FP Signalling
RRC Connection Setup (I)

The RNC replies to the UEs original RRC Connection Request message with an RRC
Connection Setup message
The RRC Connection Setup message is sent to the UE on the FACH using
unacknowledged mode RLC
Node B
UE
RNC

ALCAP and FP Signalling
RRC: RRC Connection Setup (FACH)
Signalling Radio Bearers

RRC Connection Setup (
UE
RRC Signalling
NAS Signalling
op
tio
na
RRC layer
RB0
RB1
RB2
RB3
RB4 Radio Bearer
RLC
UL: TrM
DL: UM
RLC
UL & DL:
UM
RLC
UL & DL
AM
RLC
UL & DL
AM
RLC
UL & DL
AM
CCCH
DCCH
DCCH
DCCH
DCCH
MAC
RNC
LogCH
RRC Connection Setup message

UE
NAS Signalling
RNC
user plane
RRC layer
RB
configura
tion
Radio Bearer
PDCP
BMC
RLC
LogCH
TrCH
configura
tion
PhyCh
configura
tion
MAC
TrCH
PHY
PhyCH
Example: 13.6 kbps SRB ( Part of RRC

Connection Setup )
Higher layer
RLC
MAC
RAB/signalling RB
SRB#1
SRB#2
SRB#3
SRB#4
User of Radio Bearer
RRC
RRC
NAS_DT
High prio
NAS_DT
Low prio
Logical channel type
DCCH
DCCH
DCCH
DCCH
RLC mode
UM
AM
AM
AM
Payload sizes, bit
136
128
128
128
Max data rate, bps
13 600
12 800
12 800
12 800
AMD/UMD PDU header, bit
16
16
16
MAC header, bit
MAC multiplexing
Layer 1
TrCH type
DCH
TB sizes, bit
TFS
4 logical channel multiplexing
148 (alt 0, 148)

TF0, bits
0x148 (alt 1x0)
TF1, bits
1x148
TTI, ms
Coding type
10
CC 1/3
CRC, bit
16
Max number of bits/TTI before rate matching
516
Uplink: Max number of bits/radio frame

before rate matching
516
RRC Connection Setup (III)

srb-InformationSetupList {
{
rb-Identity 1,
rlc-InfoChoice rlc-Info : {
ul-RLC-Mode ul-UM-RLC-Mode : {
},
dl-RLC-Mode dl-UM-RLC-Mode :
NULL
},
rb-MappingInfo {{
ul-LogicalChannelMappings
oneLogicalChannel : {
ul-TransportChannelType
dch : 24,
logicalChannelIdentity 1,
rlc-SizeList configured : NULL,
mac-LogicalChannelPriority 1
},
dl-LogicalChannelMappingList {
{
dl-TransportChannelType
dch:24,
logicalChannelIdentity 1
}
}
}
}
},
{
SRB 1 is:
established with rb identity 1
configured with unacknowledged mode
RLC
mapped to transport channel 24

assigned a logical channel identity 1
SRB 1 is established for control plane
communication with UTRAN when
unacknowledged mode RLC is used
Signalling RRC messages
RRC Connection Setup (1V)

rb-Identity 2,
}
}, dl-RLC-Mode dl-AM-RLC-Mode : {
inSequenceDelivery TRUE,
receivingWindowSize rw64,
dl-RLC-StatusInfo {
missingPDU-Indicator FALSE
}
}
},
rb-MappingInfo {
{
ul-TransportChannelType dch :
24,
},
{
dl-TransportChannelType
dch : 24,
}
SRB 2 is:
configured with acknowledged mode RLC
SRB 2 is established for control plane
communication with UTRAN when
acknowledged mode RLC is used
RRC Connection Setup (V)

rb-Identity 3,
}
SRB 3 is:
},
configured with acknowledged mode RLC
dl-RLC-Mode dl-AM-RLC-Mode : {
dl-RLC-StatusInfo {
missingPDU-Indicator FALSE
}
SRB 3 is established for high priority control
}
plane communication with the core network
},
rb-MappingInfo {{
24,
},
{
dl-TransportChannelType dch
: 24,
}
RRC Connection Setup (VI)

SRB 4 is:
rb-Identity 4,
}
},
dl-RLC-Mode dl-AM-RLC-Mode : {
dl-RLC-StatusInfo {
FALSE
}
}
},
rb-MappingInfo {
{
24,
},
{
dl-TransportChannelType dch :
24,
}

configured with acknowledged mode
RLC

SRB 4 is established for low priority control
plane communication with the core
network
RRC Connection Setup message

UE
NAS Signalling
RNC
user plane
RRC layer
RB
configura
tion
Radio Bearer
PDCP
BMC
RLC
LogCH
TrCH
configura
tion
PhyCh
configura
tion
MAC
TrCH
PHY
PhyCH
NBAP: Synchronisation Indication

UE
Node B
RNC
NBAP Signalling
L1 Synchronisation
Layer 1 Synchronisation happens between UE and Node B. After successful L1

Synchronisation Node B sends a Synchronisation Indication message to the RNC to
indicate that the radio link has been established.
This is a Nokia proprietary message that is equivalent to the 3GPP Radio Link Restore
Indication message
RRC Connection Setup Complete

Completion of RRC Connection Establishment
Node B
UE
RNC

ALCAP: Establish Request
ALCAP: Establish Confirm
FP: Downlink Sync
FP: Uplink Sync
L1 Synchronisation
RRC: RRC Connection Setup Complete (DCH)
Location Updating Request

The UE has now established a dedicated communication link with UTRAN and is in a
position to send a message to the core network (CS core in this case)
The UE uses an uplink RRC: Initial Direct Transfer message to encapsulate and send a
Location Updating Request message to the RNC
The Node B extracts the RRC: Initial Direct Transfer message and encapsulates it
within a DCH Frame Protocol frame
The RNC extracts the Location Updating Request message and encapsulates it within
a RANAP: Initial UE Message message prior to forwarding it to the multimedia gateway
This NAS message is transparent to RNC
UE
Node B
RNC
MGW
RRC Connection Request (RACH)

RRC Connection Setup (FACH)
RRC Connection Setup Complete (DCH)
Location Updating Request (DCH)
SCCP: Connection Request
Initial UE message : Location Updating Reques
The RANAP: Initial UE Message message is

accompanied with a SCCP: Connection
Request message which is used to establish
the Iu-cs connection orientated link
UMTS security Features: Authentication, Integrity,

Ciphering
Authentication Request
Having received the Location Updating Request message the CS core responds with an
Authentication Request message
The Authentication Request message is sent to the RNC encapsulated within a RANAP
Direct Transfer message
The RNC extracts the Authentication Request message and encapsulates it within an RRC
Downlink Direct Transfer message
The RNC then encapsulates the RRC Downlink Direct Transfer message within a downlink
Frame Protocol data frame prior to forwarding it to the Node B
The Node B extracts the RRC Downlink Direct Transfer message and forwards it to the UE
UE
Node B
RNC
MGW


SCCP: Connection Confirm
(DCH)
Authentication Response
Having received the Authenication Request message the UE responds with an
Authentication Response message
The Authentication Response message is sent to the Node B encapsulated within an RRC
Uplink Direct Transfer message
The Node B encapsulates the RRC Uplink Direct Transfer message within an uplink Frame
Protocol data frame prior to forwarding it to the RNC
The RNC extracts the Authentication Response message and encapsulates it within a
RANAP Direct Transfer message prior to forwarding it to the CS core
UE
Node B
RNC
MGW


(DCH)
Authenication Response (DCH)
Security Mode Command: Integrity, Ciphering

The CS core sends a Security Mode Command message to the UE
The purpose of this procedure is to trigger the start ciphering (Optional)
It is also used to start integrity protection all signalling radio bearers (Mandatory)
UE
Node B
RNC
MGW


(DCH)
(DCH)
Security Mode Command
Security Mode Complete

The UE responds to the Security Mode Command message with a Security Mode
Complete message
UE
Node B
RNC
MGW


(DCH)
(DCH)
Secuirty Mode Complete (DCH)
Identity Request
The CS core may request the UE to provide its identity. This is done using the Identity Request
message
The CS core sends the Identity Request message encapsulated within a RANAP: Direct
Transfer message
UEThe RNC sends the Identity Node
B
Request
message encapsulated RNC
within a RRC: Downlink Direct MGW
Transfer message

(DCH)
(DCH)
(DCH)
Identity Request
Identity Response
The UE sends the Identity Response message encapsulated within a RRC: Uplink Direct
Transfer message
The RNC sends the Identity Response message encapsulated within a RANAP: Direct Transfer
UE
Node B
RNC
MGW
message

(DCH)
(DCH)
(DCH)
Identity Request
Identity Response (DCH)
Location Updating Accept

The CS core responds to the Location Updating Request with a Location Updating Accept
message
The Location Updating Accept is sent to the RNC encapsulated within a RANAP: Direct
Transfer message
The RNC extracts the Location Updating Accept message and encapsulates it within an RRC:
UEDownlink Direct Transfer message
Node B
RNC
MGW

(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Having sent the Location Updating Accept message the CS core initiates the release
of the Iu-cs connection by sending a RANAP: Iu Release Command message to the
RNC
UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
The RNC replies to the RANAP: Iu Release Command message with a RANAP: Iu
Release Complete message
UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
Released
Having released the Iu-cs connection at the RANAP layer, the SCCP layer releases the
underlying connection orientated link
UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
SCCP: Released
RRC Connection Release

UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
SCCP: Released
SCCP: Release Complete
RRC Connection Release (DCH)
Having sent the Iu Release Complete message the RNC initiates the release of the
RRC connection by sending an RRC Connection Release message to the UE
RRC Connection Release Complete

UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Authentication Response (DCH)
Iu Release Command
Iu Release Complete
SCCP: Released
RRC Connection Release Complete (DCH)
The UE responds by sending (n308+1) RRC Connection Release Complete messages to the
RNC
Radio Link Deletion Request

UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
SCCP: Released
NBAP: Radio Link Deletion Request
Radio Link Deletion Response

UE
Node B
RNC
MGW


(DCH)
(DCH)
(DCH)
Identity Request
(DCH)
Iu Release Command
Iu Release Complete
SCCP: Released
NBAP: Radio Link Deletion Response
Summary of IMSI Attach

UE
Node B
RNC

ALCAP: Establish Request
ALCAP: Establish Confirm
FP: Downlink Sync
FP: Uplink Sync
MGW
L1 Synchronisation

(DCH)

(DCH)
(DCH)
Identity Request
(DCH)

Iu Release Command
Iu Release Complete
SCCP: Released


NBAP: Radio Link Deletion Response
ALCAP: Release Request
ALCAP: Release Confirm
UE is powered
up
AMR Speech Call
Cell search
The AMR speech call can be either mobile originated or

mobile terminated
Radio frame
synchronisation
The following slides present a mobile originated call

The first step is to establish an RRC connection. This is done
in the same way as for the IMSI attach procedure
Read BCCH
The only difference is that the establishment cause specified

in the RRC Connection Request message is specied as
Cell selection
originatingConversationalCall
UE
Node B
RNC
Register with
core network
Cell reselections
Once the RRC connection has been established the UE is able

to send a NAS message to the circuit switched core
AMR speech
call
Handovers
Release of AMR
speech call
CM Service Request
UE
Node B
MGW
RNC

Initial Direct Transfer (CM Service Request)
By sending this message UE requests a

service for the circuit switched connection
establishment
DCCH ->DCH -> DPCH

DCCH contains the RRC: Initial Direct Transfer
message
Message is sent using acknowledged mode

RLC
The message is sent to the CS core domain
The NAS message is not read by the RNC but is forwarded to the multimedia
gateway

UE
Node B
MGW
RNC


Location Reporting Control
Common ID
The CS core sends a Security Mode Command message to the UE

The purpose of this procedure is to trigger the start or stop of ciphering or to command
the restart of the ciphering with a new ciphering configuration, for the radio bearers of
one core network domain and for all signalling bearers
It is also used to start integrity protection or to modify the integrity protection
configuration for all signalling radio bearers

UE
Node B
MGW
RNC


Common ID
The UE responds to the Security Mode Command message with a Security Mode
Complete message
CM Service Accept
UE
Node B
MGW
RNC


Common ID

OR
CM Service Accept
The CM Service Accept message is only sent if the security mode procedure is not
used
If the security mode procedure is used then completion of that procedure is used
as an alternative indication of CM service acceptance.
Extract from 24.008:

In UMTS, an indication from the RR sublayer that the security mode control procedure is
completed, or reception of a CM SERVICE ACCEPT message, shall be treated as a service
acceptance indication by the mobile station
The CM Service Accept message serves only as an acknowledgement and contains

no additional information
Setup
UE
Node B
MGW
RNC


Common ID

Setup
The UE then sends a NAS Setup message to the CS core using an RRC: Uplink Direct
Transfer message
The NAS message is included and directed towards the CS core domain
The NAS message includes the number being dialled by the UE
Call Proceeding
UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Having received the NAS Setup message the CS core sends the NAS Call Proceeding
message
This message indicates to UE that Call Setup Procedure is started at the NW side
RAB Assignment Request

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
CS core sends the RANAP: RAB Assignment Resuest message to the RNC
The RANAP: RAB Assignment Resuest message requests the RNC to establish a RAB
with a specified set of QoS parameters
The CS core requests these QoS parameters based upon the UE subscription and
the service being requested
Radio Link Reconfigure Prepare

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
Assuming that the admission control procedure within the RNC decides to accept
the RAB request then it prepares to reconfigure the radio link at the Node B by
sending the NBAP: Radio Link Reconfigure Prepare message
Radio Link Reconfigure Ready

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
The Node B responds to the NBAP: Radio Link Reconfigure Prepare message with
a NBAP: Radio Link Reconfigure Ready message
Radio Link Reconfiguration Commit

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Once the transmission resouce allocations have been configured the RNC
sends a NBAP: Radio Link Reconfiguration Commit message to the Node B
Radio Bearer Setup

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Once the NBAP: Radio Link Reconfiguration Commit message has been
sent to the Node B the RNC sends a RRC: Radio Bearer Setup message to
the UE
Radio Bearer Setup (II)

Higher
layer
RAB/Signalling
RB
RLC
Logical channel
type
RLC mode
Payload sizes, bit
RAB
subflow #1
Layer
1
TM
TM
TM
39, 81
(alt. 0, 39,
81)
103
60
MAC header, bit
MAC multiplexing
N/A
Radio bearer 5 is mapped to DCH

transport channel 1. This corresponds
to the AMR class A bits transport
channel
Radio bearer 5 is configured with
DCH
DCH
DCH
TB sizes, bit
39, 81
(alt. 0, 39,
81)
103
60
TFS
0x81(alt.
1x0) (note)
0x103
0x60
TF1, bits
1x39
1x103
1x60
TF2, bits
1x81
N/A
N/A
20
20
20
CC 1/3
CC 1/3
CC 1/2
TTI, ms
Coding type
Cell_DCH after the radio bearer has

been established
AMR 12.2 kbps Radio Bearer
TF0, bits
The UE is instructed to remain in
12 200
TrD PDU header,

bit
TrCH type
RAB
subflow #3
DTCH
Max data rate,

bps
MAC
RAB
subflow #2
transparent mode RLC

to the AMR class B bits transport
channel

to the AMR class C bits
Radio bearer 5,6,7 is configured with

transparent mode RLC
Radio Bearer Setup Complete

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
The UE acknowledges the RRC: Radio Bearer Setup message with a RRC:
Radio Bearer Setup Complete message
RAB Assignment Response

UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Once the radio bearer establishment has been acknowledged, the RNC indicates to
the CS core that the RAB has been established using the RANAP: RAB Assignment
Response message
Alerting
UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Alerting
Having received the RANAP: RAB Assignment Response message, the CS core
sends the NAS Alerting message to the UE
This message is sent to indicate that the called user alerting has been initiated.
UE
Node B
Connect
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Alerting
Connect
Having received the RANAP: RAB Assignment Response message, the CS core
sends the NAS Alerting message to the UE
This message is sent to indicate call acceptance by the called user
Connect Acknowledge
UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Alerting
Connect
Connect Acknowledge
The UE acknowledges the NAS Connect message with the NAS Connect
Acknowledge message
Call Established
UE
Node B
MGW
RNC


Common ID

Setup
Call Proceeding
Facility
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
AAL2SIG:ERQ
AAL2SIG:ECF
Radio Bearer Setup
Alerting
Connect
Connect Acknowledge
Call Established
The call is established at this point
Release of AMR Speech Call

The call is released in a controlled manner when either the
originating or terminating terminal hangs-up
UE is powered
up
Cell search
Radio frame
synchronisation
The RRC connection is released and the UE returns to RRC

Idle mode
Read BCCH
Cell selection
Register with
core network
AMR speech
call
Release of AMR
speech call
Uplink Disconnect
UE
Node B
RNC
Call Established
Direct Transfer (Disconnect)
In this example the UE initiates the

call release by sending the
Disconnect message to the CS core
MGW
Downlink Release (I)

UE
Node B
RNC
MGW
Call Established
Direct Transfer (Release)
The network acknowledges the

Disconnect message with a
Release message
Uplink Release Complete

UE
Node B
RNC
MGW
Call Established
Direct Transfer (Release Complete)
Iu Release Command
UE
Node B
MGW
RNC
Call Established

Iu Release Command
The core network initiates the release of the Iu resources using the Iu Release
Command message
Iu Release Complete
UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete

UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete

UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete

UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete

UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete
Release of AMR Speech Call

UE
Node B
MGW
RNC
Call Established

Iu Release Command
Iu Release Complete
ALCAP: Release Response
ALCAP: Release Response
Call Released
UE returns to Idle Mode

4g-3g Comparison Mo Cs Call Flow

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4g-3g Comparison Mo Cs Call Flow

Uploaded by

Copyright:

Available Formats

Signalling Flow:

Summary of AMR Call Establishment

The UE then achieves radio frame

The BCCH provides system information

If the cell passes the cell selection criteria then

Having registered with the core network the UE

An originating AMR speech call is made and

Finally the AMR speech call is released and the

Uu interface protocol stack

Protocol stacks include both user and control planes

The cell search procedure is completed by correlating RSSI

Peaks in the correlation result indicate the presence of a cell

Once the UE has identified a cell the UE attempts to synchronise

Radio Frame Synchronisation

Step 1: Primary SCH identification and slot synchronisation

Step 2: Code group identification and frame synchronisation

using the Secondary SCH

Step 3: Scrambling code identification using the CPICH

Radio Frame Synchronization ..

The sot timing of the cell can be obtained

256 chip sequence transmitted in parallel with PSC.

There are 64 such code groups

SSC Allocation for S-SCH

Scrambling codes summary

and 15 codes are Secondary scrambling codes

Cell Search Procedure Summary

SIB1, SIB2 .SIB18

NBAP: BCCH Information

UE extracts the S-criteria parameters from SIB 3

Cell Selection (II)

Squal = Qqualmeas QqualMin

Srxlev = Qrxlevmeas QrxlevMin Pcompensation

Register with the Core Network

and sending NAS messages to the CS core

The non-access stratum message is encapsulated within a

Location Update Request message

RRC CONNECTION ESTABLISHMENT

(UE camps on UTRAN cell)

(adopted from TS 25.331 V

CELL_PCH and URA_PCH State

URA UTRAN Registration Area

UTRAN Specific Signalling Protocols

Register with the Core Network

and sending NAS messages to the CS core

The non-access stratum message is encapsulated within a

Location Update Request message

RRC CONNECTION ESTABLISHMENT

RRC Connection Establishment

[FACH] RRC Connection Setup

[DCH] RRC Connection Setup Complete

RRC Connection Establishment

To complete an IMSI attach the UE must first establish an RRC connection

RRC CONNECTION REQUEST

RRC CONNECTION SETUP

RRC CONNECTION SETUP COMPLETE

RRC Connection Request

The RRC Connection Request message is sent to the RNC on RACH

RRC CONNECTION REQUES: When UE wants to make a

NBAP: Radio Link Setup Request

RRC: RRC Connection Request

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

RRC: RRC Connection Request (RACH)

ALCAP and FP Signalling for Iub