RAN17 Signaling

HEEX Startpage
Page 1 of 156
(For Engineer) RAN17.1 Solution Technical Guideline

Product Version: RAN17.1
Library Version: 01
Date: 04/22/2015
For any question, please contact us.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.
10-RAN17.1 Signaling Analysis Guide

Contents
6.10 10-RAN17.1 Signaling Analysis Guide
RAN17.1
Signaling Analysis Guide
http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016
9/5/2016
HEEX Startpage
Page 2 of 156
Issue
02
Date
2015-04-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be within
the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
9/5/2016
HEEX Startpage
Page 3 of 156
About This Document
Purpose
This document describes the trigger conditions of common signaling procedures, explains the procedures in normal and abnormal
conditions, and presents the ways of signaling tracing on the RNC LMT.
Version
The following table lists the product versions related to this document.
Product Name
Version
RNC
V900R011 and later versions

NodeB

Intended Audience
This document is intended for:
z
Field engineers
System engineers
Change History
See Changes in RAN Signaling Analysis Guide.
Organization
N/A
Contents
About This Document
1 Change History
2 Cell Setup Procedure
2.1 Protocols Related to Cell Setup
2.2 Trigger Conditions of Cell Setup
2.3 Signaling Procedure of Successful Cell Setup
2.4 Using the RNC LMT to Trace the Cell Setup Procedure
2.4.1 Prerequisites
2.4.2 Context
2.4.3 Procedure
2.5 Elementary Procedures of Cell Setup
2.5.1 Resource Status Indication Procedure
2.5.2 Resource Audit Procedure
2.5.3 Cell Setup Procedure
2.5.4 Common Transport Channel Setup Procedure
2.5.5 Iub User Plane Setup Procedure
2.5.6 System Information Update Procedure
2.5.7 Physical Shared Channel Reconfiguration Procedure
2.5.8 Common Measurement Initiation Procedure
3 Cell Reconfiguration Procedure
3.1 Protocols Related to Cell Reconfiguration
3.2 Trigger Conditions of Cell Reconfiguration
3.3 Signaling Procedure of Cell Reconfiguration
9/5/2016
HEEX Startpage
Page 4 of 156
3.4 Using the RNC LMT to Trace the Cell Reconfiguration Procedure
4 Cell Deletion Procedure
4.1 Protocols Related to Cell Deletion
4.2 Trigger Conditions of Cell Deletion
4.3 Signaling Procedure of Cell Deletion
4.4 Using the RNC LMT to Trace the Cell Deletion Procedure
5 Location Update Procedure
5.1 Protocols Related to Location Update
5.2 Trigger Conditions of Location Update
5.3 Signaling Procedure of a Successful Location Update
5.4 Using the RNC LMT to Trace the Location Update Procedure
5.5 Elementary Procedures of Location Update
5.5.1 RRC Connection Setup Procedure
5.5.2 Location Update Procedure
5.5.3 Iu Release Procedure
5.5.4 RRC Connection Release Procedure
6 Outgoing Call Procedure
6.1 Protocols Related to an Outgoing Call
6.2 Trigger Conditions of an Outgoing Call
6.3 Signaling Procedure of a Successful Outgoing Call
6.4 Using the RNC LMT to Trace the Outgoing Call Procedure
6.5 Elementary Procedures of an Outgoing Call
6.5.1 Attach Procedure
6.5.3 Signaling Connection Setup Procedure (Outgoing Call)
6.5.4 Authentication and Security Mode Control Procedure
6.5.5 Call Setup Procedure (Outgoing Call)
6.5.6 RAB Setup Procedure
6.5.7 Call Release Procedure (Outgoing Call)
7 Incoming Call Procedure
7.1 Protocols Related to an Incoming Call
7.2 Trigger Conditions of an Incoming Call
7.3 Signaling Procedure of a Successful Incoming Call
7.4 Using the RNC LMT to Trace the Incoming Call Procedure
7.5 Elementary Procedures of an Incoming Call
7.5.1 Paging Procedure
7.5.3 Signaling Connection Setup Procedure (Incoming Call)
7.5.5 Call Setup Procedure (Incoming Call)
7.5.7 Call Release Procedure (Incoming Call)
8 PS Service Setup Procedure
8.1 Protocols Related to PS Service Setup
8.2 Trigger Conditions of PS Service Setup
8.3 Signaling Procedure of Successful PS Service Setup
8.4 Using the RNC LMT to Trace the PS Service Setup Procedure
9/5/2016
HEEX Startpage
Page 5 of 156
8.5 Elementary Procedures of PS Service Setup

8.5.2 Signaling Connection Setup Procedure
8.5.4 PS Service Setup Procedure
8.5.6 PS Service Release Procedure
8.5.9 Detach Procedure
9 Intra-Frequency Handover Procedure
9.1 Protocols Related to Intra-Frequency Handover
9.2 Trigger Conditions of Intra-Frequency Handover
9.3 Types of Intra-Frequency Handover
9.4 Intra-Frequency Soft Handover Within a NodeB
9.4.1 Protocols Related to Intra-Frequency Soft Handover Within a NodeB
9.4.2 Trigger Conditions of Intra-Frequency Soft Handover Within a NodeB
9.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Within a NodeB
9.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Within a NodeB
9.4.5 Elementary Procedures of Intra-Frequency Soft Handover Within a NodeB
9.5 Intra-Frequency Soft Handover Between NodeBs in an RNC
9.5.1 Protocols Related to Intra-Frequency Soft Handover Between NodeBs in an RNC
9.5.2 Trigger Conditions of Intra-Frequency Soft Handover Between NodeBs in an RNC
9.5.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between NodeBs in an RNC
9.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between NodeBs in an RNC
9.5.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC
9.6 Intra-Frequency Soft Handover Between RNCs
9.6.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs
9.6.2 Trigger Conditions of Intra-Frequency Soft Handover Between RNCs
9.6.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs
9.6.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs
9.6.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs
9.7 Intra-Frequency Hard Handover Between NodeBs in an RNC
9.7.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC
9.7.2 Trigger Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC
9.7.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC
9.7.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in an RNC
9.7.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC
9.8 Intra-Frequency Hard Handover Between RNCs
9.8.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs
9.8.2 Trigger Conditions of Intra-Frequency Hard Handover Between RNCs
9.8.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs
9.8.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between RNCs
9.8.5 Elementary Procedures of Intra-Frequency Hard Handover Between RNCs
10 Inter-Frequency Handover Procedure
10.1 Protocols Related to Inter-Frequency Handover
10.2 Trigger Conditions of Inter-Frequency Handover
10.3 Compressed Mode Procedure
10.3.2 Start of a Compressed Mode Procedure
9/5/2016
HEEX Startpage
Page 6 of 156
10.4 Types of Inter-Frequency Handover

10.5 Inter-Frequency Handover Between NodeBs in an RNC
10.5.1 Protocols Related to Inter-Frequency Handover Between NodeBs in an RNC
10.5.2 Trigger Conditions of Inter-Frequency Handover Between NodeBs in an RNC
10.5.3 Signaling Procedure of a Successful Inter-Frequency Handover Between NodeBs in an RNC
10.5.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between NodeBs in an RNC
10.5.5 Elementary Procedures of Inter-Frequency Handover Between NodeBs in an RNC
10.6 Inter-Frequency Handover Between RNCs
10.6.1 Protocols Related to Inter-Frequency Handover Between RNCs
10.6.2 Trigger Conditions of Inter-Frequency Handover Between RNCs
10.6.3 Signaling Procedure of a Successful Inter-Frequency Handover Between RNCs
10.6.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between RNCs
10.6.5 Elementary Procedures of Inter-Frequency Handover Between RNCs
11 Inter-RAT Handover Procedure
11.1 Protocols Related to Inter-RAT Handover
11.2 Trigger Conditions of Inter-RAT Handover
11.4 Types of Inter-RAT Handover
11.5 Inter-RAT CS Handover from WCDMA to GSM
11.5.1 Protocols Related to Inter-RAT CS Handover from WCDMA to GSM
11.5.2 Trigger Conditions of Inter-RAT CS Handover from WCDMA to GSM
11.5.3 Signaling Procedure of a Successful Inter-RAT CS Handover from WCDMA to GSM
11.5.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from WCDMA to GSM
11.5.5 Elementary Procedures of Inter-RAT CS Handover from WCDMA to GSM
11.6 Inter-RAT CS Handover from GSM to WCDMA
11.6.1 Protocols Related to Inter-RAT CS Handover from GSM to WCDMA
11.6.2 Trigger Conditions of Inter-RAT CS Handover from GSM to WCDMA
11.6.3 Signaling Procedure of a Successful Inter-RAT CS Handover from GSM to WCDMA
11.6.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from GSM to WCDMA
11.6.5 Elementary Procedures of Inter-RAT CS Handover from GSM to WCDMA
11.7 Inter-RAT PS Handover from WCDMA to GSM
11.7.1 Protocols Related to Inter-RAT PS Handover from WCDMA to GSM
11.7.2 Trigger Conditions of Inter-RAT PS Handover from WCDMA to GSM
11.7.3 Signaling Procedure of a Successful Inter-RAT PS Handover from WCDMA to GSM
11.7.4 Using the RNC LMT to Trace the Procedure of Inter-RAT PS Handover from WCDMA to GSM
11.7.5 Elementary Procedures of Inter-RAT PS Handover from WCDMA to GSM
11.8 Inter-RAT PS Handover from GSM to WCDMA
12 SRNS Relocation Procedure
12.1 Protocols Related to SRNS Relocation
12.2 Trigger Conditions of SRNS Relocation
12.3 Types of SRNS Relocation
12.4 Static Relocation
12.4.1 Protocols Related to Static Relocation
12.4.2 Trigger Conditions of Static Relocation
12.4.3 Signaling Procedure of a Successful Static Relocation
12.4.4 Using the RNC LMT to Trace the Static Relocation Procedure
12.4.5 Elementary Procedures of Static Relocation
12.5 Relocation with Hard Handover
9/5/2016
HEEX Startpage
Page 7 of 156
12.5.1 Protocols Related to Relocation with Hard Handover

12.5.2 Trigger Conditions of Relocation with Hard Handover
12.5.3 Signaling Procedure of a Successful Relocation with Hard Handover
12.5.4 Using the RNC LMT to Trace the Procedure of Relocation with Hard Handover
12.5.5 Elementary Procedures of Relocation with Hard Handover
12.6 Relocation with Cell/URA Update
12.6.1 Protocols Related to Relocation with Cell/URA Update
12.6.2 Trigger Conditions of Relocation with Cell/URA Update
12.6.3 Signaling Procedure of a Successful Relocation with Cell/URA Update
12.6.4 Using the RNC LMT to Trace the Procedure of Relocation with Cell/URA Update
12.6.5 Elementary Procedures of Relocation with Cell/URA Update
12.7 DSCR Procedure
12.7.1 Protocols Related to DSCR
12.7.2 Trigger Conditions of DSCR
12.7.3 Signaling Procedure of Successful DSCR
13 Location Service Procedure
13.1 Working Mode
13.2 Positioning Methods
13.3 Positioning Based on Cell ID+RTT
13.3.1 Protocols Related to Positioning Based on CELL ID+RTT
13.3.2 Positioning Based on Cell ID+RTT in RNC Centric Mode
13.3.3 Cell ID+RTT Positioning Method in SAS Centric Mode
13.4 Positioning Based on OTDOA-IPDL
13.4.1 Protocols Related to Positioning Based on OTDOA-IPDL
13.4.2 Trigger Conditions of Positioning Based on OTDOA-IPDL
13.4.3 Signaling Procedure of Successful Positioning Based on OTDOA-IPDL
13.4.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELL ID+RTT or OTDOA-IPDL
13.4.5 Elementary Procedures of Positioning Based on OTDOA-IPDL
13.5 Positioning Based on A-GPS
13.5.1 Protocols Related to Positioning Based on A-GPS
13.5.2 Positioning Based on A-GPS in RNC Centric Mode
13.5.3 A-GPS Positioning Method in SAS Centric Mode
Change History
This chapter describes the changes in RAN Signaling Analysis Guide.
02 (2015-04-10)
This is the second commercial release of this document for RAN17.1.
01 (2014-11-20)
This is the first commercial release of this document for RAN17.1.
Compared with RAN17.0, this issue does not include any changes.
Cell Setup Procedure
9/5/2016
HEEX Startpage
Page 8 of 156
The cell setup procedure is performed to set up a WCDMA cell. This chapter describes cell setup in terms of protocols, trigger
conditions, signaling procedure of successful cell setup, and signaling tracing on the RNC LMT. This topic also describes the
elementary procedures in terms of functions, trigger conditions, and signaling in normal and abnormal conditions.
2.1 Protocols Related to Cell Setup

The cell setup procedure complies with some 3GPP 25-series specifications and an ITU-T protocol.
The compliance protocols are as follows:
z
3GPP TS25.427 "UTRAN Iur/Iub interface user plane protocol for DCH data streams"
3GPP TS 25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling"
3GPP TS25.435 "UTRAN Iub interface user plane protocols for Common Transport Channel data streams"
ITU-T Q.2630 "AAL type 2 Signalling Protocol"
2.2 Trigger Conditions of Cell Setup

Cell setup can be triggered either through execution of an MML command or with a resource audit response from the NodeB.
Table 2-1 describes the two trigger conditions.
Table 2-1 Trigger conditions of cell setup
Trigger Condition
Description
Feature
Cell setup is
initiated by the
RNC LMT.
Run the ACT UCELL

command on the RNC LMT in
online mode.
The resource
audit procedure
is excluded from
cell setup.
The CRNC
receives a resource
audit response
from the NodeB.
After receiving the resource

audit response from the
NodeB, the CRNC sends a
cell setup request to the
NodeB if the cell setup
requirements are fulfilled.
The resource
audit procedure
is involved in cell
setup.
2.3 Signaling Procedure of Successful Cell Setup

This section describes the signaling procedure of successful cell setup. For the messages related to cell setup failures, see the
elementary procedures.
Figure 2-2 shows the signaling procedure of successful cell setup.
Figure 2-1 Signaling procedure of successful cell setup
9/5/2016
HEEX Startpage
Page 9 of 156
Note the following information about the procedure shown in Figure 2-1:
z The resource status indication and resource audit procedures are involved in cell setup only when the cell setup is triggered with a
resource audit response from the NodeB.
z The physical shared channel reconfiguration procedure is involved in cell setup only when the cell to be set up is a High Speed
Downlink Packet Access (HSDPA) cell.
z
If IP transport is applied to the Iub interface, the Iub user plane setup procedure is excluded from cell setup.
2.4 Using the RNC LMT to Trace the Cell Setup Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell setup.
2.4.1 Prerequisites
z
The RNC LMT works properly.
You have logged in to the RNC as a user authorized to perform tracing management.
2.4.2 Context
Table 2-2 lists the messages to be traced.
Table 2-2 Messages to be traced
Interface Message Name on the LMT

and
Protocol
to Be
Traced
Iub
Message Name in
Protocols
NBAP_AUDIT_REQ
AUDIT REQUEST
NBAP_AUDIT_RSP
AUDIT RESPONSE
NBAP_AUDIT_FAIL
AUDIT FAILURE
NBAP_CELL_SETUP_REQ
CELL SETUP
REQUEST
NBAP_CELL_SETUP_RSP
CELL SETUP
RESPONSE
NBAP_CELL_SETUP_FAIL
CELL SETUP
FAILURE
NBAP_CELL_DEL_REQ
CELL DELETION
REQUEST
NBAP_CELL_DEL_RSP
CELL DELETION
RESPONSE
NBAP_COMM_TRANSP_CH_SETUP_REQ COMMON
TRANSPORT
CHANNEL SETUP
REQUEST
NBAP_COMM_TRANSP_CH_SETUP_RSP
COMMON
TRANSPORT
CHANNEL SETUP
RESPONSE
NBAP_COMM_TRANSP_CH_SETUP_FAIL
COMMON
TRANSPORT
CHANNEL SETUP
FAILURE
NBAP_SYS_INFO_UPDATE_REQ
SYSTEM
INFORMATION
UPDATE REQUEST
NBAP_SYS_INFO_UPDATE_RSP
SYSTEM
INFORMATION
UPDATE
RESPONSE
9/5/2016
HEEX Startpage
Page 10 of 156

and
Protocol
to Be
Traced
Q.AAL2
Message Name in
Protocols
NBAP_SYS_INFO_UPDATE_FAIL
SYSTEM
INFORMATION
UPDATE FAILURE
NBAP_PSCH_RECFG_REQ
PHYSICAL SHARED
CHANNEL
RECONFIGURATION
REQUEST
NBAP_PSCH_RECFG_RSP
PHYSICAL SHARED
CHANNEL
RECONFIGURATION
RESPONSE
NBAP_PSCH_RECFG_FAIL
PHYSICAL SHARED
CHANNEL
RECONFIGURATION
FAILURE
NBAP_COMM_MEAS_INI_REQ
COMMON
MEASUREMENT
INITIATION
REQUEST
NBAP_COMM_MEAS_INI_RSP
COMMON
MEASUREMENT
INITIATION
RESPONSE
NBAP_COMM_MEAS_INI_FAIL
COMMON
MEASUREMENT
INITIATION FAILURE
NBAP_COMM_MEAS_RPRT
COMMON
MEASUREMENT
REPORT
No message name needs to be specified.
2.4.3 Procedure
Step 1 Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 2-2 shows an example of Iub signaling tracing result.
Figure 2-2 Example of Iub signaling tracing result
In practice, the messages transmitted during cell setup depend on the configured data. In this example, an HSDPA cell is set up.
During the cell setup, the common transport channel setup procedure is performed to set up a Secondary Common Control Physical
Channel (S-CCPCH), a Physical Random Access Channel (PRACH), a Paging Indicator Channel (PICH), and an Acquisition
Indicator Channel (AICH). The S-CCPCH carries two Forward Access Channels (FACHs) and a Paging Channel (PCH). The
PRACH carries a Random Access Channel (RACH).
Step 2 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task. Figure 2-3 shows an example of Q.AAL2 protocol tracing
result.
Figure 2-3 Example of Q.AAL2 protocol tracing result
9/5/2016
HEEX Startpage
Page 11 of 156
----End
2.5 Elementary Procedures of Cell Setup

This section describes the elementary procedures of cell setup in terms of trigger conditions and signaling procedures in normal and
abnormal conditions.
2.5.1 Resource Status Indication Procedure

The NodeB performs the resource status indication procedure to report the status of its physical resources to the Control RNC
(CRNC).
Trigger Conditions
The NodeB triggers the procedure in one of the following conditions:
z
A local cell is added to the NodeB.
A local cell is deleted from the NodeB.
The capabilities of a local cell change at the NodeB.
A cell changes its capability and/or its resource operational state at the NodeB.
Common physical channels and/or common transport channels change their capabilities at the NodeB.
A Communication Control Port (CCP) changes its resource operational state at the NodeB.
A local cell group changes its resource capability at the NodeB.
Procedure
Figure 2-4 shows the resource status indication procedure.
Figure 2-4 Resource status indication procedure
The NodeB sends a RESOURCE STATUS INDICATION message to the CRNC through the NodeB Control Port (NCP). The
message contains the trigger condition and the associated logical resource information.
2.5.2 Resource Audit Procedure

The CRNC performs the resource audit procedure to audit the configuration and status of the logical resources in the NodeB. The
audit may let the CRNC know the logical resources of the NodeB and re-synchronize its resources with those of the NodeB.
Trigger Conditions
The CRNC receives a RESOURCE STATUS INDICATION message from the NodeB.
Procedure
Figure 2-5 shows the resource audit procedure.
Figure 2-5 Resource audit procedure
9/5/2016
HEEX Startpage
Page 12 of 156
The procedure shown in Figure 2-5 is described as follows:

2.
3.
The CRNC sends an AUDIT REQUEST message to the NodeB through the NCP to initiate the resource audit procedure.
The NodeB sends a response message to the CRNC through the NCP.
If the audit is successful, the NodeB sends an AUDIT RESPONSE message.
The AUDIT RESPONSE message contains information about common physical channels of the logical cell, CCP, local cell, and
local cell group. The information about local cell and local cell group is the abstraction of the physical resources of the NodeB. In this
way, the CRNC can allocate the logical resources of the cell according to the abstract data.
If the audit fails, the NodeB sends an AUDIT FAILURE message.
A complete audit of a NodeB can be performed by one or more audit procedures. Each procedure carries an audit sequence
number.
2.5.3 Cell Setup Procedure

The cell setup procedure is performed to set up a cell in the NodeB.
Trigger Conditions
After receiving the AUDIT RESPONSE message from the NodeB, the CRNC checks whether the conditions of cell setup are fulfilled
and, if fulfilled, sends a CELL SETUP REQUEST message to the NodeB.
Whether the conditions of cell setup are fulfilled depends on the following local cell information reported by the NodeB:
z
Downlink power range
Minimum spreading factor
HSDPA cell capability of the NodeB
High Speed Downlink Shared Channel (HS-DSCH) resource information, which is used to set up an HSDPA cell
Common transport channel and physical channel information
CCP and NCP information
Procedure
Figure 2-6 shows the cell setup procedure.
Figure 2-6 Cell setup procedure

1.
The CRNC sends a CELL SETUP REQUEST message to the NodeB through the NCP. The NodeB then sets up a new cell
according to the parameters given in the message.
2.
If the cell is set up, the NodeB sends a CELL SETUP RESPONSE message.
If the cell fails to be set up, the NodeB sends a CELL SETUP FAILURE message.
2.5.4 Common Transport Channel Setup Procedure
9/5/2016
HEEX Startpage
Page 13 of 156
The common transport channel setup procedure is performed to establish the necessary resources in the NodeB, regarding the
following channels: S-CCPCH, PICH, PRACH, AICH, FACH, PCH, and RACH.
Trigger Conditions
The NodeB sends a CELL SETUP RESPONSE message to the CRNC.
Procedure
Figure 2-7 shows the common transport channel setup procedure.
Figure 2-7 Common transport channel setup procedure

