Professional Documents
Culture Documents
RAN Signaling Analysis Guide (RAN10.0 - 02) PDF
RAN Signaling Analysis Guide (RAN10.0 - 02) PDF
10.0
Issue 02
Date 2008-07-30
Part Number
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
7.3.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between NodeBs in an RNC
.........................................................................................................................................................................7-9
7.3.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between NodeBs in an
RNC.................................................................................................................................................................7-9
7.3.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC..................7-11
7.4 Intra-Frequency Soft Handover Between RNCs...........................................................................................7-16
7.4.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs.................................................7-17
7.4.2 Triggering Conditions of Intra-Frequency Soft Handover Between RNCs.........................................7-17
7.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs.......................7-17
7.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs.....7-18
7.4.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs.......................................7-20
7.5 Intra-Frequency Hard Handover Between NodeBs in an RNC....................................................................7-28
7.5.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC..........................7-29
7.5.2 Triggering Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC..................7-29
7.5.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC
.......................................................................................................................................................................7-29
7.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in an
RNC...............................................................................................................................................................7-30
7.5.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC.................7-32
7.6 Intra-Frequency Hard Handover Between RNCs..........................................................................................7-37
7.6.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs...............................................7-38
7.6.2 Triggering Conditions of Intra-Frequency Hard Handover Between RNCs........................................7-38
7.6.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs......................7-38
7.6.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between RNCs....7-39
7.6.5 Elementary Procedures of Intra-Frequency Hard Handover Between RNCs......................................7-41
Figures
Figure 8-6 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)....................8-8
Figure 8-7 Iub user plane setup procedure...........................................................................................................8-9
Figure 8-8 Radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover).........8-10
Figure 8-9 Physical channel reconfiguration procedure.....................................................................................8-10
Figure 8-10 Radio link deletion procedure.........................................................................................................8-11
Figure 8-11 Iub user plane release procedure.....................................................................................................8-12
Figure 8-12 Signaling procedure of a successful inter-frequency handover between RNCs.............................8-14
Figure 8-13 Example of Uu signaling tracing result..........................................................................................8-15
Figure 8-14 Example of Iub signaling tracing result (source RNC)..................................................................8-16
Figure 8-15 Example of Iub signaling tracing result (target RNC)....................................................................8-16
Figure 8-16 Example of Iur signaling tracing result..........................................................................................8-16
Figure 8-17 Example of Q.AAL2 signaling tracing result.................................................................................8-16
Figure 8-18 Radio link setup procedure (inter-RNC handover).........................................................................8-17
Figure 8-19 Iub user plane setup procedure.......................................................................................................8-18
Figure 8-20 Radio link restoration procedure (inter-RNC handover)................................................................8-19
Figure 8-21 Iur user plane setup procedure........................................................................................................8-20
Figure 8-22 Physical channel reconfiguration procedure...................................................................................8-20
Figure 8-23 Radio link deletion procedure.........................................................................................................8-21
Figure 8-24 Iub user plane release procedure.....................................................................................................8-22
Figure 8-25 Iur user plane release procedure.....................................................................................................8-23
Figure 9-1 Signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM.....................9-3
Figure 9-2 Example of Uu signaling tracing result..............................................................................................9-5
Figure 9-3 Example of Iub signaling tracing result..............................................................................................9-5
Figure 9-4 Example of Iu signaling tracing result................................................................................................9-5
Figure 9-5 Relocation preparation procedure.......................................................................................................9-6
Figure 9-6 Iu release procedure............................................................................................................................9-7
Figure 9-7 Radio link deletion procedure.............................................................................................................9-8
Figure 9-8 Signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA...................9-10
Figure 9-9 Example of Uu signaling tracing result............................................................................................9-12
Figure 9-10 Example of Iub signaling tracing result..........................................................................................9-12
Figure 9-11 Example of Iu signaling tracing result............................................................................................9-13
Figure 9-12 Relocation resource allocation procedure.......................................................................................9-14
Figure 9-13 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)................9-15
Figure 9-14 Radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover).......9-16
Figure 9-15 UE capability enquiry procedure....................................................................................................9-16
Figure 9-16 Security mode control procedure....................................................................................................9-17
Figure 9-17 UTRAN mobility information procedure.......................................................................................9-18
Figure 9-18 Signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM.................9-20
Figure 9-19 Example of Uu signaling tracing result..........................................................................................9-22
Figure 9-20 Example of Iub signaling tracing result..........................................................................................9-22
Figure 9-21 Example of Iu signaling tracing result............................................................................................9-22
Figure 9-22 Cell change order from UTRAN procedure...................................................................................9-23
Tables
Purpose
This document describes the triggering 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.
RNC V100R010
V200R010
NodeB V100R010
V200R010
Intended Audience
This document is intended for:
l Field engineers
l System engineers
Change History
Refer to Changes in RAN Signaling Analysis Guide.
Organization
The SRNS relocation procedure is performed to change control from the SRNC of a UE to
another RNC. This topic describes the SRNS relocation in terms of types, protocols, triggering
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, triggering
conditions, and signaling in normal and abnormal conditions.
The location service procedure is performed to identify the geographic location of a UE. This
topic describes the location services in terms of positioning methods, protocols, triggering
conditions, signaling procedure of successful positioning, and signaling tracing on the RNC
LMT. This topic also describes the elementary procedures in terms of functions, triggering
conditions, and signaling in normal and abnormal conditions.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol Description
TIP Indicates a tip that may help you solve a problem or save your
time.
2. General Conventions
Convention Description
Convention Description
3. Command Conventions
Convention Description
4. GUI Conventions
Convention Description
> Multi-level menus are in boldface and separated by the ">" signs.
For example,choose File > Create > Folder .
5. Keyboard Operation
Convention Description
Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two
keys should be pressed in turn.
6. Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the
pointer.
Double-click Press the primary mouse button twice continuously and quickly
without moving the pointer.
Drag Press and hold the primary mouse button and move the pointer
to a certain position.
The cell setup procedure is performed to set up a WCDMA cell. This topic describes cell setup
in terms of protocols, triggering 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, triggering conditions, and signaling in normal and abnormal conditions.
Note the following information about the procedure shown in Figure 1-1:
l 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.
l 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.
l If IP transport is applied to the Iub interface, the Iub user plane setup procedure is excluded
from cell setup.
1.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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 1-2 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
NBAP_COMM_MEAS_RPR
COMMON MEASUREMENT REPORT
T
Procedure
Step 1 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 1-2 shows an 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 1-3 shows an example of Q.AAL2 protocol tracing result.
----End
Triggering Conditions
The NodeB triggers the procedure in one of the following conditions:
l A local cell is added to the NodeB.
l A local cell is deleted from the NodeB.
l The capabilities of a local cell change at the NodeB.
l A cell changes its capability or resource operational state or both capability and resource
operational state at the NodeB.
l Common physical channels or common transport channels or both common physical
channels and common transport channels change their capabilities at the NodeB.
l A Communication Control Port (CCP) changes its resource operational state at the NodeB.
l A local cell group changes its resource capability at the NodeB.
Procedure
Figure 1-4 shows the resource status indication procedure.
The NodeB sends a RESOURCE STATUS INDICATION message to the CRNC through the
NodeB Control Port (NCP). This message contains the triggering condition and the associated
logical resource information.
Triggering Conditions
The CRNC receives a RESOURCE STATUS INDICATION message from the NodeB.
Procedure
Figure 1-5 shows the resource audit procedure.
NOTE
A complete audit of a NodeB can be performed by one or more audit procedures. Each procedure carries
an audit sequence number.
Triggering 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:
l Downlink power range
l Minimum spreading factor
l HSDPA cell capability of the NodeB
l High Speed Downlink Shared Channel (HS-DSCH) resource information, which is used
to set up an HSDPA cell
l Common transport channel and physical channel information
l CCP and NCP information
Procedure
Figure 1-6 shows the cell setup procedure.
Triggering Conditions
The NodeB sends a CELL SETUP RESPONSE message to the CRNC.
Procedure
Figure 1-7 shows the common transport channel setup procedure.
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 1-8 shows the Iub user plane setup procedure.
Triggering Conditions
The system information update procedure can be triggered in one of the following conditions:
l Physical shared channels are reconfigured.
l Cells are reconfigured.
l All common transport channels are set up.
Procedure
Figure 1-9 shows the system information update procedure.
Triggering Conditions
The system information is updated and the cell to be set up is an HSDPA cell.
Procedure
Figure 1-10 shows the physical shared channel reconfiguration procedure.
Triggering Conditions
The cell is set up and activated.
Procedure
Figure 1-11 shows the common measurement initiation procedure.
The cell reconfiguration procedure is performed to reconfigure a cell in the NodeB. This topic
describes the cell reconfiguration procedure in terms of protocols, triggering conditions,
signaling procedure, and signaling tracing on the RNC LMT.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 2-1 lists the messages to be traced.
CELL RECONFIGURATION
NBAP_CELL_RECFG_REQ
REQUEST
Procedure
Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 2-2 shows an example of Iub signaling tracing result.
----End
The cell deletion procedure is performed to delete a cell from the NodeB. This topic describes
the cell deletion procedure in terms of protocols, triggering conditions, signaling procedure, and
signaling tracing on the RNC LMT.
l 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".
l Initiates release of the user plane transport bearers for the removed common and
dedicated channels.
l 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".
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 3-1 lists the messages to be traced.
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.
----End
Location area update is initiated by the UE to inform the CS service domain of the core network
that the UE has entered a new location area. Routing area update is initiated by the UE to inform
the PS service domain of the core network that the UE has entered a new routing area. This
chapter describes the location update in terms of protocols, triggering conditions, signaling
procedure of successful location update, signaling tracing on the RNC LMT, and elementary
procedures. This chapter also describes the elementary procedures in terms of functions,
triggering conditions, procedure, and signaling in abnormal conditions.
Note the following information about the procedure shown in Figure 4-1:
l The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC
connection set up on the DCH as an example.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 4-1 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_INIT_DIRECT_TRANS
Uu INITIAL DIRECT TRANSFER
F
RANAP_INITIAL_UE_MES
INITIAL UE MESSAGE
SAGE
RANAP_COMMON_ID COMMON ID
RANAP_DIRECT_TRANSFE
DIRECT TRANSFER
Iu R
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 4-2 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 4-3 shows an example of Iub signaling tracing result.
----End
Triggering 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 accepting the request, the RRM
module 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.
Figure 4-5 shows the procedure for setting up an RRC connection on a DCH.
Figure 4-6 shows the procedure for setting up an RRC connection on a CCH.
Triggering Conditions
An RRC connection is set up between the UE and the Serving RNC (SRNC).
Procedure
Figure 4-8 shows the location update procedure.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
l The transaction between the UE and the CN is complete.
l The UTRAN requests the CN to release the resources on the Iu interface by, for example,
sending an IU RELEASE REQUEST message.
l The Serving Radio Network Subsystem (SRNS) is relocated.
l The SRNS relocation is canceled after a relocation resource allocation procedure is
complete.
Procedure
Figure 4-9 shows the 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.
NOTE
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.
Triggering Conditions
After an RAB is released, the SRNC judges whether the RRC connection carries any other RAB
of the UE. If judging that 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.
NOTE
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.
Figure 4-10 shows the procedure for releasing an RRC connection from a DCH.
The SRNC may send the RRC CONNECTION RELEASE message several times to increase the
probability of proper reception of the message by the UE. The RRC SNs of these messages are the
same. The number of retransmissions and the transmission intervals are determined by the SRNC. If
the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the UE
after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the
UE has released the RRC connection.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
3. The SRNC sends 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. (Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP
protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC
connection release procedure ends.
II. Releasing an RRC Connection from a CCH
Figure 4-11 shows the procedure for releasing an RRC connection from a CCH.
The outgoing call procedure is performed for a UE to call another terminal, such as a Public
Switched Telephony Network (PSTN) terminal. This topic describes outgoing call setup and
release in terms of protocols, triggering 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, triggering conditions, and signaling in normal and abnormal conditions.
Note the following information about the procedure shown in Figure 5-1:
l The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC
connection set up on the DCH as an example.
l 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.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 5-1 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_INIT_DIRECT_TRANS
INITIAL DIRECT TRANSFER
F
Uu RRC_DL_DIRECT_TRANSF DOWNLINK DIRECT TRANSFER
RRC_SECURITY_MODE_C
SECURITY MODE COMMAND
MD
RRC_SECURITY_MODE_C
SECURITY MODE COMPLETE
MP
RRC_SECURITY_MODE_F
SECURITY MODE FAILURE
AIL
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_INITIAL_UE_MES
INITIAL UE MESSAGE
SAGE
RANAP_COMMON_ID COMMON ID
RANAP_DIRECT_TRANSFE
DIRECT TRANSFER
R
Iu RANAP_SECURITY_MODE
SECURITY MODE COMMAND
_COMMAND
RANAP_SECURITY_MODE
SECURITY MODE COMPLETE
_COMPLETE
RANAP_SECURITY_MODE
SECURITY MODE REJECT
_REJ
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT REQUEST
T_REQ
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT RESPONSE
T_RESP
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 5-2 shows an example of Uu signaling tracing result.
----End
Triggering 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 accepting the request, the RRM
module 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.
Figure 5-5 shows the procedure for setting up an RRC connection on a DCH.
Figure 5-6 shows the procedure for setting up an RRC connection on a CCH.
Triggering Conditions
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 5-8 shows the signaling connection setup procedure.
1. The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC
connection. The message contains the initial NAS information to be sent to the CN by the
UE.
2. The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends
an INITIAL UE MESSAGE to the CN 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.
l If accepting the request, the CN 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.
l If rejecting the request, the CN 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.
Triggering Conditions
The UE and the CN exchange signaling. The network initiates the authentication and security
mode control procedure.
Procedure
Figure 5-9 shows the authentication and security mode control procedure.
1. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates
AUTHENTICATION REQUEST.
2. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
3. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
RESPONSE. If the UMTS Subscriber Identity Module (USIM) judges 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 the information about the supported
ciphering and integrity protection algorithms.
6. The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE
of the integrity protection and ciphering algorithms that the UTRAN selects.
7. The UE sends a response message to the SRNC.
l If the integrity protection and ciphering algorithms are configured successfully, the UE
sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The
SRNC then sends a SECURITY MODE COMMAND COMPLETE message to the CN.
The message contains the information about the integrity protection and ciphering
algorithms that the UE uses.
l If the UE does not support the integrity protection and ciphering algorithms, the UE
sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The
message contains the error information and the reason for the failure. The SRNC then
sends a SECURITY MODE COMMAND REJECT message to the CN.
Triggering Conditions
The UE initiates a call.
Procedure
Figure 5-10 shows the call setup procedure.
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. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message.
3. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL
PROCEEDING and contains the information about the negotiated bearer capability of the
call.
4. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
5. A Radio Access Bearer (RAB) is set up. For details, refer to 5.5.5 RAB Setup
Procedure.
6. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the
SRNC. The message indicates ALERTING.
7. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
8. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates
CONNECT, which means that the called party has answered the call.
9. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
10. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
11. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message, indicating CONNECT
ACKNOWLEDGE.
The call is set up. The calling and called parties begin the conversation.
Triggering Conditions
A call is set up.
Procedure
I. Setting Up an RAB Successfully
Figure 5-11 shows the successful RAB setup procedure.
1. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the
RAB setup procedure.
2. (Optional; applicable to the ATM-based Iu-CS interface only) 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.
3. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the
NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio
links for carrying the RAB.
4. The NodeB allocates the associated resources and then sends a RADIO LINK
RECONFIGURATION READY message to the SRNC.
5. (Optional; required for the ATM-based Iub interface only) 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.
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.
1. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the
RAB setup procedure.
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 reason for the failure.
Triggering Conditions
A call ends and the calling party hangs up.
Procedure
Figure 5-13 shows the call release procedure.
8. (Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on the
Iu interface initiates an Iu data transport bearer release procedure.
9. The SRNC sends an IU RELEASE COMPLETE message to the CN.
Triggering Conditions
After an RAB is released, the SRNC judges whether the RRC connection carries any other RAB
of the UE. If judging that 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.
NOTE
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.
NOTE
The SRNC may send the RRC CONNECTION RELEASE message several times to increase the
probability of proper reception of the message by the UE. The RRC SNs of these messages are the
same. The number of retransmissions and the transmission intervals are determined by the SRNC. If
the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the UE
after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the
UE has released the RRC connection.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
3. The SRNC sends 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. (Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP
protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC
connection release procedure ends.
II. Releasing an RRC Connection from a CCH
Figure 5-15 shows the procedure for releasing an RRC connection from a CCH.
In the incoming call procedure, the network calls a UE and the UE responds to the paging. This
topic describes incoming call setup and release in terms of protocols, triggering 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, triggering conditions, and
signaling in normal and abnormal conditions.
Note the following information about the procedure shown in Figure 6-1:
l The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC
connection set up on the DCH as an example.
l 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.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 6-1 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_INIT_DIRECT_TRANS
INITIAL DIRECT TRANSFER
F
RRC_SECURITY_MODE_C
SECURITY MODE COMMAND
MD
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_SECURITY_MODE_C
SECURITY MODE COMPLETE
MP
RRC_SECURITY_MODE_F
SECURITY MODE FAILURE
AIL
RANAP_PAGING PAGING
RANAP_INITIAL_UE_MES
INITIAL UE MESSAGE
SAGE
Iu
RANAP_COMMON_ID COMMON ID
RANAP_DIRECT_TRANSFE
DIRECT TRANSFER
R
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_SECURITY_MODE
SECURITY MODE COMMAND
_COMMAND
RANAP_SECURITY_MODE
SECURITY MODE COMPLETE
_COMPLETE
RANAP_SECURITY_MODE
SECURITY MODE REJECT
_REJ
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT REQUEST
T_REQ
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT RESPONSE
T_RESP
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 6-2 shows an example of Uu signaling tracing result.
----End
Triggering Conditions
A terminal calls the UE.
Procedure
I. Paging a UE that Is in Idle Mode or in PCH State
Figure 6-5 shows the procedure for paging a UE that is in idle mode or in PCH state.
Figure 6-5 Paging procedure (for a UE that is in idle mode or in PCH state)
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.
II. Paging a UE that Is in CELL_DCH or CELL_FACH State
Figure 6-6 shows the procedure for paging a UE that is in CELL_DCH or CELL_FACH state.
Triggering 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 accepting the request, the RRM
module 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.
Figure 6-7 shows the procedure for setting up an RRC connection on a DCH.
Triggering Conditions
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 6-10 shows the signaling connection setup procedure.
Triggering Conditions
The UE and the CN exchange signaling. The network initiates the authentication and security
mode control procedure.
Procedure
Figure 6-11 shows the authentication and security mode control procedure.
1. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates
AUTHENTICATION REQUEST.
2. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
3. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
RESPONSE. If the UMTS Subscriber Identity Module (USIM) judges 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 the information about the supported
ciphering and integrity protection algorithms.
6. The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE
of the integrity protection and ciphering algorithms that the UTRAN selects.
Triggering Conditions
A UE receives a call from the CN.
Procedure
Figure 6-12 shows the call setup procedure.
1. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates
SETUP and contains the number of the calling party and the bearer capability of the call.
2. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
3. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER message
indicates CALL CONFIRM and contains the information about the negotiated bearer
capability of the call.
5. An RAB is set up. For details, refer to 6.5.6 RAB Setup Procedure.
6. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
7. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message, indicating ALERTING to request the
called terminal to ring.
8. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
9. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT 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 indicates
CONNECT ACKNOWLEDGE.
11. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
Triggering Conditions
A call is set up.
Procedure
I. Setting Up an RAB Successfully
Figure 6-13 shows the successful RAB setup procedure.
1. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the
RAB setup procedure.
2. (Optional; applicable to the ATM-based Iu-CS interface only) 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.
3. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the
NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio
links for carrying the RAB.
4. The NodeB allocates the associated resources and then sends a RADIO LINK
RECONFIGURATION READY message to the SRNC.
5. (Optional; required for the ATM-based Iub interface only) 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.
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.
Triggering Conditions
A call ends and the calling party hangs up.
Procedure
Figure 6-15 shows the call release procedure.
Triggering Conditions
After an RAB is released, the SRNC judges whether the RRC connection carries any other RAB
of the UE. If judging that 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.
NOTE
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.
Figure 6-16 shows the procedure for releasing an RRC connection from a DCH.
1. The SRNC sends an RRC CONNECTION RELEASE message to the UE through the
DCCH.
NOTE
The SRNC may send the RRC CONNECTION RELEASE message several times to increase the
probability of proper reception of the message by the UE. The RRC SNs of these messages are the
same. The number of retransmissions and the transmission intervals are determined by the SRNC. If
the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the UE
after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the
UE has released the RRC connection.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
3. The SRNC sends 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. (Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP
protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC
connection release procedure ends.
II. Releasing an RRC Connection from a CCH
Figure 6-17 shows the procedure for releasing an RRC connection from a CCH.
The intra-frequency handover procedure is performed to hand over a UE from the WCDMA cell
that it camps on to an intra-frequency WCDMA cell. This topic describes intra-frequency
handover in terms of types, protocols, triggering conditions, signaling procedure of a successful
intra-frequency handover, and signaling tracing on the RNC LMT. This topic also describes the
elementary procedures in terms of functions, triggering conditions, and signaling in normal and
abnormal conditions.
This describes the elementary procedures of intra-frequency soft handover within a NodeB in
terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Figure 7-1 Signaling procedure of a successful intra-frequency soft handover within a NodeB
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 7-2 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE
E
RRC_ACTIVE_SET_UPDAT
Uu ACTIVE SET UPDATE COMPLETE
E_CMP
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE FAILURE
E_FAIL
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 7-2 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 7-3 shows an example of Iub signaling tracing result.
----End
Triggering Conditions
The CRNC sends a RADIO LINK ADDITION REQUEST message.
Procedure
Figure 7-4 shows the radio link addition procedure.
Triggering Conditions
The active set update procedure can be triggered in either of the following conditions:
l Radio link addition
l Radio link deletion
Procedure
Figure 7-5 shows the active set update procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-6 shows the radio link deletion procedure.
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.
Figure 7-7 Signaling procedure of a successful intra-frequency soft handover between NodeBs
in an RNC
Note the following information about the procedure shown in Figure 7-7:
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 7-3 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE
E
RRC_ACTIVE_SET_UPDAT
Uu ACTIVE SET UPDATE COMPLETE
E_CMP
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE FAILURE
E_FAIL
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 7-8 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 7-9 shows an example of Iub signaling tracing result.
Step 3 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 7-10 shows an example of Q.AAL2 signaling tracing result.
----End
7.3.5.1 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.
7.3.5.2 Iub User Plane Setup Procedure
The Iub user plane setup procedure is performed to set up bearers for data transmission on the
Iub interface.
7.3.5.3 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.
7.3.5.4 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.
7.3.5.5 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.
7.3.5.6 Iub User Plane Release Procedure
The Iub user plane release procedure is performed to release data transport bearers from the Iub
interface.
Triggering Conditions
The CRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 7-11 shows the radio link setup procedure (intra-RNC handover or GSM to WCDMA
CS handover).
Figure 7-11 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS
handover)
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 7-12 shows the 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.
l If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH
CONFIRM message.
l If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH
RELEASE CONFIRM message.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 7-13 shows the radio link restoration procedure (intra-RNC handover or GSM to
WCDMA CS handover).
Figure 7-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.
Triggering Conditions
The active set update procedure can be triggered in either of the following conditions:
l Radio link addition
l Radio link deletion
Procedure
Figure 7-14 shows the active set update procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-15 shows the radio link deletion procedure.
l 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.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 7-16 shows the Iub user plane release procedure.
Figure 7-17 Signaling procedure of a successful intra-frequency soft handover between RNCs
Note the following information about the procedure shown in Figure 7-17:
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 7-4 lists the messages to be traced.
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE
E
RRC_ACTIVE_SET_UPDAT
Uu ACTIVE SET UPDATE COMPLETE
E_CMP
RRC_ACTIVE_SET_UPDAT
ACTIVE SET UPDATE FAILURE
E_FAIL
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 7-18 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 7-19 shows an example of Iub signaling tracing on the source RNC.
Figure 7-20 shows an example of Iub signaling tracing on the target RNC.
Step 3 Create an Iur tracing task by referring to Creating an RNC Tracing Task.
Figure 7-21 shows an example of Iur signaling tracing result.
Step 4 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 7-22 shows an example of Q.AAL2 signaling tracing result.
----End
Triggering Conditions
The SRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 7-23 shows the radio link setup procedure for inter-RNC handover.
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 7-24 shows the Iub user plane setup procedure.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 7-25 shows the radio link restoration procedure for inter-RNC handover.
Triggering Conditions
The DCHs are set up.
Procedure
Figure 7-26 shows the Iur user plane setup procedure.
Triggering Conditions
The active set update procedure can be triggered in either of the following conditions:
l Radio link addition
l Radio link deletion
Procedure
Figure 7-27 shows the active set update procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-28 shows the radio link deletion procedure.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 7-29 shows the Iub user plane release procedure.
Triggering Conditions
The transport channels on the Iur user plane need to be removed.
Procedure
Figure 7-30 shows the Iur user plane release procedure.
This describes the elementary procedures of intra-frequency hard handover between NodeBs in
an RNC in terms of triggering conditions and signaling procedures in normal and abnormal
conditions.
Figure 7-31 Signaling procedure of a successful intra-frequency hard handover between NodeBs
in an RNC
Note the following information about the procedure shown in Figure 7-31:
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 7-5 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
PHYSICAL CHANNEL
RRC_PH_CH_RECFG
RECONFIGURATION
PHYSICAL CHANNEL
Uu RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_FAIL
RECONFIGURATION FAILURE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 7-32 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 7-33 shows an example of Iub signaling tracing result.
Step 3 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 7-34 shows an example of Q.AAL2 signaling tracing result.
----End
7.5.5.1 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.
7.5.5.2 Iub User Plane Setup Procedure
The Iub user plane setup procedure is performed to set up bearers for data transmission on the
Iub interface.
7.5.5.3 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.
7.5.5.4 Physical Channel Reconfiguration Procedure
The physical channel reconfiguration procedure is performed to set up, reconfigure, or release
a physical channel.
7.5.5.5 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.
7.5.5.6 Iub User Plane Release Procedure
The Iub user plane release procedure is performed to release data transport bearers from the Iub
interface.
Triggering Conditions
The CRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 7-35 shows the radio link setup procedure (intra-RNC handover or GSM to WCDMA
CS handover).
Figure 7-35 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS
handover)
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 7-36 shows the Iub user plane setup procedure.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 7-37 shows the radio link restoration procedure (intra-RNC handover or GSM to
WCDMA CS handover).
Figure 7-37 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.
Triggering Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 7-38 shows the physical channel reconfiguration procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-39 shows the radio link deletion procedure.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 7-40 shows the Iub user plane release procedure.
7.6.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between
RNCs
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of
an intra-frequency hard handover between RNCs.
7.6.5 Elementary Procedures of Intra-Frequency Hard Handover Between RNCs
This describes the elementary procedures of intra-frequency hard handover between RNCs in
terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Figure 7-41 Signaling procedure of a successful intra-frequency hard handover between RNCs
Note the following information about the procedure shown in Figure 7-41:
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 7-6 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
PHYSICAL CHANNEL
RRC_PH_CH_RECFG
RECONFIGURATION
PHYSICAL CHANNEL
Uu RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_FAIL
RECONFIGURATION FAILURE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 7-42 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 7-43 shows an example of Iub signaling tracing on the source RNC.
Figure 7-44 shows an example of Iub signaling tracing on the target RNC.
Step 3 Create an Iur tracing task by referring to Creating an RNC Tracing Task.
Figure 7-45 shows an example of Iur signaling tracing result.
Step 4 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 7-46 shows an example of Q.AAL2 signaling tracing result.
----End
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.
7.6.5.4 Iur User Plane Setup Procedure
The Iur user plane setup procedure is performed to set up bearers for data transmission on the
Iur interface.
7.6.5.5 Physical Channel Reconfiguration Procedure
The physical channel reconfiguration procedure is performed to set up, reconfigure, or release
a physical channel.
7.6.5.6 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.
7.6.5.7 Iub User Plane Release Procedure
The Iub user plane release procedure is performed to release data transport bearers from the Iub
interface.
7.6.5.8 Iur User Plane Release Procedure
The Iur user plane release procedure is performed to release data transport bearers from the Iur
interface.
Triggering Conditions
The SRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 7-47 shows the radio link setup procedure for inter-RNC handover.
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.
l 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.
l If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE
message.
5. The DRNC reports the radio link setup result to the SRNC.
l If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSE
message.
l If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE
message, indicating the failure cause.
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 7-48 shows the 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.
l If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH
CONFIRM message.
l If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH
RELEASE CONFIRM message.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 7-49 shows the radio link restoration procedure for inter-RNC handover.
Triggering Conditions
The DCHs are set up.
Procedure
Figure 7-50 shows the Iur user plane setup procedure.
Triggering Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 7-51 shows the physical channel reconfiguration procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-52 shows the radio link deletion procedure.
l If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
RESPONSE message.
l 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.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 7-53 shows the Iub user plane release procedure.
Triggering Conditions
The transport channels on the Iur user plane need to be removed.
Procedure
Figure 7-54 shows the Iur user plane release procedure.
The inter-frequency handover procedure is performed to hand over a UE from the WCDMA cell
that it camps on to an inter-frequency WCDMA cell. This topic describes inter-frequency
handover in terms of types, protocols, triggering conditions, signaling procedure of a successful
inter-frequency handover, and signaling tracing on the RNC LMT. This topic also describes the
elementary procedures in terms of functions, triggering conditions, and signaling in normal and
abnormal conditions.
Note the following information about the procedure shown in Figure 8-1:
l 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.
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 8-2 lists the messages to be traced.
PHYSICAL CHANNEL
RRC_PH_CH_RECFG
RECONFIGURATION
PHYSICAL CHANNEL
Uu RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_FAIL
RECONFIGURATION FAILURE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 8-2 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 8-3 shows an example of Iub signaling tracing result.
Step 3 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 8-4 shows an example of Q.AAL2 signaling tracing result.
----End
Triggering Conditions
The CRNC sends a RADIO LINK ADDITION REQUEST message.
Procedure
Figure 8-5 shows the radio link addition procedure.
Triggering Conditions
The CRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 8-6 shows the radio link setup procedure (intra-RNC handover or GSM to WCDMA CS
handover).
Figure 8-6 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 8-7 shows the Iub user plane setup procedure.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 8-8 shows the radio link restoration procedure (intra-RNC handover or GSM to WCDMA
CS handover).
Figure 8-8 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.
Triggering Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 8-9 shows the physical channel reconfiguration procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 8-10 shows the radio link deletion procedure.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 8-11 shows the Iub user plane release procedure.
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of
an inter-frequency handover between RNCs.
8.3.5 Elementary Procedures of Inter-Frequency Handover Between RNCs
This describes the elementary procedures of inter-frequency handover between RNCs in terms
of triggering conditions and signaling procedures in normal and abnormal conditions.
Note the following information about the procedure shown in Figure 8-12:
l During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
l 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.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 8-3 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
PHYSICAL CHANNEL
RRC_PH_CH_RECFG
RECONFIGURATION
PHYSICAL CHANNEL
Uu RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_FAIL
RECONFIGURATION FAILURE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 8-13 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 8-14 shows an example of Iub signaling tracing on the source RNC.
Figure 8-15 shows an example of Iub signaling tracing on the target RNC.
Step 3 Create an Iur tracing task by referring to Creating an RNC Tracing Task.
Figure 8-16 shows an example of Iur signaling tracing result.
Step 4 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task.
Figure 8-17 shows an example of Q.AAL2 signaling tracing result.
----End
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.
8.3.5.4 Iur User Plane Setup Procedure
The Iur user plane setup procedure is performed to set up bearers for data transmission on the
Iur interface.
8.3.5.5 Physical Channel Reconfiguration Procedure
The physical channel reconfiguration procedure is performed to set up, reconfigure, or release
a physical channel.
8.3.5.6 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.
8.3.5.7 Iub User Plane Release Procedure
The Iub user plane release procedure is performed to release data transport bearers from the Iub
interface.
8.3.5.8 Iur User Plane Release Procedure
The Iur user plane release procedure is performed to release data transport bearers from the Iur
interface.
Triggering Conditions
The SRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 8-18 shows the radio link setup procedure for inter-RNC handover.
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.
l 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.
l If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE
message.
5. The DRNC reports the radio link setup result to the SRNC.
l If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSE
message.
l If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE
message, indicating the failure cause.
Triggering Conditions
The Iub user plane setup procedure can be triggered in one of the following conditions:
l The common transport channels are set up.
l The dedicated transport channels are set up.
Procedure
Figure 8-19 shows the 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.
l If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH
CONFIRM message.
l If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH
RELEASE CONFIRM message.
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 8-20 shows the radio link restoration procedure for inter-RNC handover.
Triggering Conditions
The DCHs are set up.
Procedure
Figure 8-21 shows the Iur user plane setup procedure.
Triggering Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 8-22 shows the physical channel reconfiguration procedure.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 8-23 shows the radio link deletion procedure.
l If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
RESPONSE message.
l 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.
Triggering Conditions
The transport channels on the Iub user plane need to be removed.
Procedure
Figure 8-24 shows the Iub user plane release procedure.
Triggering Conditions
The transport channels on the Iur user plane need to be removed.
Procedure
Figure 8-25 shows the Iur user plane release 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 topic describes inter-RAT handover in terms of types,
protocols, triggering 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, triggering conditions, and signaling in normal and abnormal conditions.
Based on domains, inter-RAT handovers from WCDMA to GSM and those from GSM to
WCDMA are further categorized into the following types:
l Inter-RAT CS handover from WCDMA to GSM
l Inter-RAT PS handover from WCDMA to GSM
l Inter-RAT CS handover from GSM to WCDMA
l Inter-RAT PS handover from GSM to WCDMA
Figure 9-1 Signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM
Note the following information about the procedure shown in Figure 9-1:
l 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).
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 9-1 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RELOCATION_RE
RELOCATION REQUIRED
QUIRED
RANAP_RELOCATION_CO
RELOCATION COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 9-2 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 9-3 shows an example of Iub signaling tracing result.
----End
Triggering Conditions
The relocation preparation procedure can be triggered in either of the following conditions:
l During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
Procedure
Figure 9-5 shows the relocation preparation procedure.
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.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
Procedure
Figure 9-6 shows the 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.
NOTE
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.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 9-7 shows the radio link deletion procedure.
Figure 9-8 Signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA
Note the following information about the procedure shown in Figure 9-8:
l 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).
l 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.
l 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.
l 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.
l In practice, the signaling messages traced may differ from the signaling message shown in
the figure in terms of the sequence.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 9-2 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_UTRAN_MOBIL_INF
UTRAN MOBILITY INFORMATION
O
RRC_SECURITY_MODE_C
SECURITY MODE COMMAND
MD
RRC_SECURITY_MODE_C
SECURITY MODE COMPLETE
MP
RRC_SECURITY_MODE_F
SECURITY MODE FAILURE
AIL
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RELOCATION_RE
RELOCATION REQUEST
Q
RANAP_RELOCATION_FAI
Iu RELOCATION FAILURE
LURE
RANAP_RELOCATION_DE
RELOCATION DECTECT
TECT
RANAP_RELOCATION_CO
RELOCATION COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 9-9 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 9-10 shows an example of Iub signaling tracing result.
----End
Triggering Conditions
The relocation resource allocation procedure can be triggered in either of the following
conditions:
l During an SRNS relocation, the CN applies for resources from the target RNC.
l During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources
from the target RNC.
Procedure
Figure 9-12 shows the relocation resource allocation procedure.
Triggering Conditions
The CRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 9-13 shows the radio link setup procedure (intra-RNC handover or GSM to WCDMA
CS handover).
Figure 9-13 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS
handover)
Triggering Conditions
The NodeB detects UL signals from the UE. That is, the NodeB finishes UL synchronization
with the UE.
Procedure
Figure 9-14 shows the radio link restoration procedure (intra-RNC handover or GSM to
WCDMA CS handover).
Figure 9-14 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.
Triggering Conditions
The UTRAN sends a UE CAPABILITY ENQUIRY message to acquire the UE capability
information related to any radio access network.
Procedure
Figure 9-15 shows the 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 the 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.
Triggering Conditions
The ciphering algorithm or the integrity protection algorithm has changed.
Procedure
Figure 9-16 shows the security mode control procedure.
Triggering Conditions
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
Procedure
Figure 9-17 shows the UTRAN mobility information procedure.
Figure 9-18 shows the signaling procedure of a successful inter-RAT PS handover from
WCDMA to GSM.
Figure 9-18 Signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM
Note the following information about the procedure shown in Figure 9-18:
l When the PS data volume is low, the UE may be in 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.
l 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.
l 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 need to be
transferred.
l The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from
WCDMA to GSM.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 9-3 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_SRNS_CONTEXT_
SRNS CONTEXT REQUEST
REQ
RANAP_SRNS_CONTEXT_
SRNS CONTEXT RESPONSE
RESP
RANAP_SRNS_DATA_FOR
Iu SRNS DATA FORWARD COMMAND
WARD_COMMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 9-19 shows an example of Uu signaling tracing result.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task.
Figure 9-20 shows an example of Iub signaling tracing result.
----End
Triggering Conditions
The network decides to hand over the UE to the GSM system.
Procedure
Figure 9-22 shows the cell change order from UTRAN procedure.
Triggering 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 9-23 shows the SRNS context transfer procedure.
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.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
l The transaction between the UE and the CN is complete.
l The UTRAN requests the CN to release the resources on the Iu interface by, for example,
sending an IU RELEASE REQUEST message.
l The Serving Radio Network Subsystem (SRNS) is relocated.
l The SRNS relocation is canceled after a relocation resource allocation procedure is
complete.
Procedure
Figure 9-24 shows the Iu release procedure.
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.
Triggering Conditions
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 9-25 shows the radio link deletion procedure.
The SRNS relocation procedure is performed to change control from the SRNC of a UE to
another RNC. This topic describes the SRNS relocation in terms of types, protocols, triggering
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, triggering
conditions, and signaling in normal and abnormal conditions.
UE-not-involved reloaction:
l Static relocation: The relocation is triggered after a radio link is added to the DRNC for the
UE
l 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.
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.
If the DRNC does not obtain the information about the UE capability, the DRNC initiates a UE
capability enquiry procedure.
10.2.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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 10-1 and Table 10-2 list the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RELOCATION_REQU
RELOCATION REQUIRED
IRED
RANAP_RELOCATION_COM
RELOCATION COMMAND
MAND
RANAP_IU_RELEASE_COMM
IU RELEASE COMMAND
AND
RANAP_IU_RELEASE_COMP
IU RELEASE COMPLETE
LETE
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_UTRAN_MOBIL_INF
UTRAN MOBILITY INFORMATION
O
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RELOCATION_RE
RELOCATION REQUEST
Q
RANAP_RELOCATION_FAI
Iu RELOCATION FAILURE
LURE
RANAP_RELOCATION_DE
RELOCATION DETECT
TECT
RANAP_RELOCATION_CO
RELOCATION COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 10-2 shows an example of Uu signaling tracing result.
Step 2 Create an Iur tracing task by referring to Creating an RNC Tracing Task.
Figure 10-3 shows an example of Iur signaling tracing on the SRNC.
----End
Triggering Conditions
The relocation preparation procedure can be triggered in either of the following conditions:
l During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
l During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends a
RELOCATION REQUIRED message.
Procedure
Figure 10-7 shows the 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. The CN sends a response message to the SRNC.
l 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.
l If the resources partially or totally fail to be allocated, the CN sends a RELOCATION
PREPARATION FAILURE message.
Triggering Conditions
The relocation resource allocation procedure can be triggered in either of the following
conditions:
l During an SRNS relocation, the CN applies for resources from the target RNC.
l During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources
from the target RNC.
Procedure
Figure 10-8 shows the relocation resource allocation procedure.
Triggering Conditions
The CN sends a RELOCATION COMMAND message to the SRNC.
Procedure
Figure 10-9 shows the relocation commit procedure for the static relocation or relocation with
cell/URA update.
Figure 10-9 Relocation commit procedure (static relocation or relocation with cell/URA update)
Triggering Conditions
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
Procedure
Figure 10-10 shows the UTRAN mobility information procedure.
Triggering Conditions
The UTRAN sends a UE CAPABILITY ENQUIRY message to acquire the UE capability
information related to any radio access network.
Procedure
Figure 10-11 shows the UE capability enquiry procedure.
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.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
l The transaction between the UE and the CN is complete.
l The UTRAN requests the CN to release the resources on the Iu interface by, for example,
sending an IU RELEASE REQUEST message.
l The Serving Radio Network Subsystem (SRNS) is relocated.
l The SRNS relocation is canceled after a relocation resource allocation procedure is
complete.
Procedure
Figure 10-12 shows the 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.
NOTE
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.
Note the following information about the procedure shown in Figure 10-13:
l 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.
l 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.
l 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.
l 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.
l If the DRNC does not obtain the information about the UE capability, the DRNC initiates
a UE capability enquiry procedure.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 10-3 and Table 10-4 list the messages to be traced.
Interface
and
Message Name on the LMT Message Name in Protocols
Protocol to
Be Traced
RANAP_RELOCATION_REQ
RELOCATION REQUIRED
UIRED
RANAP_RELOCATION_COM
RELOCATION COMMAND
MAND
RANAP_IU_RELEASE_COM
IU RELEASE COMMAND
MAND
RANAP_IU_RELEASE_COMP
IU RELEASE COMPLETE
LETE
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RRC_CELL_UPDATE_CON
CELL UPDATE CONFIRM
FIRM
RRC_URA_UPDATE_CONF
URA UPDATE CONFIRM
IRM
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
RANAP_RELOCATION_RE
RELOCATION REQUEST
Q
RANAP_RELOCATION_FAI
Iu RELOCATION FAILURE
LURE
RANAP_RELOCATION_DE
RELOCATION DETECT
TECT
RANAP_RELOCATION_CO
RELOCATION COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 10-14 shows an example of Uu signaling tracing for the relocation with cell update.
Figure 10-14 Example of Uu signaling tracing for the relocation with cell update
Step 2 Create an Iur tracing task by referring to Creating an RNC Tracing Task.
Figure 10-15 shows an example of Iur signaling tracing on the SRNC.
----End
monitoring the RRC connection, switching the status of the RRC connection, reporting errors,
and transferring information.
10.3.5.4 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.
10.3.5.5 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.
10.3.5.6 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.
10.3.5.7 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.
Triggering Conditions
The relocation preparation procedure can be triggered in either of the following conditions:
l During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
l During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends a
RELOCATION REQUIRED message.
Procedure
Figure 10-19 shows the relocation preparation procedure.
Triggering Conditions
The relocation resource allocation procedure can be triggered in either of the following
conditions:
l During an SRNS relocation, the CN applies for resources from the target RNC.
l During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources
from the target RNC.
Procedure
Figure 10-20 shows the relocation resource allocation procedure.
Triggering Conditions
The cell update procedure can be triggered in one of the following conditions:
l Cell reselection
l Re-entering the service area
l Periodical cell update
l Radio link failure
l Paging response
l Uplink data transmission
l RLC unrecoverable error
Procedure
Figure 10-21 shows the cell update procedure.
Triggering Conditions
The URA update procedure can be triggered in either of the following conditions:
l URA reselection
l Periodical URA update
Procedure
Figure 10-22 shows the URA update procedure.
Triggering Conditions
The CN sends a RELOCATION COMMAND message to the SRNC.
Procedure
Figure 10-23 shows the relocation commit procedure for the static relocation or relocation with
cell/URA update.
Figure 10-23 Relocation commit procedure (static relocation or relocation with cell/URA
update)
Triggering Conditions
The UTRAN sends a UE CAPABILITY ENQUIRY message to acquire the UE capability
information related to any radio access network.
Procedure
Figure 10-24 shows the UE capability enquiry procedure.
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.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
l The transaction between the UE and the CN is complete.
l The UTRAN requests the CN to release the resources on the Iu interface by, for example,
sending an IU RELEASE REQUEST message.
l The Serving Radio Network Subsystem (SRNS) is relocated.
l The SRNS relocation is canceled after a relocation resource allocation procedure is
complete.
Procedure
Figure 10-25 shows the 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.
NOTE
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.
Note the following information about the procedure shown in Figure 10-26:
l 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.
l After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, the
DRNC sends a RELOCATION DETECT message to the CN.
l If the DRNC does not obtain the information about the UE capability, the DRNC initiates
a UE capability enquiry procedure.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 10-5 and Table 10-6 list the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
PHYSICAL CHANNEL
RRC_PH_CH_RECFG
RECONFIGURATION
Uu
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_FAIL
RECONFIGURATION FAILURE
RANAP_RELOCATION_REQU
RELOCATION REQUIRED
IRED
RANAP_RELOCATION_COM
RELOCATION COMMAND
MAND
RANAP_IU_RELEASE_COMM
IU RELEASE COMMAND
AND
RANAP_IU_RELEASE_COMP
IU RELEASE COMPLETE
LETE
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
PHYSICAL CHANNEL
RRC_PH_CH_RECFG_CMP
RECONFIGURATION COMPLETE
RANAP_RELOCATION_RE
Iu RELOCATION REQUEST
Q
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_RELOCATION_FAI
RELOCATION FAILURE
LURE
RANAP_FORWARD_SRNS_
FORWARD SRNS CONTEXT
CONTEXT
RANAP_RELOCATION_DE
RELOCATION DETECT
TECT
RANAP_RELOCATION_CO
RELOCATION COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 10-27 shows an example of Uu signaling tracing on the SRNC.
----End
Triggering Conditions
The relocation preparation procedure can be triggered in either of the following conditions:
l During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
l During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends a
RELOCATION REQUIRED message.
Procedure
Figure 10-31 shows the 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. The CN sends a response message to the SRNC.
l 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.
l If the resources partially or totally fail to be allocated, the CN sends a RELOCATION
PREPARATION FAILURE message.
Triggering Conditions
The relocation resource allocation procedure can be triggered in either of the following
conditions:
l During an SRNS relocation, the CN applies for resources from the target RNC.
l During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources
from the target RNC.
Procedure
Figure 10-32 shows the relocation resource allocation procedure.
Triggering Conditions
The CN sends a RELOCATION COMMAND message to the SRNC.
Procedure
Figure 10-33 shows the relocation commit procedure for the relocation with hard handover.
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. The original DRNC sends a RELOCATION COMPLETE message to the CN to notify that
the relocation is successful.
Triggering Conditions
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 10-34 shows the physical channel reconfiguration procedure.
Triggering Conditions
The UTRAN sends a UE CAPABILITY ENQUIRY message to acquire the UE capability
information related to any radio access network.
Procedure
Figure 10-35 shows the UE capability enquiry procedure.
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.
Triggering Conditions
The Iu release procedure can be triggered in one of the following conditions:
l The transaction between the UE and the CN is complete.
l The UTRAN requests the CN to release the resources on the Iu interface by, for example,
sending an IU RELEASE REQUEST message.
l The Serving Radio Network Subsystem (SRNS) is relocated.
l The SRNS relocation is canceled after a relocation resource allocation procedure is
complete.
Procedure
Figure 10-36 shows the 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.
NOTE
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 UE sets up an RRC connection to RNC 1, which is the SRNC. During the relocation, RNC
1 is the source RNC and RNC 2 is the target RNC.
The location service procedure is performed to identify the geographic location of a UE. This
topic describes the location services in terms of positioning methods, protocols, triggering
conditions, signaling procedure of successful positioning, and signaling tracing on the RNC
LMT. This topic also describes the elementary procedures in terms of functions, triggering
conditions, and signaling in normal and abnormal conditions.
Typically, in terms of the horizontal accuracy, Network Assisted GPS (A-GPS) ranks first,
Observed Time Difference Of Arrival (OTDOA) second and CELLID+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 CELLID+RTT positioning method may
provide higher accuracy.
After receiving the positioning request from the CN, the RNC chooses the UE-assisted CELLID
+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.
Figure 11-1 shows the signaling procedure of successful positioning based on CELLID+RTT.
Note the following information about the procedure shown in Figure 11-1:
l The CN sends an authenticated LOCATION REPORTING CONTROL message to the
SRNC, and the SRNC chooses the UE-assisted CELLID+RTT positioning method.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 11-1 lists the messages to be traced.
RANAP_LOCATION_REPO
LOCATION REPORTING CONTROL
RTING_CONTROL
Iu
RANAP_LOCATION_REPO
LOCATION REPORT
RT
Procedure
Create a Call Data Tracing (CDT) task for a UE in positioning by referring to Creating an RNC
Tracing Task.
Figure 11-2 shows an example of CDT tracing on the positioning based on CELLID+RTT.
----End
UE Measurement Procedure
The UE measurement procedure is performed for the RNC to request a report of attributes from
the UE.
Triggering Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC
initiates the UE measurement procedure for the location service.
Procedure
Figure 11-3 shows the UE measurement procedure.
Triggering 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 11-4 shows the RTT measurement procedure.
l 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.
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.
Figure 11-5 shows the signaling procedure of successful positioning based on OTDOA-IPDL.
Note the following information about the procedure shown in Figure 11-5:
l The CN sends an authenticated LOCATION REPORTING CONTROL message to the
SRNC, and the SRNC chooses the UE-assisted OTDOA-IPDL positioning method.
l If the UE is in CELL_DCH state, the SRNC performs the RTT measurement in the reference
cell.
l 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.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 11-2 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_LOCATION_REPO
LOCATION REPORTING CONTROL
RTING_CONTROL
Iu
RANAP_LOCATION_REPO
LOCATION REPORT
RT
Procedure
Create a Call Data Tracing (CDT) task for a UE in positioning by referring to Creating an RNC
Tracing Task.
Figure 11-6 shows an example of CDT tracing on the positioning based on CELLID+RTT.
----End
The UE measurement procedure is performed for the RNC to request a report of attributes from
the UE.
11.3.5.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.
UE Measurement Procedure
The UE measurement procedure is performed for the RNC to request a report of attributes from
the UE.
Triggering Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC
initiates the UE measurement procedure for the location service.
Procedure
Figure 11-7 shows the UE measurement procedure.
l 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.
Triggering 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 11-8 shows the RTT measurement procedure.
Note the following information about the procedure shown in Figure 11-9:
l The CN sends an authenticated LOCATION REPORTING CONTROL message to the
SRNC, and the SRNC chooses the UE-assisted A-GPS positioning method.
l The SRNC calculates the 3-D location of each satellite that is involved in the positioning,
according to the GPS satellite ephemeris. With the results of measurement based on A-
GPS, the SRNC performs location calculation. Then, the SRNC reports the positioning
results to the CN through a LOCATION REPORT message.
Prerequisite
l The RNC LMT works properly.
l You are logged in to the RNC as a user authorized to perform tracing management.
Context
Table 11-3 lists the messages to be traced.
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
Interface
and Protocol Message Name on the LMT Message Name in Protocols
to Be Traced
RANAP_LOCATION_REPO
LOCATION REPORTING CONTROL
RTING_CONTROL
Iu
RANAP_LOCATION_REPO
LOCATION REPORT
RT
Procedure
Create a Call Data Tracing (CDT) task for a UE in positioning by referring to Creating an RNC
Tracing Task.
Figure 11-10 shows an example of CDT tracing result.
----End
UE Measurement Procedure
The UE measurement procedure is performed for the RNC to request a report of attributes from
the UE.
Triggering Conditions
After receiving a LOCATION REPORTING CONTROL message from the CN, the RNC
initiates the UE measurement procedure for the location service.
Procedure
Figure 11-11 shows the UE measurement procedure.