RAN Signaling Analysis Guide (RAN11.0 - 01)

RAN 11.
Signalling Analysis Guide
Issue Date
01 2009-03-25
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are 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.
RAN Signalling Analysis Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Cell Setup Procedure.................................................................................................................1-1
1.1 Protocols Related to Cell Setup.......................................................................................................................1-2 1.2 Triggering Conditions of Cell Setup...............................................................................................................1-2 1.3 Signaling Procedure of Successful Cell Setup................................................................................................1-2 1.4 Using the RNC LMT to Trace the Cell Setup Procedure................................................................................1-3 1.5 Elementary Procedures of Cell Setup..............................................................................................................1-6 1.5.1 Resource Status Indication Procedure....................................................................................................1-6 1.5.2 Resource Audit Procedure......................................................................................................................1-7 1.5.3 Cell Setup Procedure..............................................................................................................................1-8 1.5.4 Common Transport Channel Setup Procedure.......................................................................................1-9 1.5.5 Iub User Plane Setup Procedure...........................................................................................................1-10 1.5.6 System Information Update Procedure................................................................................................1-11 1.5.7 Physical Shared Channel Reconfiguration Procedure..........................................................................1-12 1.5.8 Common Measurement Initiation Procedure.......................................................................................1-13
2 Cell Reconfiguration Procedure..............................................................................................2-1

2.1 Protocols Related to Cell Reconfiguration......................................................................................................2-2 2.2 Triggering Conditions of Cell Reconfiguration..............................................................................................2-2 2.3 Signaling Procedure of Cell Reconfiguration.................................................................................................2-2 2.4 Using the RNC LMT to Trace the Cell Reconfiguration Procedure...............................................................2-3
3 Cell Deletion Procedure............................................................................................................3-1

3.1 Protocols Related to Cell Deletion..................................................................................................................3-2 3.2 Triggering Conditions of Cell Deletion..........................................................................................................3-2 3.3 Signaling Procedure of Cell Deletion..............................................................................................................3-2 3.4 Using the RNC LMT to Trace the Cell Deletion Procedure...........................................................................3-3
4 Location Update Procedure......................................................................................................4-1

4.1 Protocols Related to Location Update.............................................................................................................4-2 4.2 Triggering Conditions of Location Update.....................................................................................................4-2 4.3 Signaling Procedure of a Successful Location Update...................................................................................4-2 4.4 Using the RNC LMT to Trace the Location Update Procedure......................................................................4-3 4.5 Elementary Procedures of Location Update....................................................................................................4-6 4.5.1 RRC Connection Setup Procedure.........................................................................................................4-6 Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
RAN Signalling Analysis Guide 4.5.2 Location Update Procedure....................................................................................................................4-9 4.5.3 Iu Release Procedure............................................................................................................................4-10 4.5.4 RRC Connection Release Procedure....................................................................................................4-11
5 Outgoing Call Procedure..........................................................................................................5-1

5.1 Protocols Related to an Outgoing Call............................................................................................................5-2 5.2 Triggering Conditions of an Outgoing Call....................................................................................................5-2 5.3 Signaling Procedure of a Successful Outgoing Call.......................................................................................5-2 5.4 Using the RNC LMT to Trace the Outgoing Call Procedure..........................................................................5-4 5.5 Elementary Procedures of an Outgoing Call...................................................................................................5-7 5.5.1 RRC Connection Setup Procedure.........................................................................................................5-8 5.5.2 Signaling Connection Setup Procedure (Outgoing Call).....................................................................5-11 5.5.3 Authentication and Security Mode Control Procedure........................................................................5-12 5.5.4 Call Setup Procedure (Outgoing Call).................................................................................................5-13 5.5.5 RAB Setup Procedure..........................................................................................................................5-15 5.5.6 Call Release Procedure (Outgoing Call)..............................................................................................5-16 5.5.7 RRC Connection Release Procedure....................................................................................................5-17
6 Incoming Call Procedure..........................................................................................................6-1

6.1 Protocols Related to an Incoming Call............................................................................................................6-2 6.2 Triggering Conditions of an Incoming Call....................................................................................................6-2 6.3 Signaling Procedure of a Successful Incoming Call.......................................................................................6-2 6.4 Using the RNC LMT to Trace the Incoming Call Procedure..........................................................................6-4 6.5 Elementary Procedures of an Incoming Call...................................................................................................6-7 6.5.1 Paging Procedure....................................................................................................................................6-8 6.5.2 RRC Connection Setup Procedure.........................................................................................................6-9 6.5.3 Signaling Connection Setup Procedure (Incoming Call).....................................................................6-12 6.5.4 Authentication and Security Mode Control Procedure........................................................................6-13 6.5.5 Call Setup Procedure (Incoming Call).................................................................................................6-14 6.5.6 RAB Setup Procedure..........................................................................................................................6-16 6.5.7 Call Release Procedure (Incoming Call)..............................................................................................6-17 6.5.8 RRC Connection Release Procedure....................................................................................................6-19
7 Intra-Frequency Handover Procedure....................................................................................7-1

7.1 Types of Intra-Frequency Handover...............................................................................................................7-2 7.2 Intra-Frequency Soft Handover Within a NodeB............................................................................................7-2 7.2.1 Protocols Related to Intra-Frequency Soft Handover Within a NodeB.................................................7-3 7.2.2 Triggering Conditions of Intra-Frequency Soft Handover Within a NodeB..........................................7-3 7.2.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Within a NodeB........................7-3 7.2.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Within a NodeB......7-4 7.2.5 Elementary Procedures of Intra-Frequency Soft Handover Within a NodeB........................................7-5 7.3 Intra-Frequency Soft Handover Between NodeBs in an RNC........................................................................7-8 7.3.1 Protocols Related to Intra-Frequency Soft Handover Between NodeBs in an RNC.............................7-9 7.3.2 Triggering Conditions of Intra-Frequency Soft Handover Between NodeBs in an RNC......................7-9 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
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-10 7.3.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC..................7-12 7.4 Intra-Frequency Soft Handover Between RNCs...........................................................................................7-17 7.4.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs.................................................7-18 7.4.2 Triggering Conditions of Intra-Frequency Soft Handover Between RNCs.........................................7-18 7.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs.......................7-18 7.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs.....7-19 7.4.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs.......................................7-22 7.5 Intra-Frequency Hard Handover Between NodeBs in an RNC....................................................................7-29 7.5.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC..........................7-30 7.5.2 Triggering Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC..................7-30 7.5.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC .......................................................................................................................................................................7-30 7.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in an RNC...............................................................................................................................................................7-31 7.5.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC.................7-33 7.6 Intra-Frequency Hard Handover Between RNCs..........................................................................................7-38 7.6.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs...............................................7-39 7.6.2 Triggering Conditions of Intra-Frequency Hard Handover Between RNCs........................................7-39 7.6.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs......................7-39 7.6.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between RNCs....7-40 7.6.5 Elementary Procedures of Intra-Frequency Hard Handover Between RNCs......................................7-43
8 Inter-Frequency Handover Procedure....................................................................................8-1

8.1 Types of Inter-Frequency Handover...............................................................................................................8-2 8.2 Inter-Frequency Handover Between NodeBs in an RNC...............................................................................8-2 8.2.1 Protocols Related to Inter-Frequency Handover Between NodeBs in an RNC.....................................8-3 8.2.2 Triggering Conditions of Inter-Frequency Handover Between NodeBs in an RNC.............................8-3 8.2.3 Signaling Procedure of a Successful Inter-Frequency Handover Between NodeBs in an RNC............8-3 8.2.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between NodeBs in an RNC .........................................................................................................................................................................8-4 8.2.5 Elementary Procedures of Inter-Frequency Handover Between NodeBs in an RNC............................8-6 8.3 Inter-Frequency Handover Between RNCs...................................................................................................8-12 8.3.1 Protocols Related to Inter-Frequency Handover Between RNCs........................................................8-13 8.3.2 Triggering Conditions of Inter-Frequency Handover Between RNCs.................................................8-13 8.3.3 Signaling Procedure of a Successful Inter-Frequency Handover Between RNCs...............................8-13 8.3.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between RNCs.............8-14 8.3.5 Elementary Procedures of Inter-Frequency Handover Between RNCs...............................................8-16
9 Inter-RAT Handover Procedure..............................................................................................9-1

9.1 Types of Inter-RAT Handover........................................................................................................................9-2 9.2 Inter-RAT CS Handover from WCDMA to GSM..........................................................................................9-2 Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
RAN Signalling Analysis Guide 9.2.1 Protocols Related to Inter-RAT CS Handover from WCDMA to GSM................................................9-2 9.2.2 Triggering Conditions of Inter-RAT CS Handover from WCDMA to GSM........................................9-3 9.2.3 Signaling Procedure of a Successful Inter-RAT CS Handover from WCDMA to GSM...................... 9-3 9.2.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from WCDMA to GSM .........................................................................................................................................................................9-4 9.2.5 Elementary Procedures of Inter-RAT CS Handover from WCDMA to GSM.......................................9-5
9.3 Inter-RAT CS Handover from GSM to WCDMA..........................................................................................9-8 9.3.1 Protocols Related to Inter-RAT CS Handover from GSM to WCDMA................................................9-9 9.3.2 Triggering Conditions of Inter-RAT CS Handover from GSM to WCDMA........................................9-9 9.3.3 Signaling Procedure of a Successful Inter-RAT CS Handover from GSM to WCDMA...................... 9-9 9.3.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from GSM to WCDMA .......................................................................................................................................................................9-11 9.3.5 Elementary Procedures of Inter-RAT CS Handover from GSM to WCDMA.....................................9-13 9.4 Inter-RAT PS Handover from WCDMA to GSM........................................................................................9-19 9.4.1 Protocols Related to Inter-RAT PS Handover from WCDMA to GSM..............................................9-19 9.4.2 Triggering Conditions of Inter-RAT PS Handover from WCDMA to GSM......................................9-19 9.4.3 Signaling Procedure of Successful Inter-RAT PS Handover from WCDMA to GSM.......................9-20 9.4.4 Using the RNC LMT to Trace the Procedure of Inter-RAT PS Handover from WCDMA to GSM .......................................................................................................................................................................9-21 9.4.5 Elementary Procedures of Inter-RAT PS Handover from WCDMA to GSM.....................................9-22 9.5 Inter-RAT PS Handover from GSM to WCDMA........................................................................................9-26
10 SRNS Relocation Procedure.................................................................................................10-1

10.1 Types of SRNS Relocation.........................................................................................................................10-2 10.2 Static Relocation.........................................................................................................................................10-2 10.2.1 Protocols Related to Static Relocation...............................................................................................10-2 10.2.2 Triggering Conditions of Static Relocation.......................................................................................10-3 10.2.3 Signaling Procedure of a Successful Static Relocation......................................................................10-3 10.2.4 Using the RNC LMT to Trace the Static Relocation Procedure........................................................10-3 10.2.5 Elementary Procedures of Static Relocation......................................................................................10-6 10.3 Relocation with Cell/URA Update............................................................................................................10-12 10.3.1 Protocols Related to Relocation with Cell/URA Update.................................................................10-13 10.3.2 Triggering Conditions of Relocation with Cell/URA Update..........................................................10-13 10.3.3 Signaling Procedure of a Successful Relocation with Cell/URA Update........................................10-13 10.3.4 Using the RNC LMT to Trace the Procedure of Relocation with Cell/URA Update......................10-15 10.3.5 Elementary Procedures of Relocation with Cell/URA Update........................................................10-17 10.4 Relocation with Hard Handover................................................................................................................10-25 10.4.1 Protocols Related to Relocation with Hard Handover.....................................................................10-26 10.4.2 Triggering Conditions of Relocation with Hard Handover..............................................................10-26 10.4.3 Signaling Procedure of a Successful Relocation with Hard Handover............................................10-26 10.4.4 Using the RNC LMT to Trace the Procedure of Relocation with Hard Handover..........................10-27 10.4.5 Elementary Procedures of Relocation with Hard Handover............................................................10-30 10.5 DSCR Procedure.......................................................................................................................................10-36 10.5.1 Protocols Related to the DSCR Procedure.......................................................................................10-36 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
Contents
10.5.2 Cause of Triggering the DSCR Procedure.......................................................................................10-37 10.5.3 Successful DSCR Procedure............................................................................................................10-37
11 Location Service Procedure..................................................................................................11-1

