ZXWR RNC V3!07!300 Radio Network Controller Signaling Description

ZXWR RNC
Radio Network Controller

Signaling Description
RNC Version 3.07.300
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

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History
Date Revision No. Serial No. Reason for Issue
Feb. 28, 2009 R1.0 sjzl20092915
First edition (ZXWR RNC V3.07.300i
+ OMMR V3.17.300h +
NetnumenM31 V3.10.410d)

ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
ZXWR RNC (V3.07.300) Radio Network Controller Signaling Description
Product Version RNCV3.07.300
Document Revision
Number
R1.0
Serial No. sjzl20082915
Equipment
Installation Date

Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Your evaluation
of this
documentation
I ntelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Your
suggestions for
improvement of
this
documentation
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Add more examples Add more/better quick reference aids
Add more detail Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail

This page is intentionally blank.
Contents

About This Manual ............................................................ i
Purpose................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge.............................................. i
What Is in This Manual ........................................................... i
Conventions......................................................................... ii
How to Get in Touch............................................................. iii
Chapter 1.......................................................................... 5
Basic Signaling flow......................................................... 5
Definition of Signaling............................................................ 5
RRC Connection Setup Flow.................................................... 5
NAS Signaling Connection Establishment .................................. 8
RRC Connection Release ........................................................ 9
Call Flow............................................................................ 11
Chapter 2........................................................................ 21
Measurement Procedures.............................................. 21
Measurement ............................................................... 21
Measurement Control Types ................................................. 21
Measurement Procedure................................................. 23
Measurement Control .......................................................... 23
Measurement Report ........................................................... 24
Common Measurement .................................................. 24
Common Measurement Types ............................................... 24
Common Measurement Initiation........................................... 25
Dedicated Measurement................................................. 26
Dedicated Measurement Types.............................................. 27
Dedicated Measurement Initiation ......................................... 27
Dedicated Measurement Termination ..................................... 31
Dedicated Measurement Failure ............................................ 32

Chapter 3........................................................................33
Handover Procedures ....................................................33
Soft Handover .............................................................. 33
Radio Link Addition (Branch Addition).....................................34
Radio Link Deletion (Branch Deletion) ....................................36
Hard Handover ............................................................. 37
Hard Handover ...................................................................37
SRNS Relocation .................................................................38
CS Inter RAT Hard Handover.................................................41
PS Inter RAT Data Handover........................................... 45
GPRS to UMTS Cell Reselection..............................................45
UMTS to GPRS Cell Reselection..............................................46
Chapter 4........................................................................49
MBMS Specific Procedures.............................................49
MBMS Service Activation ......................................................49
MBMS Session Start.............................................................51
MBMS UE Mobility from a PTP to PTM cell ................................54
MBMS UE Mobility from PTM cell to PTP cell .............................56
MBMS Session Stop and Service Termination...........................58
RAU during MBMS Session....................................................60
Chapter 5........................................................................63
High Speed Packet Access.............................................63
Physical Shared Channel Reconfiguration ................................63
E-DCH and HS-DSCH Resources ............................................64
HSPA Serving Cell Change ....................................................65
A p p e n d i x A ............................................................67
Abbreviations.................................................................61H67
A p p e n d i x B ............................................................62H71
Figures............................................................................ 63H71
Tables.............................................................................64H73
Index.............................................................................. 65H75

Confidential and Proprietary Information of ZTE CORPORATION i
About This Manual

Purpose
This manual describes about the internal system signaling in
ZXWR RNC Radio Network Controller.
Intended Audience
This manual is intended for engineers who perform operation
activities on the ZXWR RNC Radio Network Controller.
Prerequisite Skill and Knowledge
To use this manual effectively, users should have a good
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXWR system and its various components
System interfaces between UE, Node B, RNC and CN.
Local operating procedures
What Is in This Manual
This manual contains the following chapters:
TAB L E 1 CHA PTER SUMMARY
Chapter Summary
Chapter 1, Basic
Signaling flow
Introduces RNC radio signaling. It also
defines NAS and RRC connection setup
and Call Flow.
Chapter 2,
Measurement
Procedure
Describes about the measurement,
measurement control, and common and
dedicated measurement procedures.
Chapter 3, Handover
Procedures
Explains soft and hard handover signaling
procedures.

ZXWR RNC Signaling Description Manual

ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter Summary
Chapter 4, MBMS
Specific Procedures
Describes about MBMS session
establishment, mobility and termination.
Chapter 5, High Speed
Packet Access
Describes about structure of HSPA and
explains the channel, power, and code
configuration of HSPA.
Appendix B,
Abbreviations
List of all abbreviations used in the manual
Appendix C, Figures
and Tables
List of all figures and tables used in the
manual
Conventions
ZTE documents employ the following typographical conventions.
TAB L E 2 TYPOGRAPHI CAL CONVENTI ONS
Typeface Meaning
Italics References to other Manuals and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Const ant wi dt h
Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited
by it.

Note: Provides additional information about a
certain topic.

Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.

Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.

TAB L E 3 MOUSE OPERATI ON CONVENTI ONS
Typeface Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
Typographical
Conventions
Mouse
Operation
Conventions

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii
Typeface Meaning
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.

How to Get in Touch
The following sections provide information on how to obtain
support for the documentation and the software.
If you have problems, questions, comments, or suggestions
regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
Customer
Support
Documentation
Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 5
Ch a p t e r 1
Basic Signaling flow

Definition of Signaling
The purpose of a communication network is to transfer
information including voice and non-voice information. Therefore,
the signaling is the information that needs to be exchanged
between the devices to enable network devices to coordinate
with each other. In other words, signaling is the language used
between the devices for exchanging their status and intentions.
As any other language, signaling also observe rules set by
related organizations, namely, signaling protocol or signaling
mode.
RRC Connection Setup Flow
According to the different reason of RRC connection set up, RRC
connection can be established in common channel or dedicated
channel. RRC connection establishes in the following two ways:
RRC connection establishment in DCH
RRC connection establishment in common transport channel
(RACH/FACH)
RRC Connection Establishment in DCH
If the upper layer of UE requests to set up a signaling connection
in IDLE mode (RRC connection does not exist), UE starts RRC
connection set up process. Figure 1 shows establishment of an
RRC connection in dedicated transport channel (DCH) state.


6 Confidential and Proprietary Information of ZTE CORPORATION

FI GURE 1 RRC CONNECTI ON ESTAB L I SHMENT I N DCH
5. Downlink Synchronisation
1. CCCH : RRC Connection Request
3. Radio Link Setup Response
2. Radio Link Setup Request
7. CCCH : RRC Connection Setup
4. ALCAP Iub Data Transport Bearer Setup
9. DCCH : RRC Connection Setup Complete
6. Uplink Synchronization
8. Radio Link Restore Indication
Start RX
Description
Allocate RNTI
Select L1 and L2
parameters
Node B
Serving RNS
UE Serving RNC
Start TX
Description

The RRC Connection establishment procedure in DCH follows the
following steps:
1. The UE initiates set-up of an RRC connection by sending RRC
Connection Request message on CCCH. The information
parameters involve are Initial UE Identity (TMSI, IMSI or
IMEI) and Establishment cause.
2. According to the reason of RRC connection request and
system resource availability, SRNC decides to use a DCH for
this RRC connection and allocates U-RNTI and radio
resources for the RRC connection. When a DCH is to be set-
up, NBAP message Radio Link Setup Request is sent to
Node B. The information parameters involve are Cell id,
Transport Format Set, Transport Format Combination Set,
frequency, UL scrambling code, and Power control
information.
3. Node B allocates resources, starts PHY reception, and
responds with NBAP message Radio Link Setup Response
to SRNC. The information parameters involve are Signaling
link termination, and Transport layer addressing information
(AAL2 address, AAL2 Binding Identity) for the Iub Data
Transport Bearer.
4. SRNC initiates set-up of Iub Data Transport bearer using
ALCAP protocol. This request contains the AAL2 Binding
Identity to bind the Iub Data Transport Bearer to the DCH.

Chapter 1 Basic Signaling flow

The request for set-up of Iub Data Transport bearer is
acknowledged by Node B.
5. The SRNC establishes synchronism for the Iub and Iur Data
Transport Bearer with Node B by means of exchange of the
appropriate DCH Frame Protocol frame, Downlink
Synchronization.
6. The Node B responds with Uplink Synchronization
message. Node B starts DL transmission.
7. Message RRC Connection Setup is sent on CCCH from SRNC
to UE. The information parameters involve are Initial UE
Identity, U-RNTI, Capability update Requirement, Transport
Format Set, Transport Format Combination Set, frequency,
DL scrambling code, and Power control information.
8. Node B achieves uplink sync and notifies SRNC with NBAP
message Radio Link Restore Indication.
9. Message RRC Connection Setup Complete is sent on DCCH
from UE to SRNC. The information parameters involve are
Integrity information, ciphering information, and UE radio
access capability.
RRC Connection Establishment in Common
Transport Channel (RACH/FACH)
The establishment of an RRC connection on the RACH/FACH
common transport channel is shown in Figure 2.
FI GURE 2 RRC CONNECTI ON ESTAB L I SHMENT I N COMMON TRANSPORT
CHANNEL ( RACH/ FACH)

The necessary Iub Data Transport bearer for the RACH/FACH is
established prior to this procedure. The RRC Connection
Establishment procedure in Common Transport Channel
(RACH/FACH) follows the following steps:
1. The UE initiates set-up of an RRC connection by sending RRC
Connection Request message on CCCH. The information
parameters involve are Initial UE Identity, and Establishment
cause.



2. The SRNC decides to use RACH/FACH for this RRC connection
and allocates both U-RNTI and C-RNTI identifiers. Message
RRC Connection Setup is sent on CCCH. The information
parameters involve are Initial UE Identity, U-RNTI, C-RNTI,
Capability update Requirement, and frequency (optionally).
3. UE sends RRC Connection Setup Complete on a DCCH
logical channel mapped on the RACH transport channel. The
information parameters involve are Integrity information,
ciphering information, and UE radio access capability.
NAS Signaling Connection
Establishment
This establishment could be request by the terminal by itself (for
example to initiate a service) or could be stimulated by a paging
from CN.
NAS Signaling Connection establishment is shown in Figure 3.
FI GURE 3 NAS SI GNAL I NG CONNECTI ON ESTAB L I SHMENT

The NAS Signaling Connection Establishment procedure follows
the following steps:
1. RRC Connection establishment process is performed.
2. UE sends RRC Initial Direct Transfer to SRNC. The
information parameters involve are Initial NAS Message (for
GSM based CN, for example, CM Service Request, Location
Update Request etcetera) CN node indicator (it indicates the
correct CN node into which the NAS message shall be
forwarded).
3. SRNC initiates signaling connection to CN, and sends the
RANAP message Initial UE Message. The parameters involve
are NAS PDU (for GSM based CN, for example, CM Service
Request, Location Update Request etcetera), CN domain
indicator (indicating the CN domain towards which this
message is sent).


After these steps, NAS message transfer can use NAS signaling
connection between UE and CN.
RRC Connection Release
Release of RRC connection is in the following two ways:
Release of RRC connection establishment in DCH
Release of RRC connection establishment in common
transport channel (RACH/FACH)
RRC Connection Release in DCH
RRC Connection release of a dedicated channel is shown in
Figure 4.
FI GURE 4 RRC CONNECTI ON REL EASE OF A DEDI CATED CHANNEL
10. Radio Link Deletion Response
8. Radio Link Deletion
9. Radio Link Deletion Response
5. RRC Connection Release Complete
4. RRC Connection Release
Response
7. Radio Link
Deletion
3. ALCAP Iu Bearer
Release
ALCAP Iur Bearer
Release
13. ALCAP Iub Bearer Release
12. ALCAP Iub Bearer Release
1. Iu Release
Command
2. Iu Release
Complete
UE
Node B
Drift
Node B
Serving
Drift
RNC
Serving
RNC
CN



RRC Connection release of a dedicated channel in the case of
macro-diversity on two Node Bs, where first Node B is connected
to SRNC, and the second one to the DRNC, is explained as
follows:
1. CN initiates the release of a dedicated Channel by sending
the message Iu Release Command to the SRNC. The
parameter involve is Cause.
2. The SRNC confirms the release by sending a Iu Release
Complete message to the CN. The parameters include are
Data volume Report (if data volume reporting to PS is
required).
3. SRNC initiates release of Iu Data Transport bearer using
ALCAP protocol.
4. SRNC sends RRC Connection Release message to UE to
initiate the RRC connection release. The parameters involve
is Cause.
5. UE responds with RRC Connection Release Complete
message from SRNC to confirm the RRC connection release.
6. SRNC initiates the release of the link by sending Radio Link
Deletion to Node B (SRNC).
7. SRNC initiates the release of the link by sending Radio Link
Deletion to Drift RNC.
8. Drift RNC initiates the release of the link by sending Radio
Link Deletion to Node B (Drift RNC).
9. Node B (SRNC) confirms the release of the link by sending
Radio Link Deletion Response to SRNC.
10. Node B (Drift RNC) confirms the release of the link by
sending Radio Link Deletion Response to Drift RNC.
11. The Drift RNC confirms the release of the link by sending
Radio Link Deletion Response to SRNC.
12. Node B (SRNC) initiates release of Iub Data Transport bearer
using ALCAP protocol.
13. Node B (Drift RNC) initiates release of Iub Data Transport
bearer using ALCAP protocol.
14. Drift RNC initiates release of Iur Data Transport bearer using
ALCAP protocol.
RRC Connection Release in Common Transport
Channel (RACH/FACH)
RRC Connection release of a common transport channel is shown
in Figure 5.


FI GURE 5 RRC CONNECTI ON REL EASE OF A COMMON TRANSPORT CHANNEL

RRC Connection release of a common transport channel is as
follows:
1. CN initiates the release of a dedicated Channel by sending
the message Iu Release Command to the SRNC. The
parameter involve in this steps is Cause.
2. SRNC confirms the release by sending a Iu Release
Complete message to the CN. The parameter involve is
Data volume Report (if data volume reporting to PS is
required).
3. SRNC initiates release of Iu Data Transport bearer using
ALCAP protocol.
4. SRNC sends RRC Connection Release message to UE to
initiate the RRC connection release. The parameter involve in
this step is Cause.
5. UE responds with RRC Connection Release Complete
message to SRNC to confirm the RRC connection release.
Call Flow
Call Flow in CS Domain
Call setup in CS domain is show in Figure 6.



FI GURE 6 CAL L SETUP I N CS DOMAI N
RNC UE NodeB
1. UL-CCCH:RRC Connection Request (originatingConversationalCall)
2. Radio Link Setup Request
3. Radio Link Setup Response
4. ALCAP:ERQ
5. ALCAP:ECF
6. DL_CCCH:RRC Connection Setup
9. UL_DCCH:Initial Direct Transfer
(CM Service Request)
CN
10. Initial UE Message
(CM Service Request)
11. Direct Transfer
(CM Service Accept)
12. DL_DCCH:Downlink Direct Transfer
(CM Service Accept)
13. UL_DCCH:Uplink Direct Transfer
(Call Setup)
14. RAB Assginment
Request
(Establishment)
15. Radio Link Reconfiguration
Prepare
Ready
17. ALCAP:ERQ
18. ALCAP:ECF
Commit
20. DL_DCCH:Radio Bearer Setup
21. UL_DCCH:Radio Bearer Setup Complete
22. RAB Assignment
Response
(Call Proceeding)
(Alerting)
(Connect)
26. UL_DCCH:Uplink Direct Transfer
(Connect Acknowledge)
(Connect
Acknowledge)
7. UL_DCCH:RRC Connection Setup Complete
8. D_NBAP:Radio Link Restore Indication

Call setup flow in CS domain is described as follows:
1. UE sends the RRC Connection Request message through
the uplink CCCH, requesting for setting up an RRC
connection.
2. Based on the reason for RRC connection request and system
resource status, SRNC decides to set up RRC connection for
UE on the dedicated channel, and allocates RNTI and L1 and
L2 resources. SRNS then sends the Radio Link Setup
Request message to Node B, asking the Node B to allocate
the specified radio link resources required for RRC connection.
3. At the end of successful resource preparation, Node B
returns Radio Link Setup Response to SRNC.


4. With the ALCAP, SRNC originates the setup of Iu interface
user plane transport bearer.
5. At the end of successful terrestrial bearer setup, Node B
returns ECF to SRNC.
6. SRNC sends the RRC Connection Setup message to UE
through the downlink CCCH.
7. UE sends the RRC Connection Setup Complete message
to SRNC through the uplink DCCH. At this time, the RRC
connection setup process ends.
8. At the end of successful synchronization between RNC and
Node B, Node B returns Radio Link Restore Indication to
RNC.
9. The signaling between UE and CN is directly transferred by
RNC. When 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 RNC.
10. After receiving the initial direct transfer message from UE,
RNC sends the SCCP connection request to CN through the
Iu interface, with data as Initial UE Message sent from
RNC to CN. This message contains the message contents
sent from UE to CN.
11. If CN is ready to accept the Connection Request (CR), it
returns the CC SCCP connection confirmation to RNC,
confirming successful signaling connection setup.
12. After RNC is confirmed that the signaling connection is set up
successfully, it sends the downlink direct transfer message to
UE. The Layer-3 message is CM Service Accept.
13. UE sends the uplink direct transfer message, with Layer-3
message as Call Setup.
14. Upon receiving Call Setup Layer-3 message, CN sends RAB
assignment request to UTRAN, asking UTRAN to set up RAB.
15. SRNC maps the QoS parameter of RAB into AAL2 link feature
parameter and radio resource feature parameter. ALCAP of
the Iu interface originates user plane transport bearer setup
of the Iu interface, based on the AAL2 link feature parameter.
At the end of successful terrestrial bearer setup, SRNC sends
the Radio Link Reconfiguration prepare message to Node
B, asking the subordinate Node B to prepare for adding one
or multiple dedicated transport channels, DCH, on the
existing radio link, for bearing RAB.
16. Node B allocates the corresponding resources and sends the
Radio Link Reconfiguration Ready message to the SRNC,
indicating the completion of radio link reconfiguration
preparation.
17. The ALCAP of the Iub interface in SRNC originates the setup
of Iub interface user plane transport bearer.



19. SRNC sends the Radio Link Reconfiguration Commit
message to the subordinate Node B.
20. SRNC sends the Radio Bearer Setup message to UE, asking
for RB setup of RRC protocol.
21. After executing RB setup, UE sends the Radio Bearer Setup
Complete message to SRNC.
22. After receiving this message, SRNC returns the Radio
Access Bearer Assignment Response to CN. At this time,
the RAB setup flow ends.
23. CN sends Call Proceeding Layer-3 message to UE.
24. CN sends Altering Layer-3 message to UE.
25. Upon hook-off, CN sends Connect Layer-3 message to UE.
26. UE sends Connect Ack Layer-3 message to CN.
PDP Activation Flow in PS Domain
Packet Datagram Protocol (PDP) activation flow in PS domain is
shown in Figure 7.


FI GURE 7 PDP ACTI VATI ON FL OW I N PS DOMAI N
RNC UE Node B CN
1. UL_DCCH: Uplink Direct Transfer
(ACT. PDP Context Req)
3. RAB Assginment Request
(Establishment)
4. Radio Link Reconfiguration Prepare
5. Radio Link Reconfiguration Ready
10. Radio Link Reconfiguration Commit
11. DL_DCCH: Radio Bearer Setup
12. UL_DCCH: Radio Bearer Setup Complete
13. RAB Assignment Response
15. DL_DCCH: Downlink Direct Transfer
(ACT. PDP Context Accept)
2. Direct Transfer
(ACT. PDP Context Req)
14. Direct Transfer
(ACT. PDP Context Accept)
8. DTCH_FP: Downlink SYNC
9. DCCH_FP: Uplink SYNC
6. ALCAP - ERQ
7. ALCAP - ECF

PDP activation flow in PS domain is described as follows:
1. UE sends the uplink direct transfer message to RNC, with
Layer-3 message as PDP Context Request.
2. RNC sends the uplink direct transfer message to CN, with
Layer-3 message as PDP Context Request.
3. After receiving the PDP Context Request Layer-3 message,
CN sends the RAB Assignment Request to UTRAN, asking
UTRAN to set up RAB.
4. After receiving the RAB setup request, 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, SRNC sends the Radio
Link Reconfiguration Prepare message to Node B, asking
the subordinate Node B to prepare for adding one or multiple
dedicated transport channels DCH on the existing radio link,
for bearing RAB.
indicating the completed radio link reconfiguration
preparation.



8. RNC sends downlink FP synchronization message to Node B.
9. Node B sends uplink FP synchronization message to RNC.
14.CN sends the PDP Context Accept Layer-3 message to RNC.
15. RNC transfers the PDP Context Accept Layer-3 message to
UE.
Call Flow in PS Domain
Call flow in PS domain is show in Figure 8.


FI GURE 8 CAL L SETUP I N PS DOMAI N
RNC UE NodeB
1. UL_CCCH RRC Connection Request
2. C_NBAP: Radio Link Setup Request
3. C_NBAP: Radio Link Setup Response
4. ALCAP: ERQ
5. ALCAP: ECF
7. 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
CN
12. Initial UE Message
6. DCCH_FP: Downlink SYNC
8. DCCH_FP: Uplink SYNC
15. RAB Assignment Rquest
(Establishment)
13. Direct Transfer
14. Direct Transfer
22. D_NBAP: Radio Link Reconfiguration Commit
23. DL_DCCH: Radio Bearer Setup
24. UL_DCCH: Radio Bearer Setup Complete
25. RAB Assignment Response
20. DTCH_FP: Downlink SYNC
21. DCCH_FP: Uplink
SYNC
18. ALCAP
19. ERQ_ALCAP
ECF
(Iub InterfaceSetup)

Call flow in PS domain is described as follows:
1. UE sends the RRC Connection Request message through
the uplink CCCH, requesting for setting up an RRC
connection.
2. Based on the reason for RRC connection request and system
resource status, SRNC decides to set up RRC connection for
UE on the dedicated channel, and allocates RNT1 and L1 and
L2 resources. SRNS then sends the Radio Link Setup
Request message to Node B, asking the Node B to allocate
the specified radio link resources required for RRC connection.
3. At the end of successful resource preparation, Node B
returns Radio Link Setup Response to SRNC.
4. With the ALCAP, SRNC originates the setup of Iu interface
user plane transport bearer.



6. RNC sends downlink FP synchronization message to Node B.
7. SRNC sends the RRC Connection Setup message to UE
through the downlink CCCH.
8. Node B sends uplink FP synchronization message to RNC.
9. UE sends the RRC Connection Setup Complete message
to SRNC through the uplink DCCH. At this time, the RRC
connection setup process ends.
10. At the end of successful synchronization between RNC and
Node B, Node B returns Radio Link Restore Indication to
RNC.
11. The signaling between UE and CN is directly transferred by
RNC. When 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 RNC.
12. After receiving the initial direct transfer message from UE,
RNC sends the CR SCCP connection request to CN through
the Iu interface, with data as Initial UE Message sent from
RNC to CN. This message contains the message contents
sent from UE to CN.
13. If CN is ready to accept the CR, it returns the CC SCCP
connection confirmation to RNC, confirming successful
signaling connection setup.
14. After RNC is confirmed that the signaling connection is set up
successfully, it sends the downlink direct transfer message to
UE.
15. CN sends the RAB Assignment Request to UTRAN, asking
UTRAN to set up RAB.
16. After receiving the RAB setup request, 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, SRNC sends the Radio
Link Reconfiguration Prepare message to Node B, asking
the subordinate Node B to prepare for adding one or multiple
dedicated transport channels DCH on the existing radio link,
for bearing RAB.
indicating the completed radio link reconfiguration
preparation.


20. RNC sends the downlink FP synchronization message to Node
B.
21. RNC sends the uplink FP synchronization message to Node B.




Ch a p t e r 2
Measurement Procedures

Measurement
UTRAN uses measurement to do some optimization or some
Radio-link Resource Management.
Measurement Control Types
UTRAN may control a measurement in the UE either by
broadcast of SYSTEM INFORMATION and/or by transmitting a
MEASUREMENT CONTROL message.
There are seven types of measurements:
Intra-frequency measurement
Inter-frequency measurement
Inter-Radio Access Technology (RAT) measurement
UE positioning measurement
Traffic Volume measurement
Quality measurement
UE internal measurement
Intra-frequency Measurement
It is related to intra-frequency handover. The measurements
conducted on downlink physical channels at the same frequency
as the active set. A measurement object corresponds to one cell.



Inter-frequency Measurement
It is related to inter-frequency handover. These are the
measurements conducted on downlink physical channels at
frequencies that differ from frequency of the active set and on
downlink physical channels in the active set. A measurement
object corresponds to one cell.
Inter-Radio Access Technology (RAT)
Measurement
It is related to inter-system handover. These are the
measurements conducted on downlink physical channels
belonging to another radio access technology than UTRAN, for
example, GSM. A measurement object corresponds to one cell.
UE positioning Measurement
These are the measurements of UE position.
Traffic Volume Measurement
These are the measurements on uplink traffic volume. A
measurement object corresponds to one cell.
Quality Measurement
These are the measurements of downlink quality parameters, for
example, downlink transport Block Error Rate (BLER). A
measurement object corresponds to one transport channel in
case of BLER.
UE internal Measurement
Measurements of UE transmission power and UE received signal
level.

Chapter 2 Measurement Procedures

Measurement Procedure
Measurement Control
The purpose of the measurement control procedure is to setup,
modify or release a measurement in UE.
The UTRAN may request a measurement by the UE to be setup,
modified or released with a MEASUREMENT CONTROL message,
which is transmitted on the downlink DCCH using AM RLC. The
normal measurement control communication in is shown in
Figure 9.
FI GURE 9 MEASUREMENT CONTROL
UE UTRAN
Measurement Control

The UTRAN should take the UE capabilities into account when a
measurement is requested from the UE.
When a new measurement is created, UTRAN should set the
Measurement identity IE to a value, which is not used for
other measurements. UTRAN may use several Measurement
identity for the same Measurement type. In case of setting
several Measurement identity within a same Measurement
type, the measurement object (or the list of measurement
objects) can be set differently for each measurement with
different Measurement identity.
When a current measurement is modified or released, UTRAN
should set the Measurement identity IE to the value which is
used for the measurement being modified or released. In case of
modifying IEs within a Measurement identity, UTRAN is only
required to indicate modified IEs. The UE continues to use the
current values of IEs that are not modified.
Refer to 3GPP TS 25.331: Radio Resource Control (RRC);
Protocol Specification for details.

Purpose
Initiation



Measurement Report
The purpose of the measurement reporting procedure is to
transfer measurement results from the UE to UTRAN. The
measurement report procedure is shown in Figure 10.
FI GURE 10 MEASUREMENT REPORT
UE UTRAN
Measurement Report

Common Measurement
Common measurements are to measure the common resources
of Node B.
Common Measurement Types
The types of common measurement used in the system are as
follows:
Received Total Wide Band Power
Transmitted Carrier Power
HS-DSCH Required Power
Transmitted carrier power of all codes not used for HS-
PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH transmission
for Cell Portion

Received Total Wideband Power, Transmitted Carrier
Power and Transmitted carrier power of all codes not used
for HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH
transmission Cell Portion serves the following purposes in the
system:
Admission control
Congestion control
Load control
Power control


However, HS-DSCH Required Power is used in the system
only for the following:
Admission control
Congestion control
Load control

Common Measurement Initiation
This procedure is used by a CRNC to request the initiation of
measurements on common resources in a Node B.
The procedure is initiated with a COMMON MEASUREMENT
INITIATION REQUEST message sent from the CRNC to the Node
B using the Node B Control Port.
Upon reception, the Node B shall initiate the requested
measurement according to the parameters given in the request.
The successful communication of Common Measurement
Initiation Procedure is shown in Figure 11.
FI GURE 11 COMMON MEASUREMENT I NI TI ATI ON PROCEDURE
CRNC Node B
Common Measurement Initiation Request
Common Measurement Initiation Response

