Signaling Flow of Advanced WCDMA Radio Interfaces

Signaling Flow of Advanced WCDMA Radio Interfaces
ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: doc@zte.com.cn
Contents
Chapter 1 .........................................................................1 Overview .........................................................................1
Basic Signaling Flow ......................................................... 1
Flow Classification .................................................................. 1 Description to Basic Signaling Flow ........................................... 2
Basic Concept .................................................................. 4

UE Protocol State ................................................................... 4 UTRAN State Transition in Connection Mode .............................. 7
Chapter 2 .......................................................................13 Network Selection Flow ................................................13

UE Under Idle Mode ....................................................... 13
Overview ............................................................................. 13 PMMN Selection and Reselection............................................. 15
Cell Selection and Reselection ......................................... 15

Cell Selection ....................................................................... 15 Cell Reselection .................................................................... 17 Cell Selection Away form Connection Mode .............................. 17 Position Registraton .............................................................. 17
Chapter 3 .......................................................................19 Handover Flow in the System .......................................19

Handover Overview ........................................................ 19 Soft Handover ............................................................... 20
Between Cells in NodeB......................................................... 22 Between NodeBs in the Same RNC ......................................... 22 Between RNCs ..................................................................... 23
Hard Handover .............................................................. 24

Inter-Frequency Hard Handover under the Same RNC ............... 26 Inter-RNC Hard Handover under the same MSC ....................... 26
Inter-Systems Handover ................................................. 27

Handover Between CS Domain Systems ................................. 29 Handover Between PS Domain Systems.................................. 32
Forward Handover ......................................................... 37
Chapter 4 .......................................................................41 Call Service Flow ...........................................................41

Overview ...................................................................... 41 Paging Flow .................................................................. 42
Paging the UE in Idle Mode or PCH State ................................ 42 Paging the UE in CELL_DCH or CELL_FACH State ..................... 43 Examples of Paging Flow ...................................................... 44
RRC Connection Establishment Flow ................................. 44

RRC Connection Establishment on Special Channles ................. 45 Setting up RRC Connection on a Public Channel ....................... 46 RRC Connection Rejection ..................................................... 47
Direct Transfer Message Flow .......................................... 48

Initial Direct Transfer ........................................................... 48 Uplink Direct Transfer........................................................... 50 Downlink Direct Transfer ...................................................... 51
UE Capability Information Flow ........................................ 51

UE Capability Information Query ............................................ 52 UE Capability Information Update .......................................... 52
RAB Establishment Flow ................................................. 53

DCH-DCH ........................................................................... 54 CCH-DCH ............................................................................ 57 CCH-CCH ............................................................................ 59
Chapter 5 .......................................................................61 Service Release Flow.....................................................61

Overview ...................................................................... 61 Iu Signaling Connection Release Flow ............................... 62
Signaling Connection Release Request .................................... 62 Signaling Connection Release ................................................ 63
RAB Release Flow .......................................................... 63 Joint Release Flow of CS-Domain lu Signaling Connection and RAB ............................................................................. 65 RRC Connection Release Flow .......................................... 67
Overview ............................................................................. 67 Releasing an RRC Connection Established on a Special Channel.. 67 Releasing an RRC Connection Established on a Common Channel .......................................................................................... 68
Appendix A ....................................................................71 Basic Signaling Flow......................................................71

CS Registration and PS Attacted Flow ............................... 71
CS Registration .................................................................... 71 PS Domain Attaching ............................................................ 73
Call Flow ....................................................................... 75

Calling Flow of CS Domain ..................................................... 75 Called Flow of CS Domain ...................................................... 78 PDP Activation of PS Domain ................................................. 79 Call of PS Domain ................................................................. 81
Service Release Flow ...................................................... 84

Release of CS Domain ........................................................... 84 Flow of CS Domain Passive Release ........................................ 86 PDP Deactivation of PS Domain .............................................. 87 Detach of PS Domain ............................................................ 89
Appendix B ....................................................................91 Basic Call Code Flow......................................................91

CS Registration Code Flow .............................................. 91 Calling Code Flow in CS Domain ...................................... 92 CS Domain Taking Initiative to Release Code Flow ............. 93 CS Domain Called Code Flow ........................................... 94 CS Domain Passive Release Code Flow ............................. 95 PS Domain Attached Code Flow ....................................... 96 PS Domain Deattached Code Flow .................................... 97 PDP Activiated Code Flow in PS Domain ............................ 97 PDP Deactiviating Code Flow in PS Domain ....................... 98 Position Renewal Code Flow ............................................ 99 CS Called Concurrent Code Flow in PS Background............. 99
Chapter
Overview
Highlights

Overview of basic signaling flow Mobile protocol state and state transition
Basic Signaling Flow

Flow Classification
A variety of signaling flows exist in a WCDMA system. In terms of protocol stack, signaling flows can be access layer signaling flows or non-access layer signaling flows. In terms of network composition, signaling flows can be categorized as circuit-switched or packet-switched. Access layer and non-access layer signaling flows are actually so named from the perspective of protocol stack. In the protocol stack, the RRC layer, RANAP layer, and the protocol layers below them are access layers, while the MM, SM, CC, and SMS layers above them are known as non-access layers. Simply put, the flow at the access layer is the flow where the RNCs and NodeBs at the radio access layer need to take part in the processing. The flow at a non-access layer refers to a signaling flow where only UEs and CNs, but not RNCs or NodeBs, need to take part in the processing. The signaling at the access layer paves the way for the signaling interaction at a non-access layer. Through the signaling interaction at the access layer, a signaling path is established between the UE and CN so that the signaling flow at a non-access layer can be started. The flows at the access layer include PLMN selection, cell selection, and radio resource management flows. The radio resource management flows are the flows at the RRC layer, including the RRC connection setup flow, flow of the signaling setup between UEs and CNs, RAB setup flow, call release flow,
Confidential and Proprietary Information of ZTE CORPORATION
handover flow, and SRNS redirection flow. For the handover and SRNS redirection flows, the cross-RNC and cross-SGSN/MSC cases exist. In such cases, SGSN/MSC is also needed. Therefore, from the perspective of protocol stack, the flows at the access layer are all bottom layer flows, through which bottom layer bearer is established for the signaling flows at upper layers. The non-access flow layer flows mainly include the CS domain mobility management, the CS domain call control, the PS domain mobilility management, and the PS domain session management.
Description to Basic Signaling Flow

The following is the overview that briefly describes the basic signaling flow. At first, the whole business flow from poweron, to business, and then to poweroff can be viewed in the case that the user is not mobile, which is described as follows. 1. When a subscriber UE is powered on, the signaling interaction at the access layer is performed first. PLMN selection is then performed to select the network of a carrier, followed by cell selection to reside in an appropriate cell. After that, an RRC connection is established and the signaling connection on the Iu interface is set up. At this point, through the signaling flows at these access layers, a signaling channel is established between the UE and the CN in preparations for the signaling flows at non-access layers. 2. Then, the mobility management flows at non-access layers between UE and CN are started. The subscriber then starts attached flows, including small flows such as authentication, encryption, and location update. 3. After the flows such as authentication pass, the UE enters the service-related flows at non-access layers. Such flows include the call connection flows of the circuit domain and the session management flows of the packet domain. Through these flows, the service bearer links are established for the service. After that, the subscriber can start to make a call or access the Internet. 4. When the subscriber finishes using the service, the call connection flows of the circuit domain and the session management flows of the packet domain are also performed to tear down the service bearer links. 5. If the subscriber powers off his/her mobile phone, the mobility management flows at non-access layers are performed between the UE and CN to separate the circuit domain from the packet domain. 6. When the signaling interaction at non-access layers is complete, the system performs the signaling flows at the
Chapter 1 Overview
access layer to tear down the Iu signaling connection and RRC signaling connection previously established. At this point, the whole flow in which a subscriber powers on his/her mobile phone, uses the service, and powers off the mobile phone without moving is complete. This shows that the completion of the service process requires the cooperation between the signaling flows at the access layer and those at non-access layers. The flows at the access layer establish the signal bearer for the flows at non-access layers. The version below describes one service flow with which the user make the called service. 1. The subscriber UE is in standby mode. The subscriber UE is paged from the network side. 2. If no signaling connection exists between the UE and the CN, the signaling flows at the access layer are performed between the UE, the RNC, and the CN to establish an RRC connection and Iu interface signaling connection. 3. Then, the authentication and encryption flows of mobility management may be performed. 4. After that, service bearer links are established through the call connection flows of the circuit domain and session management flows of the packet domain so that the service can be performed. 5. When the service is finished, the related service bearer links are torn down. 6. Then, the signaling connections at the access layer, including the signaling connection on the Iu interface and the RRC connection, are released. The previously described two flows mainly describe in general how to make services in the case that the subscriber has no position change. This is only an overall and simple description while various detailed flows are described in the subsequent chapters and sections. As mobile communication has the mobile feature, flows related to a variety of hanlding mobilities are produced. For example, when the subscriber does not develop the service, the position is changed, so as to produce such flows of mobility management as position renewal; when the subscriber develops the service, the position changes so as to produce such flows as handover and SRNS repositioning.
Basic Concept
UE Protocol State
A UE has two basic operation modes: idle mode and connection mode. Upon being powered on, the UE stays in the idle mode while the mode is distinguished through such access level flags as IMSI, TMSI or P-TMSI. Because UTRAN does not save the UE information of the idle mode, the UTRAN can only page all UEs in one cell or all UEs at the same time. Only when a UE finishes the construction of the RRC connection can the UE changes its idle mode to the connection mode: CELL_FACH or CELL_DCH state. The UE connection mode, which is also called as the UE RRC state, reflects the UE connection level and which kind of transfer channel the UE can use. When the RRC connection is released, the UE changes its connection mode to the idle mode.
FIGURE 1 UE OPERATION MODE
When UE is in the connection mode, there are following four kinds of state: 1. CELL_DCH state The CELL_DCH state has the following features:
Chapter 1 Overview
A dedicated physical channel is assigned to the UE along the uplink and downlink; The cell to which the UE belongs can be obtained through the current active set of the UE; The UE can use the dedicated transport channel, uplink/downlink shard transport channel, or a combination of these transport channels. The UE enters the CELL_DCH state in the following two ways:
When the UE is in idle mode, the RRC connection is established on the dedicated channel, and therefore the UE enters the CELL_DCH state from idle mode; When in the CELL_FACH state, the UE uses the common transport channel and uses the dedicated transport channel after a channel switchover. The UE enters the CELL_DCH state from the CELL_FACH state. The CELL_FACH state has the following features:
2. CELL_FACH state No dedicated transfer channel is assigned to the UE he UE continuously monitors one downlink FACH channel A default uplink public channel or uplink shared transfer channel (such as RACH) is assigned to the UE The UE position in the cell level is known by UTRAN, which is the cell where the UE initiated the latest cell renewal. In the CELL_FACH sub state, the UE implements the following actions:

Monitor one FACH Monitor the BCH transfer channels and the decoding system information messages of the current service cell When the current cell turns to be another UTRA cell, one renewal process of the cell is initiated. Unless one new cell is selected, the allocated C-RNTI in the current cell is used as the UE flag of the public transfer channel. Transmit the uplink signaling and small data packet in the RACH In the CELL_RACH state, if the data service is not activated during a period of time, the UE will enter the CELL_PCH state so as to reduce the power comsumption. Furthermore, when the UE temporary gets rid of the CELL_PCH state and implements the cell renewal, after the renewal is finished, it will return the CELL_PCH if no requirements are necessary in the UE and the network side.
3. CELL_PCH state
The CELL_PCH state has the following features:

No dedicated channel is assigned for the UE. The UE uses the non-continuous reception (DRX) technology to monitor the information in the PCH transfer channel in some specified paging time. No uplinking actve UE positions can be known by the UTRAN in the cell level, which refers to the cell reported by the UE in the CELL_FACH state when the latest cell renewal is initiated. In the CELL_PCH activities: state, the UE makes the following
According to the DRX cycle monitor the paging time, and receive the paging information on the PCH. Monitor the BCH transfer channel of the current service cell to decode the system information When the cell changes, initiate the cell renewal process In such case, the DCCH logic channel cannot be used. If the network tries to initiate any activities, it needs to send one paging request on the PCCH logic channel of the cell where the UE is located. There are two ways for the UE to be converted to the CELL_FACH state: one way is to make paging through the UTRAN while another way
4. URA_PCH state The URA_PCH state has the following features:

No dedicated channel is allocated for the UE. The UE uses the DRX technology to monitor the information on the PCH transfer channel at some specific paging time. No uplink activities are permitted. The UE position is known by the UTRAN in the URA level, the specific one is the URA reported in the CELL_FACH state when the latest URA renewal is initiated. In the URA_PCH state, the UE make the following activities: According to the DRX cycle monitor the paging time, and receive the paging information on the PCH. Monitor the BCH transfer channel of the current serive cell to decode the system information When the URA chages, the URA renewal process is initiated. In such case, the DCCH logic channel cannot be used. If the network tries to initiate any activities, it needs to send one paging request on the PCCH logic channel of the cell where the UE is located. In the URA_PCH state, no resources are allocated for the data transfer. Therefore, if the UE has the data to transmit, firstly it is required to be coverted to the CELL_FACH state.
Chapter 1 Overview
UTRAN State Transition in Connection Mode