11.1 Positioning Methods....................................................................................................................................11-2 11.2 Positioning Based on CELLID+RTT..........................................................................................................11-2 11.2.1 Protocols Related to Positioning Based on CELLID+RTT...............................................................11-2 11.2.2 Triggering Conditions of Positioning Based on CELLID+RTT........................................................11-3 11.2.3 Signaling Procedure of Successful Positioning Based on CELLID+RTT.........................................11-3 11.2.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL .......................................................................................................................................................................11-3 11.2.5 Elementary Procedures of Positioning Based on CELLID+RTT......................................................11-5 11.3 Positioning Based on OTDOA-IPDL..........................................................................................................11-7 11.3.1 Protocols Related to Positioning Based on OTDOA-IPDL...............................................................11-7 11.3.2 Triggering Conditions of Positioning Based on OTDOA-IPDL........................................................11-8 11.3.3 Signaling Procedure of Successful Positioning Based on OTDOA-IPDL.........................................11-8 11.3.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL .......................................................................................................................................................................11-8 11.3.5 Elementary Procedures of Positioning Based on OTDOA-IPDL....................................................11-10 11.4 Positioning Based on A-GPS....................................................................................................................11-12 11.4.1 Protocols Related to Positioning Based on A-GPS..........................................................................11-12 11.4.2 Triggering Conditions of Positioning Based on A-GPS..................................................................11-12 11.4.3 Signaling Procedure of Successful Positioning Based on A-GPS...................................................11-13 11.4.4 Using the RNC LMT to Trace the Procedure of Positioning Based on A-GPS...............................11-13 11.4.5 Elementary Procedures of Positioning Based on A-GPS.................................................................11-14
Issue 01 (2009-03-25)
Figures
Figures
Figure 1-1 Signaling procedure of successful cell setup......................................................................................1-3 Figure 1-2 Example of Iub signaling tracing result..............................................................................................1-5 Figure 1-3 Example of Q.AAL2 protocol tracing result......................................................................................1-5 Figure 1-4 Resource status indication procedure.................................................................................................1-7 Figure 1-5 Resource audit procedure...................................................................................................................1-8 Figure 1-6 Cell setup procedure...........................................................................................................................1-9 Figure 1-7 Common transport channel setup procedure....................................................................................1-10 Figure 1-8 Iub user plane setup procedure.........................................................................................................1-11 Figure 1-9 System information update procedure..............................................................................................1-12 Figure 1-10 Physical shared channel reconfiguration procedure.......................................................................1-13 Figure 1-11 Common measurement initiation procedure...................................................................................1-14 Figure 2-1 Cell reconfiguration procedure...........................................................................................................2-2 Figure 2-2 Example of Iub signaling tracing result..............................................................................................2-3 Figure 3-1 Cell deletion procedure.......................................................................................................................3-2 Figure 3-2 Example of Iub signaling tracing result..............................................................................................3-3 Figure 4-1 Signaling procedure of a successful location update..........................................................................4-3 Figure 4-2 Example of Uu signaling tracing result..............................................................................................4-5 Figure 4-3 Example of Iub signaling tracing result..............................................................................................4-5 Figure 4-4 Example of Iu signaling tracing result................................................................................................4-5 Figure 4-5 RRC connection setup procedure on a DCH......................................................................................4-7 Figure 4-6 RRC connection setup procedure on a CCH......................................................................................4-8 Figure 4-7 RRC connection rejected procedure...................................................................................................4-8 Figure 4-8 Location update procedure.................................................................................................................4-9 Figure 4-9 Iu release procedure..........................................................................................................................4-10 Figure 4-10 RRC connection release procedure (from a DCH).........................................................................4-12 Figure 4-11 RRC connection release procedure (from a CCH).........................................................................4-13 Figure 5-1 Signaling procedure of a successful outgoing call.............................................................................5-3 Figure 5-2 Example of Uu signaling tracing result..............................................................................................5-6 Figure 5-3 Example of Iub signaling tracing result..............................................................................................5-7 Figure 5-4 Example of Iu signaling tracing result................................................................................................5-7 Figure 5-5 RRC connection setup procedure on a DCH......................................................................................5-9 Figure 5-6 RRC connection setup procedure on a CCH....................................................................................5-10 Figure 5-7 RRC connection rejected procedure.................................................................................................5-10 Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Figures
RAN Signalling Analysis Guide Figure 5-8 Signaling connection setup procedure..............................................................................................5-11
Figure 5-9 Authentication and security mode control procedure.......................................................................5-12 Figure 5-10 Call setup procedure (outgoing call)...............................................................................................5-14 Figure 5-11 Successful RAB setup procedure...................................................................................................5-15 Figure 5-12 Unsuccessful RAB setup procedure...............................................................................................5-16 Figure 5-13 Call release procedure (outgoing call)............................................................................................5-17 Figure 5-14 RRC connection release procedure (from a DCH).........................................................................5-18 Figure 5-15 RRC connection release procedure (from a CCH).........................................................................5-19 Figure 6-1 Signaling procedure of a successful incoming call.............................................................................6-3 Figure 6-2 Example of Uu signaling tracing result..............................................................................................6-6 Figure 6-3 Example of Iub signaling tracing result..............................................................................................6-7 Figure 6-4 Example of Iu signaling tracing result................................................................................................6-7 Figure 6-5 Paging procedure (for a UE that is in idle mode or in PCH state)......................................................6-8 Figure 6-6 Paging procedure (for a UE that is in CELL_DCH or CELL_FACH state)......................................6-9 Figure 6-7 RRC connection setup procedure on a DCH....................................................................................6-10 Figure 6-8 RRC connection setup procedure on a CCH....................................................................................6-11 Figure 6-9 RRC connection rejected procedure.................................................................................................6-11 Figure 6-10 Signaling connection setup procedure............................................................................................6-12 Figure 6-11 Authentication and security mode control procedure.....................................................................6-13 Figure 6-12 Call setup procedure (incoming call)..............................................................................................6-15 Figure 6-13 Successful RAB setup procedure...................................................................................................6-16 Figure 6-14 Unsuccessful RAB setup procedure...............................................................................................6-17 Figure 6-15 Call release procedure (incoming call)...........................................................................................6-18 Figure 6-16 RRC connection release procedure (from a DCH).........................................................................6-19 Figure 6-17 RRC connection release procedure (from a CCH).........................................................................6-20 Figure 7-1 Signaling procedure of a successful intra-frequency soft handover within a NodeB.........................7-3 Figure 7-2 Example of Uu signaling tracing result..............................................................................................7-4 Figure 7-3 Example of Iub signaling tracing result..............................................................................................7-5 Figure 7-4 Radio link addition procedure............................................................................................................7-6 Figure 7-5 Active set update procedure................................................................................................................7-7 Figure 7-6 Radio link deletion procedure.............................................................................................................7-8 Figure 7-7 Signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC .............................................................................................................................................................................7-10 Figure 7-8 Example of Uu signaling tracing result............................................................................................7-11 Figure 7-9 Example of Iub signaling tracing result............................................................................................7-11 Figure 7-10 Example of Q.AAL2 signaling tracing result.................................................................................7-12 Figure 7-11 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)................7-13 Figure 7-12 Iub user plane setup procedure.......................................................................................................7-14 Figure 7-13 Radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover).......7-15 Figure 7-14 Active set update procedure............................................................................................................7-15 Figure 7-15 Radio link deletion procedure.........................................................................................................7-16 Figure 7-16 Iub user plane release procedure.....................................................................................................7-17 Figure 7-17 Signaling procedure of a successful intra-frequency soft handover between RNCs......................7-19 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
Figures
Figure 7-18 Example of Uu signaling tracing result..........................................................................................7-20 Figure 7-19 Example of Iub signaling tracing result (source RNC)..................................................................7-21 Figure 7-20 Example of Iub signaling tracing result (target RNC)....................................................................7-21 Figure 7-21 Example of Iur signaling tracing result..........................................................................................7-21 Figure 7-22 Example of Q.AAL2 signaling tracing result.................................................................................7-21 Figure 7-23 Radio link setup procedure (inter-RNC handover).........................................................................7-23 Figure 7-24 Iub user plane setup procedure.......................................................................................................7-24 Figure 7-25 Radio link restoration procedure (inter-RNC handover)................................................................7-24 Figure 7-26 Iur user plane setup procedure........................................................................................................7-25 Figure 7-27 Active set update procedure............................................................................................................7-26 Figure 7-28 Radio link deletion procedure.........................................................................................................7-27 Figure 7-29 Iub user plane release procedure.....................................................................................................7-28 Figure 7-30 Iur user plane release procedure.....................................................................................................7-29 Figure 7-31 Signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC .............................................................................................................................................................................7-31 Figure 7-32 Example of Uu signaling tracing result..........................................................................................7-32 Figure 7-33 Example of Iub signaling tracing result..........................................................................................7-32 Figure 7-34 Example of Q.AAL2 signaling tracing result.................................................................................7-33 Figure 7-35 Radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover)................7-34 Figure 7-36 Iub user plane setup procedure.......................................................................................................7-35 Figure 7-37 Radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover).......7-36 Figure 7-38 Physical channel reconfiguration procedure...................................................................................7-36 Figure 7-39 Radio link deletion procedure.........................................................................................................7-37 Figure 7-40 Iub user plane release procedure.....................................................................................................7-38 Figure 7-41 Signaling procedure of a successful intra-frequency hard handover between RNCs.....................7-40 Figure 7-42 Example of Uu signaling tracing result..........................................................................................7-41 Figure 7-43 Example of Iub signaling tracing result (source RNC)..................................................................7-42 Figure 7-44 Example of Iub signaling tracing result (target RNC)....................................................................7-42 Figure 7-45 Example of Iur signaling tracing result..........................................................................................7-42 Figure 7-46 Example of Q.AAL2 signaling tracing result.................................................................................7-42 Figure 7-47 Radio link setup procedure (inter-RNC handover).........................................................................7-44 Figure 7-48 Iub user plane setup procedure.......................................................................................................7-45 Figure 7-49 Radio link restoration procedure (inter-RNC handover)................................................................7-45 Figure 7-50 Iur user plane setup procedure........................................................................................................7-46 Figure 7-51 Physical channel reconfiguration procedure...................................................................................7-47 Figure 7-52 Radio link deletion procedure.........................................................................................................7-48 Figure 7-53 Iub user plane release procedure.....................................................................................................7-49 Figure 7-54 Iur user plane release procedure.....................................................................................................7-50 Figure 8-1 Signaling procedure of a successful inter-frequency handover between NodeBs in an RNC............8-4 Figure 8-2 Example of Uu signaling tracing result..............................................................................................8-5 Figure 8-3 Example of Iub signaling tracing result..............................................................................................8-5 Figure 8-4 Example of Q.AAL2 signaling tracing result.....................................................................................8-6 Figure 8-5 Radio link addition procedure............................................................................................................ 8-7 Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Figures
RAN Signalling Analysis Guide 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-21 Figure 8-23 Radio link deletion procedure.........................................................................................................8-22 Figure 8-24 Iub user plane release procedure.....................................................................................................8-23 Figure 8-25 Iur user plane release procedure.....................................................................................................8-24 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-4 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-12 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 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
Figures
Figure 9-23 SRNS context transfer procedure...................................................................................................9-24 Figure 9-24 Iu release procedure........................................................................................................................9-25 Figure 9-25 Radio link deletion procedure.........................................................................................................9-26 Figure 10-1 Signaling procedure of a successful static relocation.....................................................................10-3 Figure 10-2 Example of Uu signaling tracing result..........................................................................................10-5 Figure 10-3 Example of Iur signaling tracing on the SRNC..............................................................................10-5 Figure 10-4 Example of Iur signaling tracing on the DRNC.............................................................................10-5 Figure 10-5 Example of Iu signaling tracing on the SRNC...............................................................................10-6 Figure 10-6 Example of Iu signaling tracing on the DRNC...............................................................................10-6 Figure 10-7 Relocation preparation procedure...................................................................................................10-7 Figure 10-8 Relocation resource allocation procedure.......................................................................................10-8 Figure 10-9 Relocation commit procedure (static relocation or relocation with cell/URA update)..................10-9 Figure 10-10 UTRAN mobility information procedure...................................................................................10-10 Figure 10-11 UE capability enquiry procedure................................................................................................10-11 Figure 10-12 Iu release procedure....................................................................................................................10-12 Figure 10-13 Signaling procedure of a successful relocation with cell/URA update......................................10-14 Figure 10-14 Example of Uu signaling tracing for the relocation with cell update.........................................10-16 Figure 10-15 Example of Iur signaling tracing on the SRNC..........................................................................10-17 Figure 10-16 Example of Iur signaling tracing on the DRNC.........................................................................10-17 Figure 10-17 Example of Iu signaling tracing on the SRNC...........................................................................10-17 Figure 10-18 Example of Iu signaling tracing on the DRNC...........................................................................10-17 Figure 10-19 Relocation preparation procedure...............................................................................................10-19 Figure 10-20 Relocation resource allocation procedure...................................................................................10-20 Figure 10-21 Cell update procedure.................................................................................................................10-21 Figure 10-22 URA update procedure...............................................................................................................10-22 Figure 10-23 Relocation commit procedure (static relocation or relocation with cell/URA update)..............10-23 Figure 10-24 UE capability enquiry procedure................................................................................................10-24 Figure 10-25 Iu release procedure....................................................................................................................10-25 Figure 10-26 Signaling procedure of a successful relocation with hard handover..........................................10-27 Figure 10-27 Example of Uu signaling tracing on the SRNC..........................................................................10-29 Figure 10-28 Example of Uu signaling tracing on the DRNC.........................................................................10-29 Figure 10-29 Example of Iu signaling tracing on the SRNC...........................................................................10-29 Figure 10-30 Example of Iu signaling tracing on the DRNC...........................................................................10-30 Figure 10-31 Relocation preparation procedure...............................................................................................10-31 Figure 10-32 Relocation resource allocation procedure...................................................................................10-32 Figure 10-33 Relocation commit procedure (relocation with hard handover).................................................10-33 Figure 10-34 Physical channel reconfiguration procedure...............................................................................10-34 Figure 10-35 UE capability enquiry procedure................................................................................................10-35 Figure 10-36 Iu release procedure....................................................................................................................10-36 Figure 10-37 Successful DSCR procedure.......................................................................................................10-37 Figure 11-1 Signaling procedure of successful positioning based on CELLID+RTT.......................................11-3 Figure 11-2 Example of CDT tracing result.......................................................................................................11-4 Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Figures
RAN Signalling Analysis Guide Figure 11-3 UE measurement procedure............................................................................................................11-5 Figure 11-4 RTT measurement procedure.........................................................................................................11-6
Figure 11-5 Signaling procedure of successful positioning based on OTDOA-IPDL.......................................11-8 Figure 11-6 Example of CDT tracing result.......................................................................................................11-9 Figure 11-7 UE measurement procedure..........................................................................................................11-10 Figure 11-8 RTT measurement procedure.......................................................................................................11-11 Figure 11-9 Signaling procedure of successful positioning based on A-GPS.................................................11-13 Figure 11-10 Example of CDT tracing result...................................................................................................11-14 Figure 11-11 UE measurement procedure........................................................................................................11-15
xii
Issue 01 (2009-03-25)
Tables
Tables
Table 1-1 Triggering conditions of cell setup......................................................................................................1-2 Table 1-2 Messages to be traced...........................................................................................................................1-4 Table 2-1 Messages to be traced...........................................................................................................................2-3 Table 3-1 Messages to be traced...........................................................................................................................3-3 Table 4-1 Messages to be traced...........................................................................................................................4-4 Table 5-1 Messages to be traced...........................................................................................................................5-4 Table 6-1 Messages to be traced...........................................................................................................................6-4 Table 7-1 Types of intra-frequency handover......................................................................................................7-2 Table 7-2 Messages to be traced...........................................................................................................................7-4 Table 7-3 Messages to be traced.........................................................................................................................7-11 Table 7-4 Messages to be traced.........................................................................................................................7-20 Table 7-5 Messages to be traced.........................................................................................................................7-32 Table 7-6 Messages to be traced.........................................................................................................................7-41 Table 8-1 Types of inter-frequency handover......................................................................................................8-2 Table 8-2 Messages to be traced...........................................................................................................................8-5 Table 8-3 Messages to be traced.........................................................................................................................8-15 Table 9-1 Messages to be traced...........................................................................................................................9-4 Table 9-2 Messages to be traced.........................................................................................................................9-11 Table 9-3 Messages to be traced.........................................................................................................................9-21 Table 10-1 Messages to be traced on the SRNC................................................................................................10-4 Table 10-2 Messages to be traced on the DRNC................................................................................................10-4 Table 10-3 Messages to be traced on the SRNC..............................................................................................10-15 Table 10-4 Messages to be traced on the DRNC..............................................................................................10-15 Table 10-5 Messages to be traced on the SRNC..............................................................................................10-28 Table 10-6 Messages to be traced on the DRNC..............................................................................................10-28 Table 11-1 Messages to be traced.......................................................................................................................11-4 Table 11-2 Messages to be traced.......................................................................................................................11-9 Table 11-3 Messages to be traced.....................................................................................................................11-14
Issue 01 (2009-03-25)
xiii
About This Document
About This Document
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 LMT.
Version
The following table lists the product versions related to this document. Product Name RNC Version V100R011 V200R011 NodeB V100R011 V200R011
Intended Audience
This document is intended for:
l l
Field engineers System engineers
Organization
1 Cell Setup Procedure 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. 2 Cell Reconfiguration 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.
Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1
About This Document
3 Cell Deletion Procedure 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. 4 Location Update Procedure 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. 5 Outgoing Call Procedure The outgoing call procedure is performed for a UE to call another terminal, such as a Public Switched Telephony Network (PSTN) terminal. This 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. 6 Incoming Call Procedure 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. 7 Intra-Frequency Handover Procedure The intra-frequency handover procedure is performed to hand over a UE from the WCDMA cell that it camps on to an 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. 8 Inter-Frequency Handover Procedure The inter-frequency handover procedure is performed to hand over a UE from the WCDMA cell that it camps on to an 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. 9 Inter-RAT Handover Procedure The inter-RAT handover procedure is performed to hand over a UE from a WCDMA cell to a GSM cell or the other way round. This 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. 10 SRNS Relocation Procedure
2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
About This Document
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. 11 Location Service Procedure 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
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
3
Issue 01 (2009-03-25)
About This Document
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder .
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows.
4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
About This Document
Action Click Double-click Drag
Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 01 (2009-03-25)
1 Cell Setup Procedure
1
About This Chapter
Cell Setup Procedure
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. 1.1 Protocols Related to Cell Setup The cell setup procedure complies with some 3GPP TS25 protocols and an ITU-T protocol. 1.2 Triggering Conditions of Cell Setup Cell setup can be triggered either through execution of an MML command or with a resource audit response from the NodeB. 1.3 Signaling Procedure of Successful Cell Setup This describes the signaling procedure of successful cell setup. For the messages related to cell setup failures, refer to the elementary procedures. 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. 1.5 Elementary Procedures of Cell Setup This describes the elementary procedures of cell setup in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Issue 01 (2009-03-25)
1-1
1.1 Protocols Related to Cell Setup

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

Cell setup can be triggered either through execution of an MML command or with a resource audit response from the NodeB. Table 1-1 describes the two triggering conditions. Table 1-1 Triggering conditions of cell setup Triggering Condition Cell setup is initiated by the RNC LMT. The CRNC receives a resource audit response from the NodeB. Description Run the ACT CELL command on the RNC LMT in online mode. After receiving the resource audit response from the NodeB, the CRNC sends a cell setup request to the NodeB if the cell setup requirements are fulfilled. Feature The resource audit procedure is excluded from cell setup. The resource audit procedure is involved in cell setup.
1.3 Signaling Procedure of Successful Cell Setup

This describes the signaling procedure of successful cell setup. For the messages related to cell setup failures, refer to the elementary procedures. Figure 1-1 shows the signaling procedure of successful cell setup.
1-2
Issue 01 (2009-03-25)
Figure 1-1 Signaling procedure of successful cell setup
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. 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. 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 l
The RNC LMT works properly. 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.
Issue 01 (2009-03-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
Table 1-2 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT NBAP_AUDIT_REQ NBAP_AUDIT_RSP NBAP_AUDIT_FAIL NBAP_CELL_SETUP_REQ NBAP_CELL_SETUP_RSP NBAP_CELL_SETUP_FAIL NBAP_CELL_DEL_REQ NBAP_CELL_DEL_RSP NBAP_COMM_TRANSP_C H_SETUP_REQ NBAP_COMM_TRANSP_C H_SETUP_RSP NBAP_COMM_TRANSP_C H_SETUP_FAIL Iub NBAP_SYS_INFO_UPDATE _REQ NBAP_SYS_INFO_UPDATE _RSP NBAP_SYS_INFO_UPDATE _FAIL NBAP_PSCH_RECFG_REQ NBAP_PSCH_RECFG_RSP NBAP_PSCH_RECFG_FAIL NBAP_COMM_MEAS_INI_ REQ NBAP_COMM_MEAS_INI_ RSP NBAP_COMM_MEAS_INI_ FAIL Message Name in Protocols AUDIT REQUEST AUDIT RESPONSE AUDIT FAILURE CELL SETUP REQUEST CELL SETUP RESPONSE CELL SETUP FAILURE CELL DELETION REQUEST CELL DELETION RESPONSE COMMON TRANSPORT CHANNEL SETUP REQUEST COMMON TRANSPORT CHANNEL SETUP RESPONSE COMMON TRANSPORT CHANNEL SETUP FAILURE SYSTEM INFORMATION UPDATE REQUEST SYSTEM INFORMATION UPDATE RESPONSE SYSTEM INFORMATION UPDATE FAILURE PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE COMMON MEASUREMENT INITIATION REQUEST COMMON MEASUREMENT INITIATION RESPONSE COMMON MEASUREMENT INITIATION FAILURE
1-4
Issue 01 (2009-03-25)
Interface and Protocol to Be Traced
Message Name on the LMT NBAP_COMM_MEAS_RPR T
Message Name in Protocols
COMMON MEASUREMENT REPORT
Q.AAL2
No message name needs to be specified.
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. Figure 1-2 Example of Iub signaling tracing result
In practice, the messages transmitted during cell setup depend on the configured data. In this example, an HSDPA cell is set up. During the cell setup, the common transport channel setup procedure is performed to set up a Secondary Common Control Physical Channel (S-CCPCH), a Physical Random Access Channel (PRACH), a Paging Indicator Channel (PICH), and an Acquisition Indicator Channel (AICH). The S-CCPCH carries two Forward Access Channels (FACHs) and a Paging Channel (PCH). The PRACH carries a Random Access Channel (RACH).
Step 2 Create a Q.AAL2 tracing task by referring to Creating an RNC Tracing Task. Figure 1-3 shows an example of Q.AAL2 protocol tracing result. Figure 1-3 Example of Q.AAL2 protocol tracing result
Issue 01 (2009-03-25)
1-5
----End
1.5 Elementary Procedures of Cell Setup

This describes the elementary procedures of cell setup in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 1.5.1 Resource Status Indication Procedure The NodeB performs the resource status indication procedure to report its physical resources to the Control RNC (CRNC). 1.5.2 Resource Audit Procedure The CRNC performs the resource audit procedure to audit the configuration and status of the logical resources in the NodeB. The audit may let the CRNC know the logical resources of the NodeB and re-synchronize its resources with those of the NodeB. 1.5.3 Cell Setup Procedure The cell setup procedure is performed to set up a cell in the NodeB. 1.5.4 Common Transport Channel Setup Procedure The common transport channel setup procedure is performed to establish the necessary resources in the NodeB, regarding the following channels: S-CCPCH, PICH, PRACH, AICH, FACH, PCH, and RACH. 1.5.5 Iub User Plane Setup Procedure The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface. 1.5.6 System Information Update Procedure The system information update procedure is performed for the NodeB to schedule and update the system information segments, which are broadcast on the Broadcast Control Channel (BCCH), according to the parameters in the SYSTEM INFORMATION UPDATE REQUEST message. 1.5.7 Physical Shared Channel Reconfiguration Procedure The physical shared channel reconfiguration procedure is performed for the NodeB to reconfigure the physical channels according to the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message sent from the CRNC. 1.5.8 Common Measurement Initiation Procedure The common measurement initiation procedure is performed for the CRNC to request the initiation of measurements on common resources in a NodeB. The NodeB then initiates the requested measurements according to the parameters given in the COMMON MEASUREMENT INITIATION REQUEST message sent from the CRNC.
1.5.1 Resource Status Indication Procedure

The NodeB performs the resource status indication procedure to report its physical resources to the Control RNC (CRNC).
Triggering Conditions
The NodeB triggers the procedure in one of the following conditions:
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)

l l l l
A local cell is added to the NodeB. A local cell is deleted from the NodeB. The capabilities of a local cell change at the NodeB. A cell changes its capability or resource operational state or both capability and resource operational state at the NodeB. Common physical channels or common transport channels or both common physical channels and common transport channels change their capabilities at the NodeB. A Communication Control Port (CCP) changes its resource operational state at the NodeB. A local cell group changes its resource capability at the NodeB.
l l
Procedure
Figure 1-4 shows the resource status indication procedure. Figure 1-4 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.
1.5.2 Resource Audit Procedure

The CRNC performs the resource audit procedure to audit the configuration and status of the logical resources in the NodeB. The audit may let the CRNC know the logical resources of the NodeB and re-synchronize its resources with those of the NodeB.
The CRNC receives a RESOURCE STATUS INDICATION message from the NodeB.
Issue 01 (2009-03-25)
1-7
Procedure
Figure 1-5 shows the resource audit procedure. Figure 1-5 Resource audit procedure
The procedure shown in Figure 1-5 is described as follows: 1. 2. The CRNC sends an AUDIT REQUEST message to the NodeB through the NCP to initiate the resource audit procedure. The NodeB sends a response message to the CRNC through the NCP.
l
If the audit is successful, the NodeB sends an AUDIT RESPONSE message. The AUDIT RESPONSE message contains information about common physical channels of the logical cell, CCP, local cell, and local cell group. The information about local cell and local cell group is the abstraction of the physical resources of the NodeB. In this way, the CRNC can allocate the logical resources of the cell according to the abstract data.
If the audit fails, the NodeB sends an AUDIT FAILURE message.
NOTE
A complete audit of a NodeB can be performed by one or more audit procedures. Each procedure carries an audit sequence number.
1.5.3 Cell Setup Procedure

The cell setup procedure is performed to set up a cell in the NodeB.
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 l l l
Downlink power range Minimum spreading factor HSDPA cell capability of the NodeB High Speed Downlink Shared Channel (HS-DSCH) resource information, which is used to set up an HSDPA cell Common transport channel and physical channel information CCP and NCP information
l l
Procedure
Figure 1-6 shows the cell setup procedure. Figure 1-6 Cell setup procedure
The procedure shown in Figure 1-6 is described as follows: 1. 2. The CRNC sends a CELL SETUP REQUEST message to the NodeB through the NCP. The NodeB then sets up a new cell according to the parameters given in the message. The NodeB sends a response message to the CRNC through the NCP.
l l
If the cell is set up, the NodeB sends a CELL SETUP RESPONSE message. If the cell fails to be set up, the NodeB sends a CELL SETUP FAILURE message.
1.5.4 Common Transport Channel Setup Procedure

The common transport channel setup procedure is performed to establish the necessary resources in the NodeB, regarding the following channels: S-CCPCH, PICH, PRACH, AICH, FACH, PCH, and RACH.
The NodeB sends a CELL SETUP RESPONSE message to the CRNC.
Procedure
Figure 1-7 shows the common transport channel setup procedure. Figure 1-7 Common transport channel setup procedure
The procedure shown in Figure 1-7 is described as follows: 1. The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST message to the NodeB through the NCP. One message can be used to configure only one of the following combinations:
l l
One S-CCPCH and the related FACHs, PCH and PICH One PRACH and the related RACH and AICH If the common transport channels are set up, the NodeB sends a COMMON TRANSPORT CHANNEL SETUP RESPONSE message. If the common transport channels fail to be set up, the NodeB sends a COMMON TRANSPORT CHANNEL SETUP FAILURE message. At the same time, the cell deletion procedure is triggered.
2.
The NodeB sends a response message to the CRNC through the NCP.
l
1.5.5 Iub User Plane Setup Procedure

The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface.
The Iub user plane setup procedure can be triggered in one of the following conditions:
l l
The common transport channels are set up. The dedicated transport channels are set up.
Procedure
Figure 1-8 shows the Iub user plane setup procedure.
Figure 1-8 Iub user plane setup procedure
The procedure shown in Figure 1-8 is described as follows: 1. 2. The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message to the NodeB. 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. If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
1.5.6 System Information Update Procedure

The system information update procedure is performed for the NodeB to schedule and update the system information segments, which are broadcast on the Broadcast Control Channel (BCCH), according to the parameters in the SYSTEM INFORMATION UPDATE REQUEST message.
The system information update procedure can be triggered in one of the following conditions:
l l l
Physical shared channels are reconfigured. Cells are reconfigured. All common transport channels are set up.
Procedure
Figure 1-9 shows the system information update procedure.
Issue 01 (2009-03-25)
1-11
Figure 1-9 System information update procedure
The procedure shown in Figure 1-9 is described as follows: 1. The CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to the NodeB through the NCP. The message includes the system information that is broadcast in segments on the BCCH and the scheduling information of each segment. 2. 3. The NodeB schedules and updates the system information segments on the BCCH according to the parameters in the message. The NodeB sends a response message to the CRNC through the NCP.
l
If the system information is updated, the NodeB sends a SYSTEM INFORMATION UPDATE RESPONSE message. If the system information fails to be updated, the NodeB sends a SYSTEM INFORMATION UPDATE FAILURE message. At the same time, the cell deletion procedure is triggered.
1.5.7 Physical Shared Channel Reconfiguration Procedure