1.
The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST message to the NodeB through the NCP.
One message can be used to configure only one of the following combinations:
One S-CCPCH and the related FACHs, PCH and PICH
One PRACH and the related RACH and AICH
2.
3.
If the common transport channels are set up, the NodeB sends a COMMON TRANSPORT CHANNEL SETUP RESPONSE
message.
4.
If the common transport channels fail to be set up, the NodeB sends a COMMON TRANSPORT CHANNEL SETUP FAILURE
message. At the same time, the cell deletion procedure is triggered.
2.5.5 Iub User Plane Setup Procedure

The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface.
Trigger Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
z
The common transport channels are set up.
The dedicated transport channels are set up.
Procedure
Figure 2-8 shows the Iub user plane setup procedure.
Figure 2-8 Iub user plane setup procedure

1.
The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message to the NodeB.
2.
The NodeB uses the ALCAP protocol to send a response message to the CRNC.
If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.
If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
2.5.6 System Information Update Procedure
9/5/2016
HEEX Startpage
Page 14 of 156
The system information update procedure is performed for the NodeB to schedule and update the system information segments,
which are broadcast on the Broadcast Control Channel (BCCH), according to the parameters in the SYSTEM INFORMATION
UPDATE REQUEST message.
Trigger Conditions
The system information update procedure can be triggered in one of the following conditions:
z
Physical shared channels are reconfigured.
Cells are reconfigured.
Procedure
Figure 2-9 shows the system information update procedure.
Figure 2-9 System information update procedure

1.
The CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to the NodeB through the NCP.
The message includes the system information that is broadcast in segments on the BCCH and the scheduling information of each
segment.
2.
The NodeB schedules and updates the system information segments on the BCCH according to the parameters in the
message.
3.
If the system information is updated, the NodeB sends a SYSTEM INFORMATION UPDATE RESPONSE message.
If the system information fails to be updated, the NodeB sends a SYSTEM INFORMATION UPDATE FAILURE message. At the
same time, the cell deletion procedure is triggered.
2.5.7 Physical Shared Channel Reconfiguration Procedure

The physical shared channel reconfiguration procedure is performed for the NodeB to reconfigure the physical channels according
to the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message sent from the CRNC.
Trigger Conditions
The system information is updated and the cell to be set up is an HSDPA cell.
Procedure
Figure 2-10 shows the physical shared channel reconfiguration procedure.
Figure 2-10 Physical shared channel reconfiguration procedure

1.
The CRNC sends a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message to the NodeB through the
NCP to initiate the reconfiguration of the resources on the HS-DSCH and Enhanced UL DCH (E-DCH).
2.
If the physical shared channels are reconfigured, the NodeB sends a PHYSICAL SHARED CHANNEL RECONFIGURATION
RESPONSE message.
If the physical shared channels fail to be reconfigured, the NodeB sends a PHYSICAL SHARED CHANNEL
RECONFIGURATION FAILURE message.
9/5/2016
HEEX Startpage
Page 15 of 156
2.5.8 Common Measurement Initiation Procedure

The common measurement initiation procedure is performed for the CRNC to request the initiation of measurements on common
resources in a NodeB. The NodeB then initiates the requested measurements according to the parameters given in the COMMON
MEASUREMENT INITIATION REQUEST message sent from the CRNC.
Trigger Conditions
The cell is set up and activated.
Procedure
Figure 2-11 shows the common measurement initiation procedure.
Figure 2-11 Common measurement initiation procedure

1.
The CRNC sends a COMMON MEASUREMENT INITIATION REQUEST message to the NodeB through the NCP to initiate
the common measurement initiation procedure. The message includes the measurement object type (such as cell and RACH),
common measurement type (such as transmit carrier power and received total wide band power), and report characteristics (such as
On-Demand report, periodic report, and event report).
2.
The NodeB initiates the requested measurement according to the parameters given in the message.
3.
If the measurement requested by the CRNC is initiated, the NodeB sends a COMMON MEASUREMENT INITIATION
RESPONSE message.
If the measurement requested by the CRNC fails to be initiated, the NodeB sends a COMMON MEASUREMENT INITIATION
FAILURE message.
Cell Reconfiguration Procedure
The cell reconfiguration procedure is performed to reconfigure a cell in the NodeB. This chapter describes the cell reconfiguration
procedure in terms of protocols, trigger conditions, signaling procedure, and signaling tracing on the RNC LMT.
3.1 Protocols Related to Cell Reconfiguration

The cell reconfiguration procedure complies with a 3GPP 25-series protocol.
The compliance protocol is the 3GPP TS 25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling".
3.2 Trigger Conditions of Cell Reconfiguration

Cell reconfiguration is triggered when any of the following conditions is met:
z
In online mode, the ADD UCELLDYNSHUTDOWN or RMV UCELLDYNSHUTDOWN command is executed on the RNC LMT.
After a smooth switchover, the actual cell pilot power is inconsistent with the configured value.
The Uplink Load Balance (ULB) algorithm is enabled.
In online mode, the ACT UIPDL, DEA UIPDL or MOD UIPDL command is executed on the RNC LMT.
In online mode, the MOD UCELL command is executed on the RNC LMT to modify cell parameter configurations.
The dynamic pilot power adjustment algorithm is enabled.

z
In online mode, the ACT UCELLMIMO or DEA UCELLMIMO command is executed on the RNC LMT.
3.3 Signaling Procedure of Cell Reconfiguration
This section describes the signaling procedure of cell reconfiguration.
9/5/2016
HEEX Startpage
Page 16 of 156
Figure 3-1 shows the cell reconfiguration procedure.
Figure 3-1 Cell reconfiguration procedure

1.
The CRNC sends a CELL RECONFIGURATION REQUEST message to the NodeB through the NCP. The NodeB then
reconfigures the cell according to the parameters given in the message.
2.
If the cell is reconfigured, the NodeB sends a CELL RECONFIGURATION RESPONSE message.
If the cell fails to be reconfigured, the NodeB sends a CELL RECONFIGURATION FAILURE message.
3.4 Using the RNC LMT to Trace the Cell Reconfiguration Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell reconfiguration.
Prerequisites
z
Context
Interface to
Be Traced
Message Name on the LMT
Message Name in
Protocols
Iub
NBAP_CELL_RECFG_REQ
CELL
RECONFIGURATION
REQUEST
NBAP_CELL_RECFG_RSP
CELL
RECONFIGURATION
RESPONSE
NBAP_CELL_RECFG_FAIL
CELL
RECONFIGURATION
FAILURE
Procedure
Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 3-2 shows an example of Iub signaling tracing result.
Cell Deletion Procedure
The cell deletion procedure is performed to delete a cell from the NodeB. This chapter describes the cell deletion procedure in terms
of protocols, trigger conditions, signaling procedure, and signaling tracing on the RNC LMT.
4.1 Protocols Related to Cell Deletion
9/5/2016
HEEX Startpage
Page 17 of 156
The cell deletion procedure complies with a 3GPP TS25 protocol.

The compliance protocol is the 3GPP TS 25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling".
4.2 Trigger Conditions of Cell Deletion

Cell deletion can be triggered in different conditions, for example, when the common transport channels fail to be set up.
The cell deletion procedure can be triggered in one of the following conditions:
z
The common transport channels fail to be set up.
The system information fails to be updated.
The common transport channels are deleted.
The cell is deactivated on the RNC LMT.
The cell is deleted on the RNC LMT.
4.3 Signaling Procedure of Cell Deletion

This section describes the signaling procedure of cell deletion.
Figure 4-1 shows the cell deletion procedure.
Figure 4-1 Cell deletion procedure

1.
The CRNC sends a CELL DELETION REQUEST message to the NodeB through the NCP.
2.
The NodeB performs the following operations:
Deletes the cell and any remaining common and dedicated channels within the cell. The states of the deleted cell and common
channels are set to "Not existing".
Initiates release of the user plane transport bearers for the removed common and dedicated channels.
Deletes all radio links and all NodeB communication contexts within the cell.
3.
When the cell is deleted, the NodeB sends a CELL DELETION RESPONSE message to the CRNC through the NCP.
If the CELL DELETION REQUEST message includes a C-ID IE value that does not exist in the NodeB, the NodeB sends through
the NCP to the CRNC the CELL DELETION RESPONSE message, in which the value of Criticality Diagnostics is "Not existing".
4.4 Using the RNC LMT to Trace the Cell Deletion Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell deletion.
Prerequisites
Context
Interface to Be
Traced
Message Name in
Protocols
Iub
NBAP_CELL_DEL_REQ
CELL DELETION
REQUEST
NBAP_CELL_DEL_RSP
CELL DELETION
RESPONSE
9/5/2016
HEEX Startpage
Page 18 of 156
Procedure
Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 4-2 shows an example of Iub signaling tracing result.
Location Update Procedure
A location update is performed for the UE to report its location to the CN. This chapter describes the location update in terms of
protocols, trigger conditions, signaling procedure of successful location update, and signaling tracing on the RNC LMT. This topic
also describes the elementary procedures in terms of functions, trigger conditions, and signaling in normal and abnormal conditions.
5.1 Protocols Related to Location Update

The location update procedure complies with some 3GPP 25-series specifications and an ITU-T protocol.
z
3GPP TS 25.331 "Radio Resource Control (RRC)"
3GPP TS25.413 "UTRAN Iu interface RANAP signalling"
3GPP TS 24.008 "Core network protocols"
5.2 Trigger Conditions of Location Update

z
Location update is triggered after the UE is powered on.
z After being powered on, the UE searches for a cell and then receives broadcast messages. Then, the UE triggers a location
update procedure.
z A UE performs a location registration. Location registration includes location update for GPRS UEs and routing area update for
non-GPRS UEs. There are three types of location registration:
Normal location registration
A UE performs location registration in either of the following scenarios:

After being powered on, the UE selects an appropriate cell in the new registration area (LA or RA),
which is different from the one previously stored in the USIM.
A UE in idle mode enters a new LA or RA cell.
Periodic location registration
During a periodic location registration, the location of a UE is periodically sent to the network. The network determines whether the
UE is capable of services based on this information. Periodic location registration is controlled by a periodic location update timer
T3212 for non-GPRS operation or by a periodic routing area update timer T3312 for GPRS operation. The value of T3212 is
broadcast to the UE through SIB1, whereas the value of T3312 is sent to the UE through the ATTACH ACCEPT or ROUTING AREA
UPDATE ACCEPT message. The value of T3312 is unique within one RA. T3212 is specified by the T3212(BSC6900,BSC6910)
parameter on the RNC side, whereas T3312 is configured on the CN side.
T3212 is described as follows:
Upon switch-on of the UE or when the system information indicates that periodic location registration
shall be applied, and the timer T3212 is not running, the timer shall be loaded with a random value
between 0 and T3212(BSC6900,BSC6910) and started.
When T3212 has expired, a periodic location registration is triggered.
T3212 shall be prevented from triggering a periodic location update in connected mode. When the UE
returns to the idle mode, T3212 shall be initialized with respect to the broadcast time-out value, and
then restarted.
The UE performs a successful combined routing area update and a Gs-interface location update. A
combined routing area update includes location update and the CN uses T3312 for location update.
In this case, T3212 is not used, saving radio resources. In the following scenarios, T3212 is still
used: the network operation mode is changed, the UE processes only CS services, or the MSC is
disconnected from the SGSN.
9/5/2016
HEEX Startpage
Page 19 of 156
IMSI attach/detach
IMSI attach/detach makes fast location registration much easier under certain conditions. The system information will contain an
indicator indicating whether or not IMSI attach/detach operation is mandatory to use in the cell. The UE shall operate in accordance
with the received value of the indicator. A GPRS UE shall perform GPRS attach/detach procedures independent of the value of the
IMSI attach/detach indicator.
When the IMSI attach/detach operation is applied, a UE shall send an IMSI detach message to the CN when the UE is powered
down or the SIM is removed while being in the cell update or URA update state, in order to prevent the CN from sending
unnecessary paging messages.
When the UE returns to the active state,
The UE shall initiate an LR request indicating IMSI attach, provided that the UE is still in the same registration area.
If the registration area has changed, an LR request indicating normal location update is performed.
The ATT(BSC6900,BSC6910) parameter in the ADD UCNDOMAIN or MOD UCNDOMAIN command is used to control whether to
allow the UE to perform an IMSI attach/detach.
For details about IMSI attach/detach, see 4.5.4 "IMSI attach/detach operation" in 3GPP TS 23.122 V10.0.0.
5.3 Signaling Procedure of a Successful Location Update
This section describes the signaling procedure of a successful location update. For the messages related to location update failures,
see the elementary procedures.
Figure 5-1 shows the signaling procedure of a successful location update.
Figure 5-1 Signaling procedure of a successful location update
The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection setup on the DCH as an
example.
If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or
deleted.
5.4 Using the RNC LMT to Trace the Location Update Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a location update.
Prerequisites
z
Context
Interface
to Be
Traced
Message Name in
Protocols
9/5/2016
HEEX Startpage
Page 20 of 156
Interface
to Be
Traced
Message Name in
Protocols
Uu
RRC_RRC_CONNECT_REQ
RRC
CONNECTION
REQUEST
RRC_RRC_CONN_SETUP
RRC
CONNECTION
SETUP
RRC_RRC_CONN_REJ
RRC
CONNECTION
REJECT
RRC_RRC_CONNECT_SETUP_CMP RRC
CONNECTION
SETUP
COMPLETE
Iub
Iu
RRC_INIT_DIRECT_TRANSF
INITIAL DIRECT
TRANSFER
RRC_DL_DIRECT_TRANSF
DOWNLINK
DIRECT
TRANSFER
RRC_UL_DIR_TRANSF
UPLINK DIRECT
TRANSFER
RRC_RRC_CONN_REL
RRC
CONNECTION
RELEASE
RRC_RRC_CONN_REL_CMP
RRC
CONNECTION
RELEASE
COMPLETE
NBAP_RL_SETUP_REQ
RADIO LINK
SETUP REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK
SETUP
RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK
SETUP FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
RANAP_INITIAL_UE_MESSAGE
INITIAL UE
MESSAGE
RANAP_COMMON_ID
COMMON ID
RANAP_DIRECT_TRANSFER
DIRECT
TRANSFER
RANAP_IU_RELEASE_COMMAND
IU RELEASE
COMMAND
RANAP_IU_RELEASE_COMPLETE
IU RELEASE
COMPLETE
Procedure
9/5/2016
HEEX Startpage
Page 21 of 156
Step 2 Create a Uu tracing task by referring to Creating an RNC Tracing Task. Figure 5-2 shows an example of Uu signaling tracing result.
Figure 5-2 Example of Uu signaling tracing result
Step 4 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 5-4 shows an example of Iu signaling tracing result.
Figure 5-4 Example of Iu signaling tracing result
----End
5.5 Elementary Procedures of Location Update

This section describes the elementary procedures of location update in terms of trigger conditions and signaling procedures in
normal and abnormal conditions.

The RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup
is always initiated by the UE. One UE has a maximum of one RRC connection at a time.
Trigger Conditions
The UE in idle mode initiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a
signaling connection.
Procedure
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, based on a specific algorithm. If the RRM
module accepts the request, it further determines whether to set up the RRC connection on a Dedicated Channel (DCH) or on a
Common Channel (CCH), based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
RRC connection setup procedure on a DCH
Figure 5-5 shows the procedure for setting up an RRC connection on a DCH.
Figure 5-5 RRC connection setup procedure on a DCH
9/5/2016
HEEX Startpage
Page 22 of 156

1.
The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH, requesting the
establishment of an RRC connection.
2.
Based on the cause of the RRC connection request and the system resource status, the SRNC determines to set up the RRC
connection on a DCH and allocates the Radio Network Temporary Identity (RNTI), radio resources, and L1 and L2 resources. Then
the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link
resources required for an RRC connection.
3.
The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the
resources.
4.
The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and performs the synchronization between
the SRNC and the NodeB. This procedure is optional. This step is performed only for ATM transmission on the Iub interface.
5.
The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CCCH. The message contains
information about the DCH allocated by the SRNC.
6.
The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control
Channel (DCCH) that is just set up. The message indicates that the RRC connection setup procedure ends.
RRC connection setup procedure on a CCH
Figure 5-6 shows the procedure for setting up an RRC connection on a CCH.
Figure 5-6 RRC connection setup procedure on a CCH

1.
2.
connection on a CCH. The SRNC maps the logical channel of the UE onto a CCH in the cell. The SRNC then sends an RRC
CONNECTION SETUP message to the UE through the downlink CCCH. The message contains information about the CCH.
3.
The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink CCCH. The message
indicates that the RRC connection setup procedure ends.
RRC connection rejection procedure
Figure 5-7 shows the RRC connection rejection procedure.
Figure 5-7 RRC connection rejection procedure
9/5/2016
HEEX Startpage
Page 23 of 156

1.
2.
The SRNC determines to reject the RRC connection request, based on a specific algorithm. Then, the SRNC sends an RRC
CONNECTION REJECT message to the UE. The message indicates the reason for rejecting the RRC connection request.
5.5.2 Location Update Procedure

The location update procedure is performed to update the location of a UE.
Trigger Conditions
An RRC connection is set up between the UE and the Serving RNC (SRNC).
Procedure
Figure 5-8 shows the location update procedure.
Figure 5-8 Location update procedure

1.
The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC connection. The message contains
the non-access stratum (NAS) information to be sent to the CN by the UE.
2.
The SRNC sends an INITIAL UE MESSAGE to the CN over the Iu interface. The message contains LOCATION UPDATE
REQUEST and the UE information, such as the Temporary Mobile Subscriber Identity (TMSI), International Mobile Subscriber
Identity (IMSI), and Location Area Identity (LAI).
3.
The CN updates the location information of the UE and saves the new LAI. The CN might also perform authentication and
encryption. Then, the CN sends a DIRECT TRANSFER message to the SRNC. The message contains LOCATION UPDATE
ACCEPT and the TMSI that is assigned to the UE.
4.
The SRNC transparently sends the content of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT
TRANSFER message.
5.
The UE receives the LOCATION UPDATE ACCEPT information and sends an UPLINK DIRECT TRANSFER message to the
SRNC. The message contains the information such as the NAS information and the CN ID.
6.
The SRNC transparently sends the content of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT
TRANSFER message. The DIRECT TRANSFER message indicates TMSI REALLOCATION COMPLETE.
5.5.3 Iu Release Procedure

The Iu release procedure is performed for the CN to release an Iu connection and all the UTRAN resources related only to that Iu
connection.
Trigger Conditions
The Iu release procedure can be triggered in one of the following conditions:
z
The transaction between the UE and the CN is complete.
The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST
message.
The Serving Radio Network Subsystem (SRNS) is relocated.
The SRNS relocation is canceled after a relocation resource allocation procedure is complete.
Procedure
Figure 5-9 shows the Iu release procedure.
9/5/2016
HEEX Startpage
Page 24 of 156
Figure 5-9 Iu release procedure

1.
The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu release procedure. The message indicates
the cause for the release of the signaling connection.
After sending the IU RELEASE COMMAND message, the CN will not send further RANAP connection-oriented messages on this
particular connection.
2.
The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.

The RRC connection release procedure is performed to release the signaling connection and all radio bearers between the UE and
the UTRAN.
Trigger Conditions
After an RAB is released, the SRNC determines whether the RRC connection carries any other RAB of the UE. If the RRC
connection does not carry any other RAB of the UE, the SRNC initiates an RRC connection release procedure.
Procedure
Based on the resource occupied by the RRC connection, there are two types of RRC connection release procedure: release of an
RRC connection from a DCH and release of an RRC connection from a CCH.
If an RRC connection needs to be released after a successful outgoing call, the RRC connection on the DCH is released. If a radio
bearer fails to be set up, the RRC connection on the CCH is released.
Releasing an RRC Connection from a DCH
Figure 5-10 shows the procedure for releasing an RRC connection from a DCH.
Figure 5-10 RRC connection release procedure (from a DCH)

1.
The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH.
The SRNC may send the RRC CONNECTION RELEASE message several times to ensure that the UE can receive this message.
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 considers that the UE has released the RRC connection.
2.
The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
9/5/2016
HEEX Startpage
Page 25 of 156
3.
The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, 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. Then, the RRC
connection release procedure ends. This step is performed only for ATM transmission on the Iub interface.
Releasing an RRC Connection from a CCH
Figure 5-11 shows the procedure for releasing an RRC connection from a CCH.
Figure 5-11 RRC connection release procedure (from a CCH)

1.
The SRNC sends an RRC CONNECTION RELEASE message to the UE through the CCCH.
2.
Outgoing Call Procedure
The outgoing call procedure is performed for a UE to call another terminal, such as a Public Switched Telephony Network (PSTN)
terminal. This chapter describes outgoing call setup and release in terms of protocols, trigger conditions, signaling procedure of a
successful outgoing call, and signaling tracing on the RNC LMT. This topic also describes the elementary procedures in terms of
functions, trigger conditions, and signaling in normal and abnormal conditions.
6.1 Protocols Related to an Outgoing Call

The outgoing call procedure complies with some 3GPP 25-series specifications and an ITU-T protocol.
z
6.2 Trigger Conditions of an Outgoing Call

An outgoing call is made by a UE when the UE calls another terminal.
Therefore, the trigger condition is that a UE calls a mobile phone or fixed-line phone when the UE camps on a cell.
6.3 Signaling Procedure of a Successful Outgoing Call