CELL_DCH state
1 Transition from the CELL_DCH state to the idle mode The UE enters idle mode after releasing the RRC connection. 2. Transition from the CELL_DCH state to the CELL_FACH state When all the dedicated physical channels are released, the state transitions to CELL_FACH. The state transition is completed through clear signaling (for example, physical channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer establishment, and transport channel reconfiguration) 3. Transition from the CELL_DCH state to the CELL_PCH state This state transition is completed through clear signaling (for example, physical channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer establishment, and transport channel reconfiguration). 4. Transition from the CELL_DCH state to the URA_PCH state This state transition is completed through clear signaling (for example, physical channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer establishment, and transport channel reconfiguration) 5. Radio resource allocation task (CELL_DCH) For DCH, multiple physical channel allocation policies should be provided. Such allocation may be permanent (a DCH release message is needed) or based on time segment or data volume. For each burst packet, resource configuration can be completed through the fast signaling on the DCH. For each radio frame, the UE and network use the Transport Format Combination Indicator (TFCI) to indicate the current data rates (respectively corresponding to uplink and downlink traffic). In TDD mode, however, DCH and DSCH or USCH may be mapped to different CCTrCHs, with their respective TFCIs completely independent. DCH transport does not change because the DSCH/USCH exists at the same time. If the configured combination set (the transport format set for a transport channel) is found to be insufficient to maintain the QoS required by a transport channel, the network starts a transport format set (TFS) for the transport channel for reconfiguration. The reconfiguration can be completed during or between data transport. In addition, on
the network, physical channels can be configured and the peak data rates can be increased or decreased. For uplink data transport, the UE reports the service traffic observed to the network so that the network can re-assess the current resource allocation. This report should contain the volume of data to be transported, buffer statuses within the UE, and so on 6. RRC connection mobility task (CELL_DCH) Whether to use macro diversity (soft handover) depends on the data quantity and frequency. RRC connection mobility is processed by measurement report, soft handover, and non-synchronization/synchronization. 7. UE measurement (CELL_DCH) The UE should perform the measurement according to the measurement control information and send a measurement report. The UE should use the connection mode measurement control information received in other states until the UE is assigned new measurement control information 8. Capturing of system information (CELL_DCH) In FDD mode, a UE with a specific capability (This UE supports the reception on one SCCPCH and one DPCH simultaneously) can read the system information broadcast on the FACH.
CELL_FACH State
1. Transition from the CELL_FACH state to the CELL_DCH state This state transition is completed when a dedicated physical channel is established through clear signaling (for example, physical channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer establishment, and transport channel reconfiguration) 2. Transition from the CELL_FACH state to the CELL_PCH state This state transition occurs when the UTRAN instructs the UE to enter the CELL_PCH state through clear signaling, such as cell update confirmation and radio bearer reconfiguration 3. Transition from the CELL_FACH state to idle mode The UE enters the idle mode after releasing the RRC connection 4. Transition from the CELL_FACH state to the URA_PCH state This state transition occurs when the UTRAN instructs the UE to enter the URA_PCH state through clear signaling, such as URA update confirmation and radio bearer reconfiguration.
Chapter 1 Overview
5. Radio resource allocation task (CELL_FACH) In the CELL_FACH state, the UE listens on a FACH. The UE should be able to send uplink control signals and send small packets on the RACH. The network can assign in advance transport channel parameters, such as the transport format set, to the UE for use when the UE uses the DCH. When a physical channel is assigned to the DCH, the UE should enter the CELL_DCH state and is used as the TFS allocated in advance to the DCH If no UE dedicated physical channel or transport channel configuration is specified, the UE should use the common physical channel and transport channel configuration according to the system information. For uplink data transport, the UE reports the service traffic observed to the network so that the network can re-assess the current resource allocation. This report should contain the volume of data to be transported, buffer statuses within the UE, and so on. When user data or control data is transmitted, a selection process is started to determine whether to transport the data through a common transport channel or to transition to the CELL_DCH state. This selection is dynamic and dependent on specific parameters, such as service parameters (data size and packet burst frequency) In FDD mode, the UTRAN can assign CPCH resources to the UE in the CELL_FACH state. After being assigned CPCH resources, the UE continues to listen on the FACH. The UE may use the RACH to send uplink control signals and small packets. The UE can also choose to send large packets (larger than the packets carried on the RACH) on the CPCH. The UE chooses either the RACH or one CPCH to maximally use the available capacity on the channel In FDD mode, for each CPCH used, the UE provides the UTRAN with CPCH measurement data, including data, queue length (the size of the current data buffer), average access time, and the service traffic of each CPCH used. Based on the measurement information, the UTRAN can periodically reassign network resources. The UTRAN assigns a CPCH set to each cell and assigns one to the UE. The UE can dynamically access these CPCH resources without UTRAN control. 6. RRC connection mobility task (CELL_FACH) In this state, the UE location on the cell level is known. When the UE selects a new cell to observe the common downlink channel of the new cell, the UE uses the cell update process to report to the UTRAN. Data transport can initiated on the downlink FACH without paging in advance. The UE listens on the system information about the UE itself and neighboring cells on the broadcast channel and BCCH,
and determines whether to perform a cell location update based on this information The UE should perform cell re-selection and start the cell update process when selecting a new UTRA cell. If another non-UTRA radio access system cell is selected, the UE should enter the idle mode and complete access according to the system specifications 7. UE measurement (CELL_FACH) The UE should perform the measurement according to the measurement control information and send a measurement report. By default, the UE should use the measure control information broadcast in system information. The network, however, can also provide measurement control information in MEASUREMENT CONTROL messages. In this case, the messages have a higher priority. 8. Sending and updating system information (CELL_FACH) The UE should read the BCH to obtain valid system information. For each acquisition, the UE may need the different combinations of the system information broadcast on the BCH. The system information on the broadcast channel is arranged based on the time the UE spends in obtaining the information needed. After the system information is modified, the time arrangement information is updated to reflect the change in the system information transported on the BCH. The new time arrangement information is broadcast on the FACH to notify the UE of the change. If the change is applicable to the UE, the modified system information is read on the BCH.
CELL_PCH State
1. Transition from the CELL_PCH state to the CELL_FACH state The UE transitions to the CELL_FACH state is realized through the paging (paging type 1) from the UTRAN or any uplink access. 2. Radio resource allocation task (CELL_PCH) In the CELL_PCH state, no resource is designated to be used for data transport. To transport data, the UE must transition to another state. The UE may use DRX to reduce power consumption. When the DRX is used, only one paging occasion is needed for each DRX interval. The network may instruct the UE to use a specific DRX interval length. The UE should determine its paging occasion in a mode the same as the idle mode 3. RRC connection mobility task (CELL_PCH)
10
Chapter 1 Overview
In the CELL_PCH state, the UE mobility is performed through the cell re-selection process. The UE should perform cell re-selection. When selecting a new UTRA cell, the UE transites to the CELL_FACH state and starts a cell update process in the new cell. After the cell update process is performed, if neither the UE nor the network transports data , the UE should return to the CELL_PCH state. If another non-UTRA radio access system cell is selected, the UE should enter the idle mode and complete access according to the system specifications. When the UE activity is low, the UTRAN may order the UE to transition to the URA_PCH state to reduce frequent cell updates. This transition is completed through the CELL_FACH state. The UTRAN may provide a inactive timer and an optional counter used to count the number of cell updates. When the number of cell updates exceeds a certain limit (network parameter), the UTRAN orders the UE to transition to the URA_PCH state. 4. UE measurement (CELL_PCH) The UE should perform the measurement according to the measurement control information and send a measurement report. When no dedicated measurement control information is assigned to the UE, the UE should uses the measurement control information according to the system information 5. Updating of transport and system information (CELL_PCH) The UE should read the BCH to obtain valid system information. For each acquisition, the UE may need the different combinations of the system information broadcast on the BCH. The system information on the broadcast channel is arranged based on the time the UE spends in obtaining the information needed.
URA_PCH State
1. Transition from the URA_PCH state to the CELL_FACH state (URA_PCH) Any activity will cause the UE to transition to the CELL_FACH state. For example, the RACH performs uplink access or the paging (paging type 1) from the UTRAN. Note that an RRC connection cannot be released in the URA_PCH state. The UE must first transition to the CELL_FACH state before releasing the signing. 2. Radio resource allocation task (URA_PCH)
11
In the URA_PCH state, no resource is designated to be used for data transport. To transport data, the UE must transition to the CELL_FACH state. The UE may use DRX to reduce power consumption. When the DRX is used, only one paging occasion is needed for each DRX interval. The network may instruct the UE to use a specific DRX interval length. The UE should determine its paging occasion in a mode the same as the idle mode. 3. RRC connection mobility task (URA_PCH) In the URA_PCH state, the location of the UE on the URA level is known. In this state, mobility is completed through the URA re-selection process. The UE should perform cell re-selection. When selecting a new UTRA cell (This URA cell is not the one originally used by the UE), the UE should transition to the CELL_FACH state and initiate a URA update to the network. After the URA update process is performed, if neither the UE nor the network transports data , the UE should return to the URA_PCH state. If another non-UTRA radio access system cell is selected, the UE should enter the idle mode and complete access according to the system specifications. 4. UE measurement (URA_PCH) The UE should perform the measurement according to the measurement control information and send a measurement report. When no dedicated measurement control information is assigned to the UE, the UE should uses the measurement control information according to the system information. 5. Sending and updating system information (URA_PCH) In the URA_PCH state, the mechanism of sending and updating system information is the same as that in CELL_PCH state.
12
Chapter
Network Selection Flow

Highlights

The UE in the idle mode Cell selection and reselection flow
UE Under Idle Mode

Overview
When the UE powers on or is in the roaming mode, its primary task is to find out the network and connect to it because the network service can be obtained only in this way. Therefore, in the idle mode, the UE action is vital to the UE. How can the UE implement the function? The following describes the flow. In the idle mode, the UE action can be divided in details into PLMN selection and reselection, cell choice and reselection and position registration. The relationships between these three flows are described in the following figure.
13
FIGURE 2
IDLE MODE PROCESS
User selection of PLMN
Automatic/ Manual selection
Indication to user
PLMN Selection and Reselection

Location Registration response PLMNs available
PLMN selected NAS Control
Cell Selection and Reselection

Radio measurements
Registration Area changes CM requests
Location Registration
After being powered on, the UE first selects a PLMN. After selecting a PLMN, the UE begins to select a cell belonging to this PLMN. When such a cell is found, the information about the neighboring cell can be obtained from the system information (broadcast). Thus, the UE can select a cell with the best signals among these cells and reside in the cell. Then, the UE initiates the location registration process (attach or location update). If the operation succeeds, the UE resides in the cell. The UE resides in the cell for four purposes: 1. To receive the system information broadcast by the PLMN. 2. To initiate the random access process in the cell. 3. To receive paging from the network. 4. To receive the broadcast services of the cell. When the UE resides in the cell and the registration succeeds, as the UE moves, the signal strengths of the current cell and the neighboring cell keep changing. In this case, the UE needs to select a most suitable cell. This is known as the cell re-selection process. This most suitable cell is not necessarily the cell that currently has the best signals. The reason is this: suppose the UE is at the edge of a cell and moves to and fro between the two cells, which happen to belong to different LAs or RAs. Thus, the UE needs to keep initiating location updates. This wastes not only resources but also the UE energy. Therefore, there are certain rules as to which cell to be reselected among all the cells.
14
Chapter 2 Network Selection Flow
After the UE reselects a cell, if the cell is found to belong to another rLA or RA, the UE initiates the location update process so that the network obtains the latest UE location information. The UE discovers LA or RA changes through the SIB1 in the system broadcast information If the location registration or update fails, for example, when the network rejects the UE, or when the current PLMN is out of the coverage area, the UE can perform PLMN re-selection to select another usable PLMN.
PMMN Selection and Reselection

The purpose of PLMN selectionand reselection is to select one applicable (that can provide the normal service), best PLMN. Through which can the UE realize the purpose? The UE can maintain one PLMN list, which will list the PLMN according to the priority, and then search from the higher priority to the lower priority so it is natural to find out the PLMN with the highest priority. In addition, there are two kinds of modes to select and reselect: automatic and manual. In brief, the automatic network selection is to select one PLMN for the UE according to the PLMN priority sequence while the manual network selection is to display all the currently applicable networks to the subscriber, give him/her the righ to select one PLMN.
Cell Selection and Reselection

After selecting a PLMN, the UE begins to select a cell, aiming to select the cell belonging to the PLMN and with the best signals. If the UE stores information, such as frequency and scrambling code, related to the PLMN, the UE performs a cell search (stored information cell selection) by using the information. Thus, a network can be found quickly. This is because in most cases, the UE is powered off and on in the same place. For example, the UE is powered off at night and is powered on in the morning. Such information is stored in the SIM card or the non-volatile memory of the mobile phone
Cell Selection
The procedure of cell selection is roughly as follows: 1. Cell search
15
The purpose of cell search is to find a cell, which, though, may not belong to the selected PLMN. The steps of cell search are as follows (A frequency needs to be locked first, of course): The UE obtains timeslot synchronization through the primary SCH. After timeslot synchronization, frame synchronization needs to be performed. Frame synchronization is completed through the synchronization code of the secondary SCH. In this procedure, the scrambling code group of the cell is also determined. Then, the UE associates each scrambling code of the scrambling code group on the CPICH until it finds the greatest one among the related results. Thus, the primary scrambling code is determined. Obviously, if the UE already knows some information about the cell, such as the frequency used and even the primary scrambling code, the above-mentioned procedure can be accelerated greatly. 2. Reading the broadcast channel From the above-mentioned procedure, the UE obtains the scrambling code of the PCCPCH, whose channel code is known and unique through the whole UTRAN. Thus, the UE can read the information of the broadcast channel. When reading the MIB, the UE can determine whether the found PLMN is the one intended, because there is a PLMN domain in the MIB. If yes, the UE finds another SIB and obtains its contents based on the scheduling information in other SIBs contained in the MIB. If not, the UE has to look for the next frequency, starting the procedure all over again (from cell search). If the current PLMN is the one intended by the UE, the UE reads SIB3 and obtains "Cell selection and re-selection". Through the information obtained, the UE performs calculations to determine whether the cell residence standards are met. If yes, the UE considers the cell a suitable cell. The UE resides in the cell and reads the other system information needed and initiates the location registration procedure. If the above-mentioned conditions are not met, the UE reads SIB11 and obtains the information on the neighboring cells. Thus, the UE can perform calculations and determines whether the neighboring cell meets the cell selection residence standards. If the UE finds that any neighboring meets the cell residence standards, the UE resides in the cell, reads other system information needed, and initiates the location registration procedure. If the UE finds no cell that meets the cell residence standards, the UE considers that there is coverage and continues the PLMN selection and re-selection.
16
Chapter 2 Network Selection Flow
Cell Reselection
In idle mode, the UE keeps monitoring the signal quality of the current cell and neighboring cells to select the best cell for providing services. This is known as cell re-selection. If the cell re-selection conditions are met within the re-selection time, the UE selects the cell, resides in the cell, and reads the broadcast messages of the cell. Cell re-selection is complete.
Cell Selection Away form Connection Mode