The physical shared channel reconfiguration procedure is performed for the NodeB to reconfigure the physical channels according to the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message sent from the CRNC.
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.
1-12
Issue 01 (2009-03-25)
Figure 1-10 Physical shared channel reconfiguration procedure
The procedure shown in Figure 1-10 is described as follows: 1. The CRNC sends a PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message to the NodeB through the NCP to initiate the reconfiguration of the resources on the HS-DSCH and Enhanced UL DCH (E-DCH). The NodeB sends a response message to the CRNC through the NCP.
l
2.
If the physical shared channels are reconfigured, the NodeB sends a PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. If the physical shared channels fail to be reconfigured, the NodeB sends a PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
1.5.8 Common Measurement Initiation Procedure

The common measurement initiation procedure is performed for the CRNC to request the initiation of measurements on common resources in a NodeB. The NodeB then initiates the requested measurements according to the parameters given in the COMMON MEASUREMENT INITIATION REQUEST message sent from the CRNC.
The cell is set up and activated.
Procedure
Figure 1-11 shows the common measurement initiation procedure.
Issue 01 (2009-03-25)
1-13
Figure 1-11 Common measurement initiation procedure
The procedure shown in Figure 1-11 is described as follows: 1. The CRNC sends a COMMON MEASUREMENT INITIATION REQUEST message to the NodeB through the NCP to initiate the common measurement initiation procedure. The message includes the measurement object type (such as cell and RACH), common measurement type (such as transmit carrier power and received total wide band power), and report characteristics (such as On-Demand report, periodic report, and event report). The NodeB initiates the requested measurement according to the parameters given in the message. The NodeB sends a response message to the CRNC through the NCP.
l
2. 3.
If the measurement requested by the CRNC is initiated, the NodeB sends a COMMON MEASUREMENT INITIATION RESPONSE message. If the measurement requested by the CRNC fails to be initiated, the NodeB sends a COMMON MEASUREMENT INITIATION FAILURE message.
1-14
Issue 01 (2009-03-25)
2 Cell Reconfiguration Procedure
2
About This Chapter
Cell Reconfiguration 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. 2.1 Protocols Related to Cell Reconfiguration The cell reconfiguration procedure complies with a 3GPP TS25 protocol. 2.2 Triggering Conditions of Cell Reconfiguration Cell reconfiguration is triggered when the parameters of the cell in the NodeB are modified on the RNC LMT. 2.3 Signaling Procedure of Cell Reconfiguration This describes the signaling procedure of cell reconfiguration. 2.4 Using the RNC LMT to Trace the Cell Reconfiguration Procedure The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell reconfiguration.
Issue 01 (2009-03-25)
2-1
2.1 Protocols Related to Cell Reconfiguration

The cell reconfiguration procedure complies with a 3GPP TS25 protocol. The compliance protocol is the 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signaling".
2.2 Triggering Conditions of Cell Reconfiguration

Cell reconfiguration is triggered when the parameters of the cell in the NodeB are modified on the RNC LMT. To modify parameters of the cell in the NodeB, run the MOD CELL command online on the RNC LMT.
2.3 Signaling Procedure of Cell Reconfiguration

This describes the signaling procedure of cell reconfiguration. Figure 2-1 shows the cell reconfiguration procedure. Figure 2-1 Cell reconfiguration procedure
The procedure shown in Figure 2-1 is described as follows: 1. The CRNC sends a CELL RECONFIGURATION REQUEST message to the NodeB through the NCP. The NodeB then reconfigures the cell according to the parameters given in the message. The NodeB sends a response message to the CRNC through the NCP.
l
2.
If the cell is reconfigured, the NodeB sends a CELL RECONFIGURATION RESPONSE message.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-03-25)
2-2

l
If the cell fails to be reconfigured, the NodeB sends a CELL RECONFIGURATION FAILURE message.
2.4 Using the RNC LMT to Trace the Cell Reconfiguration Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell reconfiguration.
Prerequisite
l l
Context
Table 2-1 lists the messages to be traced. Table 2-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols CELL RECONFIGURATION REQUEST CELL RECONFIGURATION RESPONSE CELL RECONFIGURATION FAILURE
NBAP_CELL_RECFG_REQ Iub NBAP_CELL_RECFG_RSP NBAP_CELL_RECFG_FAIL
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. Figure 2-2 Example of Iub signaling tracing result
----End
Issue 01 (2009-03-25)
2-3
3 Cell Deletion Procedure
3
About This Chapter
Cell Deletion Procedure
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. 3.1 Protocols Related to Cell Deletion The cell deletion procedure complies with a 3GPP TS25 protocol. 3.2 Triggering Conditions of Cell Deletion Cell deletion can be triggered in different conditions, for example, when the common transport channels fail to be set up. 3.3 Signaling Procedure of Cell Deletion This describes the signaling procedure of cell deletion. 3.4 Using the RNC LMT to Trace the Cell Deletion Procedure The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell deletion.
Issue 01 (2009-03-25)
3-1
3.1 Protocols Related to Cell Deletion

The cell deletion procedure complies with a 3GPP TS25 protocol. The compliance protocol is the 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling".
3.2 Triggering Conditions of Cell Deletion

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

This describes the signaling procedure of cell deletion. Figure 3-1 shows the cell deletion procedure. Figure 3-1 Cell deletion procedure
The procedure shown in Figure 3-1 is described as follows: 1.

3-2
The CRNC sends a CELL DELETION REQUEST message to the NodeB through the NCP.
2.
The NodeB performs the following operations:

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". Initiates release of the user plane transport bearers for the removed common and dedicated channels. Deletes all radio links and all NodeB communication contexts within the cell.
3.
When the cell is deleted, the NodeB sends a CELL DELETION RESPONSE message to the CRNC through the NCP. If the CELL DELETION REQUEST message includes a C-ID IE value that does not exist in the NodeB, the NodeB sends through the NCP to the CRNC the CELL DELETION RESPONSE message, in which the value of Criticality Diagnostics is "Not existing".
3.4 Using the RNC LMT to Trace the Cell Deletion Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of cell deletion.
Prerequisite
l l
Context
Table 3-1 lists the messages to be traced. Table 3-1 Messages to be traced Interface and Protocol to Be Traced Iub Message Name on the LMT NBAP_CELL_DEL_REQ NBAP_CELL_DEL_RSP Message Name in Protocols CELL DELETION REQUEST CELL DELETION RESPONSE
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. Figure 3-2 Example of Iub signaling tracing result
Issue 01 (2009-03-25)
3-3
----End
3-4
Issue 01 (2009-03-25)
4 Location Update Procedure
4
About This Chapter
Location Update Procedure
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. 4.1 Protocols Related to Location Update The location update procedure complies with some 3GPP TS25 protocols and an ITU-T protocol. 4.2 Triggering Conditions of Location Update Location update is triggered after the UE is powered on. 4.3 Signaling Procedure of a Successful Location Update This describes the signaling procedure of a successful location update. For the messages related to location update failures, refer to the elementary procedures. 4.4 Using the RNC LMT to Trace the Location Update Procedure The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a location update. 4.5 Elementary Procedures of Location Update This describes the elementary procedures of location update in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Issue 01 (2009-03-25)
4-1
4.1 Protocols Related to Location Update

The location update procedure complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
4.2 Triggering Conditions of Location Update

Location update is triggered after the UE is powered on. After being powered on, the UE searches for a cell and then receives broadcast messages. Then, the UE triggers the location update procedure.
4.3 Signaling Procedure of a Successful Location Update

This describes the signaling procedure of a successful location update. For the messages related to location update failures, refer to the elementary procedures. Figure 4-1 shows the signaling procedure of a successful location update.
4-2
Issue 01 (2009-03-25)
Figure 4-1 Signaling procedure of a successful location update
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. 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.
4.4 Using the RNC LMT to Trace the Location Update Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a location update.
Prerequisite
l l
Context
Table 4-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_RRC_CONNECT_REQ RRC_RRC_CONN_SETUP RRC_RRC_CONN_REJ RRC_RRC_CONNECT_SET UP_CMP Uu RRC_INIT_DIRECT_TRANS F RRC_DL_DIRECT_TRANSF RRC_UL_DIR_TRANSF RRC_RRC_CONN_REL RRC_RRC_CONN_REL_CM P NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RANAP_INITIAL_UE_MES SAGE RANAP_COMMON_ID Iu RANAP_DIRECT_TRANSFE R RANAP_IU_RELEASE_CO MMAND RANAP_IU_RELEASE_CO MPLETE Message Name in Protocols RRC CONNECTION REQUEST RRC CONNECTION SETUP RRC CONNECTION REJECT RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER DOWNLINK DIRECT TRANSFER UPLINK DIRECT TRANSFER RRC CONNECTION RELEASE RRC CONNECTION RELEASE COMPLETE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE INITIAL UE MESSAGE COMMON ID DIRECT TRANSFER IU RELEASE COMMAND IU RELEASE COMPLETE
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.
4-4
Issue 01 (2009-03-25)
Figure 4-2 Example of Uu signaling tracing result
Step 3 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 4-4 shows an example of Iu signaling tracing result. Figure 4-4 Example of Iu signaling tracing result
----End
4.5 Elementary Procedures of Location Update

This describes the elementary procedures of location update in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 4.5.1 RRC Connection Setup Procedure The RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time. 4.5.2 Location Update Procedure The location update procedure is performed to update the location of a UE. 4.5.3 Iu Release Procedure The Iu release procedure is performed for the CN to release an Iu connection and all the UTRAN resources related only to that Iu connection. 4.5.4 RRC Connection Release Procedure The RRC connection release procedure is performed to release the signaling connection and all radio bearers between the UE and the UTRAN.
4.5.1 RRC Connection Setup Procedure

The RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time.
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.
4-6
Issue 01 (2009-03-25)
Figure 4-5 RRC connection setup procedure on a DCH
The procedure shown in Figure 4-5 is described as follows: 1. 2. The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH, requesting the establishment of an RRC connection. Based on the cause in the RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio Network Temporary Identity (RNTI), radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resources required for an RRC connection. The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources. The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required for the ATM-based Iub interface only. The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CCCH. The message contains the information about the DCH allocated by the SRNC. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates that the RRC connection setup procedure ends.
3. 4.
5. 6.
Figure 4-6 shows the procedure for setting up an RRC connection on a CCH.
Issue 01 (2009-03-25)
4-7
Figure 4-6 RRC connection setup procedure on a CCH
The procedure shown in Figure 4-6 is described as follows: 1. 2. The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH, requesting the establishment of an RRC connection. Based on the cause in the RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a CCH. The SRNC maps the logical channel of the UE onto a specific CCH in the cell. The SRNC then sends an RRC CONNECTION SETUP message to the UE through the downlink CCCH. The message contains the information about the CCH. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink CCCH. The message indicates that the RRC connection setup procedure ends.
3.
Figure 4-7 shows the RRC connection rejected procedure. Figure 4-7 RRC connection rejected procedure
The procedure shown in Figure 4-7 is described as follows: 1. 2. The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH, requesting the establishment of an RRC connection. The SRNC determines to reject the RRC connection request, based on a specific algorithm. Then, the SRNC sends an RRC CONNECTION REJECT message to the UE. The message indicates the reason for rejecting the RRC connection request.
4-8
4.5.2 Location Update Procedure

The location update procedure is performed to update the location of a UE.
An RRC connection is set up between the UE and the Serving RNC (SRNC).
Procedure
Figure 4-8 shows the location update procedure. Figure 4-8 Location update procedure
The procedure shown in Figure 4-8 is described as follows: 1. The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC connection. The message contains the Non Access Stratum (NAS) information to be sent to the CN by the UE. The SRNC sends an INITIAL UE MESSAGE to the CS service domain of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST and contains the UE information, such as the Temporary Mobile Subscriber Identity (TMSI), International Mobile Subscriber Identity (IMSI), and Location Area Identity (LAI). The SRNC sends an INITIAL UE MESSAGE to the PS service domain of the CN through the Iu interface for routing area update. The message indicates ATTACH REQUEST and contains the Routing Area Identity (RAI) 3. The CN updates the location area information of the UE and saves the new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRECT TRANSFER message to the SRNC. The message indicates LOCATION UPDATE ACCEPT and contains the TMSI that is assigned to the UE.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-9
2.
Issue 01 (2009-03-25)
For routing area update, the CN updates the routing area information of the UE and saves the new RAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRECT TRANSFER message to the SRNC. The message indicates ATTACH ACCEPT and contains the TMSI that is assigned to the UE 4. 5. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE receives the LOCATION UPDATE ACCEPT information and sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the information such as the NAS information and the CN ID. For routing area update, it is the ATTACH ACCEPT information that the UE receives. 6. 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 TMSI REALLOCATION COMPLETE. For routing area update, it is ATTACH COMPLETE that the DIRECT TRANSFER message indicates.
4.5.3 Iu Release Procedure

The Iu release procedure is performed for the CN to release an Iu connection and all the UTRAN resources related only to that Iu connection.
The Iu release procedure can be triggered in one of the following conditions:
l l l l
The transaction between the UE and the CN is complete. The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST message. The Serving Radio Network Subsystem (SRNS) is relocated. The SRNS relocation is canceled after a relocation resource allocation procedure is complete.
Procedure
Figure 4-9 shows the Iu release procedure. Figure 4-9 Iu release procedure
4-10
Issue 01 (2009-03-25)
The procedure shown in Figure 4-9 is described as follows: 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.
4.5.4 RRC Connection Release Procedure

