SJ-20120319104909-005-ZXUR 9000 UMTS (V4.11.20) Signalling Description

ZXUR 9000 UMTS
Radio Network Controller

Signalling Description
Version: V4.11.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2012-04-17 First edition
Serial Number: SJ-20120319104909-005
Publishing Date: 2012-04-17 (R1.0)

About This Manual
Purpose
This manual describes the signalling procedures of the ZXUR 9000 UMTS radio network
controller product.
Target Groups
l System engineer
l Testing engineer
What is in This Manual
Chapter Summary
Chapter 1, UE States and Describes the UE states and signalling procedures related to paging.
Paging Procedures
Chapter 2, Radio Resource Describes the signalling procedures related to radio resource
Management Procedures management.
Chapter 3, Call Control Describes the signalling procedures related to call control.
Procedures
Chapter 4, HSPA Describes the signalling procedures related to HSPA.

Procedures
I
II
Contents
About This Manual ......................................................................................... I
Chapter 1 UE States and Paging Procedures .......................................... 1-1
1.1 UE States .......................................................................................................... 1-1
1.1.1 CELL_DCH State ..................................................................................... 1-1
1.1.2 CELL_FACH State ................................................................................... 1-1
1.1.3 URA_PCH State ...................................................................................... 1-2
1.2 Paging Procedures............................................................................................. 1-2
1.2.1 Performing Paging on the UE in Idle Mode or PCH State ............................ 1-2
1.2.2 Performing Paging on the UE in CELL_DCH or CELL_FACH State ............. 1-3
Chapter 2 Radio Resource Management Procedures............................. 2-1

2.1 RRC Connection Establishment Procedures ........................................................ 2-1
2.1.1 RRC Connection Established on a Dedicated Channel ............................... 2-1
2.1.2 RRC Connection Established on a Common Channel................................. 2-3
2.2 Signalling Establishment Procedures ................................................................... 2-3
2.3 RAB Establishment Procedures .......................................................................... 2-5
2.3.1 CELL_DCH - CELL_DCH ......................................................................... 2-5
2.3.2 CELL_FACH - CELL_DCH........................................................................ 2-6
2.3.3 RACH/FACH - RACH/FACH...................................................................... 2-8
2.4 Handover Procedures......................................................................................... 2-8
2.4.1 Soft Handover.......................................................................................... 2-8
2.4.2 Hard Handover....................................................................................... 2-13
2.4.3 Forward Handover.................................................................................. 2-14
2.4.4 Inter-system Handover ........................................................................... 2-17
2.5 Relocation Between RNCs................................................................................ 2-21
2.5.1 Soft Handover Relocation ...................................................................... 2-21
2.5.2 Hard Handover Relocation ...................................................................... 2-23
2.6 Security Mode Control ...................................................................................... 2-25
Chapter 3 Call Control Procedures........................................................... 3-1

3.1 UE Originating Call Establishment ....................................................................... 3-1
3.2 UE Terminating Call Establishment...................................................................... 3-3
3.3 RAB Procedures ................................................................................................ 3-4
3.3.1 RAB Establishment Procedures ................................................................ 3-4
3.3.2 RAB Release procedures.......................................................................... 3-5
I
3.3.3 RAB Modification Procedures.................................................................... 3-6
3.4 Call Release Procedures .................................................................................... 3-7
Chapter 4 HSPA Procedures ..................................................................... 4-1

4.1 Physical Shared Channel Reconfiguration ........................................................... 4-1
4.2 HSPA Serving Cell Change................................................................................. 4-2
Figures............................................................................................................. I
II
Chapter 1
UE States and Paging
Procedures
Table of Contents
UE States...................................................................................................................1-1
Paging Procedures.....................................................................................................1-2
1.1 UE States
UE supports two basic operating modes, idle mode and connected mode. After power on,
the UE stays in idle mode and is identified by non-access stratum identities such as IMSI,
TMSI, and P-TMSI. URAN, which does not save the information about the UE in idle mode,
can only page all UEs in a cell or all UEs on the same paging occasion.
When the UE completes the establishment of RRC connection, it will transit from idle
mode to connected mode, that is, entering the CELL_FACH or CELL_DCH state. The
UE in connected mode (also called in the RRC state) reflects the level of UE connection,
and which transport channels that can be used by the UE. When the RRC connection is
released, the UE transits from connected mode to idle mode.
The UE supports the following states when it is in connected mode:
l CELL_DCH
l CELL_FACH
l URA_PCH
1.1.1 CELL_DCH State

The CELL_DCH state is characterized by:
l A dedicated physical channel is allocated to the UE in the uplink and downlink.
l The UE is known on cell level according to its current active set.
l Dedicated transport channels, downlink and uplink shared transport channels, or a
combination of these channels can be used by the UE.
1.1.2 CELL_FACH State

The CELL_FACH state is characterized by:
l No dedicated transport channel is allocated to the UE.
l The UE continuously monitors one downlink FACH channel.
1-1
SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

ZXUR 9000 UMTS Signalling Description
l The UE is assigned a default common or shared transport channel in the uplink (such
as RACH) that it can use anytime during the access.
l The location of the UE is known by UTRAN on cell level according to the cell where
the UE last made a cell update.
1.1.3 URA_PCH State

The URA_PCH state is characterized by:
l No dedicated channel is allocated to the UE.
l The UE employs the discontinuous reception technology (DRX) to monitor the PCH
transport channel on a certain paging occasion.
l No uplink activity is permitted.
l The location of the UE is known by UTRAN on URA level according to the URA
assigned to the UE during the last URA update in the CELL_FACH state.
1.2 Paging Procedures

Upon receiving the paging message from one CN domain, UTRAN needs to decide
whether signalling connection is established between a UE and another CN domain. If not
established, the UTRAN can only know the serving cell where the UE locates currently,
and sends a PAGING TYPE 1 message to the UE on the paging control channel. If
established, the UTRAN can know that the UE in the CELL_DCH or CELL_FACH state
stays on which channel, and forwards the PAGING TYPE 2 message to the UE on the
dedicated channel.
1.2.1 Performing Paging on the UE in Idle Mode or PCH State