This section describes the signaling procedure of a successful outgoing call. For the messages related to outgoing call failures, see
the elementary procedures.
Figure 6-1 shows the signaling procedure of a successful outgoing call.
Figure 6-1 Signaling procedure of a successful outgoing call
9/5/2016
HEEX Startpage
Page 26 of 156
example.
z
If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up,
reconfigured, or deleted.
z
If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on the Iu-CS interface after an RAB is set up or
a call is released.
z
6.4 Using the RNC LMT to Trace the Outgoing Call Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an outgoing call.
Prerequisites
z
Context
9/5/2016
HEEX Startpage
Page 27 of 156

to Be
Traced
Message Name in
Protocols
Uu
RRC_RRC_CONNECT_REQ
RRC CONNECTION
REQUEST
RRC_RRC_CONN_SETUP
RRC CONNECTION
SETUP
RRC_RRC_CONN_REJ
RRC CONNECTION
REJECT
RRC_RRC_CONNECT_SETUP_CMP
RRC CONNECTION
SETUP COMPLETE
INITIAL DIRECT
TRANSFER
DOWNLINK DIRECT
TRANSFER
RRC_UL_DIR_TRANSF
UPLINK DIRECT
TRANSFER
RRC_SECURITY_MODE_CMD
SECURITY MODE
COMMAND
RRC_SECURITY_MODE_CMP
SECURITY MODE
COMPLETE
RRC_SECURITY_MODE_FAIL
SECURITY MODE
FAILURE
RRC_RB_SETUP
RADIO BEARER
SETUP
RRC_RB_SETUP_CMP
RADIO BEARER
SETUP COMPLETE
RRC_RB_SETUP_FAIL
RADIO BEARER
SETUP FAILURE
RRC_RRC_CONN_REL
RRC CONNECTION
RELEASE
RRC CONNECTION
RELEASE
COMPLETE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_RECFG_PREP
RADIO LINK
RECONFIGURATION
PREPARE
NBAP_RL_RECFG_REDAY
RADIO LINK
RECONFIGURATION
READY
NBAP_RL_RECFG_FAIL
RADIO LINK
RECONFIGURATION
FAILURE
NBAP_RL_RECFG_COMMIT
RADIO LINK
RECONFIGURATION
COMMIT
Iub
9/5/2016
HEEX Startpage
Page 28 of 156

to Be
Traced
Iu
Message Name in
Protocols
NBAP_RL_RECFG_CANCEL
RADIO LINK
RECONFIGURATION
CANCEL
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
INITIAL UE
MESSAGE
RANAP_COMMON_ID
COMMON ID
DIRECT TRANSFER
RANAP_SECURITY_MODE_COMMAND
SECURITY MODE
COMMAND
RANAP_SECURITY_MODE_COMPLETE SECURITY MODE

COMPLETE
RANAP_SECURITY_MODE_REJ
SECURITY MODE
REJECT
RANAP_RAB_ASSIGNMENT_REQ
RAB ASSIGNMENT
REQUEST
RANAP_RAB_ASSIGNMENT_RESP
RAB ASSIGNMENT
RESPONSE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE
Procedure
As shown in Figure 6-2, multiple RRC_UL_DIR_TRANSF messages and RRC_DL_DIRECT_TRANSF messages are traced. That is
because the UE and the RNC exchange signaling several times during the outgoing call procedure. The RRC_UL_DIR_TRANSF
messages have different content, and so do the RRC_DL_DIRECT_TRANSF messages.
9/5/2016
HEEX Startpage
Page 29 of 156
As shown in Figure 6-4, multiple RANAP_DIRECT_TRANSFER messages are traced. That is because the RNC and the CN
exchange signaling several times during the outgoing call procedure. The RANAP_DIRECT_TRANSFER messages have different
content.
----End
6.5 Elementary Procedures of an Outgoing Call

This section describes the elementary procedures of an outgoing call in terms of trigger conditions and signaling procedures in
If a UE supports PS services after being powered on, the UE must support the GPRS attach procedure.
Trigger Conditions
Procedure

1.
2.
9/5/2016
HEEX Startpage
Page 30 of 156
3.
resources.
4.
5.
6.

1.
2.
3.

1.
2.
6.5.3 Signaling Connection Setup Procedure (Outgoing Call)

The signaling connection setup procedure is performed to exchange the NAS information between the UE and the CN. The NAS
information is related to authentication, service request, connection setup, and so on.
Trigger Conditions
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 6-8 shows the signaling connection setup procedure.
9/5/2016
HEEX Startpage
Page 31 of 156
Figure 6-8 Signaling connection setup procedure

1.
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
over 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.
The CN sends a response message to the SRNC.
If the CN accepts the request, it sends a CONNECTION CONFIRM (CC) message to the SRNC. The message indicates that the
SCCP connection is set up. After receiving the message, the SRNC confirms that the signaling connection is set up.
If the CN rejects the request, it sends a CONNECTION REJECT (CJ) message to the SRNC. The message indicates that the
SCCP connection fails to be set up. After receiving the message, the SRNC confirms that the signaling connection fails to be set up
and then initiates the RRC release procedure.

The authentication and security mode control procedure is performed between the UE and the network to implement bidirectional
authentication and to negotiate and configure the integrity protection algorithm and encryption algorithm. This procedure ensures
integrity and correctness of signaling.
Trigger Conditions
The UE and the CN exchange signaling. The network initiates the authentication and security mode control procedure.
Procedure
Figure 6-9 shows the authentication and security mode control procedure.
Figure 6-9 Authentication and security mode control procedure

1.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains AUTHENTICATION REQUEST.
2.
TRANSFER message.
3.
The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4.
TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS Subscriber Identity Module (USIM) determines that
the authentication is successful, the UE returns a message with an XRES IE.
5.
The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the security mode control procedure. The
message contains information about the supported encryption and integrity protection algorithms.
9/5/2016
HEEX Startpage
Page 32 of 156
6.
The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of the integrity protection and
encryption algorithms that the UTRAN selects.
7.
The UE sends a response message to the SRNC.
If the integrity protection and encryption algorithms are configured successfully, the UE sends a SECURITY MODE COMMAND
COMPLETE message to the SRNC. The SRNC then sends a SECURITY MODE COMMAND COMPLETE message to the CN. The
message contains information about the integrity protection and encryption algorithms that the UE uses.
If the UE does not support the integrity protection and encryption algorithms, the UE sends a SECURITY MODE COMMAND
FAILURE message to the SRNC. The message contains the error information and the failure cause. The SRNC then sends a
SECURITY MODE COMMAND REJECT message to the CN.
6.5.5 Call Setup Procedure (Outgoing Call)

The call setup procedure is performed to set up a call.
Trigger Conditions
The UE initiates a call.
Procedure
Figure 6-10 shows the call setup procedure.
Figure 6-10 Call setup procedure (outgoing call)

1.
The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the number of the called party
and the information about the bearer capability of the call.
2.
TRANSFER message.
3.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains CALL PROCEEDING and information
about the negotiated bearer capability of the call.
9/5/2016
HEEX Startpage
Page 33 of 156
4.
TRANSFER message.
5.
A Radio Access Bearer (RAB) is set up. For details, see section 6.5.6 "RAB Setup Procedure."
6.
When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC. The message contains
ALERTING.
7.
TRANSFER message.
8.
The CN sends the SRNC a DIRECT TRANSFER message with "cm-msg-type" being "connect", indicating that the called party
has given a response.
9.
The SRNC transparently sends the received message to the UE through a DOWNLINK DIRECT TRANSFER message.
10.
11. The SRNC transparently sends the content of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT
TRANSFER message, indicating CONNECT ACKNOWLEDGE.
The call is set up. The calling and called parties begin the conversation.

The RAB setup procedure is performed to set up a user plane bearer.
Trigger Conditions
A call is set up.
Procedure
Successful RAB Setup Procedure
Figure 6-11 shows the successful RAB setup procedure.
9/5/2016
HEEX Startpage
Page 34 of 156
Figure 6-11 Successful RAB setup procedure

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 AAL2 link characteristic parameters and radio
resource characteristic parameters. Based on the AAL2 link characteristic parameters, the ALCAP on the Iu interface initiates an Iu
user plane transport bearer setup procedure. This step is performed only for ATM transmission on the Iub interface.
3.
The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, requesting the NodeB to add one
or more DCHs to the existing radio links for carrying the RAB.
4.
The NodeB allocates the associated resources and then sends a RADIO LINK RECONFIGURATION READY message to the
SRNC.
5.
The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform
synchronization by exchanging uplink and downlink synchronization frames in the DCH frame protocol. This step is performed only
for ATM transmission on the Iub interface.
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 the 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. The RAB is set up.
Failing to Set Up an RAB
Figure 6-12 shows the RAB setup failure procedure.
Figure 6-12 RAB setup failure procedure

1.
2.
The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indicates the ID of the RAB that fails
to be set up and the failure cause.
6.5.7 Call Release Procedure (Outgoing Call)

The call release procedure is performed to release services and resources after a call ends.
Trigger Conditions
A call ends and the calling party hangs up.
Procedure
Figure 6-13 shows the call release procedure.
Figure 6-13 Call release procedure (outgoing call)
9/5/2016
HEEX Startpage
Page 35 of 156

1.
2.
TRANSFER message, indicating DISCONNECT. This content informs the CN that the UE has hung up.
3.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains RELEASE to request release of the call.
4.
TRANSFER message.
5.
6.
TRANSFER message, indicating RELEASE COMPLETE.
7.
The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interface. The message
indicates the reason for the Iu release.
8.
The ALCAP protocol on the Iu interface initiates an Iu data transport bearer release procedure. This step is performed only for
ATM transmission on the Iub interface.
9.
The SRNC sends an IU RELEASE COMPLETE message to the CN.
the UTRAN.
Trigger Conditions
Procedure
9/5/2016
HEEX Startpage
Page 36 of 156

1.
2.
3.
4.
5.

1.
2.
Incoming Call Procedure
In the incoming call procedure, the network calls a UE and the UE responds to the paging. This chapter describes incoming call
setup and release in terms of protocols, trigger conditions, signaling procedure of a successful incoming call, and signaling tracing
on the RNC LMT. This topic also describes the elementary procedures in terms of functions, trigger conditions, and signaling in
7.1 Protocols Related to an Incoming Call

The incoming call procedure complies with some 3GPP 25-series specifications.
z
9/5/2016
HEEX Startpage
Page 37 of 156
7.2 Trigger Conditions of an Incoming Call

An incoming call is received by a UE when a mobile phone or fixed-line phone calls the UE.
Therefore, the trigger condition is that a network pages a UE that camps on a cell.
7.3 Signaling Procedure of a Successful Incoming Call

This section describes the signaling procedure of a successful incoming call. For the messages related to incoming call failures, see
Figure 7-1 shows the signaling procedure of a successful incoming call.
Figure 7-1 Signaling procedure of a successful incoming call
example.
z
z
9/5/2016
HEEX Startpage
Page 38 of 156
If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on the Iu-CS interface after an RAB is set up or
a call is released.
7.4 Using the RNC LMT to Trace the Incoming Call Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an incoming call.
Prerequisites
z
Context

to Be
Traced
Message Name in
Protocols
Uu
RRC_PAGING_TYPE1
PAGING TYPE 1
RRC_PAGING_TYPE2
PAGING TYPE 2
RRC_RRC_CONNECT_REQ
RRC CONNECTION
REQUEST
RRC_RRC_CONN_SETUP
RRC CONNECTION
SETUP
RRC_RRC_CONN_REJ
RRC CONNECTION
REJECT
RRC CONNECTION
SETUP COMPLETE
INITIAL DIRECT
TRANSFER
DOWNLINK DIRECT
TRANSFER
RRC_UL_DIR_TRANSF
UPLINK DIRECT
TRANSFER
SECURITY MODE
COMMAND
SECURITY MODE
COMPLETE
SECURITY MODE
FAILURE
RRC_RB_SETUP
RADIO BEARER
SETUP
RRC_RB_SETUP_CMP
RADIO BEARER
SETUP COMPLETE
RRC_RB_SETUP_FAIL
RADIO BEARER
SETUP FAILURE
RRC_RRC_CONN_REL
RRC CONNECTION
RELEASE
RRC CONNECTION
RELEASE
COMPLETE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
Iub
9/5/2016
HEEX Startpage
Page 39 of 156

to Be
Traced
Iu
Message Name in
Protocols
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_RECFG_PREP
RADIO LINK
RECONFIGURATION
PREPARE
NBAP_RL_RECFG_REDAY
RADIO LINK
RECONFIGURATION
READY
NBAP_RL_RECFG_FAIL
RADIO LINK
RECONFIGURATION
FAILURE
RADIO LINK
RECONFIGURATION
COMMIT
RADIO LINK
RECONFIGURATION
CANCEL
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
RANAP_PAGING
PAGING
INITIAL UE
MESSAGE
RANAP_COMMON_ID
COMMON ID
DIRECT TRANSFER
SECURITY MODE
COMMAND

COMPLETE
SECURITY MODE
REJECT
RAB ASSIGNMENT
REQUEST
RAB ASSIGNMENT
RESPONSE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE
Procedure
9/5/2016
HEEX Startpage
Page 40 of 156
because the UE and the RNC exchange signaling several times during the incoming call procedure. The RRC_UL_DIR_TRANSF
messages have different content, and so do the RRC_DL_DIRECT_TRANSF messages.
exchange signaling several times during the incoming call procedure. The RANAP_DIRECT_TRANSFER messages have different
content.
----End
7.5 Elementary Procedures of an Incoming Call

This section describes the elementary procedures of an incoming call in terms of trigger conditions and signaling procedures in
7.5.1 Paging Procedure

The paging procedure is performed when the CN calls a UE.
Trigger Conditions
A terminal calls the UE.
Procedure
Paging a UE that Is in Idle Mode or in PCH State
Figure 7-5 shows the procedure for paging a UE that is in idle mode or in PCH state.
Figure 7-5 Paging procedure (for a UE that is in idle mode or in PCH state)
9/5/2016
HEEX Startpage
Page 41 of 156

1.
The CN sends a PAGING message to the SRNC.
2.
The SRNC initiates the paging procedure by sending a PAGING TYPE 1 message to the UE through the Paging Control
Channel (PCCH) on an appropriate occasion.
The paging occasion is related to the International Mobile Subscriber Identity (IMSI) of the UE. The UTRAN may page the same UE
on several occasions to increase the probability of proper reception of the paging message by the UE.
3.
The UE in idle mode or in PCH state monitors the paging and receives the paging message from the network layer.
The paging procedure ends.

Paging a UE that Is in the CELL_DCH or CELL_FACH State
Figure 7-6 shows the procedure for paging a UE that is in the CELL_DCH or CELL_FACH state.
Figure 7-6 Paging procedure (for a UE that is in the CELL_DCH or CELL_FACH state)

1.
The CN sends a PAGING message to the SRNC.
2.
The SRNC initiates the paging procedure by sending a PAGING TYPE 2 message to the UE through the DCCH.
3.
The UE receives the PAGNG TPYE 2 message, reads it, and then reports to the NAS the information such as the paging
cause and the paging record type identifier.
The paging procedure ends.
Trigger Conditions
Procedure
9/5/2016
HEEX Startpage
Page 42 of 156

1.
2.
3.
resources.
4.
5.
6.

1.
2.
3.
9/5/2016
HEEX Startpage
Page 43 of 156

1.
2.
7.5.3 Signaling Connection Setup Procedure (Incoming Call)

Trigger Conditions
Procedure

1.
2.
NAS information is PAGING RESPONSE.
3.
If the CN rejects the request, it sends a CONNECTION REJECT (CJ) message to the SRNC. The message indicates that the
SCCP connection fails to be set up. After receiving the message, the SRNC confirms that the signaling connection fails to be set up
and then initiates the RRC release procedure.
Trigger Conditions
Procedure
9/5/2016
HEEX Startpage
Page 44 of 156

1.
2.
TRANSFER message.
3.
4.
TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS Subscriber Identity Module (USIM) determines that
the authentication is successful, the UE returns a message with an XRES IE.
5.
6.
7.
If the UE does not support the integrity protection and encryption algorithms, the UE sends a SECURITY MODE COMMAND
FAILURE message to the SRNC. The message contains the error information and the failure cause. The SRNC then sends a
SECURITY MODE COMMAND REJECT message to the CN.
7.5.5 Call Setup Procedure (Incoming Call)

The call setup procedure is performed to set up a call.
Trigger Conditions
A UE receives a call from the CN.
Procedure
Figure 7-12 shows the call setup procedure.
Figure 7-12 Call setup procedure (incoming call)
9/5/2016
HEEX Startpage
Page 45 of 156

1.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains SETUP and the number of the calling
party and the bearer capability of the call.
2.
TRANSFER message.
3.
4.
TRANSFER message. The DIRECT TRANSFER message indicates CALL CONFIRM and contains information about the negotiated
bearer capability of the call.
5.
An RAB is set up. For details, see section 7.5.6 "RAB Setup Procedure."
6.
7.
TRANSFER message, indicating ALERTING to request the called terminal to ring.
8.
9.
TRANSFER message, indicating CONNECT. This means that the called party has answered the call.
10.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains CONNECT ACKNOWLEDGE.
11. The SRNC transparently sends the content of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT
TRANSFER message.

Trigger Conditions
A call is set up.
Procedure
Successful RAB Setup Procedure
Figure7-13 shows the successful RAB setup procedure.

1.
2.
The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio
resource characteristic parameters. Based on the AAL2 link characteristic parameters, the ALCAP on the Iu interface initiates an Iu
user plane transport bearer setup procedure. This step is performed only for ATM transmission on the Iub interface.
3.
4.
SRNC.
5.
9/5/2016
HEEX Startpage
Page 46 of 156
6.
The SRNC sends a RADIO BEARER SETUP message to the UE.
7.
8.
9.
The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB is set up.
Failing to Set Up an RAB

1.
2.
The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indicates the ID of the RAB that fails
to be set up and the failure cause.
7.5.7 Call Release Procedure (Incoming Call)

The call release procedure is performed to release services and resources after a call ends.
Trigger Conditions
A call ends and the calling party hangs up.
Procedure
Figure 7-15 shows the call release procedure.
Figure 7-15 Call release procedure (incoming call)

1.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains DISCONNECT to inform the UE that the
calling party has hung up.
2.
TRANSFER message.
3.
4.
TRANSFER message. The DIRECT TRANSFER message indicates RELEASE which requests release of the call.
5.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains RELEASE COMPLETE.
6.
TRANSFER message.
7.
The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interface. The message
indicates the reason for the Iu release.
9/5/2016
HEEX Startpage
Page 47 of 156
8.
The ALCAP protocol on the Iu interface initiates an Iu data transport bearer release procedure. This step is performed only for
ATM transmission on the Iub interface.
9.
the UTRAN.
Trigger Conditions
Procedure

1.
2.
3.
4.
5.
9/5/2016
HEEX Startpage
Page 48 of 156

1.
2.
PS Service Setup Procedure
The PS service setup procedure is performed to set up services in the PS domain. This chapter describes PS service setup in terms
of protocols, trigger conditions, signaling procedure of successful PS service setup, and signaling tracing on the RNC LMT. This
topic also describes the elementary procedures in terms of functions, trigger conditions, and signaling in normal and abnormal
conditions.
8.1 Protocols Related to PS Service Setup
The PS service setup procedure complies with some 3GPP 25-series specifications and an ITU-T protocol.
z
3GPP TS25.413 "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling"
8.2 Trigger Conditions of PS Service Setup

UEs are used to browse web pages or play on-demand videos.
8.3 Signaling Procedure of Successful PS Service Setup
This section describes the signaling procedure of successful PS service setup. For the messages related to PS service setup
failures, see the elementary procedures.
Figure 8-1 Signaling procedure of successful PS service setup
Figure 8-1 Signaling procedure of successful PS service setup
9/5/2016
HEEX Startpage
Page 49 of 156
Note the following information about the procedure shown in Figure 8-1.
example.
z
z
z If IP transport is applied to the Iu-PS interface, no ALCAP procedure is performed on the Iu-PS interface after an RAB is set up or released.
8.4 Using the RNC LMT to Trace the PS Service Setup Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of PS service setup.
Prerequisites
z
Context
9/5/2016
HEEX Startpage
Page 50 of 156

to Be
Traced
Message Name in
Protocols
Uu
RRC_RRC_CONNECT_REQ
RRC CONNECTION
REQUEST
RRC_RRC CONNECTION SETUP
RRC CONNECTION
SETUP
RRC_RRC_CONN_REJ
RRC CONNECTION
REJECT
RRC CONNECTION
SETUP COMPLETE
INITIAL DIRECT
TRANSFER
DOWNLINK DIRECT
TRANSFER
RRC_UL_DIR_TRANSF
UPLINK DIRECT
TRANSFER
SECURITY MODE
COMMAND
SECURITY MODE
COMPLETE
SECURITY MODE
FAILURE
RRC_RB_SETUP
RADIO BEARER
SETUP
RRC_RB_SETUP_CMP
RADIO BEARER
SETUP COMPLETE
RRC_RB_SETUP_FAIL
RADIO BEARER
SETUP FAILURE
RRC_RRC_CONN_REL
RRC CONNECTION
RELEASE
RRC CONNECTION
RELEASE
COMPLETE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_RECFG_PREP
RADIO LINK
RECONFIGURATION
PREPARE
NBAP_RL_RECFG_REDAY
RADIO LINK
RECONFIGURATION
READY
NBAP_RL_RECFG_FAIL
RADIO LINK
RECONFIGURATION
FAILURE
RADIO LINK
RECONFIGURATION
COMMIT
Iub
9/5/2016
HEEX Startpage
Page 51 of 156