If the Common Measurement Type IE is not set to SFN-SFN
Observed Time Difference and the SFN Reporting Indicator
IE is set to FN Reporting Required, the SFN IE shall be
included in the COMMON MEASUREMENT REPORT message or in
the COMMON MEASUREMENT RESPONSE message, the latter
only in the case the Report Characteristics IE is set to On
Demand. The reported Cell System Frame Number (SFN) shall be
the SFN at the time when the measurement value was reported
by the layer 3 filter, referred to as point C in the measurement
model (refer to 3GPP TS 25.302: "Services Provided by the
Physical Layer" for more information). If the Common
Measurement Type IE is set to SFN-SFN Observed Time
Difference, the SFN Reporting Indicator IE shall be ignored.



Common Measurement Type
If the Common Measurement Type IE is set to SFN-SFN
Observed Time Difference, then the Node B shall initiate the
SFN-SFN Observed Time Difference measurements between
the reference cell identified by C-ID IE and the neighboring cells
identified by the UTRAN Cell Identifier (UC-Id) IE in the
Neighboring Cell Measurement Information IE.
Report characteristics
The Report Characteristics IE indicates how the reporting of
the measurement shall be performed.
If the Report Characteristics IE is set to On Demand and if
the SFN IE is not provided, the Node B shall return the result of
the requested measurement immediately. If the SFN IE is
provided, it indicates the frame for which the measurement
value shall be provided. The provided measurement value shall
be the one reported by the layer 3 filter, referred to as point C in
the measurement model (refer to 3GPP TS 25.302: Services
Provided by the Physical Layer for more information).
If the Report Characteristics IE is set to Periodic, the Node B
shall periodically initiate a Common Measurement Reporting
procedure for this measurement, with the requested report
frequency. If the Common Measurement Type IE is set to
SFN-SFN Observed Time Difference, all the available
measurement results shall be reported in the Successful
Neighboring Cell SFN-SFN Observed Time Difference
Measurement Information IE in the SFN-SFN Measurement
Value Information IE and the Node B shall indicate in the
Unsuccessful Neighboring Cell SFN-SFN Observed Time
Difference Measurement Information IE all the remaining
neighboring cells with no measurement result available in the
Common Measurement Reporting procedure. If the SFN IE is
provided, it indicates the frame for which the first measurement
value of a periodic reporting shall be provided. The provided
measurement value shall be the one reported by the layer 3
filter, referred to as point C in the measurement model (refer to
3GPP TS 25.302: Services Provided by the Physical Layer for
more information).
Dedicated Measurement
Dedicated measurements are to measure the dedicated
resources of Node B.
On Demand
Periodic


Dedicated Measurement Types
The types of dedicated measurement used in the system are as
follows:
Signal to Interference Ratio (SIR)
SIR Error
Transmitted Code Power
Rx Timing Deviation
Signal to Interference Ratio (SIR)
SIR is used to calculate the channel interference in the system.
Signal to Interference Ratio (SIR) Error
SIR Error is used for the calculation of outer loop power control.
Transmitted Code Power
Transmitted code power is used for the following in the system:
Access control
Dynamic radio bearer control
Dynamic AMR rate control
Rx Timing Deviation
Rx Timing Deviation is used to locate the position of UE in the
cell.
Dedicated Measurement Initiation
This procedure is used by a CRNC to request the initiation of
measurements on dedicated resources in a Node B.
The procedure is initiated with a Dedicated Measurement
Initiation Request message sent from the CRNC to the Node B
using the Communication Control Port assigned to the Node B
Communication Context.
Upon reception, the Node B shall initiate the requested
measurement according to the parameters given in the
Dedicated Measurement Initiation Request message.



The successful communication of Dedicated Measurement
Initiation Procedure is shown in Figure 12.
FI GURE 12 DEDI CATED MEASUREMENT I NI TI ATI ON PROCEDURE
CRNC Node B
Dedicated Measurement Initiation Request
Dedicated Measurement Initiation Response

If the Node B Communication Context ID IE equals the
reserved value All NBCC, the following shall be performed:
This measurement request shall apply for all current and
future Node B Communication Contexts controlled via the
Communication Control Port on which the DEDICATED
MEASUREMENT INITIATION REQUEST message was received.
Otherwise, this measurement request shall apply for the
requested Node B Communication Context ID only.
The measurement request shall be treated as a single
measurement, despite applying to multiple contexts. This
means that it may only be terminated or failed on All NBCC.
The measurement shall be initiated only for those Node B
Communication Contexts handling a mode (3.84 Mcps) for
which the concerned measurement is specified in respective
protocols (refer to 3GPP TS 25.215: Physical layer
Measurements (FDD) for more information). The initiation of
the measurement for a Node B Communication Context may
be delayed until the Reconfiguration Connection Frame
Number (CFN) has elapsed if either a Prepared
Reconfiguration exists or a Prepared Reconfiguration no
longer exists but the Reconfiguration CFN has not yet
elapsed.
If the Dedicated Measurement Object Type is indicated as being
RL in the DEDICATED MEASUREMENT INITIATION REQUEST
message, measurement results shall be reported for all indicated
Radio Links.
If the CFN Reporting Indicator IE is set to FN Reporting
Required, the CFN IE shall be included in the Dedicated
Measurement Report message or in the Dedicated
Measurement Initiation Response message, (the latter only
in the case where Report Characteristics IE is set to On
Demand). The reported CFN shall be the CFN at the time when
the measurement value was reported by the layer 3 filter,
referred to as point C in the respective measurement model
(refer to 3GPP TS 25.302: Services Provided by the Physical
Layer protocol for more information).


RLS in the Dedicated Measurement Initiation Request
message, measurement results shall be reported for all indicated
Radio Link Sets.
ALL RL in the Dedicated Measurement Initiation Request
message, measurement results shall be reported for all current
and future Radio Links within the Node B Communication
Context.
ALL RLS in the Dedicated Measurement Initiation Request
message, measurement results shall be reported for all existing
and future Radio Link Sets within the Node B Communication
Context.
If the Node B was able to initiate the measurement requested by
the CRNC, it shall respond with the Dedicated Measurement
Initiation Response message using the Communication
Control Port assigned to the Node B Communication Context.
The message shall include the same Measurement ID that was
used in the measurement request. The Dedicated
Measurement Initiation Response message shall be sent
even if the initiation is delayed for some Node B Communication
Contexts due to an existing Prepared Reconfiguration or that the
Reconfiguration CFN has not yet elapsed.
Report Characteristics
The Report Characteristics IE indicates how the reporting of
the measurement shall be performed.
If the Report Characteristics IE is set to On Demand and if the
CFN IE is not provided, the Node B shall return the result of the
measurement immediately. If the CFN IE is provided, it
indicates the frame for which the measurement value shall be
provided. The provided measurement value shall be the one
reported by the layer 3 filter, referred to as point C in the
respective measurement model (refer to 3GPP TS 25.302:
Services Provided by the Physical Layer protocol for more
information).
If the Report Characteristics IE is not set to On Demand, the
Node B is required to perform reporting for a dedicated
measurement object, in accordance with the conditions provided
in the Dedicated Measurement Initiation Request message,
as long as the object exists. If no dedicated measurement object
for which a measurement is defined exists anymore, the Node B
shall terminate the measurement locally, that is, without
reporting this to the CRNC.
If the Report Characteristics IE is set to Periodic, the Node B
shall periodically initiate the Dedicated Measurement Report
procedure for this measurement, with the requested report
Response
message
On Demand
Periodic



frequency. If the CFN IE is provided, it indicates the frame for
which the first measurement value of a periodic reporting shall
be provided. The provided measurement value shall be the one
reported by the layer 3 filter, referred to as point C in the
respective measurement model (refer to 3GPP TS 25.302:
Services Provided by the Physical Layer protocol for more
information).
If the Report Characteristics IE is set to Event A, the Node B
shall initiate the Dedicated Measurement Reporting procedure
when the measured entity rises above the requested threshold
and stays there for the requested hysteresis time. If the
Measurement Hysteresis Time IE is not included, the Node B
shall use the value zero for the hysteresis time.
If the Report Characteristics IE is set to Event B, the Node B
when the measured entity falls below the requested threshold
and stays there for the requested hysteresis time. If the
Measurement Hysteresis Time IE is not included, the Node B
shall use the value zero for the hysteresis time.
If the Report Characteristics IE is set to Event C, the Node B
when the measured entity rises by an amount greater than the
requested threshold within the requested time. After having
reported this type of event, the next C event reporting for the
same measurement cannot be initiated before the rising time
specified by the Measurement Change Time IE has elapsed
since the previous event reporting.
If the Report Characteristics IE is set to Event D, the Node B
when the measured entity falls by an amount greater than the
requested threshold within the requested time. After having
reported this type of event, the next D event reporting for the
same measurement cannot be initiated before the falling time
specified by the Measurement Change Time IE has elapsed
since the previous event reporting.
If the Report Characteristics IE is set to Event E, the Node B
when the measured entity rises above the Measurement
Threshold 1 and stays there for the Measurement Hysteresis
Time (Report A).
When the conditions for Report A are met and the Report
Periodicity IE is provided, the Node B shall also initiate the
Dedicated Measurement Reporting procedure periodically.
If the conditions for Report A have been met and the measured
entity falls below the Measurement Threshold 2 and stays
there for the Measurement Hysteresis Time, the Node B shall
initiate the Dedicated Measurement Reporting procedure (Report
B) as well as terminate any corresponding periodic reporting.
If the Measurement Threshold 2 IE is not present, the Node B
shall use the value of the Measurement Threshold 1 IE
Event A
Event B
Event C
Event D
Event E


instead. If the Measurement Hysteresis Time IE is not
included, the Node B shall use the value zero as hysteresis times
for both Report A and Report B.
If the Report Characteristics IE is set to Event F, the Node B
when the measured entity falls below the Measurement
Threshold 1 and stays there for the Measurement Hysteresis
Time (Report A).
When the conditions for Report A are met and the Report
Periodicity IE is provided, the Node B shall also initiate the
Dedicated Measurement Reporting procedure periodically.
If the conditions for Report A have been met and the measured
entity rises above the Measurement Threshold 2 and stays
there for the Measurement Hysteresis Time, the Node B shall
initiate the Dedicated Measurement Reporting procedure (Report
B) as well as terminate any corresponding periodic reporting.
If the Measurement Threshold 2 IE is not present, the Node B
shall use the value of the Measurement Threshold 1 IE
instead.
If the Measurement Hysteresis Time IE is not included, the
Node B shall use the value zero as hysteresis times for both
Report A and Report B.
If at the start of the measurement, the reporting criteria are
fulfilled for any of Event A, Event B, Event E or Event F, the
Node B shall initiate the Dedicated Measurement Reporting
procedure immediately, and then continue with the
measurements as specified in the Dedicated Measurement
Initiation Request message.
Interaction with Reset Procedure
If a measurement has been requested with the Node B
Communication Context ID IE set to All NBCC, the Node B
shall terminate the measurement locally if either the CRNC or
the Node B initiates the Reset procedure for the relevant
Communication Control Port or the entire Node B.
Dedicated Measurement Termination
This procedure is used by the CRNC to terminate a measurement
previously requested by the Dedicated Measurement Initiation
procedure.
The successful Dedicated Measurement Termination procedure is
shown in Figure 13.
Event F
Dedicated
Measurement
Reporting
Procedure for
Events A, B, E
and F



FI GURE 13 DEDI CATED MEASUREMENT TERMI NATI ON PROCEDURE
CRNC Node B
Dedicated Measurement Termination Request

This procedure is initiated with a Dedicated Measurement
Termination Request message, sent from the CRNC to the
Node B using the Communication Control Port assigned to the
Node B Communication Context.
Upon reception, the Node B shall terminate reporting of
dedicated measurements corresponding to the received
Measurement ID IE.
Dedicated Measurement Failure
This procedure is used by the Node B to notify the CRNC that a
measurement previously requested by the Dedicated
Measurement Initiation procedure can no longer be reported.
The Node B is allowed to initiate the Dedicated Measurement
Failure Indication message at any time after having sent the
Radio Link Setup Response message, as long as the Node B
Communication Context exists.
The successful Dedicated Measurement Failure procedure is
shown in Figure 14.
FI GURE 14 DEDI CATED MEASUREMENT FAI L URE PROCEDURE

This procedure is initiated with a Dedicated Measurement
Failure Indication message, sent from the Node B to the CRNC
using the Communication Control Port assigned to the Node B
Communication Context, to inform the CRNC that a previously
requested measurement can no longer be reported. The Node B
has locally terminated the indicated measurement.

Ch a p t e r 3
Handover Procedures

Handover refers to the redistribution of radio resource in mobile
communication system in cell structure, to keep discontinuous
communication of mobile phones when moving a mobile station
from a district to another.
Handover falls into the following two types:
Soft handover
Soft handover of cells within the same Node B (intra-
Node B handover, termed as softer handover)
Soft handover of cells between different Node Bs
Soft handover of cells in same band but between different
RNCs (via Iur interface)
Hard handover
Hard handover between different operators
Hard handover in same operator (forced hard handover)
Hard handover between systems (for example, handover
to GSM)
Soft Handover
The following cases are considered for Soft Handover:
Radio Link Addition (Branch Addition)
Radio link Deletion (Branch Deletion)
Radio link Addition & Deletion (simultaneous Branch Addition
& Deletion)



Radio Link Addition (Branch Addition)
This procedure shows establishment of a radio link via a Node B
controlled by another RNC than the serving RNC.
FI GURE 15 SOFT HANDOVER - RADI O L I NK ADDI TI ON ( BRANCH ADDI TI ON)
6. Radio Link Restore
Indication
ALCAP Iur Bearer Setup 5. ALCAP Iub Bearer Setup
UE
Node B
Drift RNS
Drift
RNC
Serving
RNC
Decision to setup
new RL
1. Radio Link Setup
Request
2. Radio Link Setup
Request
Start RX
Description
3. Radio Link Setup
Response
4. Radio Link Setup
Response
7. Radio Link Restore
Indication
8. Downlink Synchronization
9. Uplink Synchronization
Start RX
Description
10. DCCH: Active Setup
11. DCCH: Active Set Update Complete
[Radio Link Addition]

The radio link addition process is described as follows:
1. SRNC decides to setup a radio link via a new cell controlled
by another RNC. SRNC requests DRNC for radio resources by
sending RNSAP message Radio Link Setup Request. A new
Iur signaling connection is established for the first radio link
via DRNC for UE. This Iur signaling connection will be used
for all RNSAP signaling related to this UE. The information

Chapter 3 Handover Procedures

parameters involve in this process are Cell id, Transport
Format Set per DCH, Transport Format Combination Set,
frequency, and UL scrambling code.
2. If requested resources are available, DRNC sends NBAP
message Radio Link Setup Request to Node B and Node B
starts the UL reception. The information parameters involve
in this process are Cell ID, Transport Format Set per DCH,
Transport Format Combination Set, frequency, and UL
scrambling code.
3. Node B allocates requested resources. Successful outcome is
reported in NBAP message Radio Link Setup Response.
The information parameters involve in this process are
Signaling link termination, Transport layer addressing
information (AAL2 address, AAL2 Binding Identity(ies)) for
Data Transport Bearer(s).
4. DRNC sends RNSAP message Radio Link Setup Response
to SRNC. The information parameters involve in this
process are Transport layer addressing information (AAL2
address, AAL2 Binding Identity) for Data Transport Bearer(s),
and neighboring cell information.
5. SRNC initiates setup of Iur/Iub Data Transport Bearer using
ALCAP protocol. This request contains the AAL2 Binding
Identity to bind the Iub Data Transport Bearer to DCH.
This step gets repeated for each Iur/Iub Data Transport
Bearer to be setup.
6. Node B achieves uplink sync on the Uu and notifies DRNC
with NBAP message Radio Link Restore Indication.
7. In its turn DRNC notifies SRNC with RNSAP message Radio
Link Restore Indication.
8. SRNC establishes synchronism for the Data Transport
Bearer(s) with Node B by means of exchange of the
appropriate DCH Frame Protocol frame Downlink
Synchronization, relative already existing radio link(s).
9. Node B responds with DCH Frame Protocol frame Uplink
Synchronization. Then Node B starts DL transmission.
10. SRNC sends RRC message Active Set Update (Radio Link
Addition) to UE on DCCH. The information parameters
involve in this process are Update type, Cell id, DL
scrambling code, Power control information, Ncell
information.
11. UE acknowledges with RRC message Active Set Update
Complete.
Note: The order of transmission of Radio Link Restore
Indication messages (steps 6 and 7) is not necessarily identical
as shown. These messages could be sent before the ALCAP
bearer setup (step 5) or after the transport bearer
synchronization (steps 8 and 9).



Radio Link Deletion (Branch Deletion)
This procedure shows deletion of a radio link belonging to a
Node B controlled by another RNC than the serving RNC.
Radio Link Deletion (Branch Deletion) procedure is shown in
Figure 16.
FI GURE 16 SOFT HANDOVER - RADI O L I NK DEL ETI ON ( BRANCH DEL ETI ON)

The radio link deletion process is described as follows:
1. SRNC decides to delete a radio link from the old cell
controlled by another RNC. SRNC sends RRC message Active
Set Update (Radio Link Deletion) to UE on DCCH. The
information parameters include Update type, and Cell id.
2. UE deactivates DL reception from old branch, and
acknowledges with RRC message Active Set Update
Complete.
3. SRNC requests DRNC to de-allocate radio resources by
sending RNSAP message Radio Link Deletion Request.
The information parameters include Cell id, and Transport
layer addressing information.


4. DRNC sends NBAP message Radio Link Deletion Request
to Node B. The information parameters include Cell id, and
Transport layer addressing information.
5. Node B de-allocates radio resources. Successful operation is
reported in NBAP message Radio Link Deletion Response.
6. DRNC sends RNSAP message Radio Link Deletion
Response to SRNC.
7. SRNC initiates release of Iur/Iub Data Transport Bearer using
ALCAP protocol.
Hard Handover

Hard Handover
This procedure describes intra-RNC inter-Node B hard handover.
The successful hard handover is shown in Figure 17.
FI GURE 17 I NTRA- RNC I NTER- NODE B HARD HANDOVER

Intra-RNC Inter-Node B Hard Handover is described as follows:



1. SRNC sends Radio Link Setup Request message to the
target Node B.
2. Node B allocates resources, starts PHY reception, and
responds with NBAP message Radio Link Setup Response.
3. Target RNC initiates set-up of Iub Data Transport bearer
using ALCAP protocol. This request contains the AAL2 Binding
Identity to bind the Iub Data Transport Bearer to the DCH.
The request for set-up of Iub Data Transport bearer is
acknowledged by Node B.
4. SRNC sends an RRC message Physical Channel
Reconfiguration to UE.
5. When the UE switches from the old RL to the new RL, the
source Node B detects a failure on its RL and sends an NBAP
message Radio Link Failure Indication to SRNC.
6. Target Node B achieves uplink sync on the Uu and notifies
SRNC with NBAP message Radio Link Restore Indication.
7. When the RRC connection is established with the target Node
B and necessary radio resources have been allocated, the UE
sends RRC message Physical Channel Reconfiguration
Complete to the SRNC.
8. The source RNC sends NBAP message Radio Link Deletion
Request to the source Node B. The information parameters
include Cell id, and Transport layer addressing information.
9. The source Node B de-allocates radio resources. Successful
operation is reported in NBAP message Radio Link Deletion
Response.
10. The source RNC initiates release of Iub Data Transport
bearer using ALCAP protocol.
SRNS Relocation
SRNS Relocation via Iur Interface
Figure 18 shows the SRNS relocation processes


FI GURE 18 SRNS REL OCATI ON VI A I UR I NTERFACE
UE
DRNC SRNC CN
1. Relocation Required
2. Relocation Request
3. Relocation Request Acknowledge
4. Relocation Command
5. Relocation Commit
6. Relocation Complete
7. Iu Release Command
10. Iu Release Complete
8. UTRAN Mobility Information
9. UTRAN Mobility Information Confirm
If there are not RLs of UE in
SRNC, then SRNC can
trigger relocation

The process of SRNS starts with the normal process of hard
handover. The additional signaling is explained as follows:
1. SRNC request RNC to release Iur Data Transport bearer and
upon completion SRNC sends Relocation Required
message to CN.
2. CN sends Relocation Request message to RNC.
3. RNC reply with Relocation Request Acknowledge
message.
4. CN sends Relocation Command to SRNC to start the
relocation process.
5. SRNC forward Relocation Commit message to RNC.
6. RNC gets relocated and acknowledge CN with Relocation
Complete message.
7. Upon completion of relocation, CN asks SRNC to release Iu
with Iu Release Command.
8. RNC sends the relocation information to UE through UTRAN
Mobility Information message.
9. UE confirms the information and replies with UTRAN
Mobility Information Confirm.



10. SRNC informs CN with Iu Release Complete message.
SRNS Relocation not via Iur Interface
When RNC neighboring cell with different frequency does not
have Iur port, hard handover starts with SRNC repositioning.
FI GURE 19 SRNS REL OCATI ON NOT VI A I UR I NTERFACE

The process of SRNS relocation is explained as follows:
1. The source SRNC sends Relocation Required message to
both CN. Upon reception of Relocation Required message
the CN element prepares itself for the switch and may also
suspend user data traffic and/or signaling between UE and
itself for some bearers.
2. On completion of preparation, the CN conveys a Relocation
Request message to the target RNC. The target RNC uses
the UE identifier to link the requests from CN to the
resources (for example Iub links) that the UE is currently
using.
3. DRNC sends Radio Link Setup Request to DNode B.
4. DNode B replies with Radio Link Setup Response message.


5. After the source RNC and the target RNC have completed its
preparation phase, DRNC sends Relocation Request
Acknowledge message to CN.
6. After the CN node is ready for the SRNC move, the CN node
indicates the completion of preparation phase at the CN side
for the SRNS Relocation by sending the Relocation
Command to SRNC.
7. The SRNC prepare for the physical channel and sends
Physical Channel Reconfiguration message to UE.
8. DNode B sends Radio Link Restore Indication message to
DRNC.
9. DRNC detect the relocation and sends Relocation Detect
message to CN.
10. When the RRC connection is established with the target Node
B and necessary radio resources have been allocated, the UE
sends RRC message Physical Channel Reconfiguration
Complete to the DRNC.
11. DRNC forwards Relocation Complete message to CN.
12. CN instruct SRNC to release Iu resource by Iu Release
Command.
13. SRNC sends Radio Link Deletion Request to SNode B.
14. SNode B deletes the radio resource and replies with Radio
Link Deletion Response.
15. SRNC forwards Iu Release Complete message to CN.
CS Inter RAT Hard Handover
3G to 2G Handover Detect
This procedure explains how Hard Handover is performed from
UTRAN to GSM/BSS between a UMTS CN and a 2G-MSC.



FI GURE 20 UTRAN GSM/ BSS HANDOVER
UE
RNC
Serving
CN MSC BSC
1. Relocation
Required
2. Prepare
Handover
3. Handover
Request
4. Handover
Request Ack.
5. Prepare Handover
Response
6. Relocation
Command
7. DCCH: Handover
from UTRAN Command
8. Handover Direct
9. Handover complete
10. Handover
Complete
11. Send End
Signal Request
12. Iu Release
Command
13. Iu Release
Compelte
14. Send End
Signal Response

The procedure of Inter-RAT (3G to 2G) Hard Handover is
explained as follows:
1. Upon detection of a trigger, SRNC sends RANAP message
Relocation Required to the CN.
2. The UMTS CN will forward this request to the GSM MSC
(indicated in the received message) over the MAP/E interface
(MAP message Prepare Handover).
3. MSC and BSC communicate with each other regarding
handover as normal GSM handover operation. MSC sends
Handover Request message to BSC.
4. BSC responds with Handover Request Ack message.


5. Once initial procedures are complete in GSM MSC/BSS the
MSC returns MAP/E message Prepare Handover Response.
6. CN responds to the initial request from SRNC by sending
RANAP message Relocation Command to the SRNC.
7. Via existing RRC connection, SRNC sends RRC message
Handover from UTRAN command to the UE. One or several
message from the other system can be included in this
message. (Procedures related to synchronization etcetera to
GSM BSS are not shown.)
8. BSC sends Handover Detect to UE as normal GSM
procedure.
9. UE responds with Handover Complete as normal GSM
procedure.
10. Detection of the UE within the GSM coverage results in the
MSC sending MAP/E message Send End Signal Request to
the CN.
11. CN initiates release of resources allocated by the former
SRNC (Iu Release Command).
12. Previously allocated bearer resources are released within
UMTS (for example using RANAP and ALCAP protocols) (Iu
Release Complete).
13. Procedure is concluded from UMTS point of view by CN
sending MAP/E message Send End Signal Response (this
message is not sent until the end of the call).
2G to 3G Handover
This procedure explains how Hard Handover is performed from
GSM/BSS to UTRAN between a 2G-MSC and a UMTS CN.



FI GURE 21 GSM/ BSS UTRAN HANDOVER

The procedure of Inter-RAT (2G to 3G) Hard Handover is
explained as follows:
1. The BSC sends Handover Required message to the GSM
MSC.
2. The MSC sends MAP/E message Prepare Handover to the
UMTS CN.
3. The CN sends RANAP message Relocation Request to the
Target RNC.
4. Response Relocation Request Acknowledge is returned
to the CN by the target RNC via RANAP.


5. MAP/E message Prepare Handover Response is sent by
the UMTS CN to the MSC.
6. MSC sends Handover Command to BSC as normal GSM
procedure.
7. BSC responds to the command and sends Handover
Command to UE as normal GSM procedure.
8. When target RNC has detected the UE, Relocation Detect
message is sent to the CN node.
9. When the RRC connection is established with the target RNC
and necessary radio resources have been allocated the UE
sends RRC message Handover to UTRAN Complete to the
target RNC.
10. Once complete the target RNC sends RANAP message
Relocation Complete to the CN.
11. CN sends MAP/E message Send End Signal Request to the
MSC.
12. The MSC sends Clear Command message to the BSC.
13. The BSC responds with Clear Complete message to the
GSM.
14. The MSC sends MAP/E message Send End Signal
Response to the UMTS CN to conclude the procedure (this
message is not sent until the end of the call).
PS Inter RAT Data Handover
GPRS to UMTS Cell Reselection
The UTRAN signaling procedures for GPRS to UTRAN Cell
Reselection is shown in Figure 22.



FI GURE 22 UTRAN SI GNAL I NG PROCEDURES FOR GPRS TO UTRAN CEL L
RESEL ECTI ON

The UTRAN signaling procedures for GPRS to UTRAN Cell
Reselection is as follows:
1. The UE selects a UTRAN cell, examine system information,
and initiates establishment of a NAS signaling connection.
2. The NAS signaling connection between UE and CN can now
be used for NAS message transfer (for example execution of
security functions).
3. After necessary CN-GPRS preparations (for example UE
context information retrieval), CN initiates establishment of
Radio Access Bearer(s).
UMTS to GPRS Cell Reselection
The UMTS to GPRS Cell Reselection is same as the normal
access due to the cell reselection for UE for the case of 2G to 3G
Handover. In the RAB setup process, CN will give PDCP and GTP-
U sequence number. According to these sequence number,
UTRAN configure the user interface, to receive the grouping data
transferred from 2G GPRS.
The UTRAN signaling procedures for UTRAN to GPRS cell
reselection initiated by UE is shown in Figure 23.


FI GURE 23 UTRAN SI GNAL I NG PROCEDURES FOR UTRAN TO GPRS CEL L
RESEL ECTI ON
UE CN Serving RNC
1. Cell Reselection
triggered
2. Iu Release Command
2. Iu Release Complete

The UTRAN signaling procedures for UTRAN to GPRS cell
reselection initiated by UE is as follows:
1. The UE selects a GPRS cell, examine system information, and
initiates establishment of UE-GPRS connection.
2. After necessary CN-GPRS preparations (for example UE
context information retrieval), CN initiates release of Iu
connection. SRNC releases the RRC connection.




Ch a p t e r 4
MBMS Specific
Procedures

MBMS Service Activation
The Multimedia Broadcast and Multicast Service (MBMS) Service
Activation signaling flow is shown in Figure 24.



FI GURE 24 MBMS SERVI CE ACTI VATI ON SI GNAL I NG FL OW
UE DRNC SRNC CN
1. NAS procedure for MBMS Service activation or UE goes to PMM
connected state after previously activating the MBMS service.
UE is camped on a cell served by the DRNC.
2. MBMS UE Linking
Request
3. MBMS UE Linking
Response
4. MBMS Information
Request
5. MBMS Information
Response
No MBMS Service
context in SRNC or
DRNC
6. MBMS Attach
Command
7. Information Exchange
Initiation Request
8. Information Exchange
Initiation Response
9. MBMS Service
context created
10. MBMS Registration Request
11. MBMS Registration Response

UE performs NAS procedure for MBMS Service Activation, or
having activated the service previously, goes into PMM
connected state. UE is in a cell of DRNC. There is no MBMS
context for this service in the DRNC. MBMS Service Activation
signaling procedure is as follows:

Chapter 4 MBMS Specific Procedures

1. The Core Network initiates the MBMS UE Linking procedure
by sending RANAP MBMS UE Linking Request message to
provide the SRNC with the list of MBMS Service IDs activated
by this UE. The information parameters include TMGIs, and
PTP RB id.
2. RNC sends an RANAP MBMS UE Linking Response
message to Core Network after RNC updates the MBMS
Service Context.
3. As the SRNC has no MBMS context for this service, it does
not know the IP Multicast address or APN for this service.
The SRNC request these from the SGSN using the
connectionless RANAP Uplink Information Exchange
Request message. The information parameter is TMGI.
4. SGSN responds with RANAP Uplink Information
Exchange Response message. The information parameter
includes TMGI, IP Multicast Address and APN.
5. UE linking in the DRNC is performed using the RNSAP MBMS
Attach Command message over the Iur interface. The
information parameter is TMGIs.
6. As the DRNC has no MBMS context for this service, it does
not know the IP Multicast Address and APN for this service.
The DRNC request these from the SRNC using the
connectionless RNSAP Information Exchange Initiation
Request message. The information parameter is MBMS
Bearer Service List.
7. SRNC responds with RNSAP Information Exchange
Initiation Response message. The information parameters
include TMGI, IP Multicast Address and APN.
8. An MBMS Service Context for the service is created in the
DRNC.
9. The DRNC informs the Core Network that it would like to
receive MBMS Session Start Request messages by sending
an RANAP MBMS Registration Request message. The
information parameters include Registration Request type,
TMGI, IP Multicast Address, APN, and Global RNC id.
10. Core Network replies with an RANAP MBMS Registration
Response message.
MBMS Session Start
The MBMS Session Start signaling flow is shown in Figure 25.



FI GURE 25 MBMS SESSI ON START SI GNAL I NG FL OW


The RNC decides to perform counting and offer the service over
PTM bearer. If the UE is receiving a lower priority MBMS service
over a PTP bearer and UE capability does not allow reception of
PTP and PTM bearers simultaneously, the MBMS is started as
follows:
1. When the MBMS session starts the SGSN informs all RNCs
that is connected to this SGSN of the availability of data and
requests the establishment of the User plane bearer using
RANAP MBMS Session Start message. This also establishes
the SCCP connection for the MBMS service. The information
parameters include TMGI, Session id, Repetition number,
Bearer Service type, Iu signaling connection id, RAB
parameters, PDP type, Session Duration, Service Area,
Frequency layer convergence flag, Routing Area (RA) list of
idle mode UEs, and Global CN-id.
2. The RNC responds with an RANAP MBMS Session Start
Response message. Since there are UEs in this RNC that
have joined the service, it sets up the RAB for the MBMS
service. The information parameter is Iu transport layer
information.
3. CRNC updates the MICH using NBAP MBMS Notificaiton
Update Command. This message is updated for every
change in MICH. The information parameters include C-ID,
Common Physical Channel ID, Modification Period, MICH CFN,
and NI Information.
4. RNC is in the Service Area for the service. The RNC notifies
the UE(s) about the start of the MBMS service by updating
the RRC MBMS Modified Services Info message on the
MCCH. This is sent on DCCH for UEs in Cell-DCH and on
MCCH for other UEs. The information parameters include
TMGI, Session ID, UE action required, MBMS preferred
frequency, and Continued MCCH reading.
5. RNC takes a decision to perform UE counting in order to
evaluate what is the optimal method for MBMS delivery.
6. RNC requests UE to set up PMM connection using RRC MBMS
Access Info message on MCCH. The information parameters
include TMGI and probability factor.
7. A fraction of (or all) UEs who have joined the MBMS service
establishes PMM connection towards CN. UE linking is done
by the CN when Iu-ps connection is established for these UEs.
8. After counting, CRNC has enough information to make
PTP/PTM decision. In this scenario there were enough UEs to
exceed the threshold to justify PTM transmission.
9. The CRNC establishes the S-CCPCH and FACH which will
carry the MTCH by using the Common Transport Channel
Setup procedure.
10. CRNC informs UE of the MTCH channel used for the MBMS
service in the cell and its neighboring cells using the RRC
MBMS Common P-T-M RB Info, MBMS Current Cell P-T-



M RB Info, MBMS Neighboring Cell P-T-M RB Info
messages on MCCH. The information parameters include
TMGI, MBMS UTRAN Cell Group Identifier, logical channel,
transport channel, physical channel information, and
MSCHInformation per MBMS service.
11.UE is receiving a lower priority MBMS service on a PTP bearer.
UE capability does not allow reception of a PTP and PTM
bearer simultaneously.
12. UE requests the release of the PTP bearer for the other lower
priority service using RRC MBMS Modification Request
message. The information parameter is RB to be released.
13. RNC releases the PTP RB of the other lower priority MBMS
service.
14. MBMS data transmission for this service on the PTM bearer.
15. RNC may request the release of the Iu connection for the
UEs that were moved to PMM connected state during the
counting process.
MBMS UE Mobility from a PTP to
PTM cell
The signaling description of MBMS UE mobility from PTP to PTM
cell is shown in Figure 26.


FI GURE 26 MBMS UE MOB I L I TY FROM A PTP TO PTM CEL L

The signaling description of UE receiving MBMS service over PTP
bearer in SRNC moving into DRNC area where the service is
available over a PTM bearer is described as follows:
1. MBMS Service has been activated and is currently ongoing.
UE is receiving the MBMS traffic using a PTP bearer. SRNC
makes the decision that to add a cell in the DRNC to the
active set. The Cell already has PTM bearer for the MBMS
service.
2. UE Linking is performed via using RNSAP Radio Link Setup
Request message to add the radio link in the new cell. The
information parameter involve is MBMS Bearer Service List.
3. MBMS service context in the DRNC is updated.
4. DRNC responds with RNSAP RL Setup Response message.
The information parameter involve is Active MBMS Bearer
Service List
5. NBAP RL Setup procedure to set up the RL on the NodeB
6. RRC Active Set Update to the UE to add the PTP radio link on
the new cell to the active set.



7. When the cell in the DRNC is good enough to provide MBMS
service to UE, the SRNC deletes the PTP radio bearer. The
RRC Radio Bearer Release message includes the MBMS
RB list released to change transfer mode IE to indicate that
the release is due to transfer mode change, that is PTM
availability. The information parameters include (only MBMS
specific ones listed): MBMS FLC capability, MBMS RB list
released to change transfer mode
8. UE is able now to read information regarding the MBMS
Service on the MCCH and picks up MTCH.
MBMS UE Mobility from PTM cell to
PTP cell
The signaling description of MBMS UE mobility from a PTP to PTM
cell is shown in Figure 27.


FI GURE 27 MBMS UE MOB I L I TY FROM PTM TO PTP CEL L

The signaling description of DRNC PTP transmission when UE
moves from a cell in the SRNC with PTM bearer for the MBMS
service to another cell in the DRNC, is described as follows:
1. MBMS Service has been activated and is currently ongoing.
UE is in URA-PCH state in the DRNC coverage area and is
receiving the MBMS traffic using a PTM bearer. UE performs
cell re-selection to a cell where there is no PTM bearer for
the MBMS service within the same URA.
2. UE reads the RRC Modified Services Info and Unmodified
Services Info messages on MCCH and identifies that there is
no PTM bearer for the service in this cell.
3. UE sends a RRC Cell Update message. The information
parameter is Cause Value set to MBMS reception.
4. DRNC relays the Cell update to the SRNC in RNSAP Uplink
Signaling Transfer Indication message. Since this is the
first access in the DRNC for this UE (UE linking information is



not available in the DRNC), the DRNC cannot include the
channel type indication to the SRNC.
5. SRNC sends MBMS ATTACH COMMAND to create a UE link in
the DRNC, using the connection oriented service of the
signaling bearer. The information parameters include MBMS
Bearer Service List, D-RNTI if UE in Cell_FACH/Cell_PCH or
SRNC-ID+URA-ID if UE in URA-PCH.
6. SRNC sends the RRC Cell Update Confirm message to UE.
7. SRNC sets up PTP bearer for all the ongoing MBMS services
that the user has subscribed to and that the SRNC is not
aware as being offered PTM in the cell. The RNSAP RL
Setup Request message also performs UE linking. UE starts
to receive MBMS service over PTP bearer.
8. DRNC is aware of activated MBMS service(s) for the UE and
sends the connectionless RNSAP MBMS Channel Type
Reconfiguration Indication message indicating PTP bearer
type. This message includes the transmission mode for all
the ongoing UE linked MBMS services. The information
parameters include DRNC-id, C-ID, TMGI, Transmission
mode, and S-RNTI of affected UE.
9. SRNC releases the PTP bearers for those services that it is
now aware as being offered PTM in the cell. UE starts to
receive MBMS service over PTP bearer.
MBMS Session Stop and Service
Termination
The MBMS Session Stop and Service Termination signaling flow
is shown in Figure 28.


FI GURE 28 MBMS SESSI ON STOP AND SERVI CE TERMI NATI ON

The signaling flow of MBMS session end, and followed by a
termination of MBMS service is as follows:
1. In this scenario it is assumed that an MBMS Session is
ongoing with UE in DRNC receiving MBMS service over PTM
bearers.
2. End of MBMS data session.
3. CN invokes RANAP MBMS Session Stop message towards
all RNC that are explicitly or implicitly registered with the CN.
RAB resources and Iu signaling connection are released. The
information parameters include MBMS CN De-registration
4. RNCs send RANAP MBMS Session Stop Response
messages back to SGSN.
5. DRNC as CRNC also update and remove all relevant
information related to the MBMS Service on the MCCH: RRC
Modified Services Info message on MCCH. The information
parameters include TMGI, Release PTM RB, and all RB info on



the PTM bearer for the service on RRC, Common PTM RB Info,
Current Cell PTM RB Info, Neighboring Cell PTM RB Info.
6. UE releases the Radio Bearer for the MBMS service.
7. Iub bearer is released using NBAP Common Transport Bearer
release procedure.
8. MBMS services terminates.
9. SGSN sends a RANAP CN De-Registration Request
message to all RNCs registered with the CN in order to
inform the RNC that a certain MBMS Service is no longer
available. The information parameters include TMGI, and
Global CN-id.
10. RNCs replies with a RANAP CN De-Registration Response
message back to the SGSN.
11. RNCs remove this MBMS service context and detach all UEs
from this service.
RAU during MBMS Session
Routing Area Update (RAU) signaling during MBMS session is
shown in Figure 29.


FI GURE 29 RAU DURI NG MBMS SESSI ON

The signaling flow of RAU during MBMS session is as follows:
1. UE in idle mode receiving MBMS service over PTM crosses RA
boundary.
2. UE moves to connected mode and performs RA update. CN
releases Iu connection on completion of RA update procedure.
If the CN does not release Iu connection immediately, it
must perform UE linking.
3. This is first UE in the RA.
4. Core Network sends an RANAP MBMS Session Update
message to RNC after updating the RA list containing UEs.
The information parameters include Session Update ID and
Delta RA list of Idle mode UEs.
5. RNC responds with RANAP MBMS Session Update
Response message. MBMS Iu bearer was already set up
earlier. The information parameter is Session update Id.
6. RNC sends NBAP MBMS Notification Update Command to
update the MICH in all the cells that is part of both the MBMS
Service Area and one of the RNCs RAs indicated in the RA to
be added List IE, if this IE is included in the Delta RA List of



Idle Mode UEs IE group. The information parameters include
C-ID, Common Physical Channel ID, Modification Period,
MICH CFN and NI Information.
7. SRNC as CRNC updates the MCCH using RRC MBMS
Modified Services Info message on MCCH in all the cells
indicated in step 6 to request UE to establish PMM connection.
As this is the first UE in the RA, the SRNC does not need to
perform counting. The information parameters include MBMS
Transmission id, MBMS Required UE action and Continue
MCCH reading.
8. UE establishes PMM connection. CN performs UE linking.
9. SRNC sets up PTP radio bearer. UE starts to receive data
over PTP radio bearer.

Ch a p t e r 5
High Speed Packet
Access

Physical Shared Channel
Reconfiguration
This procedure is used to assign HS-DSCH and E-DCH related
resources to the Node B.
The Physical Shared Channel Reconfiguration is shown in Figure
30.
FI GURE 30 PHYSI CAL SHARED CHANNEL RECONFI GURATI ON

The procedure is initiated with a Physical Shared Channel
Reconfiguration Request message sent from the CRNC to the
Node B using the Node B Control Port.
Upon reception, Node B activates the new configuration at the
head boundary of SFN according to the parameters given in the
message.
If the Physical Shared Channel Reconfiguration Request
message includes an SFN IE, the Node B shall activate the new
configuration at the head boundary of that specified SFN. If no
SFN IE is included Node B shall activate the new configuration
immediately.



E-DCH and HS-DSCH Resources
The Physical Shared Channel Reconfiguration Request
message includes HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH
and E-HICH Total Power IE. The Node B shall not exceed this
maximum transmission power on all HS-PDSCH, HS-SCCH, E-
AGCH, E-RGCH and E-HICH codes in the cell. If a value has
never been set or if the value of the HS-PDSCH, HS-SCCH, E-
AGCH, E-RGCH and E-HICH Total Power IE is equal to or
greater than the maximum transmission power of the cell the
Node B may use all unused power for HS-PDSCH, HS-SCCH, E-
AGCH, E-RGCH and E-HICH codes.
HS-DSCH Resources
message includes HS-PDSCH And HS-SCCH Scrambling Code,
HS-PDSCH FDD Code Information and HS-SCCH FDD Code
Information IEs.
Node B uses HS-PDSCH And HS-SCCH Scrambling Code
IE as the scrambling code for all HS-PDSCHs and HS-SCCHs.
If a value has never been set, the Node B shall use the
primary scrambling code for all HS-PDSCH and HS-SCCH
codes.
The Node B also sets up, modify or remove HS-PDSCH and
HS-SCCH resources, based on HS-PDSCH FDD Code
Information and HS-SCCH FDD Code Information IEs.
E-DCH Resources
message includes E-AGCH And E-RGCH/E-HICH FDD
Scrambling Code, E-AGCH FDD Code Information and E-
RGCH/E-HICH FDD Code Information IEs.
Node B uses E-AGCH And E-RGCH/E-HICH FDD
Scrambling Code IE as the scrambling code for all E-AGCHs,
E-RGCHs and E-HICHs. If a value has never been set, the
Node B shall use the primary scrambling code for all E-AGCH,
E-RGCH and E-HICH codes.
The Node B also sets up, modify or remove E-AGCH and E-
RGCH/E-HICH resources based on E-AGCH FDD Code
Information and E-RGCH/E-HICH FDD Code
Information IEs.
Physical Shared Channel Reconfiguration Request message
also includes the IEs described in Table 4.

Chapter 5 High Speed Packet Access

TAB L E 4 I ES I NCL UDED I N PHYSI CAL SHARED CHANNEL RECONFI GURATI ON
REQUEST MESSAGE
IE Description
Maximum Target
Received Total Wide
Band Power IE
Node B uses this to control E-DCH
scheduling
Reference Received
Total Wide Band Power
IE
Node B uses this to control E-DCH
scheduling
Target Non-serving E-
DCH to Total E-DCH
Power Ratio IE
Node B performs E-DCH scheduling by
controlling the ratio of received E-DCH
wide band power from non-serving UEs
to the total received E-DCH power
HSPA Serving Cell Change
The intra-RNC inter-Node B cell change procedure is shown in
Figure 31.
FI GURE 31 I NTRA- RNC I NTER- NODE B CEL L CHANGE
UE
Target
Node B
Source
Node B
RNC
Prepare
Ready
Commit
6. Radio Link Reconfiguration Commit
7. Physical Channel Reconfiguration
8. Physical Channe Reconfiguration Complete

The intra-RNC inter-Node B cell change procedure is explained
as follows:



1. The source and target E-DCH cells are controlled by different
Node Bs. RNC requests the source E-DCH Node B to perform
a synchronized radio link reconfiguration using the NBAP
message Radio Link Reconfiguration Prepare, removing
its E-DCH resources for the source E-DCH radio link.
2. The source E-DCH Node B returns a NBAP message Radio
Link Reconfiguration Ready.
3. The RNC requests the target E-DCH Node B to perform a
synchronized radio link reconfiguration using the NBAP
message Radio Link Reconfiguration Prepare, adding E-
DCH resources for the target E-DCH radio link.
4. The target E-DCH Node B returns the NBAP message Radio
Link Reconfiguration Ready.
5. The E-DCH transport bearer to the target E-DCH Node B is
established. The SRNC proceeds by transmitting the RNSAP
message Radio Link Reconfiguration Commit to the RNC.
6. The RNC transmits the NBAP message Radio Link
Reconfiguration Commit to the target E-DCH Node B
including the activation time. At the indicated activation time
the source E-DCH Node B stops and the target E-DCH Node B
starts transmitting on the E-DCH to the UE.
7. RNC transmits Physical Channel Reconfiguration
message to UE.
8. At the indicated activation time the UE stops receiving E-DCH
in the source E-DCH cell and starts E-DCH reception in the
target E-DCH cell. The UE returns RRC message Physical
Channel Reconfiguration Complete to RNC.

A p p e n d i x A
Abbreviations

Abbreviation Full Form
3GPP Third Generation Partnership Project
A
AAL2 ATM Adaptation Layer type 2
AGCH Absolute Grant Channel
ALCAP Access Link Control Application Protocol
AM Acknowledged Mode
AMR Adaptive Multi Rate
APN Access Point Name
B
BLER Block Error Rate
BSC Base Station Controller
BSS Base Station System
C
CCCH Common Control Channel
CCPCH Common Control Physical Channel
CCTrCH Coded Composite Transport Channel
CFN Connection Frame Number
CM Connection Management
CN Core Network
CPICH Common Pilot Channel
CR Connection Request
CRNC Controlling Radio Network Controller
C-RNTI Cell Radio Network Temporary Identifier
CS Circuit Switching
D
DCCH Dedicated Control Channel



DCH Dedicated Channel
DL Downlink
DPCH Dedicated Physical Control Channel
DRNC Drift RNC
DSCH Downlink Shared Channel
E
E-AGCH Enhanced Access Grant Channel
ECF Event Charging Function
E-DCH Enhanced uplink DCH
E-HICH E-DCH HARQ Acknowledgement Indicator Channel
E-RGCH E-DCH Relative Grant Channel
F
FACH Forward Access Channel
FDD Frequency Division Duplex
FLC Frequency Layer Convergence
FN Frame Number
FP Frame Protocol
G
GPRS General Packet Radio System
GPS Global Positioning System
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
H
HARQ Hybrid Automatic Repeat Request
HLR Home Location Register
HSPA High Speed Packet Access
HS-PDSCH High Speed Physical Downlink Shared Channel
HSDPA High Speed Downlink Packet Access
HS-SCCH High Speed Shared Control Channel
HSUPA High Speed Uplink Packet Access
I
IE Information Element
IMEI International Mobile station Equipment Identity
IMSI International Mobile Station Identity
IP Internet Protocol
ISCP Interference Signal Code Power
L

Appendix A Abbreviations

LCR Least Cost Routing
MAP Mobility Application Part
MBMS Multimedia Broadcast/Multicast Service
MCCH MBMS Control Channel
MICH MBMS notification Indicator Channel
MSC Mobile Switching Center
MSCH MBMS Scheduling Channel
MTCH MBMS Traffic Channel
N
NAS Network Access Server
NAS Non-Access Stratum
NBAP Node B Application Part
NBCC Node B Communication Context
NE Network Element
NI Network Identity
P
PCH Paging Channel
PDCP Packet Data Convergence Protocol
PDP Packet Data Protocol
PDSCH Physical Downlink Shared Channel
PDU Packet Data Unit
PHY Physical layer
PMM Packet Mobility Management
PRACH Physical Random Access Channel
PS Packet Switched
PTM Point-to-Multipoint
PTP Point To Point
PUSCH Physical Uplink Shared Channel
Q
QoS Quality of Services
R
RA Routing Area
RAB Radio Access Bearer
RACH Random Access Channel
RANAP Radio Access Network Application Part
RAT Radio Access Technology
RAU Rate Adaptor Unit



RB Radio Bearer
RGCH Relative Grant Channel
RL Radio Link
RLC Radio Link Control
RLS Radio Link Set
RNC Radio Network Controller
RNS Radio Network Subsystem
RNSAP Radio Network Subsystem Application Part
RNTI Radio Network Temporary Identity
RRC Radio Resource Control
RSCP Received Signal Code Power
S
SCCH Synchronization Control Channel
SCCP Signaling Connection Control Part
SFN Cell System Frame Number
SGSN Serving GPRS Support Node
SICH Shared Information Channel
SIR Signal to Interference Ratio
SRNC Serving RNC
SRNS Serving RNS
s-RNTI Serving RNC RNTI
T
TFCI Transport Format Combination Indicator
TMGI Temporary Mobile Group Identity
TMSI Temporary Mobile Subscriber Identity
TSTD Time Switched Transmit Diversity
TUTRAN
U
UE User Equipment
UL Uplink
UM Unacknowledged Mode
UMTS Universal Mobile Telecommunications System
UpPTS Uplink Pilot Timeslot
URA UTRAN Registration Area
U-RNTI UTRAN Radio Network Temporary Identifier
USCH Uplink Shared Channel
UTRAN Universal Terrestrial Radio Access Network

A p p e n d i x B
Figures

Figure 1 RRC Connection Establishment in DCH....................6
Figure 2 RRC Connection Establishment in Common Transport
Channel (RACH/FACH) ........................................................7
Figure 3 NAS Signaling Connection Establishment.................8
Figure 4 RRC Connection Release of a Dedicated Channel ......9
Figure 5 RRC Connection Release of a Common Transport
Channel .......................................................................... 11
Figure 6 Call Setup in CS Domain..................................... 12
Figure 7 PDP Activation Flow in PS Domain........................ 15
Figure 8 Call Setup in PS Domain..................................... 17
Figure 9 Measurement Control ......................................... 23
Figure 10 Measurement Report ........................................ 24
Figure 11 Common Measurement Initiation Procedure......... 25
Figure 12 Dedicated Measurement Initiation Procedure ....... 28
Figure 13 Dedicated Measurement Termination Procedure ... 32
Figure 14 Dedicated Measurement Failure Procedure........... 32
Figure 15 Soft Handover - Radio Link Addition (Branch Addition)
..................................................................................... 34
Figure 16 Soft Handover - Radio Link Deletion (Branch
Deletion)......................................................................... 36
Figure 17 Intra-RNC Inter-Node B Hard Handover .............. 37
Figure 18 SRNS Relocation via Iur Interface....................... 39
Figure 19 SRNS Relocation not via Iur Interface ................. 40
Figure 20 UTRAN GSM/BSS Handover ........................... 42
Figure 21 GSM/BSS UTRAN Handover ........................... 44
Figure 22 UTRAN Signaling Procedures for GPRS to UTRAN Cell
Reselection...................................................................... 46



Figure 23 UTRAN Signaling Procedures for UTRAN to GPRS Cell
Reselection...................................................................... 47
Figure 24 MBMS Service Activation Signaling Flow.............. 50
Figure 25 MBMS Session Start Signaling Flow .................... 52
Figure 26 MBMS UE Mobility from A PTP to PTM cell ............ 55
Figure 27 MBMS UE Mobility from PTM to PTP cell ............... 57
Figure 28 MBMS Session Stop and Service Termination ....... 59
Figure 29 RAU During MBMS Session................................ 61
Figure 30 Physical Shared Channel Reconfiguration ............ 63
Figure 31 Intra-RNC Inter-Node B Cell Change................... 65


Tables

Table 1 Chapter Summary ...................................................i
Table 2 Typographical Conventions ...................................... ii
Table 3 Mouse Operation Conventions .................................. ii
Table 4 IEs Included in Physical Shared Channel
Reconfiguration Request Message ....................................... 65





Index

common channel...................5
Dedicated .......................... 34
dedicated channel .................5
Handover Detect ................. 47
IMEI.............................. 6, 76
IMSI.............................. 6, 76
MBMS Session Start ...... 56, 81
MBMS Session Start Request 55
MBMS Session Stop....... 63, 81
Reconfiguration Request .. 70,
71, 83
Radio Link Failure Indication . 42
RRC connection in DCH..........5
RRC connection set up ...........5
RRC Connection Setup ...........7
System Messages
Active Set Update...... 39, 41
Active Set Update Complete
........................... 40, 41
Altering.......................... 15
Call Proceeding ............... 15
Call Setup ...................... 14
Clear Command .............. 50
Clear Complete ............... 50
CM Service Accept ........... 14
CN De-Registration Request
................................. 65
CN De-Registration Response
................................. 65
Common Transport Channel
Setup......................... 59
Connect ......................... 15
Connect Ack ................... 15
Failure Indication......... 35
Initiation Request . 29, 30,
31, 32, 33
Initiation Response 30, 31
Downlink Synchronization..7,
39
Handover Command ........ 50
Handover Complete ......... 48
Handover Detect ............. 48
Handover from UTRAN ..... 48
Handover Request ........... 48
Handover Request Ack..... 48
Handover Required.......... 49
Handover to UTRAN
Complete ................... 50
Initial Direct Transfer..14, 19
Initial UE Message......14, 19
Iu Release.................10, 12
Iu Release Command.44, 46,
48
Iu Release Complete..10, 12,
45, 46, 48
MBMS Access Info ........... 58
MBMS Attach Command ... 55
MBMS Common P-T-M RB
Info, MBMS Current Cell P-
T-M RB Info, MBMS
Neighboring Cell P-T-M RB
Info........................... 59
MBMS Modification Request
................................ 59
MBMS Modified Services Info
...........................58, 67
MBMS Notificaiton Update
Command .................. 58
MBMS Registration Request
................................ 55
MBMS Session Start......... 58
MBMS Session Start
Response ................... 58
MBMS Session Stop......... 64
MBMS Session Stop
Response ................... 64
MBMS UE Linking Request 55
MBMS UE Linking Response
................................ 55
Modified Services Info.62, 65
NBAP MBMS Notification
Update Command........ 67
PDP Context Accept ......... 17
PDP Context Request ....... 16
Physical Channel
Reconfiguration42, 43, 46,
73
Physical Channel
Reconfiguration Complete
................................ 73
Reconfiguration Request69



Prepare Handover ...... 48, 49
Prepare Handover Response
........................... 48, 50
RAB Assignment Request 16,
19
Radio Access Bearer
Assignment Response . 15,
17, 20
Radio Bearer Setup ... 15, 17,
20
Radio Bearer Setup Complete
......................15, 17, 20
Radio Link Deletion ......... 11
Radio Link Deletion Request
......................41, 43, 46
Radio Link Deletion Response
................ 11, 41, 43, 46
Radio Link Reconfiguration 15
Radio Link Reconfiguration
Commit 15, 17, 20, 72, 73
Prepare ...........16, 19, 72
Ready........ 15, 17, 20, 72
Radio Link Restore Indication
..7, 14, 19, 39, 40, 42, 46
Radio Link Setup Request.. 6,
13, 18, 38, 39, 42, 46, 60
Radio Link Setup Response 6,
14, 34, 39, 42, 46
RANAP MBMS Registration
Response................... 55
RANAP MBMS Session Update
................................ 66
RANAP MBMS Session Update
Response................... 66
RANAP Uplink Information
Exchange Request ....... 55
RANAP Uplink Information
Exchange Response..... 55
Relocation Command. 44, 46,
48
Relocation Commit...........44
Relocation Complete . 44, 46,
50
Relocation Detect ...... 46, 50
Relocation Request44, 46, 50
Relocation Request
Acknowledge...............50
Relocation Required .. 44, 45,
48
RNSAP Information Exchange
Initiation Request ........55
RNSAP Information Exchange
Initiation Response ......55
RNSAP MBMS Channel Type
Reconfiguration Indication
.................................63
RNSAP RL Setup Request..63
RNSAP RL Setup Response 60
RNSAP Uplink Signaling
Transfer Indication.......63
RRC Cell Update ..............62
RRC Cell Update Confirm..63
RRC Connection Release..10,
12
RRC Connection Release
Complete.............. 11, 12
RRC Connection Request6, 8,
13
RRC Connection Setup.. 8, 14
RRC Connection Setup
Complete...........8, 14, 19
RRC Radio Bearer Release.61
Send End Signal Request .48,
50
Send End Signal Response48,
50
Uplink Synchronization. 7, 39
UTRAN Mobility Information
.................................45
TMSI ............................. 6, 78

ZXWR RNC V3!07!300 Radio Network Controller Signaling Description

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXWR RNC V3!07!300 Radio Network Controller Signaling Description

Uploaded by

Copyright:

Available Formats

ZXWR RNC

Radio Network Controller

You might also like