When the UE returns to the idle mode from the connection mode, it is required to make the cell choice to find one situable cell. This choice process is the same as the ordinary celll choice process. However, at this time, the choice of a cell is to select the cell used in the connection mode. If no suitable cells are found in these cells, the stored information cell selection should be used.
Position Registraton
Refer to the related content of MM and GMM for these flows. Herein these flows are omitted.
17
Chapter
Handover Flow in the System

Highlights

Soft handover flow Hard handover flow Handover flow between systems Forwarding handover flow
Handover Overview
Handover is one of the most remarkable features that distinguish mobile communications from fixed communications. UTRA FD supports the following handover modes: 1. Intra-mode handover: Softer handover, soft handover, and hard handover are intra-mode handovers. A hard handover can be a intra-frequency handover or inter-frequency handover 2. Transition Between Modes: It refers to the transition to the UTRA TDD mode. 3. Inter-system handover: For the R99, an inter-system handover refers a handover to the GSM system, namely, a handover to the 900 MHz, 1800 MHz, 1900 MHz GSM systems. During a hard handover, before a new link is established, the old link of a mobile station is released. That is, a channel can be established only after it is released. The old channel is torn down before being synchronized with the new channel. The old and the new channels do not take effect at the same time. During a soft handover or softer handover, the mobile station and UTRAN maintain at least one link between them. That is, a channel is removed before a new channel is established. The
19
original channel is removed only after the new channel takes effect. Inter-frequency handovers and inter-system handovers are always hard handovers. Intra-frequency handovers are not necessarily soft handovers. For example, if no Iur interface exists, a cross-Iur interface intra-frequency handover is a hard handover, and the new and old links cannot take effect at the same time. Here is another example. If the transmitting diversity modes of intra-frequency cells are different, no soft handover can be performed, either. Basic Concepts: 1. Active set: Set of cells connected to a mobile station. Subscriber information is sent from these cells. 2. Monitor set: Cells not in the active set but monitored according to the adjacent cell list assigned by the UTRAN belong to the monitor set. The UE measures the cells in the monitor set. If the measurement results meet certain conditions, these cells may be added to the active set. Therefore, the monitor set is sometimes known as the candidate set. 3. Detected Set: Set of cells in neither the active set nor the monitor set. Typical Handover Procedure: The typical handover procedure is measurement control -> measurement report -> handover decision -> handover execution -> new measurement control. During the measurement control phase, the network sends measurement control messages to notify the UE of the parameters of the measurement. During the measurement report phase, the UE sends measurement report messages to the network. During the handover decision phase, the network makes a handover decision based on the measurement report. During the handover execution, phase, the UE and network carry out the signaling flow and give responses according to the signaling.
Soft Handover
Mainly initiated by the network side, soft handovers are one of the indispensable core technologies unique to the direct spread spectrum CDMA system. Soft handovers are used to update UE active sets in the CELL-DCH state. During a soft handover, multiple service channels are activated (for the diversity of service channels) between intra-frequency channels to effectively lower the call drop rate in the handover. A soft handover is performed at the same frequency in different base stations. A soft handover performed between the sectors with the same frequency in the same base station is known as a softer handover. When a softer handover is performed, diversity
20
Chapter 3 Handover Flow in the System
signals are merged to the largest ratio at NodeB. This is different from a soft handover where selective merging of diversity signals is performed at the RNC. The RNC soft handover and softer handover flow consists of two steps: radio link operations on the Iub interface and active set update operations on the Uu interface. Radio link operations on the Iub interface are RADIO LINK SETUP, RADIO LINK ADDITION, and RADIO LINK REMOVAL. Active set update operations on the Uu interface are soft addition, software removal, and soft replacement. Difference between a soft handover and a softer handover is as follows: Soft handover means uplink link merging in macro-diversity status is performed at an RNC. Softer handover means the merging of uplinks is performed at NodeB. During a softer handover, a mobile station is located where the coverage of two adjacent sectors of a base station overlaps. The mobile station and base station communicate with each other through two air interface channels. There is one air interface channel in each sector. Thus, two spread spectrum codes need to be used in the downlink and the mobile station can distinguish these signals. The mobile station receives and processes these two signals through Rake receiver. This process is very similar to multi-path reception except that despread spectrum codes are need to be generated for each sector to ensure correct despread spectrum operations. In the uplink, a similar process is performed on the base station: The code division channel of the mobile station is received in each sector, sent to the same baseband Rake receiver, and merged to the maximum ratio through a normal method. During a softer handover, for each connection, only one power control loop is active. During a soft handover, a mobile station is located where the coverage of two sectors of different base stations overlaps. Same as a softer handover, the mobile station and two base stations perform communication through two different air interface channels at the same time. Same as a softer handover, the mobile station receives two channels (signals) through merging to the maximum ratio by using a Rake receiver. From the perspective of the mobile station, there is very little difference between a soft handover and a softer handover. In the uplink, however, the difference between a soft handover and a softer handover is very great: Two base stations receive the code division channels from the mobile station, but the received data is sent to the RNC for selective merging. This is because the frame reliability indicator provided for external loop power control needs to be used in the RNC to select the better frame from the two candidate frames. Such selection occurs each time the interlacing interval is complete. That is, the selection occurs ever 10 ms to 80 ms.
21
Between Cells in NodeB

FIGURE 3 SOFT HANDOVER INSIDE NODEB
In this case, the radio uplink can be merged in NodeB or the SRNC. If the radio uplink is merged in NodeB, it is known as a softer handover.
Between NodeBs in the Same RNC

FIGURE 4 SOFT HANDOVER BETWEEN NODEBS
Soft Handover Flow Between NodeBs in the Same RNC
22
FIGURE 5
SOFT HANDOVER BETWEEN NODEBS IN THE S AME RNC
The softer handover flow is basically the same as the soft handover flow between NodeBs. The only difference is that a softer handover is a handover in NodeB, with Iub interface message as RADIO LINK ADDITION REQUEST, while the switching Iub interface message between NodeBs is RADIO LINK SETUP REQUEST.
Between RNCs
FIGURE 6 SOFT HANDOVER BETWEEN RNCS IN THE S AME M SC
Soft Handover Between RNCs in the Same MSC uses the Iur interface:
23
FIGURE 7
INTER-IUR INTERFACE SOFT H ANDOVER
Hard Handover
Mainly initiated by the network side, a hard handover is used for the handovers between the intra-frequency/inter-frequency channels of the UE in the CELL_DCH state. During a hard handover, only one service is activated. An inter-frequency hard handover changes the radio frequency of the connection between the UE and UTRAN. the trigger decision between inter-frequency channels needs inter-frequency measurement supported by the compression mode technologies The process of a hard handover is to first tear down the communication with the original cell before gaining access from the new cell. Therefore, the performance of a hard handover is not as good as that of a soft handover. Thus, generally, an intra-frequency hard handover is considered only when the system cannot perform a soft handover. If the two cells involved in the handover belong to two different RNCs between which there is no Iur interface, an intra-frequency hard handover occurs. Depending on the range involved, a hard handover can be a hard handover between the FDD and TTD modes inside a cell, a hard handover between cells under the same NodeB, a hard handover between cells in the same RNC, or a hard handover between RNCs. Inter-RNC hard handovers fall into two parts: hard cut-aways to the DRNC through the Iur interface and inter-RNC hard cut-aways controlled by the core network. Inter-RNC hard cut-aways controlled by the core network are the same as UE-related relocation. Hard handovers correspond to Iub interface operations and Uu interface operations. Iub interface operations correspond to radio link reconfiguration. Uu interface operations are completed through the following five types of operations, of which physical channel reconfiguration is the most commonly performed operation. 1. RADIO BEARER SETUP;
24
2. RADIO BEARER RELEASE; 3. RADIO BEARER RECONFIGURATION; 4. Transport channel reconfiguration; 5. Physical channel reconfiguration; Compression Modes Also known as a slotted mode, a compression mode is used by a non-all frequency receiver in a CDMA system to measure other frequencies. The signal reception and transfer processing of a mobile phone stops for several milliseconds so that physical layer resources are set aside for the measurement of other frequencies. The reception and transfer are stopped not to lose data but to compress the data transfer time. Frame compression in a compression mode can be completed in three ways: 1. Upper-layer planning The upper layer obtains the scheduling information of the compression mode, lowers the data rate, and inserts DTX bits when a radio frame mapping is established to create transfer slots. 2. Spreading spectrum factors reduced by half Change spreading spectrum factors to improve data rates. For example, the physical layer changes the timeslot sequence number assigned by the upper layer from the timeslot format corresponding to the spreading spectrum factor 128 to the timeslot format corresponding to the spreading spectrum factor 64. This effectively doubles the number of symbols for valid physical timeslots and creates blank timeslots. 3. Puncturing methods With the spread spectrum factor and channelized code sequence unchanged, the puncturing of rate matching module in the code, multiplexing link at the physical layer can be used to lower the data rates. The transfer gap lengths (TGL) generated in this way, however, are relatively short. A compression mode is generally used for the downlink. If the uplink enters the compression mode, the downlink must enter the compression mode in cooperation at the same time.
25
FIGURE 8
CONDENSATION MODE PRINCIPLE
Inter-Frequency Hard Handover under the Same RNC

FIGURE 9 INTER-FREQUENCY HARD HANDOVER UNDER THE S AME RNC
Inter-RNC Hard Handover under the same MSC

The hard handover between different RNCs under the same MSC does not use the Iur interface process, which is the same as the hard handover process between different MSCs. Both are the hard handover process accompanied by repositioning.
26
FIGURE 10
RE-POSITION CAUSED BY INTER-RNC H ARD HANDOVER
Inter-Systems Handover
The inter-systems handover is based on supporting the measurement between the systems with the condensation mode, which is divided into two kinds: handover between the CS domain systems and handover between the PS domain systems. All the inter-system handovers in the CS domain are initiated by the network side and completed through handover commands. There are three possibilities of CS system cut-aways: 1) Based on a measurement report, the RNC determines that a handover to the GSM system needs to be performed; 2) The CN specifies to perform a handover when delivering RAB designation, namely, a inter-CS system switching; Direct retry (For example, when no resource is available for distribution) In terms of flow, a CS-domain inter-system cut-away consists of two phases: Iu interface CS-domain inter-system cut-away preparation and Uu interface inter-system cut-away request. Iu interface CS-domain inter-system cut-away preparation phase corresponds to the relocation preparation message. Uu interface inter-system cut-away request phase corresponds to the cut-away message HANDOVER FROM UTRAN COMMAND. CS-domain inter-system cut-aways involve the Iu interface relocation process and Uu interface system CS-domain cut-away process. The Iu interface relocation process corresponds to the resource allocation message. The Uu interface system CS-domain cut-away process corresponds to the HANDOVER TO THE UTRAN COMPLETE message, with the Uu interface system CS-domain cut-away process as an intermediate process.
27
A PS-domain handover can be initiated by the UE or by the network side. A PS-domain cut-away is initiated by the network side for the UE in the CELL_DCH or CELL_FACH state, involving the Uu interface PS-domain cut-away process and Iu interface context information acquisition process. The Uu interface PS-domain cut-away process corresponds to the CELL CHANGE ORDER FROM UTRAN message. The Iu interface context information acquisition is an intermediate process, corresponding to the Iu interface context information acquisition message. The PS-domain cut-away initiated by the UE is for the UE in the CELL_FACH, CELL_PCH, or URA_PCH state, triggered by the UE cell re-selection process and with no corresponding message on Uu interface. Only the context information acquisition process exists on the Iu interface. The context information acquisition process on the Iu interface consists of two phases: Iu interface context information acquisition request and context transfer, respectively corresponding to the messages SRNS CONTEXT REQUEST/SRNC CONTEXT RESPONSE and SRNS DATA FORWARD COMMAND/FORWARD SRNC CONTEX. Note that the failure of Iu interface context information acquisition process does not affect subsequent flows. PS-domain cut-in triggering corresponds to the RRC connection establishment request message. The PS-domain cut-in initiated by the UE corresponds to the RRC connection establishment request reason Inter-RAT cell re-selection. The PS-domain cut-in initiated by the network side corresponds to the RRC connection establishment request reason Inter-RAT cell change order. The subsequent RAB assignment message on Iu interface contains the serial number information about the PDCP and GTP-U.
28
Handover Between CS Domain Systems