to Be
Traced
Iu
Message Name in
Protocols
RADIO LINK
RECONFIGURATION
CANCEL
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
INITIAL UE
MESSAGE
RANAP_COMMON_ID
COMMON ID
DIRECT TRANSFER
SECURITY MODE
COMMAND

COMPLETE
SECURITY MODE
REJECT
RAB ASSIGNMENT
REQUEST
RAB ASSIGNMENT
RESPONSE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE
Procedure
Step 2 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 8-2 shows an example of Uu signaling tracing result.
because the UE and the RNC exchange signaling several times during the call procedure. The RRC_UL_DIR_TRANSF messages
have different content, and so do the RRC_DL_DIRECT_TRANSF messages.
Step 3 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 8-3 shows an example of Iub signaling tracing result.
9/5/2016
HEEX Startpage
Page 52 of 156
Step 4 Create an Iu tracing task by referring to Creating an RNC Tracing Task.

Figure 8-4 shows an example of Iu signaling tracing result.
exchange signaling several times during the call procedure. The RANAP_DIRECT_TRANSFER messages have different content.
----End
8.5 Elementary Procedures of PS Service Setup
This section describes the elementary procedures of PS service setup in terms of trigger conditions and signaling procedures in
Trigger Conditions
Procedure
When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the RRM module of the RNC determines
whether to accept or reject the RRC connection request, based on a specific algorithm. If the RRM module accepts the request, it
further determines whether to set up the RRC connection on a DCH or on a CCH, based on a specific RRM algorithm. Typically, an
RRC connection is set up on the DCH.
RRC Connection Setup on a DCH
Figure 8-5 Procedure for setting up an RRC connection on a DCH
9/5/2016
HEEX Startpage
Page 53 of 156

1.
establishment of an RRC connection. The Original SubscribedTrafficCALL cause carried in the message indicates that the service to
be set up may an interactive service or BE service. The message contains information about the signal quality of the serving cell of
the UE.
2.
connection on a DCH and allocates the RNTI, radio resources, and L1 and L2 resources.
3.
The SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific
radio link resources required for an RRC connection.
4.
resources.
5.
the SRNC and the NodeB. This procedure is optional. It is required for the ATM-based Iub interface only.
6.
information about the DCH allocated by the SRNC. The RRC connection is set up in the CELL_DCH state. In this case, if the UE
has an H-RNTI, the signaling is carried on the HSDPA. If the UE has an E-RNTI, the signaling is carried on the HSUPA. If the UE
9/5/2016
HEEX Startpage
Page 54 of 156
has neither an H-RNTI nor an E-RNTI, the signaling is carried on the DCH. The following figure shows the signaling carried on the
DCH.
An RRC CONNECTION SETUP message contains configuration information about the channel setup for SRB 1 to SRB 4 and
information about the RLC mode, as shown in the following figure.
The RRC CONNECTION SETUP message contains configuration information about physical channel setup for the air interface. The
channels include uplink DPCH, downlink DPCH, and PCPICH.
7.
The UE sends an RRC CONNECTION SETUP_CMP message to the SRNC after the UE receives an RRC CONNECTION
SETUP message and completes the channel synchronization. The RRC CONNECTION SETUP_CMP message indicates that the
RRC connection setup procedure ends. The message contains information about radio access capabilities and HSPA capabilities for
service capability match.
hsdsch-physical-layer-category: HSDPA capability
edch-PhysicalLayerCategory: HSUPA capability
9/5/2016
HEEX Startpage
Page 55 of 156
RRC Connection Setup on a CCH
Figure 8-6 Procedure for setting up an RRC connection on a CCH

1.
2.
connection on a CCH.
3.
The SRNC maps the logical channel of the UE onto a CCH in the cell.
4.
information about the CCH.
5.
RRC connection rejected

9/5/2016
HEEX Startpage
Page 56 of 156
1.
2.
The SRNC determines to reject the RRC connection request, based on a specific algorithm. Then, the SRNC sends an RRC CONNECTION
REJECT message to the UE. The message indicates the reason for rejecting the RRC connection request.
8.5.2 Signaling Connection Setup Procedure
Trigger Conditions
Procedure

1.
2.
NAS information is SERVICE REQUEST.
3.
If the CN rejects the request, it sends a CONNECTION REJECT (CJ) message to the SRNC. The message indicates that the SCCP
connection fails to be set up. After receiving the message, the SRNC confirms that the signaling connection fails to be set up and then initiates the
RRC release procedure.
9/5/2016
HEEX Startpage
Page 57 of 156
Trigger Conditions
Procedure

1.
2.
TRANSFER message.
3.
4.
TRANSFER message, indicating AUTHENTICATION RESPONSE. If the USIM determines that the authentication is successful, the
UE returns a message with an XRES IE.
5.
6.
7.
9/5/2016
HEEX Startpage
Page 58 of 156
If the UE does not support the integrity protection and encryption algorithms, the UE sends a SECURITY MODE COMMAND FAILURE
message to the SRNC. The message contains the error information and the failure cause. The SRNC then sends a SECURITY
MODE COMMAND REJECT message to the CN.
8.5.4 PS Service Setup Procedure
The PS service setup procedure is performed to set up a PS service.

Trigger Conditions
A UE initiates a PS service setup procedure.
Procedure
Figure 8-10 shows the PS service setup procedure.
Figure 8-10 PS service setup procedure

1.
The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains ACT PDP CONTEXT
REQUEST and description of QoS. The message indicates the delay level, reliability level of services, maximum peak rate, priority
of services, throughput of services, service type, transmission sequence, transmission mode of error SDUs, size of the largest SDU,
maximum uplink and downlink bit rate, residual BLER, SDU BLER, transmission priority, guaranteed uplink and downlink bit rate.
9/5/2016
HEEX Startpage
Page 59 of 156
2.
TRANSFER message.
3.
An RAB is set up. For details, see section 6.5.6 "RAB Setup Procedure."
4.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains ACT PDP CONTEXT ACCEPT, and the
PDP address allocated to the UE.
The PDP address C0 A8 A1 2B is a hexadecimal IP address and indicates that the IP address allocated to the UE is
192.168.161.43.
5.
The SRNC transparently sends the content of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER
message.

Trigger Conditions
The PS service setup is requested.
Procedure
Successful RAB setup procedure
Figure 8-11 shows the successful RAB setup procedure.

9/5/2016
HEEX Startpage
Page 60 of 156

1.
trafficClass: indicates the service type. The following figure shows an interactive service.
maxBitrate: indicates the maximum bit rate. The following figure shows the maximum bit rate of 8.64 Mbit/s.
transportLayerAddress: indicates the address of the peer SGSN GTPU. In most cases, the IP transmission or IP over ATM is used.
Both of them use IP paths.
IP address of the GTPU shown in the following figure: C3 C3 C3 96 is a hexadecimal IP address and indicates that the IP address of
the GTPU is 195.195.195.150. 195.195.195.150 is the destination address of the Iu-PS IP path. For details, see ADD IPPATH.
2.
3.
SRNC.
4.
5.
The SRNC sends a RADIO BEARER SETUP message to the UE. The message contains the activation time and RRC state
indication. If the RRC connection is set up in the CELL_DCH state and the UE has an H-RNTI, services are set up on the HSDPA. If
the RRC connection is set up in the CELL_DCH state and the UE has an E-RNTI, services are set up on the HSUPA. If the RRC
9/5/2016
HEEX Startpage
Page 61 of 156
connection is set up in the CELL_DCH state and the UE has neither an H-RNTI nor an E-RNTI, R99 PS services are set up. The
following figure shows that services are set up on the HSDPA and HSUPA.
transportFormatSet: indicates the transport format on the transmission channel.
6.
7.
8.
After receiving the RADIO BEARER SETUP COMPLETE message, the SRNC sends an RAB ASSIGNMENT RESPONSE
message to the CN. The RAB is set up.
transportLayerAddress: indicates the user plane IP address of the local RNC.
B3 1G 33 36 shown in the following figure is a hexadecimal IP address and indicates that the user plane IP address of the RNC is
179.27.51.54. 179.27.51.54 is the destination IP address of the Iu-CS IP path. For details, see ADD IPPATH.
RAB setup failure procedure
9/5/2016
HEEX Startpage
Page 62 of 156


1.
2.
The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up
and the failure cause.

8.5.6 PS Service Release Procedure
The PS service release procedure is performed to release services and resources after a PS service ends.
Trigger Conditions
A UE releases a signaling connection or the UTRAN releases an inactive user.
The UTRAN requests the CN to release the Iu interface, for example, by sending an IU RELEASE REQUEST message to the CN.
Procedure
Based on the triggering causes, there are two types of PS service release procedure: normal release and abnormal release. The
normal release includes the signaling connection release by a UE and the user inactivity release by the UTRAN.
Signaling connection release by a UE
Figure 8-13 shows the procedure of a signaling connection release by a UE.

Figure 8-13 Procedure of a signaling connection release
PS service release procedure
9/5/2016
HEEX Startpage
1.
Page 63 of 156
2.
TRANSFER message. The message contains dea PDP CONTEXT REQUEST to inform the UTRAN to release the PS service.
3.
The CN sends a DIRECT TRANSFER message to the SRNC. The message contains dea PDP CONTEXT ACCEPT.
4.
TRANSFER message.
5.
The CN sends a RAB ASSIGNMENT REQUEST message to the SRNC to request a PS service release. The SRNC sends an
RB REL message to inform the UE to release the RB.
6.
The CN sends an IU RELEASE COMMAND message to the SRNC to request PS service release on the Iu interface. The
message indicates the reason for the Iu release.
7.
User inactivity release by the UTRAN
PS service release procedure
1.
The RNC sends an IU RELEASE REQUEST message (cause value: user-inactivity).
2.
The CN sends an IU RELEASE COMMAND message to the SRNC to request PS service release on the Iu interface. The message indicates
the reason for the Iu release.

Procedure of an abnormal PS service release
Figure 8-14 shows the procedure of an abnormal PS service release.

Figure 8-14 Procedure of an abnormal PS service release
9/5/2016
HEEX Startpage
Page 64 of 156

When a failure occurs, the RNC sends an RAB RELEASE REQUEST message or an IU RELEASE REQUEST message to the CN. When the RNC
receives from the CN an IU RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal Release", "Successful
Relocation", or "Network Optimization", the release procedure is triggered.
the UTRAN.
Trigger Conditions
Procedure
If an RRC connection needs to be released after a successful service, the RRC connection on the DCH is released. If a radio bearer
fails to be set up, the RRC connection on the CCH is released.

1.
9/5/2016
HEEX Startpage
Page 65 of 156
2.
3.
4.
5.

1.
2.
The attach procedure establishes a PS logical connection between a UE and the serving SGSN.
Trigger Conditions
The UE sends an INITIAL DIRECT TRANSFER message to initiate the attach procedure.
Procedure
Figure 8-17 shows the attach procedure.
Figure 8-17 Attach procedure
9/5/2016
HEEX Startpage
Page 66 of 156

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.
On receiving the INITIAL DIRECT TRANSFER message, the SRNC sends an INITIAL UE MESSAGE to the
CN over the Iu interface. The message contains the NAS information to be sent to the CN by the UE, that is,
an attach request.
3.
The SGSN sends an Identity Request message to the SRNC, which transparently sends the message to the
UE through the DOWNLINK DIRECT TRANSFER message.
4.
The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. On receiving the message, the
SRNC sends an Identity Response message to the SGSN.
5.
The SGSN performs authentication and initiates a security mode control procedure and then responds with
a message to the SRNC:
If the SGSN approves the attach request, the CN returns a DIRECT TRANSFER(Attach Accept) message to
the SRNC, indicating that the attach procedure is successful. The SRNC then forwards the message to the
UE.
If the SGSN does not approve the attach request, the CN sends a DIRECT TRANSFER(Attach Reject)
message to the SRNC to reject the attach request.
6.
If the SGSN approves the attach request, the SRNC returns a DIRECT TRANSFER(Attach Complete) message to the
CN.
8.5.9 Detach Procedure
The detach procedure disconnects the PS logical connection between a UE and the serving SGSN.
Trigger Conditions
The detach procedure can be initiated by the UE or by the network side. Figure 8-18 and Figure 8-19 show the detach procedure
initiated by the UE and by the network side, respectively.
Procedure
Figure 8-18 shows the detach procedure initiated by the UE.

Figure 8-18 Detach procedure initiated by the UE

1.
The UE sends an UPLINK DIRECT TRANSFER message to the SRNC through the RRC connection. The
message contains the NAS to be sent to the CN by the UE.
2.
On receiving the UPLINK DIRECT TRANSFER message, the SRNC sends a DIRECT TRANSFER(Detach
Req) message to the CN over the Iu interface.
3.
The SGSN sends a Delete PDP Context Request message to the GGSN, requesting the GGSN to
deactivate the UE's PDP context.
4.
The GGSN deactivates the PDP context of the UE and then returns a Delete PDP Context Response
message to the SGSN.
5.
On receiving the message, the SGSN sends a DIRECT TRANSFER(Detach Accept) message to the SRNC.
6.
The SRNC transparently sends the DIRECT TRANSFER(Detach Accept) message to the UE through the
DOWNLINK DIRECT TRANSFER message.
7.
After the detach procedure is complete, the SGSN releases the UE's PS signaling connection of the UE.
9/5/2016
HEEX Startpage
Page 67 of 156
Figure 8-19 shows the detach procedure initiated by the network side.
Figure 8-19 Detach procedure initiated by the network side

1.
The SGSN sends a DIRECT TRANSFER(Detach Req) message to the SRNC to initiate the detach
procedure.
2.
The SRNC transparently forwards the DIRECT TRANSFER(Detach Req) message to the UE through the
DOWNLINK DIRECT TRANSFER message.
3.
The SGSN sends a Delete PDP Context Request message to the GGSN, requesting the GGSN, requesting
the GGSN to deactivate the UE's PDP context.
4.
The GGSN deactivates the UE's PDP context and sends a Delete PDP Context Response message to the
SGSN.
5.
The UE sends a UPLINK DIRECT TRANSFER message to the SRNC at a time after receiving the DIRECT
TRANSFER(Detach Req) message.
6.
On receiving the message, the SRNC sends a DIRECT TRANSFER(Detach Accept) message to the SGSN.
After the detach procedure is complete, the SGSN releases the UE's PS signaling connection.
Intra-Frequency Handover Procedure
The intra-frequency handover procedure is performed to hand over a UE from the WCDMA cell that it camps on to an intrafrequency WCDMA cell. This chapter describes intra-frequency handover in terms of types, protocols, trigger conditions, signaling
procedure of a successful intra-frequency handover, and signaling tracing on the RNC LMT. This topic also describes the
9.1 Protocols Related to Intra-Frequency Handover
The intra-frequency handover procedure complies with some 3GPP 25-series specifications.
The compliance 3GPP specifications are as follows:
z
9.2 Trigger Conditions of Intra-Frequency Handover
When the signal quality reaches the minimum threshold and the relative threshold for soft handover, the UE reports intra-frequency
events to trigger an intra-frequency handover. Intra-frequency events are marked by 1X, which include the following types of events:
z Event 1A: Link addition event, indicating that the signal quality of a cell is close to that of the best cell or that of cells in UE's active
set. If the UE's active set is full, no more event 1A is reported and a soft handover leg will be added.
z Event 1B: link deletion event, indicating that the signal quality of a cell is far worse than that of the best cell or that of cells in the
active set, which means that a soft handover leg will be deleted.
Event 1C: cell replacement event, indicating that the signal quality of a cell is better than that of a cell in the active set and a cell in
the active set is about to be replaced.
z
9/5/2016
HEEX Startpage
Page 68 of 156
z Event 1D: change of the best cell. If the current best cell is in the active set, change the best cell. If the current best cell is in the
monitored set, add this cell to the active set and change the best cell. In addition, the measurement control message must carry
parameters of the current best cell. Intra-frequency hard handover can be triggered only through event 1D.
z
Event 1F: The measured signal quality is worse than an absolute threshold.
9.3 Types of Intra-Frequency Handover
Based on the connections between the UE and the network during the handover, intra-frequency handovers are categorized into two
types: intra-frequency soft handover and intra-frequency hard handover.
Table 9-1 lists the types of intra-frequency handover.
Table 9-1 Types of intra-frequency handover
Type
Subtype
Description
Intra-frequency
soft handover
Intra-frequency soft
handover within a
NodeB, that is, softer
handover
During an intra-frequency
soft handover, the UE sets
up a connection to the
target cell before
disconnecting from the
source cell.
During an intra-frequency
hard handover, the UE
disconnects from the
source cell before setting
up a connection towards
the target cell.
handover is common, and
intra-frequency hard
handover is applied only in
special scenarios, for
example, a handover
between two RNCs where
no Iur interface exists.
handover between
NodeBs in an RNC
handover between
RNCs
Intra-frequency
hard handover
Intra-frequency hard
handover between
NodeBs in an RNC
Intra-frequency hard
handover between
RNCs
9.4 Intra-Frequency Soft Handover Within a NodeB

The procedure of intra-frequency soft handover within a NodeB is performed to hand over a UE from a cell to an intra-frequency cell
that is controlled by the same NodeB.
9.4.1 Protocols Related to Intra-Frequency Soft Handover Within a NodeB

The procedure of intra-frequency soft handover within a NodeB complies with some 3GPP 25-series of specifications.
z
9.4.2 Trigger Conditions of Intra-Frequency Soft Handover Within a NodeB

Intra-frequency soft handover within a NodeB is the intra-frequency soft handover where the source and target cells are controlled
by the same NodeB.
The handover is triggered when the signal quality of the serving cell is degraded or the load of the serving cell is heavy.
9.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Within a NodeB

This section describes the signaling procedure of a successful intra-frequency soft handover within a NodeB. For the messages
related to handover failures, see the elementary procedures.
Figure 9-1 shows the signaling procedure of a successful intra-frequency soft handover within a NodeB.
Figure 9-1 Signaling procedure of a successful intra-frequency soft handover within a NodeB
9/5/2016
HEEX Startpage
Page 69 of 156
9.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Within a NodeB
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover
within a NodeB.
Prerequisites
z
Context
Interface to Message Name on the LMT

Be Traced
Message Name in
Protocols
Uu
ACTIVE SET
UPDATE
RRC_ACTIVE_SET_UPDATE
RRC_ACTIVE_SET_UPDATE_CMP ACTIVE SET

UPDATE
COMPLETE
Iub
RRC_ACTIVE_SET_UPDATE_FAIL
ACTIVE SET
UPDATE FAILURE
NBAP_RL_ADD_REQ
RADIO LINK
ADDITION
REQUEST
NBAP_RL_ADD_RSP
RADIO LINK
ADDITION
RESPONSE
NBAP_RL_ADD_FAIL
RADIO LINK
ADDITION
FAILURE
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
Procedure
9/5/2016
HEEX Startpage
Page 70 of 156
----End
9.4.5 Elementary Procedures of Intra-Frequency Soft Handover Within a NodeB

This section describes the elementary procedures of intra-frequency soft handover within a NodeB in terms of trigger conditions and
signaling procedures in normal and abnormal conditions.
Radio Link Addition Procedure
The radio link addition procedure is performed to add one or more radio links towards a UE.
Trigger Conditions
The CRNC sends a RADIO LINK ADDITION REQUEST message.

Procedure
Figure 9-4 shows the radio link addition procedure.
Figure 9-4 Radio link addition procedure

1.
The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB
reserves the necessary resources and configures the new radio link or links according to the parameters given in the message.
2.
The NodeB sends a response message to the CRNC.
If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the
RADIO LINK ADDITION REQUEST message and sends a RADIO LINK ADDITION RESPONSE message.
If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the
failure cause in the Cause IE.
Active Set Update Procedure

The active set update procedure is performed to update the active set of radio links between the UE and the UTRAN.
Trigger Conditions
The active set update procedure can be triggered in either of the following conditions:
z
Radio link addition
Radio link deletion
Procedure
Figure 9-5 shows the active set update procedure.
Figure 9-5 Active set update procedure
9/5/2016
HEEX Startpage
Page 71 of 156

1.
The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio
link addition. If a radio link needs to be deleted, the message indicates radio link deletion.
2.
The UE adds or deletes the radio links according to the Radio Link Addition Information or Radio Link Removal Information IE
contained in the ACTIVE SET UPDATE message.
3.
If adding or deleting the radio links successfully, the UE sends an ACTIVE SET UPDATE COMPLETE message on the DCCH
by using Acknowledged Mode (AM) Radio Link Control (RLC).
If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain
the radio links specified by the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure

The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a
UE.
Trigger Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.

Procedure
Figure 9-6 shows the radio link deletion procedure.
Figure 9-6 Radio link deletion procedure

1.
The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB
deletes the radio links specified by the message.
2.

If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.
If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality
Diagnostics field in the message indicates the failure cause.
9.5 Intra-Frequency Soft Handover Between NodeBs in an RNC

The procedure of intra-frequency soft handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intrafrequency cell that is controlled by another NodeB in the same RNC.
9.5.1 Protocols Related to Intra-Frequency Soft Handover Between NodeBs in an RNC

The procedure of intra-frequency soft handover between NodeBs in an RNC complies with some 3GPP 25-series of specifications
and an ITU-T protocol.
z
9/5/2016
HEEX Startpage
Page 72 of 156
9.5.2 Trigger Conditions of Intra-Frequency Soft Handover Between NodeBs in an RNC

