WCDMA UTRAN Interface and Signaling Procedure ISSUE 1

WCDMA UTRAN Interface and Signaling Procedure
Revision Record
N-0
Dont Print This Page

Product
Course Code
Product
OWA10
WRAN
ALL
1.20
Developer/Modifier
Time
Approver
New/Update
SUNTAN
2009-2-2
LIANGJIE
Add notes
GUOYANG
2009-04-15
LIANGJIE
BUG correction
GUOYANG
2009-12
LIANGJIE
BUG correction
Version
Course Version ISSUE
Copyright 2008 Huawei Technologies Co., Ltd. All rights Page0

reserved.
Confidential Information of Huawei. No Spreading Without Permission
PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com
N-1
WCDMA UTRAN Interface

and Signaling Procedure
www.huawei.com
Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
l
Upon completion of this course, you will be able to:

p
Understand UTRAN interface and structure
Understand the definitions about UTRAN network elements
Understand UTRAN signaling procedure

reserved.
N-2
Contents
1. UTRAN Network Overview
2. Basic Concepts about UTRAN
3. UTRAN Signaling Procedure

reserved.
N-3
N-4
UMTS Network Structure

Core Network
CN
CS
PS
Iu-CS
CS
Iu-PS
PS
Iu-CS
RNS
Iu-PS
RNS
Iur
RNC
RNC
UTRAN
Iub
NodeB
Iub
Iub
NodeB
NodeB
Iub
NodeB
Uu
UE
reserved.
UTRAN (UMTS Terrestrial Radio Access network) structure

p
The UTRAN consists of one or several Radio Network Subsystem ( RNS ),

each containing one RNC and one or several NodeB
Interface
p
Iu interface: the Iu interface connects the UTRAN to the CN and is split in

two parts. The Iu-CS is the interface between the RNC and the circuit
switched domain of the CN. The Iu-PS interface is the interface between the
RNC and the packet switched domain of the CN.
Uu interface: the Uu interface is the WCDMA radio interface with in UMTS.
It is the interface through which the UE accesses the fixed part of the
network.
Iub interface: the Iub interface connects the NodeB and the RNC. Contrarily
to GSM, this interface is fully open in UMTS and thus more competition is
expected.
Iur interface: the RNC-RNC interface was initially designed in order to
provide inter RNC soft handover, but more features were added during the
development.
N-5
Uu Interface
GC
Nt
DC
Duplication avoidance
GC
Nt
DC
control
RRC
control
UuS boundary
U-plane information
control
control
control
C-plane signaling
L3
radio bearer
PDCP PDCP
RLC
RLC
RLC
RLC
RLC
RLC RLC
L2/PDCP
BMC
L2/BMC
RLC
L2/RLC
logical channel
MAC
L2/MAC
transport channel
PHY
L1

reserved.
The layer 1 supports all functions required for the transmission of bit streams on
the physical medium. It is also in charge of measurements function consisting in
indicating to higher layers, for example, Frame Error Rate (FER), Signal to
Interference Ratio (SIR), interference power, transmit power, It is basically
composed of a layer 1 management entity, a transport channel entity, and a
physical channel entity.
The layer 2 protocol is responsible for providing functions such as mapping,

ciphering, retransmission and segmentation. It is made of four sublayers: MAC
(Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data
Convergence Protocol) and BMC (Broadcast/Multicast Control).
The layer 3 is split into 2 parts: the access stratum and the non access stratum.
The access stratum part is made of RRC (Radio Resource Control) entity and
duplication avoidance entity. The non access stratum part is made of CC, MM
parts.
Not shown on the figure are connections between RRC and all the other protocol
layers (RLC, MAC, PDCP, BMC and L1), which provide local inter-layer control
services.
The protocol layers are located in the UE and the peer entities are in the NodeB or
the RNC.
N-6
General Protocol Mode for UTRAN

Terrestrial Interface
l
The structure is based on the principle that the layers and planes
are logically independent of each other.
Radio
Network
Layer
Control Plane
User Plane
Application
Protocol
Data
Stream(s)
Transport
Network
Layer
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
ALCAP(s)
Signaling
Bearer(s)
Signaling
Bearer(s)
Data
Bearer(s)
Physical Layer

reserved.
Protocol structures in UTRAN terrestrial interfaces are designed according to the

same general protocol model. This model is shown in above slide. The structure is
based on the principle that the layers and planes are logically independent of each
other and, if needed, parts of the protocol structure may be changed in the future
while other parts remain intact.
Horizontal Layers
p
The protocol structure consists of two main layers, the Radio Network Layer
(RNL) and the Transport Network Layer (TNL). All UTRAN-related issues
are visible only in the Radio Network Layer, and the Transport Network Layer
represents standard transport technology that is selected to be used for
UTRAN but without any UTRAN-specific changes.
Vertical Planes
p
Control Plane
The Control Plane is used for all UMTS-specific control signaling. It includes
the Application Protocol (i.e. RANAP in Iu, RNSAP in Iur and NBAP in Iub),
and the Signaling Bearer for transporting the Application Protocol messages.
The Application Protocol is used, among other things, for setting up bearers
to the UE (i.e. the Radio Access Bearer in Iu and subsequently the Radio
Link in Iur and Iub). In the three plane structure the bearer parameters in the
Application Protocol are not directly tied to the User Plane technology, but
rather are general bearer parameters. The Signaling Bearer for the
Application Protocol may or may not be of the same type as the Signaling
Bearer for the ALCAP. It is always set up by O&M actions.
N-7
User Plane
All information sent and received by the user, such as the coded voice in a
voice call or the packets in an Internet connection, are transported via the
User Plane. The User Plane includes the Data Stream(s), and the Data
Bearer (s) for the Data Stream(s). Each Data Stream is characterized by one
or more frame protocols specified for that interface.
Transport Network Control Plane
The Transport Network Control Plane is used for all control signaling within
the Transport Layer. It does not include any Radio Network Layer information.
It includes the ALCAP protocol that is needed to set up the transport bearers
(Data Bearer) for the User Plane. It also includes the Signaling Bearer
needed for the ALCAP. The Transport Network Control Plane is a plane that
acts between the Control Plane and the User Plane. The introduction of the
Transport Network Control Plane makes it possible for the Application
Protocol in the Radio Network Control Plane to be completely independent of
the technology selected for the Data Bearer in the User Plane.
About AAl2 and AAL5

p
Above the ATM layer we usually find an ATM adaptation layer (AAL). Its
function is to process the data from higher layers for ATM transmission.
This means segmenting the data into 48-byte chunks and reassembling the
original data frames on the receiving side. There are five different AALs (0, 1,
2, 3/4, and 5). AAL0 means that no adaptation is needed. The other
adaptation layers have different properties based on three parameters:
n
Real-time requirements;
Constant or variable bit rate;
Connection-oriented or connectionless data transfer.
The usage of ATM is promoted by the ATM Forum. The Iu interface uses two
AALs: AAL2 and AAL5.
AAL2 is designed for the transmission of connection oriented, real-time
data streams with variable bit rates.
AAL5 is designed for the transmission of connectionless data streams
with variable bit rates.
N-8
RNL Control Plane Application Protocol

CN
RANAP
UE
RRC
RNC
RNSAP
RNC
NBAP
NodeB
NBAP
Node B Application Part
RANAP
Radio Access Network Application Part
RNSAP
Radio Network Subsystem Application Part
RRC
Radio Resource Control

reserved.
RANAP is the signaling protocol in Iu that contains all the control information
specified for the Radio Network Layer.
RNSAP is the signaling protocol in Iur that contains all the control information
NBAP is the signaling protocol in Iub that contains all the control information
RRC is the signaling protocol in Uu that locate in the Uu interface layer 3.
N-9
Iu-CS Interface (based on ATM)

Radio
Network
Layer
Control Plane
User plane
RANAP
Iu UP
Transport Network
User Plane
Transport
Network
Layer
Transport Network
Control Plane
Transport Network
User Plane
ALCAP
ALCAP
SCCP
A
MTP3-B
SAAL NNI
MTP3-B
SAAL NNI
AAL2 PATH
ATM
Physical Layer

reserved.
Protocol Structure for Iu CS

p The Iu CS overall protocol structure is depicted in above slide. The
three planes in the Iu interface share a common ATM
(Asynchronous Transfer Mode) transport which is used for all
planes. The physical layer is the interface to the physical medium:
optical fiber, radio link or copper cable. The physical layer
implementation can be selected from a variety of standard off-theshelf transmission technologies, such as SONET, STM1, or E1.
Iu CS Control Plane Protocol Stack
The Control Plane protocol stack consists of RANAP, on top of
Broadband (BB) SS7 (Signaling System #7) protocols. The
applicable layers are the Signaling Connection Control Part (SCCP),
the Message Transfer Part (MTP3-b) and SAAL-NNI (Signaling
ATM Adaptation Layer for Network to Network Interfaces).
Iu CS Transport Network Control Plane Protocol Stack
p The Transport Network Control Plane protocol stack consists of the
Signaling Protocol for setting up AAL2 connections (Q.2630.1 and
adaptation layer Q.2150.1), on top of BB SS7 protocols. The
applicable BB SS7 are those described above without the SCCP
layer.
Iu CS User Plane Protocol Stack
p A dedicated AAL2 connection is reserved for each individual CS
service.
p
N-10
Iu-CS Interface (based on IP)

Radio
Network
Layer
Control Plane
User plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
User Plane
Transport
Network
Layer
SCCP
M3UA
RTP/RTCP
UDP
SCTP
IP
IP
DATA LINK
DATA LINK
Physical Layer

reserved.
l
l
SCTP is streaming control transmission protocol. It is a reliable transport

protocol operating on top of IP.
M3UA is MTP3 user adaption layer based on IP.
RTP is real-time transmission protocol. It provides CS data IP-based
transmission
N-11
Iu-PS Interface (based on ATM)

Radio
Network
Layer
Transport
Network
Layer
Control Plane
User plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
User Plane
SCCP
GTP-U
MTP3-B
C
UDP
IP
SAAL NNI
AAL Type 5
ATM
Physical Layer

reserved.
Protocol Structure for Iu PS

p The Iu PS protocol structure is represented in above slide. Again, a
common ATM transport is applied for both User and Control Plane.
Also the physical layer is as specified for Iu CS.
Iu PS Control Plane Protocol Stack
p The Control Plane protocol stack consists of RANAP, on top of
Broadband (BB) SS7 (Signaling System #7) protocols. The
applicable layers are the Signaling Connection Control Part (SCCP),
the Message Transfer Part (MTP3-b) and SAAL-NNI (Signaling
ATM Adaptation Layer for Network to Network Interfaces).
Iu PS Transport Network Control Plane Protocol Stack
p The Transport Network Control Plane is not applied to Iu PS. The
setting up of the GTP tunnel requires only an identifier for the tunnel,
and the IP addresses for both directions, and these are already
included in the RANAP RAB Assignment messages.
Iu PS User Plane Protocol Stack
p In the Iu PS User Plane, multiple packet data flows are multiplexed
on one or several AAL5 PVCs. The GTP-U (User Plane part of the
GPRS Tunneling Protocol) is the multiplexing layer that provides
identities for individual packet data flow. Each flow uses UDP
connectionless transport and IP addressing.
N-12
Iu-PS Interface (based on IP)

Radio
Network
Layer
Transport
Network
Layer
Control Plane
User plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
User Plane
SCCP
M3UA
GTP-U
SCTP
UDP
IP
IP
DATA LINK
DATA LINK
Physical Layer

reserved.
SCTP is streaming control transmission protocol. It is a reliable transport

protocol operating on top of IP.
M3UA is MTP3 user adaption layer based on IP.
N-13
Iub Interface (based on ATM)

Radio
Network
Layer
User plane
Control Plane
NBAP
NCP
Iub FP
CCP
Transport Network
Control Plane
Transport
Network
Layer
Transport Network
User Plane
ALCAP
ALCAP
Transport Network
User Plane
SAAL UNI
SAAL UNI
AAL2 PATH
ATM
Physical Layer

reserved.
l
l
The Iub interface is the terrestrial interface between NodeB and RNC. The
Radio Network Layer defines procedures related to the operation of the
NodeB. The Transport Network Layer defines procedures for establishing
physical connections between the NodeB and the RNC.
The Iub application protocol, NodeB application part ( NBAP ) initiates the
establishment of a signaling connection over Iub . It is divided into two
essential components, CCP and NCP.
NCP is used for signaling that initiates a UE context for a dedicated UE or
signals that is not related to specific UE. Example of NBAP-C procedure
are cell configuration , handling of common channels and radio link setup
CCP is used for signaling relating to a specific UE context.
SAAL is an ATM Adaptation Layer that supports communication between
signaling entities over an ATM link.
The user plane Iub Frame Protocol ( FP ), defined the structure of the
frames and the basic in band control procedure for every type of transport
channel. There are DCH-FP, RACH-FP, FACH-FP, HS-DSCH FP and
PCH FP.
N-14
Iub Interface (based on IP)

Radio
Network
Layer
NBAP
Iub FP
CCP
NCP
Transport
Network
Layer
User plane
Control Plane
Transport Network
User Plane
Transport Network
User Plane
SCTP
UDP
IP
IP
DATA LINK
DATA LINK
Physical Layer

reserved.
N-15
Iur Interface (based on ATM)

Radio
Network
Layer
Control Plane
User plane
RNSAP
Iur Data
Stream
Transport Network
User Plane
Transport
Network
Layer
Transport Network
Control Plane
Transport Network
User Plane
ALCAP
ALCAP
SCCP
A
MTP3-B
SAAL NNI
MTP3-B
SAAL NNI
AAL2 PATH
ATM
Physical Layer

reserved.
Iur interface connects two RNCs. The protocol stack for the Iur is shown in
above slide.
The RNSAP protocol is the signaling protocol defined for the Iur interface.
N-16
Iur Interface (based on IP)

Radio
Network
Layer
Control Plane
User plane
RNSAP
Iur Data
Stream
Transport Network
User Plane
Transport Network
User Plane
Transport
Network
Layer
SCCP
M3UA
UDP
SCTP
IP
IP
DATA LINK
DATA LINK
Physical Layer

reserved.
Contents

reserved.
N-17
N-18
SRNC / DRNC
CN
SRNC
DRNC
Interface
Data
l
SRNC and DRNC are concepts for a connected UE.
The SRNC handles the connection to one UE, and may borrow radio
resources of a certain cell from the DRNC.
Drift RNCs support the Serving RNC by providing radio resources
A UE in connection state has at least one and only one SRNC, but can
has 0 or multiple DRNCs

reserved.
Inside the UTRAN, the RNCs of the Radio Network Subsystems can be
interconnected together through the Iur. Iu(s) and Iur are logical interfaces. Iur can
be conveyed over direct physical connection between RNCs or virtual networks
using any suitable transport network .
For each connection between User Equipment and the UTRAN, One RNC is the
Serving RNC. When required, Drift RNCs support the Serving RNC by providing
radio resources. The role of an RNC (Serving or Drift) is on a per connection basis
between a UE and the UTRAN.
N-19
RAB, RB and RL
RAB
RB
RNC
UE
CN
RL
NodeB
UTRAN

reserved.
RAB: The service that the access stratum provides to the non-access stratum for
transfer of user data between User Equipment and CN.
RB: The service provided by the layer2 for transfer of user data between User
Equipment and Serving RNC.
RL: A "radio link" is a logical association between single User Equipment and a
single UTRAN access point. Its physical realization comprises one or more radio
bearer transmissions.
N-20
UE Working Modes and States

l
Idle Mode
Connected Mode
p
CELL_DCH
CELL_FACH
CELL_PCH
URA_PCH

reserved.
If RRC connection does not exit between UE and RNC, then the UE is in idle mode.
If RRC connection exits between UE and RNC, then the UE is in connected mode.
Based on UE mobility and activity UE in connected mode may be allocated to four

different states: CELL_DCH, CELL_FACH, CELL_PCH and URA_PCH.
The UE leaves the connected mode and returns to idle mode when the RRC
connection is released or at RRC connection failure.
N-21
Idle Mode
l
The UE has no relation to UTRAN, only to CN. For data

transfer, a signaling connection has to be established.
UE camps on a cell
p
It enables the UE to receive system information from the PLMN
UE can monitor PICH of a cell for paging
The idle mode tasks can be divided into three processes:

p
PLMN selection and reselection
Cell selection and reselection
Location registration

reserved.
When a UE is switched on, a public land mobile network (PLMN) is selected and
the UE searches for a suitable cell of this PLMN to camp on.
The UE searches for a suitable cell of the chosen PLMN and chooses that cell to
provide available services, and tunes to its control channel. This choosing is known
as "camping on the cell". The UE will, if necessary, then register its presence, by
means of a NAS registration procedure, in the registration area of the chosen cell.
If the UE finds a more suitable cell, it reselects onto that cell and camps on it. If the
new cell is in a different registration area, location registration is performed.
N-22
Connected Mode
l
When UE is in connected mode

p
The UE position can be known on different levels:

n
Cell level (CELL_DCH/CELL_FACH/CELL_PCH)
UTRAN Registration Area (URA) level (URA_PCH)
The UE can use different types of channels in connected mode

n
Dedicated transport channels (CELL_DCH)
Common transport channels (CELL_FACH)

reserved.
Assuming that there exists an RRC connection, there are two basic families of RRC
connection mobility procedures, URA updating and handover. Different families of
RRC connection mobility procedures are used in different levels of UE connection
(cell level and URA level):
p
URA updating is a family of procedures that updates the UTRAN registration

area of a UE when an RRC connection exists and the position of the UE is
known on URA level in the UTRAN;
Handover is a family of procedures that adds or removes one or several
radio links between one UE and UTRAN when an RRC connection exists
and the position of the UE is known on cell level in the UTRAN.
Which type of transport channel is used by UE in connected mode is decided by

RNC according to the UE activity.
N-23
Connected Mode
l
Cell-DCH
p
In active state
Communicating via its dedicated channels
UTRAN knows which cell UE stays in

reserved.
If there is huge data to be transmitted, it must allocate dedicated channel. Thus UE

will be in Cell-DCH. UE in Cell-DCH state is communicating via DCH (downlink and
uplink) with UTRAN.
N-24
Connected Mode
l
Cell-FACH
p
In active state
Few data to be transmitted both in uplink and in downlink.

There is no need to allocate dedicated channel for this UE
Downlink uses FACH and uplink uses RACH
UE needs to monitor the FACH for its information
UTRAN knows which cell the UE stays in

reserved.
If there is only few data to be transmitted, there is no need to allocate dedicated

channel. Thus UE will be in Cell-FACH. UE in Cell-FACH state is communicating
via FACH (downlink) and RACH (uplink) with UTRAN. UE need to monitor the
FACH for its relative information because FACH is shared for all users in the cell.
N-25
Connected Mode
l
Cell-PCH
p
No data to be transmitted or received
Monitor PICH, to receive its paging
UTRAN knows which cell the UE stays in
UTRAN has to update cell information of UE when UE roams

to another cell
Lower the power consumption of UE

reserved.
If UE has no data to be transmitted or received, UE will be in Cell-PCH or URAPCH. In these two states, UE needs to monitor PICH,to receive its paging. UTRAN
knows which cell or URA UE is now in. The difference between Cell-PCH and
URA-PCH is that UTRAN update UE information only after UE which is in URAPCH state has roamed to other URA.
UTRAN have to update cell information of UE when UE roams to another cell. UE

migrates to cell-FACH state to complete the cell update. If there is also no data to
be transmitted or received, UE is back to CELL-PCH state after cell update. If the
cell update times in a fixed time reach a preset value, UTRAN will let UE migrate to
URA-PCH. URA is an area of several cells.
N-26
Connected Mode
l
URA-PCH
p
No data to be transmitted or received
Monitor PICH, to receive its paging
UTRAN only knows which URA (which consists of multiple

cells) that UE stays
UTRAN updates UE information only after UE has roamed to

other URA
A better way to reduce the resource occupancy and signaling

transmission

reserved.
It is the same as the CELL-PCH state. UE should migrate to CELL-FACH state to

complete the URA update.
N-27
UE Working Modes and States

- Reduce activity further
- Avoid unnecessary
signaling
RRC Connection
- Reduce activity, DRX,

and save power
URA_PCH
CELL_PCH
CELL_DCH
CELL_FACH
- Dedicated channel
- Common service,
such as voice
- Common channel
- PS service with few
data to transmit
IDLE
DEAD
- Monitor paging channel

- Cell re-selection
- Scan networks (PLMN)

- Camp on a cell

reserved.
This is the UE states figure. These states are significant only for UTRAN and UE.
They are transparent to CN. Lets focus on the switch between the states.
Contents

reserved.
N-28
Contents
3.1 System Information Broadcast
3.2 Paging
3.3 Call Process
3.4 Handover

reserved.
N-29
N-30
System Information Broadcast Flow

UE
NodeB
RNC
1. System Information Update

Request
2. System Information Update
Response
3. System Information

reserved.
Introduction of System Information

l
MIB:
PLMN tag
Scheduling information for SB
(Scheduling Block)
Scheduling information for
SIB (System Information Block)

l
SB1: scheduling information for
SIB
l
SB2: scheduling information for
SIB (extended)

reserved.
N-31

l
SIB1: System information for NAS and the timer/counter for

UE
SIB2: URA information
SIB3: Parameters for cell selection and cell re-selection
SIB4: Parameters for cell selection and cell re-selection while UE

is in connected mode
SIB5: Parameters for the common physical channels of the

cell
SIB6: Parameters for the common physical channels of the cell

while UE is in connected mode

reserved.
N-32

l
SIB7: uplink interference level and the refreshing timer
SIB8: the CPCH static information
SIB9: the CPCH dynamic information
SIB10: information to be used by UEs having their DCH controlled

by a DRAC procedure
SIB11: measurement controlling information
SIB12: measurement controlling information in connected mode

reserved.
N-33

l
SIB13: ANSI-41 system information
SIB14: the information in TDD mode
SIB15: the position service information
SIB16: the needed pre-configuration information for handover

from other RAT to UTRAN
SIB17: the configuration information for TDD
SIB18: the PLMN identities of the neighboring cells to be used in

shared networks to help with the cell reselection process

reserved.
N-34
System Information Block Type 1

l
System information type 1

p
The NAS system information
CS domain DRX: K=6, then DRX

period is 2^k= 2^6= 64TTI=640 ms
PS domain DRX: K=6, then DRX

period is 2^k=2^6=64TTI =640 ms

reserved.
N-35

l
System info type 2

p
URA information

reserved.
N-36

l
The references for cell selection

and re-selection
p
Qhyst2s
Sintrasearch
Sintersearch
Sinterratsearch
Qqualmin
Qrxlemin
T reselection
Max Allowed UE TX power

reserved.
N-37

l
The configuration information for

the following physical channels
and the counterpart transport
channels
p
PCCPCH
SCCPCH
PICH
AICH
PRACH

reserved.
N-38
System Information Block Type 7 and 11

l
System info type 7

p
Including the UL interference level which is used for open loop power
control
Including the Expiration Time Factor which is used for refreshing the
SIB7 periodically
System info type 11

p
The neighbor cell information for cell re-selection in IDLE mode

reserved.
N-39
Contents
3.2 Paging
3.3 Call Process
3.4 Handover

reserved.
N-40
N-41
Paging Initiation
l
CN initiated paging
l
Establish a signaling connection
UTRAN initiated paging

l
Trigger the cell update procedure
Trigger reading of updated system information

reserved.
For CN originated paging:

p
In order to request UTRAN connect to UE, CN initiates the paging procedure,

transmits paging message to the UTRAN through Iu interface, and UTRAN transmits
the paging message from CN to UE through the paging procedure on Uu interface,
which will make the UE initiate a signaling connection setup process with the CN.
For UTRAN originated paging:

p
UE state transition: In order to trigger UE in the CELL_PCH or URA_PCH state to

carry out state transition (for example, transition to the CELL_FACH state), the
UTRAN will perform a paging process. Meanwhile, the UE will initiate a cell update
or URA update process, as a reply to the paging.
When the cell system message is updated: When system messages change, the
UTRAN will trigger paging process in order to inform UE in the idle, CELL_PCH or
URA_PCH state to carry out the system message update, so that the UE can read
the updated system message.
N-42
Paging Type 1
l
If UE is in CELL_PCH,URA_PCH or IDLE statethe paging

message will be transmitted on PCCH with paging type 1
CN
RNC1
RNC2
NODEB1.1
NODEB2.1
UE
PAGING
RANAP
RANAP
RANAP
PAGING
RANAP
PCCH: PAGING TYPE 1
PCCH: PAGING TYPE 1

reserved.
Paging type 1:
p
The message is transmitted in one LA or RA according to LAI or RAI.
After calculating the paging time, the paging message will be transmitted at that time
If UE is in CELL_PCH or URA_PCH state, the UTRAN transmits the paging

information in PAGING TYPE 1 message to UE. After received paging message, UE
performs a cell update procedure to transit state to CELL_FACH.
As shown in the above figure, the CN initiates paging in a location area (LA), which is
covered by two RNCs. After receiving a paging message, the RNC searches all the cells
corresponding to the LAI, and then calculates the paging time, at which it will send the
PAGING TYPE 1 message to these cells through the PCCH.
N-43
Paging Type 2
l
If UE is in CELL_DCH or CELL_FACH statethe paging

message will be transmitted on DCCH with paging type 2
CN
SRNC
UE
PAGING
RANAP
RANAP
DCCH: PAGING TYPE 2

RRC
RRC

reserved.
Paging type 2:
p
If UE is in CELL_DCH or CELL_FACH statethe paging message will be

transmitted on DCCH with paging type 2
The message will be only transmitted in a cell
As shown in the above figure, if the UE is in the CELL_-DCH or CELL_FACH state, the
UTRAN will immediately transmit PAGING TYPE 2 message to the paged UE on DCCH
channel.
Contents
3.2 Paging
3.3 Call Process
3.4 Handover

reserved.
N-44
Introduction of Call Process

l
In WCDMA system, a call process includes the following basic

signaling flows:
p
RRC connection flow
Direct transfer message flow
Authentication flow (optional)
Security flow (optional)
RAB establish flow
Call proceeding
NAS signaling before correlative bearer release
Correlative bearer release

reserved.
N-45
N-46
RRC Connection Establishment Flow (CCH)

UE
NodeB
SRNC
1. RRC Connection Request
2. RRC Connection Setup
3. RRC Connection Setup Complete

reserved.
In the idle mode, when the non-access layer of the UE requests to establish a
signaling connection, the UE will initiate the RRC connection procedure. Each UE
has up to one RRC connection only.
When the SRNC receives an RRC CONNECTION REQUEST message from the
UE, the Radio Resource Management (RRM) module of the RNC determines
whether to accept or reject the RRC connection request according to a specific
algorithm. If accepting the request, the RRM module determines whether to set up
the RRC connection on a Dedicated Channel (DCH) or on a Common Channel
(CCH) according to a specific RRM algorithm.
Description:
p
The UE sends an RRC CONNECTION REQUEST message to the SRNC

through the uplink CCCH, requesting the establishment of an RRC
connection.
Based on the RRC connection request cause and the system resource state,
the SRNC decides to establish the connection on the common channel.
The SRNC sends an RRC CONNECTION SETUP message to the UE
through the downlink CCCH. The message contains the information about
the CCH.
The UE sends an RRC CONNECTION SETUP COMPLETE message to the
SRNC through the uplink CCCH.
N-47
RRC Connection Establishment Flow (DCH)

UE
NodeB
SRNC
1. RRC Connection Request

2. Radio Link Setup Request
3. Radio Link Setup Response
4. ALCAP Iub Data Transport
Bearer Setup
5. RRC Connection Setup
6. RRC Connection Setup Complete

reserved.
Typically, an RRC connection is set up on the DCH.
Description:
p
The UE sends an RRC Connection Request message via the uplink CCCH
to request to establish an RRC connection.
Based on the RRC connection request cause and the system resource state,
the SRNC decides to establish the connection on the dedicated channel, and
allocates the RNTI and L1 and L2 resources.
The SRNC sends a Radio Link Setup Request message to Node B,
requesting the Node B to allocate specific radio link resources required by
the RRC connection.
After successfully preparing the resources, the Node B responds to the
SRNC with the Radio Link Setup Response message.
The SRNC initiates the establishment of Iub user plane transport bearer with
the ALCAP protocol and completes the synchronization between the RNC
and the Node B.
The SRNC sends an RRC Connection Setup message to the UE in the
downlink CCCH.
The UE sends an RRC Connection Setup Complete message to the SRNC
in the uplink DCCH.
N-48
RRC Connection Setup Causes and corresponding bear:
ID
Name
Recommended value
ORIGCONVCALLEST
Originating Conversational Call
DCH_13.6K_SIGNALLING
ORIGSTREAMCALLEST
Originating Streaming Call
ORIGINTERCALLEST
Originating Interactive Call
ORIGBKGCALLEST
Originating Background Call
ORIGSUBSTRAFFCALLEST
Originating Subscribed traffic Call
TERMCONVCALLEST
Terminating Conversational Call
TERMSTREAMCALLEST
Terminating Streaming Call
TERMINTERCALLEST
Terminating Interactive Call
TERMBKGCALLEST
Terminating Background Call
EMERGCALLEST
Emergency Call RRC establish type
INTERRATCELLRESELEST
Inter-RAT cell re-selection
DCH_3.4K_SIGNALLING
INTERRATCELLCHGORDER
EST
Inter-RAT cell change order
DCH_3.4K_SIGNALLING
REGISTEST
Registration
DETACHEST
Detach
FACH
ORIGHIGHPRIORSIGEST
Originating High Priority Signaling
ORIGLOWPRIORSIGEST
Originating Low Priority Signaling
FACH
CALLREEST
Call re-establishment
DCH_3.4K_SIGNALLING
TERMHIGHPRIORSIGEST
Terminating High Priority Signaling
TERMLOWPRIORSIGEST
Terminating Low Priority Signaling
FACH
TERMCAUSEUNKNOWN
Terminating cause unknown
FACH
DEFAULTEST
Spare RRC establish
DCH_3.4K_SIGNALLING
N-49
Direct Transfer Message Flow
In Iu interface, radio network layer reports the RANAP

information and NAS information. NAS information is
taken as directed message in RANAP information.

reserved.
After the RRC connection between the UE and the UTRAN is successfully set up,
the UE sets up a signaling connection with the CN via the RNC for NAS information
exchange between the UE and the CN, such as authentication, service request and
connection setup. This is also called the NAS signaling setup procedure.
1. The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through

the RRC connection. The message contains the initial NAS information to be sent
to the CN by the UE.
2. The SRNC receives the INITIAL DIRECT TRANSFER message from the UE
and sends an INITIAL UE MESSAGE to the CN through the Iu interface. The
INITIAL UE MESSAGE contains the NAS information to be sent to the CN by the
UE. The content of the NAS information is CM SERVICE REQUEST.
3. If the signaling connection is set up, CN will send COMMON ID message to

SRNC.
Common ID

reserved.
COMMON ID includes the IMSI of the UE.
N-50
N-51
Authentication and Security Flow

UE
SRNC
CN
1. Direct Transfer (Authentication

Request)
2. Downlink Direct Transfer
3. Uplink Direct Transfer
4. Direct Transfer (Authentication
Response)
5. Security Mode Command
Complete

Complete

reserved.
Authentication is used for the validity of CN and UE.
Security flow includes the encrypt process and integrity protection.
1. The CN sends to the SRNC a DIRECT TRANSFER message, indicating

AUTHENTICATION REQUEST.
2. The SRNC transparently sends the contents of the DIRECT TRANSFER

message to the UE through a DOWNLINK DIRECT TRANSFER message.
3. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4. The SRNC transparently sends the contents of the UPLINK DIRECT

TRANSFER message to the CN through a DIRECT TRANSFER message,
indicating AUTHENTICATION RESPONSE. If the UMTS Subscriber Identity
Module (USIM) regards that the authentication succeeds, the UE returns a
message with an XRES Information Element (IE).
5. The CN sends to the SRNC a SECURITY MODE COMMAND message to

initiate the security mode control procedure. The message contains the information
about the supported ciphering and integrity protection algorithms.
6. The SRNC sends a SECURITY MODE COMMAND message to the UE to inform

the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
N-52
7. The UE sends a response message to the SRNC.

p
If the integrity protection and ciphering algorithms are configured

successfully, the UE sends a SECURITY MODE COMMAND COMPLETE
message to the SRNC. The SRNC then sends to the CN a SECURITY
MODE COMMAND COMPLETE message, containing the information about
the integrity protection and ciphering algorithms that the UE uses.
If the UE does not support the integrity protection and ciphering algorithms,
the UE sends to the SRNC a SECURITY MODE COMMAND FAILURE
message that contains the error information and the reason for the failure.
The SRNC then sends a SECURITY MODE COMMAND REJECT message
to the CN.
N-53
Call Setup Flow

UE
SRNC
CN

2. Direct Transfer (Setup)
3. Direct Transfer (Call Proceeding)
5. RAB Establishment
6. Direct Transfer (Alerting)
8. Direct Transfer (Connect)
11. Direct Transfer (Connect
Acknowledge)
reserved.
1. The UE sends to the SRNC an UPLINK DIRECT TRANSFER message that contains the
number of the callee and the information about the bearing capability of the call.
2. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER
message to the CN through a DIRECT TRANSFER message.
3. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates
CALL PROCEEDING and contains the information about the negotiated bearing capability
of the call.
4. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
5. A Radio Access Bearer (RAB) is set up. For details, refer to next page.
6. When the callee rings, the CN sends to the SRNC a DIRECT TRANSFER message,
indicating ALERTING.
8. The CN sends to the SRNC a DIRECT TRANSFER message, indicating CONNECT. This
means the callee has answered the call.
10. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
11. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER
message to the CN through a DIRECT TRANSFER message, indicating CONNECT
ACKNOWLEDGE.
N-54
RAB Establishment Flow

reserved.
The RAB refers to the user plane bearer that is used to transfer voice, data and
multimedia services between the UE and the CN. The UE needs to complete the
RRC connection establishment before setting up the RAB. RAB is the carrier which
is provided by AS for NAS. RAB establishment flow mainly includes the AAL2
PATH establishment of Iu and Iub interface, also includes the reconfiguration
process of radio resource.
The RAB setup is initiated by the CN and executed by the UTRAN. The basic
procedure is as follows:
p
1. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC

to initiate the RAB setup procedure.
2. The SRNC maps the Quality of Service (QoS) parameters for the RAB to
the ATM Adaptation Layer type 2 (AAL2) link characteristic parameters and
radio resource characteristic parameters. The ALCAP on the Iu interface
initiates a setup procedure for an Iu user plane transport bearer according to
the AAL2 link characteristic parameters. (For the PS domain, this step does
not exist.)
3. The SRNC sends to the NodeB a RADIO LINK RECONFIGURATION
PREPARE message, requesting the NodeB to prepare for adding one or
more DCHs to the existing radio links for carrying the RAB.
4. The NodeB allocates the appropriate resources and then sends a RADIO
LINK RECONFIGURATION READY message to the SRNC.
N-55
5. The Iub ALCAP at the SRNC initiates a setup procedure for an Iub user
plane transport bearer. The NodeB and the SRNC perform synchronization
by exchanging uplink and downlink synchronization frames in the DCH frame
protocol.
6. The SRNC sends a RADIO BEARER SETUP message to the UE.
7. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT
message to the NodeB.
8. After performing radio bearer setup, the UE sends a RADIO BEARER
SETUP COMPLETE message to the SRNC.
9. The SRNC sends an RAB ASSIGNMENT RESPONSE message to the
CN.
When the RAB is successfully established, a basic call is set up and the UE enters
the conversation process.
N-56
RRC Connection Release Flow (CCH)

reserved.
1. The SRNC sends an RRC CONNECTION RELEASE message to the UE

through the CCCH.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the

SRNC.
N-57
RRC Connection Release Flow (DCH)

reserved.
1. The SRNC sends an RRC CONNECTION RELEASE message to the UE

through the DCCH.
p
NOTE: The SRNC may send the RRC CONNECTION RELEASE message
several times to increase the probability of proper reception of the message
by the UE. The RRC SNs of these messages are the same. The number of
retransmissions and the transmission intervals are determined by the SRNC.
If the SRNC does not receive an RRC CONNECTION RELEASE
COMPLETE message from the UE after sending the RRC CONNECTION
RELEASE message for four times, the SRNC regards that the UE has
released the RRC connection.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the

SRNC.
3. The SRNC sends to the NodeB a RADIO LINK DELETION REQUEST message,
requesting the NodeB to delete the radio link resources in the NodeB.
4. After releasing the resources, the NodeB sends a RADIO LINK DELETION
RESPONSE message to the SRNC.
5. The SRNC uses the ALCAP protocol to initiate an Iub user plane transport
bearer release procedure.
N-58
NAS Signaling (CS)

MSC
UE
MSC
UE
Paging
RRC and NAS signaling Connection Setup
RRC and NAS signaling Connection Setup
CM Service Request
Authentication Request
Authentication Response
Security Mode Command
Security Mode Command Complete
Setup
Call Proceeding
RAB Assignment
Paging Response
Authentication Request
Authentication Response
Security Mode Command Complete
Setup
Call Confirmed
RAB Assignment
Alerting
Alerting
Connect
Connect
Connect ACK
Connect ACK
Disconnect
Disconnect
Release
Release
Release Complete
Release Complete
UE Outgoing Call
UE Terminating Call

reserved.
Authentication and security flow are optional.
CN does not need to the CM Service Response if the security mode is used.
N-59
UE to UE CS Call Process (1)

UE1
RRC Connection
Setup
NAS Signaling
Setup
NodeB1
RNC1
CN
RNC2
NodeB2
UE2
RRC Connection Req

RL Setup Req
RL Setup Rsp
ALCAP Iub Data
Transport Bearer Setup
RRC Connection Setup
Cmp
Initial DT
DL DT
UL DT
Authentication
and Security Flow
Initial UE
Message (CM
Service Req)
DT
(Authentication
Req)
DT
(Authentication
Rsp)
Common ID
Security Mode Cmd

Security Mode Cmp
Security Mode
Cmd
Security Mode
Cmp
UL DT
DT (Setup)
NAS Signaling
DL DT
DT (Call
Proceeding)
RAB Ass Req
Paging
Paging Type 1
RRC Connection Req
Iu-CS AAL2 Setup

RL Recfg Prep
RAB
Establishment
RL Recfg
Ready
ALCAP Iub Data
RL Setup Req
RL Setup Rsp
ALCAP Iub Data
RB Setup
RL Recfg
Commit
RB Setup Cmp
RRC Connection Setup Cmp
RAB Ass Rsp
N-60

UE1
NodeB1
RNC1
CN
RNC2
NodeB2
Initial DT
Initial UE
Message
(Paging Rsp)
DT
(Authentication
Req)
DL DT
UL DT
DT
(Authentication
Rsp)
Common ID
Security Mode
Cmd
Security Mode Cmd

Security Mode Cmp
Security Mode
Cmp
DT (Setup)
DL DT
UL DT
DT (Call
Confirm)
RAB Ass Req
Iu-CS AAL2 Setup
RL Recfg Prep
RL Recfg
Ready
ALCAP Iub Data
RB Setup
RL Recfg
Commit
RB Setup Cmp
RAB Ass Rsp

UL DT
DT (Alerting)
DT (Alerting)
UL DT
DL DT
NAS
Signaling
DT (Connect)
DT (Connect)
DL DT
UL DT
DT (Connect
Acknowlege)
DT (Connect
Acknowledge)
DL DT
UE2
N-61
Ass: Assignment
Cmp: Complete
Rel: Release
Rsp: Response
UL: Uplink
CM: Call Management

DL: Downlink
Req: Request
Prep: Prepare
Cmd: Command
DT: Direct Transfer
RL: Radio Link
Recfg: Reconfiguration
N-62
PS Call Process
UE1
NodeB1
RNC1
CN
RRC Connection Request

RRC Connection
Setup
Radio Link Setup Request

Radio Link Setup Response
ALCAP Iub Data Transport
Bearer Setup
RRC Connection Setup Complete
NAS Signaling
Setup
Initial Direct Transfer
Initial UE Message
(Service Request)
DT (Authentication
Request)
DL DT
UL DT
DT (Authentication
Response)
Authentication
and Security Flow
Common ID
Security Mode Complete
Security Mode Complete
NAS Signaling
(Call Setup)
DT (Service Accept)
DL DT
UL DT
DT (PDP Context
Request)
RAB Assignment
Request
Radio Link Reconfiguration
Prepare
Ready
RAB
Establishment
ALCAP Iub Data Transport

Bearer Setup
Radio Bearer Setup
Commit
Radio Bearer Setup Complete
NAS Signaling
(Call Setup)
RAB Assignment
Response
DT (PDP Context
Accept)
DL DT
Contents
3.2 Paging
3.3 Call Process
3.4 Handover

reserved.
N-63
N-64
Concepts about Soft Handover

l
Soft handover: the signals from different NodeBs are

merged in RNC
Softer handover: the signals from different cells, but from

the same NodeB are merged in NodeB

reserved.
In the WCDMA system, since the intra-frequency exists among neighboring cells,
the UE can communicate with the network via multiple radio links, and can select
one with good signal quality by comparison when these radio links are merged,
thus optimizing the communication quality. The soft handover can be conducted
only in the FDD mode. The soft handover falls into the following cases according to
the locations of the cells. The first case is the soft handover among difference cells
of the Node B. In this case, the radio links can be merged within the Node B or the
SRNC. If they are merged within the Node B, it is called softer handover. The
second case is the soft handover among different Node Bs within the same RNC
and among different RNCs.
An important issue during the soft handover is the merge of multiple radio links. In
the WCDMA system, the MACRO DIVERSITY technology is adopted for the merge
of the radio links, that is, the system compares the data from different radio links
based on certain standards (such as BER), and selects the data with better quality
to send to the upper layer.
Soft handover:
Selection combination in uplink
Maximum combination in downlink
Softer handover
p
Maximum combination in uplink and downlink
N-65
Soft Handover Flow (Intra-RNC)
NodeB
CN
CN
CN
SRNC
SRNC
SRNC
NodeB
Before Handover
NodeB
NodeB
During Handover
NodeB
NodeB
After Handover

reserved.
During the soft handover, two or more radio links are connected with UE, and data
in each RL are same.
The following are some key concepts about the neighboring cell in the soft
handover:
p
Active set: The set of cells currently used by the UE. The execution result of
the soft handover indicates the increase or decrease of the cells in the active
set.
Monitor set: The set of cells that are not in the active set but are being
observed by the UE based on the neighboring cell information from the
UTRAN. The UE measures the cells in the observation set. When the
measurement results satisfy certain conditions, the cells may be added to the
active set. Therefore, the observation set sometimes is also called the
candidate set.
Detected set: The set of cells that have been detected by the UE but do not
belong to the active set or the observation set. The UTRAN can request the
UE to report the measurement result of the detected set. Since the cells in
the detected set are not listed in the neighboring cell list, this set is also
called the unlisted set.
N-66
Soft Handover Flow

Core Network
RNC (SRNC)
Node B
AirBridge
AirBridge
AirBridge

reserved.
It is no handover in this slide, only one radio links is connected with UE.
N-67
Soft Handover Flow

Core Network
RNC (SRNC)
Node B
AirBridge
AirBridge
AirBridge
Merged in NodeB

reserved.
It is softer handover. During the handover, the cells in active set belong to one
NodeB. The NodeB uses the RAKE receiver to combine the data, and the UE also
combines the data in RAKE receiver.
N-68
Soft Handover Flow

Core Network
RNC (SRNC)
Node B
AirBridge
AirBridge
AirBridge
Merged in RNC

reserved.
It is soft handover. During the handover, the cells in active set belong to one RNC,
but different NodeBs. So the UE can combine the data in RAKE receiver. But in
uplink, the data are combined with selection combination in RNC.
N-69
Soft Handover Flow (SRNC-DRNC)

Core Network
Serving RNC
Drift RNC
Node B
AirBridge
AirBridge
AirBridge
Merged in SRNC

reserved.
It is soft handover. During the handover, the cells in active set belong to different
RNCs. So the UE can combine the data in RAKE receiver. But in uplink, the data
are combined with selection combination in SRNC.
N-70
Soft Handover Flow (SRNC Relocation)

Core Network
RNC
Serving RNC
Node B
AirBridge
AirBridge
AirBridge

reserved.
There is no handover, but the SRNC has been changed.
N-71
Typical Soft Handover Flow (L3 Signaling)

l
Soft handover is triggered by 1A/1B/1C or 1D event

UE
RNC
RRC Connection Setup Procedure
Measurement Control
Measurement Report (1A/1B/1C or 1D)
Active Set Update
Active Set Update Complete
Measurement Control

reserved.
The soft handover procedure comprises the following steps:

p
p
p
Based on the Measurement Control information from the RNC, the UE

measures the intra-frequency neighboring cells, and reports the
measurement result to the RNC via Measurement Report.
The RNC compares the reported measurement result with the set threshold
to decide the cells to be added and deleted.
(If some cells are to be added, the RNC notifies the Node B to get ready. )
The RNC notifies the UE to add and/or delete cells via the Active Set
Update message.
After the UE successfully update the active set, UE will send Active Set
Update Complete to inform RNC.
(if the cells are deleted, the Node B will be notified to release the
corresponding resources. )
After the soft handover, perhaps the measurement control information
changes, if it is, RNC will send new Measurement Control to UE.
The original communication is not affected during the soft handover procedure so
that smooth handover from a cell to another can be successfully completed.
N-72
Soft Handover Flow (Add Branch in AS)

UE
NodeB(new)
RNC
Measurement Report
Decision to
setup new RL
RL Setup Req.
RL Setup Rsp.
DL Synchronization
DL Synchronization
Active Set Update

reserved.
For adding a cell into Active Set, RNC will notify NodeB to prepare the new RL
before sending Active Set Update.
N-73
Soft Handover Flow (Del Branch from AS)

UE
NodeB (old)
RNC
Measurement Report
Decision to
delete a RL
Active Set Update
RL Deletion Req.
RL Deletion Rsp.

reserved.
For deleting a cell from Active Set, RNC sends Active Set Update to UE first. After
UE deleting the RL successfully, RNC will inform NodeB to delete the RL.
N-74
Hard Handover
NodeB
CN
CN
SRNC
SRNC
NodeB
Before Handover
NodeB
NodeB
After Handover
Radio Link can not exist simultaneously

reserved.
It is hard handover. The UE disconnects the original radio link, then connects to the
target cell. It happens in intra-frequency, inter-frequency and inter-RAT.
N-75
Intra-Frequency Hard Handover

l
Intra-Frequency hard handover is triggered by 1D event

UE
RNC
Measurement Control (Intra-freq)
Measurement Report (1D)
Decision to
setup new RL
Physical Channel Reconfiguration
Physical Channel Reconfiguration Complete
Measurement Control (Intra-Freq)

reserved.
N-76
Inter-frequency Handover
UE
RNC
Measurement Control (2D & 2F)
Measurement Report(2D)
Decision to enter
compress mode
Measurement Control (Inter-Freq)
Measurement Report
Decision to
setup new RL

reserved.
Description:
p
p
Step 1 to step 5 is similar with soft handover, the differences are:

The SRNC sends the Physical Channel Reconfiguration message carrying
the target cell information to the UE via the downlink DCCH.
After the UE hands over from the source cell to the target cell, the Node B of
the source cell detects the radio link communication failure and then sends
the Radio Link Failure Indication message to the SRNC, indicating the radio
link failure.
After successfully handing over to the target cell, the UE sends the Physical
Channel Reconfiguration Complete message to the SRNC via the DCCH,
notifying the SRNC that the physical cannel reconfiguration is complete.
The Node B where the source cell is deletes the radio link resources, and
then responds to the SRNC with the Radio Link Deletion Response message.
The SRNC adopts the ALCAP protocol to release the Iub interface transport
bearer of the SRNC and the Node B where the source cell is.
N-77
CS Domain Inter-RAT Handover Flow

(UMTS->GSM)

reserved.
l
l
l
l
After receiving measurement report (inter-RAT measurement) from UE, the SRNC
sends the 3G MSC a RANAP message RELOCATION REQUIRED if the condition
of Inter-RAT outgoing handover is met.
As indicated in the received message, the 3G MSC forwards this request to the 2G
MSC on the MAP/E interface through a MAP message PREPARE HANDOVER.
The 2G MSC forwards the request to the BSC. The message shown in the figure is
for reference only and is subject to the actual condition of the GSM.
The BSC responds to this request. The message shown in the figure is for
reference only and is subject to the actual condition of the GSM.
Once the initial procedures are completed in the 2G MSC/BSS, the 2G MSC
returns a MAP/E message PREPARE HANDOVER RESPONSE.
The 3G MSC sends the SRNC a RANAP message RELOCATION COMMAND.
The SRNC sends the UE an RRC message HANDOVER FROM UTRAN through
the existing RRC connection. This message may include information from one or
several other systems.
The BSC performs handover detection. The figure does not show such procedures
as GSM BSS synchronization. The message shown in the figure is for reference
only and is subject to the actual condition of the GSM.
The UE sends the BSC a HANDOVER COMPLETE message.
The BSC sends the MSC a HANDOVER COMPLETE message. The message
shown in the figure is for reference only and is subject to the actual condition of the
GSM.
After detecting the UE in the coverage area of the GSM, the MSC sends the CN a
MAP/E message SEND END SIGNAL REQUEST.
The CN sends the former SRNC an IU RELEASE COMMAND message,
requesting the former SRNC to release the allocated resource.
After the bearer resource is released in the UMTS, the former SRNC sends the CN
an IU RELEASE COMPLETE message.
N-78
PS Domain Inter-RAT Handover Flow (UMTS>GSM & UE in CELL_FACH, CELL_PCH or

URA_PCH)

reserved.
If the UE is in CELL_FACH, CELL_PCH or URA_PCH, the PS domain

handover from UMTS to GSM is actually a cell reselection procedure. The
procedure is:
p
1. The UE in CELL_FACH, CELL_PCH or URA_PCH find the signal

in UMTS is weak, so it triggers cell selection procedure and reselects
GSM network. In GSM network the UE reads system information and
triggers registration in GSM.
2. SRNC and SGSN perform context transfer procedure. The context

is transferred to SGSN and then to GSM PS domain. There are some
signaling procedures between 2G and 3G in this step but they are
ignored here.
3. The CN sends the former SRNC an IU RELEASE COMMAND

message, requesting the former SRNC to release the allocated
resource.
4. After the bearer resource is released in the UMTS, the former
SRNC sends the CN an IU RELEASE COMPLETE message.
N-79
PS Domain Inter-RAT Handover Flow

(UMTS->GSM & UE in CELL_DCH)

reserved.
1. The UE finds the signal in UMTS is weak and sends 2D measurement

report to the RNC.
2 & 3. After receiving 2D measurement report the SRNC triggers

compressed mode and sends inter-RAT measurement control to the UE.
4. After receiving inter-RAT measurement control the UE starts inter-RAT

measurement and sends measurement reports (periodical report or eventtriggered report) to the SRNC.
5. After receiving measurement reports the SRNC decides to trigger interRAT handover if the condition is OK. The RNC sends CELL CHANGE
ORDER message to the UE.
6. UE releases connection in UMTS and triggers reselection to GSM. The
NodeB sends RADIO LINK FAILURE to the SRNC.
l
l
7. SRNC and SGSN perform context transfer procedure. The context is

transferred to SGSN and then to GSM PS domain. There are some
signaling procedures between 2G and 3G in this step but they are ignored
here.
8 & 9. Iu connection between the SRNC and the SGSN is released.
10 & 11. The radio link is released.
Inter-RAT Handover Flow (GSM->UMTS)

reserved.
N-80
Thank you
www.huawei.com
N-81

WCDMA UTRAN Interface and Signaling Procedure ISSUE 1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

WCDMA UTRAN Interface and Signaling Procedure ISSUE 1

Caricato da

Copyright:

Formati disponibili

WCDMA UTRAN Interface and Signaling Procedure

Dont Print This Page

Course Version ISSUE

Copyright 2008 Huawei Technologies Co., Ltd. All rights Page0

Confidential Information of Huawei. No Spreading Without Permission

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com