FIGURE 11 U T R AN G S M / B S S H A N D O V E R
29
FIGURE 12
S E R V I C E B A S E D U T R AN T O G S M / B S S I N T E R S Y S T E M H A N D O V E R
30
FIGURE 13 HANDOVER
D I R E C T R E T R Y B A S E D U T R AN T O G S M / B S S I N T E R S Y S T E M
31
FIGURE 14
G S M / B S S T O T H E U T R AN H A N D O V E R
Handover Between PS Domain Systems

FIGURE 15 UM TS TO GPRS CELL RESELECTION, THE UE INITI ATED
32
FIGURE 16 UM TS TO GPRS CELL RESELECTION, THE UE INITI ATED, WITH UE CONTEXT ACCESS PROCESS, WITHIN ONE SGSN
33
FIGURE 17
UM TS TO GPRS CELL RESELECTION CONTEXT ACCESS PROVES, BETWEEN TWO SGSNS
UE I NITIATED, WITH UE
34
FIGURE 18
UM TS TO GPRS CELL RESELECTION, NETWORK INITI ATED
FIGURE 19
GP RS TO UM TS CELL RESELECTION
35
FIGURE 20
GP RS TO UM TS CELL RESELECTION (WITHIN ONE SGSN)
36
FIGURE 21
GP RS TO UM TS CELL RESELECTION (BETWEEN TWO SGSNS)
Forward Handover
A forward handover means that the UE initiates a cell update/URA update for the mobility management of the UE in the UTRAN connection mode but using only the common channel. A cell update generally refers to a notification of a location change of the UE in the CELL_PCH/CELL_FACH state to
37
the RNC for timely updating of the information about the UE on the UTRAN side. A cell update is also used to monitor RRC connections, switch RRC connection states, and perform the anomaly report functions. The URA update flow is used for the UTRAN registration area URA update by the UE in the URA_PCH state. Depending on ranges, forward handovers fall into two types: 1. Cell update process among the cells in the RNCDepending on parameter differences, this process can be divided into two flows: one requiring reconfiguration (returning the RB/Trch/Phy reconfiguration complete message) and the other requiring no reconfiguration (If a parameter such as a newly assigned C_RNTI, the UE needs to return the Mobility Info Confirm message). 2. Cell update process among different RNC cellsThis process is further divided into two flows: one requiring relocation (updating SRNC) and the other requiring no relocation (updating DRNC).
FIGURE 22 CELL UPDATE WITH SRNS RELOC ATION
38
FIGURE 23
CELL UPDATE VIA I UR WITHOUT SRNS RELOCATION
FIGURE 24
CELL UPDATE (CORE NETWORK)
39
Chapter
Call Service Flow

Highlights

Paging flow RRC connection setup flow Direct transfer message flow UE capability query flow RAB setup flow
Overview
When the UE finds a cell and reads the system messages of the cell, the UE can obtain the parameter configuration information about the system and the conditions for network access There are two types of call establishment: UE as the caller and UE as the callee. The difference between the two is that when the UE acts as the callee, the system needs to page the UE in the specified area through the paging flow before the call is established. Regardless of whether the UE acts as the caller or callee, call establishment and call release contain the following procedure: 1. An RRC connection is established between the UE and UTRAN. 2. A connection is established between the UE and CN through a direct transfer message. 3. UE capability information flow. 4. RAB establishment flow. 5. RAB release and Iu release flow. 6. RRC connection release flow.
41
Paging Flow
Paging can be initiated by the CN or UTRAN The paging initiated by the CN is used to establish a signaling connection. The paging initiated by the CN can be collaborated or non-collaborated. Through the RANAP PAGING message, the CN indicates whether the RNC needs to perform UTRAN collaborated paging. In collaborated paging, the RNC checks whether the UE has any other CN-domain signaling connection. If the UE has any other CN-domain signaling connection and is in the CELL_DCH or CELL_FACH state, the paging message is delivered through the DCCH channel of the existing connection on the radio interface. If the UE has any other CN-domain signaling connection and is in the CELL_PCH or URA_PCH state, the paging message is delivered through the PCCH channel on the radio interface. If the UE has no other CN-domain signaling connection, the paging message is delivered through the PCCH channel. In non-collaborated paging, the RNC directly delivers the paging message through the PCCH channel in the paging area specified by the CN without checking whether UE has any CN-domain signaling connection not in the paging domain. In paging initiated by the UTRAN, the UE in the CELL_PCH or URA_PCH state can be paged. The UE initiates a cell update process through a paging response to transit the user state from CELL_PCH or URA_PCH to CELL_FACH. Alternatively, when the system information changes, the UTRAN triggers the UE (in idle mode, CELL_PCH or URA_PCH state) to read the system information after the update again goes through paging messages. If the UE is in idle mode or in the CELL_PCH or URA_PCH state. The RNC pages the UE by using the PAGING TYPE1 message through the PCCH channel. The RNC pages the UE by using the PAGING TYPE2 message through the DCCH channel.
Paging the UE in Idle Mode or PCH State

The UTRAN generally pages the UE in idle mode, CELL_PCH, or URA_PCH state by using the PAGING TYPE1 message through the PCCH channel. Such paging generally occurs in the following cases: 1. Paging is initiated by an upper level of the network side to establish a call or a signaling connection;
42
Chapter 4 Call Service Flow
2. The UTRAN initiates the paging that triggers UE state transition to transit the UE state from CELL_PCH or URA_PCH to CELL_FACH; 3. When the system information changes, the UTRAN initiates the paging that triggers the UE to read the updated system information. In this case, the value label of the master information block (MIB) is contained in the "BCCH modification info" in PAGING TYPE 1 message.
FIGURE 25 P AGING I DLE TYPE OR PCH S TATE
UE
PAGING TYPE 1
UTRAN
The UTRAN sends the PAGING TYPE1 message when an appropriate paging opportunity is available to start the paging process. The UTRAN can select multiple paging opportunities to repeatedly page a UE to increase the possibility of the UE correctly receiving paging messages. The UE in idle mode or PCH state monitors the appropriate paging opportunities and receives the paging messages from the network layer.
Paging the UE in CELL_DCH or CELL_FACH State

The UTRAN generally pages the UE in CELL_DCH or CELL_FACH state by using the PAGING TYPE2 message through the DCCH channel.
FIGURE 26 P A G I N G C E L L _ D C H O R C E L L _ F AC H S T A T E
UE
PAGING TYPE 2
UTRAN
43
The UTRAN sends the PAGING TYPE2 message through the DCCH channel to initiate the paging process. Such paging is also known as dedicated paging. The UE receives and reads the contents in the PAGING TYPE 2 message and reports the paging reason, paging record category identifier, and other information to the non-access layer of the local side. The paging flow is complete. This process does not affect any other RRC process running on the UE side. If the UE finds any protocol error in the PAGING TYPE 2 message received, the UE discards the paging message, uses the AM RLC mode through the uplink DCCH, and sends the RRC STATUS message to the UTRAN.
Examples of Paging Flow

Description of the Signaling Flow: 1. The CN initiates paging and the UE in idle mode. In this case, the UTRAN pages the UE by sending a PAGING TYPE1 message. 2. The CN initiates paging and the UE is in CELL_DCH or CELL_FACH state of the connection mode. In this case, the UTRAN pages the UE by sending a PAGING TYPEE2 message. 3. The CN initiates paging and the UE is in CELL_PCH or URA_PCH state of the connection mode. In this case, the UTRAN first transitions the state of the UE from CELL_PCH or URA_PCH to CELL_FACH by sending a PAGING TYPE1 message. Then, the UTRAN pages the UE by sending a PAGING TYPE2 message. 4. The UTRAN initiates paging and the UE is in CELL_PCH or URA_PCH state of the connection mode. In this case, the UTRAN pages the UE by 1. sending a PAGING TYPE1 message so that the state of the UE transitions to CELL_FACH.
RRC Connection Establishment Flow

When the UE is in idle mode, if the NAS (non-access layer) of the UE requests the establishment of a signaling connection, the UE initiates the RRC connection request flow.
44
When the RNC receives an RRC connection request from the UE, the RNC determines whether to accept or reject the request based on a specific algorithm. If the RNC accepts the request, the RNC determines whether to establish the RRC connection on a dedicated channel or common channel based a specific radio resource algorithm. The RRC connection establishment flows vary with RRC connection establishment channels. If the RRC connection cannot be established, the RNC rejects the establishment of the RRC connection. Description
RRC connection establishment requests are always initiated by the UE. An RRC connection release request is initiated by the RNC. Each UE can have up to one RRC connection.
RRC Connection Establishment on Special Channles

If the RRC connection is set up on the special channel, the RNC needs to allocate the special radio resource for the UE, sets up the radio links, and sets up the ALCAP user side carrier of the Iub interface for the radil links.
FIGURE 27 RRC CONNECTION S ETUP (SPECI AL CHANNEL)
UE
: RRC CONNECTION REQUEST 1.CCCH RRC
NodeB
RNC
RRC
2.Allocate parameters such asRNTIL1 L2 3. RADIO LINK SETUP REQUEST NBAP 4. RADIO LINK SETUP RESPONSE NBAP NBAP NBAP
5.ALCAP Setup and synchronization

6. CCCH : RRC CONNECTION SETUP RRC 7. DCCH: RRC CONNECTION SETUP COMPLETE RRC RRC RRC
Description of the Signaling Flow: 1. Through the uplink CCCH, the UE sends RRC CONNECTION REQUEST to request for setting up an RRC connection.
45
2. According to the RRC connection request cause and the system resource state, the RNC decides that the UE is set up on the special channel, and allocates RNTI, radio resources and other resources (L1 and L2 resources). 3. The RNC sends the NodeB the RADIO LINK SETUP REQUEST to request the NodeB for allocating the specific radio link resources necessary for the RRC connection. 4. After the NodeB resource is well-prepared, the RADIO LINK SETUP RESPONSE is sent to the RNC. 5. The RNC uses the ALCAP protocols to set up the Iub interface user side transfer bearer, and implements the synchronous process between the RNC and the NodeB. 6. Through the downlink CCCH channel, the RNC sends the UE the RRC CONNECTION SETUP message, which includes the special channel information included in the RNC. 7. After the UE verifies that the RRC connection setup succeeds, the newly setup uplink DCCH channel sends the RNC the RRC CONNECTION SETUP COMPLETE message. The RRC connection setup process is finished.
Setting up RRC Connection on a Public Channel

When the RRC connection is set up on the public channek, because the newly setup cell public resources have been used, it is not required to set up the radio link or the data transfer bearer on the user side. It is only necessary to map the logic channel used by the UE on the cell public channel, and the rest process is similar to the situation that the RRC is connected to set up on the special channel.
46
FIGURE 28
RRC CONNECTION S ETUP (PUBLIC CH ANNEL)
UE
1.CCCH : RRC CONNECTION REQUEST RRC
NodeB
RNC
RRC
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
RRC Connection Rejection

If the RNC judges that this RRC connection request cannot be set up (such as the resources are insufficient), the RNC directly sends the UE the RRC CONNECTION REJECT message, in which the cuase of rejecting the RRC connection is indicated.
FIGURE 29 RRC CONNECTION REJECT
UE
RNC
CCCH:RRC CONNECTION REQUEST
CCCH:RRC CONNECTION REJECT
47
Direct Transfer Message Flow

Direct transfer message refers to the signaling interaction NAS information between the UE and the CN, such as authentication, service request, connection setup and so on. As the information is transparently transmitted in the RNC, it is called Direct Transfer Information. What the RRC connection sets up is the signaling connection between the UE and the RNC, so it is also required to go on setting up the signaling connection between the UE and the CN so as to transmit the direct transfer information. When the RNC receives the first piece of direct information (the INITIAL DIRECT TRANSFER information), it sets up a signaling connection between the RNC and the CN, which is set up above the SS7 SCCP. After the signaling connections of the UE and CN are set up successfully, the information the UE sends is sent to the RNC through the UPLINK DIRECT TRANSFER information while the RNC coverts the information to the DIRECT TRANSFER information; the information that the CN sends to the UE is sent to the RNC through the DIRECT TRANSFER message while the RNC converts the information to the DOWNLINK DIRECT TRANSFER message to be sent to the UE.
Initial Direct Transfer

The initial direct transfer process is used to set up one signaling connection between the RNC and the CN, and meanwhile bear one piece of initial NAS information. The content of the NAS information is not explained in the RNC, but is forwarded to the CN. Description
When the UE stays at the CELL_PCH or the URA_PCH state, the UE will at first make the cell renewal for making the initial direct transfer while the state is transferred into the CELL_FACH state. The renewal reason is Uplink Data Transfer. After the cell renewal successfully ends, the UE will go on with the initial direct transfer.
48
FIGURE 30
INITIAL DIRECT TRANSFER
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
Description of the Signaling Flow: 1. After the RRC connection is set up, the UE sends the RNC the INITIAL DIRECT TRANSFER information through the RRC connection while the information carries such content as initial NAS information and NC flags sent to the CN by the UE. 2. The RNC receives the initial direct transfer information of the UE, and sends the SCCP CONNECTION REQUEST information through the Iu interface while the information data is the INITIAL UE MESSAGE sent to the CN by the RNC. The information includes the information content sent to the CN by the UE. 3. If the CN prepares to accept the connection request, the CN returns the CONNECTION CONFIRM information to the SCCP to indicate that the SCCP connection setup succeeds. After the RNC receives the information, the signaling connection setup is confirmed to be successful. 4. If the CN cannot accept the connection request, the CN returns the CONNECTION REFUSE information to the SCCP while the SCCP connection setup fails. If the RNC receives the information and verifies the signaling connection setup to fail, the RNC enables the RRC release process. For the NAS content carried during the initial direct transfer process, the CN will send the UE the acceptance or refusal information to the service through the downlink direct transfer process.
49
Uplink Direct Transfer

When the UE needs to send a NAS message to the CN on an existing signaling connection, the UE initiates the uplink direct transfer procedure. Description
When the UE stays at the CELL_PCH or the URA_PCH state, it is necessary to make the cell renewal before making the initial direct transfer while the state is transferred into the CELL_FACH state. The renewal reason is Uplink Data Transfer. After the cell renewal successfully ends, the UE will go on with the initial direct transfer.
UPLINK DIRECT TRANSFER
FIGURE 31
UE
1. UPLINK DIRECT TRANSFER RRC
SRNC
RRC
CN
2.DIRECT TRANSFER RANAP RANAP
Uplink Direct Transfer: 1. The UE sends an UPLINK DIRECT TRANSFER message to the RNC to initiate the uplink direct transfer process. The message contains such information as NAS message and CN identification. 2. The RNC routes the message according to the CN identifier in the message and sends the NAS information carried in the message to the CN through a DIRECT TRANSFER message on Iu interface. The uplink direct transfer process is complete. Description
If the UPLINK DIRECT TRANSFER message includes the Measured Results on RACH information unit, it shows that the message carries the measurement report while the UTRAN uses the related analyzed information content to control the radio resource and the rest of the message is still transmitted to the CN.
50
Downlink Direct Transfer

When the CN needs to send the NAS message to the UE on the existing signaling connection, it enables the downlink direct transfer process. The signaling flow of the downlink direct transfer is shown in the following figure.
FIGURE 32 DOWNLINK DIRECT TR ANSFER
UE
SRNC
1.DIRECT TRANSFER RANAP
CN
RANAP
2. DOWNLINK DIRECT TRANSFER RRC RRC
Signaling Flow Description: 1. The CN sends a DIRECT TRANSFER message to the RNC to initiate the downlink direct transfer process. The message contains the NAS message. 2. The UTRAN sends a DOWNLINK DIRECT TRANSFER message through the DCCH channel in AM RLC mode. The message carries the NAS information that the CN sends to the UE and CN identifier. The UE receives and reads the DOWNLINK DIRECT TRANSFER message carrying the NAS information. If the received message contains a protocol error, the UE sends an RRC STATUS message on the uplink DCCH in AM RLC mode.
UE Capability Information Flow

UE capability information includes security capability, location capability, measurement capability, physical channel capability, and transport channel capability. The vendors, specifications, and capabilities of UEs are different. Therefore, after an RRC connection is established, the UE should send UE capability information to the UTRAN so that the network side configures the UE according to the capability parameters supported by the UE.
51
UE capability information can be transferred to the RNC in the following three scenarios: 1. After an RRC connection is established, the UE capability information is transferred to the RNC through an RRC CONNECTION SETUP COMPLETE message. 2. After an RRC connection is established, when the RNC finds that the corresponding capability information does not exist, the RNC sends a UE CAPABILITY ENQUIRY message to the UE. The UE sends the UE capability information to the RNC through a UE CAPABILITY INFORMATION message; 3. After an RRC connection is established, when the UE capability information changes, the UE sends the new UE capability information to the RNC through a UE CAPABILITY INFORMATION message.
UE Capability Information Query

Through the UE capability information query, the UTRAN requests the UE for enabling the UE capability query process, shown in the following figure.
FIGURE 33 UE C AP ABILITY QUERY
UE
UE CAPABILITY ENQUIRY
UTRAN
Through the downlink DCCH logic channel, the UTRAN introduces the AMRLC mode to send the UE CAPABILITY ENQUIRY message to implement the UE capability information query process.
UE Capability Information Update

If the UTRAN initiates the UE capability information enquiry process or the UE capability information changes during the RRC connection, the UE initiates the UE capability information update process. The UE capability information update process is used to transfer the radio network related capabilities supported by the UE to the UTRAN.
52
FIGURE 34
UE C AP ABILITY INFORMATION UPD ATE
1. The UE sends a UE CAPABILITY INFORMATION message in AM or UM RLC mode on uplink DCCH. The message carries the UE capability information. 2. The UTRAN reads the UE capability information and sends a UE CAPABILITY INFORMA CONFIRM message in AM or UM RLC mode on the downlink DCCH channel. The UE capability information update process is complete.
RAB Establishment Flow

The RAB is used between the UE and CN to transfer voice, data, multimedia, and other services. The RAB is established only after a signaling connection is established between the UE and CN. RAB establishment is the function initiated by the CN for execution by the UTRAN. The basic procedure of RAB establishment is as follows: The CN initiates a RAB ASSIGNMENT REQUEST message. The RNC configures the parameters related to the radio network according tot he QoS parameters in the RAB ASSIGNMENT REQUEST, and then returns a RAB ASSIGNMENT RESPONSE message to the CN to indicate whether the RAB is established. Description
A RAB ASSIGNMENT REQUEST is always initiated by the CN. Each UE can have one or more RABs.
Depending on the RRC connection states before and after the RAB establishment, there are three scenarios for the RAB establishment flow: 1. DCH-DCH: Before the RAB is established, an RRC connection uses the DCH. After the RAB is established, an RRC connection uses the DCH; 2. CCH-DCH: Before the RAB is established, an RRC connection uses the CCH. After the RAB is established, an RRC connection uses the DCH; 3. CCH-CCH: Before the RAB is established, an RRC connection uses the CCH. After the RAB is established, an RRC connection uses the CCH;
53
DCH-DCH
When the current RRC state of the UE is DCH, the RAB assigned can be established on DCH only. Based on radio link reconfiguration, the RAB establishment flow can be divided into two scenarios: 1. Synchronous reconfiguration of radio links 2. Asynchronous reconfiguration of radio links The difference between the two is whether the new configuration parameter can be used immediately when the NodeB and UE receive the configuration message delivered by the Serving Radio Network Controller (SRNC).
RAB Setup Flow of Synchronously Reconfiguring Radio Links

In this case, synchronization and reconfiguration of radio links need to be performed among SRNC, NodeB, and UE. The synchronization process is as follows 1. When NodeB receives a reconfiguration radio link message delivered by the SRNC, the NodeB cannot use the new configuration parameter immediately. Instead, the NodeB prepares the corresponding radio resources, waits for the reconfiguration execution message delivered by the SRNC, and obtains the synchronization time specified by the SRNC; 2. Upon receiving the configuration message delivered by the SRNC, the UE also cannot immediately use the new configuration parameter. Instead, the UE obtains the synchronization time specified by the SRNC in the message; 3. At the synchronization time specified by the SRNC, NodeB and UE use the new configuration parameter at the same time. The figure of RAB Setup Flow of Synchronously Reconfiguring Radio Links is shown in the following figure.
54
FIGURE 35
R AB S E T U P F L O W ( D C H - D C H , S Y N C H R O N O U S L Y )
UE
NodeB
SRNC
1. RAB ASSIGNMENT REQUEST RANAP
CN
RANAP
2.ALCAP setup 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 8. RADIO BEARER SETUP COMPLETE RRC RRC 9. RAB ASSIGNMENT RESPONSE RANAP RANAP
The signaling flow is described as follows: 1. The CN sends a RAB ASSIGNMENT REQUEST message to the UTRAN to initiate the RAB establishment process. 2. Upon receiving the RAB establishment request, the SRNC maps the QoS parameters of the RAB to AAL2 link feature parameters and radio resource feature parameters. The ALCAP of Iu interface initiates the user plane transport bearer establishment process according to the AAL2 link feature parameters (For the PS domain, this step does not exist). 3. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the controlled NodeB to request the controlled NodeB to prepare to add one or more dedicated channels (DCHs) carrying RAB on the existing radio link. 4. NodeB allocates the resources accordingly and then sends a RADIO LINK RECONFIGURATION READY message to the SRNC to which the NodeB belongs, notifying the SRNC that the radio link reconfiguration preparation is complete. 5. The ALCAP of the Iub interface in the SRNC initiates the user plane transport bearer establishment process on Iub interface. NodeB and SRNC exchange the uplink/downlink synchronization frames of the DCH frame protocol for synchronization. 6. The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the UE. 7. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the controlled NodeB.
55
8. After executing RB setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. 9. Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC returns a RAB ASSIGNMENT RESPONSE message to the CN. The RAB establishment flow is complete.
RAB Establishment Flow with Asynchronous Reconfiguration Radio Links

In this case, synchronization and reconfiguration of radio links does not need to be performed among SRNC, NodeB, and UE. Upon receiving the configuration message delivered by the SRNC, the NodeB and UE immediately use the new configuration parameter. RAB Establishment Flow with Asynchronous Reconfiguration Radio Links is described as follows.
FIGURE 36 R AB S E T U P F L O W ( D C H - D C H , A S Y N C H R O N O U S L Y )
UE
NodeB
SRNC
1. RAB ASSIGNMENT REQUEST RANAP
CN
RANAP
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
Description of the Signaling Flow: 1. The CN sends a RAB ASSIGNMENT REQUEST message of the RANAP protocol to the SRNC to initiate the RAB establishment process. 2. Upon receiving the RAB establishment request, the SRNC maps the QoS parameters of the RAB to AAL2 link feature parameters and radio resource feature parameters. The ALCAP of Iu interface initiates the user plane transport bearer establishment process according to the AAL2 link
56
feature parameters (For the PS domain, this step does not exist). 3. In asynchronous mode, radio reconfiguration does not need to be performed synchronously. The SRNC sends an NBAP RADIO LINK RECONFIGURATION REQUEST message to the controlled NodeB to request the controlled NodeB to establish a new DCH on the existing radio link. 4. Upon receiving the RADIO LINK RECONFIGURATION REQUEST message, NodeB assigns the resources accordingly and then returns a RADIO LINK RECONFIGURATION RESPONSE message to the SRNC to which the NodeB belongs, notifying the SRNC that the radio link reconfiguration is complete. 5. The ALCAP of the Iub interface in the SRNC initiates the user plane transport bearer establishment process on Iub interface. NodeB and SRNC exchange the uplink/downlink synchronization frames of the DCH frame protocol for synchronization. 6. The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the UE. 7. After executing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC 8. Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC returns a RAB ASSIGNMENT RESPONSE message to the CN. The RAB establishment flow is complete.
CCH-DCH
When a RRC connection is established on a CCH, the RNC can establish the assigned RAB on a DCH according to the QoS parameters in the RAB assignment message. In this case, the RRC connection state needs to be changed from CCH to DCH. CCH-DCH RAB setup flow is shown in the following figure.
57
FIGURE 37
R AB S E T U P F L O W ( C C H - D C H )
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
6. RADIO BEARER SETUP RRC 7. RADIO BEARER SETUP COMPLETE RRC RRC 8. RAB ASSIGNMENT RESPONSE RANAP RANAP RRC
Description of the Signaling Flow: 1. The CN sends a RAB ASSIGNMENT REQUEST message of the RANAP protocol to the SRNC to initiate the RAB establishment process. 2. Upon receiving the RAB establishment request, the SRNC maps the QoS parameters of the RAB to AAL2 link feature parameters and radio resource feature parameters. The ALCAP of Iu interface initiates the user plane transport bearer establishment process according to the AAL2 link feature parameters (For the PS domain, this step does not exist). 3. The SRNC starts the radio link establishment process on Iub interface and sends a RADIO LINK SETUP REQUEST message to the controlled NodeB to request the NodeB to assign the specific radio link resources required for the RRC connection. 4. Upon completing the resource preparations, NodeB sends a RADIO LINK SETUP RESPONSE message to the RNC. 5. The RNC establishes the Iub interface user plane transport bearer through ALCAP and completes the synchronization between the RNC and NodeB. 6. The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the UE. 7. After executing radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC. 8. Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC returns a RAB ASSIGNMENT RESPONSE message to the CN. The RAB establishment flow is complete.
58
CCH-CCH
When a RRC connection is established on a CCH, the RNC can continue to establish the assigned RAB on a CCH according to the QoS parameters in the RAB assignment message.
FIGURE 38 R AB S E T U P F L O W ( C C H - C C H )
UE
NodeB
SRNC
1. RAB ASSIGNMENT REQUEST
CN
RANAP
RANAP
2. ALCAP setup 3. RADIO BEARER SETUP RRC 4. RADIO BEARER SETUP COMPLETE RRC RRC 5. RAB ASSIGNMENT RESPONSE RANAP RANAP RRC
Description of signaling flow: 1. The CN sends the RAB ASSIGNMENT REQUEST information of the RANAP protocol to enable the RAB setup request. 2. After the SRNC receives the RAB setup request, the SRNC maps the RAB QoS parameter as the AAL2 link feature parameter and the radio resource feature parameter. According to the AAL2 link feature parmameter, the Iu interface ALCAP enables the transfer bearer setup process of the Iu interface user side. 3. The SRNC sends the UE the RADIO BEARER SETUP message of the RRC protocol. 4. After the UE implements the radio bearer setup, the UE sends the SRNC the RADIO BEARER SETUP COMPLETE message. 5. After the SRNC receives the information that the radio bearer has implemented the setup, the SRNC sends the CN the RAB ASSIGNMENT RESPONSE message. The RAB setup process is finished.
59
Chapter
Service Release Flow

Highlights

Signaling release flow RRC connection release flow RAB release flow
Overview
Service release flows fall into two types: high-layer release request initiated by the UE and high-layer release request initiated by the CN. Regardless of release type, the ultimate resource release process is initiated by the CN. For a UE, such a scenario may exist: An RRC connection corresponds to multiple RABs (For example, VP service and Web Browse service are performed at the same time), and CS-domain and PS-domain correspond to a Iu signaling connection respectively. Service release flow is roughly divided into several scenarios. 1. CS-domain service release When the UE releases a CS-domain service:
If only one RAB is established in CS domain, the CN initiates an IU RELEASE COMMAND message. Upon receiving this message, the RNC automatically releases the Iu signaling connection and RAB. When the service release is complete, the SRNC determines whether the RRC connection corresponds to any Iu signaling connection (PS domain). If not, the RRC connection release process is initiated. If multiple RABs are established in CS domain, the CN initiates the RAB release flow only for the RAB that needs to be released, without releasing the Iu signaling connection. When the UE releases a PS-domain service:
2. PS-domain service release
61
If only one RAB is established in PS domain, the CN first initiates the RAB release flow for the RAB. When the release is complete, the CN sends an IU RELEASE COMMAND message before releasing the Iu signaling connection on Iu-PS interface. When the service release is complete, the SRNC determines whether the RRC connection corresponds to any Iu signaling connection (CS domain). If not, the RRC connection release process is initiated. If multiple RABs are established in PS domain, the CN initiates the RAB release flow only for the RAB that needs to be released, without releasing the Iu signaling connection.
Iu Signaling Connection Release Flow

Signaling Connection Release Request
The Iu connection release flow is generally initiated directly the CN and can also be initiated by the CN at the request of the UTRAN. The Iu connection release request flow is used by the UTRAN to request the CN to initiate the Iu connection release process.
FIGURE 39 SIGN ALING CONNECTION RELEASE REQUEST
RNC
IU RELEASE REQUEST
CN
The SRNC sends an IU RELEASE REQUEST message to the CN domain to initiate the Iu connection release request process. The message indicates the reason for releasing the Iu connection. The CN determines how to react to the Iu connection release request. For example, if the CN decides to release the Iu connection, the CN initiates the Iu connection release process.
62
Chapter 5 Service Release Flow
Signaling Connection Release

The Iu connection release process is used by the CN to release an Iu connection, releasing all the UTRAN resources related to a specific Iu connection. The following shows the signaling flow.
FIGURE 40 SIGN ALING CONNECTION RELEASE
RNC
1.IU RELEASE COMMAND 2.IU RELEASE COMPLETE
CN
1. The CN sends an IU RELEASE COMMAND message to the UTRAN to initiate the signaling connection release process. The message contains the reason for releasing the signaling connection, for example, "Successful Relocation", "Normal Release", "Release due to the UTRAN Generated Reason", "Relocation Cancelled", and "No Remaining RAB". After sending the message, the CN no longer sends any connection-oriented RNAP message on this connection. 2. Upon receiving the message, the RNC clears the related resources in the UTRAN. The RNC sends an IU RELEASE COMPLETE message to the CN. The Iu connection release process is complete.
RAB Release Flow

For the RAB release flow, like the RAB establishment flow, there are three scenarios: 1. DCH-DCH: Before the RAB is released, an RRC connection uses the DCH. After the RAB is released, an RRC connection uses the DCH; 2. CCH-CCH: Before the RAB is released, an RRC connection uses the CCH. After the RAB is released, an RRC connection uses the CCH 3. DCH-CCH: Before the RAB is released, an RRC connection uses the DCH. After the RAB is released, an RRC connection uses the CCH; Only the RAB release flow in the DCH-DCH scenario is described. The RAB release flows in the other scenarios are similar.
63
Similar to the RAB establishment flow, on a radio interface, there are two scenarios for the DCH-DCH RAB release: 1. Synchronous reconfiguration of radio links 2. Asynchronous reconfiguration of radio links The RAB release flow of the DCH-DCH synchronous reconfiguration of radio links is described
FIGURE 41 R AB R E L E A S E ( D C H - D C H , S Y N C H R O N O M O U S L Y )
UE
NodeB Serving RNS
Serving RNC
RANAP
CN
1 RAB ASSIGNMENT REQUEST RANAP [Release]
NBAP
2RADIO LINK RECONFIGURATION PRPARE NBAP [DCH Deletion]
3.RADIO LINK RECONFIGURATION READY NBAP NBAP RRC 4:RADIO BEARER RELEASE RRC 5.RADIO LINK RECONFIGURATION COMMIT NBAP NBAP
Apply new transport format set DCCH 6.DCCH : RADIO BEARER RELEASE COMPLETE
RRC
RRC
7.ALCAP Iub Data Transport Bearer Release
8. ALCAP Iu Data TransportBearer Release not required towards PS domain 9. RAB ASSIGNMENT RESPONSE RANAP
RANAP
Description of the Signaling Flow: 1. The CN sends a RAB ASSIGNMENT REQUEST message (release) to start the RAB release flow. The message indicates the ID of the RAB to be released. 2. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB to request the NodeB to prepare for the releasing of the DCH carrying the RAB. 3. The NodeB sends a RADIO LINK RECONFIGURATION READY message to the SRNC to notify the SRNC that the release preparations are complete. 4. The SRNC sends a RADIO BEARER RELEASE message to the UE to start the bearer release flow. 5. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB.
64
6. The SRNC receives a RADIO BEARER RELEASE COMPLETE message from the UE. 7. The RNC releases the data transport bearer on Iub interface. 8. The SRNC uses ALCAP. In case of AAL2 bearer, the SRNC sends an AAL2 release message to start releasing the Iu data transport bearer between the SRNC and CN (This step is not needed for the PS domain). 9. The SRNC sends a RANAP RAB ASSIGNMENT RESPONSE to the CN. The release flow is complete. Note that, when the RNC user plane becomes abnormal, the RANAP sends a RAB RELEASE REQUEST message to the CN to request the CN to release the affected RAB.
FIGURE 42 R AB R E L E A S E R E Q U E S T
RNC
RAB RELEASE REQUEST
CN
Joint Release Flow of CS-Domain lu Signaling Connection and RAB

If only one service is created in the CS domain, when the service is released, the MSC first sends an IU RELEASE COMMAND message to the RNC. Upon receiving the message, the RNC releases the Iu signaling connection and RAB on Iu-CS interface at the same time. Joint Release Flow of CS-Domain lu Signaling Connection and RAB is shown in the following figure.
65
FIGURE 43 JOINT RELE ASE FLOW OF CS-DOMAIN LU SIGNALING C O N N E C T I O N A N D R AB
UE
NodeB Serving RNS
Serving RNC
RANAP 1 IU RELEASE COMMAND
CN
RANAP
2 RADIO LINK RECONFIGURATION PRPARE NBAP NBAP [DCH Deletion] 3.RADIO LINK RECONFIGURATION READY NBAP NBAP RRC 4:RADIO BEARER RELEASE RRC 5.RADIO LINK RECONFIGURATION COMMIT NBAP NBAP
Apply new transport format set DCCH 6.DCCH : RADIO BEARER RELEASE COMPLETE
RRC
RRC
7.ALCAP Iub Data Transport Bearer Release
8. ALCAP Iu Data TransportBearer Release
9. IU RELEASE COMPLETE RANAP RANAP
1. The CN sends an IU RELEASE COMMAND message the SRNC. 2. The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB to request the NodeB to prepare for the releasing of the DCH carrying the RAB. 3. The NodeB sends a RADIO LINK RECONFIGURATION READY message to the SRNC to notify the SRNC that the release preparations are complete. 4. The SRNC sends a RADIO BEARER RELEASE message to the UE to start the bearer release flow. 5. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. 6. The SRNC receives a RADIO BEARER RELEASE COMPLETE message from the UE. 7. The RNC releases the data transport bearer on Iub interface. 8. The SRNC uses ALCAP. In case of AAL2 bearer, the SRNC sends an AAL2 release message to start releasing the Iu data transport bearer between the SRNC and CN. 9. The SRNC sends an IU RELEASE COMPLETE message the CN.
66
RRC Connection Release Flow

Overview
After the RAB is released, the SRNC determines whether any Iu signaling connection borne by the same RRC exists in the system. If all the Iu signaling connections corresponding to the UE are released, the RRC connection is released. To release an RRC connection is to release the signaling links between the UE and UTRAN and all the radio bearers. Through the RRC connection release flow, all the signaling connections related to the UE are released on the radio interface. Based on the resource consumption by the RRC connection, there are two types of connection release: release of an RRC connection established on a dedicated channel and release of an RRC connection established on a common channel. An RRC connection can be released only when it is in the CELL_DCH or CELL_FACH state. If the current RRC connection is in the CELL_PCH or URA_PCH state, the UTRAN initiates paging to transition the UE state to CELL_FACH before releasing the RRC connection. Based on actual conditions, the RNC sends an RRC CONNECTION RELEASE message in UM RLC mode on the downlink DCCH or CCCH. If the DCCH is available during the RRC connection release, the UTRAN sends an RRC CONNECTION RELEASE message through the downlink DCCH. Otherwise, the UTRAN sends an RRC CONNECTION RELEASE message through the downlink CCCH.
Releasing an RRC Connection Established on a Special Channel

The signaling flow of RRC Connection Release Set up on Special Channels is shown in the following figure.
67
FIGURE 44 CHANNEL)
RRC CONNECTION RELE ASE (S PECIAL
UE
NodeB
1.RRC CONNECTION RELEASE
SRNC
RRC 2.RRC CONNECTION RELEASE COMPLETE RRC 3. RADIO LINK DELETION REQUEST NBAP 4. RADIO LINK DELETION RESPONSE NBAP
RRC
RRC
NBAP
NBAP
5.ALCAP Release
Description of signaling flow: 1. The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH. The SRNC may sends the message for several times to ensure that the UE receives the message. 2. The UE returns an RRC CONNECTION RELEASE COMPLETE message to the SRNC. 3. The SRNC sends a RADIO LINK DELETION REQUEST message to NodeB to delete the radio link resources in NodeB. 4. When the resources in the NodeB are deleted, NodeB returns a RADIO LINK DELETION RESPONSE message to the SRNC. 5. The RNC uses ALCAP to initiate the releasing of the user plane transport bearer on Iub interface.The RRC connection release flow is complete.
Releasing an RRC Connection Established on a Common Channel

The signaling flow of Releasing an RRC Connection Established on a Common Channel is shown in the following figure.
68
FIGURE 45
RRC CONNECTION RELEASE (P UBLIC CHANNEL)
UE
NodeB
RRC CONNECTION RELEASE
SRNC
RRC
RRC
The SRNC sends an RRC CONNECTION RELEASE message through the CCCH to the UE to initiate the RRC connection release flow, and the UE releases the resources. When an RRC connection established on the common channel is released, no RRC CONNECTION RELEASE COMPLETE message is sent. In addition, because cell common resources are used, only the UE needs to be released directly and there is no need to release NodeB resources and data transport bearer. Description
The UTRAN may send the RRC CONNECTION RELEASE message for several times to ensure that the UE receives the message correctly. The RRC SN values of these messages are the same. The number of message retransfers and transfer interval are controlled by the network.
69
Appendix
Basic Signaling Flow
CS Registration and PS Attacted Flow

CS Registration
UE (1)RRC Connetcion Request (2)RRC Connection Setup RNC CN
(3)RRC Connection Complete
(4) Initial Direct Transfer (Location Update) (5) CR: Initial UE Message CC (6) Direct Transfer (Location Update Accept) (7) Downlink Direct Transfer (Location Update Accept)
(8) Iu Release Command (9) Iu Release Complete
(10) RRC Connection Release
(11) RRC Connection Release Complete
Flow description: 1. The UE sends the RRC Connection Request message through the uplink CCCH, requesting for setting up an RRC connection. 2. The SRNC sends the RRC Connection Setup message to the UE through the downlink CCCH.
71
3. The UE sends the RRC Connection Setup Complete message to the SRNC through the uplink DCCH. At this time, the RRC connection setup process ends. 4. For RNC, the signaling interacted between the UE and the CN is a direct transfer message. When the RNC receives the first direct transfer message, that is, Initial Direct Transfer, it sets up the signaling connection with the CN on SCCP. The UE sends the Initial Direct Transfer message to the RNC. 5. After receiving the initial direct transfer message from the UE, the RNC sends the CR SCCP connection request to the CN through the Iu interface, with data as Initial UE Message sent from the RNC to the CN. This message contains the message contents sent from the UE to the CN. 6. If the CN is ready to accept the CR, it returns the CC SCCP connection confirmation to the RNC, confirming successful signaling connection setup. 7. After the RNC is confirmed that the signaling connection is set up successfully, it sends the downlink direct transfer message to the UE. 8. The CN sends the Iu Release Command message to the RNC, asking it to release the Iu connection of the CS domain. 9. The RNC sends the Iu Release Complete message to the CN, and makes the ALCAP to originate the release of Iu interface user plane bearer. 10. The RNC sends the RRC Connection Release message to the UE, asking for the RRC connection release. 11. After the UE releases the RRC connection, it sends the RRC Connection Release Complete message to the RNC.
72
Appendix A Basic Signaling Flow
PS Domain Attaching
UE
NodeB
RNC
CN
(1)UL-CCCH:RRC Connection Request (2)C_NBAP:Rdaio Link Setup Request (3)C_NBAP:Radio Link Setup Response (4)ALCAP:ERQ (5)ALCAP:ECF (6)DCCH_FP:Downlink SYNC (7)DCCH_FP:Uplink SYNC (8)DL_CCCH:RRC Connection Setup (9)UL_DCCH:RRC Connection Setup Complete (10)D_NBAP:Radio Link Restore Indication (11)UL_DCCH:Initial Direct Transfer (Attach Req) (12)Initial UE Message (Attach Req) (13)Direct Transfer (14)DL_DCCH:Downlink Direct Transfer (Attach Accept) (Attach Accept)
Flow descriptions: 1. The UE sends the RRC Connection Request message through the uplink CCCH, requesting for setting up an RRC connection. 2. Based on the reason for the RRC CR and system resource status, the SRNC decides to set up a UE on the dedicated channel, and allocates the RNT1 and L1 and L2 resources. And then it sends the Radio Link Setup Request message to NodeB, asking the NodeB to allocate the specified radio link resources required for RRC connection. 3. At the end of successful resource preparation, NodeB returns Radio Link Setup Response to the SRNC. 4. With the ALCAP, the SRNC originates the setup of Iu interface user plane transport bearer. 5. At the end of successful terrestrial bearer setup, NodeB returns the ECF to the SRNC. 6. The RNC sends the downlink FP synchronization message to NodeB. 7. The NC sends the uplink FP synchronization message to NodeB. 8. The SRNC sends the RRC Connection Setup message to the UE through the downlink CCCH.
73
9. The UE sends the RRC Connection Setup Complete message to the SRNC through the uplink DCCH. At this time, the RRC connection setup process ends. 10. At the end of successful synchronization between the RNC and NodeB, NodeB returns Radio Link Restore Indication to the RNC. 11. For the RNC, the signaling interacted between the UE and the CN is a direct transfer message. When the RNC receives the first direct transfer message, that is, Initial Direct Transfer, it sets up the signaling connection with the CN on SCCP. The UE sends the Initial Direct Transfer message to the RNC. 12.After receiving the initial direct transfer message from the UE, the RNC sends the CR SCCP connection request to the CN through the Iu interface, with data as Initial UE Message sent from the RNC to the CN. This message contains the message contents sent from the UE to the CN. 13. If the CN is ready to accept the CR, it returns the CC SCCP connection confirmation to the RNC, confirming successful signaling connection setup. 14. After the RNC is confirmed that the signaling connection is set up successfully, it sends the downlink direct transfer message to the UE. The Layer-3 message is ATTACH ACCEPT
74
Call Flow
Calling Flow of CS Domain
UE
NodeB
RNC
CN
(1)UL-CCCH:RRC Connection Request(originatingConversationalCall) (2)C_NBAP:Rdaio Link Setup Request (3)C_NBAP:Radio Link Setup Response (4)ALCAP:ERQ (5)ALCAP:ECF (6)DL_CCCH:RRC Connection Setup (7)UL_DCCH:RRC Connection Setup Complete (8)D_NBAP:Radio Link Restore Indication (9)UL_DCCH:Initial Direct Transfer (CM Service Request) (10)Initial UE Message (CM Service Request) (11)Direct Transfer (12)DL_DCCH:Downlink Direct Transfer (CM Service Accept) (13)UL_DCCH:Uplink Direct Transfer (Call Setup) (15)D_NBAP:Radio Link Reconfiguration Prepare (16)D:NBAP Radio Link Reconfiguration Ready (17)ALCAP:ERQ (18)ALCAP:ECF (19)D_NBAP:Radio Link Reconfiguration Commit (20)DL_DCCH:Radio Bearer Setup (21)UL_DCCH:Radio Bearer Setup Complete (22)RAB Assignment Response (23)DL_DCCH:Downlink Direct Transfer (Call Proceeding) (24)DL_DCCH:Downlink Direct Transfer (Alerting) (25)DL_DCCH:Downlink Direct Transfer (Connect) (26)UL_DCCH:Uplink Direct Transfer (Connect Acknowledge) Downlink Direct Transfer (Connect) (14)RAB Assginment Request (Establishment) (CM Service Accept)
(27)Direct Transfer (Connect Acknowledge)
Flow descriptions:
The UE sends the RRC Connection Request message through the uplink CCCH, requesting for setting up an RRC connection. Based on the reason for the RRC CR and system resource status, the SRNC decides to set up a UE on the dedicated channel, and allocates RNT1 and L1 and L2 resources. And then it sends the Radio Link Setup Request message to NodeB, asking the NodeB to allocate the specified radio link resources required for RRC connection.
75
At the end of successful resource preparation, NodeB returns Radio Link Setup Response to the SRNC. With the ALCAP, the SRNC originates the setup of Iu interface user plane transport bearer. At the end of successful terrestrial bearer setup, NodeB returns the ECF to the SRNC. The SRNC sends the RRC Connection Setup message to the UE through the downlink CCCH. The UE sends the RRC Connection Setup Complete message to the SRNC through the uplink DCCH. At this time, the RRC connection setup process ends. At the end of successful synchronization between RNC and NodeB, NodeB returns Radio Link Restore Indication to the RNC. For RNC, the signaling interacted between the UE and the CN is direct transfer message. When the RNC receives the first direct transfer message, that is, Initial Direct Transfer, it sets up the signaling connection with the CN on the SCCP. The UE sends the Initial Direct Transfer message to the RNC. After receiving the initial direct transfer message from the UE, the RNC sends the CR SCCP connection request to the CN through the Iu interface, with data as Initial UE Message sent from the RNC to the CN. This message contains the message contents sent from the UE to the CN. If the CN is ready to accept the CR, it returns the CC SCCP connection confirmation to the RNC, confirming successful signaling connection setup. After the RNC is confirmed that the signaling connection is set up successfully, it sends the downlink direct transfer message to the UE. The Layer-3 message is CM SERVICE ACCEPT. The UE sends the uplink direct transfer message, with Layer-3 message as CALL SETUP. After receiving the CALL SETUP Layer-3 message, the CN sends the RAB assignment request to the UTRAN, asking the UTRAN to set up the RAB. After receiving the RAB setup request, the SRNC maps the QoS parameter of the RAB into AAL2 link feature parameter and radio resource feature parameter. Based on the AAL2 link feature parameter, the ALCAP of the Iu interface originates user plane transport bearer setup of the Iu interface. At the end of successful terrestrial bearer setup, the SRNC sends the Radio Link Reconfiguration prepare message to NodeB, asking the subordinate NodeB to prepare for adding one or multiple dedicated transport channels DCH on the existing radio link, for bearer RAB.
76
NodeB allocates the corresponding resources and sends the Radio Link Reconfiguration Ready message to the SRNC, indicating the completed radio link reconfiguration preparation. The ALCAP of the Iub interface in the SRNC originates the setup of Iub interface user plane transport bearer. At the end of successful terrestrial bearer setup, NodeB returns ECF to the SRNC. SRNC sends the Radio Link Reconfiguration Commit message to the subordinate NodeB. SRNC sends the Radio Bearer Setup message to the UE, asking for RB setup of RRC protocol. After executing RB setup, the UE sends the Radio Bearer Setup Complete message to the SRNC. After receiving this message, the SRNC returns the Radio Access Bearer Assignment Response to the CN. At this time, the RAB setup flow ends. The CN sends the Call Proceeding Layer-3 message to the UE. The CN sends the Altering Layer-3 message to the UE. Upon hook-off, the CN sends the Connect Layer-3 message to the UE. The UE sends the Connect Ack Layer-3 message to the CN.
77
Called Flow of CS Domain

UE NodeB RNC 1Paging CN
2)DL_CCCHPaging Type 1 (3)UL-CCCH:RRC Connection Request (4)C_NBAP:Rdaio Link Setup Request (5)C_NBAP:Radio Link Setup Response (6)ALCAP:ERQ (7)ALCAP:ECF (8)DCCH_FP:Downlink SYNC (9)DCCH_FP:Uplink SYNC (10)DL_CCCH:RRC Connection Setup (11)UL_DCCH:RRC Connection Setup Complete (12)D_NBAP:Radio Link Restore Indication (13)UL_DCCH:Initial Direct Transfer Paging Response 16DL_DCCH:Downlink Direct Transfer Call Setup 17DL_DCCH:Uplink Direct Transfer Call Confirmed)
(14)Initial UE Message ( Paging Response) (15)Direct Transfer Call Setup
(18)RAB Assignment Request (Establish)
(18)D_NBAP:Radio Link Reconfiguration Prepare (19)D:NBAP Radio Link Reconfiguration Ready (20)ALCAP:ERQ (21)ALCAP:ECF (22)DTCH_FP:Downlink SYNC (23)DTCH_FP:Uplink SYNC
(24)D_NBAP:Radio Link Reconfiguration Commit (25)DL_DCCH:Radio Bearer Setup (26)UL_DCCH:Radio Bearer Setup Complete (27)RAB Assignment Response (28)UL_DCCH:Downlink Direct Transfer (Alerting) (30)UL_DCCH:Downlink Direct Transfer (Connect) (33)DL_DCCH:Uplink Direct Transfer (Connect Acknowledge) (29)Direct Transfer (Alerting) (31)Direct Transfer (Connect) (32)Direct Transfer (Connect Acknowledge)
Flow description:
78
The difference between calling flow and called flow is: The CN originates the call message in the called flow. The other steps are omitted here.
PDP Activation of PS Domain

UE NodeB (1)UL_DCCH:Uplink Direct Transfer (ACT. PDP Context Req) RNC CN
(2)Direct Transfer (ACT. PDP Context Req) (3)RAB Assginment Request
(Establishment) (4)D_NBAP:Radio Link Reconfiguration Prepare (5)D:NBAP Radio Link Reconfiguration Ready (6)ALCAP-ERQ (7)ALCAP-ECF (8)DTCH_FP:Downlink SYNC (9)DCCH_FP:Uplink SYNC (10)D_NBAP:Radio Link Reconfiguration Commit (11)DL_DCCH:Radio Bearer Setup (12)UL_DCCH:Radio Bearer Setup Complete (13)RAB Assignment Response (14)Direct Transfer (15)DL_DCCH:Downlink Direct Transfer (ACT. PDP Context Accept) (ACT. PDP Context Accept)
Flow descriptions:
The UE sends the uplink direct transfer message to the RNC, with Layer-3 message as PDP Context Request. The RNC sends the uplink direct transfer message to the CN, with Layer-3 message as PDP Context Request. After receiving the PDP Context Request Layer-3 message, the CN sends the RAB assignment request to the UTRAN, asking UTRAN to set up RAB. After receiving the RAB setup request, the SRNC maps the QoS parameter of RAB into AAL2 link feature parameter and radio resource feature parameter. Based on the AAL2 link feature parameter, the ALCAP of the Iu interface originates user plane transport bearer setup of the Iu interface. At the end of successful terrestrial bearer setup, the SRNC sends the Radio Link Reconfiguration prepare message to NodeB, asking the subordinate NodeB to prepare for adding one or multiple dedicated transport channels DCH on the existing radio link, for the bearer RAB.
79
NodeB allocates the corresponding resources and sends the Radio Link Reconfiguration Ready message to the SRNC, indicating the completed radio link reconfiguration preparation. The ALCAP of the Iub interface in the SRNC originates the setup of Iub interface user plane transport bearer. At the end of successful terrestrial bearer setup, NodeB returns the ECF to the SRNC. The RNC sends the downlink FP synchronization message to NodeB. The RNC sends the uplink FP synchronization message to NodeB. The SRNC sends the Radio Link Reconfiguration Commit message to the subordinate NodeB. The SRNC sends the Radio Bearer Setup message to the UE, asking for RB setup of RRC protocol. After executing RB setup, the UE sends the Radio Bearer Setup Complete message to the SRNC. After receiving this message, the SRNC returns the Radio Access Bearer Assignment Response to the CN. At this time, the RAB setup flow ends. The CN sends the PDP Context Accept Layer-3 message to the RNC. The RNC transfers the PDP Context Accept Layer-3 message to the UE.
80
Call of PS Domain
UE NodeB RNC CN (1)UL-CCCH:RRC Connection Request (2)C_NBAP:Rdaio Link Setup Request (3)C_NBAP:Radio Link Setup Response (4)ALCAP:ERQ (5)ALCAP:ECF (6)DCCH_FP:Downlink SYNC (7)DCCH_FP:Uplink SYNC (8)DL_CCCH:RRC Connection Setup (9)UL_DCCH:RRC Connection Setup Complete (10)D_NBAP:Radio Link Restore Indication (11)UL_DCCH:Initial Direct Transfer (12)Initial UE Message (13)Direct Transfer (14)Direct Transfer (16)D_NBAP:Radio Link Reconfiguration Prepare (17)D:NBAP Radio Link Reconfiguration Ready (18)ALCAP-ERQ (19)ALCAP-ECF (20)DTCH_FP:Downlink SYNC (21)DCCH_FP:Uplink SYNC (22)D_NBAP:Radio Link Reconfiguration Commit (23)DL_DCCH:Radio Bearer Setup (24)UL_DCCH:Radio Bearer Setup Complete (25)RAB Assignment Response (15)RAB Assginment Request (Establishment)
Flow description:
The UE sends the uplink direct transfer message to the RNC, with Layer-3 message as PDP Context Request. The RNC sends the uplink direct transfer message to the CN, with Layer-3 message as PDP Context Request. After receiving the PDP Context Request Layer-3 message, the CN sends the RAB assignment request to the UTRAN, asking UTRAN to set up RAB. After receiving the RAB setup request, the SRNC maps the QoS parameter of RAB into AAL2 link feature parameter and radio resource feature parameter. Based on the AAL2 link feature parameter, the ALCAP of the Iu interface originates user plane transport bearer setup of the Iu interface. At the end of successful terrestrial bearer setup, the SRNC sends the Radio Link Reconfiguration prepare message to NodeB, asking the subordinate NodeB to prepare for adding one or multiple dedicated transport channels DCH on the existing radio link, for bearer RAB. NodeB allocates the corresponding resources and sends the Radio Link Reconfiguration Ready message to the SRNC,
81
indicating the preparation.
completed
radio
link
reconfiguration
The ALCAP of the Iub interface in the SRNC originates the setup of Iub interface user plane transport bearer. At the end of successful terrestrial bearer setup, NodeB returns ECF to the SRNC. The RNC sends the downlink FP synchronization message to NodeB. The RNC sends the uplink FP synchronization message to NodeB. The SRNC sends the Radio Link Reconfiguration Commit message to the subordinate NodeB. For RNC, the signaling interacted between the UE and the CN is direct transfer message. When the RNC receives the first direct transfer message, that is, Initial Direct Transfer, it sets up the signaling connection with CN on SCCP. UE sends the Initial Direct Transfer message to the RNC. After receiving the initial direct transfer message from the UE, the RNC sends the CR SCCP connection request to the CN through the Iu interface, with data as Initial UE Message sent from the RNC to the CN. This message contains the message contents sent from the UE to the CN. If the CN is ready to accept the CR, it returns the CC SCCP connection confirmation to the RNC, confirming successful signaling connection setup. After the RNC is confirmed that the signaling connection is set up successfully, it sends the downlink direct transfer message to the UE. The CN sends the RAB assignment request to the UTRAN, asking the UTRAN to set up the RAB. After receiving the RAB setup request, the SRNC maps the QoS parameter of RAB into AAL2 link feature parameter and radio resource feature parameter. Based on the AAL2 link feature parameter, the ALCAP of the Iu interface originates user plane transport bearer setup of the Iu interface. At the end of successful terrestrial bearer setup, the SRNC sends the Radio Link Reconfiguration prepare message to NodeB, asking the subordinate NodeB to prepare for adding one or multiple dedicated transport channels DCH on the existing radio link, for bearer RAB. NodeB allocates the corresponding resources and sends the Radio Link Reconfiguration Ready message to the SRNC, indicating the completed radio link reconfiguration preparation. The ALCAP of the Iub interface in the SRNC originates the setup of Iub interface user plane transport bearer.
82
At the end of successful terrestrial bearer setup, NodeB returns the ECF to the SRNC. The RNC sends the downlink FP synchronization message to NodeB. The RNC sends the uplink FP synchronization message to NodeB. The SRNC sends the Radio Link Reconfiguration Commit message to the subordinate NodeB. The SRNC sends the Radio Bearer Setup message to the UE, asking for the RB setup of RRC protocol. After executing the RB setup, the UE sends the Radio Bearer Setup Complete message to the SRNC. After receiving this message, the SRNC returns the Radio Access Bearer Assignment Response to the CN. At this time, the RAB setup flow ends.
83
Service Release Flow

Release of CS Domain
UE NodeB (1)UL_DCCH:Uplink Direct Transfer 2Direct Transfer (Disconnect) (4)DL_DCCH:Downlink Direct Transfer (Release) (5)UL_DCCHUplink Direct Transfer (Release Complete) (6)Direct Transfer (Release Complete) (7)Iu Release Command (8)Iu Release Complete (9)DL_DCCH:RRC Connection Release (10)UL_DCCH:RRC Connection Release Complete (11)D_NBAP:Radio Link Deletion Request (12)D_NBAP:Radio Link Deletion Response (Disconnect) 3Direct Transfer (Release) RNC CN
(13)ALCAP:REL(DTCH) (14)ALCAP:RLC(DTCH) (15)ALCAP:REL(DCCH) (16)ALCAP:RLC(DCCH)
Flow description:
Upon hook-on, the UE sends the direct transfer message to the RNC, with Layer-3 message as DISCONNECT, for asking the release of the connection with a CN domain. After receiving the direct transfer message from the UE, the RNC directly transfers this message to the CN. After receiving this message, the CN sends the downlink direct transfer message, with the Layer-3 message as RELEASE. The RNC transparently sends the downlink direct transfer message to the UE. The MS sends the direct transfer message to the RNC, with the Layer-3 message as RELEASE COMPLETE. If the
84
communication channel is not required any more, the channel release flow need be executed.

The RNC sends the uplink direct transfer message to the CN. The CN sends the IU RELEASE COMMAND message to the RNC, asking for Iu connection release. The RNC sends the IU RELEASE COMPLETE message to the CN, indicating RNC being released. The RNC sends the RRC CONNECTION RELEASE message to the UE, asking for the RRC connection release. UE sends the RRC message to the RNC. CONNECTION RELEASE COMPLETE
RNC sends the RADIO LINK DELETION REQUEST to NodeB, asking for release of radio link connection. NodeB sends the RADIO LINK DELETION RESPONSE to the RNC. The RNC releases the access control and code resources, originates the terrestrial resource release, and sends the ALCAP RELEASE request to NodeB, asking for terrestrial resource release. NodeB sends the ALCAP RELEASE CONFIRM message to the RNC, indicating successful terrestrial bearer release. If any terrestrial bearer still exists, the RNC continues to send the ALCAP RELEASE request to NodeB, asking for terrestrial bearer release. NodeB sends the ALCAP RELEASE CONFIRM message to the RNC, indicating successful terrestrial bearer release. If all the terrestrial bearers are released, this flow ends.
85
Flow of CS Domain Passive Release

UE NodeB RNC CN
(1)Direct Transfer (2)DL_DCCH: Downlink Direct Transfer

(Disconnect) (Disconnect)
(3)UL_DCCH: Uplink Direct Transfer

(Release)
(4)Direct Transfer
(Release) (5)Direct Transfer (Release Complete) (7)Iu Release Command (8)Iu Release Complete
(6)DL_DCCH: Downlink Direct Transfer

(Release Complete)
(9)DL_DCCH:RRC Connection Release (10)UL_DCCH:RRC Connection Release Complete (11)D_NBAP:Radio Link Deletion Request (12)D_NBAP:Radio Link Deletion Response
(13)ALCAP:REL(DTCH) (14)ALCAP:RLC(DTCH) (15)ALCAP:REL(DCCH) (16)ALCAP:RLC(DCCH)
Flow description: The difference between calling flow and called flow is: CN originates the Disconnect message in the called flow. The other steps are omitted here.
86
PDP Deactivation of PS Domain

UE NodeB (1)UL_DCCH:Uplink Direct Transfer RNC CN
(DEACTIVE PDP Contex Request)
2Direct Transfer
(DEACTIVE PDP Contex Request) (3) RAB Assignment Request

(4)DL_DCCH:RB Release Request (Release)
(5)UL_DCCH:RB Release Complete

(6)D_NBAP: Radio Link Reconfiguration Prepare (7)D_NBAP: Radio Link Reconfiguration Ready (8)ALCAP: REL (9)ALCAP: RLC (10)DTCH_FP: Downlink Synchronization (11)DTCH_FP: Uplink Synchronization (12)D_NBAP: Radio Link Reconfiguration Commit (13)RAB Assignment Response (14) Direct Transfer (15)DL_DCCH:Downlink Direct Transfer (Deactive PDP Context Accept) (Deactive PDP Context Accept)
Flow description:
The UE sends the uplink direct transfer message to the RNC, with Layer-3 message as DEACTIVATE PDP Context Request. After receiving the direct transfer message from the UE, the RNC directly transfers this message to the CN. After receiving this message, the CN sends the RAB Assignment Request to the RNC, with the RAB Id for release. After receiving this message, the RNC sends RB Release Request to the UE. The UE sends the RB Release COMPLETE message to the RNC. It also releases the resources occupied by the UE. If there are other services, the RNC sends RADIO LINK RECONFIGURATION REQUEST to NodeB. NodeB sends the RADIO LINK RECONFIGURATION READY message to the RNC.
87
The RNC releases the access control and code resources, originates the terrestrial resource release, and sends the ALCAP RELEASE request to NodeB, asking for terrestrial resource release. NodeB sends the ALCAP RELEASE CONFIRM message to the RNC, indicating successful terrestrial bearer release. The RNC sends the downlink FP synchronization message to NodeB. The RNC sends the uplink FP synchronization message to NodeB. The RNC sends the Radio Link Reconfiguration Commit message to the subordinate NodeB. The RNC returns RAB Assignment Response to the CN. The CN sends the downlink direct transfer message to the RNC, with Layer-3 message as DEACTIVATE PDP Context Accept. After receiving the direct transfer message from CN, the RNC directly transfers this message to the UE.
88
Detach of PS Domain
UE NodeB (1)UL_DCCH:Uplink Direct Transfer RNC CN
(Detach Request)
2Direct Transfer
(Detach Request) (3)Detach Accept

(4)DL_DCCH: Downlink Direct Transfer
(Detach Accept)
(5) IU Release Command (6) IU Release Complete
(7)DL_DCCH: RRC Connection Release (8)UL_DCCH: RRC Connection Release Complete (9)D_NBAP: Radio Link Delete Request (10)D_NBAP: Radio Link Delete Response (11)ALCAP: REL (DTCH) (12)ALCAP: RLC (DTCH) (13)ALCAP: REL (DCCH) (14)ALCAP: RLC (DCCH)
Flow description:
Upon hook-on, the UE sends the direct transfer message to the RNC, with Layer-3 message as DETACH, for asking the release of the connection with CN domain. After receiving the direct transfer message from the UE, the RNC directly transfers this message to the CN. After receiving this message, the CN sends the downlink direct transfer message, with the Layer-3 message as DETACH ACCEPT. The RNC transparently sends the downlink direct transfer message to the UE. The CN sends the IU RELEASE COMMAND message to the RNC, asking for Iu connection release. The RNC sends the IU RELEASE COMPLETE message to the CN, indicating RNC being released. The RNC sends the RRC CONNECTION RELEASE message to the UE, asking for RRC connection release.
89
The UE sends the RRC CONNECTION RELEASE COMPLETE message to the RNC. The RNC sends the RADIO LINK DELETION REQUEST to NodeB, asking for release of radio link connection. NodeB sends the RADIO LINK DELETION RESPONSE to the RNC. The RNC releases the access control and code resources, originates the terrestrial resource release, and sends the ALCAP RELEASE request to NodeB, asking for terrestrial resource release. NodeB sends the ALCAP RELEASE CONFIRM message to the RNC, indicating successful terrestrial bearer release. If any terrestrial bearer still exists, the RNC continues to send the ALCAP RELEASE request to NodeB, asking for terrestrial bearer release. NodeB sends the ALCAP RELEASE CONFIRM message to the RNC, indicating successful terrestrial bearer release. If all the terrestrial bearers are released, this flow ends.
90
Appendix
Basic Call Code Flow
CS Registration Code Flow

Mobile registration flow on the UE side:
Mobile registration flow on the RNC side:
91
The mobile registration scrabbed on the RNC side has not initiated the position renewal as there is no change in the position of the mobile around the time when it powers off.
Calling Code Flow in CS Domain

Flow of calling initiating call in the CS domain on the UE side:
Calling flow in the CS domain on the RNC side:
92
Appendix B Basic Call Code Flow
The 40th item downlink direct transfer is to send the Alerting signaling to the UE on the network side. The 42nd item downlink direct transfer is to send the Connect signaling to the UE on the network side.
CS Domain Taking Initiative to Release Code Flow

Initiative to release flow in the CS domain on the UE side:
93
Initiative to release flow in the CS domain on the RNC side:
CS Domain Called Code Flow

Called initiating call flow in the CS domain on the UE side
Called setup flow in the CS domain on the RNC side:
94
CS Domain Passive Release Code Flow

Passive release flow in the CS domain on the UE side:
95
Passive release flow in the CS domain on the RNC side:
PS Domain Attached Code Flow

Attatched Flow of the PS domain on the RNC side:
96
PS Domain Deattached Code Flow
PDP Activiated Code Flow in PS Domain

PDP Activiated Flow in the PS domain on the UE side:
97
When in the UE side the PDP activiating request is enabled and as the radio environment quality is not good, the UE has not received the RRC Connection Setup message after initiating the RRC Connection Request. After two seconds, the UE resends the RRC Connection Request message. PDP activiating flow in the PS domain on the RNC side:
PDP Deactiviating Code Flow in PS Domain

PDP decativiating flow in the PS domain on the UE side:
98
PDP decativiating flow in the PS domain on the RNC side:
Position Renewal Code Flow

Position Renewal Flow on the UE side:
CS Called Concurrent Code Flow in PS Background

CS Called Concurrent Code Flow in PS Background on the UE side:
99
When the PS service concurrents the called CS, the RNC issues the paging type 2 message to the UE and starts to set up the CS session.
100

Signaling Flow of Advanced WCDMA Radio Interfaces

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Signaling Flow of Advanced WCDMA Radio Interfaces

Încărcat de

Drepturi de autor:

Formate disponibile

Signaling Flow of Advanced WCDMA Radio Interfaces

Basic Concept .................................................................. 4

Chapter 2 .......................................................................13 Network Selection Flow ................................................13

Cell Selection and Reselection ......................................... 15

Chapter 3 .......................................................................19 Handover Flow in the System .......................................19

Hard Handover .............................................................. 24

Inter-Systems Handover ................................................. 27

Forward Handover ......................................................... 37

Chapter 4 .......................................................................41 Call Service Flow ...........................................................41

RRC Connection Establishment Flow ................................. 44

Direct Transfer Message Flow .......................................... 48

UE Capability Information Flow ........................................ 51

RAB Establishment Flow ................................................. 53

Chapter 5 .......................................................................61 Service Release Flow.....................................................61

Appendix A ....................................................................71 Basic Signaling Flow......................................................71

Call Flow ....................................................................... 75

Service Release Flow ...................................................... 84

Appendix B ....................................................................91 Basic Call Code Flow......................................................91

Basic Signaling Flow

Confidential and Proprietary Information of ZTE CORPORATION