Intra-frequency soft handover between NodeBs in an RNC is the intra-frequency soft handover where the source and target cells are
controlled by different NodeBs in an RNC.
The handover is triggered when the SRNC finds that another cell has higher signal quality than the serving cell or that the load of the
serving cell is heavy.
9.5.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between NodeBs in an RNC
This section describes the signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC. For the
messages related to handover failures, see the elementary procedures.
Figure 9-7 shows the signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC.
Figure 9-7 Signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC
z
During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
deleted.
9.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between NodeBs in
an RNC
between NodeBs in an RNC.
Prerequisites
z
Context
Interface
and Protocol
to Be
Traced
Message Name in
Protocols
Uu
ACTIVE SET
UPDATE

UPDATE
COMPLETE
ACTIVE SET
UPDATE
FAILURE
9/5/2016
HEEX Startpage
Page 73 of 156
Q.AAL2
NBAP_RL_SETUP_REQ
RADIO LINK
SETUP
REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK
SETUP
RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK
SETUP FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
No message name needs to be

specified.
Procedure
Step 4 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task. Figure 9-10 shows an example of Q.AAL2 signaling
tracing result.
Figure 9-10 Example of Q.AAL2 signaling tracing result
----End
9.5.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC

This section describes the elementary procedures of intra-frequency soft handover between NodeBs in an RNC in terms of trigger
conditions and signaling procedures in normal and abnormal conditions.
Radio Link Setup Procedure (Intra-RNC Handover or GSM to WCDMA CS Handover)
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an
SRNC-controlled NodeB for a UE.
Trigger Conditions
The CRNC sends a RADIO LINK SETUP REQUEST message.

Procedure
9/5/2016
HEEX Startpage
Page 74 of 156
Figure 8-11 shows the radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover).
Figure 9-11 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)

1.
The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves
the necessary resources and configures the new radio link according to the parameters given in the message.
2.
If the radio link is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP
REQUEST message and sends a RADIO LINK SETUP RESPONSE message.
If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure
cause.
Iub User Plane Setup Procedure

Trigger Conditions
z
Procedure

1.
2.
Radio Link Restoration Procedure (Intra-RNC Handover or GSM to WCDMA CS Handover)

The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a NodeB to notify the
CRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.
Trigger Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization with the UE.
Procedure
Figure 9-13 shows the radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover).
9/5/2016
HEEX Startpage
Page 75 of 156
Figure 9-13 Radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC.
Trigger Conditions
z
Radio link addition
Radio link deletion
Procedure

1.
2.
3.

UE.
Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 76 of 156

1.
2.

Iub User Plane Release Procedure

The Iub user plane release procedure is performed to release data transport bearers from the Iub interface.
Trigger Conditions
The transport channels on the Iub user plane need to be removed.

Procedure
Figure 9-16 shows the Iub user plane release procedure.
Figure 9-16 Iub user plane release procedure

1.
2.
The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST message to the NodeB.
If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASE CONFIRM message that indicates the
failure cause.
9.6 Intra-Frequency Soft Handover Between RNCs

The procedure of intra-frequency soft handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell
that is controlled by another RNC.
9.6.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs

The procedure of intra-frequency soft handover between RNCs complies with some 3GPP 25-series of specifications and an ITU-T
protocol.
z
3GPP TS25.423 "UTRAN Iur interface RNSAP signalling"
9.6.2 Trigger Conditions of Intra-Frequency Soft Handover Between RNCs

Intra-frequency soft handover between RNCs is the intra-frequency soft handover where the source and target cells are controlled
by different RNCs.
9.6.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs
9/5/2016
HEEX Startpage
Page 77 of 156
This section describes the signaling procedure of a successful intra-frequency soft handover between RNCs. For the messages
Figure 9-17 shows the signaling procedure of a successful intra-frequency soft handover between RNCs.
Figure 9-17 Signaling procedure of a successful intra-frequency soft handover between RNCs
z
deleted.
If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iur interface after radio links are set up or
deleted.
9.6.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs
between RNCs.
Prerequisites
z
Context
Interface and
Protocol to
Be Traced
Message Name
in Protocols
Uu
ACTIVE SET
UPDATE

UPDATE
COMPLETE
ACTIVE SET
UPDATE
FAILURE
9/5/2016
HEEX Startpage
Page 78 of 156
Interface and
Protocol to
Be Traced
Iur
Q.AAL2
Message Name
in Protocols
NBAP_RL_SETUP_REQ
RADIO LINK
SETUP
REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK
SETUP
RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK
SETUP
FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
RNSAP_RL_SETUP_REQ
RADIO LINK
SETUP
REQUEST
RNSAP_RL_SETUP_RSP
RADIO LINK
SETUP
RESPONSE
RNSAP_RL_SETUP_FAIL
RADIO LINK
SETUP
FAILURE
RNSAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
No message name needs to be

specified.
Procedure
Step 3 Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 9-19 shows an example of Iub signaling tracing on the
source RNC.
Figure 9-19 Example of Iub signaling tracing result (source RNC)
Figure 9-20 shows an example of Iub signaling tracing on the target RNC.
Figure 9-20 Example of Iub signaling tracing result (target RNC)
Step 4 Create an Iur tracing task by referring to Creating an RNC Tracing Task. Figure 9-21 shows an example of Iur signaling tracing result.
9/5/2016
HEEX Startpage
Page 79 of 156
Figure 9-21 Example of Iur signaling tracing result
tracing result.
----End
9.6.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs

This section describes the elementary procedures of intra-frequency soft handover between RNCs in terms of trigger conditions and
Radio Link Setup Procedure (Inter-RNC Handover)

The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE.
Trigger Conditions
The SRNC sends a RADIO LINK SETUP REQUEST message.

Procedure
Figure 9-23 shows the radio link setup procedure for inter-RNC handover.
Figure 9-23 Radio link setup procedure (inter-RNC handover)

1.
The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC.
2.
The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB.
3.
The NodeB reserves the necessary resources and configures the new radio link according to the parameters given in the
message.
4.
The NodeB reports the radio link setup result to the DRNC.
5.
If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message.
The DRNC reports the radio link setup result to the SRNC.
If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSE message.
If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE message, indicating the failure cause.

9/5/2016
HEEX Startpage
Page 80 of 156
Trigger Conditions
z
Procedure

1.
2.
Radio Link Restoration Procedure (Inter-RNC Handover)

The radio link restoration procedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink
synchronization of one or more radio links is achieved or re-achieved.
Trigger Conditions
Procedure
Figure 9-25 shows the radio link restoration procedure for inter-RNC handover.
Figure 9-25 Radio link restoration procedure (inter-RNC handover)

1.
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the
DRNC.
2.
The DRNC sends a RADIO LINK RESTORE INDICATION message to the SRNC.
Iur User Plane Setup Procedure

The Iur user plane setup procedure is performed to set up bearers for data transmission on the Iur interface.
Trigger Conditions
The DCHs are set up.

Procedure
Figure 9-26 shows the Iur user plane setup procedure.
9/5/2016
HEEX Startpage
Page 81 of 156
Figure 9-26 Iur user plane setup procedure

1.
The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message to the DRNC.
2.
The DRNC uses the ALCAP protocol to send a response message to the SRNC.
If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISH CONFIRM message.
If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLISH RELEASE CONFIRM message.

Trigger Conditions
z
Radio link addition
Radio link deletion
Procedure

1.
2.
3.

UE.
Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 82 of 156

1.
2.


Trigger Conditions

Procedure

1.
2.
failure cause.
Iur User Plane Release Procedure

The Iur user plane release procedure is performed to release data transport bearers from the Iur interface.
Trigger Conditions
The transport channels on the Iur user plane need to be removed.

Procedure
Figure 9-30 shows the Iur user plane release procedure.
Figure 9-30 Iur user plane release procedure
9/5/2016
HEEX Startpage
Page 83 of 156

1.
The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST message to the DRNC.
2.
If the Iur data transport bearers are released, the DRNC sends a QAAL2 RELEASE CONFIRM message to confirm the release.
If an Iur data transport bearer fails to be released, the DRNC sends a QAAL2 RELEASE CONFIRM message that indicates the
failure cause.
9.7 Intra-Frequency Hard Handover Between NodeBs in an RNC

The procedure of intra-frequency hard handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intrafrequency cell that is controlled by another NodeB in the same RNC.
9.7.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC

The procedure of intra-frequency hard handover between NodeBs in an RNC complies with some 3GPP 25-series of specifications
and an ITU-T protocol.
z
9.7.2 Trigger Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC

Intra-frequency hard handover between NodeBs in an RNC is the intra-frequency hard handover where the source and target cells
are controlled by different NodeBs in an RNC.
9.7.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC
This section describes the signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC. For the
Figure 9-31 shows the signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC.
Figure 9-31 Signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC
z
9/5/2016
HEEX Startpage
Page 84 of 156
deleted.
z
9.7.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in
an RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency hard handover
Prerequisites
z
Context
Interface
and Protocol
to Be
Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG
PHYSICAL CHANNEL
RECONFIGURATION
RRC_PH_CH_RECFG_CMP PHYSICAL CHANNEL

RECONFIGURATION
COMPLETE
Iub
Q.AAL2
RRC_PH_CH_RECFG_FAIL
PHYSICAL CHANNEL
RECONFIGURATION
FAILURE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK RESTORE

INDICATION
NBAP_RL_DEL_REQ
RADIO LINK DELETION

REQUEST
NBAP_RL_DEL_RSP
RADIO LINK DELETION

RESPONSE
No message name needs to

be specified.
Procedure
9/5/2016
HEEX Startpage
Page 85 of 156
tracing result.
----End
9.7.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC

This section describes the elementary procedures of intra-frequency hard handover between NodeBs in an RNC in terms of trigger
Trigger Conditions

Procedure

1.
2.
cause.

Trigger Conditions
z
Procedure
9/5/2016
HEEX Startpage
Page 86 of 156

1.
2.

Trigger Conditions
Procedure
Physical Channel Reconfiguration Procedure
The physical channel reconfiguration procedure is performed to set up, reconfigure, or release a physical channel.
Trigger Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.

Procedure
Figure 9-38 shows the physical channel reconfiguration procedure.
Figure 9-38 Physical channel reconfiguration procedure

1.
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical
channel.
2.
The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.
3.
9/5/2016
HEEX Startpage
Page 87 of 156
If successfully reconfiguring the physical channels specified by the PHYSICAL CHANNEL RECONFIGURATION message, the
UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC.
If failing to reconfigure the physical channels specified by the PHYSICAL CHANNEL RECONFIGURATION message, the UE
restores the configuration to the old physical channel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL
RECONFIGURATION FAILURE message is "physical channel failure".

UE.
Trigger Conditions

Procedure

1.
2.


Trigger Conditions

Procedure

1.
2.
9/5/2016
HEEX Startpage
Page 88 of 156
failure cause.
9.8 Intra-Frequency Hard Handover Between RNCs

The procedure of intra-frequency hard handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell
that is controlled by another RNC.
9.8.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs

The procedure of intra-frequency hard handover between RNCs complies with some 3GPP 25-series of specifications and an ITU-T
protocol.
z
9.8.2 Trigger Conditions of Intra-Frequency Hard Handover Between RNCs

Intra-frequency hard handover between RNCs is the intra-frequency hard handover where the source and target cells are controlled
by different RNCs.
9.8.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs

This section describes the signaling procedure of a successful intra-frequency hard handover between RNCs. For the messages
Figure 9-41 shows the signaling procedure of a successful intra-frequency hard handover between RNCs.
Figure 9-41 Signaling procedure of a successful intra-frequency hard handover between RNCs
z
deleted.
z
deleted.
z
9.8.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between RNCs
9/5/2016
HEEX Startpage
Page 89 of 156
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency hard handover
between RNCs.
Prerequisites
z
Context
Interface
and Protocol
to Be
Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG
PHYSICAL CHANNEL
RECONFIGURATION

RECONFIGURATION
COMPLETE
Iub
Iur
PHYSICAL CHANNEL
RECONFIGURATION
FAILURE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK RESTORE

INDICATION
NBAP_RL_DEL_REQ
RADIO LINK DELETION

REQUEST
NBAP_RL_DEL_RSP
RADIO LINK DELETION

RESPONSE
RNSAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
RNSAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
RNSAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
RNSAP_RL_RESTORE_IND RADIO LINK RESTORE

INDICATION
Q.AAL2

be specified.
Procedure
Step 3 Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 9-43 shows an example of Iub signaling tracing on the
source RNC.
9/5/2016
HEEX Startpage
Page 90 of 156
tracing result.
----End
9.8.5 Elementary Procedures of Intra-Frequency Hard Handover Between RNCs

This section describes the elementary procedures of intra-frequency hard handover between RNCs in terms of trigger conditions
and signaling procedures in normal and abnormal conditions.
Trigger Conditions

Procedure

1.
2.
3.
message.
4.
9/5/2016
HEEX Startpage
5.
Page 91 of 156

Trigger Conditions
z
Procedure

1.
2.

Trigger Conditions
Procedure

1.
DRNC.
2.

9/5/2016
HEEX Startpage
Page 92 of 156
Trigger Conditions

Procedure

1.
2.

Trigger Conditions

Procedure

1.
channel.
2.
3.

UE.
Trigger Conditions
9/5/2016
HEEX Startpage
Page 93 of 156

Procedure

1.
2.


Trigger Conditions

Procedure

1.
2.
failure cause.

Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 94 of 156

1.
2.
failure cause.
10
Inter-Frequency Handover Procedure
The inter-frequency handover procedure is performed to hand over a UE from the WCDMA cell that it camps on to an interfrequency WCDMA cell. This chapter describes inter-frequency handover in terms of types, protocols, trigger conditions, signaling
procedure of a successful inter-frequency handover, and signaling tracing on the RNC LMT. This topic also describes the
10.1 Protocols Related to Inter-Frequency Handover
The inter-frequency handover procedure complies with some 3GPP 25-series specifications.
z
10.2 Trigger Conditions of Inter-Frequency Handover
Inter-frequency measurement can be periodically triggered or event-triggered. If inter-frequency measurement is

periodically triggered, the UE periodically sends an inter-frequency measurement report to the RNC to trigger an
inter-frequency handover. If inter-frequency measurement is event-triggered, the UE sends an inter-frequency
measurement event report to the RNC to trigger an inter-frequency handover procedure. Inter-frequency events are
marked by 2X, which include the following types of events:
z Event 2B: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a nonused frequency is above a certain threshold.
z
Event 2C: The estimated quality of a non-used frequency is above a certain threshold.
z Event 2D: The estimated quality of the currently used frequency is below a certain threshold. This event is used for starting the compressed
mode.
Event 2F: The estimated quality of the currently used frequency is below a certain threshold. This event is used for stopping the
compressed mode.
z

During a compressed mode procedure:
1.
The RNC receives from a UE an event 2D or an event 2F report.
2.
The RNC delivers compressed mode parameters to the UE and NodeB.
3.
The RNC sends a compressed mode activation or deactivation message to the UE and NodeB based on the received event.
When the CMP_IUR_CMCF_SWITCH is set to off, the RNC sends compressed mode parameters to the UE and NodeB through
the PHYSICAL CHANNEL RECONFIGURATION and RADIO LINK RECONFIGURATION PREPARE message, respectively, and
activates the compressed mode for the UE and NodeB through the MEASUREMENT CONTROL and COMPRESS MODE
COMMAND message, respectively.
9/5/2016
HEEX Startpage
Page 95 of 156
When the CMP_IUR_CMCF_SWITCH is set to on, the RNC configures and activates the compressed mode for the UE and
NodeB through the PHYSICAL CHANNEL RECONFIGURATION and RADIO LINK RECONFIGURATION COMMIT message,
respectively.
The following figure shows the start of a compressed mode procedure when the CMP_IUR_CMCF_SWITCH is set to off.
The following figure shows the start of a compressed mode procedure when the CMP_IUR_CMCF_SWITCH is set to on.
Stop of a Compressed Mode Procedure

The stop of the compressed mode procedure is the same regardless of whether the CMP_IUR_CMCF_SWITCH is set to on or off.
10.4 Types of Inter-Frequency Handover

Inter-frequency handovers are categorized into two types: handover within an RNC and handover between RNCs.
Table 10-1 lists the types of inter-frequency handover.
Table 10-1 Types of inter-frequency handover
Type
Subtype
Description
Inter-frequency
handover within
an RNC
Inter-frequency
handover within
a NodeB
The procedures of the two

subtypes are similar. They are
described in the procedure of
inter-frequency handover
9/5/2016
HEEX Startpage
Page 96 of 156
Type
Subtype
Description
Inter-frequency
handover
between NodeBs
Inter-frequency
handover
between RNCs
Inter-frequency
handover
between RNCs
without relocation
Inter-frequency
handover
between RNCs
with UE-notinvolved
relocation
When a UE performs an interfrequency handover between

RNCs with UE-not-involved
relocation, an Iur interface must
be configured between the two
RNCs. When a UE performs an
inter-frequency handover
between RNCs with UE-involved
relocation, no Iur interface exists
between the two RNCs.
Inter-frequency
handover
between RNCs
with UE-involved
relocation
10.5 Inter-Frequency Handover Between NodeBs in an RNC

The procedure of inter-frequency handover between NodeBs in an RNC is performed to hand over a UE from a cell to an interfrequency cell that is controlled by the same RNC.
10.5.1 Protocols Related to Inter-Frequency Handover Between NodeBs in an RNC

The procedure of inter-frequency handover between NodeBs in an RNC complies with some 3GPP 25-series of specifications and
an ITU-T protocol.
z
10.5.2 Trigger Conditions of Inter-Frequency Handover Between NodeBs in an RNC

Inter-frequency handover between NodeBs in an RNC is the inter-frequency handover where the source and target cells are
controlled by different NodeBs in an RNC.
10.5.3 Signaling Procedure of a Successful Inter-Frequency Handover Between NodeBs in an RNC

This section describes the signaling procedure of a successful inter-frequency handover between NodeBs in an RNC. For the
Figure 10-1 shows the signaling procedure of a successful inter-frequency handover between NodeBs in an RNC.
Figure 10-1 Signaling procedure of a successful inter-frequency handover between NodeBs in an RNC
9/5/2016
HEEX Startpage
Page 97 of 156
The radio link setup procedure shown in the figure applies when the source and target cells of the handover are controlled by
different NodeBs. If the source and target cells are controlled by the same NodeB, the radio link setup procedure should be replaced
by the radio link addition procedure, and the radio link restoration procedure is excluded.
z
deleted.
z
10.5.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between NodeBs in an
RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between
NodeBs in an RNC.
Prerequisites
z
Context
Interface
and
Protocol to
Be Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG
PHYSICAL CHANNEL
RECONFIGURATION

RECONFIGURATION
COMPLETE
Iub
Q.AAL2
PHYSICAL CHANNEL
RECONFIGURATION
FAILURE
NBAP_RL_ADD_REQ
RADIO LINK ADDITION

REQUEST
NBAP_RL_ADD_RSP
RADIO LINK ADDITION

RESPONSE
NBAP_RL_ADD_FAIL
RADIO LINK ADDITION

FAILURE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK RESTORE

INDICATION
NBAP_RL_DEL_REQ
RADIO LINK DELETION

REQUEST
NBAP_RL_DEL_RSP
RADIO LINK DELETION

RESPONSE

be specified.
Procedure
9/5/2016
HEEX Startpage
Page 98 of 156
tracing result.
----End
10.5.5 Elementary Procedures of Inter-Frequency Handover Between NodeBs in an RNC

This section describes the elementary procedures of inter-frequency handover between NodeBs in an RNC in terms of trigger
Radio Link Addition Procedure
The radio link addition procedure is performed to add one or more radio links towards a UE.
Trigger Conditions
The CRNC sends a RADIO LINK ADDITION REQUEST message.
Procedure
Figure 10-5 shows the radio link addition procedure.
Figure 10-5 Radio link addition procedure

1.
The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB
reserves the necessary resources and configures the new radio link or links according to the parameters given in the message.
2.
If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the
RADIO LINK ADDITION REQUEST message and sends a RADIO LINK ADDITION RESPONSE message.
If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the
failure cause in the Cause IE.

Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 99 of 156

1.
2.
cause.

Trigger Conditions
z
Procedure

1.
2.

Trigger Conditions
Procedure
9/5/2016
HEEX Startpage
Page 100 of 156
Trigger Conditions

Procedure

1.
channel.
2.
3.

UE.
Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 101 of 156
1.
2.


Trigger Conditions

Procedure

1.
2.
failure cause.
10.6 Inter-Frequency Handover Between RNCs

The procedure of inter-frequency handover between RNCs is performed to hand over a UE from a cell to an inter-frequency cell that
is controlled by another RNC.
10.6.1 Protocols Related to Inter-Frequency Handover Between RNCs

The procedure of inter-frequency handover between RNCs complies with some 3GPP 25-series of specifications and an ITU-T
protocol.
z
3GPP TS25.423 "UTRAN Iur interface RNSANP signalling"
10.6.2 Trigger Conditions of Inter-Frequency Handover Between RNCs

Inter-frequency handover between RNCs is the inter-frequency handover where the source and target cells are controlled by
different RNCs.
10.6.3 Signaling Procedure of a Successful Inter-Frequency Handover Between RNCs

This section describes the signaling procedure of a successful inter-frequency handover between RNCs. For the messages related
to handover failures, see the elementary procedures.
Figure 10-12 shows the signaling procedure of a successful inter-frequency handover between RNCs.
Figure 10-12 Signaling procedure of a successful inter-frequency handover between RNCs
9/5/2016
HEEX Startpage
Page 102 of 156
z
deleted.
deleted.
10.6.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between RNCs
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between
RNCs.
Prerequisites
z
Context
Interface
and
Protocol to
Be Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG
PHYSICAL CHANNEL
RECONFIGURATION

RECONFIGURATION
COMPLETE
Iub
PHYSICAL CHANNEL
RECONFIGURATION
FAILURE
NBAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
NBAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK RESTORE