Signaling Procedure
The following figure illustrates how paging is performed for the UE in idle mode or in the
URA_PCH state on PCCH that is used to send paging messages to the selected UE.
1-2

Chapter 1 UE States and Paging Procedures
Figure 1-1 Paging the UE in Idle Mode or PCH State
UTRAN pages the UE by sending the PAGING TYPE 1 message on PCCH.
1.2.2 Performing Paging on the UE in CELL_DCH or CELL_FACH

State
Signalling Procedures
The following figure illustrates how paging is performed for the UE in connected mode
(the CELL_DCH or CELL_FACH state) on DCCH that is used to send dedicated paging
messages to the selected UE.
1-3

Figure 1-2 Paging the UE in CELL_DCH or CELL_FACH State
UTRAN pages the UE by sending the PAGING TYPE 2 message on DCCH.
1-4

Chapter 2
Radio Resource Management
Procedures
Table of Contents
RRC Connection Establishment Procedures ..............................................................2-1
Signalling Establishment Procedures..........................................................................2-3
RAB Establishment Procedures .................................................................................2-5
Handover Procedures ................................................................................................2-8
Relocation Between RNCs .......................................................................................2-21
Security Mode Control ..............................................................................................2-25
2.1 RRC Connection Establishment Procedures

When the non-access stratum requests for the setup of signalling connection, the UE in
idle mode will initiate the establishment of an RRC connection. Each UE supports up to
one RRC connection.
When SRNC receives the RRC CONNECTION REQUEST message, the radio resource
management module (RRM) of SRNC decides to accept or reject the RRC connection
request according to the specific algorithm. If the request is accepted, the SRNC
determines that the connection is established on the dedicated channel or common
channel. The procedures for RRC connection establishment vary from the channel used
by the establishment of RRC connection.
2.1.1 RRC Connection Established on a Dedicated Channel

The following figure illustrates the signalling procedures when an RRC connection is
established on a dedicated channel.
2-1

Figure 2-1 RRC Connection Established on a Dedicated Channel
1. The UE initiates the setup of an RRC connection by sending the RRC CONNECTION
REQUEST message on UL CCCH.
2. SRNC, according to the reason of RRC connection request and system resource
status, determines that the RRC connection is established on the dedicated channel,
and allocates the RNTI, L1, and L2 resources.
3. The SRNC sends a Radio Link Setup Request message to Node B for allocating the
specific radio link resources.
4. After the Node B prepares the resources successfully, it replies a Radio Link Setup
Response message to the SRNC.
5. The SRNC initiates the setup of Iub user-plane transport bearer by using the ALCAP
protocol, and implements the synchronization between the RNC and Node B.
6. On the DL CCCH, the SRNC sends the RRC CONNECTION SETUP message to the
UE.
7. On the UL DCCH, the UE sends the RRC Connection Setup Complete message to
the SRNC.
2-2

Chapter 2 Radio Resource Management Procedures
2.1.2 RRC Connection Established on a Common Channel

The following figure illustrates the signalling procedures for an RRC connection established
on a common channel.
Figure 2-2 RRC Connection Established on a Common Channel
1. The UE initiates the setup of an RRC connection by sending the RRC Connection
Request message on UL CCCH.
2. The SRNC, according to the reason of RRC connection request and system resource
status, determines that the RRC connection is established on a common channel, and
allocates the RNTI, L1, and L2 resources.
3. On the DL CCCH, the SRNC sends the RRC Connection Setup message to the UE.
4. On the UL DCCH, the UE sends the RRC Connection Setup Complete message to
the SRNC.
2.2 Signalling Establishment Procedures

Signalling establishment procedures, also called NAS signalling establishment
procedures, refer to the signalling connection between the UE and CN through an RNC
after an RRC connection is established successfully between the UE and UTRAN,. The
NAS signalling establishment procedures are for the UE interacting such NAS messages
with CN as authentication, service request, and connection establishment.
2-3

The following figure illustrates the signalling establishment procedures.
Figure 2-3 Signalling Establishment Procedures
1. After RRC connection is established, the UE forwards the Initial Direct Transfer
message to the RNC through the RRC connection. NAS message contents sent from
the UE to CN are carried in the Initial Direct Transfer message.
2. After receiving the Initial Direct Transfer message from the UE, the RNC sends the
SCCP Connection Request message (CR) to the CN through the lu interface. The
SCCP Connection Request message is the Initial UE Message sent from the RNC to
the CN, and carries the contents sent to the CN by the UE.
3. If the CN prepares to accept the connection request, it sends the SCCP connection
confirming message CC to the RNC to confirm the signalling connection establishment
success. The RNC confirms that the signalling connection is established successfully
after having received the message.
4. If the CN prepares to reject the connection request, it sends the SCCP connection
confirming message CC to the RNC to confirm the signalling connection establishment
failure. The RNC confirms that the establishment of signalling connection is failure
after having received the message, and then initiates the release of RRC connection.
2-4

2.3 RAB Establishment Procedures

RAB, which refers to the bearer at the user plane, is used to transmit voice, data, and
multimedia services between the UE and CN. The UE can establish RAB only after it has
set up an RRC connection.
According to the utilization status of radio resources, RAB establishment involves the
following three procedures:
l DCH-DCH: RRC uses DCH, and RAB uses the DCH.
l RACH/FACH-RACH/FACH: RRC uses CCH, and RAB uses the CCH.
l RACH/FACH-DCH: RRC uses CCH, and RAB uses DCH.
2.3.1 CELL_DCH - CELL_DCH

The assigned RAB can only be established on a dedicated transport channel when the
RRC state of UE is the CELL_DCH state.
The Node B and UE should not enable a new configuration parameter immediately
after receiving the configuration message released by the SRNC, but enable the new
configuration parameter simultaneously during the synchronization after obtaining the
synchronization time specified by the SRNC from the configuration message.
The following figure illustrates the procedure for reconfiguring radio links (CELL_DCH -
CELL_DCH synchronized) during the establishment of RAB.
Figure 2-4 RAB Establishment Procedures (CELL_DCH - CELL_DCH Synchronized)
2-5

1. The CN initiates the request for RAB establishment by sending the Radio Access
Bearer Assignment Request message to UTRAN.
2. After receiving the RAB establishment request, the SRNC maps the Qos parameters
of the RAB to the AAL2 link feature parameters and radio resource feature parameters.
The ALCAP on the lu interface initiates the user plane transmission bearer
establishment on the lu interface according to the AAL2 link feature parameters.
3. The SRNC sends a Radio Link Reconfiguration Prepare message to the Node B, to
require the Node B to prepare to add one or more RAB bearing DCHs on the radio link.
4. The Node B allocates corresponding resources and sends a Radio Link
Reconfiguration Ready message to the SRNC, indicating that the radio link
reconfiguration preparation is completed.
5. The SRNC initiates the establishment of user plane transport bearer of ALCAP at the
Iub interface. The Node B and SRNC establish synchronism by means of exchanging
the uplink synchronization and downlink synchronization frames of the DCH frame
protocol.
6. The SRNC sends the Radio Link Reconfiguration Commit message to the Node B.
7. The SRNC sends the Radio Bearer Setup message of the RRC protocol to the UE.
8. After implementing RB setup, the UE sends the Radio Bearer Setup Complete
message to the SRNC.
9. After receiving the Radio Bearer Setup Complete message, the SRNC sends the Radio
Access Bearer Assignment Response message to the CN. The RAB establishment
procedures ate completed.
2.3.2 CELL_FACH - CELL_DCH

When the RRC state of the UE is the CELL_FACH state, the RNC can, according to the
Qos parameters in the RAB assignment message, establish the assigned RAB on the
common channel RACH/FACH or the dedicated channel DCH.
The following figure illustrates the procedures for RAB established on a dedicated channel
when the UE's state is the CELL_FACH state.
2-6

Figure 2-5 RAB Establishment Procedures (CELL_DCH - CELL_DCH)
The ALCAP on the lu interface initiates the user plane transmission bearer establish-
ment on the lu interface according to the AAL2 link feature parameters.
3. The SRNC sends the Radio Link Setup Request message to the Node B, to require it
to establish new radio links.
4. After allocating corresponding resources, the Node B sends the Radio Link Setup
Response message to the SRNC, indicating that the radio link setup is completed.
5. The SRNC initiates the establishment of user plane transport bearer of ALCAP at the
Iub interface. The Node B and SRNC establish synchronism by means of exchanging
the uplink synchronization and downlink synchronization frames of the DCH frame
protocol.
Access Bearer Assignment Response message to the CN . The RAB establishment
procedures are completed.
2-7

2.3.3 RACH/FACH - RACH/FACH

The following figure illustrates the procedures for RAB established on a common channel
when the UE's state is the CELL_FACH state.
Figure 2-6 RAB Establishment Procedures (RACH/FACH - RACH/FACH)
The ALCAP on the lu interface initiates the user plane transmission bearer establish-
ment on the lu interface according to the AAL2 link feature parameters.
Access Bearer Assignment Response message to the CN . The RAB establishment
procedures are coimpleted.
2.4 Handover Procedures

2.4.1 Soft Handover
In the WCDMA system, common frequency exists in the neighboring cells, so the UE
can communicate with the network through several radio links. When performing macro
diversity combination on several radio links, the UE selects the link with better signal
quality, to optimize the communication quality.
2-8

Soft handover is performed in the following five steps:

1. According to the measurement control information given by an RNC, the UE measures
the neighboring cells with the same frequency, processes the measurement result, and
reports the result to the RNC.
2. According to the reported measurement result, the RNC confirms that which cells
should be added or deleted.
3. If some cells should be added, the RNC notifies the Node B to make preparations.
4. The RNC notifies the UE to add/delete cells through the active set update message.
5. After updating the active set successfully, the UE will notify the Node B to release
corresponding resources if some cells are deleted.
According to the utilization status of resources, the soft handover falls into the following
three types:
l Radio link addition
l Radio link deletion
l Radio link replacement
2.4.1.1 Radio Link Addition
The following figure illustrates the soft handover signalling procedures for radio link
addition, taking the Node B controlled by non-SRNC as an example.
Figure 2-7 Soft Handover (Radio Link Addition)
2-9

1. According to the utilization status of resources, the SRNC requests the DRNC for radio
resources by sending a RADIO LINK SETUP REQUEST message, to set up a radio
link in a new cell controlled by the DRNC.
2. If the requested resources are available, the DRNC sends the RADIO LINK SETUP
REQUEST message to the target Node B. The Node B starts the UL reception.
3. After allocating the requested resources successfully, the Node B reports the allocation
result to the DRNC by sending the RADIO LINK SETUP RESPONSE message.
4. The DRNC initiates the setup of Iub transport bearer by using the ALCAP protocol.
5. The Node B sends the RADIO LINK DELETION RESPONSE message to the SRNC.
6. The SRNC initiates the setup of Iur transport bearer by using the ALCAP protocol.
7. The SRNC sends the RRC message Active Set Update (Radio Link Addition) to the
UE on DCCH. The RRC message carries the RL information that needs to be added.
8. The UE adds corresponding RL information to the active set, and sends the RRC
message ACTIVE SET UPDATE COMPLETE back to the SRNC. The soft handover
procedures for radio link addition are completed.
2.4.1.2 Radio Link Deletion
deletion, taking the Node B controlled by non-SRNC as an example.
Figure 2-8 Soft Handover (Radio Link Deletion)
2-10

1. According to the utilization status of resources, the SRNC decides to delete one
radio link in DRNC by sending the RRC message ACTIVE SET UPDATE (Radio Link
Deletion) to the UE on DCCH. The message carries the RL contents that need to be
deleted.
2. The UE deactivates the DL reception of the radio link, deletes the radio link, and sends
the RRC message ACTIVE SET UPDATE COMPLETE to the SRNC.
3. The SRNC determines that the radio link to be deleted is at the DRNC side, and then
requests the DRNC for releasing the allocated radio resources by sending the RNSAP
message RADIO LINK DELETION REQUEST.
4. The DRNC requests Node B for releasing the allocated radio resources by sending
the NBAP message RADIO LINK DELETION REQUEST.
5. After allocating the requested resources successfully, the Node B reports the
allocation result to the DRNC by sending the NBAP message RADIO LINK DELETION
RESPONSE.
6. The DRNC initiates the release of Iub data transport bearer by using the ALCAP
protocol.
7. The DRNC sends the RNSAP message RADIO LINK DELETION RESPONSE to the
SRNC.
8. The SRNC initiates the release of Iub data transport bearer by using the ALCAP
protocol. The soft handover procedures for radio link deletion are completed.
2.4.1.3 Radio Link Replacement

The soft handover procedures for radio link replacement are needed when the maximum
number of branches allowed for the macro-diversity set is reached.
replacement, taking the Node B controlled by non-SRNC as an example.
2-11

Figure 2-9 Soft Handover (Radio Link Replacement)
1. According to the utilization status of resources, the SRNC requests the DRNC for radio
resources by sending a RADIO LINK SETUP REQUEST message, to set up a radio
link in a new cell controlled by the DRNC.
2. If the requested resources are available, the DRNC sends the RADIO LINK SETUP
REQUEST message to the target Node B. The Node B starts the UL reception.
3. After allocating the requested resources successfully, the Node B reports the allocation
result to the DRNC by sending the RADIO LINK SETUP RESPONSE message.
4. The DRNC initiates the setup of Iub transport bearer by using the ALCAP protocol.
5. The Node B sends the RNSAP message RADIO LINK DELETION RESPONSE to the
SRNC.
6. The SRNC initiates the setup of Iur transport bearer by using the ALCAP protocol.
7. The SRNC sends RRC message Active Set Update (Radio Link Addition) to the UE
on DCCH. The RRC message carries two pieces of RL information that need to be
replaced.
8. The UE completes the addition and deletion of corresponding RL, and sends the RRC
message ACTIVE SET UPDATE COMPLETE to the SRNC.
9. The SRNC requests the Node B for releasing the allocated radio resources by sending
the NBAP message RADIO LINK DELETION REQUEST.
10. After allocating the requested resources successfully, the Node B reports the
release result to the SRNC by sending the NBAP message RADIO LINK DELETION
RESPONSE.
11. The SRNC initiates the release of Iub and Iub bearer by using the ALCAP protocol.
2-12

2.4.2 Hard Handover

Hard handover means that the old connection between the UE and RNC is interrupted
before a new connection is established. It is only applicable to the UE in the Cell_DCH
state, changing the frequency band between the UE and UTRAN. In addition, it applies
to two different cells with the same frequency, and the swichover between FDD and TDD
modes.
According to the location relationship between the source cell and the target cell, the hard
handover includes:
1. Inter-cell handover within the same Node B
2. Inter-cell handover within different Node Bs of the same RNC
3. Inter-cell handover within different RNCs
The hard handover applies to the following signalling procedures at the Uu interface:
1. Physical channel reconfiguration
2. Transport channel reconfiguration
3. RB establishment
4. RB release
5. RB reconfiguration
The following figure, which takes physical channel reconfiguration as an example,
illustrates the signalling procedures for hard handover performed between different Node
Bs.
Figure 2-10 Hard Handover Procedure
2-13

1. The SRNC requests the target Node B for setting up one radio link by sending the
Radio Link Setup Request message.
2. The target Node B responds with a Radio Link Setup Response message, indicating
that the radio link is set up successfully.
3. The SRNC establishes the Iub transport bearer between itself and the target Node B
by using the ALCAP protocol, and implements FP synchronization.
4. The SRNC sends the Physical Channel Reconfiguration message that carries the
target cell information to UE on DCCH.
5. After the UE hands over from the source cell to the target cell, the source Node B
detects a failure on its radio links and sends the Radio Link Failure Indication message
to the SRNC.
6. After handing over to the target cell successfully, the UE sends the Physical Channel
Reconfiguration Complete message to the SRNC on DCCH, indicating that the
physical channel reconfiguration is completed.
7. The SRNC requests the source Node B for removing the radio links in the source cell
by sending the Radio Link Deletion Request message.
8. After deleting the radio link resources, the source Node B sends the Radio Link
Deletion Response message to the SRNC.
9. The SRNC releases the Iub transport bearer between itself and the source Node B.
2.4.3 Forward Handover

Forward handover is a part of the RRC connection mobility management, including cell
update and URA update. It is used to update UE's information at the UTRAN side when
the position of the UE changes, monitor the RRC connection, report failure, and forward
information. Both the cell update and URA update are initiated actively by the UE.
2.4.3.1 Cell Update

The UE in the CELL_FACH or the URA_PCH state may initiate cell update procedures.
The reason and procedures of cell update vary from the connection state of UE.
1. The following figure illustrates the procedures for cell update when periodical cell
update is necessary and UTRAN does not allocate a new CRNTI or a new URNTI
to the UE.
2-14

Figure 2-11 Periodical Cell Update Procedures
Signalling procedure description

a. The UE sends the CELL UPDATE message to the UTRAN on CCCH.
b. After receiving and processing the CELL UPDATE message, the UTRAN
responds to the UE with the CELL UPDATE CONFIRM message. The cell update
is completed after the UE has received the CELL UPDATE CONFIRM message.
2. The following figure illustrates the procedures for cell update with physical channel
reconfiguration.
Figure 2-12 Procedures for Cell Update With Physical Channel Reconfiguration
2-15

b. After receiving and processing the CELL UPDATE message, the UTRAN responds
to the UE with the CELL UPDATE CONFIRM message and waits for a response
message from the UE.
c. After receiving the CELL UPDATE CONFIRM message, the UE sends the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the
UTRAN. The cell update at the UE side is completed. The cell update is completed
after the UTRAN receives the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message sent by the UE.
3. The following figure illustrates the procedures for cell update with transport channel
reconfiguration.
Figure 2-13 Procedures for Cell Update With Transport Channel Reconfiguration

b. After receiving and processing the CELL UPDATE message, the UTRAN responds
to the UE with the CELL UPDATE CONFIRM message and waits for a response
message from the UE.
c. After receiving the CELL UPDATE CONFIRM message, the UE sends the
TRANSPORT CHANNEL RECONFIGURATION COMPLETE message to the
UTRAN. The cell update at the UE side is completed.The cell update is completed
after the UTRAN receives the TRANSPORT CHANNEL RECONFIGURATION
COMPLETE message sent by the UE.
2-16

2.4.3.2 URA Update

The UE initiates the procedures for URA update according to cell broadcast and the status
of the T306 timer, to ensure that the UE belongs to one and only one valid URA.
The UE is in the URA_PCH state (RRC connection is established).
The UE is within the serving cell , but T306 is timed out, so the UE initiates the procedures
for URA update.
The UE initiates the procedures for URA update if it detects that the URA is not in the URA
ID list of cell broadcast.
The following figure illustrates the procedures for URA update if the UTRAN does not
allocate a new CRNTI or a new URNTI to UE.
Figure 2-14 URA Update Procedures
Signalling procedures description

1. The UE sends the URA UPDATE message to the UTRAN on CCCH.
2. After receiving and processing the URA UPDATE message, the UTRAN responds to
the UE with the URA UPDATE CONFIRM message. The URA update at the UTRAN
side is completed. The URA update is completed after the UE having received the
URA UPDATE CONFIRM message.
2.4.4 Inter-system Handover

The WCDMA system supports a UE for performing handover between the UTRAN and
existing system like GSM/GPRS, such as handover to GSM under the network control
and UE performing cell selection to GPRS, including handover to UTRAN and handover
from the UTRAN. Hereafter takes the signallings in the UTRAN to describe the signalling
procedures for inter-system handover in four cases.
2-17

2.4.4.1 Handover to UTRAN
The following figure illustrates the procedures for handover to UTRAN.
Figure 2-15 Handover to UTRAN
1. The CN notifies the UTRAN of the information that a UE is to be handed over with the
Relocation Request message.
2. After the preparation of resources is completed, the UTRAN responds to the CN with
the Relocation Request Acknowledge message that carries the Handover To UTRAN
Command message, and then the target system forwards the Handover To UTRAN
Command message to the UE.
3. After successful handover to UTRAN, the UE sends the Handover to UTRAN Complete
message to the UTRAN.
2.4.4.2 Handover From UTRAN
The following figure illustrates the procedures for handover from UTRAN.
2-18

Figure 2-16 Handover From UTRAN
1. The UTRAN requests the target system to prepare for inter-system handover by
sending the Relocation Required message to the CN.
2. The CN sends the Relocation Command message to the UTRAN, indicating that the
target system has completed its preparation phase.
3. The UTRAN requests the UE to perform inter-system handover by sending the
Handover From UTRAN Command message.
2.4.4.3 UE Performing Cell Reselection From UTRAN
In the CS, there is no specific signalling for the UE to perform cell reselection from the
UTRAN. In the PS RAB that supports intact transition, there is a group of signallings for
forwarding the cached packet data.
2-19

Figure 2-17 Cell Reselection From UTRAN
1. The CN sends the SRNS Context Request message to the UTRAN, to notify the
UTRAN to convey the GTP-U and PDCP serial number information needed by data
transmission.
2. The UTRAN responds to the CN with the SRNS Context Response message that car-
ries the start serial number of data transmission prepared for each RAB.
3. The CN sends the SRNS Data Forward Command message to the UTRAN, to notify
the UTRAN to enable the transmission of cached packet data.
2.4.4.4 UE Performing Cell Reselection to UTRAN
The following figure illustrates the procedures for handover to UTRAN.
2-20

Figure 2-18 Cell Reselection to UTRAN
1. The UE selects one UTRAN cell to read the system information, and initiates the setup
of NAS signalling connection.
2. The NAS signalling connection is to transmit NAS message between the UE and CN.
3. The CN initiates the RAB establishment procedures.
2.5 Relocation Between RNCs

The relocation between RNCs means that the serving RNC of UE changes from one RNC
to another RNC. It includes the soft handover relocation and hard handover relocation
according to the different positions of the UE when relocation occurs.
2.5.1 Soft Handover Relocation

The prerequisite for the occurrence of soft handover relocation is that the UE is accessed
from one and only one DRNC. The relocation is also called UE not involved relocation
because it does not need the participation of the UE.
The following figure illustrates the signalling procedures for soft handover relocation.
2-21

Figure 2-19 Signalling Procedures for Soft Handover Relocation
1. The SRNC sends the Relocation Required message to the SGSN.
2. The SRNC sends the Relocation Required message to the MSC.
3. The SGSN requests the DRNC to prepare for relocation by sending the Relocation
Request message.
4. The MSC requests the DRNC to prepare for relocation by sending the Relocation
Request message.
5. Through the ALCAP protocol, the SRNC initiates the user plane transmission bearer
establishment on the lub interface of CS.
6. The DRNC sends the Relocation Request Acknowledge message to the SGSN to
notify it that the preparation of resources required by relocation is completed.
7. The DRNC sends the Relocation Request Acknowledge message to the MSC to notify
it that the resources needed for relocation are prepared.
8. The SGSN sends the Relocation Command message to the SRNC to notify it that the
relocation can be performed.
9. The MSC sends the Relocation Command message to the SRNC to notify it that the
10. The SRNC sends the Relocation Trigger message to the DRNC over the Iur interface.
If the RAB that supports intact relocation, the PDCP and GTP-U's sequence numbers
will be carried in the message, and then the SRNC will start data forwarding.
11. The DRNC sends the Relocation Detect message to the SGSN, indicating that the
DRNC has detected shift trigger.
2-22

12. The DRNC sends the Relocation Detect message to the MSC, indicating that the
DRNC has detected shift trigger.
13. The DRNC sends the UTRAN Mobility Information and UTRAN Mobility Information
Confirm messages to the UE, requesting the UE to modify the U-RNTI value.
14. The UE sends the URNTI Reallocation Complete message to the DRNC, indicating
that the modification of the DRNC has been completed. In this case, the role of the
DRNC has shifted to that of the SRNC.
15. The DRNC sends the Relocation Complete message to the SGSN, indicating that the
relocation is completed.
16. The DRNC sends the Relocation Complete message to the MSC, indicating that the
relocation is completed.
17. The CN sends the lu release command message to the source SRNC to inform it to
release the lu connection in the PS domain.
18. The MSC sends the lu release command message to the source SRNC to inform it to
release the lu connection in the CS domain.
19. The source SRNC initiates the release of Iub user-plane bearer by using the ALCAP
protocol.
2.5.2 Hard Handover Relocation

The hard handover relocation means that the UE performs handover from the SRNC to
the target RNC, together with the change of the Iu interface. It is also called UE involved
handover because the relocation needs the participation of the UE.
The following figure illustrates the signalling procedures for hard handover relocation.
2-23

Figure 2-20 Signalling Procedures for Hard Handover Relocation
1. The SRNC sends the Relocation Required message to the SGSN.
2. The SRNC sends the Relocation Required message to the MSC.
3. The SGSN requests the DRNC to prepare for relocation by sending a Relocation
Request message.
4. The MSC requests the DRNC to prepare for relocation by sending a Relocation
Request message.
5. By using the ALCAP protocol, the DRNC initiates the establishment of IuCS user-plane
bearer.
6. The DRNC sends the Relocation Request Acknowledge message to the SGSN to
notify it that the resources needed for relocation are prepared.
7. The DRNC sends a Relocation Request Acknowledge message to the MSC to notify
it that the resources needed for relocation are prepared.
8. The SGSN sends the Relocation Command message to the SRNC to notify it that the
9. The MSC sends a Relocation Command message to the SRNC to notify it that the
10. If the RAB that supports intact relocation exists, the SRNC sends the Forward SRNS
Context message to the SGSN, expecting that the SGSN forwards the GTP-U and
PDCP's sequence numbers needed for data forwarding to the target RNC.
2-24

11. After having received the Forward SRNS Context message from the SRNC, the
SGSN sends the Forward SRNS Context message to the target RNC. The GTP-U and
PDCP's sequence numbers needed for data forwarding are carried in the message.
12. The SRNC sends the Physical Channel Reconfiguration message (the message is
taken as an example) to the UE. The message to be sent is determined by the resource
preparation of the target RNC.
13. After successful handover to the target RNC, the UE sends the Physical Channel
Reconfiguration Complete message to the target RNC that is called the SRNC of the
UE.
14. The target RNC sends the Relocation Complete message to the SGSN, indicating that
the relocation is completed.
15. The target RNC sends the Relocation Complete message to the MSC, indicating that
the relocation is completed.
16. The CN sends the lu release command message to the source SRNC to inform it to
release the lu connection in the PS domain.
17. The MSC sends the lu release command message to the source SRNC to inform it to
release the lu connection in the CS domain.
18. The source SRNC initiates the release of Iub user-plane bearer by using the ALCAP
protocol.
2.6 Security Mode Control

Security mode control procedures are used by the network side to send encrypted
information to the radio access network side. During the procedures, the network side
of CN negotiates with the radio access network to perform encryption algorithm on the
user terminal, so that the user can use the encryption algorithm in the subsequent service
transmission. In addition, after the terminal user performs handover, the encryption
algorithm is quite possible to used by the user. In this case, the encrypted parameters will
be forwarded to the target RNC of handover.
The following figure illustrates the signalling procedures for security mode control.
2-25

Figure 2-21 Signalling Procedures for Security Mode Control
2-26

Chapter 3
Call Control Procedures
Table of Contents
UE Originating Call Establishment..............................................................................3-1
UE Terminating Call Establishment.............................................................................3-3
RAB Procedures ........................................................................................................3-4
Call Release Procedures............................................................................................3-7
3.1 UE Originating Call Establishment

When the UE wants to initiate a call, it needs to establish communication with the network
by using radio access signalling, and sends a message that carries the called user number.
The CN will set up a communication channel connecting with the UE, and will use the called
party address to create an IAM message, and then will forward the message to the called
party.
The following figure illustrates the procedures for initial call establishment.
3-1

Figure 3-1 Procedures for Initial Call Establishment
1. The UE sends the CHANNEL REQUEST to the network on the random access
channel.
2. The network responds with a IMMEDIATE ASSIGNMENT message, indicating that the
UE can occupy the specified dedicated channel.
3. The UE sends the initial service request message CM SERVICE REQUEST to the CN.
4. The network will initial the authentication and encryption procedures.
5. After having sent the SECURITY MODE COMPLETE message, the UE sends the
SETUP message to the MS for initiating call establishment.
6. The CALL PROCEEDING message will be sent back from the network.
7. A communication channel should be allocated before the call establishment of fixed
network is initiated by the network.
8. When the phone of the called rings, the network side needs to send an ALERTING
message to the caller UE.
9. After making a response, the called sends the CONNECT message to the network,
and then the network forwards the message to the caller side.
10. The call establishment procedures are completed after the caller UE responds with a
CONNECT ACKNOWLEDGE message.
3-2

Chapter 3 Call Control Procedures
3.2 UE Terminating Call Establishment

Upon receiving the IAM message, if the CN allows the incoming call to be established, it
needs to page the UE by using radio interface signallings. Upon receiving the PAGE ACK
message sent by the UE, the CN establishes a communication channel connecting with
the UE.
UE terminating call applies to the scenario under which the UE is the called and the network
initiates call establishment procedures.
The following figure illustrates the procedures for UE terminating call establishment.
Figure 3-2 UE Terminating Call Establishment
1. The CN sends the PAGE message to the RNS that broadcasts the message on the
paging channel.
2. Upon detecting the paging message, the called UE sends a channel request to the
RNS. The RNS responds to the UE with an immediate Assignment command, indicat-
ing that the UE uses the specified signalling channel.
3. Upon receiving a corresponding paging message sent by the UE, the CN initiates the
authentication and encryption procedures.
3-3

4. The CN sends a SETUP message to the RNS. The bearing capability information of
the call is carried in the message.
5. Upon receiving the SETUP message sent by the RNS, the UE responds with a CALL
CONFIRMED message. The bearing capability information is carried in the message
if the negotiated bearing capability parameter is changed.
6. Upon receiving the CALL CONFIRMED message sent by the RNS, the CN sends the
RAB ASSIGNMENT REQ message to the RNS to request it to allocate radio channels.
The RNS will send a allocation command to the UE to assign it to tune to a specified
communication channel. After tuning to the specified channel, the UE will send an
ASSIGNMENT COMPLETED message to the RNS.
7. The RNS sends the RAB ASSIGNMENT RESP message to the CN.
8. The UE sends the ALERTING message to the called to indicate it to ring.
9. During the process of the called user making a response, the called UE sends a
CONNECT message to the RNS that forwards the message to the CN.
10. The CN responds to the UE with a CONNECT ACK message. The call establishment
procedures are completed.
3.3 RAB Procedures

3.3.1 RAB Establishment Procedures
DCH-DCH synchronous establishment procedures are an example to describe the
procedures for RAB establishment between the CN and UE through the UTRAN, as
illustrated in the following figure.
3-4

Figure 3-3 RAB Establishment Procedures (DCH-DCH Synchronous Establishment

Procedures)
1. The CN sends the RANAP: RAB ASSIGNMENT REQUEST message, to request for
the RAB establishment.
2. By using the ALCAP protocol, the SRNC initiates the user plane transmission bearer
establishment on the lub interface.
3. After the Node B having reconfigured radio links and performed UL and DL
synchronization, the SRNC conveys RAB related parameters carried in the Radio
Bearer Setup message to the UE.
4. After the SRNC having received the RRC message Radio Bearer Setup Complete
returned from the UE and the ALCAP procedures are established successfully, the
SRNC sends the RANAP: RAB Assignment Response message to the CN.
3.3.2 RAB Release procedures

DCH-DCH synchronous release procedures are an example to describe the procedures
for RAB establishment between the CN and UE through the UTRAN, as illustrated in the
following figure.
3-5

Figure 3-4 RAB Establishment Procedures (DCH-DCH Synchronous Release

Procedures)
1. The CN sends the RANAP: RAB Assignment Request message, to start the RAB
release procedures.
2. The SRNC acknowledges with the RANAP message RAB Assignment Response.
3. Through the ALCAP protocol, if the SRNC is borne on AAL2, the SRNC uses the AAL2
RELEASE message to start the release of Iu data transport bearer between the SRNC
and CN.
4. After the Node B having released radio links, the SRNC sends the RRC message
Radio Bearer Release to the UE to start the bearer release procedures.
5. The UE responds with the RRC message Radio Bearer Release Complete. The whole
release procedures are completed.
3.3.3 RAB Modification Procedures

DCH-DCH synchronous modification procedures are an example to describe the
procedures for RAB modification between the CN and UE, as illustrated in the following
figure.
3-6

Figure 3-5 RAB Modification Procedures (DCH-DCH Synchronous Modification

Procedures)
1. The CN sends the RANAP: RAB ASSIGNMENT REQUEST message, to request for
the modification of RAB.
2. The SRNC selects related parameters.
3. SRNC modifies the channel features of Iu data transport bearer by using the ALCAP
protocol.
4. After completing the modification of the Iub transport control plane and radio links, the
SRNC sends the RRC message Radio Bearer Reconfiguration to the UE.
5. The UE sends the RRC message Radio Bearer Reconfiguration Complete to the
SRNC.
6. The SRNC sends the RANAP message RAB Assignment Response to the CN.
7. The UTRAN initializes the Iu user plane.
3.4 Call Release Procedures

When the user completes the calling, the hook-on information of the caller and the called
should be notified to the network side, to release the call.
The following figure illustrates the procedures for user originating successful call release.
3-7

Figure 3-6 Procedures for User Originating Successful Call Release
1. After the user hooks on, the MS sends the DISCONNECT message to the network, to
clear the call.
2. Upon receiving the message, the network sends the RELEASE message to the MS.
3. The MS sends the RELEASE COMPLETE message to the network. If the
communication channel is not needed, channel release procedures should be started.
4. If there is only one call at the Iu connection during the call, then the Iu connection
should be released. The CN sends the IU RELEASE COMMAND message to the
RNS, to request for the release of the Iu connection.
3-8

Chapter 4
HSPA Procedures
Table of Contents
Physical Shared Channel Reconfiguration..................................................................4-1
HSPA Serving Cell Change ........................................................................................4-2
4.1 Physical Shared Channel Reconfiguration

The procedures for physical shared channel reconfiguration are used to establish,
reconfigure, and delete the HS-DSCH and E-DCH's related resources in the Node B.
The following figure illustrate the procedures for physical shared channel reconfiguration.
Figure 4-1 Procedures for Physical Shared Channel Reconfiguration
1. Through the NCP, the CRNC sends the Physical Shared Channel Reconfiguration
Request message to the Node B, to initiate the procedures for physical shared channel
reconfiguration .
2. Upon receiving the message, the Node B activates the new configuration at the header
boundary of SFN according to the parameter carried in the message.
4-1

If the SFN IE is carried in the Physical Shared Channel Reconfiguration Request

message, the Node B will activate the new configuration at the header boundary of
the SFN. If the SFN IE is not carried in the message, the Node B will activate a new
configuration.
4.2 HSPA Serving Cell Change

The following figure illustrates the procedures for the change of HSPA serving cell inside
the RNC.
Figure 4-2 Procedures for HSPA Serving Cell Change Inside the RNC
1. The source E-DCH cell and the target E-DCH cell are controlled by different Node
Bs. The RNC sends the NBAP message Radio Link Reconfiguration Prepare to the
source E-DCH Node B, to request the source E-DCH Node B to synchronize radio link
reconfiguration and to release E-DCH resources for the source E-DCH.
2. The source E-DCH Node B responds with the Radio Link Reconfiguration Ready
message.
4-2

Chapter 4 HSPA Procedures
3. The RNC sends the NBAP message Radio Link Reconfiguration Prepare to the
target E-DCH Node B, to request the target E-DCH Node B to synchronize radio link
reconfiguration and to release E-DCH resources for the target E-DCH.
4. The target E-DCH Node B responds with the Radio Link Reconfiguration Ready mes-
sage.
5. The E-DCH transport bearer of the target E-DCH Node B is established. The RNC
sends the Radio Link Reconfiguration Commit message to the source E-DCH Node
B.
6. The RNC sends the NBAP message Radio Link Reconfiguration Commit that carries
the activation time to the target E-DCH Node B. At the specified activation time, the
source E-DCH Node B stops transmitting but the target E-DCH Node B starts to
transmit data to the UE on E-DCH.
7. The RNC sends the Physical Channel Reconfiguration message to the UE.
8. At the specified activation time, the UE stops the reception on E-DCH of the source
E-DCH cell, but starts the reception on E-DCH of the target E-DCH cell. The UE
returns the RRC message Physical Channel Reconfiguration Complete to the RNC.
4-3