The RRC connection release procedure is performed to release the signaling connection and all radio bearers between the UE and the UTRAN.
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.
I. Releasing an RRC Connection from a DCH Figure 4-10 shows the procedure for releasing an RRC connection from a DCH.
Issue 01 (2009-03-25)
4-11
Figure 4-10 RRC connection release procedure (from a DCH)
The procedure shown in Figure 4-10 is described as follows: 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. 3. 4. 5.
The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC. The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, requesting the NodeB to delete the radio link resources in the NodeB. After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE message to the SRNC. (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.
4-12
Issue 01 (2009-03-25)
Figure 4-11 RRC connection release procedure (from a CCH)
The procedure shown in Figure 4-11 is described as follows: 1. 2. The SRNC sends an RRC CONNECTION RELEASE message to the UE through the CCCH. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
Issue 01 (2009-03-25)
4-13
5 Outgoing Call Procedure
5
About This Chapter
Outgoing Call Procedure
The outgoing call procedure is performed for a UE to call another terminal, such as a Public Switched Telephony Network (PSTN) terminal. This 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. 5.1 Protocols Related to an Outgoing Call The outgoing call procedure complies with some 3GPP TS25 protocols and an ITU-T protocol. 5.2 Triggering Conditions of an Outgoing Call An outgoing call is made by a UE when the UE calls another terminal. 5.3 Signaling Procedure of a Successful Outgoing Call This describes the signaling procedure of a successful outgoing call. For the messages related to outgoing call failures, refer to the elementary procedures. 5.4 Using the RNC LMT to Trace the Outgoing Call Procedure The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an outgoing call. 5.5 Elementary Procedures of an Outgoing Call This describes the elementary procedures of an outgoing call in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Issue 01 (2009-03-25)
5-1
5.1 Protocols Related to an Outgoing Call

The outgoing call procedure complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
5.2 Triggering Conditions of an Outgoing Call

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

This describes the signaling procedure of a successful outgoing call. For the messages related to outgoing call failures, refer to the elementary procedures. Figure 5-1 shows the signaling procedure of a successful outgoing call.
5-2
Issue 01 (2009-03-25)
Figure 5-1 Signaling procedure of a successful outgoing call
Issue 01 (2009-03-25)
5-3
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. 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. 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.
5.4 Using the RNC LMT to Trace the Outgoing Call Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an outgoing call.
Prerequisite
l l
Context
Table 5-1 lists the messages to be traced. Table 5-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_RRC_CONNECT_REQ RRC_RRC_CONN_SETUP RRC_RRC_CONN_REJ RRC_RRC_CONNECT_SET UP_CMP Uu RRC_INIT_DIRECT_TRANS F RRC_DL_DIRECT_TRANSF RRC_UL_DIR_TRANSF RRC_SECURITY_MODE_C MD RRC_SECURITY_MODE_C MP
5-4
Message Name in Protocols RRC CONNECTION REQUEST RRC CONNECTION SETUP RRC CONNECTION REJECT RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER DOWNLINK DIRECT TRANSFER UPLINK DIRECT TRANSFER SECURITY MODE COMMAND SECURITY MODE COMPLETE
Issue 01 (2009-03-25)
Message Name on the LMT RRC_SECURITY_MODE_F AIL RRC_RB_SETUP RRC_RB_SETUP_CMP RRC_RB_SETUP_FAIL RRC_RRC_CONN_REL RRC_RRC_CONN_REL_CM P NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_RECFG_PREP NBAP_RL_RECFG_REDAY
SECURITY MODE FAILURE RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE RADIO BEARER SETUP FAILURE RRC CONNECTION RELEASE RRC CONNECTION RELEASE COMPLETE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK RECONFIGURATION PREPARE RADIO LINK RECONFIGURATION READY RADIO LINK RECONFIGURATION FAILURE RADIO LINK RECONFIGURATION COMMIT RADIO LINK RECONFIGURATION CANCEL RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE INITIAL UE MESSAGE COMMON ID DIRECT TRANSFER SECURITY MODE COMMAND SECURITY MODE COMPLETE
Iub NBAP_RL_RECFG_FAIL NBAP_RL_RECFG_COMMI T NBAP_RL_RECFG_CANCE L NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RANAP_INITIAL_UE_MES SAGE RANAP_COMMON_ID Iu RANAP_DIRECT_TRANSFE R RANAP_SECURITY_MODE _COMMAND RANAP_SECURITY_MODE _COMPLETE
Issue 01 (2009-03-25)
5-5
Message Name on the LMT RANAP_SECURITY_MODE _REJ RANAP_RAB_ASSIGNMEN T_REQ RANAP_RAB_ASSIGNMEN T_RESP RANAP_IU_RELEASE_CO MMAND RANAP_IU_RELEASE_CO MPLETE
SECURITY MODE REJECT RAB ASSIGNMENT REQUEST RAB ASSIGNMENT RESPONSE IU RELEASE COMMAND IU RELEASE COMPLETE
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. Figure 5-2 Example of Uu signaling tracing result
As shown in Figure 5-2, multiple RRC_UL_DIR_TRANSF messages and RRC_DL_DIRECT_TRANSF messages are traced. That is because the UE and the RNC exchange signaling several times during the outgoing call procedure. The RRC_UL_DIR_TRANSF messages have different contents, and so do the RRC_DL_DIRECT_TRANSF messages.
Step 2 Create an Iub tracing task by referring to Creating an RNC Tracing Task. Figure 5-3 shows an example of Iub signaling tracing result.
Figure 5-3 Example of Iub signaling tracing result
As shown in Figure 5-4, multiple RANAP_DIRECT_TRANSFER messages are traced. That is because the RNC and the CN exchange signaling several times during the outgoing call procedure. The RANAP_DIRECT_TRANSFER messages have different contents.
----End
5.5 Elementary Procedures of an Outgoing Call

This describes the elementary procedures of an outgoing call in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 5.5.1 RRC Connection Setup Procedure The RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time. 5.5.2 Signaling Connection Setup Procedure (Outgoing Call)
The signaling connection setup procedure is performed to exchange the NAS information between the UE and the CN. The NAS information is related to authentication, service request, connection setup, and so on. 5.5.3 Authentication and Security Mode Control Procedure The authentication and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signaling. 5.5.4 Call Setup Procedure (Outgoing Call) The call setup procedure is performed to set up a call. 5.5.5 RAB Setup Procedure The RAB setup procedure is performed to set up a user plane bearer. 5.5.6 Call Release Procedure (Outgoing Call) The call release procedure is performed to release services and resources after a call ends. 5.5.7 RRC Connection Release Procedure The RRC connection release procedure is performed to release the signaling connection and all radio bearers between the UE and the UTRAN.

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.
5-8
Issue 01 (2009-03-25)
Figure 5-5 RRC connection setup procedure on a DCH
3. 4.
5. 6.
Issue 01 (2009-03-25)
5-9
3.
5-10
5.5.2 Signaling Connection Setup Procedure (Outgoing Call)

The signaling connection setup procedure is performed to exchange the NAS information between the UE and the CN. The NAS information is related to authentication, service request, connection setup, and so on.
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 5-8 shows the signaling connection setup procedure. Figure 5-8 Signaling connection setup procedure
The procedure shown in Figure 5-8 is described as follows: 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. 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. The CN sends a response message to the SRNC.
l
2.
3.
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. 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.
Issue 01 (2009-03-25)
5-11
5.5.3 Authentication and Security Mode Control Procedure

The authentication and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signaling.
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. Figure 5-9 Authentication and security mode control procedure
The procedure shown in Figure 5-9 is described as follows: 1. 2. 3. 4. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
5-12
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. 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. The UE sends a response message to the SRNC.
l
6. 7.
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. 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.
5.5.4 Call Setup Procedure (Outgoing Call)

The call setup procedure is performed to set up a call.
The UE initiates a call.
Procedure
Figure 5-10 shows the call setup procedure.
Issue 01 (2009-03-25)
5-13
Figure 5-10 Call setup procedure (outgoing call)
The procedure shown in Figure 5-10 is described as follows: 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. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message. 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. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. A Radio Access Bearer (RAB) is set up. For details, refer to 5.5.5 RAB Setup Procedure. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC. The message indicates ALERTING. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CONNECT, which means that the called party has answered the call. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
2. 3.
4. 5. 6. 7. 8. 9.
5-14
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.
5.5.5 RAB Setup Procedure

The RAB setup procedure is performed to set up a user plane bearer.
A call is set up.
Procedure
I. Setting Up an RAB Successfully Figure 5-11 shows the successful RAB setup procedure. Figure 5-11 Successful RAB setup procedure
The procedure shown in Figure 5-11 is described as follows: 1. 2. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB setup procedure. (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.
Issue 01 (2009-03-25)
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. The NodeB allocates the associated resources and then sends a RADIO LINK RECONFIGURATION READY message to the SRNC. (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. The SRNC sends a RADIO BEARER SETUP message to the UE. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB is set up.
4. 5.
6. 7. 8. 9.
II. Failing to Set Up an RAB Figure 5-12 shows the unsuccessful RAB setup procedure. Figure 5-12 Unsuccessful RAB setup procedure
The procedure shown in Figure 5-12 is described as follows: 1. 2. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB setup procedure. 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.
5.5.6 Call Release Procedure (Outgoing Call)

The call release procedure is performed to release services and resources after a call ends.
A call ends and the calling party hangs up.
Procedure
Figure 5-13 shows the call release procedure. Figure 5-13 Call release procedure (outgoing call)
The procedure shown in Figure 5-13 is described as follows: 1. 2. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN that the UE has hanged up. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELEASE to request release of the call. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE. The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interface. The message indicates the reason for the Iu release. (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. The SRNC sends an IU RELEASE COMPLETE message to the CN.
3. 4. 5. 6. 7. 8. 9.

Procedure
NOTE
I. Releasing an RRC Connection from a DCH Figure 5-14 shows the procedure for releasing an RRC connection from a DCH. Figure 5-14 RRC connection release procedure (from a DCH)
NOTE
5-18
Issue 01 (2009-03-25)
2. 3. 4. 5.
II. Releasing an RRC Connection from a CCH Figure 5-15 shows the procedure for releasing an RRC connection from a CCH. Figure 5-15 RRC connection release procedure (from a CCH)
Issue 01 (2009-03-25)
5-19
6 Incoming Call Procedure
6
About This Chapter
Incoming Call Procedure
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. 6.1 Protocols Related to an Incoming Call The incoming call procedure complies with some 3GPP TS25 protocols. 6.2 Triggering Conditions of an Incoming Call An incoming call is received by a UE when a mobile phone or fixed-line phone calls the UE. 6.3 Signaling Procedure of a Successful Incoming Call This describes the signaling procedure of a successful incoming call. For the messages related to incoming call failures, refer to the elementary procedures. 6.4 Using the RNC LMT to Trace the Incoming Call Procedure The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an incoming call. 6.5 Elementary Procedures of an Incoming Call This describes the elementary procedures of an incoming call in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
Issue 01 (2009-03-25)
6-1
6.1 Protocols Related to an Incoming Call

The incoming call procedure complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling"
6.2 Triggering Conditions of an Incoming Call

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

This describes the signaling procedure of a successful incoming call. For the messages related to incoming call failures, refer to the elementary procedures. Figure 6-1 shows the signaling procedure of a successful incoming call.
6-2
Issue 01 (2009-03-25)
Figure 6-1 Signaling procedure of a successful incoming call
Issue 01 (2009-03-25)
6-3
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. 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. 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.
6.4 Using the RNC LMT to Trace the Incoming Call Procedure
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an incoming call.
Prerequisite
l l
Context
Table 6-1 lists the messages to be traced. Table 6-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_PAGING_TYPE1 RRC_PAGING_TYPE2 RRC_RRC_CONNECT_REQ RRC_RRC_CONN_SETUP RRC_RRC_CONN_REJ Uu RRC_RRC_CONNECT_SET UP_CMP RRC_INIT_DIRECT_TRANS F RRC_DL_DIRECT_TRANSF RRC_UL_DIR_TRANSF RRC_SECURITY_MODE_C MD
6-4
Message Name in Protocols PAGING TYPE 1 PAGING TYPE 2 RRC CONNECTION REQUEST RRC CONNECTION SETUP RRC CONNECTION REJECT RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER DOWNLINK DIRECT TRANSFER UPLINK DIRECT TRANSFER SECURITY MODE COMMAND
Issue 01 (2009-03-25)
Message Name on the LMT RRC_SECURITY_MODE_C MP RRC_SECURITY_MODE_F AIL RRC_RB_SETUP RRC_RB_SETUP_CMP RRC_RB_SETUP_FAIL RRC_RRC_CONN_REL RRC_RRC_CONN_REL_CM P NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_RECFG_PREP NBAP_RL_RECFG_REDAY
SECURITY MODE COMPLETE SECURITY MODE FAILURE RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE RADIO BEARER SETUP FAILURE RRC CONNECTION RELEASE RRC CONNECTION RELEASE COMPLETE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK RECONFIGURATION PREPARE RADIO LINK RECONFIGURATION READY RADIO LINK RECONFIGURATION FAILURE RADIO LINK RECONFIGURATION COMMIT RADIO LINK RECONFIGURATION CANCEL RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE PAGING INITIAL UE MESSAGE COMMON ID DIRECT TRANSFER
Iub NBAP_RL_RECFG_FAIL NBAP_RL_RECFG_COMMI T NBAP_RL_RECFG_CANCE L NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RANAP_PAGING RANAP_INITIAL_UE_MES SAGE RANAP_COMMON_ID RANAP_DIRECT_TRANSFE R
Iu
Issue 01 (2009-03-25)
6-5
Message Name on the LMT RANAP_SECURITY_MODE _COMMAND RANAP_SECURITY_MODE _COMPLETE RANAP_SECURITY_MODE _REJ RANAP_RAB_ASSIGNMEN T_REQ RANAP_RAB_ASSIGNMEN T_RESP RANAP_IU_RELEASE_CO MMAND RANAP_IU_RELEASE_CO MPLETE
SECURITY MODE COMMAND SECURITY MODE COMPLETE SECURITY MODE REJECT RAB ASSIGNMENT REQUEST RAB ASSIGNMENT RESPONSE IU RELEASE COMMAND IU RELEASE COMPLETE
Procedure
As shown in Figure 6-2, multiple RRC_UL_DIR_TRANSF messages and RRC_DL_DIRECT_TRANSF messages are traced. That is because the UE and the RNC exchange signaling several times during the incoming call procedure. The RRC_UL_DIR_TRANSF messages have different contents, and so do the RRC_DL_DIRECT_TRANSF messages.
As shown in Figure 6-4, multiple RANAP_DIRECT_TRANSFER messages are traced. That is because the RNC and the CN exchange signaling several times during the incoming call procedure. The RANAP_DIRECT_TRANSFER messages have different contents.
----End
6.5 Elementary Procedures of an Incoming Call

This describes the elementary procedures of an incoming call in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
6.5.1 Paging Procedure The paging procedure is performed when the CN calls a UE. 6.5.2 RRC Connection Setup Procedure The RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time. 6.5.3 Signaling Connection Setup Procedure (Incoming Call) The signaling connection setup procedure is performed to exchange the NAS information between the UE and the CN. The NAS information is related to authentication, service request, connection setup, and so on. 6.5.4 Authentication and Security Mode Control Procedure The authentication and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signaling. 6.5.5 Call Setup Procedure (Incoming Call) The call setup procedure is performed to set up a call. 6.5.6 RAB Setup Procedure The RAB setup procedure is performed to set up a user plane bearer. 6.5.7 Call Release Procedure (Incoming Call) The call release procedure is performed to release services and resources after a call ends. 6.5.8 RRC Connection Release Procedure The RRC connection release procedure is performed to release the signaling connection and all radio bearers between the UE and the UTRAN.
6.5.1 Paging Procedure

The paging procedure is performed when the CN calls a UE.
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)
6-8
Issue 01 (2009-03-25)
The procedure shown in Figure 6-5 is described as follows: 1. 2. The CN sends a PAGING message to the SRNC. The SRNC initiates the paging procedure by sending a PAGING TYPE 1 message to the UE through the Paging Control Channel (PCCH) on an appropriate occasion.
NOTE
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. Figure 6-6 Paging procedure (for a UE that is in CELL_DCH or CELL_FACH state)
The procedure shown in Figure 6-6 is described as follows: 1. 2. 3. The CN sends a PAGING message to the SRNC. The SRNC initiates the paging procedure by sending a PAGING TYPE 2 message to the UE through the DCCH. The UE receives the PAGNG TPYE 2 message, reads it, and then reports to the NAS the information such as the paging cause and the paging record type identifier.
The paging procedure ends.

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. Figure 6-7 RRC connection setup procedure on a DCH
3. 4.
5. 6.
3.
Issue 01 (2009-03-25)
6.5.3 Signaling Connection Setup Procedure (Incoming Call)

The signaling connection setup procedure is performed to exchange the NAS information between the UE and the CN. The NAS information is related to authentication, service request, connection setup, and so on.
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 6-10 shows the signaling connection setup procedure. Figure 6-10 Signaling connection setup procedure
The procedure shown in Figure 6-10 is described as follows: 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. The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends an INITIAL UE MESSAGE to the CN through the Iu interface. The INITIAL UE MESSAGE contains the NAS information to be sent to the CN by the UE. The content of the NAS information is PAGING RESPONSE. The CN sends a response message to the SRNC.
l
2.
3.
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. 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.
6-12
Issue 01 (2009-03-25)
6.5.4 Authentication and Security Mode Control Procedure

The authentication and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signaling.
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. Figure 6-11 Authentication and security mode control procedure
The procedure shown in Figure 6-11 is described as follows: 1. 2. 3. 4. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
Issue 01 (2009-03-25)
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. 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. The UE sends a response message to the SRNC.
l
6. 7.
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. 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.
6.5.5 Call Setup Procedure (Incoming Call)

The call setup procedure is performed to set up a call.
A UE receives a call from the CN.
Procedure
Figure 6-12 shows the call setup procedure.
6-14
Issue 01 (2009-03-25)
Figure 6-12 Call setup procedure (incoming call)
The procedure shown in Figure 6-12 is described as follows: 1. 2. 3. 4. 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. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 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. An RAB is set up. For details, refer to 6.5.6 RAB Setup Procedure. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 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. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 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.
5. 6. 7.
8. 9.
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.
6.5.6 RAB Setup Procedure

The RAB setup procedure is performed to set up a user plane bearer.
A call is set up.
Procedure
I. Setting Up an RAB Successfully Figure 6-13 shows the successful RAB setup procedure. Figure 6-13 Successful RAB setup procedure
The procedure shown in Figure 6-13 is described as follows: 1. 2. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB setup procedure. (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. 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.
3.
6-16
4. 5.
The NodeB allocates the associated resources and then sends a RADIO LINK RECONFIGURATION READY message to the SRNC. (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. The SRNC sends a RADIO BEARER SETUP message to the UE. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB is set up.
6. 7. 8. 9.
II. Failing to Set Up an RAB Figure 6-14 shows the unsuccessful RAB setup procedure. Figure 6-14 Unsuccessful RAB setup procedure
The procedure shown in Figure 6-14 is described as follows: 1. 2. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB setup procedure. 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.
6.5.7 Call Release Procedure (Incoming Call)

The call release procedure is performed to release services and resources after a call ends.
A call ends and the calling party hangs up.
Procedure
Figure 6-15 shows the call release procedure. Figure 6-15 Call release procedure (incoming call)
The procedure shown in Figure 6-15 is described as follows: 1. 2. 3. 4. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates DISCONNECT to inform the UE that the calling party has hanged up. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 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 RELEASE which requests release of the call. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELEASE COMPLETE. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interface. The message indicates the reason for the Iu release. (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. The SRNC sends an IU RELEASE COMPLETE message to the CN.
5. 6. 7. 8. 9.
6-18
Issue 01 (2009-03-25)

Procedure
NOTE
I. Releasing an RRC Connection from a DCH Figure 6-16 shows the procedure for releasing an RRC connection from a DCH. Figure 6-16 RRC connection release procedure (from a DCH)
Issue 01 (2009-03-25)

NOTE
2. 3. 4. 5.
II. Releasing an RRC Connection from a CCH Figure 6-17 shows the procedure for releasing an RRC connection from a CCH. Figure 6-17 RRC connection release procedure (from a CCH)
6-20
Issue 01 (2009-03-25)
7 Intra-Frequency Handover Procedure
Intra-Frequency Handover Procedure
About This Chapter

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. 7.1 Types of Intra-Frequency Handover Based on the connections between the UE and the network during the handover, intra-frequency handovers are categorized into two types: intra-frequency soft handover and intra-frequency hard handover. 7.2 Intra-Frequency Soft Handover Within a NodeB The procedure of intra-frequency soft handover within a NodeB is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by the same NodeB. 7.3 Intra-Frequency Soft Handover Between NodeBs in an RNC The procedure of intra-frequency soft handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another NodeB in the same RNC. 7.4 Intra-Frequency Soft Handover Between RNCs The procedure of intra-frequency soft handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another RNC. 7.5 Intra-Frequency Hard Handover Between NodeBs in an RNC The procedure of intra-frequency hard handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another NodeB in the same RNC. 7.6 Intra-Frequency Hard Handover Between RNCs The procedure of intra-frequency hard handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another RNC.
Issue 01 (2009-03-25)
7-1
7.1 Types of Intra-Frequency Handover

Based on the connections between the UE and the network during the handover, intra-frequency handovers are categorized into two types: intra-frequency soft handover and intra-frequency hard handover. Table 7-1 lists the types of intra-frequency handover. Table 7-1 Types of intra-frequency handover Type Subtype Intra-frequency soft handover within a NodeB, that is, softer handover Intra-frequency soft handover between NodeBs in an RNC Intra-frequency soft handover between RNCs Intrafrequency hard handover Intra-frequency hard handover between NodeBs in an RNC Intra-frequency hard handover between RNCs Description During an intra-frequency soft handover, the UE sets up a connection to the target cell before disconnecting from the source cell. During an intra-frequency hard handover, the UE disconnects from the source cell before setting up a connection towards the target cell. Intra-frequency soft handover is common, and intra-frequency hard handover is applied only in special scenarios, for example, a handover between two RNCs where no Iur interface exists.
Intrafrequency soft handover
7.2 Intra-Frequency Soft Handover Within a NodeB

The procedure of intra-frequency soft handover within a NodeB is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by the same NodeB. 7.2.1 Protocols Related to Intra-Frequency Soft Handover Within a NodeB The procedure of intra-frequency soft handover within a NodeB complies with some 3GPP TS25 protocols. 7.2.2 Triggering Conditions of Intra-Frequency Soft Handover Within a NodeB Intra-frequency soft handover within a NodeB is the intra-frequency soft handover where the source and target cells are controlled by the same NodeB. 7.2.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Within a NodeB This describes the signaling procedure of a successful intra-frequency soft handover within a NodeB. For the messages related to handover failures, refer to the elementary procedures. 7.2.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Within a NodeB The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover within a NodeB. 7.2.5 Elementary Procedures of Intra-Frequency Soft Handover Within a NodeB 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.
7.2.1 Protocols Related to Intra-Frequency Soft Handover Within a NodeB

The procedure of intra-frequency soft handover within a NodeB complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling"
7.2.2 Triggering Conditions of Intra-Frequency Soft Handover Within a NodeB

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

This describes the signaling procedure of a successful intra-frequency soft handover within a NodeB. For the messages related to handover failures, refer to the elementary procedures. Figure 7-1 shows the signaling procedure of a successful intra-frequency soft handover within a NodeB. Figure 7-1 Signaling procedure of a successful intra-frequency soft handover within a NodeB
Issue 01 (2009-03-25)
7-3
7.2.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Within a NodeB
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover within a NodeB.
Prerequisite
l l
Context
Table 7-2 lists the messages to be traced. Table 7-2 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_ACTIVE_SET_UPDAT E Uu RRC_ACTIVE_SET_UPDAT E_CMP RRC_ACTIVE_SET_UPDAT E_FAIL NBAP_RL_ADD_REQ NBAP_RL_ADD_RSP Iub NBAP_RL_ADD_FAIL NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP Message Name in Protocols
ACTIVE SET UPDATE ACTIVE SET UPDATE COMPLETE ACTIVE SET UPDATE FAILURE RADIO LINK ADDITION REQUEST RADIO LINK ADDITION RESPONSE RADIO LINK ADDITION FAILURE RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE
Procedure
7-4
Issue 01 (2009-03-25)
----End
7.2.5 Elementary Procedures of Intra-Frequency Soft Handover Within a NodeB

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. 7.2.5.1 Radio Link Addition Procedure The radio link addition procedure is performed to add one or more radio links towards a UE. 7.2.5.2 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.2.5.3 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.
Radio Link Addition Procedure

The radio link addition procedure is performed to add one or more radio links towards a UE.
The CRNC sends a RADIO LINK ADDITION REQUEST message.
Procedure
Figure 7-4 shows the radio link addition procedure.
Issue 01 (2009-03-25)
7-5
Figure 7-4 Radio link addition procedure
The procedure shown in Figure 7-4 is described as follows: 1. The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary resources and configures the new radio link or links according to the parameters given in the message. The NodeB sends a response message to the CRNC.
l
2.
If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK ADDITION REQUEST message and sends a RADIO LINK ADDITION RESPONSE message. If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the Cause IE.
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.
The active set update procedure can be triggered in either of the following conditions:
l l
Radio link addition Radio link deletion
Procedure
Figure 7-5 shows the active set update procedure.
7-6
Issue 01 (2009-03-25)
Figure 7-5 Active set update procedure
The procedure shown in Figure 7-5 is described as follows: 1. The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted, the message indicates radio link deletion. The UE adds or deletes the radio links according to the Radio Link Addition Information or Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message. The UE sends a response message to the SRNC.
l
2. 3.
If adding or deleting the radio links successfully, the UE sends an ACTIVE SET UPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM) Radio Link Control (RLC). If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the radio links specified by the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure

The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a UE.
The CRNC sends a RADIO LINK DELETION REQUEST message.
Procedure
Figure 7-6 shows the radio link deletion procedure.
Issue 01 (2009-03-25)
7-7
Figure 7-6 Radio link deletion procedure
The procedure shown in Figure 7-6 is described as follows: 1. 2. The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message. The NodeB sends a response message to the CRNC.
l
If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.
7.3 Intra-Frequency Soft Handover Between NodeBs in an RNC

The procedure of intra-frequency soft handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another NodeB in the same RNC. 7.3.1 Protocols Related to Intra-Frequency Soft Handover Between NodeBs in an RNC The procedure of intra-frequency soft handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. 7.3.2 Triggering Conditions of Intra-Frequency Soft Handover Between NodeBs in an RNC Intra-frequency soft handover between NodeBs in an RNC is the intra-frequency soft handover where the source and target cells are controlled by different NodeBs in an RNC. 7.3.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between NodeBs in an RNC This describes the signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. 7.3.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between NodeBs in an RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover between NodeBs in an RNC. 7.3.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC This describes the elementary procedures of intra-frequency soft handover between NodeBs in an RNC in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
7.3.1 Protocols Related to Intra-Frequency Soft Handover Between NodeBs in an RNC

The procedure of intra-frequency soft handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
7.3.2 Triggering Conditions of Intra-Frequency Soft Handover Between NodeBs in an RNC

Intra-frequency soft handover between NodeBs in an RNC is the intra-frequency soft handover where the source and target cells are controlled by different NodeBs in an RNC. The handover is triggered when the SRNC finds that another cell has higher signal quality than the serving cell or that the load of the serving cell is heavy.
7.3.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between NodeBs in an RNC
This describes the signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. Figure 7-7 shows the signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC.
Issue 01 (2009-03-25)
7-9
Figure 7-7 Signaling procedure of a successful intra-frequency soft handover between NodeBs in an RNC
l l
During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 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.
7.3.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between NodeBs in an RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover between NodeBs in an RNC.
Prerequisite
l l
Context
7-10
Issue 01 (2009-03-25)
Table 7-3 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_ACTIVE_SET_UPDAT E Uu RRC_ACTIVE_SET_UPDAT E_CMP RRC_ACTIVE_SET_UPDAT E_FAIL NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP Q.AAL2 No message name needs to be specified. Message Name in Protocols
ACTIVE SET UPDATE ACTIVE SET UPDATE COMPLETE ACTIVE SET UPDATE FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE
Procedure
Issue 01 (2009-03-25)
7-11
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. Figure 7-10 Example of Q.AAL2 signaling tracing result
----End
7.3.5 Elementary Procedures of Intra-Frequency Soft Handover Between NodeBs in an RNC

This describes the elementary procedures of intra-frequency soft handover between NodeBs in an RNC in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 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.
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.
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)
The procedure shown in Figure 7-11 is described as follows: 1. The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary resources and configures the new radio link according to the parameters given in the message. The NodeB sends a response message to the CRNC.
l
2.
If the radio link is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIO LINK SETUP RESPONSE message. If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.
Iub User Plane Setup Procedure

l l
Issue 01 (2009-03-25)
Procedure
Figure 7-12 shows the Iub user plane setup procedure. Figure 7-12 Iub user plane setup procedure
l
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.
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.

l l
Procedure
Figure 7-14 shows the active set update procedure. Figure 7-14 Active set update procedure
The procedure shown in Figure 7-14 is described as follows:

1.
The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted, the message indicates radio link deletion. The UE adds or deletes the radio links according to the Radio Link Addition Information or Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message. The UE sends a response message to the SRNC.
l
2. 3.

Procedure
Figure 7-15 shows the radio link deletion procedure. Figure 7-15 Radio link deletion procedure
l
If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.
7-16

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.
Iub User Plane Release Procedure

The Iub user plane release procedure is performed to release data transport bearers from the Iub interface.
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-16 Iub user plane release procedure
The procedure shown in Figure 7-16 is described as follows: 1. 2. The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST message to the NodeB. The NodeB uses the ALCAP protocol to send a response message to the CRNC.
l
If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release. If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASE CONFIRM message that indicates the failure cause.
7.4 Intra-Frequency Soft Handover Between RNCs

The procedure of intra-frequency soft handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another RNC. 7.4.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs
The procedure of intra-frequency soft handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. 7.4.2 Triggering Conditions of Intra-Frequency Soft Handover Between RNCs Intra-frequency soft handover between RNCs is the intra-frequency soft handover where the source and target cells are controlled by different RNCs. 7.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs This describes the signaling procedure of a successful intra-frequency soft handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. 7.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover between RNCs. 7.4.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs This describes the elementary procedures of intra-frequency soft handover between RNCs in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
7.4.1 Protocols Related to Intra-Frequency Soft Handover Between RNCs

The procedure of intra-frequency soft handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.423 "UTRAN Iur interface RNSAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
7.4.2 Triggering Conditions of Intra-Frequency Soft Handover Between RNCs

Intra-frequency soft handover between RNCs is the intra-frequency soft handover where the source and target cells are controlled by different RNCs. 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.
7.4.3 Signaling Procedure of a Successful Intra-Frequency Soft Handover Between RNCs

This describes the signaling procedure of a successful intra-frequency soft handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. Figure 7-17 shows the signaling procedure of a successful intra-frequency soft handover between RNCs.
7-18
Issue 01 (2009-03-25)
Figure 7-17 Signaling procedure of a successful intra-frequency soft handover between RNCs
l l
During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 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. 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.
7.4.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Soft Handover Between RNCs
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency soft handover between RNCs.
Prerequisite
l l
Context
Table 7-4 lists the messages to be traced. Table 7-4 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_ACTIVE_SET_UPDAT E Uu RRC_ACTIVE_SET_UPDAT E_CMP RRC_ACTIVE_SET_UPDAT E_FAIL NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RNSAP_RL_SETUP_REQ Iur RNSAP_RL_SETUP_RSP RNSAP_RL_SETUP_FAIL RNSAP_RL_RESTORE_IND Q.AAL2 No message name needs to be specified. Message Name in Protocols
ACTIVE SET UPDATE ACTIVE SET UPDATE COMPLETE ACTIVE SET UPDATE FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION
Procedure
7-20
Issue 01 (2009-03-25)
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-19 Example of Iub signaling tracing result (source RNC)
Figure 7-20 shows an example of Iub signaling tracing on the target RNC. Figure 7-20 Example of Iub signaling tracing result (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. Figure 7-21 Example of Iur signaling tracing result
----End
7.4.5 Elementary Procedures of Intra-Frequency Soft Handover Between RNCs

This describes the elementary procedures of intra-frequency soft handover between RNCs in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 7.4.5.1 Radio Link Setup Procedure (Inter-RNC Handover) The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE. 7.4.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.4.5.3 Radio Link Restoration Procedure (Inter-RNC Handover) The radio link restoration procedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved. 7.4.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.4.5.5 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.4.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.4.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.4.5.8 Iur User Plane Release Procedure The Iur user plane release procedure is performed to release data transport bearers from the Iur interface.
Radio Link Setup Procedure (Inter-RNC Handover)

The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE.
The SRNC sends a RADIO LINK SETUP REQUEST message.
Procedure
Figure 7-23 shows the radio link setup procedure for inter-RNC handover.
7-22
Issue 01 (2009-03-25)
Figure 7-23 Radio link setup procedure (inter-RNC handover)
The procedure shown in Figure 7-23 is described as follows: 1. 2. 3. 4. The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC. The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB. The NodeB reserves the necessary resources and configures the new radio link according to the parameters given in the message. 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. If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSE message. If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE message, indicating the failure cause.
5.
The DRNC reports the radio link setup result to the SRNC.
l

l l
Procedure
l l
Radio Link Restoration Procedure (Inter-RNC Handover)

The radio link restoration procedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.
Procedure
Figure 7-25 shows the radio link restoration procedure for inter-RNC handover. Figure 7-25 Radio link restoration procedure (inter-RNC handover)
7-24
Issue 01 (2009-03-25)
The procedure shown in Figure 7-25 is described as follows: 1. 2. After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the DRNC. The DRNC sends a RADIO LINK RESTORE INDICATION message to the SRNC.
Iur User Plane Setup Procedure

The Iur user plane setup procedure is performed to set up bearers for data transmission on the Iur interface.
The DCHs are set up.
Procedure
Figure 7-26 shows the Iur user plane setup procedure. Figure 7-26 Iur user plane setup procedure
The procedure shown in Figure 7-26 is described as follows: 1. 2. The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message to the DRNC. The DRNC uses the ALCAP protocol to send a response message to the SRNC.
l
If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISH CONFIRM message. If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLISH RELEASE CONFIRM message.

l l
Procedure
Figure 7-27 shows the active set update procedure. Figure 7-27 Active set update procedure
The procedure shown in Figure 7-27 is described as follows: 1. The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted, the message indicates radio link deletion. The UE adds or deletes the radio links according to the Radio Link Addition Information or Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message. The UE sends a response message to the SRNC.
l
2. 3.

Procedure
l

Procedure
Figure 7-29 shows the Iub user plane release procedure.
Issue 01 (2009-03-25)
7-27
Figure 7-29 Iub user plane release procedure
l
Iur User Plane Release Procedure

The Iur user plane release procedure is performed to release data transport bearers from the Iur interface.
The transport channels on the Iur user plane need to be removed.
Procedure
Figure 7-30 shows the Iur user plane release procedure.
7-28
Issue 01 (2009-03-25)
Figure 7-30 Iur user plane release procedure
The procedure shown in Figure 7-30 is described as follows: 1. 2. The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST message to the DRNC. The DRNC uses the ALCAP protocol to send a response message to the SRNC.
l
If the Iur data transport bearers are released, the DRNC sends a QAAL2 RELEASE CONFIRM message to confirm the release. If an Iur data transport bearer fails to be released, the DRNC sends a QAAL2 RELEASE CONFIRM message that indicates the failure cause.
7.5 Intra-Frequency Hard Handover Between NodeBs in an RNC

The procedure of intra-frequency hard handover between NodeBs in an RNC is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another NodeB in the same RNC. 7.5.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC The procedure of intra-frequency hard handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. 7.5.2 Triggering Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC Intra-frequency hard handover between NodeBs in an RNC is the intra-frequency hard handover where the source and target cells are controlled by different NodeBs in an RNC. 7.5.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC This describes the signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. 7.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in an RNC The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency hard handover between NodeBs in an RNC.
7.5.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC 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.
7.5.1 Protocols Related to Intra-Frequency Hard Handover Between NodeBs in an RNC

The procedure of intra-frequency hard handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l
7.5.2 Triggering Conditions of Intra-Frequency Hard Handover Between NodeBs in an RNC

Intra-frequency hard handover between NodeBs in an RNC is the intra-frequency hard handover where the source and target cells are controlled by different NodeBs in an RNC. 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.
7.5.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between NodeBs in an RNC
This describes the signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. Figure 7-31 shows the signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC.
7-30
Issue 01 (2009-03-25)
Figure 7-31 Signaling procedure of a successful intra-frequency hard handover between NodeBs in an RNC
l l
During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 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.
7.5.4 Using the RNC LMT to Trace the Procedure of Intra-Frequency Hard Handover Between NodeBs in an RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an intra-frequency hard handover between NodeBs in an RNC.
Prerequisite
l l
Context
Issue 01 (2009-03-25)
7-31
Table 7-5 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION PHYSICAL CHANNEL RECONFIGURATION COMPLETE PHYSICAL CHANNEL RECONFIGURATION FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE
RRC_PH_CH_RECFG Uu RRC_PH_CH_RECFG_CMP RRC_PH_CH_RECFG_FAIL NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP Q.AAL2 No message name needs to be specified.
Procedure
7-32
Issue 01 (2009-03-25)
----End
7.5.5 Elementary Procedures of Intra-Frequency Hard Handover Between NodeBs in an RNC

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. 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.

Procedure
l
2.

l l
7-34
Procedure
l

Procedure
Physical Channel Reconfiguration Procedure

The physical channel reconfiguration procedure is performed to set up, reconfigure, or release a physical channel.
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message.
Procedure
Figure 7-38 shows the physical channel reconfiguration procedure. Figure 7-38 Physical channel reconfiguration procedure
The procedure shown in Figure 7-38 is described as follows: 1. 2. 3.

7-36
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel. The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel. The UE sends a response message to the SRNC.

l
If successfully reconfiguring the physical channels specified by the PHYSICAL CHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC. If failing to reconfigure the physical channels specified by the PHYSICAL CHANNEL RECONFIGURATION message, the UE restores the configuration to the old physical channel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physical channel failure".

Procedure
l
Issue 01 (2009-03-25)

Procedure
l
7.6 Intra-Frequency Hard Handover Between RNCs

The procedure of intra-frequency hard handover between RNCs is performed to hand over a UE from a cell to an intra-frequency cell that is controlled by another RNC. 7.6.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs The procedure of intra-frequency hard handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. 7.6.2 Triggering Conditions of Intra-Frequency Hard Handover Between RNCs
Intra-frequency hard handover between RNCs is the intra-frequency hard handover where the source and target cells are controlled by different RNCs. 7.6.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs This describes the signaling procedure of a successful intra-frequency hard handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. 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.
7.6.1 Protocols Related to Intra-Frequency Hard Handover Between RNCs

The procedure of intra-frequency hard handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.423 "UTRAN Iur interface RNSAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
7.6.2 Triggering Conditions of Intra-Frequency Hard Handover Between RNCs

Intra-frequency hard handover between RNCs is the intra-frequency hard handover where the source and target cells are controlled by different RNCs. 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.
7.6.3 Signaling Procedure of a Successful Intra-Frequency Hard Handover Between RNCs

This describes the signaling procedure of a successful intra-frequency hard handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. Figure 7-41 shows the signaling procedure of a successful intra-frequency hard handover between RNCs.
Issue 01 (2009-03-25)
7-39
Figure 7-41 Signaling procedure of a successful intra-frequency hard handover between RNCs
l l
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.
Prerequisite
l
The RNC LMT works properly.

7-40

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. Table 7-6 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION PHYSICAL CHANNEL RECONFIGURATION COMPLETE PHYSICAL CHANNEL RECONFIGURATION FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION
RRC_PH_CH_RECFG Uu RRC_PH_CH_RECFG_CMP RRC_PH_CH_RECFG_FAIL NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RNSAP_RL_SETUP_REQ Iur RNSAP_RL_SETUP_RSP RNSAP_RL_SETUP_FAIL RNSAP_RL_RESTORE_IND Q.AAL2 No message name needs to be specified.
Procedure
Issue 01 (2009-03-25)
7-41
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-43 Example of Iub signaling tracing result (source RNC)
----End
7-42
Issue 01 (2009-03-25)
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. 7.6.5.1 Radio Link Setup Procedure (Inter-RNC Handover) The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE. 7.6.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.6.5.3 Radio Link Restoration Procedure (Inter-RNC Handover) The radio link restoration procedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved. 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.

Procedure
Figure 7-47 shows the radio link setup procedure for inter-RNC handover.
Issue 01 (2009-03-25)
7-43
Figure 7-47 Radio link setup procedure (inter-RNC handover)
l
5.
l

l l
Procedure
l l

Procedure
Issue 01 (2009-03-25)
7-45

Procedure
l

Procedure
The procedure shown in Figure 7-51 is described as follows: 1. 2. 3. The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel. The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel. The UE sends a response message to the SRNC.
l

Procedure
l

Procedure
7-48
Issue 01 (2009-03-25)
l

Procedure
Issue 01 (2009-03-25)
7-49
l
7-50
Issue 01 (2009-03-25)
8 Inter-Frequency Handover Procedure
Inter-Frequency Handover Procedure
About This Chapter

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. 8.1 Types of Inter-Frequency Handover Inter-frequency handovers are categorized into two types: handover within an RNC and handover between RNCs. 8.2 Inter-Frequency Handover Between NodeBs in an RNC The procedure of inter-frequency handover between NodeBs in an RNC is performed to hand over a UE from a cell to an inter-frequency cell that is controlled by the same RNC. 8.3 Inter-Frequency Handover Between RNCs The procedure of inter-frequency handover between RNCs is performed to hand over a UE from a cell to an inter-frequency cell that is controlled by another RNC.
Issue 01 (2009-03-25)
8-1
8.1 Types of Inter-Frequency Handover

Inter-frequency handovers are categorized into two types: handover within an RNC and handover between RNCs. Table 8-1 lists the types of inter-frequency handover. Table 8-1 Types of inter-frequency handover Type Interfrequency handover within an RNC Subtype Inter-frequency handover within a NodeB Inter-frequency handover between NodeBs Inter-frequency handover between RNCs without relocation Inter-frequency handover between RNCs with UE-notinvolved relocation Inter-frequency handover between RNCs with UEinvolved relocation Description The procedures of the two subtypes are similar. They are described in the procedure of inter-frequency handover between NodeBs in an RNC. When a UE performs an inter-frequency handover between RNCs with UE-notinvolved relocation, an Iur interface must be configured between the two RNCs. When a UE performs an inter-frequency handover between RNCs with UEinvolved relocation, no Iur interface exists between the two RNCs.
Interfrequency handover between RNCs
8.2 Inter-Frequency Handover Between NodeBs in an RNC

The procedure of inter-frequency handover between NodeBs in an RNC is performed to hand over a UE from a cell to an inter-frequency cell that is controlled by the same RNC. 8.2.1 Protocols Related to Inter-Frequency Handover Between NodeBs in an RNC The procedure of inter-frequency handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. 8.2.2 Triggering Conditions of Inter-Frequency Handover Between NodeBs in an RNC Inter-frequency handover between NodeBs in an RNC is the inter-frequency handover where the source and target cells are controlled by different NodeBs in an RNC. 8.2.3 Signaling Procedure of a Successful Inter-Frequency Handover Between NodeBs in an RNC This describes the signaling procedure of a successful inter-frequency handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. 8.2.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between NodeBs in an RNC The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between NodeBs in an RNC.
8.2.5 Elementary Procedures of Inter-Frequency Handover Between NodeBs in an RNC This describes the elementary procedures of inter-frequency handover between NodeBs in an RNC in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
8.2.1 Protocols Related to Inter-Frequency Handover Between NodeBs in an RNC

The procedure of inter-frequency handover between NodeBs in an RNC complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l
8.2.2 Triggering Conditions of Inter-Frequency Handover Between NodeBs in an RNC

Inter-frequency handover between NodeBs in an RNC is the inter-frequency handover where the source and target cells are controlled by different NodeBs in an RNC. The handover is triggered when the signal quality of the serving cell is degraded or the load of the serving cell is heavy.
8.2.3 Signaling Procedure of a Successful Inter-Frequency Handover Between NodeBs in an RNC

This describes the signaling procedure of a successful inter-frequency handover between NodeBs in an RNC. For the messages related to handover failures, refer to the elementary procedures. Figure 8-1 shows the signaling procedure of a successful inter-frequency handover between NodeBs in an RNC.
Issue 01 (2009-03-25)
8-3
Figure 8-1 Signaling procedure of a successful inter-frequency handover between NodeBs in an RNC
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. During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 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 l
8.2.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between NodeBs in an RNC
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between NodeBs in an RNC.
Prerequisite
l l
Context
8-4
Issue 01 (2009-03-25)
Table 8-2 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION PHYSICAL CHANNEL RECONFIGURATION COMPLETE PHYSICAL CHANNEL RECONFIGURATION FAILURE RADIO LINK ADDITION REQUEST RADIO LINK ADDITION RESPONSE RADIO LINK ADDITION FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE
RRC_PH_CH_RECFG Uu RRC_PH_CH_RECFG_CMP RRC_PH_CH_RECFG_FAIL NBAP_RL_ADD_REQ NBAP_RL_ADD_RSP NBAP_RL_ADD_FAIL NBAP_RL_SETUP_REQ Iub NBAP_RL_SETUP_RSP NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP Q.AAL2 No message name needs to be specified.
Procedure
Issue 01 (2009-03-25)
8-5
----End
8.2.5 Elementary Procedures of Inter-Frequency Handover Between NodeBs in an RNC

This describes the elementary procedures of inter-frequency handover between NodeBs in an RNC in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 8.2.5.1 Radio Link Addition Procedure The radio link addition procedure is performed to add one or more radio links towards a UE. 8.2.5.2 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. 8.2.5.3 Iub User Plane Setup Procedure The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface. 8.2.5.4 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. 8.2.5.5 Physical Channel Reconfiguration Procedure The physical channel reconfiguration procedure is performed to set up, reconfigure, or release a physical channel. 8.2.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.2.5.7 Iub User Plane Release Procedure The Iub user plane release procedure is performed to release data transport bearers from the Iub interface.
Radio Link Addition Procedure

The radio link addition procedure is performed to add one or more radio links towards a UE.
The CRNC sends a RADIO LINK ADDITION REQUEST message.
Procedure
Figure 8-5 shows the radio link addition procedure. Figure 8-5 Radio link addition procedure
The procedure shown in Figure 8-5 is described as follows: 1. The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary resources and configures the new radio link or links according to the parameters given in the message. The NodeB sends a response message to the CRNC.
l
2.
If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK ADDITION REQUEST message and sends a RADIO LINK ADDITION RESPONSE message. If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the Cause IE.

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)
l
2.

l l
Procedure
8-8
Issue 01 (2009-03-25)
l

Procedure
Issue 01 (2009-03-25)
8-9

Procedure
The procedure shown in Figure 8-9 is described as follows: 1. 2. 3.

8-10
The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel. The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel. The UE sends a response message to the SRNC.

l

Procedure
l
Issue 01 (2009-03-25)

Procedure
l
8.3 Inter-Frequency Handover Between RNCs

The procedure of inter-frequency handover between RNCs is performed to hand over a UE from a cell to an inter-frequency cell that is controlled by another RNC. 8.3.1 Protocols Related to Inter-Frequency Handover Between RNCs The procedure of inter-frequency handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. 8.3.2 Triggering Conditions of Inter-Frequency Handover Between RNCs
Inter-frequency handover between RNCs is the inter-frequency handover where the source and target cells are controlled by different RNCs. 8.3.3 Signaling Procedure of a Successful Inter-Frequency Handover Between RNCs This describes the signaling procedure of a successful inter-frequency handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. 8.3.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between RNCs The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between RNCs. 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.
8.3.1 Protocols Related to Inter-Frequency Handover Between RNCs

The procedure of inter-frequency handover between RNCs complies with some 3GPP TS25 protocols and an ITU-T protocol. The compliance protocols are as follows:
l l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.423 "UTRAN Iur interface RNSANP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signalling" ITU-T Q.2630 "AAL type 2 Signalling Protocol"
8.3.2 Triggering Conditions of Inter-Frequency Handover Between RNCs

Inter-frequency handover between RNCs is the inter-frequency handover where the source and target cells are controlled by different RNCs. The handover is triggered when the signal quality of the serving cell is degraded or the load of the serving cell is heavy.
8.3.3 Signaling Procedure of a Successful Inter-Frequency Handover Between RNCs

This describes the signaling procedure of a successful inter-frequency handover between RNCs. For the messages related to handover failures, refer to the elementary procedures. Figure 8-12 shows the signaling procedure of a successful inter-frequency handover between RNCs.
Issue 01 (2009-03-25)
8-13
Figure 8-12 Signaling procedure of a successful inter-frequency handover between RNCs
l l
8.3.4 Using the RNC LMT to Trace the Procedure of Inter-Frequency Handover Between RNCs
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-frequency handover between RNCs.
Prerequisite
l l
8-14
Context
Table 8-3 lists the messages to be traced. Table 8-3 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION PHYSICAL CHANNEL RECONFIGURATION COMPLETE PHYSICAL CHANNEL RECONFIGURATION FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION
RRC_PH_CH_RECFG Uu RRC_PH_CH_RECFG_CMP RRC_PH_CH_RECFG_FAIL NBAP_RL_SETUP_REQ NBAP_RL_SETUP_RSP Iub NBAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RNSAP_RL_SETUP_REQ Iur RNSAP_RL_SETUP_RSP RNSAP_RL_SETUP_FAIL RNSAP_RL_RESTORE_IND Q.AAL2 No message name needs to be specified.
Procedure
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-14 Example of Iub signaling tracing result (source RNC)
----End
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. 8.3.5.1 Radio Link Setup Procedure (Inter-RNC Handover)
The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE. 8.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. 8.3.5.3 Radio Link Restoration Procedure (Inter-RNC Handover) The radio link restoration procedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved. 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.

Procedure
Figure 8-18 shows the radio link setup procedure for inter-RNC handover. Figure 8-18 Radio link setup procedure (inter-RNC handover)
Issue 01 (2009-03-25)
8-17
l
5.
l l

l l
Procedure
8-18
Issue 01 (2009-03-25)
l

Procedure

Procedure
l

Procedure
Figure 8-22 shows the physical channel reconfiguration procedure.
8-20
Issue 01 (2009-03-25)
Figure 8-22 Physical channel reconfiguration procedure
l

Procedure
Issue 01 (2009-03-25)
8-21
l

Procedure
8-22
Issue 01 (2009-03-25)
l

Procedure
Issue 01 (2009-03-25)
8-23
l
8-24
Issue 01 (2009-03-25)
9 Inter-RAT Handover Procedure
9
About This Chapter
Inter-RAT Handover Procedure
The inter-RAT handover procedure is performed to hand over a UE from a WCDMA cell to a GSM cell or the other way round. This 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. 9.1 Types of Inter-RAT Handover Based on the direction of handover, inter-RAT handovers are categorized into two types: interRAT handover from WCDMA to GSM and inter-RAT handover from GSM to WCDMA. 9.2 Inter-RAT CS Handover from WCDMA to GSM The procedure of inter-RAT CS handover from WCDMA to GSM is performed to hand over the CS services of a UE from the WCDMA system to the GSM system. 9.3 Inter-RAT CS Handover from GSM to WCDMA The procedure of inter-RAT CS handover from GSM to WCDMA is performed to hand over the CS services of a UE from the GSM system to the WCDMA system. 9.4 Inter-RAT PS Handover from WCDMA to GSM The procedure of inter-RAT PS handover from WCDMA to GSM is performed to hand over the PS services of a UE from the WCDMA system to the GSM system. 9.5 Inter-RAT PS Handover from GSM to WCDMA The procedure of inter-RAT PS handover from GSM to WCDMA is performed through cell reselection to WCDMA that is initiated by the UE.
Issue 01 (2009-03-25)
9-1
9.1 Types of Inter-RAT Handover

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

The procedure of inter-RAT CS handover from WCDMA to GSM is performed to hand over the CS services of a UE from the WCDMA system to the GSM system. 9.2.1 Protocols Related to Inter-RAT CS Handover from WCDMA to GSM The procedure of inter-RAT CS handover from WCDMA to GSM complies with some 3GPP TS25 protocols. 9.2.2 Triggering Conditions of Inter-RAT CS Handover from WCDMA to GSM The signal quality of the WCDMA cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy. 9.2.3 Signaling Procedure of a Successful Inter-RAT CS Handover from WCDMA to GSM This describes the signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM. For the messages related to handover failures, refer to the elementary procedures. 9.2.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from WCDMA to GSM The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from WCDMA to GSM. 9.2.5 Elementary Procedures of Inter-RAT CS Handover from WCDMA to GSM This describes the elementary procedures of inter-RAT CS handover from WCDMA to GSM in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
9.2.1 Protocols Related to Inter-RAT CS Handover from WCDMA to GSM

The procedure of inter-RAT CS handover from WCDMA to GSM complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
9-2
9.2.2 Triggering Conditions of Inter-RAT CS Handover from WCDMA to GSM

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

This describes the signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM. For the messages related to handover failures, refer to the elementary procedures. Figure 9-1 shows the signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM. Figure 9-1 Signaling procedure of a successful inter-RAT CS handover from WCDMA to GSM
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). 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.
Issue 01 (2009-03-25)
9.2.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from WCDMA to GSM
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from WCDMA to GSM.
Prerequisite
l l
Context
Table 9-1 lists the messages to be traced. Table 9-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_HO_FROM_UTRAN_C MD_GSM RRC_HO_FROM_UTRAN_F AIL NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RANAP_RELOCATION_RE QUIRED RANAP_RELOCATION_CO MMAND Iu RANAP_RELOCATION_PR EPARATION_FAILURE RANAP_IU_RELEASE_CO MMAND RANAP_IU_RELEASE_CO MPLETE Message Name in Protocols HANDOVER FROM UTRAN COMMAND HANDOVER FROM UTRAN FAILURE RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RELOCATION REQUIRED RELOCATION COMMAND RELOCATION PREPARATION FAILURE IU RELEASE COMMAND IU RELEASE COMPLETE
Uu
Iub
Procedure
9-4
Issue 01 (2009-03-25)
----End
9.2.5 Elementary Procedures of Inter-RAT CS Handover from WCDMA to GSM

This describes the elementary procedures of inter-RAT CS handover from WCDMA to GSM in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 9.2.5.1 Relocation Preparation Procedure The relocation preparation procedure is performed to prepare resources for relocation of the SRNS. 9.2.5.2 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. 9.2.5.3 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.
Relocation Preparation Procedure

The relocation preparation procedure is performed to prepare resources for relocation of the SRNS.
The relocation preparation procedure can be triggered in either of the following conditions:

l l
During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message. During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends a RELOCATION REQUIRED message.
Procedure
Figure 9-5 shows the relocation preparation procedure. Figure 9-5 Relocation preparation procedure
The procedure shown in Figure 9-5 is described as follows: 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. The CN interacts with the target RNC or the target network system, such as the GSM system, to prepare relevant resources. The CN sends a response message to the SRNC.
l
2. 3.
If the target RNC or the target network system prepares the relevant resources successfully, the CN sends a RELOCATION COMMAND message when the preparation is complete. The message contains the L3 information IE, which carries the information about the relevant resources allocated by the target RNC or the target network system. If the resources partially or totally fail to be allocated, the CN sends a RELOCATION PREPARATION FAILURE message.
Iu Release Procedure
l l
l l
Procedure
NOTE
2.

Procedure
l
9.3 Inter-RAT CS Handover from GSM to WCDMA

The procedure of inter-RAT CS handover from GSM to WCDMA is performed to hand over the CS services of a UE from the GSM system to the WCDMA system. 9.3.1 Protocols Related to Inter-RAT CS Handover from GSM to WCDMA The procedure of inter-RAT CS handover from GSM to WCDMA complies with some 3GPP TS25 protocols. 9.3.2 Triggering Conditions of Inter-RAT CS Handover from GSM to WCDMA The signal quality of the GSM cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy. 9.3.3 Signaling Procedure of a Successful Inter-RAT CS Handover from GSM to WCDMA This describes the signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA. For the messages related to handover failures, refer to the elementary procedures. 9.3.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from GSM to WCDMA
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from GSM to WCDMA. 9.3.5 Elementary Procedures of Inter-RAT CS Handover from GSM to WCDMA This describes the elementary procedures of inter-RAT CS handover from GSM to WCDMA in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
9.3.1 Protocols Related to Inter-RAT CS Handover from GSM to WCDMA

The procedure of inter-RAT CS handover from GSM to WCDMA complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
9.3.2 Triggering Conditions of Inter-RAT CS Handover from GSM to WCDMA

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

This describes the signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA. For the messages related to handover failures, refer to the elementary procedures. Figure 9-8 shows the signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA.
Issue 01 (2009-03-25)
9-9
Figure 9-8 Signaling procedure of a successful inter-RAT CS handover from GSM to WCDMA
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). After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a RELOCATION DETECT message to the MSC server to inform the MSC server that the UE has been handed over from GSM to WCDMA. After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fails, the UE reports the failure to the GSM system. After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a RELOCATION COMPLETE message to the MSC server. In addition, the RNC controls the UE to perform the UTRAN mobility information procedure, the UE capability enquiry procedure, and the security mode control procedure. In practice, the signaling messages traced may differ from the signaling message shown in the figure in terms of the sequence.
9-10
9.3.4 Using the RNC LMT to Trace the Procedure of Inter-RAT CS Handover from GSM to WCDMA
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT CS handover from GSM to WCDMA.
Prerequisite
l l
Context
Table 9-2 lists the messages to be traced. Table 9-2 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_HO_UTRAN_CMP RRC_UTRAN_MOBIL_INF O RRC_UTRAN_MOBIL_INF O_CONFIRM RRC_UTRAN_MOBIL_INF O_FAILURE RRC_UE_CAP_ENQUIRY Uu RRC_UE_CAP_INFO RRC_UE_CAP_INFO_CONF IRM RRC_SECURITY_MODE_C MD RRC_SECURITY_MODE_C MP RRC_SECURITY_MODE_F AIL NBAP_RL_SETUP_REQ Iub NBAP_RL_SETUP_RSP RNSAP_RL_SETUP_FAIL NBAP_RL_RESTORE_IND
Issue 01 (2009-03-25)
Message Name in Protocols HANDOVER TO UTRAN COMPLETE UTRAN MOBILITY INFORMATION UTRAN MOBILITY INFORMATION CONFIRM UTRAN MOBILITY INFORMATION FAILURE UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION UE CAPABILITY INFORMATION CONFIRM SECURITY MODE COMMAND SECURITY MODE COMPLETE SECURITY MODE FAILURE RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE RADIO LINK SETUP FAILURE RADIO LINK RESTORE INDICATION
9-11
Message Name on the LMT RANAP_RELOCATION_RE Q RANAP_RELOCATION_RE Q_ACK
RELOCATION REQUEST RELOCATION REQUEST ACKNOWLEDGE RELOCATION FAILURE RELOCATION DECTECT RELOCATION COMPLETE
Iu
RANAP_RELOCATION_FAI LURE RANAP_RELOCATION_DE TECT RANAP_RELOCATION_CO MPLETE
Procedure
9-12
Issue 01 (2009-03-25)
----End
9.3.5 Elementary Procedures of Inter-RAT CS Handover from GSM to WCDMA

This describes the elementary procedures of inter-RAT CS handover from GSM to WCDMA in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 9.3.5.1 Relocation Resource Allocation Procedure The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation. 9.3.5.2 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. 9.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. 9.3.5.4 UE Capability Enquiry Procedure The UE capability enquiry procedure is performed to request a UE to transmit its capability information related to any radio access network so that the network can perform data configuration based on the UE capability. 9.3.5.5 Security Mode Control Procedure The security mode control procedure is performed to configure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a UE. 9.3.5.6 UTRAN Mobility Information Procedure The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domainrelated information.
Relocation Resource Allocation Procedure

The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation.
The relocation resource allocation procedure can be triggered in either of the following conditions:
l l
During an SRNS relocation, the CN applies for resources from the target RNC. During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources from the target RNC.
Issue 01 (2009-03-25)
9-13
Procedure
Figure 9-12 shows the relocation resource allocation procedure. Figure 9-12 Relocation resource allocation procedure
The procedure shown in Figure 9-12 is described as follows: 1. The CN sends a RELOCATION REQUEST message to the target RNC. The message contains certain information, such as the IMSI of the UE, CN domain indicator, target cell identifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters. The target RNC allocates radio resources for the relocation. The target RNC sends a response message to the CN.
l
2. 3.
If the resources are allocated, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and other parameters allocated to the UE. The parameters include the UTRAN Radio Network Temporary Identifier (U-RNTI), RAB, transport layer and physical layer information, chosen encryption algorithm, and chosen integrity protection algorithm. If the resources partially or totally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION FAILURE message, indicating the failure cause.

Procedure
l
2.

Procedure
UE Capability Enquiry Procedure

The UE capability enquiry procedure is performed to request a UE to transmit its capability information related to any radio access network so that the network can perform data configuration based on the UE capability.
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. Figure 9-15 UE capability enquiry procedure
The procedure shown in Figure 9-15 is described as follows:

1. 2.
The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. 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. 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.
3.
Security Mode Control Procedure

The security mode control procedure is performed to configure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a UE.
The ciphering algorithm or the integrity protection algorithm has changed.
Procedure
Figure 9-16 shows the security mode control procedure. Figure 9-16 Security mode control procedure
The procedure shown in Figure 9-16 is described as follows: 1. Through a SECURITY MODE COMMAND message sent to the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity protection configurations for the RBs or one CN domain and for all Signaling Radio Bearers (SRBs). The UE sends a response message to the SRNC.
l
2.
If the UE completes configuring or reconfiguring the relevant parameters for one or both of the ciphering and integrity protection algorithms, the UE sends a SECURITY MODE COMPLETE message to inform the SRNC of the completion. If the SECURITY MODE COMMAND message contains neither Ciphering mode info IE nor Integrity protection mode info IE or if each of the two IEs has inconsistent
Issue 01 (2009-03-25)
information, the UE sends a SECURITY MODE FAILURE message, indicating the failure of the security mode control procedure as well as the failure cause.
UTRAN Mobility Information Procedure

The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domainrelated information.
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
Procedure
Figure 9-17 shows the UTRAN mobility information procedure. Figure 9-17 UTRAN mobility information procedure
The procedure shown in Figure 9-17 is described as follows: 1. 2. 3. The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE. The UE starts to update the related fields according to the values of the IEs carried in the message. The UE sends a response message to the SRNC.
l
If the UE succeeds in conducting the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message. If the UE fails to conduct the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION FAILURE message, indicating the failure cause.
9-18
9.4 Inter-RAT PS Handover from WCDMA to GSM

The procedure of inter-RAT PS handover from WCDMA to GSM is performed to hand over the PS services of a UE from the WCDMA system to the GSM system. 9.4.1 Protocols Related to Inter-RAT PS Handover from WCDMA to GSM The procedure of inter-RAT PS handover from WCDMA to GSM complies with some 3GPP TS25 protocols. 9.4.2 Triggering Conditions of Inter-RAT PS Handover from WCDMA to GSM The signal quality of the WCDMA cell that the UE camps on is dissatisfactory or the load of the serving cell is heavy. 9.4.3 Signaling Procedure of Successful Inter-RAT PS Handover from WCDMA to GSM This describes the signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM. For the messages related to handover failures, refer to the elementary procedures. 9.4.4 Using the RNC LMT to Trace the Procedure of Inter-RAT PS Handover from WCDMA to GSM The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT PS handover from WCDMA to GSM. 9.4.5 Elementary Procedures of Inter-RAT PS Handover from WCDMA to GSM This describes the elementary procedures of inter-RAT PS handover from WCDMA to GSM in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
9.4.1 Protocols Related to Inter-RAT PS Handover from WCDMA to GSM

The procedure of inter-RAT PS handover from WCDMA to GSM complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
9.4.2 Triggering Conditions of Inter-RAT PS Handover from WCDMA to GSM

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

This describes the signaling procedure of a successful inter-RAT PS handover from WCDMA to GSM. For the messages related to handover failures, refer to the elementary procedures. 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
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. After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message because the UE stops the transmission towards the WCDMA cell. This message, however, is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM. After the UE accesses a GSM cell, the SGSN directly sends an IU RELEASE COMMAND message to the SRNC, if the Packet Data Protocol (PDP) context does not need to be transferred. The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM.
9-20
9.4.4 Using the RNC LMT to Trace the Procedure of Inter-RAT PS Handover from WCDMA to GSM
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of an inter-RAT PS handover from WCDMA to GSM.
Prerequisite
l l
Context
Table 9-3 lists the messages to be traced. Table 9-3 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_CELL_CHANGE_ORD ER_FROM_UTRAN RRC_CELL_CHANGE_ORD ER_FROM_UTRAN_FAIL NBAP_RL_FAIL_IND Iub NBAP_RL_DEL_REQ NBAP_RL_DEL_RSP RANAP_SRNS_CONTEXT_ REQ RANAP_SRNS_CONTEXT_ RESP Iu RANAP_SRNS_DATA_FOR WARD_COMMAND RANAP_IU_RELEASE_CO MMAND RANAP_IU_RELEASE_CO MPLETE Message Name in Protocols CELL CHANGE ORDER FROM UTRAN CELL CHANGE ORDER FROM UTRAN FAILURE RADIO LINK FAILURE INDICATION RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE SRNS CONTEXT REQUEST SRNS CONTEXT RESPONSE SRNS DATA FORWARD COMMAND IU RELEASE COMMAND IU RELEASE COMPLETE
Uu
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.
Issue 01 (2009-03-25)
9-21
Figure 9-19 Example of Uu signaling tracing result
----End
9.4.5 Elementary Procedures of Inter-RAT PS Handover from WCDMA to GSM

This describes the elementary procedures of inter-RAT PS handover from WCDMA to GSM in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 9.4.5.1 Cell Change Order from UTRAN Procedure The cell change order from UTRAN procedure is performed to hand over, under the control of the network, a UE in CELL_DCH state to a GSM cell when the RABs established in the WCDMA system are only from the PS domain. 9.4.5.2 SRNS Context Transfer Procedure The SRNS context transfer procedure is performed to transfer SRNS contexts from the source RNC to the SGSN. 9.4.5.3 Iu Release Procedure The Iu release procedure is performed for the CN to release an Iu connection and all the UTRAN resources related only to that Iu connection. 9.4.5.4 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.
Cell Change Order from UTRAN Procedure

The cell change order from UTRAN procedure is performed to hand over, under the control of the network, a UE in CELL_DCH state to a GSM cell when the RABs established in the WCDMA system are only from the PS domain.
The network decides to hand over the UE to the GSM system.
Procedure
Figure 9-22 shows the cell change order from UTRAN procedure. Figure 9-22 Cell change order from UTRAN procedure
The procedure shown in Figure 9-22 is described as follows: 1. Through a CELL CHANGE ORDER FROM UTRAN message, the SRNC orders the UE to perform a cell change to the GSM system. The message contains certain IEs about the target cell. The IEs include BSIC, Band indicator, BCCH ARFCN, and NC mode. Upon reception of the CELL CHANGE ORDER FROM UTRAN message, the UE starts timer T309 and initiates access to the GSM cell.
l l
2.
If the UE accesses the GSM cell before the timer expires, the procedure ends. If the UE fails to access the GSM cell before the timer expires, the UE sends a CELL CHANGE ORDER FROM UTRAN FAILURE message to the SRNC.
SRNS Context Transfer Procedure

The SRNS context transfer procedure is performed to transfer SRNS contexts from the source RNC to the SGSN.
Issue 01 (2009-03-25)
9-23
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. Figure 9-23 SRNS context transfer procedure
The procedure shown in Figure 9-23 is described as follows: 1. 2. The SGSN sends an SRNS CONTEXT REQUEST message to the SRNC. The message includes the list of RABs whose contexts should be transferred. The SRNC sends an SRNS CONTEXT RESPONSE message to the SGSN.
l
If the transfer is successful, the message contains RAB IDs that include the sequence numbers for the downlink and uplink GTP PDUs and PDCP SDUs. If the SRNC fails to identify the ID of the RAB whose context should be transferred to the SGSN, the SRNS CONTEXT RESPONSE message contains a Cause IE whose value is "Invalid RAB ID".
l
The transaction between the UE and the CN is complete.

9-24

l
The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST message. The Serving Radio Network Subsystem (SRNS) is relocated. The SRNS relocation is canceled after a relocation resource allocation procedure is complete.
l l
Procedure
NOTE
2.

Procedure
l
9.5 Inter-RAT PS Handover from GSM to WCDMA

The procedure of inter-RAT PS handover from GSM to WCDMA is performed through cell reselection to WCDMA that is initiated by the UE. For details, refer to 4 Location Update Procedure.
9-26
Issue 01 (2009-03-25)
10 SRNS Relocation Procedure
10
About This Chapter
SRNS Relocation 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. 10.1 Types of SRNS Relocation Based on whether the connection between the UE and the DRNC is set up during the relocation, SRNS relocation is categorized into two types: UE-not-involved relocation and UE-involved relocation. 10.2 Static Relocation The static relocation procedure is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered after a radio link is added to the DRNC for the UE. An Iur interface exists between the two RNCs involved in the relocation. 10.3 Relocation with Cell/URA Update The procedure of relocation with cell/URA update is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered by a cell update or URA update when the UE performs cell reselection to a cell in another RNC. 10.4 Relocation with Hard Handover The procedure of relocation with hard handover is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered when the UE performs an inter-RNC hard handover, which can be either an intra-frequency hard handover or an inter-frequency handover. No Iur interface exists between the two RNCs involved in the relocation. 10.5 DSCR Procedure When the Iur connection is missing, the RNC cannot contact the SRNC to verify the UE. As a result, the DSCR procedure is triggered, and the RNC sends the "RRC CONNECTION RELEASE" message.
Issue 01 (2009-03-25)
10-1
10.1 Types of SRNS Relocation

Based on whether the connection between the UE and the DRNC is set up during the relocation, SRNS relocation is categorized into two types: UE-not-involved relocation and UE-involved relocation. UE-not-involved reloaction:
l
Static relocation: The relocation is triggered after a radio link is added to the DRNC for the UE 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.
UE-involved SRNS relocation :

l
Relocation with hard handover: An SRNS relocation is triggered when the UE performs an inter-RNC hard handover where no Iur interface exists between the two RNCs.
10.2 Static Relocation

The static relocation procedure is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered after a radio link is added to the DRNC for the UE. An Iur interface exists between the two RNCs involved in the relocation. 10.2.1 Protocols Related to Static Relocation The static relocation procedure complies with some 3GPP TS25 protocols. 10.2.2 Triggering Conditions of Static Relocation All the radio links connected to the UE exist only in the DRNC. 10.2.3 Signaling Procedure of a Successful Static Relocation This describes the signaling procedure of a successful static relocation. For the messages related to relocation failures, refer to the elementary procedures. 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. 10.2.5 Elementary Procedures of Static Relocation This describes the elementary procedures of static relocation in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
10.2.1 Protocols Related to Static Relocation

The static relocation procedure complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.423 "UTRAN Iur interface RNSAP signalling"
10-2
10.2.2 Triggering Conditions of Static Relocation

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

This describes the signaling procedure of a successful static relocation. For the messages related to relocation failures, refer to the elementary procedures. Figure 10-1 shows the signaling procedure of a successful static relocation. Figure 10-1 Signaling procedure of a successful static relocation
If the DRNC does not obtain the information about the UE capability, the DRNC initiates a UE capability enquiry procedure.
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 l
Context
Table 10-1 and Table 10-2 list the messages to be traced. Table 10-1 Messages to be traced on the SRNC Interface and Protocol to Be Traced Iur Message Name on the LMT RNSAP_RELOC_COMMIT RANAP_RELOCATION_REQU IRED RANAP_RELOCATION_COM MAND Iu RANAP_RELOCATION_PREP ARATION_FAILURE RANAP_IU_RELEASE_COMM AND RANAP_IU_RELEASE_COMP LETE Table 10-2 Messages to be traced on the DRNC Interface and Protocol to Be Traced Message Name on the LMT RRC_UTRAN_MOBIL_INF O RRC_UTRAN_MOBIL_INF O_CONFIRM Uu RRC_UTRAN_MOBIL_INF O_FAILURE RRC_UE_CAP_ENQUIRY RRC_UE_CAP_INFO RRC_UE_CAP_INFO_CONF IRM Iur RNSAP_RELOC_COMMIT Message Name in Protocols Message Name in Protocols RELOCATION COMMIT RELOCATION REQUIRED RELOCATION COMMAND RELOCATION PREPARATION FAILURE IU RELEASE COMMAND IU RELEASE COMPLETE
UTRAN MOBILITY INFORMATION UTRAN MOBILITY INFORMATION CONFIRM UTRAN MOBILITY INFORMATION FAILURE UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION UE CAPABILITY INFORMATION CONFIRM RELOCATION COMMIT
10-4
Issue 01 (2009-03-25)
Message Name on the LMT RANAP_RELOCATION_RE Q RANAP_RELOCATION_RE Q_ACK
RELOCATION REQUEST RELOCATION REQUEST ACKNOWLEDGE RELOCATION FAILURE RELOCATION DETECT RELOCATION COMPLETE
Iu
Procedure
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. Figure 10-3 Example of Iur signaling tracing on the SRNC
Figure 10-4 shows an example of Iur signaling tracing on the DRNC. Figure 10-4 Example of Iur signaling tracing on the DRNC
Step 3 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 10-5 shows an example of Iu signaling tracing on the SRNC.
Figure 10-5 Example of Iu signaling tracing on the SRNC
Figure 10-6 shows an example of Iu signaling tracing on the DRNC. Figure 10-6 Example of Iu signaling tracing on the DRNC
----End
10.2.5 Elementary Procedures of Static Relocation

This describes the elementary procedures of static relocation in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 10.2.5.1 Relocation Preparation Procedure The relocation preparation procedure is performed to prepare resources for relocation of the SRNS. 10.2.5.2 Relocation Resource Allocation Procedure The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation. 10.2.5.3 Relocation Commit Procedure (Static Relocation or Relocation with Cell/URA Update) The relocation commit procedure is performed to execute the change of control from the SRNC of a UE to the DRNC. 10.2.5.4 UTRAN Mobility Information Procedure The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domainrelated information. 10.2.5.5 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.2.5.6 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.
10-6
Issue 01 (2009-03-25)

l l
Procedure
Figure 10-7 shows the relocation preparation procedure. Figure 10-7 Relocation preparation procedure
l
2. 3.
If the target RNC or the target network system prepares the relevant resources successfully, the CN sends a RELOCATION COMMAND message when the preparation is complete. The message contains the L3 information IE, which carries the information about the relevant resources allocated by the target RNC or the target network system.
Issue 01 (2009-03-25)

l
If the resources partially or totally fail to be allocated, the CN sends a RELOCATION PREPARATION FAILURE message.

l l
Procedure
l
2. 3.
If the resources are allocated, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and other
10-8
parameters allocated to the UE. The parameters include the UTRAN Radio Network Temporary Identifier (U-RNTI), RAB, transport layer and physical layer information, chosen encryption algorithm, and chosen integrity protection algorithm.
l
If the resources partially or totally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION FAILURE message, indicating the failure cause.
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.
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)
The procedure shown in Figure 10-9 is described as follows: 1. The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, the RELOCATION COMMIT message carries the GTP-U and PDCP sequence numbers required for data forwarding. Then, the SRNC initiates data forwarding. The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of the detection of the relocation commitment.
2.
Issue 01 (2009-03-25)
3.
The original DRNC sends a RELOCATION COMPLETE message to the CN to notify that the relocation is successful.
UTRAN Mobility Information Procedure

The UTRAN mobility information procedure is performed for the network to allocate a new UTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network Temporary Identifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domainrelated information.
The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.
Procedure
Figure 10-10 shows the UTRAN mobility information procedure. Figure 10-10 UTRAN mobility information procedure
The procedure shown in Figure 10-10 is described as follows: 1. 2. 3. The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE. The UE starts to update the related fields according to the values of the IEs carried in the message. The UE sends a response message to the SRNC.
l
If the UE succeeds in conducting the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message. If the UE fails to conduct the operations specified by the UTRAN MOBILITY INFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION FAILURE message, indicating the failure cause.
10-10

Procedure
The procedure shown in Figure 10-11 is described as follows: 1. 2. The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. 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. 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.
3.

l l
l l
Procedure
NOTE
2.
10.3 Relocation with Cell/URA Update

The procedure of relocation with cell/URA update is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered by a cell update or URA update when the UE performs cell reselection to a cell in another RNC. 10.3.1 Protocols Related to Relocation with Cell/URA Update The procedure of relocation with cell/URA update complies with some 3GPP TS25 protocols. 10.3.2 Triggering Conditions of Relocation with Cell/URA Update
When the UE performs cell reselection to a cell in another RNC, a CCH cannot be set up on the Iur interface or the attempt to set up a CCH on the Iur interface fails. 10.3.3 Signaling Procedure of a Successful Relocation with Cell/URA Update This describes the signaling procedure of a successful relocation with cell/URA update. For the messages related to relocation failures, refer to the elementary procedures. 10.3.4 Using the RNC LMT to Trace the Procedure of Relocation with Cell/URA Update The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with cell/URA update. 10.3.5 Elementary Procedures of Relocation with Cell/URA Update This describes the elementary procedures of relocation with cell/URA update in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
10.3.1 Protocols Related to Relocation with Cell/URA Update

The procedure of relocation with cell/URA update complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.423 "UTRAN Iur interface RNSAP signalling"
10.3.2 Triggering Conditions of Relocation with Cell/URA Update

When the UE performs cell reselection to a cell in another RNC, a CCH cannot be set up on the Iur interface or the attempt to set up a CCH on the Iur interface fails.
10.3.3 Signaling Procedure of a Successful Relocation with Cell/ URA Update

This describes the signaling procedure of a successful relocation with cell/URA update. For the messages related to relocation failures, refer to the elementary procedures. Figure 10-13 shows the signaling procedure of a successful relocation with cell/URA update.
Issue 01 (2009-03-25)
10-13
Figure 10-13 Signaling procedure of a successful relocation with cell/URA update
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. 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. After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message to the UE. After a successful URA update, the DRNC sends a URA UPDATE CONFIRM message to the UE. After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message from the DRNC, the UE can send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MOBILITY INFORMATION CONFIRM message (for the URA update) to the DRNC. This response from the UE is optional.
10-14

l
If the DRNC does not obtain the information about the UE capability, the DRNC initiates a UE capability enquiry procedure.
10.3.4 Using the RNC LMT to Trace the Procedure of Relocation with Cell/URA Update
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with cell/URA update.
Prerequisite
l l
Context
Table 10-3 and Table 10-4 list the messages to be traced. Table 10-3 Messages to be traced on the SRNC Interface and Protocol to Be Traced
Message Name on the LMT
Iur
RNSAP_UL_SIG_TRANSF_IN D RNSAP_RELOC_COMMIT RANAP_RELOCATION_REQ UIRED RANAP_RELOCATION_COM MAND
UPLINK SIGNALLING TRANSFER INDICATION RELOCATION COMMIT RELOCATION REQUIRED RELOCATION COMMAND RELOCATION PREPARATION FAILURE IU RELEASE COMMAND IU RELEASE COMPLETE
Iu
RANAP_RELOCATION_PREP ARATION_FAILURE RANAP_IU_RELEASE_COM MAND RANAP_IU_RELEASE_COMP LETE
Table 10-4 Messages to be traced on the DRNC Interface and Protocol to Be Traced Uu Message Name on the LMT RRC_CELL_UPDATE RRC_URA_UPDATE Message Name in Protocols CELL UPDATE URA UPDATE
10-15
Issue 01 (2009-03-25)
Message Name on the LMT RRC_CELL_UPDATE_CON FIRM RRC_URA_UPDATE_CONF IRM RRC_PH_CH_RECFG_CMP RRC_UTRAN_MOBIL_INF O_CONFIRM RRC_UE_CAP_ENQUIRY RRC_UE_CAP_INFO RRC_UE_CAP_INFO_CONF IRM RNSAP_UL_SIG_TRANSF_I ND RNSAP_RELOC_COMMIT RANAP_RELOCATION_RE Q RANAP_RELOCATION_RE Q_ACK
CELL UPDATE CONFIRM URA UPDATE CONFIRM PHYSICAL CHANNEL RECONFIGURATION COMPLETE UTRAN MOBILITY INFORMATION CONFIRM UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION UE CAPABILITY INFORMATION CONFIRM UPLINK SIGNALLING TRANSFER INDICATION RELOCATION COMMIT RELOCATION REQUEST RELOCATION REQUEST ACKNOWLEDGE RELOCATION FAILURE RELOCATION DETECT RELOCATION COMPLETE
Iur
Iu
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
10-16
Issue 01 (2009-03-25)
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. Figure 10-15 Example of Iur signaling tracing on the SRNC
Figure 10-16 shows an example of Iur signaling tracing on the DRNC. Figure 10-16 Example of Iur signaling tracing on the DRNC
Step 3 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 10-17 shows an example of Iu signaling tracing on the SRNC. Figure 10-17 Example of Iu signaling tracing on the SRNC
Figure 10-18 shows an example of Iu signaling tracing on the DRNC. Figure 10-18 Example of Iu signaling tracing on the DRNC
----End
10.3.5 Elementary Procedures of Relocation with Cell/URA Update

This describes the elementary procedures of relocation with cell/URA update in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 10.3.5.1 Relocation Preparation Procedure The relocation preparation procedure is performed to prepare resources for relocation of the SRNS. 10.3.5.2 Relocation Resource Allocation Procedure
The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation. 10.3.5.3 Cell Update Procedure The cell update procedure is performed to update the UE-related information on the UTRAN side when the location of a UE changes. In addition, the cell update procedure takes the role of monitoring the RRC connection, switching the status of the RRC connection, reporting errors, and transferring information. 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.

l l
Procedure
Figure 10-19 shows the relocation preparation procedure.
10-18
Issue 01 (2009-03-25)
Figure 10-19 Relocation preparation procedure
l
2. 3.

l l
Issue 01 (2009-03-25)
Procedure
l
2. 3.
Cell Update Procedure

The cell update procedure is performed to update the UE-related information on the UTRAN side when the location of a UE changes. In addition, the cell update procedure takes the role of monitoring the RRC connection, switching the status of the RRC connection, reporting errors, and transferring information.
10-20
Issue 01 (2009-03-25)
The cell update procedure can be triggered in one of the following conditions:
l l l l l l l
Cell reselection Re-entering the service area Periodical cell update Radio link failure Paging response Uplink data transmission RLC unrecoverable error
Procedure
Figure 10-21 shows the cell update procedure. Figure 10-21 Cell update procedure
The procedure shown in Figure 10-21 is described as follows: 1. The UE sends a CELL UPDATE message to the RNC. The message contains the information such as the Serving RNC Radio Network Temporary Identifier (S-RNTI) and the SRNC ID. The RNC sends a CELL UPDATE CONFIRM message to the UE. The message contains the information such as the U-RNTI and the IEs about the transport channels, physical channels, and radio bearers. According to related IEs in the received message, the UE may respond with messages or not. If the UE responds, the message can be one of the following messages:
l l
2.
3.
UTRAN MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURATION COMPLETE

Issue 01 (2009-03-25)

l l l
TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER RELEASE COMPLETE
URA Update Procedure

The URA update procedure is performed to update the URA-related location information on the network side when the location of a UE changes.
The URA update procedure can be triggered in either of the following conditions:
l l
URA reselection Periodical URA update
Procedure
Figure 10-22 shows the URA update procedure. Figure 10-22 URA update procedure
The procedure shown in Figure 10-22 is described as follows: 1. 2. The UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA update and the IEs such as the U-RNTI. The RNC sends a URA UPDATE CONFIRM message to the UE. The message contains the new C-RNTI and U-RNTI or the information about the new ciphering and integrity protection modes. The UE responds optionally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to the RNC after taking the new parameters into effect.
3.
10-22
Issue 01 (2009-03-25)
Relocation Commit Procedure (Static Relocation or Relocation with Cell/URA Update)

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)
The procedure shown in Figure 10-23 is described as follows: 1. The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, the RELOCATION COMMIT message carries the GTP-U and PDCP sequence numbers required for data forwarding. Then, the SRNC initiates data forwarding. The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of the detection of the relocation commitment. The original DRNC sends a RELOCATION COMPLETE message to the CN to notify that the relocation is successful.
2. 3.