INDICATION
9/5/2016
HEEX Startpage
Page 103 of 156
Iur
NBAP_RL_DEL_REQ
RADIO LINK DELETION

REQUEST
NBAP_RL_DEL_RSP
RADIO LINK DELETION

RESPONSE
RNSAP_RL_SETUP_REQ
RADIO LINK SETUP

REQUEST
RNSAP_RL_SETUP_RSP
RADIO LINK SETUP

RESPONSE
RNSAP_RL_SETUP_FAIL
RADIO LINK SETUP

FAILURE
RNSAP_RL_RESTORE_IND RADIO LINK RESTORE

INDICATION
Q.AAL2

be specified.
Procedure
Step 3 Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 10-14 shows an example of Iub signaling tracing on
the source RNC.
tracing result.
----End
9/5/2016
HEEX Startpage
Page 104 of 156
10.6.5 Elementary Procedures of Inter-Frequency Handover Between RNCs

This section describes the elementary procedures of inter-frequency handover between RNCs in terms of trigger conditions and
Trigger Conditions

Procedure

1.
2.
3.
message.
4.
5.

Trigger Conditions
z
Procedure
9/5/2016
HEEX Startpage
Page 105 of 156
The procedure shown in Figure10-19 is described as follows:

1.
2.

Trigger Conditions
Procedure

1.
DRNC.
2.

Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 106 of 156

1.
2.

Trigger Conditions

Procedure

1.
channel.
2.
3.

UE.
Trigger Conditions

Procedure
9/5/2016
HEEX Startpage
Page 107 of 156
1.
2.


Trigger Conditions

Procedure

1.
2.
failure cause.

Trigger Conditions

Procedure

1.
2.
failure cause.
9/5/2016
HEEX Startpage
11
Page 108 of 156
Inter-RAT Handover Procedure
The inter-RAT handover procedure is performed to hand over a UE from a WCDMA cell to a GSM cell or the other way round. This
chapter describes inter-RAT handover in terms of types, protocols, trigger conditions, signaling procedure of a successful inter-RAT
handover, and signaling tracing on the RNC LMT. This topic also describes the elementary procedures in terms of functions, trigger
conditions, and signaling in normal and abnormal conditions.
11.1 Protocols Related to Inter-RAT Handover
The inter-RAT handover procedure complies with some 3GPP 25-series specifications.
z
11.2 Trigger Conditions of Inter-RAT Handover
Inter-RAT measurement can be periodically triggered or event-triggered. As a type of inter-frequency handover, inter-RAT handover
requires inter-frequency measurement by staring the compressed mode. Inter-RAT handover is triggered when the UE sends a
periodic measurement report or an inter-RAT event report to the RNC. Inter-RAT events are marked by 3X, which include the
following types of events:
Event 2D: The estimated quality of the currently used frequency is below a certain threshold. This event is used for starting the
compressed mode for GSM measurement.
z
Event 2F: The estimated quality of the currently used frequency is below a certain threshold. This event is used for stopping the
compressed mode for GSM measurement.
z
Event 3A: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a GSM
cell is above a certain threshold.
z
z Event 3C: The estimated quality of a GSM cell is above a certain threshold.
During a compressed mode procedure:

1.
The RNC receives from a UE an event 2D or an event 2F report.
2.
The RNC delivers compressed mode parameters to the UE and NodeB.
3.
The RNC sends a compressed mode activation or deactivation message to the UE and NodeB based on the received event.
z When the CMP_IUR_CMCF_SWITCH is set to off, the RNC sends compressed mode parameters to the UE and NodeB through the PHYSICAL
CHANNEL RECONFIGURATION and RADIO LINK RECONFIGURATION PREPARE message, respectively, and activates the compressed mode
for the UE and NodeB through the MEASUREMENT CONTROL and COMPRESS MODE COMMAND message, respectively.
z When the CMP_IUR_CMCF_SWITCH is set to on, the RNC configures and activates the compressed mode for the UE and
NodeB through the PHYSICAL CHANNEL RECONFIGURATION and RADIO LINK RECONFIGURATION COMMIT message,
respectively.
The following figure shows the start of a compressed mode procedure when the CMP_IUR_CMCF_SWITCH is set to off.
9/5/2016
HEEX Startpage
Page 109 of 156
The following figure shows the start of a compressed mode procedure when the CMP_IUR_CMCF_SWITCH is set to on.
Stop of a Compressed Mode Procedure

The stop of a compressed mode is the same regardless of whether the CMP_IUR_CMCF_SWITCH is set to on or off.
11.4 Types of Inter-RAT Handover

Based on the direction of handover, inter-RAT handovers are categorized into two types: inter-RAT handover from WCDMA to GSM
and inter-RAT handover from GSM to WCDMA.
Based on domains, inter-RAT handovers from WCDMA to GSM and those from GSM to WCDMA are further categorized into the
following types:
z
Inter-RAT CS handover from WCDMA to GSM
Inter-RAT PS handover from WCDMA to GSM
Inter-RAT CS handover from GSM to WCDMA
Inter-RAT PS handover from GSM to WCDMA
11.5 Inter-RAT CS Handover from WCDMA to GSM

The procedure of inter-RAT CS handover from WCDMA to GSM is performed to hand over the CS services of a UE from the
WCDMA system to the GSM system.
11.5.1 Protocols Related to Inter-RAT CS Handover from WCDMA to GSM
9/5/2016
HEEX Startpage
Page 110 of 156
The procedure of inter-RAT CS handover from WCDMA to GSM complies with some 3GPP 25-series of specifications.
z
11.5.2 Trigger Conditions of Inter-RAT CS Handover from WCDMA to GSM

The signal quality of the WCDMA cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy.
In such a condition, if the signal quality of a neighboring GSM cell is satisfactory and its load is relatively light, the UE will be handed
over from the WCDMA cell to the GSM cell.
11.5.3 Signaling Procedure of a Successful Inter-RAT CS Handover from WCDMA to GSM

This section describes the signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM. For the messages
Figure 11-1 shows the signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM.
Figure 11-1 Signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM
z This figure presents only a brief of the signaling between the MSC server and the MSC (GSM) and that between the MSC (GSM)
and the BSC (GSM).
z The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The message contains the RAB ID, the
activation time, the GSM frequency, and the GSM information in bit strings.
11.5.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from WCDMA to GSM
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from
WCDMA to GSM.
Prerequisites
z
Context

to Be
Traced
Message Name
in Protocols
9/5/2016
HEEX Startpage
Page 111 of 156
Uu
Iub
Iu
RRC_HO_FROM_UTRAN_CMD_GSM
HANDOVER
FROM UTRAN
COMMAND
RRC_HO_FROM_UTRAN_FAIL
HANDOVER
FROM UTRAN
FAILURE
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
RANAP_RELOCATION_REQUIRED
RELOCATION
REQUIRED
RANAP_RELOCATION_COMMAND
RELOCATION
COMMAND
RANAP_RELOCATION_PREPARATION_FAILURE RELOCATION
PREPARATION
FAILURE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE
Procedure
----End
11.5.5 Elementary Procedures of Inter-RAT CS Handover from WCDMA to GSM

This section describes the elementary procedures of inter-RAT CS handover from WCDMA to GSM in terms of trigger conditions
Relocation Preparation Procedure
The relocation preparation procedure is performed to prepare resources for relocation of the SRNS.
Trigger Conditions
The relocation preparation procedure can be triggered in either of the following conditions:
z
During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends a RELOCATION REQUIRED message.
9/5/2016
HEEX Startpage
Page 112 of 156
Procedure
Figure 11-5 shows the relocation preparation procedure.
Figure 11-5 Relocation preparation procedure

1.
The SRNC sends a RELOCATION REQUIRED message to the CN. The message contains certain information such as
relocation type, relocation cause, source PLMN, source LAC, source SAC, target PLMN, and target LAC.
2.
The CN interacts with the target RNC or the target network system, such as the GSM system, to prepare relevant resources.
3.
If the target RNC or the target network system prepares the relevant resources successfully, the CN sends a RELOCATION
COMMAND message when the preparation is complete. The message contains the L3 information IE, which carries the information
about the relevant resources allocated by the target RNC or the target network system.
If the resources partially or totally fail to be allocated, the CN sends a RELOCATION PREPARATION FAILURE message.
Iu Release Procedure
connection.
Trigger Conditions

z
z The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST
message.
z
Procedure

1.
2.
9/5/2016
HEEX Startpage
Page 113 of 156
UE.
Trigger Conditions

Procedure

1.
2.

11.6 Inter-RAT CS Handover from GSM to WCDMA

The procedure of inter-RAT CS handover from GSM to WCDMA is performed to hand over the CS services of a UE from the GSM
system to the WCDMA system.
11.6.1 Protocols Related to Inter-RAT CS Handover from GSM to WCDMA

The procedure of inter-RAT CS handover from GSM to WCDMA complies with some 3GPP 25-series of specifications.
z
11.6.2 Trigger Conditions of Inter-RAT CS Handover from GSM to WCDMA

The signal quality of the GSM cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy.
In such a condition, if the signal quality of a neighboring WCDMA cell is satisfactory and its load is relatively light, the UE will be
handed over from the GSM cell to the WCDMA cell.
11.6.3 Signaling Procedure of a Successful Inter-RAT CS Handover from GSM to WCDMA

This section describes the signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA. For the messages
Figure 11-8 shows the signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA.
Figure 11-8 Signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA
9/5/2016
HEEX Startpage
Page 114 of 156
This figure presents only a brief of the signaling between the MSC server and the MSC (GSM) and that between the MSC (GSM)
and the BSC (GSM).
After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a RELOCATION DETECT message to the
MSC server to inform the MSC server that the UE has been handed over from GSM to WCDMA.
After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fails, the UE
reports the failure to the GSM system.
After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a RELOCATION COMPLETE message to the
MSC server. In addition, the RNC controls the UE to perform the UTRAN mobility information procedure, the UE capability enquiry
procedure, and the security mode control procedure.
In practice, the signaling messages traced may differ from the signaling message shown in the figure in terms of the sequence.
11.6.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from GSM to WCDMA
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from GSM
to WCDMA.
Prerequisites
z
Context
Interface
to Be
Traced
Message Name in
Protocols
9/5/2016
HEEX Startpage
Page 115 of 156
Interface
to Be
Traced
Message Name in
Protocols
Uu
RRC_HO_UTRAN_CMP
HANDOVER TO
UTRAN
COMPLETE
RRC_UTRAN_MOBIL_INFO
UTRAN
MOBILITY
INFORMATION
RRC_UTRAN_MOBIL_INFO_CONFIRM UTRAN
MOBILITY
INFORMATION
CONFIRM
Iub
Iu
RRC_UTRAN_MOBIL_INFO_FAILURE
UTRAN
MOBILITY
INFORMATION
FAILURE
RRC_UE_CAP_ENQUIRY
UE CAPABILITY
ENQUIRY
RRC_UE_CAP_INFO
UE CAPABILITY
INFORMATION
RRC_UE_CAP_INFO_CONFIRM
UE CAPABILITY
INFORMATION
CONFIRM
SECURITY
MODE
COMMAND
SECURITY
MODE
COMPLETE
SECURITY
MODE FAILURE
NBAP_RL_SETUP_REQ
RADIO LINK
SETUP
REQUEST
NBAP_RL_SETUP_RSP
RADIO LINK
SETUP
RESPONSE
RNSAP_RL_SETUP_FAIL
RADIO LINK
SETUP FAILURE
NBAP_RL_RESTORE_IND
RADIO LINK
RESTORE
INDICATION
RANAP_RELOCATION_REQ
RELOCATION
REQUEST
RANAP_RELOCATION_REQ_ACK
RELOCATION
REQUEST
ACKNOWLEDGE
RANAP_RELOCATION_FAILURE
RELOCATION
FAILURE
RANAP_RELOCATION_DETECT
RELOCATION
DECTECT
RANAP_RELOCATION_COMPLETE
RELOCATION
COMPLETE
Procedure
9/5/2016
HEEX Startpage
Page 116 of 156
----End
11.6.5 Elementary Procedures of Inter-RAT CS Handover from GSM to WCDMA

This section describes the elementary procedures of inter-RAT CS handover from GSM to WCDMA in terms of trigger conditions
Relocation Resource Allocation Procedure
The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation.
Trigger Conditions
The relocation resource allocation procedure can be triggered in either of the following conditions:
z
During an SRNS relocation, the CN applies for resources from the target RNC.
During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources from the target RNC.
Procedure
Figure 11-12 shows the relocation resource allocation procedure.
Figure 11-12 Relocation resource allocation procedure

1.
The CN sends a RELOCATION REQUEST message to the target RNC. The message contains certain information, such as
the IMSI of the UE, CN domain indicator, target cell identifier, encryption, integrity protection, Iu signaling connection ID, handover
cause, and RAB parameters.
2.
The target RNC allocates radio resources for the relocation.
3.
The target RNC sends a response message to the CN.
9/5/2016
HEEX Startpage
Page 117 of 156
If the resources are allocated, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message
contains the radio resources and other parameters allocated to the UE. The parameters include the UTRAN Radio Network
Temporary Identifier (U-RNTI), RAB, transport layer and physical layer information, chosen encryption algorithm, and chosen
integrity protection algorithm.
If the resources partially or totally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target
RNC sends a RELOCATION FAILURE message, indicating the failure cause.

Trigger Conditions

Procedure

1.
2.
cause.

Trigger Conditions
Procedure
UE Capability Enquiry Procedure
The UE capability enquiry procedure is performed to request a UE to transmit its capability information related to any radio access
network so that the network can perform data configuration based on the UE capability.
9/5/2016
HEEX Startpage
Page 118 of 156
Trigger Conditions
The UTRAN sends a UE CAPABILITY ENQUIRY message to acquire the UE capability information related to any radio access
network.
Procedure
Figure 11-15 shows the UE capability enquiry procedure.
Figure 11-15 UE capability enquiry procedure

1.
The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
2.
The UE sends a UE CAPABILITY INFORMATION message to the SRNC through the uplink DCCH using AM or UM RLC. The
message contains information about UE capabilities.
3.
The SRNC reads the UE capability information and then sends a UE CAPABILITY INFORMA CONFIRM message to the UE
through the downlink DCCH using AM or UM RLC.
Security Mode Control Procedure
The security mode control procedure is performed to configure or reconfigure one or both of the encryption algorithm and the
integrity protection algorithm for a UE.
Trigger Conditions
The encryption algorithm or the integrity protection algorithm has changed.

Procedure
Figure 11-16 shows the security mode control procedure.
Figure 11-16 Security mode control procedure

1.
Through a SECURITY MODE COMMAND message sent to the UE, the SRNC starts or reconfigures one or both of the
encryption and integrity protection configurations for the RBs or one CN domain and for all Signaling Radio Bearers (SRBs).
2.
If the UE completes configuring or reconfiguring the relevant parameters for one or both of the encryption and integrity protection
algorithms, the UE sends a SECURITY MODE COMPLETE message to inform the SRNC of the completion.
If the SECURITY MODE COMMAND message contains neither Ciphering mode info IE nor Integrity protection mode info IE or if
each of the two IEs has inconsistent information, the UE sends a SECURITY MODE FAILURE message, indicating the failure of the
security mode control procedure as well as the failure cause.
UTRAN Mobility Information Procedure

The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary
Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information
such as timer values and CN domainrelated information.
9/5/2016
HEEX Startpage
Page 119 of 156
Trigger Conditions
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.

Procedure
Figure 11-17 shows the UTRAN mobility information procedure.
Figure 11-17 UTRAN mobility information procedure

1.
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
2.
The UE starts to update the related fields according to the values of the IEs carried in the message.
3.
If the UE succeeds in conducting the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a
UTRAN MOBILITY INFORMATION CONFIRM message.
If the UE fails to conduct the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN
MOBILITY INFORMATION FAILURE message, indicating the failure cause.
11.7 Inter-RAT PS Handover from WCDMA to GSM

The procedure of inter-RAT PS handover from WCDMA to GSM is performed to hand over the PS services of a UE from the
WCDMA system to the GSM system.
11.7.1 Protocols Related to Inter-RAT PS Handover from WCDMA to GSM

The procedure of inter-RAT PS handover from WCDMA to GSM complies with some 3GPP 25-series of specifications.
z
11.7.2 Trigger Conditions of Inter-RAT PS Handover from WCDMA to GSM

The signal quality of the WCDMA cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy.
When the UE is in the CELL_PCH, URA_PCH, or CELL_FACH state, the UE initiates cell reselection to perform a handover to
GSM.
When the UE is in the CELL_DCH state, the UTRAN sends a CELL CHANGE ORDER message to the UE to perform a handover
to GSM.
11.7.3 Signaling Procedure of a Successful Inter-RAT PS Handover from WCDMA to GSM

This section describes the signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM. For the messages
Figure 11-18 shows the signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM.
Figure 11-18 Signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM
9/5/2016
HEEX Startpage
Page 120 of 156
z When the PS data volume is low, the UE may be in the CELL_PCH, URA_PCH, or URA_FACH state. Based on the parameters in
the system information, the UE can initiate cell reselection to perform a handover to GSM. The cell reselection is initiated with an
SRNS CONTEXT REQUEST message sent from the SGSN to SRNC.
z After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message because the UE stops the
transmission towards the WCDMA cell. This message, however, is unnecessary to the procedure of inter-RAT PS handover from
WCDMA to GSM.
After the UE accesses a GSM cell, the SGSN directly sends an IU RELEASE COMMAND message to the SRNC, if the Packet
Data Protocol (PDP) context does not have to be transferred.
11.7.4 Using the RNC LMT to Trace the Procedure of Inter-RAT PS Handover from WCDMA to GSM
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT PS handover from
WCDMA to GSM.
Prerequisites
z
Context

to Be
Traced
Message
Name in
Protocols
Uu
CELL
CHANGE
ORDER
FROM
UTRAN
RRC_CELL_CHANGE_ORDER_FROM_UTRAN
RRC_CELL_CHANGE_ORDER_FROM_UTRAN_FAIL CELL
CHANGE
ORDER
FROM
UTRAN
FAILURE
Iub
NBAP_RL_FAIL_IND
RADIO LINK
FAILURE
INDICATION
9/5/2016
HEEX Startpage
Page 121 of 156
Iu
NBAP_RL_DEL_REQ
RADIO LINK
DELETION
REQUEST
NBAP_RL_DEL_RSP
RADIO LINK
DELETION
RESPONSE
RANAP_SRNS_CONTEXT_REQ
SRNS
CONTEXT
REQUEST
RANAP_SRNS_CONTEXT_RESP
SRNS
CONTEXT
RESPONSE
RANAP_SRNS_DATA_FORWARD_COMMAND
SRNS DATA
FORWARD
COMMAND
IU
RELEASE
COMMAND
IU
RELEASE
COMPLETE
Procedure
----End
11.7.5 Elementary Procedures of Inter-RAT PS Handover from WCDMA to GSM

This section describes the elementary procedures of inter-RAT PS handover from WCDMA to GSM in terms of trigger conditions
Cell Change Order from UTRAN Procedure
The cell change order from UTRAN procedure is performed to hand over, under the control of the network, a UE in the CELL_DCH
state to a GSM cell when the RABs established in the WCDMA system are only from the PS domain.
Trigger Conditions
The network decides to hand over the UE to the GSM system.
9/5/2016
HEEX Startpage
Page 122 of 156
Procedure
Figure 11-22 shows the cell change order from UTRAN procedure.
Figure 11-22 Cell change order from UTRAN procedure

1.
Through a CELL CHANGE ORDER FROM UTRAN message, the SRNC orders the UE to perform a cell change to the GSM
system. The message contains certain IEs about the target cell. The IEs include BSIC, Band indicator, BCCH ARFCN, and NC
mode.
2.
Upon reception of the CELL CHANGE ORDER FROM UTRAN message, the UE starts timer T309 and initiates access to the
GSM cell.
If the UE accesses the GSM cell before the timer expires, the procedure ends.
If the UE fails to access the GSM cell before the timer expires, the UE sends a CELL CHANGE ORDER FROM UTRAN
FAILURE message to the SRNC.
SRNS Context Transfer Procedure

The SRNS context transfer procedure is performed to transfer SRNS contexts from the source RNC to the SGSN.
Trigger Conditions
During the inter-RAT PS handover from WCDMA to GSM, the 2G equipment needs to get the PDP contexts of the UE from the 3G
equipment.
Procedure
Figure 11-23 shows the SRNS context transfer procedure.
Figure 11-23 SRNS context transfer procedure

1.
The SGSN sends an SRNS CONTEXT REQUEST message to the SRNC. The message includes the list of RABs whose
contexts should be transferred.
2.
The SRNC sends an SRNS CONTEXT RESPONSE message to the SGSN.
If the transfer is successful, the message contains RAB IDs that include the sequence numbers for the downlink and uplink GTP
PDUs and PDCP SDUs.
If the SRNC fails to identify the ID of the RAB whose context should be transferred to the SGSN, the SRNS CONTEXT
RESPONSE message contains a Cause IE whose value is "Invalid RAB ID".
connection.
Trigger Conditions
9/5/2016
HEEX Startpage
Page 123 of 156

z
message.
z
Procedure

1.
2.

UE.
Trigger Conditions

Procedure

1.
2.