This page intentionally left blank.
4-4

Figures
Figure 1-1 Paging the UE in Idle Mode or PCH State ................................................ 1-3
Figure 1-2 Paging the UE in CELL_DCH or CELL_FACH State ................................ 1-4
Figure 2-1 RRC Connection Established on a Dedicated Channel ............................ 2-2
Figure 2-2 RRC Connection Established on a Common Channel.............................. 2-3
Figure 2-3 Signalling Establishment Procedures ....................................................... 2-4
Figure 2-4 RAB Establishment Procedures (CELL_DCH - CELL_DCH
Synchronized)......................................................................................... 2-5
Figure 2-5 RAB Establishment Procedures (CELL_DCH - CELL_DCH) .................... 2-7
Figure 2-6 RAB Establishment Procedures (RACH/FACH - RACH/FACH) ................ 2-8
Figure 2-7 Soft Handover (Radio Link Addition) ........................................................ 2-9
Figure 2-8 Soft Handover (Radio Link Deletion) ...................................................... 2-10
Figure 2-9 Soft Handover (Radio Link Replacement) .............................................. 2-12
Figure 2-10 Hard Handover Procedure ................................................................... 2-13
Figure 2-11 Periodical Cell Update Procedures ....................................................... 2-15
Figure 2-12 Procedures for Cell Update With Physical Channel
Reconfiguration..................................................................................... 2-15
Figure 2-13 Procedures for Cell Update With Transport Channel
Reconfiguration..................................................................................... 2-16
Figure 2-14 URA Update Procedures ..................................................................... 2-17
Figure 2-15 Handover to UTRAN ............................................................................ 2-18
Figure 2-16 Handover From UTRAN....................................................................... 2-19
Figure 2-17 Cell Reselection From UTRAN............................................................. 2-20
Figure 2-18 Cell Reselection to UTRAN .................................................................. 2-21
Figure 2-19 Signalling Procedures for Soft Handover Relocation ............................ 2-22
Figure 2-20 Signalling Procedures for Hard Handover Relocation........................... 2-24
Figure 2-21 Signalling Procedures for Security Mode Control ................................. 2-26
Figure 3-1 Procedures for Initial Call Establishment .................................................. 3-2
Figure 3-2 UE Terminating Call Establishment .......................................................... 3-3
Figure 3-3 RAB Establishment Procedures (DCH-DCH Synchronous
Establishment Procedures) ..................................................................... 3-5
Figure 3-4 RAB Establishment Procedures (DCH-DCH Synchronous Release
Procedures) ............................................................................................ 3-6
I
Figure 3-5 RAB Modification Procedures (DCH-DCH Synchronous Modification

Procedures) ............................................................................................ 3-7
Figure 3-6 Procedures for User Originating Successful Call Release ........................ 3-8
Figure 4-1 Procedures for Physical Shared Channel Reconfiguration ....................... 4-1
Figure 4-2 Procedures for HSPA Serving Cell Change Inside the RNC ..................... 4-2
II

SJ-20120319104909-005-ZXUR 9000 UMTS (V4.11.20) Signalling Description

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

SJ-20120319104909-005-ZXUR 9000 UMTS (V4.11.20) Signalling Description

Uploaded by

Copyright:

Available Formats

ZXUR 9000 UMTS

Radio Network Controller

Revision No. Revision Date Revision Reason

R1.0 2012-04-17 First edition

Serial Number: SJ-20120319104909-005

Publishing Date: 2012-04-17 (R1.0)

What is in This Manual

Chapter 4, HSPA Describes the signalling procedures related to HSPA.

Chapter 2 Radio Resource Management Procedures............................. 2-1

Chapter 3 Call Control Procedures........................................................... 3-1

Chapter 4 HSPA Procedures ..................................................................... 4-1

1.1.1 CELL_DCH State

1.1.2 CELL_FACH State

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

1.1.3 URA_PCH State

1.2 Paging Procedures

1.2.1 Performing Paging on the UE in Idle Mode or PCH State

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 Paging the UE in Idle Mode or PCH State

1.2.2 Performing Paging on the UE in CELL_DCH or CELL_FACH

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 1-2 Paging the UE in CELL_DCH or CELL_FACH State

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.1 RRC Connection Establishment Procedures

2.1.1 RRC Connection Established on a Dedicated Channel

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 RRC Connection Established on a Dedicated Channel

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.1.2 RRC Connection Established on a Common Channel

Figure 2-2 RRC Connection Established on a Common Channel

2.2 Signalling Establishment Procedures

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-3 Signalling Establishment Procedures

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.3 RAB Establishment Procedures

2.3.1 CELL_DCH - CELL_DCH

Figure 2-4 RAB Establishment Procedures (CELL_DCH - CELL_DCH Synchronized)

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.3.2 CELL_FACH - CELL_DCH

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-5 RAB Establishment Procedures (CELL_DCH - CELL_DCH)

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.3.3 RACH/FACH - RACH/FACH

Figure 2-6 RAB Establishment Procedures (RACH/FACH - RACH/FACH)

2.4 Handover Procedures

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Soft handover is performed in the following five steps:

2.4.1.1 Radio Link Addition

Figure 2-7 Soft Handover (Radio Link Addition)

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.4.1.2 Radio Link Deletion

Figure 2-8 Soft Handover (Radio Link Deletion)

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.4.1.3 Radio Link Replacement

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-9 Soft Handover (Radio Link Replacement)

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.4.2 Hard Handover

Figure 2-10 Hard Handover Procedure

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

2.4.3 Forward Handover

2.4.3.1 Cell Update

SJ-20120319104909-005|2012-04-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-11 Periodical Cell Update Procedures