Procedure
3.
l l
The transaction between the UE and the CN is complete. The UTRAN requests the CN to release the resources on the Iu interface by, for example, sending an IU RELEASE REQUEST message. The Serving Radio Network Subsystem (SRNS) is relocated.
10-24

l
The SRNS relocation is canceled after a relocation resource allocation procedure is complete.
Procedure
NOTE
2.
10.4 Relocation with Hard Handover

The procedure of relocation with hard handover is performed to change control from the SRNC of a UE to the DRNC. The relocation is triggered when the UE performs an inter-RNC hard handover, which can be either an intra-frequency hard handover or an inter-frequency handover. No Iur interface exists between the two RNCs involved in the relocation. 10.4.1 Protocols Related to Relocation with Hard Handover The procedure of relocation with hard handover complies with some 3GPP TS25 protocols. 10.4.2 Triggering Conditions of Relocation with Hard Handover The UE in CELL_DCH state performs an inter-RNC hard handover, which can be either an intra-frequency hard handover or an inter-frequency handover. 10.4.3 Signaling Procedure of a Successful Relocation with Hard Handover This describes the signaling procedure of a successful relocation with hard handover. For the messages related to relocation failures, refer to the elementary procedures.
10.4.4 Using the RNC LMT to Trace the Procedure of Relocation with Hard Handover The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with hard handover. 10.4.5 Elementary Procedures of Relocation with Hard Handover This describes the elementary procedures of relocation with hard handover in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
10.4.1 Protocols Related to Relocation with Hard Handover

The procedure of relocation with hard handover complies with some 3GPP TS25 protocols. The compliance protocols are as follows:
l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling"
10.4.2 Triggering Conditions of Relocation with Hard Handover

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

This describes the signaling procedure of a successful relocation with hard handover. For the messages related to relocation failures, refer to the elementary procedures. Figure 10-26 shows the signaling procedure of a successful relocation with hard handover.
10-26
Issue 01 (2009-03-25)
Figure 10-26 Signaling procedure of a successful relocation with hard handover
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. After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, the DRNC sends a RELOCATION DETECT message to the CN. If the DRNC does not obtain the information about the UE capability, the DRNC initiates a UE capability enquiry procedure.
10.4.4 Using the RNC LMT to Trace the Procedure of Relocation with Hard Handover
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of a relocation with hard handover.
Issue 01 (2009-03-25)
10-27
Prerequisite
l l
Context
Table 10-5 and Table 10-6 list the messages to be traced. Table 10-5 Messages to be traced on the SRNC Interface and Protocol to Be Traced Message Name on the LMT Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION PHYSICAL CHANNEL RECONFIGURATION FAILURE RELOCATION REQUIRED RELOCATION COMMAND RELOCATION PREPARATION FAILURE FORWARD SRNS CONTEXT IU RELEASE COMMAND IU RELEASE COMPLETE
RRC_PH_CH_RECFG Uu RRC_PH_CH_RECFG_FAIL RANAP_RELOCATION_REQU IRED RANAP_RELOCATION_COM MAND RANAP_RELOCATION_PREP ARATION_FAILURE RANAP_FORWARD_SRNS_C ONTEXT RANAP_IU_RELEASE_COMM AND RANAP_IU_RELEASE_COMP LETE Table 10-6 Messages to be traced on the DRNC Interface and Protocol to Be Traced Message Name on the LMT
Iu
Message Name in Protocols PHYSICAL CHANNEL RECONFIGURATION COMPLETE UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION UE CAPABILITY INFORMATION CONFIRM
RRC_PH_CH_RECFG_CMP RRC_UE_CAP_ENQUIRY RRC_UE_CAP_INFO RRC_UE_CAP_INFO_CONF IRM
Uu
10-28
Issue 01 (2009-03-25)
Message Name on the LMT RANAP_RELOCATION_RE Q RANAP_RELOCATION_RE Q_ACK RANAP_RELOCATION_FAI LURE RANAP_FORWARD_SRNS_ CONTEXT RANAP_RELOCATION_DE TECT RANAP_RELOCATION_CO MPLETE
RELOCATION REQUEST RELOCATION REQUEST ACKNOWLEDGE RELOCATION FAILURE FORWARD SRNS CONTEXT RELOCATION DETECT RELOCATION COMPLETE
Iu
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. Figure 10-27 Example of Uu signaling tracing on the SRNC
Figure 10-28 shows an example of Uu signaling tracing on the DRNC. Figure 10-28 Example of Uu signaling tracing on the DRNC
Step 2 Create an Iu tracing task by referring to Creating an RNC Tracing Task. Figure 10-29 shows an example of Iu signaling tracing on the SRNC. Figure 10-29 Example of Iu signaling tracing on the SRNC
Figure 10-30 shows an example of Iu signaling tracing on the DRNC.

Figure 10-30 Example of Iu signaling tracing on the DRNC
----End
10.4.5 Elementary Procedures of Relocation with Hard Handover

This describes the elementary procedures of relocation with hard handover in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 10.4.5.1 Relocation Preparation Procedure The relocation preparation procedure is performed to prepare resources for relocation of the SRNS. 10.4.5.2 Relocation Resource Allocation Procedure The relocation resource allocation procedure is performed to allocate resources from the target RNS for an SRNS relocation. 10.4.5.3 Relocation Commit Procedure (Relocation with Hard Handover) The relocation commit procedure is performed to execute the change of control from the SRNC of a UE to the DRNC. 10.4.5.4 Physical Channel Reconfiguration Procedure The physical channel reconfiguration procedure is performed to set up, reconfigure, or release a physical channel. 10.4.5.5 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.4.5.6 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.

l l
Procedure
Figure 10-31 shows the relocation preparation procedure.
Figure 10-31 Relocation preparation procedure
l
2. 3.

l l
Issue 01 (2009-03-25)
Procedure
l
2. 3.
Relocation Commit Procedure (Relocation with Hard Handover)

Procedure
Figure 10-33 shows the relocation commit procedure for the relocation with hard handover. Figure 10-33 Relocation commit procedure (relocation with hard handover)
The procedure shown in Figure 10-33 is described as follows: 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. After receiving the FORWARD SRNS CONTEXT message, the SGSN forwards the message to the DRNC. 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. The original DRNC sends a RELOCATION COMPLETE message to the CN to notify that the relocation is successful.
2. 3.
4.

Procedure
Figure 10-34 shows the physical channel reconfiguration procedure.
Figure 10-34 Physical channel reconfiguration procedure
l

Procedure
Figure 10-35 shows the UE capability enquiry procedure.
10-34
Issue 01 (2009-03-25)
Figure 10-35 UE capability enquiry procedure
3.
l l
l l
Procedure
Figure 10-36 shows the Iu release procedure.
Issue 01 (2009-03-25)
10-35
Figure 10-36 Iu release procedure
NOTE
2.
10.5 DSCR Procedure

When the Iur connection is missing, the RNC cannot contact the SRNC to verify the UE. As a result, the DSCR procedure is triggered, and the RNC sends the "RRC CONNECTION RELEASE" message. 10.5.1 Protocols Related to the DSCR Procedure The DSCR procedure complies with the following 3GPP TS25 protocols: 10.5.2 Cause of Triggering the DSCR Procedure When the Iur connection is missing, the RNC cannot contact the SRNC to verify the UE. As a result, the directed signaling connection re-establishment (DSCR) procedure is triggered, and the RNC sends the "RRC CONNECTION RELEASE" message. 10.5.3 Successful DSCR Procedure This describes a successful DSCR procedure.
10.5.1 Protocols Related to the DSCR Procedure

The DSCR procedure complies with the following 3GPP TS25 protocols:
l l
3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS23.060 "General Packet Radio Service (GPRS)"
10-36
10.5.2 Cause of Triggering the DSCR Procedure

When the Iur connection is missing, the RNC cannot contact the SRNC to verify the UE. As a result, the directed signaling connection re-establishment (DSCR) procedure is triggered, and the RNC sends the "RRC CONNECTION RELEASE" message.
10.5.3 Successful DSCR Procedure

This describes a successful DSCR procedure. Figure 10-37 shows a successful DSCR procedure. Figure 10-37 Successful DSCR procedure
The UE sets up the RRC connection to the RNC1 (namely, SRNC). During the relocation, the RNC1 is the source RNC and the RNC2 is the destination RNC. The procedure is as follows: 1. 2. The RNC1 initiates a DSCR procedure. The RNC1 sends the "DOWNLINK SIGNALLING TRANSFER REQUEST" message to the RNC2, requesting the RNC2 to send the "RRC CONNECTION RELEASE" message to the UE.
Issue 01 (2009-03-25)
3. 4. 5. 6. 7. 8. 9.
The RNC2 sends the UE the "RRC CONNECTION RELEASE" message, which contains "DSCR", namely, the cause of the "RRC CONNECTION RELEASE" message." After receiving the message, the UE releases the current RAB connection and RRC connection and then enters the idle mode. The UE performs a cell reselection procedure to find a suitable cell. After the UE finds a suitable cell, the UE reestablishes the RRC connection and RAB connection immediately. The UE sends the RNC2 the "ROUTE AREA UPDATE" message to initiate the URA update. The SGSN requests the RNC1 to transmit data packets. Then, the RNC1 transmits data packets (except those unacknowledged by the RNC1) to the SGSN. The UE sends the SGSN the "DIRECT TRANSFER" message to request the service setup.
10. The SGSN initiates the RAB establishment procedure.
10-38
Issue 01 (2009-03-25)
11 Location Service Procedure
11
About This Chapter
Location Service Procedure
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. 11.1 Positioning Methods Three standard positioning methods are available in a WCDMA system. They are CELLID +RTT, OTDOA, and A-GPS. 11.2 Positioning Based on CELLID+RTT When the CELLID+RTT positioning method is adopted, the location of a UE is identified based on the coverage area of the reference cell and the RTT measurements performed on all the cells in the active set of the UE. 11.3 Positioning Based on OTDOA-IPDL When the OTDOA-IPDL positioning method is adopted, the location of a UE is identified based on the arrival time differences of CPICH signals from three inter-NodeB cells to the UE, which measures the differences. 11.4 Positioning Based on A-GPS When the A-GPS positioning method is adopted, the location of a UE is identified based on the GPS positioning-assistance data and GPS pseudo-range measurement results collected by the RNC.
Issue 01 (2009-03-25)
11-1
11.1 Positioning Methods

Three standard positioning methods are available in a WCDMA system. They are CELLID +RTT, OTDOA, and A-GPS. Typically, in terms of the horizontal accuracy, Network Assisted GPS (A-GPS) ranks first, Observed Time Difference Of Arrival (OTDOA) second and 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.
11.2 Positioning Based on CELLID+RTT

When the CELLID+RTT positioning method is adopted, the location of a UE is identified based on the coverage area of the reference cell and the RTT measurements performed on all the cells in the active set of the UE. 11.2.1 Protocols Related to Positioning Based on CELLID+RTT The procedure of positioning based on CELLID+RTT complies with some 3GPP TS22, TS23, and TS25 protocols. 11.2.2 Triggering Conditions of Positioning Based on CELLID+RTT The CN initiates a positioning request and the RNC chooses the UE-assisted CELLID+RTT positioning method. 11.2.3 Signaling Procedure of Successful Positioning Based on CELLID+RTT This describes the signaling procedure of successful positioning based on CELLID+RTT. For the messages related to positioning failures, refer to the elementary procedures. 11.2.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELLID+RTT or OTDOA-IPDL. 11.2.5 Elementary Procedures of Positioning Based on CELLID+RTT This describes the elementary procedures of positioning based on CELLID+RTT in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
11.2.1 Protocols Related to Positioning Based on CELLID+RTT

The procedure of positioning based on CELLID+RTT complies with some 3GPP TS22, TS23, and TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS22.071 "Location Services (LCS)" 3GPP TS23.271 "Functional stage 2 description of LCS" 3GPP TS25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN)" 3GPP TS25.331 "Radio Resource Control (RRC)"
11-2

l l
3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signaling"
11.2.2 Triggering Conditions of Positioning Based on CELLID+RTT

The CN initiates a positioning request and the RNC chooses the UE-assisted CELLID+RTT positioning method. 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.
11.2.3 Signaling Procedure of Successful Positioning Based on CELLID+RTT

This describes the signaling procedure of successful positioning based on CELLID+RTT. For the messages related to positioning failures, refer to the elementary procedures. Figure 11-1 shows the signaling procedure of successful positioning based on CELLID+RTT. Figure 11-1 Signaling procedure of successful positioning based on CELLID+RTT
l
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UE-assisted CELLID+RTT positioning method. 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.
11.2.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELLID+RTT or OTDOA-IPDL.
Prerequisite
l l
Context
Table 11-1 lists the messages to be traced. Table 11-1 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_MEAS_CTRL Uu RRC_MEAS_RPRT RRC_MEAS_CTRL_FAIL NBAP_DECIC_MEAS_INIT_ REQ NBAP_DECIC_MEAS_INIT_ RSP RANAP_LOCATION_REPO RTING_CONTROL RANAP_LOCATION_REPO RT Message Name in Protocols MEASUREMENT CONTROL MEASUREMENT REPORT MEASUREMENT CONTROL FAILURE DEDICATED MEASUREMENT INITIALIZATION REQUEST DEDICATED MEASUREMENT INITIALIZATION REPONSE LOCATION REPORTING CONTROL LOCATION REPORT
Iub
Iu
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. Figure 11-2 Example of CDT tracing result
----End
11-4
Issue 01 (2009-03-25)
11.2.5 Elementary Procedures of Positioning Based on CELLID +RTT

This describes the elementary procedures of positioning based on CELLID+RTT in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 11.2.5.1 UE Measurement Procedure The UE measurement procedure is performed for the RNC to request a report of attributes from the UE. 11.2.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.
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. Figure 11-3 UE measurement procedure
The procedure shown in Figure 11-3 is described as follows: 1. The SRNC sends a MEASUREMENT CONTROL message to the UE to request the UE to perform measurements based on the positioning method:
l
CELLID+RTT positioning method: UE Rx-Tx type 2 measurement (or UE Rx-Tx type 1 measurement, if the UE does not support the UE Rx-Tx type 2 measurement)
Issue 01 (2009-03-25)

l
OTDOA-IPDL positioning method: OTDOA type 2 measurements between the reference cell and the neighboring cells, and UE Rx-Tx type 2 measurement in the reference cell (if the UE is in CELL_DCH state) A-GPS positioning method: GPS pseudo-range measurement and Doppler measurement If the measurements are successful, the UE sends a MEASUREMENT REPORT message to report the measurement results. If the UE does not support the measurement requested by the SRNC or if the measurement results exceed the maximum number of criteria supported by the UE, the UE sends a MEASUREMENT CONTROL FAILURE message.
2.
The UE sends a response message to the SRNC.

l
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.
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. Figure 11-4 RTT measurement procedure
The procedure shown in Figure 11-4 is described as follows: 1. The CRNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message to the NodeB to request the NodeB to perform an RTT measurement. The measurement object varies with the positioning method as follows:
l l
CELLID+RTT positioning method: cells in the active set OTDOA-IPDL positioning method: reference cell
2.
11-6
The NodeB sends a response message to the CRNC.


l
If the measurement is successful, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION REPONSE message to report the measurement results. If the measurement requested by the CRNC fails to be initialized, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION FAILURE message to inform the CRNC of the failure.
11.3 Positioning Based on OTDOA-IPDL

When the OTDOA-IPDL positioning method is adopted, the location of a UE is identified based on the arrival time differences of CPICH signals from three inter-NodeB cells to the UE, which measures the differences. 11.3.1 Protocols Related to Positioning Based on OTDOA-IPDL The procedure of positioning based on OTDOA-IPDL complies with some 3GPP TS22, TS23, and TS25 protocols. 11.3.2 Triggering Conditions of Positioning Based on OTDOA-IPDL The CN initiates a positioning request and the RNC chooses the UE-assisted OTDOA-IPDL positioning method. 11.3.3 Signaling Procedure of Successful Positioning Based on OTDOA-IPDL This describes the signaling procedure of successful positioning based on OTDOA-IPDL. For the messages related to positioning failures, refer to the elementary procedures. 11.3.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELLID+RTT or OTDOA-IPDL. 11.3.5 Elementary Procedures of Positioning Based on OTDOA-IPDL This describes the elementary procedures of positioning based on OTDOA-IPDL in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
11.3.1 Protocols Related to Positioning Based on OTDOA-IPDL

The procedure of positioning based on OTDOA-IPDL complies with some 3GPP TS22, TS23, and TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS22.071 "Location Services (LCS)" 3GPP TS23.271 "Functional stage 2 description of LCS" 3GPP TS25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN)" 3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling" 3GPP TS25.433 "UTRAN Iub interface Node B Application Part (NBAP) signaling"
l l l
Issue 01 (2009-03-25)
11-7
11.3.2 Triggering Conditions of Positioning Based on OTDOAIPDL

The CN initiates a positioning request and the RNC chooses the UE-assisted OTDOA-IPDL positioning method. After receiving the positioning request from the CN, the RNC chooses the UE-assisted OTDOAIPDL 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.
11.3.3 Signaling Procedure of Successful Positioning Based on OTDOA-IPDL

This describes the signaling procedure of successful positioning based on OTDOA-IPDL. For the messages related to positioning failures, refer to the elementary procedures. Figure 11-5 shows the signaling procedure of successful positioning based on OTDOA-IPDL. Figure 11-5 Signaling procedure of successful positioning based on OTDOA-IPDL
l
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UE-assisted OTDOA-IPDL positioning method. If the UE is in CELL_DCH state, the SRNC performs the RTT measurement in the reference cell. 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.
11.3.4 Using the RNC LMT to Trace the Procedure of Positioning Based on CELLID+RTT or OTDOA-IPDL
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on CELLID+RTT or OTDOA-IPDL.
Prerequisite
l l
Context
Table 11-2 lists the messages to be traced. Table 11-2 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_MEAS_CTRL Uu RRC_MEAS_RPRT RRC_MEAS_CTRL_FAIL NBAP_DECIC_MEAS_INIT_ REQ NBAP_DECIC_MEAS_INIT_ RSP RANAP_LOCATION_REPO RTING_CONTROL RANAP_LOCATION_REPO RT Message Name in Protocols MEASUREMENT CONTROL MEASUREMENT REPORT MEASUREMENT CONTROL FAILURE DEDICATED MEASUREMENT INITIALIZATION REQUEST DEDICATED MEASUREMENT INITIALIZATION REPONSE LOCATION REPORTING CONTROL LOCATION REPORT
Iub
Iu
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. Figure 11-6 Example of CDT tracing result
----End
Issue 01 (2009-03-25)
11-9
11.3.5 Elementary Procedures of Positioning Based on OTDOAIPDL

This describes the elementary procedures of positioning based on OTDOA-IPDL in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 11.3.5.1 UE Measurement Procedure 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.
Procedure
l
CELLID+RTT positioning method: UE Rx-Tx type 2 measurement (or UE Rx-Tx type 1 measurement, if the UE does not support the UE Rx-Tx type 2 measurement)
11-10

l
OTDOA-IPDL positioning method: OTDOA type 2 measurements between the reference cell and the neighboring cells, and UE Rx-Tx type 2 measurement in the reference cell (if the UE is in CELL_DCH state) A-GPS positioning method: GPS pseudo-range measurement and Doppler measurement If the measurements are successful, the UE sends a MEASUREMENT REPORT message to report the measurement results. If the UE does not support the measurement requested by the SRNC or if the measurement results exceed the maximum number of criteria supported by the UE, the UE sends a MEASUREMENT CONTROL FAILURE message.
2.

l
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.
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. Figure 11-8 RTT measurement procedure
The procedure shown in Figure 11-8 is described as follows: 1. The CRNC sends a DEDICATED MEASUREMENT INITIALIZATION REQUEST message to the NodeB to request the NodeB to perform an RTT measurement. The measurement object varies with the positioning method as follows:
l l
CELLID+RTT positioning method: cells in the active set OTDOA-IPDL positioning method: reference cell
2.
Issue 01 (2009-03-25)
The NodeB sends a response message to the CRNC.


l
If the measurement is successful, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION REPONSE message to report the measurement results. If the measurement requested by the CRNC fails to be initialized, the NodeB sends a DEDICATED MEASUREMENT INITIALIZATION FAILURE message to inform the CRNC of the failure.
11.4 Positioning Based on A-GPS

When the A-GPS positioning method is adopted, the location of a UE is identified based on the GPS positioning-assistance data and GPS pseudo-range measurement results collected by the RNC. 11.4.1 Protocols Related to Positioning Based on A-GPS The procedure of positioning based on A-GPS complies with some 3GPP TS22, TS23, and TS25 protocols. 11.4.2 Triggering Conditions of Positioning Based on A-GPS The CN initiates a positioning request and the RNC chooses the UE-assisted A-GPS positioning method. 11.4.3 Signaling Procedure of Successful Positioning Based on A-GPS This describes the signaling procedure of successful positioning based on A-GPS. For the messages related to positioning failures, refer to the elementary procedures. 11.4.4 Using the RNC LMT to Trace the Procedure of Positioning Based on A-GPS The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on A-GPS. 11.4.5 Elementary Procedures of Positioning Based on A-GPS This describes the elementary procedures of positioning based on A-GPS in terms of triggering conditions and signaling procedures in normal and abnormal conditions.
11.4.1 Protocols Related to Positioning Based on A-GPS

The procedure of positioning based on A-GPS complies with some 3GPP TS22, TS23, and TS25 protocols. The compliance protocols are as follows:
l l l
3GPP TS22.071 "Location Services (LCS)" 3GPP TS23.271 "Functional stage 2 description of LCS" 3GPP TS25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN)" 3GPP TS25.331 "Radio Resource Control (RRC)" 3GPP TS25.413 "UTRAN Iu interface RANAP signalling"
l l
11.4.2 Triggering Conditions of Positioning Based on A-GPS

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

This describes the signaling procedure of successful positioning based on A-GPS. For the messages related to positioning failures, refer to the elementary procedures. Figure 11-9 shows the signaling procedure of successful positioning based on A-GPS. Figure 11-9 Signaling procedure of successful positioning based on A-GPS
l
The CN sends an authenticated LOCATION REPORTING CONTROL message to the SRNC, and the SRNC chooses the UE-assisted A-GPS positioning method. 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 AGPS, the SRNC performs location calculation. Then, the SRNC reports the positioning results to the CN through a LOCATION REPORT message.
11.4.4 Using the RNC LMT to Trace the Procedure of Positioning Based on A-GPS
The signaling tracing function of the RNC LMT can be used to trace the signaling procedure of positioning based on A-GPS.
Prerequisite
l l
Context
Issue 01 (2009-03-25)
11-13
Table 11-3 Messages to be traced Interface and Protocol to Be Traced Message Name on the LMT RRC_MEAS_CTRL Uu RRC_MEAS_RPRT RRC_MEAS_CTRL_FAIL RANAP_LOCATION_REPO RTING_CONTROL RANAP_LOCATION_REPO RT Message Name in Protocols MEASUREMENT CONTROL MEASUREMENT REPORT MEASUREMENT CONTROL FAILURE LOCATION REPORTING CONTROL LOCATION REPORT
Iu
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. Figure 11-10 Example of CDT tracing result
----End
11.4.5 Elementary Procedures of Positioning Based on A-GPS

This describes the elementary procedures of positioning based on A-GPS in terms of triggering conditions and signaling procedures in normal and abnormal conditions. 11.4.5.1 UE Measurement Procedure The UE measurement procedure is performed for the RNC to request a report of attributes from the UE.
Procedure
l
CELLID+RTT positioning method: UE Rx-Tx type 2 measurement (or UE Rx-Tx type 1 measurement, if the UE does not support the UE Rx-Tx type 2 measurement) OTDOA-IPDL positioning method: OTDOA type 2 measurements between the reference cell and the neighboring cells, and UE Rx-Tx type 2 measurement in the reference cell (if the UE is in CELL_DCH state) A-GPS positioning method: GPS pseudo-range measurement and Doppler measurement If the measurements are successful, the UE sends a MEASUREMENT REPORT message to report the measurement results. If the UE does not support the measurement requested by the SRNC or if the measurement results exceed the maximum number of criteria supported by the UE, the UE sends a MEASUREMENT CONTROL FAILURE message.
2.

l
Issue 01 (2009-03-25)
11-15

RAN Signaling Analysis Guide (RAN11.0 - 01)

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

RAN Signaling Analysis Guide (RAN11.0 - 01)

Diunggah oleh

Hak Cipta:

Format Tersedia

RAN 11.

Signalling Analysis Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

2 Cell Reconfiguration Procedure..............................................................................................2-1

3 Cell Deletion Procedure............................................................................................................3-1

4 Location Update Procedure......................................................................................................4-1

5 Outgoing Call Procedure..........................................................................................................5-1

6 Incoming Call Procedure..........................................................................................................6-1

7 Intra-Frequency Handover Procedure....................................................................................7-1

RAN Signalling Analysis Guide

8 Inter-Frequency Handover Procedure....................................................................................8-1

9 Inter-RAT Handover Procedure..............................................................................................9-1

10 SRNS Relocation Procedure.................................................................................................10-1

RAN Signalling Analysis Guide

11 Location Service Procedure..................................................................................................11-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

RAN Signalling Analysis Guide

RAN Signalling Analysis Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

About This Document

About This Document

Field engineers System engineers

About This Document

RAN Signalling Analysis Guide

RAN Signalling Analysis Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

RAN Signalling Analysis Guide

RAN Signalling Analysis Guide

About This Document

Action Click Double-click Drag

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

1 Cell Setup Procedure

Cell Setup Procedure

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1 Cell Setup Procedure

RAN Signalling Analysis Guide

1.1 Protocols Related to Cell Setup

1.2 Triggering Conditions of Cell Setup

1.3 Signaling Procedure of Successful Cell Setup

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

1 Cell Setup Procedure

Figure 1-1 Signaling procedure of successful cell setup

1 Cell Setup Procedure

RAN Signalling Analysis Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

RAN Signalling Analysis Guide

1 Cell Setup Procedure

Interface and Protocol to Be Traced

Message Name on the LMT NBAP_COMM_MEAS_RPR T

Message Name in Protocols