11.8 Inter-RAT PS Handover from GSM to WCDMA
9/5/2016
HEEX Startpage
Page 124 of 156
The procedure of inter-RAT PS handover from GSM to WCDMA is performed through cell reselection to WCDMA that is initiated by
the UE.
For details, see chapter 4 Location Update Procedure.
12
SRNS Relocation Procedure
The SRNS relocation procedure is performed to change control from the SRNC of a UE to another RNC. This chapter describes the
SRNS relocation in terms of types, protocols, trigger conditions, signaling procedure of a successful SRNS relocation, and signaling
tracing on the RNC LMT. This topic also describes the elementary procedures in terms of functions, trigger conditions, and signaling
in normal and abnormal conditions.
12.1 Protocols Related to SRNS Relocation
The SRNS relocation procedure complies with some 3GPP 25-series specifications.
z
12.2 Trigger Conditions of SRNS Relocation
The RNC decides whether to trigger an SRNS relocation to change the serving RNC based on the setting of the relocation algorithm
switch, the parameter configurations, and the current UE link status.
12.3 Types of SRNS Relocation
Based on whether the connection between the UE and the DRNC is set up during the relocation, the SRNS relocations are
categorized into two types: UE-not-involved relocation and UE-involved relocation.
UE-involved SRNS relocations are categorized into the following subtypes:
Relocation with hard handover: An SRNS relocation is triggered when the UE performs an inter-RNC hard handover where no Iur
interface exists between the two RNCs.
z
Relocation with cell/URA update: This type of relocation is triggered when the UE performs a cell reselection to a cell under an
RNC between which and the SRNC no Iur interface exists.
12.4 Static Relocation

The static relocation procedure is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered after
a radio link is added to the DRNC for the UE. An Iur interface exists between the two RNCs involved in the relocation.
12.4.1 Protocols Related to Static Relocation

The static relocation procedure complies with some 3GPP 25-series of specifications.
z
12.4.2 Trigger Conditions of Static Relocation

All the radio links connected to the UE exist only in the DRNC.
After a radio link is added to the DRNC for the UE, if all the radio links exist only in the DRNC between which and the SRNC an Iur
interface is available, the SRNC initiates the static relocation procedure when the conditions for static relocation are met.
12.4.3 Signaling Procedure of a Successful Static Relocation

This section describes the signaling procedure of a successful static relocation. For the messages related to relocation failures, see
9/5/2016
HEEX Startpage
Page 125 of 156
Figure 12-1 shows the signaling procedure of a successful static relocation.
Figure 12-1 Signaling procedure of a successful static relocation
If the DRNC does not obtain the information about the UE capability, the DRNC initiates a UE capability enquiry procedure.
12.4.4 Using the RNC LMT to Trace the Static Relocation Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a static relocation.
Prerequisites
z
Context
Table 12-1 and Table 12-2 list the messages to be traced.
Table 12-1 Messages to be traced on the SRNC

to Be
Traced
Message Name
in Protocols
Iur
RNSAP_RELOC_COMMIT
RELOCATION
COMMIT
Iu
RELOCATION
REQUIRED
RELOCATION
COMMAND
PREPARATION
FAILURE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE
Table 12-2 Messages to be traced on the DRNC
9/5/2016
HEEX Startpage
Page 126 of 156
Interface
to Be
Traced
Message Name
in Protocols
Uu
RRC_UTRAN_MOBIL_INFO
UTRAN
MOBILITY
INFORMATION
RRC_UTRAN_MOBIL_INFO_CONFIRM UTRAN
MOBILITY
INFORMATION
CONFIRM
RRC_UTRAN_MOBIL_INFO_FAILURE
UTRAN
MOBILITY
INFORMATION
FAILURE
RRC_UE_CAP_ENQUIRY
UE CAPABILITY
ENQUIRY
RRC_UE_CAP_INFO
UE CAPABILITY
INFORMATION
UE CAPABILITY
INFORMATION
CONFIRM
Iur
RNSAP_RELOC_COMMIT
RELOCATION
COMMIT
Iu
RELOCATION
REQUEST
RELOCATION
REQUEST
ACKNOWLEDGE
RELOCATION
FAILURE
RELOCATION
DETECT
RELOCATION
COMPLETE
Procedure
Step 3 Create an Iur tracing task by referring to Creating an RNC Tracing Task. Figure 12-3 shows an example of Iur signaling tracing on the
SRNC.
Figure 12-3 Example of Iur signaling tracing on the SRNC
Figure 12-4 shows an example of Iur signaling tracing on the DRNC.
Figure 12-4 Example of Iur signaling tracing on the DRNC
Step 4 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 12-5 shows an example of Iu signaling tracing on the
SRNC.
9/5/2016
HEEX Startpage
Page 127 of 156
Figure 12-5 Example of Iu signaling tracing on the SRNC
Figure 12-6 shows an example of Iu signaling tracing on the DRNC.
Figure 12-6 Example of Iu signaling tracing on the DRNC
----End
12.4.5 Elementary Procedures of Static Relocation

This section describes the elementary procedures of static relocation in terms of trigger conditions and signaling procedures in
12.4.5.1 Relocation Preparation Procedure
Trigger Conditions
z
Procedure

1.
2.
3.
12.4.5.2 Relocation Resource Allocation Procedure

9/5/2016
HEEX Startpage
Page 128 of 156
Trigger Conditions
z
Procedure

1.
2.
3.
12.4.5.3 Relocation Commit Procedure (Static Relocation or Relocation with Cell/URA Update)
The relocation commit procedure is performed to execute the change of control from the SRNC of a UE to the DRNC.
Trigger Conditions
The CN sends a RELOCATION COMMAND message to the SRNC.

Procedure
Figure 12-9 shows the relocation commit procedure for the static relocation or relocation with cell/URA update.
Figure 12-9 Relocation commit procedure (static relocation or relocation with cell/URA update)
9/5/2016
HEEX Startpage
Page 129 of 156
1.
The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supporting lossless SRNS relocation is
available on the Iu-PS interface, the RELOCATION COMMIT message carries the GTP-U and PDCP sequence numbers required
for data forwarding. Then, the SRNC initiates data forwarding.
2.
The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of the detection of the relocation
commitment.
3.
The original DRNC sends a RELOCATION COMPLETE message to the CN to notify that the relocation is successful.
12.4.5.4 UTRAN Mobility Information Procedure

The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary
Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information
such as timer values and CN domainrelated information.
Trigger Conditions
The DRNC sends a UTRAN MOBILITY INFORMATION message to the UE.

Procedure
Figure 12-10 shows the UTRAN mobility information procedure.
Figure 12-10 UTRAN mobility information procedure

1.
The DRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
2.
The UE starts to update the related fields according to the values of the IEs carried in the message.
3.
The UE sends a response message to the DRNC.
If the UE succeeds in conducting the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a
UTRAN MOBILITY INFORMATION CONFIRM message.
If the UE fails to conduct the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN
MOBILITY INFORMATION FAILURE message, indicating the failure cause.
12.4.5.5 UE Capability Enquiry Procedure

Trigger Conditions
network.
9/5/2016
HEEX Startpage
Page 130 of 156
Procedure

1.
The DRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
2.
The UE sends a UE CAPABILITY INFORMATION message to the DRNC through the uplink DCCH using AM or UM RLC. The
3.
The DRNC reads the UE capability information and then sends a UE CAPABILITY INFORMA CONFIRM message to the UE
12.4.5.6 Iu Release Procedure
connection.
Trigger Conditions

z
Procedure

1.
9/5/2016
HEEX Startpage
Page 131 of 156
2.
12.5 Relocation with Hard Handover

The procedure of relocation with hard handover is performed to change control from the SRNC of a UE to the DRNC. The relocation
is triggered when the UE performs an inter-RNC hard handover, which can be either an intra-frequency hard handover or an interfrequency handover. No Iur interface exists between the two RNCs involved in the relocation.
12.5.1 Protocols Related to Relocation with Hard Handover

The procedure of relocation with hard handover complies with some 3GPP 25-series of specifications.
z
12.5.2 Trigger Conditions of Relocation with Hard Handover

The UE in the CELL_DCH state performs an inter-RNC hard handover, which can be either an intra-frequency hard handover or an
inter-frequency handover.
In such a condition, if no Iur interface exists between the two RNCs, the SRNC performs a relocation with hard handover.
12.5.3 Signaling Procedure of a Successful Relocation with Hard Handover

This section describes the signaling procedure of a successful relocation with hard handover. For the messages related to relocation
Figure 12-13 shows the signaling procedure of a successful relocation with hard handover.
Figure 12-13 Signaling procedure of a successful relocation with hard handover
9/5/2016
HEEX Startpage
Page 132 of 156
During the relocation with hard handover, if an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, the
SRNC sends the GTP-U and PDCP sequence numbers to the DRNC through the FORWARD SRNS CONTEXT message. The
sequence numbers are required for data forwarding.
After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, the DRNC sends a RELOCATION DETECT
message to the CN.
12.5.4 Using the RNC LMT to Trace the Procedure of Relocation with Hard Handover
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with hard handover.
Prerequisites
z
Context

to Be
Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG
PHYSICAL
CHANNEL
RECONFIGURATION
PHYSICAL
CHANNEL
RECONFIGURATION
FAILURE
RELOCATION
REQUIRED
RELOCATION
COMMAND
Iu
9/5/2016
HEEX Startpage
Page 133 of 156

to Be
Traced
Message Name in
Protocols
PREPARATION
FAILURE
RANAP_FORWARD_SRNS_CONTEXT
FORWARD SRNS
CONTEXT
IU RELEASE
COMMAND
IU RELEASE
COMPLETE

to Be
Traced
Message Name in
Protocols
Uu
RRC_PH_CH_RECFG_CMP
PHYSICAL
CHANNEL
RECONFIGURATION
COMPLETE
RRC_UE_CAP_ENQUIRY
UE CAPABILITY
ENQUIRY
RRC_UE_CAP_INFO
UE CAPABILITY
INFORMATION
UE CAPABILITY
INFORMATION
CONFIRM
RELOCATION
REQUEST
RELOCATION
REQUEST
ACKNOWLEDGE
RELOCATION
FAILURE
Iu
RANAP_FORWARD_SRNS_CONTEXT FORWARD SRNS

CONTEXT
RELOCATION
DETECT
RELOCATION
COMPLETE
Procedure
Step 2 Create a Uu tracing task by referring to Creating an RNC Tracing Task. Figure 12-14 shows an example of Uu signaling tracing on the
SRNC.
Figure 12-14 Example of Uu signaling tracing on the SRNC
Figure 12-15 shows an example of Uu signaling tracing on the DRNC.
Figure 12-15 Example of Uu signaling tracing on the DRNC
9/5/2016
HEEX Startpage
Page 134 of 156
SRNC.
----End
12.5.5 Elementary Procedures of Relocation with Hard Handover

This section describes the elementary procedures of relocation with hard handover in terms of trigger conditions and signaling
procedures in normal and abnormal conditions.
Trigger Conditions
z
Procedure

1.
2.
3.

Trigger Conditions
9/5/2016
HEEX Startpage
Page 135 of 156
z
Procedure

1.
2.
3.
Relocation Commit Procedure (Relocation with Hard Handover)

Trigger Conditions

Procedure
Figure 12-20 shows the relocation commit procedure for the relocation with hard handover.
Figure 12-20 Relocation commit procedure (relocation with hard handover)
9/5/2016
HEEX Startpage
Page 136 of 156
1.
When an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, the SRNC sends a FORWARD SRNS
CONTEXT message to the SGSN to ask the SGSN to transfer the GTP-U and PDCP sequence numbers to the DRNC. The
sequence numbers are required for data forwarding.
2.
After receiving the FORWARD SRNS CONTEXT message, the SGSN forwards the message to the DRNC.
3.
The UE is handed over from the SRNC to the DRNC through a physical channel reconfiguration procedure. After receiving a
RADIO LINK RESTORE INDICATION message from the NodeB, the DRNC sends a RELOCATION DETECT message to the CN.
4.

Trigger Conditions

Procedure

1.
channel.
2.
3.

Trigger Conditions
network.
Procedure
9/5/2016
HEEX Startpage
Page 137 of 156

1.
2.
3.
connection.
Trigger Conditions

z
message.
Procedure

1.
2.
12.6 Relocation with Cell/URA Update

The procedure of relocation with cell/URA update is performed to change control from the SRNC of a UE to the DRNC. The
relocation is triggered by a cell update or URA update when the UE performs cell reselection to a cell in another RNC.
12.6.1 Protocols Related to Relocation with Cell/URA Update

The procedure of relocation with cell/URA update complies with some 3GPP 25-series of specifications.
z
12.6.2 Trigger Conditions of Relocation with Cell/URA Update

When the UE performs cell reselection to a cell in another RNC, a CCH cannot be set up on the Iur interface or the attempt to set up
a CCH on the Iur interface fails.
9/5/2016
HEEX Startpage
Page 138 of 156
12.6.3 Signaling Procedure of a Successful Relocation with Cell/URA Update

This section describes the signaling procedure of a successful relocation with cell/URA update. For the messages related to
relocation failures, see the elementary procedures.
Figure 12-24 shows the signaling procedure of a successful relocation with cell/URA update.
Figure 12-24 Signaling procedure of a successful relocation with cell/URA update
The DRNC acquires the SRNC ID of the UE from the URNTI IE in the CELL UPDATE message and then sends an UPLINK
SIGNALLING TRANSFER INDICATION message to the SRNC to indicate that the UE requests a cell update.
z
To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initiate a URA update, the UE sends a URA
UPDATE message to the DRNC.
z
After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message to the UE. After a successful URA update,
the DRNC sends a URA UPDATE CONFIRM message to the UE.
After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message from the DRNC, the UE can send a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MOBILITY INFORMATION
CONFIRM message (for the URA update) to the DRNC. This response from the UE is optional.
12.6.4 Using the RNC LMT to Trace the Procedure of Relocation with Cell/URA Update
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with cell/URA update.
Prerequisites
z
Context
9/5/2016
HEEX Startpage
Page 139 of 156

to Be
Traced
Message Name
in Protocols
Iur
RNSAP_UL_SIG_TRANSF_IND
UPLINK
SIGNALLING
TRANSFER
INDICATION
RNSAP_RELOC_COMMIT
RELOCATION
COMMIT
RELOCATION
REQUIRED
RELOCATION
COMMAND
Iu
PREPARATION
FAILURE
IU RELEASE
COMMAND
IU RELEASE
COMPLETE

to Be
Traced
Message Name in
Protocols
Uu
RRC_CELL_UPDATE
CELL UPDATE
RRC_URA_UPDATE
URA UPDATE
RRC_CELL_UPDATE_CONFIRM
CELL UPDATE
CONFIRM
RRC_URA_UPDATE_CONFIRM
URA UPDATE
CONFIRM
RRC_PH_CH_RECFG_CMP
PHYSICAL
CHANNEL
RECONFIGURATION
COMPLETE
RRC_UTRAN_MOBIL_INFO_CONFIRM UTRAN MOBILITY

INFORMATION
CONFIRM
Iur
Iu
RRC_UE_CAP_ENQUIRY
UE CAPABILITY
ENQUIRY
RRC_UE_CAP_INFO
UE CAPABILITY
INFORMATION
UE CAPABILITY
INFORMATION
CONFIRM
RNSAP_UL_SIG_TRANSF_IND
UPLINK
SIGNALLING
TRANSFER
INDICATION
RNSAP_RELOC_COMMIT
RELOCATION
COMMIT
RELOCATION
REQUEST
RELOCATION
REQUEST
ACKNOWLEDGE
9/5/2016
HEEX Startpage
Page 140 of 156

to Be
Traced
Message Name in
Protocols
RELOCATION
FAILURE
RELOCATION
DETECT
RELOCATION
COMPLETE
Procedure
Step 2 Create a Uu tracing task by referring to Creating an RNC Tracing Task. Figure 12-25 shows an example of Uu signaling tracing for the
relocation with cell update.
Figure 12-25 Example of Uu signaling tracing for the relocation with cell update
Step 3 Create an Iur tracing task by referring to Creating an RNC Tracing Task. Figure 12-26 shows an example of Iur signaling tracing on the
SRNC.
Figure 12-26 Example of Iur signaling tracing on the SRNC
Figure 12-27 shows an example of Iur signaling tracing on the DRNC.
Figure 12-27 Example of Iur signaling tracing on the DRNC
SRNC.
----End
12.6.5 Elementary Procedures of Relocation with Cell/URA Update

This section describes the elementary procedures of relocation with cell/URA update in terms of trigger conditions and signaling
9/5/2016
HEEX Startpage
Page 141 of 156
Trigger Conditions
z
Procedure

1.
2.
3.

Trigger Conditions
z
Procedure

1.
2.
3.
9/5/2016
HEEX Startpage
Page 142 of 156
Cell Update Procedure

The cell update procedure is performed to update the UE-related information on the UTRAN side when the location of a UE
changes. In addition, the cell update procedure takes the role of monitoring the RRC connection, switching the status of the RRC
connection, reporting errors, and transferring information.
Trigger Conditions
The cell update procedure can be triggered in one of the following conditions:
z
Cell reselection
Re-entering the service area
Periodical cell update
Radio link failure
Paging response
Uplink data transmission
RLC unrecoverable error
Procedure
Figure 12-32 shows the cell update procedure.
Figure 12-32 Cell update procedure

1.
The UE sends a CELL UPDATE message to the RNC. The message contains the information such as the Serving RNC Radio
Network Temporary Identifier (S-RNTI) and the SRNC ID.
2.
The RNC sends a CELL UPDATE CONFIRM message to the UE. The message contains the information such as the U-RNTI
and the IEs about the transport channels, physical channels, and radio bearers.
3.
According to related IEs in the received message, the UE may respond with messages or not. If the UE responds, the
message can be one of the following messages:
UTRAN MOBILITY INFORMATION CONFIRM
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RELEASE COMPLETE
URA Update Procedure

The URA update procedure is performed to update the URA-related location information on the network side when the location of a
UE changes.
Trigger Conditions
The URA update procedure can be triggered in either of the following conditions:
9/5/2016
HEEX Startpage
URA reselection
Periodical URA update
Page 143 of 156
Procedure
Figure 12-33 shows the URA update procedure.
Figure 12-33 URA update procedure

1.
The UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA
update and the IEs such as the U-RNTI.
2.
The RNC sends a URA UPDATE CONFIRM message to the UE. The message contains the new C-RNTI and U-RNTI or the
information about the new encryption and integrity protection modes.
3.
The UE responds optionally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to
the RNC after taking the new parameters into effect.
Relocation Commit Procedure (Static Relocation or Relocation with Cell/URA Update)
Trigger Conditions

Procedure
Figure 12-34 shows the relocation commit procedure for the static relocation or relocation with cell/URA update.
Figure 12-34 Relocation commit procedure (static relocation or relocation with cell/URA update)

1.
The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supporting lossless SRNS relocation is
available on the Iu-PS interface, the RELOCATION COMMIT message carries the GTP-U and PDCP sequence numbers required
for data forwarding. Then, the SRNC initiates data forwarding.
2.
The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of the detection of the relocation
commitment.
3.

9/5/2016
HEEX Startpage
Page 144 of 156
Trigger Conditions
network.
Procedure

1.
2.
3.
connection.
Trigger Conditions

z
z The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST
message.
z
Procedure

1.
2.
9/5/2016
HEEX Startpage
12.7 D
Page 145 of 156
SCR Procedure
As the Iur connection is broken, the DRNC cannot instruct the SRNC to authenticate the UE. As a result, a direct signaling
connection reestablishment (DSCR) procedure is triggered and the DRNC sends an RRC CONNECTION RELEASE message to the
UE.
The DSCR procedure complies with some 3GPP TS25.
As the Iur connection is released, the RNC cannot contact the SRNC to authenticate the UE. As a result, a DSCR procedure is
triggered and the RNC sends an RRC CONNECTION RELEASE message to the UE.
This section describes the successful DSCR procedure.
The DSCR procedure complies with some 3GPP TS25.

z
3GPP TS23.060 "General Packet Radio Service (GPRS)"
As the Iur connection is released, the RNC cannot contact the SRNC to authenticate the UE. As a result, a DSCR procedure is
triggered and the RNC sends an RRC CONNECTION RELEASE message to the UE.
This section describes the successful DSCR procedure.

Figure 12-37 shows the signaling procedure of successful DSCR.
Figure 12-37 Signaling procedure of successful DSCR
The UE sets up an RRC connection to RNC 1 (SRNC). During relocation, RNC 1 is the source RNC and RNC 2 is the target RNC.
1.
RNC 1 initiates a DSCR procedure.
2.
RNC 1 sends a DOWNLINK SIGNALLING TRANSFER REQUEST message to RNC 2, requesting RNC 2 to send an RRC
CONNECTION RELEASE message to the UE.
3.
RNC 2 sends the UE an RRC CONNECTION RELEASE message with DSCR cause value.
4.
After receiving the RRC CONNECTION RELEASE message, the UE releases the current RAB and RRC connection and
enters the idle mode.
5.
The UE performs a cell reselection to select a proper cell.
6.
After selecting a proper cell, the UE immediately requests an RRC connection and RAB reestablishment.
7.
The UE sends RNC 2 a ROUTE AREA UPDATE message to initiate the URA update procedure.
8.
The SGSN requests RNC 1 to forward data. Then, RNC 1 forwards packets to the SGSN but does not forward the packets that
RNC 1 cannot recognize.
9.
The UE sends the SGSN a DIRECT TRANSFER message to request service setup.
9/5/2016
HEEX Startpage
10.
Page 146 of 156
The SGSN initiates the RAB setup procedure.
13
Location Service Procedure
The location service procedure is performed to identify the geographic location of a UE. This chapter describes the location services
in terms of working modes, positioning methods, protocols, trigger conditions, signaling procedure of successful positioning, and
signaling tracing on the RNC LMT. This topic also describes the elementary procedures in terms of functions, trigger conditions, and
signaling in normal and abnormal conditions.
13.1 Working Mode
The SRNC can work in either RNC centric mode or SAS centric mode.
The QoS (including the positioning accuracy and positioning delay) obtained using the two working modes is almost the same. The
reason is that the QoS of the location service depends on the positioning accuracy and positioning delay of an individual LCS
positioning method.
In RNC centric mode, the RNC selects the positioning method and procedure. In SAS centric mode, independent SAS devices are
required and SAS devices select the positioning method and procedure. In this case, the RNC only assists the SAS in obtaining
original measurement values for a specific LCS positioning method.
The RNC selects the positioning method as follows:
z
The LCS supports the following positioning methods in RNC centric mode.
Cell ID+RTT (including the cell-center method)
OTDOA
A-GPS
The LCS supports the following positioning methods in SAS centric mode.
Cell ID+RTT
A-GPS
13.2 Positioning Methods
Three standard positioning methods are available in a WCDMA system. They are CELL ID+RTT, OTDOA, and A-GPS.
Typically, in terms of the horizontal accuracy, Network Assisted GPS (A-GPS) ranks first, Observed Time Difference Of Arrival
(OTDOA) second and CELL ID+RTT third. RTT is short for Round Trip Time. Exceptions, however, may exist. For example, in
places where obstacles exist in large number and not enough satellite signals are found, the A-GPS positioning method may fail or
perform with poor accuracy. In that case, the CELL ID+RTT positioning method may provide higher accuracy.
13.3 Positioning Based on Cell ID+RTT

