Documente Academic
Documente Profesional
Documente Cultură
1 Uu Protocol Structure..................................................................... 1.2.2 RRC Functions ............................................................................... 1.2.3 L2 Functions .................................................................................. 1.2.4 L1 Functions .................................................................................. 1.3 Iub interface ............................................................................................ 1.3.1 Iub Protocol Structure .................................................................... 1.3.2 Functions of NBAP ......................................................................... 1.3.3 NBAP Procedures .......................................................................... 1.3.4 Iub FP for Common Transport Channel Data Transfer .................. 1.3.5 Iub FP for Dedicated Transport Channel Data Transfer ................ 1.4 Iur Interface ............................................................................................ 1.4.1 Iur Protocol Structure ..................................................................... 1.4.2 Functions of RNSAP ...................................................................... 1.4.3 RNSAP Procedures ....................................................................... 1.4.4 Iur FP for Transport Channel Data Transfer .................................. 1.5 Iu Interface ............................................................................................. 1.5.1 Iu Protocol Architecture.................................................................. 1.5.2 Functions of RANAP ...................................................................... 1.5.3 RANAP Procedures ....................................................................... 1.5.4 Functions of Iu UP ......................................................................... 1.5.5 GTP-U ............................................................................................ 1.5.6 Functions of SABP ......................................................................... Chapter 2 Transport Network Layer Procedure Analysis ............................ 2.1 Overview ................................................................................................ 2.2 SAAL ...................................................................................................... 2.2.1 Overview ........................................................................................ 2.2.2 SSCOP .......................................................................................... 2.2.3 SSCF ............................................................................................. 2.2.4 CPCS ............................................................................................. 2.2.5 SAR................................................................................................ 2.2.6 LM .................................................................................................. 2.2.7 SSCOP Message ........................................................................... 2.3 MTP3-B .................................................................................................. 2.3.1 Overview ........................................................................................ 2.3.2 Function ......................................................................................... 2.3.3 Message Structure .........................................................................
1-1 1-1 1-2 1-2 1-4 1-5 1-6 1-6 1-6 1-8 1-8 1-10 1-14 1-18 1-18 1-19 1-20 1-22 1-22 1-22 1-25 1-26 1-28 1-33 1-33 2-1 2-1 2-1 2-1 2-2 2-7 2-8 2-8 2-9 2-10 2-11 2-11 2-12 2-14
2.3.4 Changeover/Changeback/ Management prohibit .......................... 2.3.5 Signaling Network Management and Status of Signaling Link ...... 2.3.6 Signaling Network Management and Signaling Route Status ....... 2.3.7 MTP3-B Upper User Message ....................................................... 2.3.8 MTP3-B Test Message .................................................................. 2.3.9 MTP3-B Management Message .................................................... 2.4 ALCAP .................................................................................................... 2.4.1 Overview ........................................................................................ 2.4.2 Function ......................................................................................... 2.4.3 Message structure ......................................................................... 2.4.4 Establish Request Message .......................................................... 2.5 SCCP ..................................................................................................... 2.5.1 Overview ........................................................................................ 2.5.2 Function ......................................................................................... 2.5.3 Message Structure ......................................................................... 2.5.4 Connection Request Message ....................................................... Chapter 3 Cell Related Procedure Analysis .................................................. 3.1 Overview ................................................................................................ 3.2 Procedures Involved in Cell Setup ......................................................... 3.2.1 Resource Status Indication Procedure .......................................... 3.2.2 Resource Audit Procedure ............................................................. 3.2.3 Cell Setup Procedure ..................................................................... 3.2.4 Common Transport Channel Setup Procedure.............................. 3.2.5 Iub Interface User Plane Setup ...................................................... 3.2.6 System Information Update ........................................................... 3.2.7 Common Measurement Initiation Procedure ................................. 3.2.8 Cell Reconfiguration Procedure ..................................................... 3.2.9 Cell Deletion Procedure ................................................................. 3.2.10 Resource Status Indication Message .......................................... 3.2.11 Audit Response Message ............................................................ 3.2.12 Cell Setup Request Message ...................................................... 3.2.13 Common Transport Channel Setup Request Message ............... 3.2.14 System Information Update Request Message ........................... 3.3 Example of Cell Setup Procedures ........................................................ Chapter 4 System Information Procedure Analysis ..................................... 4.1 Overview ................................................................................................ 4.1.1 System Information Structure ........................................................ 4.1.2 System Information Monitoring Mechanism ................................... 4.1.3 Functions of System Information ...................................................
2-19 2-20 2-22 2-23 2-24 2-25 2-26 2-26 2-27 2-29 2-30 2-31 2-31 2-32 2-33 2-34 3-1 3-1 3-1 3-1 3-2 3-3 3-4 3-4 3-5 3-5 3-6 3-7 3-7 3-12 3-16 3-20 3-25 3-28 4-1 4-1 4-1 4-2 4-2
4.2 System Information Broadcast and Update ............................................ 4.2.1 System Information Broadcast ....................................................... 4.2.2 System Information Update ........................................................... 4.2.3 System Information Message ........................................................ 4.3 System Information Modification ............................................................ 4.3.1 Modification by a value tag ............................................................ 4.3.2 Modification by a timer ................................................................... 4.3.3 Paging Type 1 Message ................................................................ Chapter 5 Call Setup and Release Procedure Analysis ............................... 5.1 Overview ................................................................................................ 5.2 Paging .................................................................................................... 5.2.1 Overview ........................................................................................ 5.2.2 Paging for UEs in Idle Mode or in PCH State ................................ 5.2.3 Paging for UEs in CELL_DCH or CELL_FACH State .................... 5.2.4 Paging Type 1 Message ................................................................ 5.2.5 Paging Type 2 Message ................................................................ 5.3 RRC Connection Setup .......................................................................... 5.3.1 Overview ........................................................................................ 5.3.2 RRC Connection Setup on Dedicated Channel ............................. 5.3.3 RRC Connection Setup on Common Channel ............................... 5.3.4 RRC Connection Reject ................................................................. 5.3.5 RRC Connection Request Message .............................................. 5.3.6 RRC Connection Setup Message .................................................. 5.3.7 RRC Connection Reject Message ................................................. 5.3.8 Radio Link Setup Request Message .............................................. 5.4 Direct Transfer Messages ...................................................................... 5.4.1 Overview ........................................................................................ 5.4.2 Initial Direct Transfer ...................................................................... 5.4.3 Uplink Direct Transfer .................................................................... 5.4.4 Downlink Direct Transfer ................................................................ 5.4.5 Initial Direct Transfer Message ...................................................... 5.4.6 Uplink Direct Transfer Message ..................................................... 5.4.7 Downlink Direct Transfer Message ................................................ 5.5 UE Capability Information ....................................................................... 5.5.1 UE Capability Enquiry .................................................................... 5.5.2 UE Capability Information Update .................................................. 5.6 RAB Setup .............................................................................................. 5.6.1 Overview ........................................................................................ 5.6.2 DCH-DCH ...................................................................................... 5.6.3 CCH-DCH ......................................................................................
4-3 4-3 4-3 4-4 4-6 4-7 4-7 4-7 5-1 5-1 5-1 5-1 5-2 5-3 5-3 5-4 5-5 5-5 5-6 5-7 5-7 5-8 5-10 5-13 5-14 5-18 5-18 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-25 5-26 5-26 5-27 5-30
5.6.4 CCH-CCH ...................................................................................... 5.6.5 RAB Assignment Request Message .............................................. 5.6.6 RAB Assignment Response Message ........................................... 5.6.7 Radio Bearer Setup Message ........................................................ 5.7 Call Release ........................................................................................... 5.7.1 Overview ........................................................................................ 5.7.2 Iu Signaling Connection Release ................................................... 5.7.3 RAB Release ................................................................................. 5.7.4 Combined Release of CS Domain Iu Signaling Link and RAB ...... 5.7.5 RRC Connection Release .............................................................. Chapter 6 Mobility Management Procedure Analysis .................................. 6.1 Overview ................................................................................................ 6.2 Forward handover .................................................................................. 6.2.1 Overview ........................................................................................ 6.2.2 Cell Update .................................................................................... 6.2.3 URA Update ................................................................................... 6.2.4 Cell Update Message..................................................................... 6.2.5 URA Update Message ................................................................... 6.3 Soft Handover ........................................................................................ 6.3.1 Overview ........................................................................................ 6.3.2 Radio Link Addition ........................................................................ 6.3.3 Radio Link Deletion ........................................................................ 6.3.4 Radio Link Addition and Deletion ................................................... 6.3.5 Radio Link Setup Request Message .............................................. 6.3.6 Active Set Update Message ........................................................... 6.4 Hard Handover ....................................................................................... 6.4.1 Overview ........................................................................................ 6.4.2 Compressed Mode ......................................................................... 6.4.3 Iur Interface Hard Handover .......................................................... 6.4.4 Combined Hard Handover ............................................................. 6.4.5 Radio Link Setup Request Message .............................................. 6.4.6 Physical Channel Reconfiguration Message ................................. 6.5 Inter-RAT Handover ............................................................................... 6.5.1 Overview ........................................................................................ 6.5.2 WCDMA->GSM Inter-RAT Handover ............................................ 6.5.3 GSM->WCDMA Inter-RAT Handover ............................................ 6.5.4 GSM/GPRS->WCDMA Cell Reselection ....................................... 6.5.5 WCDMA->GSM/GPRS Cell Reselection ....................................... 6.5.6 Handover from UTRAN Command Message................................. 6.5.7 Handover to UTRAN Command Message .....................................
5-32 5-33 5-36 5-38 5-43 5-43 5-44 5-45 5-47 5-48 6-1 6-1 6-1 6-1 6-1 6-3 6-4 6-6 6-8 6-8 6-9 6-10 6-12 6-13 6-13 6-15 6-15 6-16 6-17 6-19 6-22 6-22 6-24 6-24 6-25 6-27 6-29 6-29 6-32 6-33
6.6 Relocation .............................................................................................. 6.6.1 Overview ........................................................................................ 6.6.2 Static Relocation ............................................................................ 6.6.3 Relocation with Hard Handover ..................................................... 6.6.4 Relocation with Forward Handover ................................................ 6.6.5 Relocation Required Message ....................................................... 6.6.6 Relocation Request Message ........................................................ 6.6.7 Relocation Command Message ..................................................... 6.6.8 UTRAN Mobility Information Message ........................................... 6.6.9 Uplink Signaling Transfer Indication Message ............................... Chapter 7 Dynamic Resource Control Procedure Analysis ........................ 7.1 Overview ................................................................................................ 7.2 RAB Modification .................................................................................... 7.2.1 Overview ........................................................................................ 7.2.2 RAB Modification (DCH-DCH) ....................................................... 7.2.3 RAB Assignment Request Message .............................................. 7.2.4 Radio Bearer Reconfiguration Message ........................................ 7.3 Dynamic Channel Reconfiguration ......................................................... 7.3.1 Overview ........................................................................................ 7.3.2 RB Reconfiguration ........................................................................ 7.3.3 Radio Bearer Reconfiguration Message ........................................ Appendix A Tracing Tools .............................................................................. A.1 About Tracing Tools ............................................................................... A.1.1 RNC Tracing Tool .......................................................................... A.1.2 NodeB Tracing Tool ....................................................................... Appendix B Call Example ............................................................................... B.1 Overview ................................................................................................ B.2 Originating Call Procedure ..................................................................... B.3 Terminated Call procedure .................................................................... Appendix C Acronyms and Abbreviations .................................................... Index .................................................................................................................
6-35 6-35 6-35 6-39 6-41 6-42 6-45 6-46 6-49 6-51 7-1 7-1 7-1 7-1 7-1 7-3 7-3 7-6 7-6 7-7 7-8 A-1 A-1 A-1 A-1 B-1 B-1 B-1 B-4 C-1
HUAWEI
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Trademarks
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd. All other trademarks mentioned in this manual are the property of their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has been made in the preparation of this manual to ensure accuracy of the contents, but all statements, information, and recommendations in this manual do not constitute the warranty of any kind, express or implied.
Summary of Updates
This section provides the update history of this manual and introduces the contents of subsequent updates.
Update History
This manual is updated for a major product version to maintain consistency with system hardware or software versions and to incorporate customer suggestions. Manual Version T2-030223-20041001-C-1.22 Notes Initial commercial release
Updates of Contents
None
Organization
The manual analyzes protocols and signaling of radio access network in UMTS. There are 7 chapters and 3 appendixes in the manual. Chapter 1 UTRAN Interface Protocols and Functions profiles the interfaces, functions and the corresponding protocols in the radio access network of UMTS. The user planes of Iub/Iur/Iu interfaces are described in this chapter. Chapter 2 Transport Network Layer Procedure Analysis analyzes the signalling procedures of transport network layer and describes the functions of entities in the transport network signalling layer. Chapter 3 Cell Related Procedure Analysis analyzes the cell-related procedures, such as cell setup, common channel setup and a whole cell setup procedure example is presented. Chapter 4 System Information Procedure Analysis analyzes the system information procedures. Chapter 5 Call Setup and Release Procedure Analysis mainly analyzed the procedures of RRC connection setup and release, of RAB setup and release. Chapter 6 Mobility Management Procedure Analysis analyzes the procedures of forward handover, soft handover, hard handover, Inter-Rat handover and SRNS relocation. Chapter 7 Dynamic Resource Control Procedure Analysis analyzes the procedures of RAB modification and dynamic channel reconfiguration. Appendix A Tracing Tools introduce the message tracing tools. Appendix B Call Example presents a whole typical call procedure example. Appendix C Acronyms and Abbreviations
Intended Audience
The manual is intended for the following readers: Technical marketing specialists Operation and maintenance personnel
Conventions
The manual uses the following conventions:
I. General conventions
Convention Arial Arial Narrow Boldface Courier New Description Normal paragraphs are in Arial. Warnings, Cautions, Notes and Tips are in Arial Narrow. Headings are in Boldface. Terminal Display is in Courier New.
II. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:
Caution, Warning, Danger: Means reader be extremely careful during the operation. Note, Comment, Tip, Knowhow, Thought: Means a complementary description.
Table of Contents
Table of Contents
Chapter 1 UTRAN Interface Protocols and Functions............................................................... 1-1 1.1 Overview ............................................................................................................................ 1-1 1.2 Uu Interface ....................................................................................................................... 1-2 1.2.1 Uu Protocol Structure.............................................................................................. 1-2 1.2.2 RRC Functions ........................................................................................................ 1-4 1.2.3 L2 Functions............................................................................................................ 1-5 1.2.4 L1 Functions............................................................................................................ 1-6 1.3 Iub interface ....................................................................................................................... 1-6 1.3.1 Iub Protocol Structure ............................................................................................. 1-6 1.3.2 Functions of NBAP.................................................................................................. 1-8 1.3.3 NBAP Procedures ................................................................................................... 1-8 1.3.4 Iub FP for Common Transport Channel Data Transfer......................................... 1-10 1.3.5 Iub FP for Dedicated Transport Channel Data Transfer ....................................... 1-14 1.4 Iur Interface...................................................................................................................... 1-18 1.4.1 Iur Protocol Structure ............................................................................................ 1-18 1.4.2 Functions of RNSAP ............................................................................................. 1-19 1.4.3 RNSAP Procedures .............................................................................................. 1-20 1.4.4 Iur FP for Transport Channel Data Transfer ......................................................... 1-22 1.5 Iu Interface ....................................................................................................................... 1-22 1.5.1 Iu Protocol Architecture......................................................................................... 1-22 1.5.2 Functions of RANAP ............................................................................................. 1-25 1.5.3 RANAP Procedures .............................................................................................. 1-26 1.5.4 Functions of Iu UP................................................................................................. 1-28 1.5.5 GTP-U ................................................................................................................... 1-33 1.5.6 Functions of SABP ................................................................................................ 1-33 Chapter 2 Transport Network Layer Procedure Analysis ......................................................... 2-1 2.1 Overview ............................................................................................................................ 2-1 2.2 SAAL.................................................................................................................................. 2-1 2.2.1 Overview ................................................................................................................. 2-1 2.2.2 SSCOP.................................................................................................................... 2-2 2.2.3 SSCF....................................................................................................................... 2-7 2.2.4 CPCS ...................................................................................................................... 2-8 2.2.5 SAR ......................................................................................................................... 2-8 2.2.6 LM ........................................................................................................................... 2-9 2.2.7 SSCOP Message .................................................................................................. 2-10 2.3 MTP3-B............................................................................................................................ 2-11 2.3.1 Overview ............................................................................................................... 2-11
Table of Contents
2.3.2 Function................................................................................................................. 2-12 2.3.3 Message Structure ................................................................................................ 2-14 2.3.4 Changeover/Changeback/ Management prohibit ................................................. 2-19 2.3.5 Signaling Network Management and Status of Signaling Link ............................. 2-20 2.3.6 Signaling Network Management and Signaling Route Status .............................. 2-22 2.3.7 MTP3-B Upper User Message .............................................................................. 2-23 2.3.8 MTP3-B Test Message ......................................................................................... 2-24 2.3.9 MTP3-B Management Message ........................................................................... 2-25 2.4 ALCAP ............................................................................................................................. 2-26 2.4.1 Overview ............................................................................................................... 2-26 2.4.2 Function................................................................................................................. 2-27 2.4.3 Message structure................................................................................................. 2-29 2.4.4 Establish Request Message.................................................................................. 2-30 2.5 SCCP ............................................................................................................................... 2-31 2.5.1 Overview ............................................................................................................... 2-31 2.5.2 Function................................................................................................................. 2-32 2.5.3 Message Structure ................................................................................................ 2-33 2.5.4 Connection Request Message .............................................................................. 2-34 Chapter 3 Cell Related Procedure Analysis ............................................................................... 3-1 3.1 Overview ............................................................................................................................ 3-1 3.2 Procedures Involved in Cell Setup..................................................................................... 3-1 3.2.1 Resource Status Indication Procedure ................................................................... 3-1 3.2.2 Resource Audit Procedure ...................................................................................... 3-2 3.2.3 Cell Setup Procedure .............................................................................................. 3-3 3.2.4 Common Transport Channel Setup Procedure....................................................... 3-4 3.2.5 Iub Interface User Plane Setup ............................................................................... 3-4 3.2.6 System Information Update..................................................................................... 3-5 3.2.7 Common Measurement Initiation Procedure .......................................................... 3-5 3.2.8 Cell Reconfiguration Procedure .............................................................................. 3-6 3.2.9 Cell Deletion Procedure .......................................................................................... 3-7 3.2.10 Resource Status Indication Message ................................................................... 3-7 3.2.11 Audit Response Message ................................................................................... 3-12 3.2.12 Cell Setup Request Message.............................................................................. 3-16 3.2.13 Common Transport Channel Setup Request Message ...................................... 3-20 3.2.14 System Information Update Request Message .................................................. 3-25 3.3 Example of Cell Setup Procedures.................................................................................. 3-28 Chapter 4 System Information Procedure Analysis .................................................................. 4-1 4.1 Overview ............................................................................................................................ 4-1 4.1.1 System Information Structure.................................................................................. 4-1 4.1.2 System Information Monitoring Mechanism............................................................ 4-2 4.1.3 Functions of System Information............................................................................. 4-2 4.2 System Information Broadcast and Update....................................................................... 4-3
ii
Table of Contents
4.2.1 System Information Broadcast ................................................................................ 4-3 4.2.2 System Information Update..................................................................................... 4-3 4.2.3 System Information Message.................................................................................. 4-4 4.3 System Information Modification........................................................................................ 4-6 4.3.1 Modification by a value tag...................................................................................... 4-7 4.3.2 Modification by a timer ............................................................................................ 4-7 4.3.3 Paging Type 1 Message ......................................................................................... 4-7 Chapter 5 Call Setup and Release Procedure Analysis ............................................................ 5-1 5.1 Overview ............................................................................................................................ 5-1 5.2 Paging................................................................................................................................ 5-1 5.2.1 Overview ................................................................................................................. 5-1 5.2.2 Paging for UEs in Idle Mode or in PCH State ......................................................... 5-2 5.2.3 Paging for UEs in CELL_DCH or CELL_FACH State............................................. 5-3 5.2.4 Paging Type 1 Message ......................................................................................... 5-3 5.2.5 Paging Type 2 Message ......................................................................................... 5-4 5.3 RRC Connection Setup ..................................................................................................... 5-5 5.3.1 Overview ................................................................................................................. 5-5 5.3.2 RRC Connection Setup on Dedicated Channel ...................................................... 5-6 5.3.3 RRC Connection Setup on Common Channel........................................................ 5-7 5.3.4 RRC Connection Reject .......................................................................................... 5-7 5.3.5 RRC Connection Request Message ....................................................................... 5-8 5.3.6 RRC Connection Setup Message ......................................................................... 5-10 5.3.7 RRC Connection Reject Message ........................................................................ 5-13 5.3.8 Radio Link Setup Request Message..................................................................... 5-14 5.4 Direct Transfer Messages................................................................................................ 5-18 5.4.1 Overview ............................................................................................................... 5-18 5.4.2 Initial Direct Transfer ............................................................................................. 5-18 5.4.3 Uplink Direct Transfer ........................................................................................... 5-19 5.4.4 Downlink Direct Transfer....................................................................................... 5-20 5.4.5 Initial Direct Transfer Message ............................................................................. 5-21 5.4.6 Uplink Direct Transfer Message............................................................................ 5-22 5.4.7 Downlink Direct Transfer Message ....................................................................... 5-23 5.5 UE Capability Information ................................................................................................ 5-24 5.5.1 UE Capability Enquiry ........................................................................................... 5-25 5.5.2 UE Capability Information Update......................................................................... 5-25 5.6 RAB Setup ....................................................................................................................... 5-26 5.6.1 Overview ............................................................................................................... 5-26 5.6.2 DCH-DCH.............................................................................................................. 5-27 5.6.3 CCH-DCH.............................................................................................................. 5-30 5.6.4 CCH-CCH.............................................................................................................. 5-32 5.6.5 RAB Assignment Request Message ..................................................................... 5-33 5.6.6 RAB Assignment Response Message .................................................................. 5-36
iii
Table of Contents
5.6.7 Radio Bearer Setup Message ............................................................................... 5-38 5.7 Call Release..................................................................................................................... 5-43 5.7.1 Overview ............................................................................................................... 5-43 5.7.2 Iu Signaling Connection Release .......................................................................... 5-44 5.7.3 RAB Release......................................................................................................... 5-45 5.7.4 Combined Release of CS Domain Iu Signaling Link and RAB ............................. 5-47 5.7.5 RRC Connection Release ..................................................................................... 5-48 Chapter 6 Mobility Management Procedure Analysis ............................................................... 6-1 6.1 Overview ............................................................................................................................ 6-1 6.2 Forward handover.............................................................................................................. 6-1 6.2.1 Overview ................................................................................................................. 6-1 6.2.2 Cell Update.............................................................................................................. 6-1 6.2.3 URA Update ............................................................................................................ 6-3 6.2.4 Cell Update Message.............................................................................................. 6-4 6.2.5 URA Update Message ............................................................................................ 6-6 6.3 Soft Handover .................................................................................................................... 6-8 6.3.1 Overview ................................................................................................................. 6-8 6.3.2 Radio Link Addition ................................................................................................. 6-9 6.3.3 Radio Link Deletion ............................................................................................... 6-10 6.3.4 Radio Link Addition and Deletion .......................................................................... 6-12 6.3.5 Radio Link Setup Request Message..................................................................... 6-13 6.3.6 Active Set Update Message.................................................................................. 6-13 6.4 Hard Handover................................................................................................................. 6-15 6.4.1 Overview ............................................................................................................... 6-15 6.4.2 Compressed Mode................................................................................................ 6-16 6.4.3 Iur Interface Hard Handover.................................................................................. 6-17 6.4.4 Combined Hard Handover .................................................................................... 6-19 6.4.5 Radio Link Setup Request Message..................................................................... 6-22 6.4.6 Physical Channel Reconfiguration Message ........................................................ 6-22 6.5 Inter-RAT Handover......................................................................................................... 6-24 6.5.1 Overview ............................................................................................................... 6-24 6.5.2 WCDMA->GSM Inter-RAT Handover ................................................................... 6-25 6.5.3 GSM->WCDMA Inter-RAT Handover ................................................................... 6-27 6.5.4 GSM/GPRS->WCDMA Cell Reselection .............................................................. 6-29 6.5.5 WCDMA->GSM/GPRS Cell Reselection .............................................................. 6-29 6.5.6 Handover from UTRAN Command Message........................................................ 6-32 6.5.7 Handover to UTRAN Command Message............................................................ 6-33 6.6 Relocation ........................................................................................................................ 6-35 6.6.1 Overview ............................................................................................................... 6-35 6.6.2 Static Relocation ................................................................................................... 6-35 6.6.3 Relocation with Hard Handover ............................................................................ 6-39 6.6.4 Relocation with Forward Handover ....................................................................... 6-41
iv
Table of Contents
6.6.5 Relocation Required Message .............................................................................. 6-42 6.6.6 Relocation Request Message ............................................................................... 6-45 6.6.7 Relocation Command Message ............................................................................ 6-46 6.6.8 UTRAN Mobility Information Message.................................................................. 6-49 6.6.9 Uplink Signaling Transfer Indication Message...................................................... 6-51 Chapter 7 Dynamic Resource Control Procedure Analysis...................................................... 7-1 7.1 Overview ............................................................................................................................ 7-1 7.2 RAB Modification ............................................................................................................... 7-1 7.2.1 Overview ................................................................................................................. 7-1 7.2.2 RAB Modification (DCH-DCH) ................................................................................ 7-1 7.2.3 RAB Assignment Request Message ....................................................................... 7-3 7.2.4 Radio Bearer Reconfiguration Message ................................................................. 7-3 7.3 Dynamic Channel Reconfiguration .................................................................................... 7-6 7.3.1 Overview ................................................................................................................. 7-6 7.3.2 RB Reconfiguration ................................................................................................. 7-7 7.3.3 Radio Bearer Reconfiguration Message ................................................................. 7-8 Appendix A Tracing Tools............................................................................................................A-1 A.1 About Tracing Tools ..........................................................................................................A-1 A.1.1 RNC Tracing Tool ...................................................................................................A-1 A.1.2 NodeB Tracing Tool................................................................................................A-1 Appendix B Call Example .............................................................................................................B-1 B.1 Overview............................................................................................................................B-1 B.2 Originating Call Procedure ................................................................................................B-1 B.3 Terminated Call procedure................................................................................................B-4 Appendix C Acronyms and Abbreviations .................................................................................C-1 Index ................................................................................................................................................ i-1
Figure 1-1 UTRAN interfaces As shown in Figure 1-1, UTRAN interfaces in the UMTS system include Iub, Iur, Iu and Uu interfaces. See Table 1-1 for the description of the interfaces. Table 1-1 UTRAN interfaces Interface Uu Iub Iur Iu Description Logical interface between UTRAN and UE Logical interface between RNC and NodeB Logical interface between RNCs Logical interface between RNC and CN
1-1
Iub, Iur, Iu and Uu interfaces are standard interfaces and can be used to connect different network elements (NEs) from different vendors. Iub, Iur and Iu interfaces are also called as UTRAN terrestrial interfaces. According to the type of CN entity connected to RNC, the Iu interface can be classified into Iu-CS interface, Iu-PS interface and Iu-BC interface. Iu-CS interface is used to connect RNC and MSC. Iu-PS interface is used to connect RNC and SGSN. The Iu-BC interface is used to connect RNC and CBC.
1.2 Uu Interface
1.2.1 Uu Protocol Structure
Uu interface is the interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and it is the most important interface in the UMTS system. As shown in Figure 1-2, Uu interface includes three protocol layers, physical layer (L1), data link layer (L2) and network layer (L3). L1 provides the radio physical channels for the transmission of the traffic from upper layers. The functions of L1 are implemented by NodeB. L2 includes four sublayers, Medium Access Control (MAC), Radio Link Control (RLC), Broadcast/Multicast Control (BMC) and Packet Data Convergence Protocol (PDCP). The functions of L2 are implemented by RNC. L3 includes the RRC sublayer in the access stratum, the Mobility Management (MM) and Call Control (CC) in the non-access stratum. The RRC functions of L3 are implemented by RNC, and the MM and CC functions of L3 are implemented by CN.
1-2
GC
Nt
control
L3
Radio Bearers PDCP PDCP
L2/PDCP
BMC
L2/BMC
RLC RLC
RLC
RLC
L2/RLC
L2/MAC
Transport Channels
PHY
L1
Figure 1-2 Uu interface protocol stack Uu interface specifications are shown in Figure 1-3.
1-3
GC
Nt
DC
Duplication avoidance GC C-plane signalling Nt DC U-plane information control TS25.331 TS25.323 UuS boundary
L3 L2/PDCP L2/BMC
control
control
control
control
TS25.324
RLC RLC
RLC
RLC
L2/RLC
L2/MAC
Transport Channels
TS25.211~TS25.215
L1
Arbitration of radio resources on uplink DCH; RRC message integrity protection; CBS control.
1.2.3 L2 Functions
L2 includes four sublayers, Medium Access Control (MAC), Radio Link Control (RLC), Broadcast/Multicast Control (BMC) and Packet Data Convergence Protocol (PDCP).
I. MAC
The functions of MAC include: Mapping between logical channels and transport channels Selection of appropriate Transport Format for each Transport Channel Priority handling between data flows of one UE Priority handling between UEs by means of dynamic scheduling Priority handling between data flows of several users on FACH Identification of UEs on common transport channels Multiplexing/demultiplexing of upper layer PDUs into/from transport blocks delivered to/from the physical layer on common transport channels Traffic volume measurement Transport Channel type switching Ciphering for transparent mode RLC Access Service Class selection
II. RLC
The functions of RLC include: Segmentation and reassembly, concatenation, padding and transfer of user data. Flow control Error correction, in-sequence delivery of upper layer PDUs and duplicate detection Sequence numbers check Protocol error detection and recovery Ciphering Suspend/resume function
III. PDCP
The functions of PDCP include: Header compression and decompression of IP data streams at the transmitting and receiving entity respectively. Transfer of user data
1-5
Forward the PDCP-SDU from non-access stratum to RLC, and multiplex different RBs to the same RLC entity.
IV. BMC
The functions of BMC include: Storage of Cell Broadcast Messages Traffic volume monitoring and radio resource request for CBS Scheduling of BMC messages Transmission of BMC messages to UE Delivery of Cell Broadcast messages to upper layer (NAS)
1.2.4 L1 Functions
The functions of L1 (physical layer) mainly includes: Measurements and indication to higher layers (e.g. FER, SIR, interference power, transmission power, etc) Macro-diversity distribution/combining and soft handover execution; Frequency and time (chip, bit, slot, frame) synchronization; Closed-loop power control; RF processing; Multiplexing of transport channels and demultiplexing of coded composite transport channels; Mapping of coded composite transport channels on physical channels; Modulation and spreading/demodulation and despreading of physical channels; The detailed functions and relevant specifications of L1 are involved with the basic principles of W-CMDA which is out of the range of this manual. Refer to relevant protocols for the details.
1-6
Radio Network Control Plane Node B Application Part (NBAP) Transport Network Control Plane ALCAP Q.2630.1 Q.2150.2 SSCF-UNI SSCOP AAL Type 5 SSCF-UNI SSCOP AAL Type 5 ATM Physical Layer
Transport Layer
AAL Type 2
Figure 1-4 Protocol Stack of Iub interface Iub interface specifications are shown in Figure 1-5.
User Plane
Dedicated Channels Common Channels
TS 25.427
TS 25.435
Transport Layer
NBAP Transport
TS 25.426
(Dedicated Channel Transport) Dedicated Channel Transport Common Channel Transport
TS 25.432
TS 25.434
TS 25.426
TS 25.434
Figure 1-5 Iub interface specifications In this section, only the functions and procedures of radio network layer are given. For the transport layer, refer to Chapter 2 Transfer Network Layer Procedure Analysis. The radio network user plane of Iub interface is to transfer the data between RNC and NodeB. The plane is implemented by means of Frame Protocol (FP) of transport
1-7
channels. According to the type of transported data, the FP can be classified as FP for common transport channel and FP for Dedicated transport channel.
1-8
NBAP common procedures are procedures that request initiation of a UE context for a specific UE in NodeB or are not related to a specific UE. NBAP common procedures also incorporate logical O&M procedures. NBAP dedicated procedures are procedures that are related to a specific UE context in NodeB. This UE context is identified by a UE context identity. The two types of procedures may be carried on separate signaling links.
Configuration Alignment
1-9
Table 1-3 Mapping between functions and NBAP dedicated procedures Function Radio Link Management. Dedicated Procedure(s) a) Radio Link Addition b) Radio Link Deletion c) Unsynchronized Radio Link Reconfiguration d) Synchronized Radio Link Reconfiguration Preparation e) Synchronized Radio Link Reconfiguration Commit f) Synchronized Radio Link Reconfiguration Cancellation g) Radio Link Pre-emption Radio Link Supervision. Compressed Mode Control a) Radio Link Failure b) Radio Link Restoration a) Radio Link Setup b) Radio Link Addition c) Compressed Mode Command d) Unsynchronized Radio Link Reconfiguration e) Synchronized Radio Link Reconfiguration Preparation f) Synchronized Radio Link Reconfiguration Commit g) Synchronized Radio Link Reconfiguration Cancellation a) Dedicated Measurement Initiation b) Dedicated Measurement Reporting c) Dedicated Measurement Termination d) Dedicated Measurement Failure Downlink Power Control Error Indication
1-10
The procedure is realized by a transmission of Data Frame from NodeB to CRNC, as shown in Figure 1-6.
NodeB
RACH Data Frame
CRNC
NodeB
FACH Data Frame
CRNC
CRNC
1-11
TheT1, T2, T3 parameters are defined as: T1: RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. T2: NodeB specific frame number (BFN) that indicates the time when NodeB receives the correspondent DL Node synchronization frame through the SAP from the transport layer. T3: NodeB specific frame number (BFN) that indicates the time when NodeB sends the frame through the SAP to the transport layer.
1-12
NodeB
DL Synchronization UL Synchronization
CRNC
CRNC
.
Figure 1-11 FACH and PCH Timing Adjustment procedure
The arrival window and the time of arrival are defined as follows:
Time of Arrival Window Endpoint (ToAWE): ToAWE represents the time point
by which the DL data shall arrive to the NodeB from Iub. The ToAWE is defined as the amount of milliseconds before the last time point from which a timely DL transmission for the identified CFN would still be possible taking into account the NodeB internal delays. ToAWE is set via control plane. If data does not arrive before ToAWE a Timing Adjustment Control Frame shall be sent by NodeB.
Time of Arrival Window Startpoint (ToAWS): ToAWS represents the time after
which the DL data shall arrive to the NodeB from Iub. The ToAWS is defined as the amount of milliseconds from the ToAWE. ToAWS is set via control plane. If data arrives before ToAWS a Timing Adjustment Control Frame shall be sent by NodeB.
Time of Arrival (ToA): ToA is the time difference between the end point of the DL
arrival window (ToAWE) and the actual arrival time of DL frame for a specific CFN. A positive ToA means that the frame is received before the ToAWE, a negative ToA means that the frame is received after the ToAWE.
1-13
NodeB
UL Data Frame
SRNC
Uplink Data Transfer procedure is used to transfer data from NodeB to SRNC. The procedure is realized by a transmission of UL Data Frame from NodeB to SRNC, as shown in Figure 1-12. Two modes can be used for the UL transmission: normal mode and silent mode. The mode is selected by the SRNC when the transport bearer is set up and signalled to the NodeB with the relevant control plane procedure. In normal mode, the NodeB shall always send an UL Data Frame to the RNC for all the DCHs in a set of coordinated DCHs regardless of the number of Transport Blocks of the DCHs. In silent mode and in case only one transport channel is transported on a transport bearer, the NodeB shall not send an UL Data Frame to the RNC when it has received a TFI indicating number of TB equal to 0 for the transport channel during a TTI. In silent mode and in case of coordinated DCHs, when the NodeB receives a TFI indicating number of TB equal to 0 for all the DCHs in a set of coordinated DCHs, the NodeB shall not send an UL data frame to the RNC for this set of coordinated DCHs.
1-14
NodeB
DL Data Frame
SRNC
Downlink Data Transfer procedure is used to transfer data from SRNC to NodeB. The procedure is realized by a transmission of DL Data Frame from SRNC to NodeB, as shown in Figure 1-13. The NodeB shall consider a transport bearer synchronized only after it has received at least one data frame on this transport bearer before the latest time of arrival (LTOA). The NodeB shall consider the DL user plane for a certain RL synchronized if all transport bearers established for carrying DL DCH data frames for this RL are synchronized. Only when the DL user plane is considered synchronized, the NodeB shall transmit the data on the DL DPDCH. When the DL user plane is considered synchronized and the NodeB does not receive a valid DL Data Frame in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the following cases: If the NodeB is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. When combining the TFIs of the different transport channels, a valid TFCI might result and in this case data shall be transmitted on Uu. If the NodeB is not aware of a TFI value corresponding to zero bits for this transport channel or if combining the TFI corresponding to zero bits with other TFIs, results in an unknown TFI combination, the handling will be different. In the former case, at each radio frame, the NodeB shall build the TFCI value of each CCTrCH, according to the TFI of the DCH data frames multiplexed on this CCTrCH. In the latter case, NodeB shall transmit only the DPCCH without TFCI bits.
1-15
The procedure is realized by a transmission of Outer Loop PC control frame from SRNC to NodeB, as shown in Figure 1-14. The Outer Loop PC control frame can be sent via any of the transport bearers dedicated to one UE. Based, for example, on the CRC Indicator (CRCI) values and on the quality estimate in the UL frames, SRNC modifies the SIR target used by the UL Inner Loop Power Control by including the absolute value of the new SIR target in the Outer Loop PC control frame sent to the NodeB's. At the reception of the Outer Loop PC control frame, the NodeB shall immediately update the SIR target used for the inner loop power control with the specified value.
NodeB
Outer Loop PC
SRNC
NodeB
SRNC
V. Node Synchronization
Node synchronization procedure is to obtain the round trip delay (RTD) of the transmission between information entities over the Iub interface.
1-16
In the Node Synchronization procedure, the SRNC sends a DL Node Synchronization control frame to NodeB containing the parameter T1. Upon reception of a DL Node Synchronization control frame, the NodeB shall respond with UL Node Synchronization control frame, indicating t2 and t3, as well as t1 which was indicated in the initiating DL Node Synchronization control frame, as shown in Figure 1-16.
NodeB SRNC
The T1, T2, T3 parameters are defined as: T1: RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. T2: NodeB specific frame number (BFN) that indicates the time when NodeB receives the correspondent DL synchronization frame through the SAP from the transport layer. T3: NodeB specific frame number (BFN) that indicates the time when NodeB sends the frame through the SAP to the transport layer.
1-17
NodeB
DL Synchronization UL Synchronization
SRNC
NodeB
Timing Adjustment
SRNC
1-18
Control Plane RNSAP Transport Network Control Plane ALCAP(Q.2630.1) STC (Q.2150.1) MTP3-B SSCF-NNI SSCOP AAL5 ATM Physical Layer
AAL2
TS 25.427
TS 25.425
Transport Signaling
Transport Layer
Signalling Transport
TS 25.426
(Dedicated Channel Transport) Dedicated Channel Transport Common Channel Transport
TS 25.424
(Common Channel Transport) Physical LayerTS 25.421
TS 25.422
TS 25.426
TS 25.424
Physical Channel Reconfiguration. This function allows the DRNC to reallocate the physical channel resources for a Radio Link; Radio Link Supervision. This function allows the DRNC to report failures and restorations of a Radio Link; Compressed Mode Control. This function allows the SRNC to control the usage of compressed mode within a DRNS; Measurements on Dedicated Resources. This function allows the SRNC to initiate measurements on dedicated resources in the DRNS. The function also allows the DRNC to report the result of the measurements; DL Power Drifting Correction. This function allows the SRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links; CCCH Signaling Transfer. This function allows the SRNC and DRNC to pass information between the UE and the SRNC on a CCCH controlled by the DRNS; Paging. This function allows the SRNC to page a UE in a URA or a cell in the DRNS; Relocation Execution. This function allows the SRNC to finalise a Relocation previously prepared via other interfaces; Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined.
1-20
Elementary Procedure
Initiating Message
Response message Successful Outcome Unsuccessful Outcome RADIO LINK RECONFIGURATION FAILURE PHYSICAL CHANNEL RECONFIGURATION FAILURE DEDICATED MEASUREMENT INITIATION FAILURE COMMON TRANSPORT CHANNEL RESOURCES FAILURE
Unsynchronised Radio Link Reconfiguration Physical Channel Reconfiguration Dedicated Measurement Initiation Common Transport Channel Resources Initialisation
RADIO LINK RECONFIGURATION REQUEST PHYSICAL CHANNEL RECONFIGURATION REQUEST DEDICATED MEASUREMENT INITIATION REQUEST COMMON TRANSPORT CHANNEL RESOURCES REQUEST
RADIO LINK RECONFIGURATION RESPONSE PHYSICAL CHANNEL RECONFIGURATION COMMAND DEDICATED MEASUREMENT INITIATION RESPONSE COMMON TRANSPORT CHANNEL RESOURCES RESPONSE
Table 1-5 Class 2 Elementary Procedures Elementary Procedure Uplink Signalling Transfer Downlink Signalling Transfer Relocation Commit Paging Synchronised Radio Link Reconfiguration Commit Synchronised Radio Link Reconfiguration Cancellation Radio Link Failure Radio Link Restoration Dedicated Measurement Reporting Dedicated Measurement Termination Dedicated Measurement Failure Downlink Power Control Compressed Mode Command Common Transport Channel Resources Release Error Indication Radio Link Pre-emption Initiating Message UPLINK SIGNALLING TRANSFER INDICATION DOWNLINK SIGNALLING TRANSFER REQUEST RELOCATION COMMIT PAGING REQUEST RADIO LINK RECONFIGURATION COMMIT RADIO LINK RECONFIGURATION CANCEL RADIO LINK FAILURE INDICATION RADIO LINK RESTORE INDICATION DEDICATED MEASUREMENT REPORT DEDICATED MEASUREMENT TERMINATION REQUEST DEDICATED MEASUREMENT FAILURE INDICATION DL POWER CONTROL REQUEST COMPRESSED MODE COMMAND COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST ERROR INDICATION RADIO LINK PREEMPTION REQUIRED INDICATION
1-21
data transfer. Iur FP for dedicated transport channel data transfer and Iub FP for dedicated transport channel data transfer are both specified in 3GPP TS25.427 protocol. Refer to 1.3.5 Iub
FP for dedicated Transport Channel Data Transfer for the Iur FP for dedicated
1.5 Iu Interface
1.5.1 Iu Protocol Architecture
Iu interface is the interface between UTRAN and CN. The Iu interface that connects with CS domain of CN is called as Iu-CS whose protocol stack is shown in Figure 1-21 ; The Iu interface that connects with PS domain of CN is called as Iu-PS whose protocol stack is shown in Figure 1-22; The Iu interface that connects with BC domain of CN is called as Iu-BC whose protocol stack is shown in Figure 1-23.
1-22
Control Plane RANAP Transport Network Control Plane Q.2630.1 Q.2150.1 MTP3-B SSCF-NNI SSCOP AAL5 ATM Physical Layer
AAL2
SCCP MTP3-B SSCF-NNI SSCOP AAL5 ATM Physical Layer GTP-U UDP IP AAL5 ATM Physical Layer
1-23
TCP IP AAL5
1-24
25.413
25.412
25.414
25.411
Controlling overload in the Iu interface. This function allows adjusting the load in the Iu interface. Resetting the Iu. This function is used for resetting an Iu interface. Sending the UE Common ID (permanent NAS UE identity) to the RNC. This function makes the RNC aware of the UE's Common ID. Paging the user. This function provides the CN for capability to page the UE. Controlling the tracing of the UE activity. This function allows setting the trace mode for a given UE. This function also allows the deactivation of a previously established trace. Transport of NAS information between UE and CN. This function has two sub-classes: Sub-class1: Transport of the initial NAS signalling message from the UE to CN. This function transfers transparently the NAS information. As a consequence also the Iu signalling connection is set up. Sub-class2: Transport of NAS signalling messages between UE and CN, This function transfers transparently the NAS signalling messages on the existing Iu signalling connection. It also includes a specific service to handle signalling messages differently. Controlling the security mode in the UTRAN. This function is used to send the security keys (ciphering and integrity protection) to the UTRAN, and setting the operation mode for security functions. Controlling location reporting. This function allows the CN to operate the mode in which the UTRAN reports the location of the UE. Location reporting. This function is used for transferring the actual location information from RNC to the CN. Data volume reporting function. This function is responsible for reporting unsuccessfully transmitted DL data volume over UTRAN for specific RABs. Reporting general error situations.
1-26
Table 1-6 Class 1 elementary procedures Elementary Procedure Initiating Message Response message Successful Outcome Iu Release Relocation Preparation Relocation Resource Allocation Relocation Cancel SRNS Context Transfer Security Mode Control Data Volume Report Reset Reset Resource IU RELEASE COMMAND RELOCATION REQUIRED RELOCATION REQUEST RELOCATION CANCEL SRNS CONTEXT REQUEST SECURITY MODE COMMAND DATA VOLUME REPORT REQUEST RESET RESET RESOURCE IU RELEASE COMPLETE RELOCATION COMMAND RELOCATION REQUEST ACKNOWLEDGE RELOCATION CANCEL ACKNOWLEDGE SRNS CONTEXT RESPONSE SECURITY MODE COMPLETE DATA VOLUME REPORT RESET ACKNOWLEDGE RESET RESOURCE ACKNOWLEDGE SECURITY MODE REJECT RELOCATION PREPARATION FAILURE RELOCATION FAILURE Unsuccessful Outcome
Table 1-7 Class 2 elementary procedures Elementary Procedure RAB Release Request Iu Release Request Relocation Detect Relocation Complete SRNS Data Forwarding Initiation SRNS Context Forwarding from Source RNC to CN SRNS Context Forwarding to Target RNC from CN Paging Common ID CN Invoke Trace CN Deactivate Trace Location Reporting Control Location Report Message RAB RELEASE REQUEST IU RELEASE REQUEST RELOCATION DETECT RELOCATION COMPLETE SRNS DATA FORWARD COMMAND FORWARD SRNS CONTEXT FORWARD SRNS CONTEXT PAGING COMMON ID CN INVOKE TRACE CN DEACTIVATE TRACE LOCATION REPORTING CONTROL LOCATION REPORT
1-27
Elementary Procedure Initial UE Message Direct Transfer Overload Control Error Indication
Table 1-8 Class 3 elementary procedures Elementary Procedure RAB Assignment Initiating Message RAB ASSIGNMENT REQUEST Response Message RAB ASSIGNMENT RESPONSE x N (N>=1)
1.5.4 Functions of Iu UP
Iu UP is located in the User plane of the Radio Network layer over the Iu interface and used to convey user data associated to Radio Access Bearers. One Iu UP protocol instance is associated to one RAB only. Iu UP protocol instances exist at Iu access point i.e. at CN and UTRAN. Whenever a RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established, relocated and released together with the associated RAB procedures. The Iu UP includes two modes of operation: Transparent Mode (TrM) and Support Mode for predefined SDU size (SMpSDU). Transparent mode (TrM) The transparent mode is intended for those RABs that do not require any particular feature from the Iu UP protocol other than transfer of user data. Figure 1-25 illustrates the transparent mode of Iu UP protocol layer.
1-28
TNL-SAP
TNL-SAP
In this mode, the Iu UP protocol instance does not perform any Iu UP protocol information exchange with its peer over the Iu interface. The Iu UP protocol layer is used for PDUs transfer between upper layers and transport network layer. For instance, Iu UP of Iu-PS adopts transparent mode. Support mode The support modes are intended for those RABs that require particular features from the Iu UP protocol in addition to transfer of user data. When operating in a support mode, the peer Iu UP protocol instances exchange Iu UP frames. Figure 1-26 illustrates the support mode of Iu UP protocol layer.
Iu RNL-SAP CN Non Access Stratum Access Stratum Iu UP layer (support mode) Radio Interface Protocols Support Mode Functions Transfer of Iu UP protocol frames Iu UP layer (support mode) Support Mode Functions
UTRAN
TNL-SAP
TNL-SAP
The only support mode which has been defined is the Support mode for predefined SDU size (SMpSDU). For instance, the transfer of AMR speech PDUs would utilize SMpSDU.
1-29
CN/ RNC
1-30
RNC
*
CN/other
The requested Iu UP protocol layer entity in the peer node adjusts the transmission timing by the amount as indicated by SRNC. If the time alignment frame is correctly formatted and treated by the receiving Iu UP protocol layer and the time alignment is treated correctly by the upper layers, this latter sends a time alignment acknowledgement frame. Upon reception of a time alignment acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer TTA. If CN can not handle the time alignment frame, it will send NACK frame to RNC, indicating the causes. The RNC will decide to send the time alignment frame or not according to the causes and stop the timer TTA.
RNC
User data with bad timing Time Alignment ACK User data with adjusted timing
CN
V. Error Event
Error event procedure is to handle the error reporting. Over the Iu UP protocol the error reports are made with Error event frames as shown in in Figure 1-31,The Error event procedure in the Iu UP can be triggered by: An error detected by the Iu UP functions A request by the upper layers When an Error event is reported by an Error event frame the following information shall be included: A cause value Error distance (=0 if Iu UP function detected, =1 if requested by upper layers).
1-32
RNC/ CN or other
Error event (Cause value, Error distance)
CN or other/ RNC
CN/RNC
1.5.5 GTP-U
The function of GTP-U (GPRS Tunnel Protocol User Plane) is to transfer Iu-PS user data through tunnel protocol. In addition, it also includes the user plane auxiliary signaling such as error indication of data transferring, handshaking message and supported extension head list.
1-33
Message Handling. This function is responsible for the broadcast of new messages, amend existing broadcasted messages and to stop the broadcasting of specific messages. Load Handling. This function is responsible for determining the loading of the broadcast channels at any particular point in time. Reset. This function permits the CBC to end broadcasting in one or more Service Areas. Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined.
1-34
2.2 SAAL
2.2.1 Overview
Signaling adaptation is required for the transmission of signaling messages in the ATM network, that is, signaling messages in various formats in the upper layer shall be converted into the messages of format that can be transmitted in the ATM network. These functions can be accomplished by the SAAL layer.
NBAP SAAL SSCS SSCF AT UNI SSCF AT NNI STC MTP3-B
SSCOP CP
LM
CPCS SAR
Figure 2-1 SAAL Structure The structure of SAAL in BSC6800 is illustrated in Figure 2-1. The SAAL comprises the following parts:
2-1
Service Specification Convergence Sublayer (SSCS), which includes SSCF (Service Specific Coordination Function), SSCOP (Service Specific Connection Oriented Protocol). Common Part (CP). CP adopts AAL type 5 as adaptation layer and comprises two parts: CPCS and SAR. Layer Management (LM).
Note: For details about SSCF, refer to ITU-T Q.2140. For details about SSCOP, refer to ITU-T Q.2110. For details about LM, refer to ITU-T Q.2144.
2.2.2 SSCOP
I. Overview
SSCOP provides the transmission of information and control information between two peer to peer entities.
II. Function
The SSCOP performs the following functions. Sequence Integrity. This function preserves the order of SSCOP SDUs that were submitted for transfer by SSCOP. Error Correction by Selective Retransmission. Through a sequencing mechanism, the receiving SSCOP entity can detect missing SSCOP SDUs. This function corrects sequence errors through retransmission. Flow Control. This function allows an SSCOP receiver to control the rate at which the peer SSCOP transmitter entity may send information. Error Reporting to Layer Management. This function indicates to layer management errors which have occurred. Keep Alive. This function verifies that the two peer SSCOP entities participating in a connection are remaining in a link connection established state even in the case of a prolonged absence of data transfer. Local Data Retrieval. This function allows the local SSCOP user to retrieve in-sequence SDUs which have not yet been released by the SSCOP entity. Connection Control. This function performs the establishment, release, and resynchronization of an SSCOP connection. It also allows the transmission of variable length user-to-user information without a guarantee of delivery.
2-2
Transfer of User-Data. This function is used for the conveyance of user data between users of the SSCOP. SSCOP supports both assured and unassured data transfer. Protocol Error Detection and Recovery. This function detects and recovers from errors in the operation of the protocol. Status Reporting. This function allows the transmitter and receiver peer entities to exchange status information. SSCOP data units are the message units transmitted between SSCOP peer layers for connection setup and release, and for message reliable transmission. They include the following basic message units. BGN PDU (Begin), used to set up connection between two peer SSCOP entities. It requests the peer SSCOP to clear data in the transmitter and receiver buffers, to perform initialization of state variables and receiving/sending counters. BGAK PDU (Begin Acknowledge), used to acknowledge the connection request from the peer end. BGREJ PDU (Begin Reject), used to reject the connection request from the peer SSCOP entity. END PDU (End), used to release the connection between the two ends in communication. ENDAK PDU (End Acknowledge), used to acknowledge the release action. RS PDU (Resynchronization), used to resynchronize the buffers and data transfer state variables. RSAK PDU (Resynchronization Acknowledge), used to acknowledge the resynchronization request originated from the peer entity. ER PDU (Error Recovery), used to recover errors in connection action. ERAK PDU (Error Recovery Acknowledge), used to acknowledge the recovery request. SD PDU (Sequenced Data), used to send user service data to the peer entity after SSCOP connection has been set up. POLL PDU (Status Request), used to request status information of the peer SSCOP after SSCOP connection setup. STAT PDU (Solicited Status Response), used as the response for POLL PDU. It is used to notify which SD PDUs have been received and which have not. It is also used to update the location of sending window so as to control the sending sequence No. of the max. SD PDU. The STAT PDU also includes the sending SN of the POLL PDU(N(PS)), which is used as the response to the POLL PDU. USTAT PDU (Unsolicited Status Response). It is sent by the receiving end to inform the peer end resending the lost SD PDUs when the receiving end detects loss of SD PDUs after comparing the receiving SN of SD PDU. The USTAT PDU also contains data for updating sending window of the peer end, but contains no N(PS) segment.
2-3
Unnumbered Data (UD). UD are transmitted between peer SSCOP users. The in-progress connection oriented sequencing will not be affected, no counter or status between the two entities will be altered, and no data will be retransmitted if they get lost. Management Data (MD). Unnumbered MD is transmitted between two SSCOP management entities. Similar to UD PDUs, no reliable receiving of the peer end is guaranteed.
2-4
AA-ESTABLISH.req
AA-ESTABLISH.con.
PDU BGAK
AA-ESTABLISH.rsp.
2-5
AA-RELEASE.indication
Note: The odd element (the value is 3) represents a PDU within a certain loss interval, while the even element represents the first PDU in the next sequence properly received.
2-6
POLL(5,1)
1 2 X X
X X
Free 1, 2
X X 7
2.2.3 SSCF
I. Overview
As shown in Figure 2-1, the SSCF functions as the adaptation layer of the SSCOP and the upper layer applications. Upper layer applications include NBAP, MTP3-B and Signal Transport Convert (STC). The MTP3-B is used for Network to network interface (NNI), which has higher link quality. SAAL is required to support link quality check and to help the MTP3-B with link switchover. However, NBAP is used for User to Network Interface (UNI), which has poorer link quality and greater delay. Therefore, SSCF is divided into SSCF-NNI and SSCF-UNI to cater to different upper layer applications. SSCF-NNI is used for adapting SSCOP and upper layer MTP3-B. It maps the primitive from MTP3-B to SSCOP signal as required, or reversely. SSCF-NNI acts as a medium for signal transferring between SSCOP and MTP3-B. SSCF does not send PDUs to the peer SSCF of the receiver. It transfers its information through the SSCOP PDU. Besides primitive mapping, SSCF-NNI also implements local data retrieval, link state maintenance and link quality check functions. It reports link information to layer management. SSCF-UNI is used for adapting SSCOP or upper layer NBAP or STC. It implements error-free sequential data transmission by use of SSCOP. Similar to SSCF-NNI, it maps the primitive from NBAP/STC to SSCOP signal as required. It differs from SSCF-NNI in that it does not implement link alignment and data retrieval functions. SSCF-UNI accomplishes primitive mapping, SAAL link setup and release, and data transmission acknowledgement.
II. Function
The SSCF performs the following functions. Primitive mapping. SSCF maps the primitive from MTP3-B to SSCOP signals as required, or reversely.
2-7
Local data retrieval. SSCF retrieves data that have not been sent in the links when the links get faulty or switched over, and sends the data to other links for transmission. Flow control. SSCF reports to the user the congestion level (or no congestion) to prevent the loss of cells. It also adjusts certain PDU flow to the lower layer to prevent congestion of the peer end. Link state maintenance. According to the primitive received from MTP3-B and SSCOP, SSCF maintains information about link states, such as Out Of Service and In Service. Using the information, it can provide primitives/signals to MTP3-B and SSCOP to help with link management. Layer management report. SCCF sends MAAL primitive to LM, for example, SSCF reports link fault to LM when one link gets faulty. It monitors errors with the help of LM. Link alignment.
2.2.4 CPCS
CPCS-PDU Payload
UU 8 bits
CPI 8 bits
LI 16 bits
CRC 32 bits
CPCS-PDU Tail
Figure 2-5 CPCS-PDU format CPCS-PDU format is shown in Figure 2-5, including three parts, CPCS-PDU payload, PAD and PCS-PDU tail. The length of CPCS-PDU payload is variable within 1~65535 bytes. PAD filling-in bits makes the length of CPCS-PDU the integer times of 48 bytes. The length of CPCS-PDU tail is 8 bytes, including the following parts: User-to-User Indication (UUI), used for the transparent transmission of information between CPCS users. CPCS Part Indication (CPI), used to make the length of CPCS-PDU tail as 8 bytes. Length Indication (LI), used to indicate the length of CPCS-PDU payload. Cyclic Redundancy Check (CRC), used to check the content of CPCS-PDU, including CPCS-PDU payload area, PAD, UU, CP and LI and so on.
2.2.5 SAR
The Segment And Reassemble (SAR) sublayer in the AAL5 segments the CPCS-PDU into 48-byte SAR-PDU without any overheads. Reassembly function is achieved during SDU receiving.
2-8
2.2.6 LM
I. Overview
LM interacts directly with SAAL sublayers to accomplish Operation And Maintenance (OAM) functions. No interactions are defined in CPCS and SAR, because CPCS and SAR are accomplished by the hardware. SSCS LM is responsible for the following tasks. Determine whether a link shall exit service or enter service. As a component for accomplishing operations, links must be monitored so as to prevent great delay in transmission. To prevent useless link change, LM allows certain amount of errors on the links. Conduct periodical measurement; for example, record the service life of each links with counters, the fault frequency, congestion frequency, number of congestions and other information. LM can be in any of the following states: Out Of Service Alignment Proving Aligned Ready In Service
II. Function
LM provides three algorithms for error monitoring. These algorithms can detect bursting errors lasting more than 400ms. Algorithm 1 is mainly used when the load is heavy. If the data volume to be sent is too large, the receiving end does not have enough time to process them so that data in the buffer cannot be released on time and the sending queue keeps increasing. When the sending queue is increased to a certain value, links will get released. Algorithm 2 is mainly for medium load. Algorithm 2 monitors the number of data retransmissions. Within a certain period, if the number of data retransmissions exceeds the threshold, the link quality must be very poor. When the transmission delay cannot be tolerated by the system, links will get released. Algorithm 3 is mainly used for low load. When the load is low, the difference between the number of POLL PDUs sent and the number of STAT PDUs received, that is, the number of STAT PDUs lost, exceeds a certain value within a certain period, it means the link quality is very poor and links will get released.
2-9
2-10
II. Example
2.3 MTP3-B
2.3.1 Overview
Based on Message Transfer Part Layer 3 (MTP3), MTP3-B is the protocol specification aiming at ATM features. It performs message exchange through the services provided by SAAL. MTP3-B module performs MTP3-B protocol functions, including signaling message handling and signaling network management, as shown in Figure 2-6. The signaling message handling part provides the following functions: Guaranteeing the signaling message generated at the user part of a signaling point (SP) can be transmitted to the corresponding user part of the destination
2-11
specified by the related field in Message signaling unit (MSU). There are only two user parts at Iu/Iur interface, that is, SCCP and Signal Transport Convert (STC). Functionally this part may be further subdivided into message discrimination, message routing and message distribution. The signaling network management part provides the following functions: Performing re-networking for a signaling network that gets faulty (e.g., a signaling link or a signaling transfer point is congested) during its running. With the increase of signaling network traffics and of loads over signaling links, the signaling network might be congested. Therefore, this part also performs congestion control function. The signaling network management function can be classified into signaling traffic management, signaling link management and signaling route management.
2.3.2 Function
I. Message Discrimination
Message discrimination function is used to identify the signaling message destination and to direct the signaling message. Message discrimination is implemented by analyzing the destination signaling point code (DPC) in the signaling message routing label. When a signaling message is transmitted from Level 2 (SAAL) arrives at Level 3 (MTP3-B) , message discrimination will firstly process it and determine its next handling procedure. If the local signaling point is the destination of the message, the message will be handed over to the message distribution function for subsequent
2-12
handling. If the local signaling point is not the destination and is capable of transferring, the message routing function will be enabled, so as to transfer the message through message routing. If the local signaling point does not have the transferring capability, the signaling network management function will be informed to handle the message as an illegal one.
In case a signaling route is restricted, the traffics over this route will be changed over to the substitute route by using the controlled rerouting program. To limit the traffics of signaling sources in case of congestion, the signaling traffic flow control program is used to control these traffics.
2-14
Figure 2-7 Format and codes of SIO Service Indicator (SI) SI is used to indicate to which specified user part the transmitted messages belong. In the Message Transfer Part of the signaling network, signaling message handling function distributes the message to the specified user part according to the indication of SI. The code of SI is illustrated in Figure 2-7. The capacity of SI can be used to indicate 16 different user parts. The figure only shows several of them. Sub-Service Field (SSF) It is made up of 4 bits, of which the higher two bits act as the network indicator, and the lower two bits, coded 00, are reserved presently. The network indicator serves to distinguish the network attribute of the transmitted message, that is, to distinguish between an international signaling network message and a national signaling network message, as shown in Figure 2-7.
Label includes the necessary information needed to send the message to its destination. The length of standard routing label is 32 bits, it locates in the beginnig of the SIF. Label includes Destination Point Code (DPC), Originating signaling Point Code (OPC) and Signaling Link Selection Code (SLS). DPC is digital address, which is the code used to identify each signaling point uniquely in the SS7. When the DPC of the message represents the accepting signaling point, the message is sent to the corresponding user part that the service indicator of the SIO indicates (for instance, the SCCP). SLS is used to: Guarantee the message order. Any two messages with the same SLS reaches their destination with the same order they are sent. Allow all the available links to share the traffic load equally. If a user part sends message periodically, and distributes the SLS in a cyclic way, then all the service level at the destination shall be the same.
SIF SIO First bit transmitted
Signaling message
SL S
OP C
DP C
Signaling message part is also called as service information part. This part can be further divided into several sub-fields. These sub-fields can be mandatory or optional. The length of them can be fixed or flexible to meet the demand of various functions or expansion. This enables the signaling message unit to meet different user messages. It also makes it possible to transmit different user messages in the common channel. The most important signaling message of MTP layer is the signaling network management message. In the following, we will focus on it.
2-16
Being one of MSUs, the signaling information of signaling network management messages is transmitted in the SIF, with the structure illustrated in Figure 2-9.
Management information
H1
H0
SLC
OPC
8n ( n = 0)
24/14
24/14
The heading code is made up of two 4 bits: H0 and H1. H0 identifies the management message group, and H1 determines the messages in a message group. H0 and H1 occupy 4 bits respectively and their total capacity of representing messages is up to 265 kinds, i.e., there are 16 message groups and each of them has 16 types of message. Table 2-1 The allocation of heading code H0 H0 0000 0001 0010 0011 0100 0101 0110 0111 1001 1010 10111111 Reserved Changeover and changeback messages (CHM) Emergency changeover message (ECM) Transfer controlled and signaling route set congestion messages (FCM) Transfer-prohibited-allowed-restricted messages (TFM) Signaling-route-set-test messages (RSM) Management inhibit messages (MIM) Traffic restart allowed message (TRM) Spare User part flow control messages (UFC) Spare Description
2-17
Signaling network management message and its heading code allocation are described in Table 2-2 in details. Table 2-2 Messages of SS7 the third function level network management Message Group H1 00 H0 0000 CHM ECM FCM TFM RSM MIM 0001 0010 0011 0100 0101 0110 ECO ECA RCT TFC TFP RST RSR LIN (TRA ) LUN LIA LUA LID LFU LLT (LRT ) TFR TFA XCO XCA CBD CBA 00 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111
TRM DLM
UFC
(UP U)
CBA: Changeback-acknowledgement signal CBD: Changeback-declaration signal XCA: Extended Changeover Acknowledgement XCO: Extended Changeover Order ECA: Emergency-changeover-acknowledgement signal
2-18
ECO: Emergency-changeover-order signal RCT: Signaling-route-set-congestion-test signal RSR: Signaling-route-set-test signal for restricted destination (national option), RST: Signaling-route-set-test signal for prohibited destination TFR: Transfer-restricted signal (national option) TFA: Transfer-allowed signal TFC: Transfer-controlled signal TRA: Traffic-restart-allowed signal TFP: Transfer-prohibited signal LID: Link inhibit denied signal LFU: Link forced uninhibit signal LIN: Link inhibit signal LIA: Link inhibit acknowledgement signal LUA: Link uninhibit acknowledgement signal LUN: Link uninhibit signal LLT: Link local inhibit test signal LRT: Link remote inhibit test signal UPU: User Part Unavailable signal
II. Changback
Generally, signaling traffic in the signaling network are carried on normal signaling links, while alternative signaling links only take over the signaling traffic from the signaling links that are "temporarily" faulty. Therefore signaling traffic must be changed back to normal signaling links once the temporarily faulty links are available again.
not change. However, the signaling link is marked as blocked, the signaling traffic of the blocked link is stopped temporarily. You can carry out test periodically. If necessary, the blocked link can be unblocked by the MML command. Signaling route control function can also start the unblocking management prohibit procedure.
In any of the following cases, the signaling link is deemed faulty and unavailable: SAAL gives the fault indications Out of Service Receives request from the management system. Receives changeover command from the opposite end, requesting to change over the signaling traffic of the signaling link to another signaling link. 2) Signaling link restoration The process to remove signaling link fault and make the signaling ready for transmitting signaling traffic is referred to as signaling link restoration. When the fault is removed and initial alignment is successfully completed at both ends of the once faulty signaling link, the signaling link becomes available again. 3) Disconnection of signaling link
The process to stop traffic of a signaling link set or a signaling link is defined as signaling link disconnection. Signaling link may be disconnected upon the request by the maintenance and management system, or performed by the signaling link management function as well.
2-20
4)
The process to make the signaling link ready for signaling traffic transmission is defined as connection of a signaling link. When a disconnected signaling link has its signaling data link or signaling terminal connected again and the initial alignment is completed successfully, the once disconnected signaling link is regarded as being connected. Table 2-3 shows general management process of signaling network upon change of signaling link status. Table 2-3 General management process of signaling network upon change of signaling link status Signaling network management Signaling link status Signaling traffic management starts the changeover procedure (or emergency changeover procedure when necessary) to transfer the When a signaling link is faulty (becomes unavailable) signaling traffic on the unavailable signaling link to one or more alternative signaling links. The process above mentioned includes specifying the alternative signaling link, recovering the sent yet not acknowledged messages. the changeback process, when necessary, is activated to change the signaling traffic from the one or more When a signaling link is restored alternative signaling links back to the link which recovers to be available. It includes the process to specify the signaling traffic that can be changed back and to maintain correct message sequence. When a signaling link Normally, when a signaling link is to be disconnected, the if another signaling link in the same link set is connected during the signaling link fault, then the stop process is used to change the signaling link set status back to that before the fault occurs, and to disconnect the operating link connected during the signaling link fault, regarding it unable to transmit signaling. When one signaling link is disconnected, if the number of when a signaling link is faulty, signaling link management function will, according to the status of the signaling link set, connect another signaling link in the signaling link set, and then prepare for the restoration of the faulty signaling link and its signaling transmission Signaling link management Signaling route management signaling route function is not enabled if the signaling link fault does not result in any changes of signaling route set status. However, if the fault affects the status of route sets, the transfer forbidden process or transfer restricted process has to be started. signaling route function is not enabled if the signaling link fault does not result in any changes of signaling route set status. Otherwise, the transfer allowed process has to be started. the same procedure as that of signaling link
2-21
Signaling network management Signaling link status is disconnected Signaling traffic management signaling traffic has already been transferred. If it is not yet transferred, the signaling traffic changeover process shall be executed. When the signaling link is connected, if When a signaling link is connected the same procedure as that of signaling link restoration the number of connected signaling links in the link set is greater than the necessary number, another link will be disconnected. If a signaling route set becomes unavailable or restricted, due to When a signaling link is blocked the same procedure as that of signaling link fault handling. blocking, it can not None perform transfer prohibited process on the STP which can select route for relevant messages. When a signaling route set becomes When a signaling link is unblocked the same procedure as that of signaling link restoration. available again due to None unblocking of the link, the transfer allowed process will be employed. the same procedure as that of signaling link restoration. Signaling link management signaling links operating in the link set is less than the necessary number, another link will be connected. Signaling route management fault handling.
2-22
When a transfer allowed message is received, indicating that the signaling traffic to a destination can be transmitted via the STP sending out transfer allowed message, the signaling route will again become available. shows the process involved in signaling route status changing Table 2-4 The process involved in signaling route status changing Signaling route status Signaling network management Signaling traffic management the forced rerouting process is performed so that the signaling traffic to When a signaling route turns unavailable a destination is changed over from the link set which includes the unavailable route to the alternative route connecting another STP. the controlled rerouting process is performed so that the signaling traffic to When a signaling route becomes available a destination is changed back from the signaling link set which includes the alternative signaling route to the signaling link set which includes the recovered route once in faulty. Signaling route management when a signaling route becomes unavailable, the transfer prohibited process will be started, informing one or multiple adjacent signaling points that it can no longer transmit messages via this STP. In the meantime, the route set testing process or the route set congestion testing process will be started accordingly. the transfer allowed process will be started, informing one or multiple adjacent signaling points that it can transmit messages again via this STP. In the meantime, the route set testing process or route set congestion testing process will be stopped
2-23
II. Example
2-24
II. Example
2-25
II. Example
2.4 ALCAP
2.4.1 Overview
SAAL UNI
MTP3-B
Figure 2-10 ALCAP structure in the BSC6800 system Access Link Control Application Part (ALCAP), also called Q.AAL2 protocol, is the control plane of the Iub/Iur/Iu-CS transport network layer with the signaling bearers of SAAL UNI type and MTP3-B type.
2-26
As is shown in Figure 2-10, ALCAP consists of a Q.AAL2 protocol processing layer and two STC adaptation layers the former of which performs all protocol functions while the latter one adapts primitives and shield bottom-layer differences (SAAL, MTP3-B). The basic function of ALCAP is establishing and releasing AAL2 connection between two SPs. Besides, it also maintains and manages such resources as path and micro channel. The ALCAP of BSC6800 complies with ITU-T Q.2630.1.
2.4.2 Function
ALCAP performs the processes of AAL2 connection establishment and release, of AAL2 PATH block and unblock, of AAL2 connection reset.
Figure 2-11 Establishment and release of AAL2 connection The procedures to establish AAL2 connection are as follows: 1) 2) ALCAP at RNC sends ESTABLISH REQUEST message to the ALCAP of the peer end. Upon receiving an ESTABLISH request sent by the ALCAP of the peer end, the ALCAP sends an ESTABLISH indication primitive to the service layer after resource allocation and activates the wait timer. 3) After receiving an ESTABLISH response from the service layer before the time expires, it sends an ESTABLISH confirm to the RNC ALCAP. The release procedures are similar with the establish procedures.
2-27
BLOCK REQUEST BLOCK REQUEST BLOCK CONFIRM BLOCK CONFIRM UNBLOCK REQUEST UNBLOCK REQUEST UNBLOCK CONFIRM UNBLOCK CONFIRM
Figure 2-12 Blocking and unblocking of a path The procedures to block a path are as follows: 1) 2) 3) 4) O&M at RNC initiates BLOCK REQUEST to ALCAP at RNC. ALCAP at RNC sends BLOCK REQUEST to ALCAP at the peer end. After analyzing the message, ALCAP at the peer end set the path as blocked and generates a BLOCK confirm message. After receiving the BLOCK CONFIRM message, RNC ALCAP sends back the message to O&M. The unblocking procedures are similar with the blocking procedures.
III. Reset
Reset can help to release AAL2 connection or AAL2 PATH in a confused state. There are three types of resets: reset of an AAL2 connection, reset of an AAL2 PATH and reset of all AAL2 PATHs between two SPs. The message procedures for a reset are shown in Figure 2-13.
2-28
RESET REQUEST RESET REQUEST RELEASE INDICATION RESET CONFIRM RESET CONFIRM
Figure 2-13 Reset procedures This procedures to reset are as follows: 1) 2) 3) O&M at RNC initiates RESET REQUEST to ALCAP at RNC. ALCAP at RNC sends RESET REQUEST to ALCAP at the peer end. After analyzing the message, ALCAP at the peer end set the path as blocked and generates a RESET confirm message. If there is any connection in the micro path or tunnel, the connection will be released and a RELEASE INDICATION will be reported to service layer. 4) After receiving the RESET CONFIRM message, RNC ALCAP feeds back the message to O&M.
2-29
Signaling related ID Message ID Message compatability field Message length ID of parameter A Compatability field for parameter A Length of parameter A Field a in parameter A Field b in parameter A Length of field c in parameter A Field c in parameter A Parameter B M
2-30
II. Example
2.5 SCCP
2.5.1 Overview
Signaling Connection Control Part (SCCP) is used to enhance the functions of Message Transfer Part (MTP). The addressing function of MTP only can be used to transmit messages to nodes, providing only the connectionless message transfer. While SCCP is able to provide a type of addressing function to identify each SCCP user in a node using DPC and subsystem number (SSN). The SCCP in the BSC6800 system complies with ITU-T Q711-716.
2-31
2.5.2 Function
The SCCP performs network service, routing and management functions.
Connectionless services are implemented in the case that the user directly transmits data information in the signaling network by means of SCCP and MTP route functions without prior establishment of signaling connections, featuring flexibility and simpleness and applicable for the transmission of small quantities of data. Among them, class-0 service does not ensure the messages can be transmitted in sequence but class-1 service is able to do that depending on the cooperation of the signaling link selection code (SLS) and MTP. Connectionless services implement user data transmission using Unit Data (UDT) and Enhanced Unit Data (XUDT) messages. The UDT message is not able to segment/reassemble data and the maximum length of the user data that can be transmitted via this message is 255 octets. The XUDT message is capable of segmenting/reassembling data and transmitting the user data of with the maximum length of 2k octets. 2) Connection-oriented services
Connection-oriented services are implemented only after the user establishes signaling connections (virtual connections) between OSPs and DSPs by means of answer mode before transmitting signaling messages. In this way, data can be transmitted via the established signaling connection instead of the route selected via the SCCP routing function. Upon the completion of the data transmission, the user can release the connection with the primitive N_DISCONNECT_REQ. Connection-oriented services are applicable for the transmission of large quantities of data. The DSP is confirmed to be able to receive data prior to data transmission; therefore invalid transmission of large quantities of data can be avoided. Furthermore, the pre-established connection makes the SCCP routing function unnecessary for the subsequent transmissions, thus effectively reducing the batch transmission delay. The implementation procedure of connection-oriented services includes connection establishment, data transmission and connection release. Capable of setting up coupling connections, the BSC6800 system provides the local reference function of
2-32
freezing the local node to prevent disordered connections when releasing the local connection reference source.
In which DPC is the one adopted by MTP while SSN is used to identify different SCCP users (for example, ISUP, MAP, TCAP. and so on) so as to compensate for shortage of MTP users and broaden the addressing scope, thus to be applicable for new services in the future. The routing function of the BSC6800 system can translate the following types of address information as per the actual requirements: DPC+SSN and DPC. Upon receiving a message from MTP, the SCCP route control part of a node analyzes its called address. If this node is the destination of this message, it will distribute the message to the destination user. Otherwise it will translate the address of the message to form a new route flag and potential new called address and then send them to MTP. Upon receiving a message from the connection-oriented control part or the connectionless control part, SCCP performs route analysis to it and then send it to the MTP part, the connection-oriented control part or the connectionless control part for processing.
2-33
2-34
II. Example
2-35
Figure 3-1 Resource status indication NodeB uses resource status indication to report its physical resources to RNC. In the following cases, NodeB will trigger the resource status indication procedures: When a Local Cell becomes existing at the NodeB. When a Local Cell is to be deleted in NodeB, that is, the status becomes Not existing. When the capabilities of the Local Cell changes at the NodeB.
3-1
When a cell has changed its capability and/or its resource operational state at NodeB. When common physical channels and/or common transport channels have changed their capabilities at a NodeB. When a communication control port changed its resource operational state at the NodeB. When a Local Cell Group has changed its resource capability at the NodeB. The NodeB initiates a RESOURCE STATUS INDICATION message to the CRNC in each of the above cases and the RESOURCE STATUS INDICATION message may contain the trigger cause and the associated logical resource contents, as shown in Figure 3-1.
AUDIT REQUEST
AUDIT
RESPONSE
Figure 3-2 Resource audit procedure The NodeB responds to the resource audit request of the RNC by an AUDIT RESPONSE message. AUDIT RESPONSE message includes information about physical common channel of logical cell, CCP, local cell, local group cell. Among which the local cell and the local cell group information is the abstraction of the NodeBs
3-2
physical resources. In this way, RNC can distribute the logical resources of the cell according to the abstract data. If the information provided in the AUDIT RESPONSE message completes the audit sequence, the NodeB shall set the End of Audit Sequence Indicator IE in the AUDIT RESPONSE message to End of Audit Sequence. If not all audit information has been provided yet as part of the ongoing audit sequence, the NodeB shall set the End of Audit Sequence Indicator IE in the AUDIT RESPONSE message to Not End of Audit Sequence.
Figure 3-3 Cell setup procedure After receiving the AUDIT RESPONSE from the NodeB, the CRNC sends a CELL SETUP REQUEST message to the NodeB if the conditions of cell setup are satisfied. The NodeB shall set up a new cell according to the parameters included in that message, as shown in Figure 3-3. If the CELL SETUP REQUEST message includes one or more Secondary CPICH Information IE(s), the NodeB shall configure and activate the Secondary CPICH(s) (SCPICH(s)) in the cell according to received configuration data. The Maximum Transmission Power IE value shall be stored in the NodeB and at any instance of time the total maximum output power in the cell shall not be bigger than this value. If the CELL SETUP REQUEST message includes one or more Closed Loop Timing Adjustment Mode IE(s), the value(s) shall be stored in the NodeB and applied when closed loop Feed-Back mode diversity is used on DPCH. When the cell is successfully configured, the NodeB shall store the Configuration Generation ID IE value and send a CELL SETUP RESPONSE message as a response. When the cell is successfully configured, CPICH(s), Primary SCH (PSCH), Secondary SCH (SSCH), Primary CCPCH (PCCPCH) and BCH exist. The cell and the channels shall be set to Enabled state. When the cell is not successfully configured, the CELL SETUP FAILURE message shall be sent to CRNC.
3-3
COMMON TRANSPORT CHANNEL SETUP REQUEST COMMON TRANSPORT CHANNEL SETUP RESPONSE
Figure 3-4 Common transport channel setup procedure The procedure is initiated with a COMMON TRANSPORT CHANNEL SETUP REQUEST message sent from the CRNC to the NodeB. One message can configure only one of the following combinations: One SCCPCH, and FACHs, PCH and PICH related to that SCCPCH One PRACH, one RACH and one AICH related to that PRACH If successfully set up the common transport channel, NodeB responds with a COMMON TRANSPORT CHANNEL SETUP RESPONSE message to the CRNC. If fails to set up the common transport channel, NodeB responds with a COMMON TRANSPORT CHANNEL SETUP FAILURE message.
Note: The transport channel synchronization procedure in user plane follows the establishment of downlink common transport channel. After the PCH is established successfully, the node synchronization procedure in user plane may follow.
3-4
Figure 3-5 System information update After all common transport channels are set up, the CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to the NodeB, as shown in Figure 3-5. That message includes the contents of the system information segments broadcast on the BCCH and the segment scheduling information. When the NodeB successfully completes the updating of the broadcast channel scheduling cycle according to the parameters given in the SYSTEM INFORMATION UPDATE REQUEST message, it responds to the CRNC with a SYSTEM INFORMATION UPDATE RESPONSE message. When the NodeB does not successfully complete the updating, it responds with a SYSTEM INFORMATION UPDATE FAILURE message.
COMMON
INITIATION
COMMON
INITIATION
Figure 3-6 Common measurement initiation procedure The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the CRNC to the NodeB using the NodeB control port, as shown in Figure 3-6. That message includes the measurement object type (cell, RACH, and so on), common measurement type (Tx carrier power, total Rx broadband power, and so on) and report characteristics (On-Demand report, periodic report, event report, and so on). Upon receipt of the message, the NodeB initiates the requested measurement according to the parameters given in the request.
3-5
If the NodeB is able to initiate the measurement requested by the CRNC, it responds with the COMMON MEASUREMENT INITIATION RESPONSE message sent over the NodeB control port. If the initiation fails, it responds the COMMON MEASUREMENT INITIATION FAILURE message.
CELL
RECONFIGURATION RESPONSE
Figure 3-7 Cell reconfiguration The CRNC sends a CELL RECONFIGURATION REQUEST message to the NodeB. Upon reception, the NodeB reconfigures the cell according to the parameter included in the message. If the CELL RECONFIGURATION REQUEST message includes the Primary SCH Information IE, the NodeB reconfigures Primary SCH power in the cell according to Primary SCH Power IE value. If the CELL RECONFIGURATION REQUEST message includes the Secondary SCH Information IE, the NodeB reconfigures Secondary SCH power in the cell according to the Secondary SCH Power IE value. If the CELL RECONFIGURATION REQUEST message includes the Primary CPICH Information IE, the NodeB reconfigures Primary CPICH power in the cell according to the Primary CPICH Power IE value. NodeB adjusts all the transmitted power levels relative to the Primary CPICH power according to the new value. If the CELL RECONFIGURATION REQUEST message includes one or more Secondary CPICH Information IE, the NodeB reconfigures the power for each Secondary CPICH in the cell according to their Secondary CPICH Power IE value. If the CELL RECONFIGURATION REQUEST message includes the Primary CCPCH Information IE, the NodeB reconfigures BCH power in the cell according to the BCH Power IE value. If the CELL RECONFIGURATION REQUEST message includes the Maximum Transmission Power IE, the value shall be stored in the NodeB and at any
3-6
instance of time the total maximum output power in the cell shall not be bigger than this value. If reconfigure the cell successfully, NodeB stores the new Configuration Generation ID IE value and sends a CELL RECONFIGURATION RESPONSE message as a response. If fail to reconfigure the cell, NodeB sends a CELL RECONFIGURATION FAILURE message. If the CELL RECONFIGURATION REQUEST message includes the Synchronization Configuration IE, NodeB reconfigures the indicated parameters in the cell according to the IE value. When the parameters in the Synchronization Configuration IE affect the thresholds applied to a radio link set, NodeB immediately applies the new thresholds.
Figure 3-8 Cell deletion 1) The CRNC sends a CELL DELETION REQUEST message to NodeB. Upon reception, NodeB deletes the cell and any remaining common and dedicated channels within the cell. The states for the cell and the deleted common channels shall be set as Not Existing. The NodeB deletes all radio links and all NodeB Communication Context within the cell. NodeB also initiates releasing of the user plane transport bearers for the deleted common and dedicated channels. 2) After delete the cell, NodeB return a CELL DELETION RESPONSE message as a response.
3-7
IE/Group Name Transaction ID Indication Type CHOICE Indication Type >No Failure >>Local Cell Information >>>Local Cell ID >>>Add/Delete Indicator >>>DL or Global Capacity Credit >>>UL Capacity Credit >>>Common Channels Capacity Consumption Law >>>Dedicated Channels Capacity Consumption Law >>>Maximum DL Power Capability >>>Minimum Spreading Factor >>>Minimum DL Power Capability >>>Local Cell Group ID >>Local Cell Group Information >>>Local Cell Group ID >>>DL or Global Capacity Credit >>>UL Capacity Credit >>>Common Channels Capacity Consumption Law >>>Dedicated Channels Capacity Consumption Law >Service Impacting >>Local Cell Information >>>Local Cell ID M M M M O M M M M M M
Presence
Semantics description
C-add O C-add
C-add
3-8
IE/Group Name >>>DL or Global Capacity Credit >>>UL Capacity Credit >>>Common Channels Capacity Consumption Law >>>Dedicated Channels Capacity Consumption Law >>>Maximum DL Power Capability >>>Minimum Spreading Factor >>>Minimum DL Power Capability >>Local Cell Group Information >>>Local Cell Group ID >>>DL or Global Capacity Credit >>>UL Capacity Credit >>>Common Channels Capacity Consumption Law >>>Dedicated Channels Capacity Consumption Law >>Communication Control Port Information >>>Communication Control Port ID >>>Resource Operational State >>>Availability Status >>Cell Information >>>C-ID >>>Resource Operational State >>>Availability Status >>>Primary SCH Information >>>Secondary SCH Information M O O O O M M M O M O O O O O O O O O O
Presence
Semantics description
3-9
IE/Group Name >>>Primary CPICH Information >>>Secondary CPICH Information >>>>Secondary CPICH Individual Information >>>Primary CCPCH Information >>>BCH Information >>>Secondary CCPCH Information >>>>Secondary CCPCH Individual Information >>>PCH Information >>>PICH Information >>>FACH Information >>>>FACH Individual Information >>>PRACH Information >>>>PRACH Individual Information >>>RACH Information >>>>RACH Individual Information >>>AICH Information >>>>AICH Individual Information >>>PCPCH Information >>>>PCPCH Individual Information >>>CPCH Information >>>>CPCH Individual Information >>>AP-AICH Information >>>>AP-AICH Individual Information >>>CD/CA-ICH Information M M M M M M M M O O M O O M O
Presence
Semantics description
3-10
Presence
Semantics description
3-11
II. Examples
3-12
IE/Group Name Message Discriminator Message Type Transaction ID End Of Audit Sequence Indicator Cell Information >C-ID >Configuration Generation ID >Resource Operational State >Availability Status >Local Cell ID >Primary SCH Information >Secondary SCH Information >Primary CPICH Information >Secondary CPICH Information >>Secondary CPICH Individual Information >Primary CCPCH Information >BCH Information >Secondary CCPCH Information >>Secondary CCPCH Individual Information >PCH Information >PICH Information >FACH Information >>FACH Individual Information >PRACH Information >>PRACH Individual Information >RACH Information M M O O M M O O M M M M M O O O M M M M
Presence
Semantics description
3-13
IE/Group Name >>RACH Individual Information >AICH Information >>AICH Individual Information >PCPCH Information >>PCPCH Individual Information >CPCH Information >>CPCH Individual Information >AP-AICH Information >>AP-AICH Individual Information >CD/CA-ICH Information >>CD/CA-ICH Individual Information >SCH Information Communication Control Port Information >Communication Control Port ID >Resource Operational State >Availability Status Local Cell Information >Local Cell ID >DL or Global Capacity Credit >UL Capacity Credit >Common Channels Capacity Consumption Law >Dedicated Channels Capacity Consumption Law >Maximum DL Power Capability >Minimum Spreading Factor O O M M M O M M M M M O M M M M M
Presence
Semantics description
3-14
IE/Group Name >Minimum DL Power Capability >Local Cell Group ID Local Cell Group Information >Local Cell Group ID >DL or Global Capacity Credit >UL Capacity Credit >Common Channels Capacity Consumption Law >Dedicated Channels Capacity Consumption Law Criticality Diagnostics O M M M O M O O
Presence
Semantics description
3-15
II. Examples
I. Message Structure
IE/Group Name Message Discriminator Message Type Transaction ID Local Cell ID C-ID Configuration Generation ID T_Cell UARFCN UARFCN Maximum Transmission Power Closed Loop Timing Adjustment Mode Primary Scrambling Code Synchronization Configuration >N_INSYNC_IND >N_OUTSYNC_IND >T_RLFAILURE DL TPC pattern 01 count Primary SCH Information >Common Physical Channel ID >Primary SCH Power >TSTD Indicator Secondary SCH Information >Common Physical Channel ID >Secondary SCH power >TSTD Indicator M M M M M M M M M M M M M M M M M M M M O M Presence Cell ID Offset of T_cell against BFN Maximum transmission power Primary scrambling code of cell Semantics description
3-17
IE/Group Name Primary CPICH Information >Common Physical Channel ID >Primary CPICH power >Transmit Diversity Indicator Secondary CPICH Information >Common Physical Channel ID >DL Scrambling code >FDD DL Channelisation Code Number >Secondary CPICH Power >Transmit Diversity Indicator Primary CCPCH Information >Common Physical Channel ID >BCH Information >>Common Transport Channel ID >>BCH Power >STTD Indicator Limited power increase information >Power_Raise_Limit >DL_power_averaging_window_size M M M M M M M M M M M M M M
Presence
Semantics description
3-18
II. Example
3-19
3-20
IE/Group Name >>>>Transport Format Set >>>>ToAWS >>>>ToAWE >>>>Max FACH Power >>>PCH Parameters >>>>Common Transport Channel ID >>>>Transport Format Set >>>>ToAWS >>>>ToAWE >>>>PCH Power >>>>PICH Parameters >>>>>Common Physical Channel ID >>>>>FDD DL Channelisation Code Number >>>>>PICH Power >>>>>PICH Mode >>>>>STTD Indicator >PRACH M M M M M M M M M M M M M M
Presence
Semantics description
. .
>>PRACH >>>Common Physical Channel ID >>>Scrambling Code Number >>>TFCS >>>Preamble Signatures >>>Allowed Slot Format Information >>>>RACH Slot Format >>>RACH Sub Channel Numbers M M M M M M .
3-21
IE/Group Name >>>Puncture Limit >>>Preamble Threshold >>>RACH Parameters >>>>Common Transport Channel ID >>>>Transport Format Set >>AICH Parameters >>>Common Physical Channel ID >>>AICH Transmission Timing >>>FDD DL Channelisation Code Number >>>AICH Power >>>STTD Indicator >PCPCHes M M M M M M M M M
Presence
Semantics description
>>CPCH Parameters >>>Common Transport Channel ID >>>Transport Format Set >>>AP Preamble Scrambling Code >>>CD Preamble Scrambling Code >>>TFCS >>>CD Signatures >>>CD Sub Channel Numbers >>>Puncture Limit >>>CPCH UL DPCCH Slot Format >>>UL SIR >>>Initial DL transmission Power >>>Maximum DL Power >>>Minimum DL Power M M M M M M M M M M M O
3-22
IE/Group Name >>>PO2 >>>PO3 >>>FDD TPC DL Step Size >>>N_Start_Message >>>N_EOT >>>Channel Assignment Indication >>>CPCH Allowed Total Rate >>>PCPCH Channel Information >>>>Common Physical Channel ID >>>>CPCH Scrambling Code Number >>>>DL Scrambling Code >>>>FDD DL Channelisation Code Number >>>>PCP Length >>>>UCSM Information >>>>>Min UL Channelisation Code Length >>>>>NF_max >>>>>Channel Request Parameters >>>>>>AP Preamble Signature >>>>>AP Sub Channel Number >>>VCAM Mapping Information >>>>Min UL Channelisation Code Length >>>>NF_max >>>>Max Number of PCPCHes >>>>SF Request Parameters >>>>>AP Preamble Signature >>>>>AP Sub Channel Number M O M O M M M M M M M M M M M M
Presence
Semantics description
C-NCA M M
C-CA M M M
3-23
IE/Group Name >>>AP-AICH Parameters >>>>Common Physical Channel ID >>>>FDD DL Channelisation Code Number >>>>AP-AICH Power >>>>CSICH Power >>>>STTD Indicator >>>CD/CA-ICH Parameters >>>>Common Physical Channel ID >>>>FDD DL Channelisation Code Number >>>>CD/CA-ICH Power >>>>STTD Indicator M M M M M M M M M
Presence
Semantics description
3-24
II. Example
I. Message Structure
IE/Group Name Message Discriminator Message Type Transaction ID C-ID BCCH Modification Time MIB/SB/SIBInformation >IB Type >IB OC ID >CHOICE IB DeletionIndicator >>NoDeletion >>>SIB Originator >>>IB SG REP >>>Segment Information >>>>IB SG POS >>>>Segment type O C CRNCOrigination >>>>IB SG DATA C CRNCOrigination >>Deletion C-SIB O M M M M M M M
O
Presence
Semantics description
3-26
II. Example
3-27
3-28
Node B
1.NCP:RESOURCE STATUS INDICATION 2. NCP: AUDIT REQUEST 3.NCP: AUDIT RESPONSE 4.NCP: CELL SETUP REQUEST 5.NCP: CELL SETUP RESPONSE
RNC
6.NCP: COMMON TRANSPORT CHANNEL SETUP REQUEST 7.NCP: COMMON TRANSPORT CHANNEL SETUP RESPONSE 8.ALCAP:QAAL2 ESTABLISH REQUEST 9.ALCAP:QAAL2 ESTABLISH CONFIRM 10.NCP: COMMON TRANSPORT CHANNEL SETUP REQUEST 11.NCP: COMMON TRANSPORT CHANNEL SETUP RESPONSE 12.ALCAP:QAAL2 ESTABLISH REQUEST 13.ALCAP:QAAL2 ESTABLISH CONFIRM 14.ALCAP:QAAL2 ESTABLISH REQUEST 15.ALCAP:QAAL2 ESTABLISH CONFIRM 16.ALCAP:QAAL2 ESTABLISH REQUEST 17.ALCAP:QAAL2 ESTABLISH CONFIRM 18.NCP:COMMON TRANSPORT CHANNEL SETUP REQUEST 19.NCP:COMMON TRANSPORT CHANNEL SETUP RESPONSE 20. ALCAP: QAAL2 ESTABLISH REQUEST 21. ALCAP: QAAL2 ESTABLISH CONFIRM 22. ALCAP: QAAL2 ESTABLISH REQUEST 23. ALCAP: QAAL2 ESTABLISH CONFIRM
3-29
NodeB
RNC
24. NCP: SYSTEM INFORMATION UPDATE REQUEST 25 NCP:SYSTEM INFORMATION UPDATE RESPONSE
26. NCP: COMMON MEASUREMENT INITIATION REQUEST 27.NCP: COMMON MEASUREMENT INITIATION RESPONSE 28. NCP: COMMON MEASUREMENT INITIATION REQUEST 29. NCP: COMMON MEASUREMENT INITIATION RESPONSE 30. NCP: COMMON MEASUREMENT INITIATION REQUEST 31. NCP: COMMON MEASUREMENT INITIATION RESPONSE 32. NCP: MEASUREMENT REPORT 33. NCP: MEASUREMENT REPORT 34. NCP: MEASUREMENT REPORT
Figure 3-9 Cell setup procedures Each step is explained as follows: 1) NodeB sends a RESOURCE STATUS INDICATION message to the CRNC. The message may contain the trigger cause and the associated logical resource contents. 2) 3) The CRNC sends an AUDIT REQUEST message to the NodeB to initiate the resource audit procedure. The CRNC performs an audit of the configuration and status of the logical resources in the NodeB. It may also re-synchronize the NodeB and the CRNC. After the audit, the NodeB returns an AUDIT RESPONSE message to the CRNC. 4) 5) The CRNC sends a CELL SETUP REQUEST message to the NodeB to initiate a cell setup procedure. The NodeB stores the necessary resources and configures a new cell according to the parameters given in the CELL SETUP REQUEST message. After the cell setup, the NodeB returns a CELL SETUP RESPONSE message to the CRNC, confirming that the cell is successfully set up.
3-30
6) 7) 8)
The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST message to the NodeB, requesting the NodeB to set up a PRACH. The NodeB returns a COMMON TRANSPORT CHANNEL SETUP RESPONSE, confirming that the common transport channel is successfully set up. The CRNC sends a QAAL2 ESTABLISH REQUEST message to the NodeB using ALCAP protocol to initiate an Iub interface data transport bearer establishment procedure. The message contains an AAL2 binding identity to bind the Iub interface data transport bearer to the RACH.
9)
The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the CRNC as a response.
10) The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST to the NodeB, requesting the NodeB to set up an SCCPCH. Here, the SCCPCH bears two FACHs and one PCH. 11) The NodeB returns a COMMON TRANSPORT CHANNEL SETUP RESPONSE message, confirming that the common transport channel is successfully set up. 12) 14) 16) The CRNC sends a QAAL2 ESTABLISH REQUEST message to the NodeB to initiate an Iub interface data transport bearer establishment procedure. This procedure is implemented for three times to set up three Iub interface data transport bearers. Each QAAL2 ESTABLISH REQUEST message contains an AAL2 binding identity to bind the corresponding Iub interface data transport bearer to the two FACHs and one PCH. 13) 15) 17) The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the CRNC as a response. Corresponding to the three QAAL2 ESTABLISH REQUEST messages, the NodeB returns three QAAL2 ESTABLISH CONFIRM messages to the CRNC. 14) The CRNC sends a COMMON TRANSPORT CHANNEL SEUTP REQUEST message to the NodeB, requesting the NodeB to set up a SCCPCH. This SCCPCH bears two FACHs. 15) The NodeB returns a COMMON TRANSPORT CHANNEL SETUP RESPONSE message, confirming the successful setup of the common transport channel. 16) 22) The CRNC sends an ALCAP message QAAL2 ESTABLISH REQUEST to the NodeB to initiate an Iub interface data transport bearer establishment procedure. This procedure is implemented for two times to set up two Iub interface data transport bearers. Each QAAL2 ESTABLISH REQUEST message contains an AAL2 binding identity to bind the corresponding Iub interface data transport bearer to the two FACHs. 17) 23) The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the CRNC as a response. Corresponding to the two QAAL2 ESTABLISH REQUEST messages, the NodeB returns two QAAL2 ESTABLISH CONFIRM messages to the CRNC. 18) The CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to the NodeB.
3-31
19) The NodeB returns a SYSTEM INFORMATION UPDATE RESPONSE message, confirming the successful update of the system information. 20) 28) 30) The RNC sends a COMMON MEASUREMENT INITIATION REQUEST message to the NodeB. The message is sent for three times, requesting for three types of common measurements: Tx carrier power measurement in the form of periodic report, RTWP measurement in the form of periodic report and Tx carrier power measurement in the form of event-E report. 21) 29) 31) Corresponding to the three COMMON MEASUREMENT INITIATION REQUEST messages, the NodeB returns three COMMON MEASUREMENT INITIATION RESPONSE messages, confirming the successful initiation of the common measurement. 22) According to the RNC request, the NodeB periodically sends the Tx carrier power MEASUREMENT REPORT. 23) According to the RNC request, the NodeB periodically sends the RTWP MEASUREMENT REPORT. 24) According the RNC request, the NodeB sends the Tx carrier power MEASUREMENT REPORT only when the event E occurs. So far, the setup of the cell has completed and UE can access to the network.
3-32
SIB
Figure 4-1 System information structure The three types of system information blocks are organized as a tree as shown in Figure 4-1. Their features and main contents are as follows: A MIB bears scheduling information to a number of SIBs or SBs in a cell. A MIB can also contain the PLMN Type (GSM and/or ANSI-41) supported by the cell and the PLMN ID. MIBs are regularly broadcast on a BCH on fixed occasions. Because BCH is mapped to the PCCPCH, UE within the cell can read the content of MIB to know if it is necessary of update or store the system information. A SB bears additional scheduling information for SIBs. The SB is applied when the scheduling resources of the MIB are insufficient.
4-1
SIB bears the actual system information, including 18 type of SIB. The scheduling information of SIB is borne by MIB or SB.
SIB15: include information on UE-based or UE-assisted positioning method SIB 16: include parameters of radio bearing, transport channel and physical channel. These parameters are stored in UE (either in idle mode or in connected mode). It is used when UE switched to UTRAN. The scope is PLMN. SIB17: include the rapid changed parameters used to configure the shared physical channel under connected mode. Only used in TDD. SIB18: include PLMN identity of neighbor cell.
UTRAN
Figure 4-2 System information broadcast UTRAN sends a SYSTEM INFORMATION message to the UE. The message contains the scheduling information, area scope, system information contents, and so on. The RRC layer in UTRAN performs segmentation and concatenation of encoded system information blocks. If the encoded system information block is larger than the size of a SYSTEM INFORMATION message, it will be segmented and transmitted in several messages. If the encoded system information block is smaller than a SYSTEM INFORMATION message, UTRAN may concatenate several system information blocks, or the first segment or the last segment into the same message. The UE shall read SYSTEM INFORMATION messages broadcast on a BCH transport channel in idle mode and in states CELL_PCH, CELL_FACH and URA_PCH. In idle mode and connected mode different combinations of SIBs are valid. The UE shall acquire the needed system information blocks. The UE may store SIBs for different cells and different PLMNs, to be used if the UE returns to these cells or PLMNs.
4-3
UE
NodeB
NBAP NBAP 3. BCCH: SYSTEM INFORMATION 1.SYSTEM INFORMATION UPDATE REQUEST 2.SYSTEM INFORMATION UPDATE RESPONSE
CRNC
NBAP NBAP
RRC
RRC
RRC
RRC
RRC
Figure 4-3 System information update Each step is explained in the following list: 1) 2) 3) The RNC sends a NBAP SYSTEM INFORMATION UPDATE REQUEST message to the associated NodeB, requesting for system information broadcast. The NodeB returns a NBAP message SYSTEM INFORMATION UPDATE RESPONSE to the RNC, confirming the system information broadcast. ~ 5), the NodeB sends SYSTEM INFORMATION messages on the air interface.
4-4
Information Element/Group name >>Last segment >>First Segment >Combination 6 >>Last Segment >>Complete list >>>Complete >Combination 7 >>Last Segment >>Complete list >>>Complete >>First Segment >Combination 8 >>Complete list >>>Complete >Combination 9 >>Complete list >>>Complete >>First Segment >Combination 10 >>>Complete SIB of size 215 to 226 >Combination 11 >>Last segment of size 215 to 222 MP MP MP MP MP MP MP MP MP MP MP MP MP MP MP MP
Need
4-5
II. Example
4-6
UE
PAGING TYPE 1
UTRAN
Figure 4-4 System information modification (in idle mode and in state CELL_PCH or URA_PCH)
UE
SYSTEM INFORMATION CHANGE INDICATION
UTRAN
5.2 Paging
5.2.1 Overview
Paging includes CN originated paging and UTRAN originated paging. The CN originated paging procedure is used to establish a signaling connection. It is divided into co-ordination paging and non co-ordination paging. The CN indicates in the RANAP PAGING message whether the RNC shall perform the UTRAN coordination paging. In the case of co-ordination paging, the RNC shall check whether the UE has other CN domain signaling connections besides the paging domain connection. If so and the UE is in CELL_DCH or CELL_FACH state, the paging message shall be transmitted on the already connected DCCH on the radio interface. If so and the UE is in CELL_FACH or URA_PCH state, the paging message shall be transmitted on the PCCH on the radio interface. If no, the paging message shall be transmitted on the PCCH.
5-1
In the case of non co-ordination paging, the RNC need not check whether the UE has other CN domain signaling connections besides the paging domain connection but directly transmit the paging message on the PCCH in the CN specified paging area. UTRAN may initiate paging for UEs in CELL_PCH or URA_PCH state to trigger a cell update procedure to CELL_FACH state. In addition, UTRAN may initiate paging for UEs to trigger reading of updated system information. For UEs in idle mode or in CELL_PCH or URA_PCH state, RNC initiates the paging procedure by transmitting a PAGING TYPE 1 message on the PCCH. For UEs in CELL_FACH or CELL_DCH state, RNC initiates the paging procedure by transmitting a PAGING TYPE 2 message on the DCCH.
UE
PAGING TYPE 1
UTRAN
Figure 5-1 Paging procedure for UEs in idle mode or in PCH state UTRAN initiates the paging procedure by transmitting a PAGING TYPE 1 message on an appropriate paging occasion on the PCCH. UTRAN may repeat transmission of a PAGING TYPE 1 message to a UE on several paging occasions to increase the probability of proper reception of a page. UEs in idle mode and in PCH state receive the paging information from the network layer for all its monitored paging occasions. The paging procedure ends.
5-2
UE
PAGING TYPE 2
UTRAN
UTRAN initiates the paging procedure by transmitting a PAGING TYPE 2 message on the DCCH. Such paging procedure is also called dedicated paging procedure. The UE receives and reads the PAGING TYPE 2 message and forwards the Paging cause IE and the Paging record type identifier IE to NAS in it. The paging procedure ends. This procedure shall not affect the state of any other ongoing RRC procedures at the UE. If the UE receives a PAGING TYPE 2 message which contains a protocol error, the UE shall discard that paging message and transmit an RRC STATUS message on the uplink DCCH using AM RLC.
5-3
II. Example
5-4
II. Example
5-5
UE
1.CCCH : RRC CONNECTION REQUEST RRC
NodeB
RNC
RRC
2.Allocate parameters such asRNTIL1 L2 3. RADIO LINK SETUP REQUEST NBAP 4. RADIO LINK SETUP RESPONSE NBAP NBAP NBAP
Each step is explained in the following list: 1) 2) The UE sends an RRC CONNECTION REQUEST message on the uplink CCCH, requesting for the establishment of an RRC connection. The RNC determines, according to the cause in the RRC connection request and the system resource status, to set up the RRC connection on a dedicated channel and allocates the RNTI, radio resources and other resources (L1 and L2 resources). 3) The RNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resources required for an RRC connection. 4) 5) The NodeB responds with a RADIO LINK SETUP RESPONSE message to the RNC after successfully preparing the resources. The RNC sets up the Iub interface user plane transport bearer using ALCAP and performs the NodeB synchronization procedure.
5-6
6)
The RNC sends an RRC CONNECTION SETUP message to the UE on the downlink CCCH. The message contains the information about the dedicated channel allocated by the RNC.
7)
The UE sends an RRC CONNECTION SETUP COMPLETE message on the just established uplink DCCH after confirming that the RRC connection is successfully set up. The RRC connection setup procedure ends.
NodeB
RNC
2.Allocate parameters such as RNTIL1 L2 3.Map the logical channels used by UE to the common channels
4.CCCH: :RRC CONNECTION SETUP RRC 5. DCCH: RRC CONNECTION SETUP COMPLETE RRC RRC RRC
5-7
UE
RNC
5-8
Need
Comments Originating High Priority Signalling, Originating Low Priority Signalling, Call re-establishment, Terminating High Priority Signalling, Terminating Low Priority Signalling, Terminating cause unknown
MD
OP
5-9
II. Example
5-10
Need MP
Comments
MP MD Activation time defines the exact starting time point of the operation caused by the message. The range is 0255 (CFN)
MP OP MP
UTRAN DRX cycle length coefficient Capability update requirement RB Information Elements Signaling RB information to setup list >Signaling RB information to setup
MP MD
MP MP
TrCH Information Elements Uplink transport channels UL Transport channel information common for all transport channels Added or Reconfigured TrCH information list >Added or Reconfigured UL TrCH information Downlink transport channels DL Transport channel information common for all transport channels OP MP MP OP
5-11
Information Element/Group name Added or Reconfigured TrCH information list >Added or Reconfigured DL TrCH information PhyCH information elements Frequency info Uplink radio resources Maximum allowed UL TX power CHOICE channel requirement >Uplink DPCH info >CPCH SET Info Downlink radio resources Downlink information common for all radio links Downlink information per radio link list >Downlink information for each radio link
Need MP
Comments
MP
MD MD OP OP
OP MP
5-12
II. Example
5-13
Information Element/Group name Message Type UE information elements RRC transaction identifier Initial UE identity Rejection cause
Need MP MP MP MP
Comments
Wait time
MP
Indicate the time that the UE needs to wait to re-send the RRC connection request
Redirection info
OP
II. Example
None
5-14
IE/Group Name >TFCS >UL DPCCH Slot Format > UL SIR Target >Diversity mode >SSDT cell ID Length >S Field Length DL DPCH Information >TFCS >DL DPCH Slot Format >TFCI signalling mode >TFCI presence >Multiplexing Position >PDSCH RL ID >PDSCH code mapping >Power Offset Information >>PO1 >>PO2 >>PO3 >FDD TPC DL Step Size >Limited Power Increase >Inner Loop DL PC Status DCH Information DSCH Information TFCI2 bearer information >ToAWS >ToAWE M M M M M M M M M O M M M M M M M O
Presence
C-FBI
5-15
IE/Group Name RL Information >RL ID >C-ID >First RLS Indicator >Frame Offset >Chip Offset >Propagation Delay >Diversity Control Field M M M M M O
Presence
C NotFirstRL
>DL Code Information >Initial DL transmission Power >Maximum DL power >Minimum DL power >SSDT Cell Identity >Transmit Diversity Indicator
M M M M O C Diversity mode
5-16
II. Example
5-17
Note: Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall perform a cell update procedure using the cause "uplink data transmission" to transfer the UE to the CELL_FACH state. When the cell update procedure completed successfully, the UE shall continue with the initial direct transfer procedure.
5-18
UE
1. INITIAL DIRECT TRANSFER RRC
SRNC
RRC
CN
2.INITIAL UE MESSAGE RANAP RANAP 3.CONNECITON CONFIRMSUCCESS SCCP 4.CONNECTION REFUSEFAILURE SCCP SCCP SCCP
Each step is explained in the following list: 1) After the RRC connection is set up, the UE sends an INITIAL DIRECT TRANSFER message to the RNC. The message shall contain the initial NAS message and CN domain identity the UE wants to send to the CN. 2) After receiving the INITIAL DIRECT TRANSFER message from the UE, the RNC sends an INITIAL UE MESSAGE to the CN on the Iu interface as a Connection Request (CR) for SCCP connection establishment. The message shall contain the message the UE sends to the CN. 3) The CN shall return a CONNECTION CONFIRM message to the RNC if it determines to accept the connection request and the SCCP connection is successfully set up. Upon reception of the message, the RNC confirms that the connection is successfully set up. 4) The CN shall return a CONNECTION REFUSE message to the RNC if it determines to refuse the connection request and the SCCP connection setup fails. Upon reception of the message, the RNC confirms that the connection setup fails and initiates an RRC release procedure. The initial direct transfer procedure ends. For the NAS message contained in INITIAL DIRECT TRANSFER and INITIAL UE MESSAGE from UE to CN, the acceptance or reject information is forwarded from CN to UE by the downlink transfer procedure.
5-19
Note: Upon initiation of the uplink direct transfer procedure in CELL_PCH or URA_PCH state, the UE shall perform a cell update procedure using the cause "uplink data transmission" to transfer the UE to the CELL_FACH state. When the cell update procedure completed successfully, the UE shall continue with the uplink direct transfer procedure.
UE
1. UPLINK DIRECT TRANSFER RRC
SRNC
RRC
CN
Each step is explained in the following list: 1) The UE sends an UPLINK DIRECT TRANSFER message to the RNC to initiate an uplink direct transfer procedure. The message shall contain the NAS messages and CN domain identity. 2) On reception of the UPLINK DIRECT TRANSFER message, the RNC shall send a DIRECT TRANSFER message on the Iu interface to the CN according to the CN domain identity so as to route the NAS messages to the CN.
Note: If the UPLINK DIRECT TRANSFER message includes the Measured results on RACH IE information unit, it indicates the message carries a measurement report. UTRAN should extract the contents to be used for radio resource control. The rest of the message continues to be sent to the CN.
5-20
UE
SRNC
1.DIRECT TRANSFER RANAP
CN
RANAP
Each step is explained in the following list: 1) 2) The CN sends a DIRECT TRANSFER message to the RNC to initiate a downlink direct transfer procedure. The message shall contain the NAS messages. UTRAN sends a DOWNLINK DIRECT TRANSFER message on the downlink DCCH using AM RLC. The message shall contain the NAS messages and CN domain identity the CN wants to send to the US. The UE receives and reads the NAS messages contained in the DOWNLINK DIRECT TRANSFER message. If the UE receives a DOWNLINK DIRECT TRANSFER message which contains a protocol error, the UE shall transmit an RRC STATUS message on the uplink DCCH using AM RLC. The downlink direct transfer procedure ends.
5-21
II. Example
5-22
Information Element/Group name CN domain identity NAS message Measurement information elements Measured results on RACH
Need MP MP
Semantics description
OP
II. Example
5-23
Need MP MP
II. Example
5-24
When the RRC connection is successfully set up, the RNC sends a UE CAPABILITY ENQUIRY message to the UE if it finds the capability information about the corresponding UE does not exist. UE returns a UE CAPABILITY INFORMATION message to the RNC which contains the UE capability information. When the UE capability information changes during the RRC connection setup procedure, the UE transmits the updated UE capability to the RNC through a UE CAPABILITY INFORMATION message.
UE
UE CAPABILITY ENQUIRY
UTRAN
The UE capability enquiry procedure is initiated by UTRAN by transmitting a UE CAPABILITY ENQUIRY message on the downlink DCCH using AM RLC.
5-25
1) 2)
The UE sends a UE CAPABILITY INFORMATION message on the uplink DCCH using AM or UM RLC. The message shall contain the UE capability information. UTRAN reads the UE capability information and returns a UE CAPABILITY INFORMATION CONFIRM message on the downlink DCCH using AM or UM RLC. The UE capability information update procedure ends.
Note: RAB ASSIGNMENT REQUEST is initiated by CN; each UE can have one RAB or several RABs.
The RAB setup procedure can be classified into the following three kinds according to the RRC connection status before and after the RAB setup: DCH-DCH: The RRC connection is on a DCH before the RAB setup and also on a DCH after the RAB setup. CCH-DCH: The RRC connection is on a CCH before the RAB setup and on a DCH after the RAB setup.
5-26
CCH-CCH: The RRC connection is on a CCH before the RAB setup and also on a CCH after the RAB setup.
5.6.2 DCH-DCH
When the current RRC status of the UE is DCH, the assigned RAB can only be set up on a DCH. The RAB setup procedure can be further classified into the following two kinds according to the radio link reconfiguration situation: Synchronized radio link reconfiguration Unsynchronized radio link reconfiguration The difference is that in the former kind of procedure the NodeB and UE cannot invoke the reconfiguration parameters immediately after they receive the configuration messages from the Serving Radio Network Controller (SRNC) while in the latter they can.
5-27
UE
NodeB
SRNC
1. RAB ASSIGNMENT REQUEST RANAP 2.ALCAP setup
CN
RANAP
3. RADIO LINK RECONFIGURATION PREPARE (Synchronised) NBAP NBAP 4. RADIO LINK RECONFIGURATION READY (Synchronised) NBAP NBAP
5.ALCAP Setup and synchronization 6. RADIO BEARER SETUP RRC RRC 7. RADIO LINK RECONFIGURATION COMMIT (Synchronised) NBAP
NBAP RRC
8. RADIO BEARER SETUP COMPLETE RRC 9. RAB ASSIGNMENT RESPONSE RANAP RANAP
Each step is explained in the following list: 1) 2) The CN sends an RAB ASSIGNMENT REQUEST message to UTRAN to initiate an RAB setup procedure. Upon reception of the RAB ASSIGNMENT REQUEST message, the SRNC shall map the QoS parameter for the RAB to the AAL2 link characteristic parameter and radio resource characteristic parameter. The ALCAP on the Iu interface shall initiate an Iu interface user plane transport bearer setup procedure according to the AAL2 link characteristic parameter (as for PS domain, the ALCAP step does not exist). 3) The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the controlled NodeB to request the NodeB to prepare to add one (or several) DCH(s) to the existing radio link for bearing the RAB. 4) The NodeB allocates the corresponding resources and returns a RADIO LINK RECONFIGURATION READY message to the SRNC which it belongs to, informing it that the radio link reconfiguration is ready. 5) The ALCAP on the Iub interface at the SRNC initiates an Iub interface user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization by exchanging the uplink & downlink synchronization frame in the DCH frame protocol. 6) 7) The SRNC sends an RRC message RADIO BEARER SETUP to the UE. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the controlled NodeB.
5-28
8) 9)
After performing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. Upon reception of the RADIO BEARER SETUP COMPLETE message, the SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB setup procedure ends.
CN
2.ALCAP setup 3. RADIO LINK RECONFIGURATION REQUEST NBAP 4. RADIO LINK RECONFIGURATION RESPONSE NBAP NBAP
NBAP
6. RADIO BEARER SETUP RRC 7. RADIO BEARER SETUP COMPLETE RRC RRC 8. RAB ASSIGNMENT RESPONSE RANAP RANAP RRC
Each step is explained in the following list: 1) 2) The CN sends a RANAP message RAB ASSIGNMENT REQUEST to the SRNC to initiate an RAB setup procedure. Upon reception of the RAB ASSIGNMENT REQUEST message, the SRNC shall map the QoS parameter for the RAB to the AAL2 link characteristic parameter and radio resource characteristic parameter. The ALCAP on the Iu interface shall initiate an Iu interface user plane transport bearer setup procedure according to the AAL2 link characteristic parameter (as for PS domain, the ALCAP step does not exist).
5-29
3)
In the unsynchronized situation, the radio link reconfiguration need not be implemented synchronously. The SRNC sends a NBAP message RADIO LINK RECONFIGURATION REQUEST to the controlled NodeB, requesting the NodeB to reconfigure the DCH in the existing radio link.
4)
Upon reception of the RADIO LINK RECONFIGURATION REQUEST message, the NodeB allocates the corresponding resources and returns a RADIO LINK RECONFIGURATION RESPONSE message to the SRNC which it belongs to, informing the SRNC that it finishes radio link reconfiguration.
5)
The ALCAP on the Iub interface at the SRNC initiates an Iub interface user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization by exchanging the uplink & downlink synchronization frame in the DCH frame protocol.
6) 7) 8)
The SRNC sends an RRC message RADIO BEARER SETUP to the UE. After performing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC Upon reception of the RADIO BEARER SETUP COMPLETE message, the SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB setup procedure ends.
5.6.3 CCH-DCH
When the RRC connection is on a CCH, the RNC can set up the assigned RAB on a DCH according to the QoS parameter in the RAB ASSIGNMENT REQUEST message. The RRC status shall be transferred from the CCH to the DCH. Figure 5-13 illustrates the CCH-DCH RAB setup procedure.
5-30
UE
NodeB
SRNC
1. RABASSIGNMENT REQUEST RANAP
CN
RANAP
2. ALCAP setup 3. NBAP 4. NBAP RADIO LINK SETUP RESPONSE NBAP RADIO LINK SETUP REQUEST NBAP
5.ALCAP Setup and synchronization 6. RADIO BEARER SETUP RRC 7. RADIO BEARER SETUP COMPLETE RRC RRC 8. RAB ASSIGNMENT RESPONSE RANAP RANAP RRC
Each step is explained in the following list: 1) 2) The CN sends a RANAP message RAB ASSIGNMENT REQUEST to the SRNC to initiate an RAB setup procedure. Upon reception of the RAB ASSIGNMENT REQUEST message, the SRNC shall map the QoS parameter for the RAB to the AAL2 link characteristic parameter and radio resource characteristic parameter. The ALCAP on the Iu interface shall initiate an Iu interface user plane transport bearer setup procedure according to the AAL2 link characteristic parameter (as for PS domain, the ALCAP step does not exist). 3) The SRNC initiates an Iub interface radio link setup procedure by sending a RADIO LINK SETUP REQUEST message to the controlled NodeB to request the NodeB to allocate the specific radio link resources required for the RRC connection. 4) 5) 6) 7) 8) After preparing the resources, the NodeB returns a RADIO LINK SETUP RESPONSE message to the RNC. The RNC sets up an Iub interface user plane transport bearer using ALCAP and performs the NodeB synchronization procedure. The SRNC sends an RRC message RADIO BEARER SETUP to the UE. After performing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. Upon reception of the RADIO BEARER SETUP COMPLETE message, the SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB setup procedure ends.
5-31
5.6.4 CCH-CCH
When the RRC connection is on a CCH, the RNC can set up the assigned RAB on a CCH according to the QoS parameter in the RAB ASSIGNMENT REQUEST message. Figure 5-14 illustrates the CCH-CCH RAB setup procedure.
UE NodeB SRNC
1. RAB ASSIGNMENT REQUEST
CN
RANAP
RANAP
2. ALCAP setup 3. RADIO BEARER SETUP RRC 4. RADIO BEARER SETUP COMPLETE RRC 5. RAB ASSIGNMENT RESPONSE RANAP RANAP RRC
RRC
Each step is explained in the following list: 1) 2) The CN sends a RANAP message RAB ASSIGNMENT REQUEST to UTRAN to initiate an RAB setup procedure. Upon reception of the RAB ASSIGNMENT REQUEST message, the SRNC shall map the QoS parameter for the RAB to the AAL2 link characteristic parameter and radio resource characteristic parameter. The ALCAP on the Iu interface shall initiate an Iu interface user plane transport bearer setup procedure according to the AAL2 link characteristic parameter (as for PS domain, the ALCAP step does not exist). 3) 4) 5) The SRNC sends an RRC message RADIO BEARER SETUP to the UE. After performing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. Upon reception of the RADIO BEARER SETUP COMPLETE message, the SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB setup procedure ends.
5-32
5-33
IE/Group Name RABs To Be Released List >RABs To Be Released Item IEs >>RAB ID >>Cause M M
Presence C ifNoOtherGroup
Comments
Release cause
5-34
II. Example
5-35
>RABs Released Item IEs >>RAB ID >>DL Data Volumes >>>Data Volume List >>>>Unsuccessfully Transmitted DL Data Volume >>>>Data Volume Reference >>DL GTP-PDU Sequence Number >>UL GTP-PDU Sequence Number RABs Queued List >RABs Queued Item IEs >>RAB ID RABs Failed To Setup Or Modify List M C ifNoOtherGroup O C-ifAvailUiPS C-ifAvailUiPS C ifNoOtherGroup
5-36
IE/Group Name >RABs Failed To Setup Or Modify Item IEs >>RAB ID >>Cause RABs Failed To Release List >RABs Failed To Release Item IEs >>RAB ID >>Cause Criticality Diagnostics M M O M M
Presence
Comments
C ifNoOtherGroup
5-37
II. Example
5-38
Information Element/Group name RRC transaction identifier Integrity check info Integrity protection mode info Ciphering mode info Activation time New U-RNTI New C-RNTI RRC State Indicator UTRAN DRX cycle length coefficient CN Information Elements CN Information info UTRAN mobility information elements URA identity RB Information Elements Signaling RB information to setup list >Signaling RB information to setup RAB information to setup list >RAB information for setup RB information to be affected list >RB information to be affected Downlink counter synchronisation info >RB with PDCP information list >>RB with PDCP information TrCH Information Elements Uplink transport channels UL Transport channel information common for all transport channels OP OP MP OP MP OP MP OP OP MP OP OP MP CH OP OP MD OP OP MP MD
Need
5-39
Information Element/Group name Deleted TrCH information list >Deleted UL TrCH information Added or Reconfigured TrCH information list >Added or Reconfigured UL TrCH information CHOICE mode >FDD >>CPCH set ID >>Added or Reconfigured TrCH information for DRAC list >>>DRAC static information >TDD Downlink transport channels DL Transport channel information common for all transport channels Deleted TrCH information list >Deleted DL TrCH information Added or Reconfigured TrCH information list >Added or Reconfigured DL TrCH information PhyCH information elements Frequency info Uplink radio resources Maximum allowed UL TX power CHOICE channel requirement >Uplink DPCH info >CPCH SET Info Downlink radio resources MD OP MD MP OP MP OP OP MP OP OP MP OP OP MP OP
Need
5-40
Information Element/Group name CHOICE mode >FDD >>Downlink PDSCH information >TDD Downlink information common for all radio links Downlink information per radio link list >Downlink information for each radio link OP OP MP OP MP
Need
5-41
II. Example
5-42
5-43
CN
The SRNC sends an IU RELEASE REQUEST message to the CN domain to initiate an Iu interface release request procedure. The message shall contain the cause for the Iu connection release request. The CN determines how to respond to the Iu release request. For example, the CN may initiate an Iu release procedure if it determines to release the Iu connection.
RNC
1.IU RELEASE COMMAND 2.IU RELEASE COMPLETE
CN
5-44
1)
The CN sends an IU RELEASE COMMAND to UTRAN to initiate a signaling connection release procedure. The message shall contain the cause for the signaling connection release e.g., "Successful Relocation", "Normal Release", "Release due to UTRAN Generated Reason", "Relocation Cancelled" and "No Remaining RAB". After sending the message, the CN shall no more send any connection-oriented RANAP message on that connection.
2)
Upon reception of the IU RELEASE COMMAND message, the RNC shall clear the related resources in UTRAN. The RNC returns an IU RELEASE COMPLETE message to the CN. The Iu signaling connection release procedure ends.
5-45
UE
Serving RNC
RANAP
CN
NBAP
3.RADIO LINK RECONFIGURATION READY NBAP NBAP RRC 4:RADIO BEARER RELEASE RRC
Apply new transport format set DCCH 6.DCCH : RADIO BEARER RELEASE COMPLETE
RRC
RRC
8. ALCAP Iu Data TransportBearer Release not required towards PS domain RANAP 9. RAB ASSIGNMENT RESPONSE RANAP
Each step is explained in the following list: 1) The CN sends an RAB ASSIGNMENT REQUEST (release) message to initiate an RAB release procedure. The message shall indicate the ID of the RAB to be released. 2) The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, requesting the NodeB to prepare to release the DCH bearing the RAB. 3) 4) 5) 6) 7) The NodeB returns a RADIO LINK RECONFIGURATION READY message to the SRNC, informing it that the release is ready. The SRNC sends a RADIO BEARER RELEASE message to the UE to initiate the bearer release procedure. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. The SRNC receives a RADIO BEARER RELEASE COMPLETE message from the UE. The SRNC initiates an Iub interface user plane transport bearer release procedure using ALCAP.
5-46
8)
If it is an AAL2 bearer, the SRNC uses an ALCAP AAL2 release message to initiate the Iu interface data transport bearer release from the CN (this step is not required towards PS domain).
9)
The SRNC sends a RANAP message RAB ASSIGNMENT RESPONSE to the CN. The RAB release procedure ends.
Note: In the case of user plane exception at RNC, the RNCAP shall send an RAB RELEASE REQUEST message to the CN, requesting the CN to release the affected RAB, as illustrated in Figure 5-18.
RNC
RAB RELEASE REQUEST
CN
5-47
UE
CN
RANAP
2 RADIO LINK RECONFIGURATION PRPARE NBAP NBAP [DCH Deletion] 3.RADIO LINK RECONFIGURATION READY NBAP NBAP RRC 4:RADIO BEARER RELEASE RRC
Apply new transport format set DCCH 6.DCCH : RADIO BEARER RELEASE COMPLETE
RRC
RRC
RANAP
Figure 5-19 Combined release of CS domain Iu signaling link and RAB (DCH-DCH)
1) 2) 3) 4) 5) 6) 7) 8) 9)
CN sends IU RELEASE COMMAND message to SRNC. SRNC sends RADIO LINK RECONFIGURATION PREPARE message to NodeB, requesting NodeB to prepare for the release of DCH that bears the RAB. NodeB sends RADIO LINK RECONFIGURATION READY to SRNC, informing SRNC that the release is ready. SRNC sends RADIO BEARER RELEASE to UE, starting the bearer release procedure. SRNC sends RADIO LINK RECONFIGURATION COMMIT to NodeB. SRNC receives the RADIO BEARER RELEASE COMPLETE message of UE. RNC releases the data transfer bearer of Iub interface through ALCAP protocol. SRNC uses ALCAP protocol. If it is AAL2 bearer, it uses AAL2 release message to start the release of Iu data transfer bearer between CN. SRNC sends IU RELEASE COMPLETE message to CN.
5-48
The RRC connection release procedure is used to release the RRC connection including all radio bearers between the UE and the UTRAN. By doing so, all established signaling connections will be released. The RRC connection release procedure can be divided into two kinds according to the RRC status i.e., RRC release on a DCH and RRC release on a CCH. Only when the UE is in CELL_DCH or CELL_FACH state, can RRC connection release be implemented. If the RRC is currently in CELL_PCH or URA_PCH state, UTRAN shall initiate a paging procedure to transfer the UE to CELL_FACH state before it performs the release. The RNC shall send an RRC CONNECTION RELEASE message on the downlink DCCH or CCCH using UM RLC. UTRAN sends RRC CONNECTION RELEASE message using DCCH channel if DCCH is available. Otherwise, UTRAN sends the message using CCCH.
SRNC
RRC
RRC
2.RRC CONNECTION RELEASE COMPLETE RRC 3. RADIO LINK DELETION REQUEST NBAP 4. RADIO LINK DELETION RESPONSE NBAP NBAP NBAP RRC
5.ALCAP Release
Each step is explained in the following list: 1) The SRNC sends the RRC CONNECTION RELEASE message to the UE on the DCCH. It may transmit several RRC CONNECTION RELEASE messages to increase the probability of proper reception of the message by the UE 2) 3) The UE returns an RRC CONNECTION RELEASE COMPLETE message to the SRNC. The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB to delete the radio link resources in the NodeB.
5-49
4) 5)
After releasing the resources, the NodeB returns a RADIO LINK DELETION RESPONSE message to the SRNC. The RNC initiates an Iub interface user plane transport bearer release procedure using ALCAP. The RRC connection release procedure ends.
UE
NodeB
RRC CONNECTION RELEASE
SRNC
RRC
RRC
The SRNC sends the RRC CONNECTION RELEASE message to the UE on the CCCH to initiate an RRC connection release procedure. The UE shall release the resources. In the case of RRC connection release on a CCH, the RRC CONNECTION RELEASE COMPLETE is not required. UTRAN shall release only the UE rather than the NodeB resources and data transport bearer, for the UE uses only the cell common resources.
Note: UTRAN may transmit several RRC CONNECTION RELEASE messages to increase the probability of proper reception of the message by the UE. The RRC message sequence number (RRC SN) for these messages is the same. The number of repetitions and the repetition period are controlled by the network
5-50
6-1
UTRAN
Figure 6-1 Basic cell update procedure Each step is explained in the following list: 1) 2) The UE sends a CELL UPDATE message to the RNC to initiate a cell update procedure. The message shall contain the cell update cause, U-RNTI and so on. The RNC returns a CELL UPDATE CONFIRM message to the UE. The message may contain the transport channel information elements, physical channel information elements, radio bearer information elements, U-RNTI and so on. Upon reception of the CELL UPDATE CONFIRM message, the UE shall invoke information elements in the message and performs corresponding status transition. Depending on the different information elements included in the CELL UPDATE CONFIRM message, the UE may return different messages or no message to the RNC. The messages the UE may return are given below: RADIO BEARER RELEASE COMPLETE RADIO BEARER RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE PHYSICAL CHANNEL RECONFIGURATION COMPLETE UTRAN MOBILITY INFORMATION CONFIRM The cell update procedure ends. This section describes a cell update instance in which the UE returns a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the radio interface, as illustrated in Figure 6-2.
UE
RRC 2.CELL UPDATE CONFIRM RRC 3.PHYSICAL CHANNEL RECONFIGURATION COMPLETE RRC RRC RRC
NodeB
1.CELL UPDATE
RNC
RRC
6-2
The CELL UPDATE CONFIRM message contains the C-RNTI and U-RNTI the network allocates to the UE. After invoking the new parameters, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the RNC. The cell update procedure ends.
Figure 6-3 Basic URA update procedure Each step is explained in the following list: 1) 2) The UE sends a URA UPDATE message to the RNC to initiate a URA update procedure. The message shall contain the URA update cause, U-RNTI and so on. The RNC returns a URA UPDATE CONFIRM message to the UE. The message may contain the new C-RNTI, U-RNTI, ciphering mode info, integrity protection mode info and so on. Upon reception of the URA UPDATE CONFIRM message, the UE shall invoke information elements in the message and send a PHYSICAL CHANNEL RECONGURITION COMPLETE message or no message to the RNC depending on the different information elements included in the URA UPDATE CONFIRM message. This section describes a URA update instance in which a PHYSICAL CHANNEL RECONGURITION COMPLETE message is sent, as illustrated in Figure 6-4.
6-3
UE
RRC
NodeB
1.URA UPDATE
RNC
RRC
2.URA UPDATE CONFIRM RRC 3.PHYSICAL CHANNEL RECONFIGURATION COMPLETE RRC RRC RRC
Figure 6-4 URA update procedure The URA UPDATE CONFIRM message contains RRC Transaction Identity and RRC State Indicator, and may contain the CN information elements, integrity protection mode info, ciphering mode info, new C-RNTI and U-RNTI. After invoking the new parameters, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the RNC. The URA update procedure ends.
Need
Type and reference re-entered service area, radio link failure, RLC unrecoverable error
Failure cause RB timer indicator Measurement information elements Measured results on RACH
OP MP
OP
6-5
II. Example
6-6
Information Element/Group name UE information elements U-RNTI RRC transaction identifier Integrity check info URA update cause MP
Need
CV- ProtErr CH MP
MD
CV-ProtErr
6-7
II. Example
6-8
1)
The UE performs measurements for the intra-frequency neighboring cells according to the measurement control information from the RNC. The measurement results are reported to the RNC after a certain processing.
2) 3) 4) 5)
The RNC compares the measurement results with the set thresholds to determine which cell shall be added or deleted. The RNC requests the NodeB to prepare if it determines to add a cell. The RNC requests the UE to add and/or delete a cell through an ACTIVE SET UPDATE procedure. The UE successfully performs the active set update. RNC shall request the NodeB to release the corresponding RL resources if it deletes a cell.
Decision to setup new RL 1. RADIO LINK SETUP REQUEST RNSAP 2. RADIO LINK SETUP REQUEST NBAP Start RX description NBAP 3. RADIO LINK SETUP RESPONSE NBAP 4.ALCAP Iub Bearer setup 5. RADIO LINK SETUP RESPONSE RNSAP 6.ALCAP Iur Bearer setup Start TX description 7. ACTIVE SET UPDATE RRC [RADIO LINK ADDITION] 8. ACTIVE SET UPDATE COMPLETE RRC RRC RNSAP NBAP RNSAP
RRC
Figure 6-5 Soft handover procedure (radio link addition) Each step is explained in the following list: 1) According to the resource usage situation, the SRNC decides to set up a radio link in the new cell in DRNC. It sends a RNSAP message RADIO LINK SETUP
6-9
REQUEST to the DRNC, requesting for radio resources. If this is the first radio link between the DRNC and the UE, a signaling connection shall also be established on the Iur interface for bearing the RNSAP signaling associated with the UE. 2) After confirming that the resources requested by the SRNC are available, the DRNC sends a NBAP message RADIO LINK SETUP REQUEST to the target NodeB. The NodeB starts uplink receiving. 3) After successfully allocating the resources requested by the SRNC, the NodeB sends a NBAP message RADIO LINK SETUP RESPONSE to the DRNC, reporting the allocation result. 4) 5) 6) 7) The DRNC initiates an Iub interface transport bearer setup procedure using ALCAP. The DRNC sends a RNSAP message RADIO LINK SETUP RESPONSE to the SRNC. The SRNC initiates an Iur interface transport bearer setup procedure using ALCAP. The SRNC transmits the ACTIVE SET UPDATE (Radio Link Addition) message to the UE on the DCCH. The message shall contain the information about the radio link to be added. 8) The UE adds the corresponding radio link information to the active set and returns an RRC message ACTIVE SET UPDATE COMPLETE message to the SRNC. The soft handover procedure (radio link addition) ends.
6-10
UE
NodeB DRNS
DRNC
SRNC
Decision to delete old RL 1. ACTIVE SET UPDATE RRC RADIO LINK DELETION RRC 2. ACTIVE SET UPDATE COMPLETE RRC RNSAP 4. RADIO LINK DELETION REQUEST NBAP Stop RX and TX 5. RADIO LINK DELETION RESPONSE NBAP NBAP 6.ALCAP Iub Bearer release 7. RADIO LINK DELETION RESPONSE RNSAP 8.ALCAP Iur Bearer release RNSAP NBAP 3. RADIO LINK DELETION REQUEST RNSAP RRC
Figure 6-6 Soft handover procedure (radio link deletion) Each step is explained in the following list: 1) According to the resource usage situation, the SRNC decides to delete a radio link from the DRNC. It transmits the RRC message ACTIVE SET UPDATE (Radio Link Deletion) to the UE on the DCCH. The message shall contain the information about the radio link to be deleted. 2) The UE stops downlink receiving on the radio link and deletes that radio link. Then it sends an RRC message ACTIVE SET UPDATE COMPLETE to the SRNC. 3) After confirming that the deleted radio link is in the DRNC, the SRNC sends a RNSAP message RADIO LINK DELETION REQUEST to the DRNC, requesting the DRNC to release the allocated radio resources. 4) 5) The DRNC sends a NBAP message RADIO LINK DELETION REQUEST to the NodeB, requesting the NodeB to release the allocated radio resources. After successfully releasing the radio resources, the NodeB returns a NBAP message RADIO LINK DELETION RESPONSE to the DRNC, reporting the release result. 6) 7) The DRNC initiates an Iub interface data transport bearer release procedure using ALCAP. The DRNC sends a RNSAP message RADIO LINK DELETION RESPONSE to the SRNC.
6-11
8)
The SRNC initiates an Iur interface data transport bearer release procedure using ALCAP. The soft handover procedure (radio link deletion) ends.
RNSAP
2. RADIO LINK SETUP REQUEST
RNSAP
NBAP
NBAP
NBAP
RRC
8. ACTIVE SET UPDATE COMPLETE RRC 9.RADIO LINK DELETION REQUEST NBAP Stop RX and TX 10.RADIO LINK DELETION RESPONSE NBAP NBAP
NBAP
Figure 6-7 Soft handover procedure (radio link addition and deletion) Each step is explained in the following list: 1) 6) These steps are the same as the steps 1) 6) in the "soft handover procedure (radio link addition)" (see Figure 6-5). Through these steps, a radio link is added to the NodeB under control of DRNC.
6-12
7) The SRNC transmits the RRC message ACTIVE SET UPDATE (Radio Link Addition & Deletion) message to the UE on the DCCH. The message shall contain the information about the radio links to be added & deleted. 8) After successfully adding & deleting the corresponding radio links, the UE sends an RRC message ACTIVE SET UPDATE COMPLETE to the NodeB. 9) 11) These steps are similar to the steps 3)7) in the "soft handover procedure (radio link deletion)" (see Figure 6-6). The difference is that the radio link is deleted from the NodeB under control of SRNC in this case. Therefore, no radio link deletion through Iur interface is implemented.
6-13
Information Element/Group name Uplink radio resources Maximum allowed UL TX power Downlink radio resources Radio link addition information >Radio link addition information Radio link removal information >Radio link removal information TX Diversity Mode SSDT information OP MP OP MP MD OP MD
Need
6-14
II. Example
intra-frequency hard handover and inter-frequency hard handover according to the comparison of working frequencies before and after the hard handover. Since the hard handovers performance is worse than the soft handovers, the hard handover procedure is generally not adopted unless the soft handover procedure cannot be implemented. Relocation shall be triggered along with hard handover when the UE performs the hard handover between different RNCs. Such relocation is generally called relocation with hard handover. The hard handover procedure may be performed by using one of the following five procedures on the Uu interface: Physical channel reconfiguration Transport channel reconfiguration Radio bearer setup Radio bearer release Radio bearer reconfiguration In the following, we will introduce the compressed mode and then introduce the hard handover of Iur interface and the CN combined hard handover to demonstrate the hard handover procedures.
6-16
The fundamental principle of compressed mode is given below: When in compressed mode, the UE transmits a radio frame compressed in time instead of a full radio frame so that the decoder can switch to another frequency or mode to perform inter-frequency and inter-RAT measurements during the transmission gap. The transmission time reduction can be achieved by puncturing or by SF/2. Puncturing is a method in which bits of a coded radio frame on a radio channel are regularly stopped to create a transmission gap. SF/2 is a method in which the spreading factor is halved to increase the transmission rate of data bits. That is, this method is used to transmit the bits originally transmitted in one radio frame in a shorter period so as to create a transmission gap. When the UE performs inter-frequency hard handover measurements, the NodeB shall also be in the compressed mode to ensure that the UE can receive messages from the RNC. Whether to use the compressed mode is determined by the RNC.
6-17
UE
SRNC
4. ALCAP
Iub Data Transport Bearer Setup 5. RADIO LINK SETUP RESPONSE RNSAP RNSAP
6. ALCAP Iur Data Transport Bearer Setup 7. PHYSICALl CHANNEL RECONFIGURATION RRC 8. RADIO LINK FAILURE INDICATION NBAP NBAP 9. RADIO LINK FAILURE INDICATION RNSAP 10. PHYSICAL CHANNEL RECONFIGURATION COMPLETE RRC 11. RADIO LINK DELETION REQUEST RNSAP 12. RADIO LINK DELETION REQUEST NBAP 13. RADIO LINK DELETION RESPONSE NBAP NBAP NBAP RNSAP RRC RNSAP RRC
14. ALCAP
Iub Data Transport Bearer Release 15. RADIO LINK DELETION RESPONSE RNSAP RNSAP
16. ALCAP
Figure 6-9 Hard handover (UE in DCH) on Iur interface Each step is explained in the following list: 1) 2) 3) 4) 5) The SRNC sends a RADIO LINK SETUP REQUEST message to the target RNC on the Iur interface. The target RNC allocates the RNTI and radio resources and sends a RADIO LINK SETUP REQUEST message to the target NodeB on the Iub interface. The target NodeB allocates the resources starts physical layer receiving and returns a RADIO LINK SETUP RESPONSE message to the target RNC. The target RNC initiates an Iub interface data transport bearer setup procedure using ALCAP. The target RNC sends a RADIO LINK SETUP RESPONSE message to the SRNC on the Iur interface.
6-18
6) 7) 8)
The SRNC initiates an Iur interface data transport bearer setup procedure using ALCAP. The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE on the Uu interface. The UE clears the previous radio links and access the network on the new radio links. The NodeB detects the radio link failure and sends a RADIO LINK FALURE INDICATION message to the CRNC on the Iub interface.
9)
The source RNC sends a RADIO LINK FAILURE INDICATION message to the SRNC on the Iur interface.
10) After setting up a radio connection to the target RNC and allocating the necessary radio resources, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SRNC on the Uu interface. 11) The SRNC sends a RADIO LINK DELETION REQUEST message to the source RNC on the Iur interface. 12) The source RNC sends a RADIO LINK DELETION REQUEST message to the source NodeB on the Iub interface. 13) After successfully releasing the radio resources, the source NodeB returns a RADIO LINK DELETION RESPONSE message. 14) The source RNC initiates an Iub interface data transport bearer release procedure using ALCAP. 15) After successful release, the source RNC sends a RADIO LINK DELETION RESPONSE message to the SRNC. 16) The SRNC initiates an Iur interface data transport bearer release procedure using ALCAP. The hard handover procedure implemented on the Iur interface ends.
6-19
UE
NodeB Source
NodeB Target
RNC Source
RANAP RANAP
RNC Target
MSC
SGSN
RANAP
RANAP RANAP
RANAP
RANAP
RANAP
5. ALCAP Iu Data Transport Bearer Setup NBAP NBAP 6. RADIO LINK SETUP REQUEST 7. RADIO LINK SETUP RESPONSE NBAP NBAP
8. ALCAP Iub Data Transport Bearer Setup 9. RELOCATION REQUEST ACKNOWLEDGE RANAP 10. RELOCATION REQUEST ACKNOWLEDGE
RANAP
RANAP
RANAP
RANAP
RANAP
RANAP
RRC
RRC 14. RADIO LINK RESTORE INDICAITON NBAP RANAP 15. RELOCATION DETECT RANAP 16. RELOCATION DETECT RANAP
NBAP
NBAP
RANAP NBAP
RRC
RANAP
RANAP
RANAP
RANAP
RANAP
RANAP
23. ALCAP IU DATA TRANSPORT BEARER RELEASE RANAP 24. IU RELEASE COMPLETE RANAP
RANAP
RANAP
Figure 6-10 Combined hard handover (through CN domain) Each step is explained in the following list: 1)2): The source RNC decides to perform relocation with hard handover. The combined hard handover procedure starts. The source RNC sends two RELOCATION
6-20
REQUIRED messages respectively to two CN nodes. Upon reception of the RELOCATION REQUIRED message, the two CN nodes respectively make preparation for the handover procedure. 3)4): After successful preparation, the two CN nodes respectively send a RELOCATION REQUEST message to the target RNC, requesting the target RNC to allocate resources. The target RNC configures the necessary resources for the radio links to be set up during the hard handover procedure. 5): The target RNC and the MSC set up a new Iu interface transport bearer for the RAB associated with that MSC. 6): The target RNC allocates the RNTI and radio resources to the RRC connection and radio links and sends a RADIO LINK SETUP REQUEST message to the target NodeB. 7) The target NodeB allocates the resources starts physical layer receiving and sends a RADIO LINK SETUP RESPONSE message to the target RNC. 8): The target RNC initiates an Iub interface data transport bearer set up procedure using ALCAP. 9)10): After successful preparation, the target RNC sends two RELOCATION REQUEST ACKNOWLEDGE messages respectively to the two CN nodes. 11)12): After successful preparation for SRNC relocation, the two CN nodes respectively send a RELOCATION COMMAND message to the source RNC. 13): The source RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, informing it of the new physical channel parameters. 14)16): The target NodeB detects the radio link synchronization on the air interface and sends a RADIO LINK RESTORE INDICATION message to the target RNC, causing the target RNC to send RELOCATION DETECT messages respectively to the MSC and the SGSN. 17): When the UE is handed from the previous radio links over to the new ones, the NodeB detects the asynchronization of the previous radio links and sends a RADIO LINK FAILURE INDICATION message to the target RNC. 18)20): After successfully physical channel reconfiguration, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the target RNC, causing the target RNC to send RELOCATION COMPLETE messages respectively to the MSC and the SGSN. 21)22): The MSC and the SGSN respectively send an IU RELEASE COMMAND message to the source RNC to initiate an Iu connection release procedure. 23)25): Upon reception of the IU RELEASE COMMAND messages from the two CN nodes, the source RNC returns two IU RELEASE COMPLETE messages respectively to the CN node and releases all visible UTRAN resources associated with the RRC connection.
6-21
6-22
Information Element/Group name Maximum allowed UL TX power CHOICE channel requirement >Uplink DPCH info >CPCH SET Info >CPCH set ID Downlink radio resources CHOICE mode >FDD >>Downlink PDSCH information >TDD Downlink information common for all radio links Downlink information per radio link list >Downlink information for each radio link
Need MD OP
MP
OP
OP OP MP
6-23
II. Example
1)
WCDMA->GSM inter-RAT handover: This procedure is used to hand the UE in CELL_DCH state that sets up CS domain service in the WCDMA system over to the GSM system.
2)
GSM->WCDMA inter-RAT handover: This procedure is used to hand the UE in connection mode that sets up CS domain service in the GSM system over to the WCDMA system.
3) 4)
Note: This manual only introduces the signaling procedures of UTRAN. The signaling procedures of CN and GSM/BSS are not included. This section describes equipment in the format of ABC/abc to distinguish equipment that may exist in UMTS, GSM and GPRS systems. For example, GSM/MSC denotes the MSC in GSM.
Note: The signaling procedures between the UMTS/CN and the GSM/MSC and between the GSM/MSC and the GSM/BSC are outside the scope of this manual and are only schematically mentioned here.
6-25
SRNC
CN
GSM/MSC
GSM/BSC
1. RELOCATION REQUIRED RANAP RANAP 2. PREPARE HANDOVER MAP/E MAP/E 3. HANDOVER REQUEST BSSMAP BSSMAP
BSSMAP
6. RELOCATION COMMAND RANAP 7.DCCH : HANDOVER FROM UTRAN COMMAND RRC [Hard Handover] 8. HANDOVER DETECT RRC RANAP
BSSMAP
BSSMAP
Figure 6-11 Inter-RAT handover procedure (WCDMA->GSM) Each step is explained in the following list: 1) The SRNC decides to perform inter-RAT handover to the GSM system and sends a RELOCATION REQUIRED message to the CN on the Iu interface. 2) The CN sends a MAP message PREPARE HANDOVER to the GSM/MSC. 3) 4) these two steps indicate the signaling procedures in GSM and are only schematically mentioned here. 5) The GSM/MSC and the GSM/BSS perform the initialization procedure and return a MAP/E message PREPARE HANDOVER RESPONSE to the CN.
6-26
6) The CN sends a RANAP message RELOCATION COMMAND to the SRNC as a response to the RELOCATION REQUIRED message. 7) The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE on the existing RRC connection, commanding the UE to perform inter-RAT handover. 8) This step indicates a signaling procedure in GSM and is only schematically mentioned here. 9)10) The UE accesses the network via the GSM/BSS and sends a HANDOVER COMPLETE message. 11) The GSM/MSC detects the UE in the GSM coverage and sends a MAP/E message SEND END SIGNAL REQUEST to the CN. 12) The CN sends an IU RELEASE COMMAND message to initiate a release procedure for the SRNC allocated resources. 13) The UMTS releases the bearer resources and returns an IU RELEASE COMPLETE message to the CN on the Iu interface. 14) Upon completion of the call, the CN sends a MAP/E message SEND END SIGNAL RESPONSE to the GSM/MSC.
Note: The signaling procedures between the CN and the GSM/MSC and between the GSM/MSC and the GSM/BSC are outside the scope of this manual and are only schematically mentioned here.
6-27
UE
NodeB
RNC Target
CN
MSC
BSC
RANAP
RRC
10. RELOCATION COMPLETE RANAP RANAP 11. SEND END SIGNAL REQUEST MAP/E 12. CLEAR COMMAND BSSMAP BSSMAP
MAP/E
13. CLEAR COMPLETE BSSMAP 14. SEND END SIGNAL MAP/E RESPONSE MAP/E BSSMAP
Figure 6-12 Inter-RAT handover procedure (GSM->WCDMA) Each step is explained in the following list: 1) 2) 3) 4) 5) 6) The GSM/BSC sends a HANDOVER REQUIRED message to the GSM/MSC. The GSM/MSC sends a MAP/E message PREPARE HANDOVER to the CN. The CN sends a RELOCATION REQUEST message to the target RNC on the Iu interface. The target RNC returns a RELOCATION REQUEST ACKNOWLEDGE message to the CN. The CN sends a MAP/E message PREPARE HANDOVER RESPONSE to the GSM/MSC. The GSM/MSC sends a HANDOVER COMMAND message to the GSM/BSC.
6-28
7) 8) 9)
The GSM/BSC sends a HANDOVER COMMAND message to the UE, commanding the UE to access the network via the target RNC in UMTS. The target RNC detects the UE and sends a RELOCATION DETECT message to the CN node. The UE sets up an RRC connection to the target RNC. After allocating the necessary radio resources, the UE sends a HANDOVER TO UTRAN COMPLETE message to the target RNC.
10) The target RNC sends a RANAP message RELOCATION COMPLETE to the CN. 11) The CN sends a MAP/E message SEND END SIGNAL REQUEST to the GSM/MSC. 12) The GSM/MSC sends a CLEAR COMMAND message to the GSM/BSC. 13) The GSM/BSC returns a CLEAR COMPLETE message to the GSM/MSC. 14) The GSM/MSC sends a MAP/E message SEND END SIGNAL RESPONSE to the CN.
6-29
UE
CN
3. RANAP
Figure 6-13 Cell reselection procedure (UMTS->GPRS initiated by UE) 1) 2) The UE selects a GPRS cell, reads the system information of the cell and initiates a UE-GPRS signaling connection setup procedure. After necessary CN-GPRS preparation (e.g., UE context information retrieval), the CN sends an IU RELEASE COMMAND message to the SRNC to initiate an Iu connection release procedure. 3) After successful release, the SRNC returns an IU RELEASE COMPLETE message to the CN. The WCDMA->GPRS cell reselection procedure initiated by the UE ends.
6-30
measurement report, the network can initiate a WCDMA->GPRS cell reselection signaling procedure, as illustrated in Figure 6-14.
Note: The UMTS->GPRS cell reselection procedure can be initiated by the network only when the RNC can generate GSM messages.
UE
Serving RNC
CN
3. RANAP
Figure 6-14 Cell reselection procedure (UMTS->GPRS initiated by network) Each step is explained in the following list: 1) The SRNC decides to perform handover to GPRS for the UE based on the measurement results from the UE and sends a CELL CHANGE ORDER FROM UTRAN message to the UE. Upon reception of the message, the UE performs a UE-GPRS connection setup procedure. 2) After necessary CN-GPRS preparation (e.g., UE context information retrieval), the CN sends an IU RELEASE COMMAND message to the SRNC to initiate an RRC connection release procedure on the Iu interface. 3) After successfully releasing all resources reserved for the UE, the SRNC returns an IU RELEASE COMPLETE message to the CN. The WCDMA->GPRS cell reselection procedure initiated by the network ends.
6-31
II. Example
None
6-32
6-33
Information Element/Group name >>>>Downlink PDSCH information >>>TDD >>Downlink information common for all radio links >>Downlink information per radio link >>>Downlink information for each radio link >Preconfiguration >>CHOICE Preconfiguration mode >>>Predefined configuration >>>Default configuration >>>>Default configuration mode >>>>Default configuration identity >>RAB info >>Uplink DPCH info Downlink radio resources >>Downlink information common for all radio links >>Downlink information per radio link >>>Downlink information for each radio link >>CHOICE mode >>>FDD >>>TDD >>>>Primary CCPCH Tx Power Frequency info Maximum allowed UL TX power
Need OP
MP MP MP
MP MP
MP MP OP MP
MP MP MP MP
MP MP MP
II. Example
None
6-34
6.6 Relocation
6.6.1 Overview
The RNC relocation procedure is a procedure in which the SRNC of the UE changes from one RNC to another. According to whether the connection between UE and DRNC is set up during the relocation procedure, the procedure is divided into two kinds i.e., UE NOT INVOLVED relocation and UE INVOLVED relocation. According to the triggering cause, the relocation procedure can also be divided into the following four kinds: Static relocation: A relocation procedure occurring after a radio link is added to the DRNC. The UE has set up a radio link in the DRNC and established a connection to the DRNC before the static relocation procedure; therefore, this relocation is a kind of UE NOT INVOLVED relocation. Relocation with hard handover: A relocation procedure occurring with inter-RNC hard handover. The UE removes the connection with the SRNC and establishes a connection to the DRNC during the relocation with hard handover; therefore, this relocation is a kind of UE INVOLVED relocation. Relocation with forward handover: A relocation procedure occurring when the UE with RRC connection to the SRNC enters into a DRNC cell and initiates a forward handover (cell update or URA update) procedure. The UE has entered into the DRNC and sent a CELL UPDATE or URA UPDATE message before the relocation with forward handover; therefore, this relocation is a kind of UE NOT INVOLVED relocation. Inter-RAT handover: The UE removes the connection with the SRNC and establishes a connection to the GSM system during the inter-RAT handover procedure; therefore, inter-RAT handover is a kind of UE INVOLVED relocation. This section describes the former three kinds of relocation procedures. Refer to 6.5 Inter-RAT Handover for the details about the inter-RAT handover procedure.
6-35
CN SRNC DRNC
Orig. SRNC
SRNC
NodeB
CELL CELL
NodeB
CELL CELL
NodeB
CELL CELL
NodeB
CELL CELL
UE
UE
Note: If the UE has connections to two CN domains in the WCDMA system before the relocation procedure, the two CN domains must be relocated together.
6-36
UE
SRNC
DRNC
1. RELOCATION REQUIRED
MSC
SGSN
RANAP 2. RELOCATION REQUIRED RANAP RANAP 3. RELOCATION REQUEST RANAP 4. RELOCATION REQUEST RANAP 5.ALCAP SETUP 6. RELOCATION REQUEST ACKNOWLEDGE RANAP RANAP 8. RELOCATION COMMAND RANAP 9. RELOCATION COMMAND RANAP 10. RELOCATION COMMIT RNSAP RNSAP 11. RELOCATION DETECT RANAP 12. RELOCATION DETECT RANAP 13.UTRAN MOBILITY INFORMATION RRC 14.UTRAN MOBILITY INFORMATION CONFIRM RRC RRC 15. RELOCATION COMPLETE RANAP 16. RELOCATION COMPLETE RANAP 17. IU RELEASE COMMAND RANAP 18. IU RELEASE COMMAND RANAP 19.ALCAP 20. IU RELEASE COMPLETE RANAP 21. IU RELEASE COMPLETE RANAP RANAP release RANAP RANAP RRC RANAP RANAP 7. RELOCATION REQUEST ACKNOWLEDGE RANAP RANAP
RANAP
RANAP
RANAP
RANAP
RANAP
RANAP RANAP
RANAP
Figure 6-16 Static relocation procedure Each step is explained in the following list: 1) 2) 3) 4) 5) 6) 7) The SRNC sends a RELOCATION REQUIRED message to the SGSN (CN in PS domain). The SRNC sends a RELOCATION REQUIRED message to the MSC (CN in CS domain). The SGSN sends a RELOCATION REQUEST message to the DRNC, requesting the DRNC to make resource preparation for the relocation. The MSC sends a RELOCATION REQUEST message to the DRNC, requesting the DRNC to make resource preparation for the relocation. The DRNC initiates an Iu interface user plane bearer setup procedure using ALCAP. The DRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the SGSN, informing it that the resource preparation is ready. The DRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the MSC, informing it that the resource preparation is ready.
6-37
8) 9)
The SGSN sends a RELOCATION COMMAND message to the SRNC, informing it that the relocation may start. The MSC sends a RELOCATION COMMAND message to the SRNC, informing it that the relocation may start.
10) The SRNC sends a RELOCATION COMMIT message to the DRNC on the Iur interface. If an RAB supporting lossless relocation exists, the message shall contain the PDCP and GTP-U sequence numbers required for context transfer. Then the SRNC starts context transfer. After receiving the RELOCATION COMMIT message, the DRNC becomes the SRNC. 11) The DRNC sends a RELOCATION DETECT message to the SGSN, informing the SGSN that it detects the relocation triggering. 12) The DRNC sends a RELOCATION DETECT message to the MSC, informing the MSC that it detects the relocation triggering. 13) The DRNC sends a UTRAN MOBILITY INFORMATION message to the UE. The message shall contain the new U-RNTI and so on. 14) The UE returns a UTRAN MOBILITY INFORMATION CONFIRM message to the DRNC. 15) The DRNC sends a RELOCATION COMPLETE message to the SGSN, informing it that the relocation ends successfully. 16) The DRNC sends a RELOCATION COMPLETE message to the MSC, informing it that the relocation ends successfully. 17) The SGSN sends an IU RELEASE COMMAND message to the original SRNC, requesting it to release the Iu connection in the PS domain. 18) The MSC sends an IU RELEASE COMMAND message to the original SRNC, requesting it to release the Iu connection in the CS domain. 19) The original SRNC initiates an Iu interface user plane bearer release procedure using ALCAP. 20) After successful release, the SRNC returns an IU RELEASE COMPLETE message to the MSC. 21) The SRNC returns an IU RELEASE COMPLETE message to the SGSN. The static relocation procedure ends.
Note: When two Iu connections are handed over, the relocation messages for the CS and PS domains are not transmitted in the precedence order. Take the RELOCATION REQUIRED message for example. The SRNC may either first send the RELOCATION REQUIRED message to the MSC or first send the RELOCATION REQUIRED message to the SGSN. The same applies below.
6-38
MSC
SGSN
RANAP
RRC RRC
RRC 14. RELOCATION COMPLETE RANAP 15. RELOCATION COMPLETE RANAP RANAP RANAP RANAP
16. IU RELEASE COMMAND RANAP 17. IU RELEASE COMMAND RANAP 18.ALCAP release 19. IU RELEASE COMPLETE RANAP 20. IU RELEASE COMPLETE RANAP RANAP RANAP RANAP
Figure 6-17 Relocation procedure with hard handover Each step is explained in the following list: 1) 2) 3) 4) 5) The SRNC sends a RELOCATION REQUIRED message to the SGSN. The SRNC sends a RELOCATION REQUIRED message to the MSC. The SGSN sends a RELOCATION REQUEST message to the DRNC, requesting the DRNC to make resource preparation for the relocation. The MSC sends a RELOCATION REQUEST message to the DRNC, requesting the DRNC to make resource preparation for the relocation. The DRNC initiates an Iu interface user plane bearer setup procedure using ALCAP.
6-39
6)
The DRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the SGSN, informing it that the resource preparation is ready. The message shall contain the reconfiguration information, indicating which of the radio bearer setup, radio bearer release, radio bearer reconfiguration, transport channel reconfiguration and physical channel reconfiguration procedures the SRNC shall use to perform the relocation.
7)
The DRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the MSC, informing it that the resource preparation is ready. The message shall contain the reconfiguration information, indicating which of the radio bearer setup, radio bearer release, radio bearer reconfiguration, transport channel reconfiguration and physical channel reconfiguration procedures the SRNC shall use to perform the relocation.
8) 9)
The SGSN sends a RELOCATION COMMAND message to the SRNC, informing it that the relocation may start. The MSC sends a RELOCATION COMMAND message to the SRNC, informing it that the relocation may start.
10) Optional. If an RAB supporting lossless relocation exists, the SRNC shall send a FORWARD SRNS CONTEXT message to the SGSN, requesting the SGSN to send the PDCP and GTP-U sequence numbers required for context transfer to the target RNC. Then the system goes to step 11). Otherwise, the system skips to step 12). 11) Optional. If it receives a FORWARD SRNS CONTEXT message from the SRNC, the SGSN shall forward the message to the target RNC. The message shall contain the PDCP and GTP-U sequence numbers required for context transfer. 12) The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, informing it of the new physical channel parameters. The specific message type sent at this step is determined by the target RNC during resource preparation and the SRNC is informed of that message type through steps 6), 7), 8) and 9). 13) After successfully accessing the target RNC, the UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the target RNC. The handover procedure succeeds and the target RNC becomes the new SRNC of the UE. 14) The target RNC sends a RELOCATION COMPLETE message to the SGSN, informing it that the relocation ends successfully. 15) The target RNC sends a RELOCATION COMPLETE message to the MSC, informing it that the relocation ends successfully. 16) The SGSN sends an IU RELEASE COMMAND message to the original SRNC, requesting it to release the Iu connection in the PS domain. 17) The MSC sends an IU RELEASE COMMAND message to the original SRNC, requesting it to release the Iu connection in the CS domain.
6-40
18) The original SRNC initiates an Iu interface (including Iu-CS interface and Iu-PS interface) user plane bearer release procedure using ALCAP. 19) The original SRNC returns an IU RELEASE COMPLETE message to the SGSN, indicating that the IU release completes. 20) The original SRNC returns an IU RELEASE COMPLETE message to the MSC, indicating that the IU release completes.
DRNC
SGSN
Figure 6-18 Relocation procedure with cell update Each step is explained in the following list: 1) 2) The UE sends a CELL UPDATE message to the DRNC. The message shall contain the S-RNTI, SRNC ID and so on. The DRNC gets the SRNC ID of the UE from the URNTI information element in the CELL UPDATE message. Then the DRNC sends an UPLINK SIGNALING TRANSFER INDICATION message to the SRNC, informing it that the UE requests for cell update. 3) The SRNC sends a RELOCATION REQUIRED message to the SGSN.
6-41
4) 5) 6) 7)
The SGSN sends a RELOCATION REQUEST message to the DRNC, requesting the DRNC to make resource preparation for the relocation. The DRNC returns a RELOCATION REQUEST ACKNOWLEDGE message to the SGSN, informing it that the resource preparation is ready. The SGSN sends a RELOCATION COMMAND message to the SRNC, informing it that the relocation may start. The SRNC sends a RELOCATION COMMIT message to the DRNC on the Iur interface. If an RAB supporting lossless relocation exists, the message shall contain the PDCP and GTP-U sequence numbers required for data transfer. Then the SRNC starts data transfer.
8) 9)
The DRNC sends a RELOCATION DETECT message to the SGSN, informing the SGSN that it detects the relocation triggering. The DRNC sends a CELL UPDATE CONFIRM message to the UE. The message may contain the transport channel information element, physical channel information element, radio bearer information element, U-RNTI and so on.
10) The UE sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the DRNC. 11) The DRNC sends a RELOCATION COMPLETE message to the SGSN, informing it that the relocation ends successfully. The DRNC becomes the SRNC. 12) The SGSN sends an IU RELEASE COMMAND message to the original SRNC, requesting it to release the Iu connection in the PS domain. 13) After successfully releasing the Iu connection in the PS domain, the original SRNC returns an IU RELEASE COMPLETE message to the SGSN, indicating that the Iu connection release in the PS domain completes. The relocation procedure with cell update ends.
6-42
IE/Group Name Source RNC To Target RNC Transparent Container Old BSS To New BSS Information
Presence C ifUMTStarget
C ifGSMtarget
6-43
II. Example
6-44
6-45
II. Example
6-46
Presence
ifRecdFromRelocTarget CifRecdFromRelocTarget
RABs To Be Released List >RABs To Be Released Item IEs >>RAB ID RABs Subject To Data Forwarding List >RABs Subject To Data Forwarding Item IEs >>RAB ID >>Transport Layer Address >>Iu Transport Association Criticality Diagnostics
M C - ifPS
M M M O
6-47
II. Example
6-48
6-49
II. Example
6-50
6-51
II. Example
6-52
Synchronized radio link reconfiguration Unsynchronized radio link reconfiguration This section describes only the RAB modification procedure in the case of synchronized radio link reconfiguration. Figure 7-1 illustrates the DCH-DCH RAB modification procedure in the case of synchronized radio link reconfiguration.
UE NodeB Serving RNS Serving RNC
RANAP 1. RAB ASSIGNMENT REQUEST [Modify]
CN
RANAP
2. Select L1, L2 and Data Iu Transport Bearer parameters e.g. for Radio Bearer reconfiguration.)
3. ALCAP Iu Data Transport Bearer Modify 4.RADIO LINK RECONFIGURATION PREPARE NBAP 5.RADIO LINK RECONFIGURATION READY NBAP NBAP
NBAP
ALCAP
RRC
RRC NBAP
NBAP
Actualizing Radio Bearer modification (e.g. Apply new transport format set) 8 .DCCH: RADIO BEARER RECONFIGURATION COMPLETE
RRC
RANAP
Figure 7-1 RAB modification procedure (DCH-DCH, synchronized) Each step is explained in the following list: 1) The CN sends a RAB ASSIGNMENT REQUEST (modify) message to initiate an RAB modification procedure. The message shall indicate the RAB ID, modified RAB information, user plane information, transport network layer information, etc. 2) 3) 4) 5) The SRNC selects the corresponding parameters for the corresponding reconfiguration procedure. The SRNC modifies the channel characteristics of the Iu interface data transport bearer using ALCAP if the Iu interface user plane is borne on an AAL2 link. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB on the Iub interface to initiate a radio link reconfiguration procedure. The NodeB returns a RADIO LINK RECONFIGURATION READY message to the SRNC on the Iub interface.
7-2
6)
After the Iu interface transport control plane is successfully modified and the NodeB successfully modifies the radio link, the SRNC sends a RADIO BEARER RECONFIGURATION message to the UE on the DCCH. The message shall contain the RAB information, RAB ID, etc.
7)
The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. The message shall contain the CFN information element. When the next CFN indicated by the information element is received, the NodeB shall use the prepared new configuration.
8) 9)
The UE returns a RADIO BEARER SETUP COMPLETE message to the SRNC. The SRNC sends a RANAP message RADIO BEARER ASSIGNMENT RESPONSE to the CN, confirming that the RAB modification procedure succeeds. The RAB modification procedure ends.
7-3
Information Element/Group name URA identity RB information elements RAB information to reconfigure list >RAB information to reconfigure RB information to reconfigure list >RB information to reconfigure RB information to be affected list >RB information to be affected TrCH Information Elements Uplink transport channels UL Transport channel information common for all transport channels Deleted TrCH information list
Need OP
OP MP MP MP OP MP
OP
OP
>Deleted UL TrCH information Added or Reconfigured TrCH information list >Added or Reconfigured UL TrCH information CHOICE mode >FDD >>CPCH set ID >>Added or Reconfigured TrCH information for DRAC list >>>DRAC static information >TDD Downlink transport channels DL Transport channel information common for all
MP OP
MP OP
OP OP
MP
OP
7-4
Need
OP
>Deleted DL TrCH information Added or Reconfigured TrCH information list >Added or Reconfigured DL TrCH information PhyCH information elements Frequency info Uplink radio resources Maximum allowed UL TX power CHOICE channel requirement >Uplink DPCH info >CPCH SET Info Downlink radio resources CHOICE mode >FDD >>Downlink PDSCH information >TDD Downlink information common for all radio links Downlink information per radio link list
MP OP
MP
MD
MD OP
MP
OP
OP MP
MP
7-5
II. Example
measurement, downlink code transmit power, etc. during the service process. When the rate of service origin or quality of air interface changes, the RNC adjusts the channel bandwidth to satisfy the new requirement of the service origin. This procedure is called dynamic channel reconfiguration. The RNC informs the UE of the new radio link parameters through the procedure of radio bearer reconfiguration.
7.3.2 RB Reconfiguration
The radio bearer reconfiguration procedure is used to reconfigure a radio bearer. This section describes the dynamic channel reconfiguration procedure, as illustrated in Figure 7-2, with radio bearer reconfiguration as an example. The RRC connection of the UE is in CELL_FACH state before the radio bearer reconfiguration and in CELL_DCH state after the radio bearer reconfiguration.
UE NodeB
1. RADIO LINK SETUP REQUEST NBAP 2. RADIO LINK SETUP RESPONSE NBAP NBAP NBAP
CRNC
3. ALCAP
RRC
4.RADIO BEARER RECONFIGURATION RRC 5. RADIO BEARER RECONFIGURATION COMPLETE 6. RADIO LINK RESTORE NBAP NBAP
RRC
RRC
Figure 7-2 Radio bearer reconfiguration procedure (CCH-DCH) Each step is explained in the following list: 1) 2) 3) 4) The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB where the target cell belongs to initiate a radio link setup procedure. The NodeB where the target cell belongs returns a RADIO LINK SETUP RESPONSE message to the CRNC. The CRNC sets up an Iub interface transport bearer between the CRNC and the NodeB using ALCAP and implements synchronization using FP. The CRNC sends a RADIO BEARER RECONFIGURATION message to the UE on the downlink DCCH. The message shall contain the target cell information and the target RRC connection status of the UE. 5) After successfully handed over to the target cell, the UE sends a RADIO BEARER RECONFIGURATION COMPLETE message to the CRNC on the DCCH.
7-7
6)
After detecting the uplink synchronization of the new radio link, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC. The message shall contain the information about the radio link detected as synchronized. The radio bearer reconfiguration procedure ends.
7-8
A-1
Appendix B
Call Example
To successfully make a call, the UE initiates the RRC connection setup procedure to set up a signaling connection to the RNC. For details, see Section 5.3 RRC Connection Setup. 2) Signaling connection setup
The RNC sets up a signaling connection to the CN. For details, see Section 5.4 Direct Transfer Messages. 3) RAB setup
The CN responds to the service request from the UE and requests the RNC to set up the corresponding RAB. After successful RAB setup, the called party answers the call and the call is set up. For details, see Section 5.6 RAB Setup. 4) Signaling connection release
Upon completion of the call, the signaling connection between the RNC and the CN shall be released. For details, see Section 5.7 Call Release. 5) RAB release
The RAB shall be released through the RAB release procedure. For details, see Section 5.7 Call Release. 6) RRC connection release
The RRC connection between the UE and the RNC shall be released through the RRC connection release procedure if the RRC bears no other RABs. For details, see Section 5.7 Call Release.
B-1
Appendix B
SRNC
RRC NBAP
Call Example
NodeB SRNS
CCCH : RRC CONNECTION REQUEST RADIO LINK SETUP REQUEST NBAP Start RX RADIO LINK SETUP RESPONSE NBAP ALCAP
CN
NBAP
Start TX CCCH : RRC CONNECTION SETUP RRC RRC RRC DCCH : RRC CONNECTION SETUP COMPLETE DCCH :INITAL DIRECT TRANSFER RRC RRC RRC RANAP RANAP RRC RRC RRC DCCH DOWNLINK DIRECT TRANSFER DCCH : UPLINK DIRECT TRANSFER RRC RRC RANAP RANAP RRC RRC DOWNLINK DIRECT TRANSFER DCCH DCCH UPLINK DIRECT TRANSFER RRC RRC RAB ASSIGNMENT REQUEST RANAP ALCAP RADIO LINK RECONFIGURATION PREPARE NBAP NBAP RADIO LINK RECONFIGURATION READY NBAP NBAP (Establishment) RANAP DIRECT TRANSFER (Setup) DIRECT TRANSFER (Call Proceeding) RANAP RANAP INNTIAL UE MESSAGE (CM Service Request) DIRECT TRANSFER (CM Service Accept) RANAP RANAP
B-2
Appendix B
Call Example
UE
NodeB SRNS
ALCAP
SRNC
Iub Data Transport Bearer Setup
CN
RRC
Apply new transport format set RRC DCCH : RADIO BEARER SETUP COMPLETE RRC RANAP RAB ASSIGNMENT RESPONSE RANAP (Establish) DIRECT TRANSFER (Alerting) DIRECT TRANSFER (Connect) RANAP
RANAP RRC DCCH DOWNLINK DIRECT TRANSFER RRC RANAP RRC RRC DCCHDOWNLINK DIRECT TRANSFER DCCH: UPLINK DIRECT TRANSFER RRC RRC RANAP RRC DCCH: UPLINK DIRECT TRANSFER RRC RANAP RANAP RRC RRC DCCH: DOWNLINK DIRECT TRANSFER DCCH: UPLINK DIRECT TRANSFER RRC RRC RANAP RANAP
RANAP
DIRECT TRANSFER (Connect Acknowledge) DIRECT TRANSFER (Disconnect) DIRECT TRANSFER ( Release)
RANAP
RANAP RANAP
RANAP RANAP
RANAP RRC RRC DCCH : RRC CONNECTION RELEASE DCCH : RRC CONNECTION RELEASE NBAP COMPLETE RRC RRC NBAP
RANAP
RADIO LINK DELETION COMPLETE NBAP NBAP ALCAP Iub Data Transport Bearer Release
B-3
Appendix B
Call Example
The network pages the UE. For details, see Section 5.2 Paging. 2) RRC connection setup
The UE answers the call and initiates an RRC connection setup procedure to set up a connection to the RNC. For details, see Section 5.3 RRC Connection Setup. 3) Signaling connection setup and direct transfer
The RNC sets up a signaling connection to the CN. For details, see Section 5.4 Direct Transfer Messages. 4) RAB setup
The CN requests the RNC to set up the corresponding RAB. After successful RAB setup, the UE exchanges signaling messages with the CN and answers the call to enter into a conversation. For details, see Section 5.6 RAB Setup. 5) Signaling connection release
Upon completion of the call, the signaling connection between the RNC and the CN shall be released. For details, see Section 5.7 Call release. 6) RAB release
The RAB shall be released through the RAB release procedure. For details, see Section 5.7 Call release. 7) RRC release
The RRC connection between the UE and the RNC shall be released through the RRC connection release procedure if the RRC bears no other RABs. For details, see Section 5.7 Call release. Figure Figure B-2 illustrates a specific terminated procedure.
B-4
Appendix B
Call Example
UE
NodeB SRNS
SRNC
PAGING
CN
RANAP
RANAP PAGING TYPE 1 RRC RRC CCCH: RRC CONNECTION REQUEST RRC RRC RADIO LINK SETUP REQUEST NBAP NBAP
Start TX RRC RRC RRC CCCH : RRC CONNECTION SETUP DCCH : RRC CONNECTION SETUP COMPLETE DCCH : INITAL DIRECT TRANSFER RRC RRC RRC INITIAL UE MESSAGE RANAP (Paging Response) RANAP RRC RRC RRC DCCH: DOWNLINK DIRECT TRANSFER : DCCH : UPLINK DIRECT TRANSFER RRC RRC RANAP DIRECT TRANSFER (Call Confirm) RANAP DIRECT TRANSFER (Set Up) RANAP RANAP
RAB ASSIGNRMENT REQUEST RANAP RANAP (Establishment) ALCAP Iu Data Transport Bearer Setup
RAKIO LINK RECONFIGURATION NBAP NBAP PREPARE RADIO LINK RECONFIGURATION NBAP READY NBAP
B-5
Appendix B
Call Example
UE
NodeB SRNS
ALCAP
SRNC
Iub Data Transport Bearer Setup RRC NBAP
CN
RRC
DCCH : RADIO BEARER SETUP RADIO LINK RECONFIGURATION NBAP COMMIT Apply new transport format set DCCH : RADIO BEARER SETUP COMPLETE
RRC
RRC RAB ASSIGNMENT RESPONSE RANAP (Establishment) RRC RANAP DIRECT TRANSFER ( Alerting) DIRECT TRANSFER (Connect) DIRECT TRANSFER (Connect Acknowledge) RRC RANAP DIRECT TRANSFER (Disconnect) RANAP RANAP RANAP
RRC
RRC
RRC
RRC RRC
RRC RRC RANAP RANAP DIRECT TRANSFER (Release) DIRECT TRANSFER (ReleaseComplete) RANAP RANAP
RRC
ALCAP
RANAP RRC RRC RRC CONNECTION RELEASE DCCH RRC CONNECTION RELEASE COMPLETE DCCH NBAP RADIO LINK DELETION RRC RRC NBAP
RANAP
RADIO LINK DELETION COMPLETE NBAP NBAP ALCAP Iub Data Transport Bearer Release
B-6
Appendix C
C-1
Appendix C
CN CPCH CPCS CPICH CRC CRNC C-RNTI CS CSICH D DCCH DCH DPC DPCCH DPCH DPDCH DRNC DRNS DRX DSCH F FACH FDD FER G GPRS GSM GTP-U
Core Network Common Packet Channel Common Part Convergence Sublayer Common Pilot Channel Cyclic Redundancy Check Controlling RNC Cell Radio Network Temporary Identifier Circuit-Switched CPCH status indication channel
Dedicated Control CHannel Dedicated CHannel Destination (Signaling)Point Code Dedicated Physical Control Channel Dedicated Physical Channel Dedicated Physical Data Channel Drift RNC Drift RNS Discontinuous Reception Downlink Shared Channel
General Packet Radio Service Global System for Mobile Communications User plane part of GPRS tunneling protocol
C-2
Appendix C
I IE IMSI IP ISUP ITU-T Information Element International Mobile Station Identity Internet Protocol Integrated Services Digital Network User Part/ISDN User Part International Telecommunication Union - Telecommunication Standardization Sector IU IUR L LAI M MAC MIB MM MS MSC MSU MTP MTP3 N NAS NBAP NNI NodeB O OAM OPC Operation Administration and Maintenance Originating Point Code Non-Access Stratum NodeB Application Part Network Node Interface (Network-to-Network) WCDMA Base Station Medium Access Control Master Information Block Mobility Management Mobile Station Mobile Switching Center Message Signalling Unit Message Transfer Part Message Transfer Part Layer 3 Location Area Identity Iu Interface Iur Interface
C-3
Appendix C
P PCCH PCCPCH PCH PCP PCPCH PCPICH PDCP PDP PDSCH PICH PLMN PRACH PS PSCH PSTN Q QoS R RAB RACH RANAP RB RFN RNC RNS RNSAP RNTI Radio Access Bearer Random Access CHannel Radio Access Network Application Part Radio Bearer RNC Frame Number counter Radio Network Controller Radio Network Subsystem Radio Network Subsystem Application Part Radio Network Temporary Identity Quality of Service Paging Channel (logical Channel) Primary Common Control Physical Channel Paging Channel Power Control Preamble Physical Common Packet Channel Primary Common Pilot Channel Packet Data Convergence Protocol Packet Data Protocol Physical Downlink Shared Channel Paging Indicator Channel Public Land Mobile Network Packet Random Access Channel Packet Switched Physical shared channel Public Switched Telephone Network
C-4
Appendix C
RRC RTWP S SAAL SABP SAR SCCP SCCPCH SCH SCPICH SDU SGSN SI SIB SIF SIO SIR SLS SRB SRNC SRNS SS7 SSCF SSCH SSCOP SSCS SSN STC
Signaling ATM Adaptation Layer Service Area Broadcast Protocol Segmentation And Reassembly Signaling Connection and Control Part Secondary Common Control Physical Channel Synchronization CHannel Secondary Common Pilot Channel Service Data Unit Serving GPRS Support Node Service Indicator System Information Block Signaling Information Field Service Information Octet Signal-Interference Ratio Signaling Link Selection Signalling radio bearer Serving RNC Serving RNS Signaling System Number 7 Service Specific Coordination Function Secondary Synchronization CHannel Service Specific Connection Oriented Protocol Service Special Convergence Sublayer Sub-System Number Signaling Transport Converter
C-5
Appendix C
STTD T TB TBS TDD TFC TFCI TFI ToA ToAWE ToAWS TPC TTI U UE UMTS
Transport Block Transport Block Set Time Division Duplex Transport Format Combination Transmit Format Combined Indicator Transport Format Indicator Time of Arrival Time of Arrival Window Endpoint Time of Arrival Window Startpoint Transmit Power Control Transmission Time Interval
Logical User-Network Interface User Plane UTRAN Registration Area UTRAN Radio Network Temporary Identifier UMTS Terrestrial Radio Access Network Uu Interface
C-6
Index
Index
A
active set update message, 6-13 ALCAP, 2-26 audit response message, 3-12
D
DCH-DCH, 5-27 direct transfer message, 5-18 disconnection of signaling link, 2-20 DL timing adjustment, 1-13 DL transport channel synchronization, 1-12 downlink data transfer, 1-15 downlink direct transfer, 5-20 downlink direct transfer message, 5-23 downlink timing adjustment, 1-18 downlink transport channel sychronization, 1-17 dynamic channel reconfiguration, 7-6 dynamic resource control procedure analysis, 7-1
B
blocking of AAL2 path, 2-28 BMC, 1-6
C
call example, B-1 call release, 5-43 call setup and release procedure analysis, 5-1 CCH-CCH, 5-32 CCH-DCH, 5-30 cell deletion procedure, 3-7 cell reconfiguration procedure, 3-6 cell related procedure analysis, 3-1 cell setup procedure, 3-3 cell setup request message, 3-16 cell update, 6-1 cell update message, 6-4 changback, 2-19 changeover, 2-19 class 1 elementary procedure, 1-20, 1-27 class 2 elementary procedure, 1-21, 1-27 class 3 elementary procedure, 1-28 combined hard handover, 6-19 combined release, 5-47 common measurement initiation procedure, 3-5 common transport Channel setup procedure, 3-4 common transport channel setup request, 3-20 compressed mode, 6-16 connection request message, 2-34 CPCS, 2-8 CS domain service release, 5-43
E
error event, 1-32 establish request message, 2-30 establishment of AAL2 connection, 2-27 example of cell setup procedure, 3-28
F
FACH data transfer, 1-11 forward handover, 6-1 frame quality classification, 1-33 function of Iu UP, 1-28 function of NBAP, 1-8 function of RANAP, 1-25 function of RNSAP, 1-19 function of SABP, 1-33 function of system information, 4-2
G
GSM/GPRS->WCDMA cell reselection, 6-29 GSM->WCDMA inter-RAT handover, 6-27 GTP-U, 1-33
i-1
Index cell update, 6-4 common transport channel setup request, 3-20 connection request, 2-34 downlink direct transfer, 5-23 establish request, 2-30 handover from UTRAN command, 6-32 handover to UTRAN command, 6-33 initial direct transfer, 5-21 MTP3-B management, 2-25 MTP3-B test, 2-24 MTP3-B upper user, 2-23 paging type 1, 5-3 paging type 2, 5-4 physical channel reconfiguration, 6-22 RAB assignment request, 5-33 RAB assignment response, 5-36 radio bearer reconfiguration, 7-3 radio bearer setup, 5-38 radio link setup request, 5-14 relocation command, 6-46 relocation request, 6-45 relocation required, 6-42 resource status indication, 3-7 RRC connection reject, 5-13 RRC connection request, 5-8 RRC connection setup, 5-10 SSCOP, 2-10 system information, 4-4 system information update request, 3-25 uplink direct transfer, 5-22 uplink signaling transfer indication, 6-51 URA update, 6-6 UTRAN mobility information, 6-49 message discrimination, 2-12 message distribution, 2-13 message routing, 2-13 message structure, 2-14, 2-29, 2-33 mobility management procedure analysis, 6-1 modification by a timer, 4-7 modification by a value tag, 4-7 MTP3-B, 2-11 MTP3-B management message, 2-25
H
handover from UTRAN command message, 6-32 handover to UTRAN command message, 6-33 hard handover, 6-15 heading code, 2-17
I
initial direct transfer, 5-18 initial direct transfer message, 5-21 initialisation procedure, 1-30 Inter-RAT handover, 6-24 Iu interface, 1-22 Iu interface specification, 1-25 Iu protocol architecture, 1-22 Iu rate control, 1-31 Iu signaling connection release, 5-44 Iub FP common transport channel data transfer, 1-10 dedicated transport channel data transfer, 1-14 Iub interface, 1-6 Iub interface specification, 1-7 Iub interface user plane setup, 3-4 Iub protocol structure, 1-6 Iur FP transport channel data transfer, 1-22 Iur interface, 1-18 Iur interface hard handover, 6-17 Iur interface specification, 1-19 Iur protocol structure, 1-18
L
L1 function, 1-6 L2 function, 1-5 LM, 2-9
M
MAC, 1-5 management prohibit, 2-19 message active set update, 6-13 audit response, 3-12 cell setup request, 3-16 i-2
Protocols and Signalling Analysis HUAWEI UMTS Radio Access Network MTP3-B test message, 2-24 MTP3-B upper user message, 2-23 soft handover, 6-8
Index
system information broadcast and update, 4-3 system information modification, 4-6 UE capability information, 5-24 procedure Involved in cell setup, 3-1 Protocol stack of Iub interface, 1-7 protocol stack of Iu-BC interface, 1-24 protocol stack of Iu-CS interface, 1-23 protocol stack of Iu-PS interface, 1-23 protocol stack of Iur interface, 1-19 protocol structure of MTP3-B, 2-12 PS domain service release, 5-43
N
NBAP common procedure, 1-9 NBAP dedicated procedure, 1-9 NBAP procedure, 1-8 Node synchronization, 1-12, 1-16 NodeB tracing tool, A-1
O
originating call procedure, B-1 outer loop power control transfer, 1-15
R
RAB assignment request message, 5-33 RAB assignment response message, 5-36 RAB modification, 7-1 RAB modification (DCH-DCH), 7-1 RAB release, 5-45 RAB setup, 5-26 RACH data transfer, 1-10 radio bearer reconfiguration message, 7-3 radio bearer setup message, 5-38 radio interface parameter update, 1-16 radio link addition, 6-9 radio link addition and deletion, 6-12 radio link deletion, 6-10 radio link setup request message, 5-14 RANAP procedure, 1-26 release of AAL2 connection, 2-27 relocation, 6-35 relocation command message, 6-46 relocation request message, 6-45 relocation required message, 6-42 relocation with forward handover, 6-41 relocation with hard handover, 6-39 reset, 2-28 resource audit procedure, 3-2 resource status indication message, 3-7 resource status indication procedure, 3-1 RLC, 1-5 RNC tracing tool, A-1
P
paging, 5-1 UE in CELL_DCH state, 5-3 UE in CELL_FACH state, 5-3 UE in idle mode, 5-2 UE in PCH state, 5-2 paging type 1 message, 5-3 paging type 2 message, 5-4 PCH data transfer, 1-11 PDCP, 1-5 physical channel reconfiguration message, 6-22 procedure ALCAP, 2-26 call release, 5-43 cell setup, 3-1 direct transfer message, 5-18 dynamic channel reconfiguration, 7-6 forward handover, 6-1 hard handover, 6-15 inter-RAT handover, 6-24 MTP3-B, 2-11 paging, 5-1 RAB modification, 7-1 RAB setup, 5-26 relocation, 6-35 RRC connection setup, 5-5 SAAL, 2-1 SCCP, 2-31
i-3
Protocols and Signalling Analysis HUAWEI UMTS Radio Access Network RNSAP procedure, 1-20 RRC connection reject, 5-7 RRC connection reject message, 5-13 RRC connection release, 5-48 on CCH, 5-50 on DCH, 5-49 RRC connection request message, 5-8 RRC connection setup, 5-5 on common channel, 5-7 on dedicated channel, 5-6 RRC connection setup message, 5-10 RRC function, 1-4
Index system information broadcast and update, 4-3 system information message, 4-4 system information modification, 4-6 system information monitoring mechanism, 4-2 system information procedure analysis, 4-1 system information structure, 4-1 system information update, 3-5, 4-3 system information update request message, 3-25
T
terminated call procedure, B-4 time alignment procedure, 1-31 ToA, 1-13 ToAWE, 1-13 ToAWS, 1-13 tool NodeB message tracing, A-1 RNC message tracing, A-1 transport network layer procedure analysis, 2-1
S
SAAL, 2-1 SAAL Structure, 2-1 SAR, 2-8 SCCP, 2-31 service indicator (SI), 2-15 service information octet(SIO), 2-14 signaling connection release, 5-44 signaling connection release request, 5-44 signaling information field (SIF), 2-15 signaling link connecting, 2-21 signaling link fault, 2-20 signaling link management, 2-14 signaling link restoration, 2-20 signaling network management message, 2-16 signaling route management, 2-14 signaling traffic management, 2-13 soft handover, 6-8 SSCF, 2-7 SSCOP, 2-2 SSCOP connection release, 2-5 SSCOP connection setup, 2-5 SSCOP data transmission, 2-6 SSCOP error recovery, 2-6 SSCOP message, 2-10 SSCOP operation state, 2-4 static relocation, 6-35 synchronized radio link reconfiguration, 5-27 system information broadcast, 4-3
U
UE capability enquiry, 5-25 UE capability information, 5-24 UE capability information update, 5-25 unblocking of AAL2 path, 2-28 unsynchronized radio link reconfiguration, 5-29 uplink data transfer, 1-14 uplink direct transfer, 5-19 uplink direct transfer message, 5-22 uplink signaling transfer indication message, 6-51 URA update, 6-3 URA update message, 6-6 user data transfer, 1-30 UTRAN interface function, 1-1 UTRAN interface protocol, 1-1 UTRAN interface protocol and function, 1-1 UTRAN interfaces, 1-1 UTRAN mobility information message, 6-49 Uu interface, 1-2 Uu protocol structure, 1-2
i-4
i.
i-5