When the Cell ID+RTT positioning method is adopted, the location of a UE is identified based on the coverage area of the reference
cell and the RTT measurements performed on all the cells in the active set of the UE.
13.3.1 Protocols Related to Positioning Based on CELL ID+RTT

The procedure of positioning based on CELL ID+RTT complies with some 3GPP TS22, TS23, and TS25 protocols.
z
3GPP TS22.071 "Location Services (LCS)"
3GPP TS23.271 "Functional stage 2 description of LCS"
3GPP TS25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN)"
13.3.2 Positioning Based on Cell ID+RTT in RNC Centric Mode

The CN initiates a positioning request. If the RNC chooses the RNC centric mode, the positioning method is UE-assisted cell
ID+RTT.
After receiving the positioning request from the CN, the RNC chooses the UE-assisted cell ID+RTT positioning method based on the
factors such as the QoS of positioning, the positioning method configured on the RNC side, and the positioning capability of the UE.
9/5/2016
HEEX Startpage
Page 147 of 156
13.3.2.1 Signaling Procedure of Successful Positioning Based on Cell ID+RTT

This section describes the signaling procedure of successful positioning based on CELL ID+RTT. For the messages related to
positioning failures, see the elementary procedures.
Figure 13-1 shows the signaling procedure of successful positioning based on CELL ID+RTT.
Figure 13-1 Signaling procedure of successful positioning based on CELL ID+RTT
1.
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UEassisted cell ID+RTT positioning method.
2.
The SRNC sends the UE a MEASUREMENT CONTROL message, requesting the UE to perform a UE Rx-Tx type 2
measurement. If the UE does not support UE Rx-Tx type 2 measurement, the RNC requests the UE to perform a UE Rx-Tx type 1
measurement.
3.
The UE sends the RNC the UE Rx-Tx type 2 measurement results through a MEASUREMENT REPORT message (if the UE
does not support UE Rx-Tx type 2 measurement, it reports UE Rx-Tx type 1 measurement results to the RNC.
4.
The RNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message over the Iub or Iur interface to request
an RTT measurement on cells in the active set.
5.
The NodeB sends the RTT measurement results to the RNC through a DEDICATED MEASUREMENT INITIALIZATION
RESPONSE message over the Iub or Iur interface.
6.
The SRNC performs location calculation based on the RTT measurement results and the known location of each cell and then
reports the positioning results to the CN through a LOCATION REPORT message.
13.3.2.2 Using the RNC LMT to Trace the Procedure of Positioning Based on CELL ID+RTT or OTDOA-IPDL
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELL ID+RTT
or OTDOA-IPDL.
Prerequisites
z
Context

to Be
Traced
Message Name
in Protocols
Uu
RRC_MEAS_CTRL
MEASUREMENT
CONTROL
RRC_MEAS_RPRT
MEASUREMENT
REPORT
RRC_MEAS_CTRL_FAIL
MEASUREMENT
CONTROL
FAILURE
9/5/2016
HEEX Startpage
Page 148 of 156
Iu
NBAP_DECIC_MEAS_INIT_REQ
DEDICATED
MEASUREMENT
INITIALIZATION
REQUEST
NBAP_DECIC_MEAS_INIT_RSP
DEDICATED
MEASUREMENT
INITIALIZATION
REPONSE
RANAP_LOCATION_REPORTING_CONTROL LOCATION
REPORTING
CONTROL
RANAP_LOCATION_REPORT
LOCATION
REPORT
Procedure
Create a Call Data Tracing (CDT) task for a UE in positioning by referring to Creating an RNC Tracing Task. Figure 12-2 shows an
example of CDT tracing on the positioning based on CELL ID+RTT.
Figure 13-2 Example of CDT tracing result
13.3.2.3 Elementary Procedures of Positioning Based on CELL ID+RTT

This section describes the elementary procedures of positioning based on CELL ID+RTT in terms of trigger conditions and signaling
UE Measurement Procedure
The UE measurement procedure is performed for the RNC to request a report of attributes from the UE.
Trigger Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC initiates the UE measurement procedure for
the location service.
Procedure
Figure 13-3 shows the UE measurement procedure.
Figure 13-3 UE measurement procedure

1.
The SRNC sends a MEASUREMENT CONTROL message to the UE to request the UE to perform measurements based on
the positioning method:
CELL ID+RTT positioning method: UE Rx-Tx type 2 measurement (or UE Rx-Tx type 1 measurement, if the UE does not support
the UE Rx-Tx type 2 measurement)
OTDOA-IPDL positioning method: OTDOA type 2 measurements between the reference cell and the neighboring cells, and UE
Rx-Tx type 2 measurement in the reference cell (if the UE is in the CELL_DCH state)
2.
A-GPS positioning method: GPS pseudo-range measurement and Doppler measurement

9/5/2016
HEEX Startpage
Page 149 of 156
If the measurements are successful, the UE sends a MEASUREMENT REPORT message to report the measurement results.
If the UE does not support the measurement requested by the SRNC or if the measurement results exceed the maximum
number of criteria supported by the UE, the UE sends a MEASUREMENT CONTROL FAILURE message.
RTT Measurement Procedure

Dedicated for positioning, the RTT measurement procedure is performed by the NodeB to measure the Round Trip Time (RTT) for
one or more cells.
Trigger Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC starts to perform an RTT measurement for
the cells in the active set or for the reference cell.
Procedure
Figure 13-4 shows the RTT measurement procedure.
Figure 13-4 RTT measurement procedure

1.
The CRNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message to the NodeB to request the NodeB
to perform an RTT measurement. The measurement object varies with the positioning method as follows:
CELL ID+RTT positioning method: cells in the active set
OTDOA-IPDL positioning method: reference cell
2.
If the measurement is successful, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION REPONSE message to
report the measurement results.
If the measurement requested by the CRNC fails to be initialized, the NodeB sends a DEDICATED MEASUREMENT
INITIALIZATION FAILURE message to inform the CRNC of the failure.
13.3.3 Cell ID+RTT Positioning Method in SAS Centric Mode
The CN initiates a positioning request, the positioning working mode selected by the RNC is SAS centric, and the positioning
method selected by the SAS is UE assisted cell ID+RTT.
13.3.3.1 Signaling Procedure for Cell ID+RTT Positioning
The following figure shows the general signaling procedure for the cell ID+RTT positioning method in SAS centric mode.
Figure 13-5 General signaling procedure for the cell ID+RTT positioning method
9/5/2016
HEEX Startpage
Page 150 of 156
The general signaling procedure for the cell ID+RTT positioning method is described as follows:
1.
The CN sends the RNC an authenticated positioning request through the LOCATION REPORTING CONTROL message.
2.
The RNC includes the cell ID and UE capability information in the LOCATION REPORTING CONTROL message and
encapsulates this message as a PCAP POSITION INITIATION REQUEST message sent to the SAS.
3.
The SAS sends the RNC a PCAP POSITION ACTIVATION REQUEST message to specify the positioning method. This
message contains the positioning method and positioning assistance data. Assume that the positioning method selected by the SAS
is UE assisted cell ID+RTT.
If the UE is not in the CELL_DCH state, the RNC must transit the UE to the CELL_DCH state.
4.
The RNC sends the UE a MEASUREMENT CONTROL message, requesting the UE to perform a UE Rx-Tx type 2
measurement (the value of the Measurement type IE in this message is "UE positioning measurement".
If the UE does not support UE Rx-Tx type 2 measurement, the RNC requests the UE to perform a UE Rx-Tx
type 1 measurement (the value of the Measurement type IE in this message is "UE internal measurement".
For details about the MEASUREMENT CONTROL message, see 10.2.17 "MEASUREMENT CONTROL" in
3GPP TS 25.331 V7.10.0.
5.
In addition to measurement-based positioning, the SAS can perform positioning based on cell signal quality. If the SAS
requests the RNC to measure the CPICH Ec/N0, CPICH RSCP, and path loss of cells in the active and monitored sets, the SAS
sends a PCAP POSITION ACTIVATION REQUEST message to the RNC. Upon receiving this message, the RNC sends the UE a
MEASUREMENT CONTROL message with the Measurement type IE being "Intra-frequency measurement", requesting the UE to
report the CPICH Ec/N0, CPICH RSCP, and path loss of cells in the active set and monitored set.
6.
The RNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message over the Iub or Iur interface to request
an RTT measurement on cells in the active set.
7.
The NodeB sends the RTT measurement results to the RNC through a DEDICATED MEASUREMENT INITIALIZATION
RESPONSE message over the Iub or Iur interface.
8.
The UE reports the UE Rx-Tx type 2 measurement results to the RNC through a MEASUREMENT REPORT message.
If the UE does not support UE Rx-Tx type 2 measurement, the UE reports UE Rx-Tx type 1 measurement
results.
9.
If the RNC sends the UE an intra-frequency measurement control message, the UE reports the CPICH Ec/N0, CPICH RSCP,
and path loss of cells in the active and monitored sets to the RNC through aMEASUREMENT REPORT message.
10. The RNC sends the positioning results to the SAS through the PCAP POSITION ACTIVATION RESPONSE message. If the
RNC sends the UE an intra-frequency measurement control message, the RNC will also report the measurement results obtained
from the UE to the SAS.
11. The SAS performs location calculation and sends the ultimate location of the UE to the RNC through a PCAP POSITION
INITIATION RESPONSE message.
12.
The RNC reports the ultimate location of the UE to the CN through a LOCATION REPORT message.
13.4 Positioning Based on OTDOA-IPDL
When the OTDOA-IPDL positioning method is adopted, the location of a UE is identified based on the arrival time differences of
CPICH signals from three inter-NodeB cells to the UE, which measures the differences.
9/5/2016
HEEX Startpage
Page 151 of 156
13.4.1 Protocols Related to Positioning Based on OTDOA-IPDL

The procedure of positioning based on OTDOA-IPDL complies with some 3GPP TS22, TS23, and TS25 protocols.
z
13.4.2 Trigger Conditions of Positioning Based on OTDOA-IPDL

The CN initiates a positioning request and the RNC chooses the UE-assisted OTDOA-IPDL positioning method.
After receiving the positioning request from the CN, the RNC chooses the UE-assisted OTDOA-IPDL positioning method based on
the factors such as the QoS of positioning, the positioning method configured on the RNC side, and the positioning capability of the
UE.
13.4.3 Signaling Procedure of Successful Positioning Based on OTDOA-IPDL

This section describes the signaling procedure of successful positioning based on OTDOA-IPDL. For the messages related to
positioning failures, see the elementary procedures.
Figure 13-5 shows the signaling procedure of successful positioning based on OTDOA-IPDL.
Figure 13-6 Signaling procedure of successful positioning based on OTDOA-IPDL
1.
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UEassisted OTDOA-IPDL positioning method.
2.
The RNC sends the UE a MEASUREMENT CONTROL message, requesting the UE to perform SFN-SFN type 2
measurement or SFN-CFN measurement in the reference cell and multiple neighboring cells of the reference cell.
If the UE is in the CELL_DCH state, the UE sends the following measurement results to the RNC through the MEASUREMENT
REPORT message:
Measurement results of SFN-SFN type 2 measurement or SFN-CFN measurement in the reference cell or multiple neighboring
cells
(Optional) UE Rx-Tx timing difference of the reference cell
If the UE is in the CELL_DCH state, the RNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message over
the Iub or Iur interface, requesting the NodeB to perform RTT measurement on the reference cell.
When the UE is in the CELL_DCH state, the NodeB reports the RTT measurement results of the reference cell to the RNC by
sending a DEDICATED MEASUREMENT INITIALIZATION RESPONSE message over the Iub or Iur interface.
3.
The SRNC performs location calculation based on the known location of each cell, the results of the OTDOA measurement,
and the measurement results of the Relative Time Difference (RTD) between the reference cell and the neighboring cells. Then, the
SRNC reports the positioning results to the CN through a LOCATION REPORT message.
13.4.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELL ID+RTT or OTDOA-IPDL
9/5/2016
HEEX Startpage
Page 152 of 156
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELL ID+RTT
or OTDOA-IPDL.
Prerequisites
z
Context

to Be
Traced
Message Name
in Protocols
Uu
RRC_MEAS_CTRL
MEASUREMENT
CONTROL
RRC_MEAS_RPRT
MEASUREMENT
REPORT
RRC_MEAS_CTRL_FAIL
MEASUREMENT
CONTROL
FAILURE
NBAP_DECIC_MEAS_INIT_REQ
DEDICATED
MEASUREMENT
INITIALIZATION
REQUEST
NBAP_DECIC_MEAS_INIT_RSP
DEDICATED
MEASUREMENT
INITIALIZATION
REPONSE
Iub
Iu
REPORTING
CONTROL
LOCATION
REPORT
Procedure
example of CDT tracing on the positioning based on CELL ID+RTT.
13.4.5 Elementary Procedures of Positioning Based on OTDOA-IPDL

This section describes the elementary procedures of positioning based on OTDOA-IPDL in terms of trigger conditions and signaling
Trigger Conditions
Procedure
9/5/2016
HEEX Startpage
Page 153 of 156

1.
2.

RTT Measurement Procedure

Dedicated for positioning, the RTT measurement procedure is performed by the NodeB to measure the Round Trip Time (RTT) for
one or more cells.
Trigger Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC starts to perform an RTT measurement for
the cells in the active set or for the reference cell.
Procedure
Figure 13-8 shows the RTT measurement procedure.
Figure 13-9 RTT measurement procedure

1.
The CRNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message to the NodeB to request the NodeB
to perform an RTT measurement. The measurement object varies with the positioning method as follows:
CELL ID+RTT positioning method: cells in the active set
OTDOA-IPDL positioning method: reference cell
2.
If the measurement is successful, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION REPONSE message to
report the measurement results.
If the measurement requested by the CRNC fails to be initialized, the NodeB sends a DEDICATED MEASUREMENT
INITIALIZATION FAILURE message to inform the CRNC of the failure.
13.5 Positioning Based on A-GPS
9/5/2016
HEEX Startpage
Page 154 of 156
When the A-GPS positioning method is adopted, the location of a UE is identified based on the GPS positioning-assistance data and
GPS pseudo-range measurement results collected by the RNC.
13.5.1 Protocols Related to Positioning Based on A-GPS

The procedure of positioning based on A-GPS complies with some 3GPP TS22, TS23, and TS25 protocols.
z
13.5.2 Positioning Based on A-GPS in RNC Centric Mode

The CN initiates a positioning request and the positioning method is UE-assisted A-GPS if the positioning working mode selected by
the RNC is RNC centric.
After receiving the positioning request from the CN, the RNC chooses the UE-assisted A-GPS positioning method based on the
factors such as the QoS of positioning, the positioning method configured on the RNC side, and the positioning capability of the UE.
13.5.2.1 Signaling Procedure of Successful Positioning Based on A-GPS
This section describes the signaling procedure of successful positioning based on A-GPS. For the messages related to positioning
Figure 13-9 shows the signaling procedure of successful positioning based on A-GPS.
Figure 13-10 Signaling procedure of successful positioning based on A-GPS
1.
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UEassisted A-GPS positioning method.
2.
The RNC calculates the A-GPS assistance data and sends the UE a MEASUREMENT CONTROL message, requesting the
UE to perform a pseudo GPS measurement.
3.
The UE reports the pseudo GPS measurement results to the RNC through a MEASUREMENT REPORT message based on
the positioning accuracy. The RNC calculates the 3-D location of each satellite that is involved in the positioning according to the
GPS satellite ephemeris.
4.
The RNC reports the positioning results to the CN through a LOCATION REPORT message.
13.5.2.2 Using the RNC LMT to Trace the Procedure of Positioning Based on A-GPS
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on A-GPS.
Prerequisites
z
Context
9/5/2016
HEEX Startpage
Page 155 of 156

to Be
Traced
Message Name
in Protocols
Uu
RRC_MEAS_CTRL
MEASUREMENT
CONTROL
RRC_MEAS_RPRT
MEASUREMENT
REPORT
RRC_MEAS_CTRL_FAIL
MEASUREMENT
CONTROL
FAILURE
Iu
REPORTING
CONTROL
LOCATION
REPORT
Procedure
example of CDT tracing result.
13.5.2.3 Elementary Procedures of Positioning Based on A-GPS

This section describes the elementary procedures of positioning based on A-GPS in terms of trigger conditions and signaling
Trigger Conditions
Procedure

1.
9/5/2016
HEEX Startpage
2.
Page 156 of 156

13.5.3 A-GPS Positioning Method in SAS Centric Mode
The CN initiates a positioning request and the positioning method selected by the SAS is UE-assisted A-GPS if the positioning
working mode selected by the RNC is SAS Centric.
13.5.3.1 Signaling Procedure for A-GPS Positioning
The following figure shows the general signaling procedure for the A-GPS positioning method in SAS centric mode.
Figure 13-13 General signaling procedure for A-GPS positioning
The general signaling procedure for the A-GPS positioning method in SAS centric mode is described as follows:
1.
The CN sends the RNC an authenticated positioning request through the LOCATION REPORTING CONTROL message.
2.
The RNC includes the cell ID and UE capability information in the LOCATION REPORTING CONTROL message and
encapsulates this message as a PCAP POSITION INITIATION REQUEST message sent to the SAS.
3.
The SAS sends the RNC a PCAP POSITION ACTIVATION REQUEST message to specify the positioning method. This
message contains the positioning method and assistance data. This signaling procedure assumes that the positioning method
selected by the SAS is UE assisted A-GPS.
In this positioning method, the positioning mode supported by the UE is determined by the SAS and the UE capability.
4.
The RNC sends the UE a MEASUREMENT CONTROL message, requesting the UE to perform a pseudo GPS measurement.
5.
The EU reports the pseudo GPS measurement results to the RNC through a MEASUREMENT REPORT message.
6.
The RNC sends the pseudo GPS measurement results to the SAS through a PCAP POSITION ACTIVATION RESPONSE
message.
7.
The SAS sends the calculated UE location information to the RNC through a PCAP POSITION INITIATION RESPONSE
message.
8.
The RNC reports the positioning results to the CN through a LOCATION REPORT message.
9/5/2016

RAN17 Signaling

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

RAN17 Signaling

Uploaded by

Copyright:

Available Formats

HEEX Startpage

(For Engineer) RAN17.1 Solution Technical Guideline

For any question, please contact us.

10-RAN17.1 Signaling Analysis Guide

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Huawei Technologies Co., Ltd.

Huawei Industrial Base

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

About This Document

V900R011 and later versions

V100R011 and later versions

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

8.5 Elementary Procedures of PS Service Setup

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

10.4 Types of Inter-Frequency Handover

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

12.5.1 Protocols Related to Relocation with Hard Handover

This chapter describes the changes in RAN Signaling Analysis Guide.

Cell Setup Procedure

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

2.1 Protocols Related to Cell Setup

ITU-T Q.2630 "AAL type 2 Signalling Protocol"

2.2 Trigger Conditions of Cell Setup

Table 2-1 Trigger conditions of cell setup

Run the ACT UCELL

After receiving the resource

2.3 Signaling Procedure of Successful Cell Setup

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

The RNC LMT works properly.

Table 2-2 Messages to be traced

Interface Message Name on the LMT

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

Interface Message Name on the LMT

No message name needs to be specified.

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

2.5 Elementary Procedures of Cell Setup

2.5.1 Resource Status Indication Procedure

A local cell is added to the NodeB.

A local cell is deleted from the NodeB.

The capabilities of a local cell change at the NodeB.

A local cell group changes its resource capability at the NodeB.

2.5.2 Resource Audit Procedure

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

The procedure shown in Figure 2-5 is described as follows:

If the audit fails, the NodeB sends an AUDIT FAILURE message.

2.5.3 Cell Setup Procedure

Downlink power range

Minimum spreading factor

HSDPA cell capability of the NodeB

Common transport channel and physical channel information

CCP and NCP information

The procedure shown in Figure 2-6 is described as follows:

2.5.4 Common Transport Channel Setup Procedure

http://localhost:7890/printtopics.html?time=Mon Sep 5 08:58:42 UTC+0700 2016

The procedure shown in Figure 2-7 is described as follows:

One S-CCPCH and the related FACHs, PCH and PICH

One PRACH and the related RACH and AICH

2.5.5 Iub User Plane Setup Procedure

The common transport channels are set up.

The dedicated transport channels are set up.

The procedure shown in Figure 2-8 is described as follows: