ZXWR RNC (V3.07.300) Radio Network Controller Signaling Description

8/13/2019 ZXWR RNC (V3.07.300) Radio Network Controller Signaling Description

1/82

ZXWR RNCRadio Network Controller

Signaling Description

RNC Version 3.07.300

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900 800-9830-9830Fax: (86) 755 26772236URL: http://support.zte.com.cnE-mail: [email protected]
http://support.zte.com.cn/mailto:[email protected]:[email protected]://support.zte.com.cn/


2/82

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

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

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTECORPORATION 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 theuse 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 ZTECORPORATION 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 sjzl20092915First edition (ZXWR RNC V3.07.300i+ OMMR V3.17.300h +

NetnumenM31 V3.10.410d)


3/82

ZTE CORPORATIONValues Your Comments & Suggestions!

Your opinion is of great value and will help us improve the quality of our productdocumentation and offer better services to our customers.

Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTECORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,Shenzhen, P. R. China 518057.

Thank you for your cooperation!

DocumentName

ZXWR RNC (V3.07.300) Radio Network Controller Signaling Description

Product Version RNCV3.07.300Document RevisionNumber

R1.0

Serial No. sjzl20082915 EquipmentInstallation 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 evaluationof thisdocumentation

Intelligibility:

(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Yoursuggestions forimprovement ofthisdocumentation

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


4/82

This page is intentionally blank.


5/82

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


6/82

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


7/82

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 operationactivities 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:

TA B L E 1 CH A P T E R S UM M ARY

Chapter Summary

Chapter 1, Basic

Signaling flow

Introduces RNC radio signaling. It also

defines NAS and RRC connection setupand Call Flow.

Chapter 2,MeasurementProcedure

Describes about the measurement,measurement control, and common anddedicated measurement procedures.

Chapter 3, HandoverProcedures

Explains soft and hard handover signalingprocedures.


8/82

ZXWR RNC Signaling Description Manual

ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter Summary

Chapter 4, MBMSSpecific Procedures

Describes about MBMS sessionestablishment, mobility and termination.

Chapter 5, High SpeedPacket Access Describes about structure of HSPA andexplains the channel, power, and codeconfiguration of HSPA.

Appendix B,Abbreviations

List of all abbreviations used in the manual

Appendix C, Figuresand Tables

List of all figures and tables used in themanual

Conventions

ZTE documents employ the following typographical conventions.

TA B L E 2 T Y P O G R A P H I C A L C O NVENT I O NS

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, inputfields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screensand company name.

Const ant wi dth Text that you type, program code, files anddirectory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimitedby it.

Note: Provides additional information about acertain topic.

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

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

TA B L E 3 M O USE OP E R A T I O N CO NVENT I O NS

Typeface Meaning

Click Refers to clicking the primary mouse button (usuallythe left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button

TypographicalConventions

MouseOperation

Conventions


9/82

AboutThis 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 andmoving the mouse.

How to Get in Touch

The following sections provide information on how to obtainsupport for the documentation and the software.

If you have problems, questions, comments, or suggestionsregarding your product, contact us by e-mail [email protected]. You can also call our customer supportcenter at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the qualityand usefulness of this document. For further questions,comments, or suggestions on the documentation, you cancontact us by e-mail at [email protected]; or you can fax yourcomments and suggestions to (86) 755 26772236. You can alsobrowse our website at http://support.zte.com.cn, which contains

various interesting subjects like documentation, knowledge base,forum and service request.

CustomerSupport

Documentation

Support


10/82


iv Confidential and Proprietary Information of ZTE CORPORATION



11/82

Confidential and Proprietary Information of ZTE CORPORATION 5

C h a p t e r

1

Basic Signaling flow

Definition of Signaling

The purpose of a communication network is to transferinformation including voice and non-voice information. Therefore,the signaling is the information that needs to be exchangedbetween the devices to enable network devices to coordinatewith 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 byrelated organizations, namely, signaling protocol or signalingmode.

RRC Connection Setup Flow

According to the different reason of RRC connection set up, RRCconnection can be established in common channel or dedicatedchannel. 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 connectionin IDLE mode (RRC connection does not exist), UE starts RRCconnection set up process. Figure1 shows establishment of anRRC connection in dedicated transport channel (DCH) state.


12/82


6 Confidential and Proprietary Information of ZTE CORPORATION

F I G URE 1 RRC C O NNECT I O N ES T A B L I S H M E N T 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 RNSUE Serving RNC

Start TX

Description

The RRC Connection establishment procedure in DCH follows thefollowing steps:

1. The UE initiates set-up of an RRC connection by sending RRCConnection Request message on CCCH. The informationparameters involve are Initial UE Identity (TMSI, IMSI orIMEI) and Establishment cause.

2. According to the reason of RRC connection request andsystem resource availability, SRNC decides to use a DCH forthis RRC connection and allocates U-RNTI and radioresources for the RRC connection. When a DCH is to be set-up, NBAP message Radio Link Setup Request is sent toNode B. The information parameters involve are Cell id,Transport Format Set, Transport Format Combination Set,

frequency, UL scrambling code, and Power controlinformation.

3. Node B allocates resources, starts PHY reception, andresponds with NBAP message Radio Link Setup Responseto SRNC. The information parameters involve are Signalinglink termination, and Transport layer addressing information

(AAL2 address, AAL2 Binding Identity) for the Iub DataTransport Bearer.

4. SRNC initiates set-up of Iub Data Transport bearer usingALCAP protocol. This request contains the AAL2 BindingIdentity to bind the Iub Data Transport Bearer to the DCH.


13/82

Chapter 1 BasicSignaling 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 DataTransport Bearer with Node B by means of exchange of the

appropriate DCH Frame Protocol frame, DownlinkSynchronization.

6. The Node B responds with Uplink Synchronizationmessage. Node B starts DL transmission.

7. Message RRC Connection Setup is sent on CCCH from SRNC

to UE. The information parameters involve are Initial UEIdentity, U-RNTI, Capability update Requirement, TransportFormat 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 DCCHfrom UE to SRNC. The information parameters involve areIntegrity information, ciphering information, and UE radioaccess capability.

RRC Connection Establishment in CommonTransport Channel (RACH/FACH)

The establishment of an RRC connection on the RACH/FACHcommon transport channel is shown in Figure 2.

F I G URE 2 RRC C O NNECT I O N ES T A B L I S H M E N T I N CO M M O N T R A N S P O R TC H A N N E L (RACH/FACH)

The necessary Iub Data Transport bearer for the RACH/FACH is

established prior to this procedure. The RRC ConnectionEstablishment procedure in Common Transport Channel

(RACH/FACH) follows the following steps:

1. The UE initiates set-up of an RRC connection by sending RRCConnection Request message on CCCH. The informationparameters involve are Initial UE Identity, and Establishment

cause.


14/82



2. The SRNC decides to use RACH/FACH for this RRC connection

and allocates both U-RNTI and C-RNTI identifiers. MessageRRC 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 ConnectionEstablishment

This establishment could be request by the terminal by itself (forexample to initiate a service) or could be stimulated by a pagingfrom CN.

NAS Signaling Connection establishment is shown in Figure 3.

F I G URE 3 NA S S I G N A L I N G CO NNECT I O N ES T A B L I S H M E N T

The NAS Signaling Connection Establishment procedure followsthe following steps:

1. RRC Connection establishment process is performed.

2. UE sends RRC Initial Direct Transfer to SRNC. Theinformation parameters involve are Initial NAS Message (forGSM based CN, for example, CM Service Request, LocationUpdate Request etcetera) CN node indicator (it indicates thecorrect CN node into which the NAS message shall beforwarded).

3. SRNC initiates signaling connection to CN, and sends theRANAP message Initial UE Message. The parameters involveare NAS PDU (for GSM based CN, for example, CM ServiceRequest, Location Update Request etcetera), CN domainindicator (indicating the CN domain towards which thismessage is sent).


15/82



After these steps, NAS message transfer can use NAS signaling

connection between UE and CN.

RRC Connection ReleaseRelease 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 inFigure 4.

F I G URE 4 RRC C O NNECT I O N RE L E A S E O F A DE D I C A T E D C H A N N E L

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

Release13. ALCAP Iub Bearer Release

12. ALCAP Iub Bearer Release

1. Iu Release

Command

2. Iu Release

Complete

UENode B

Drift

Node B

Serving

Drift

RNC

Serving

RNCCN


16/82



RRC Connection release of a dedicated channel in the case of

macro-diversity on two Node Bs, where first Node B is connectedto SRNC, and the second one to the DRNC, is explained as

follows:

1. CN initiates the release of a dedicated Channel by sendingthe message Iu Release Command to the SRNC. Theparameter involve is Cause.

2. The SRNC confirms the release by sending a Iu ReleaseCompletemessage to the CN. The parameters include areData volume Report (if data volume reporting to PS isrequired).

3. SRNC initiates release of Iu Data Transport bearer usingALCAP protocol.

4. SRNC sends RRC Connection Release message to UE to

initiate the RRC connection release. The parameters involveis Cause.

5. UE responds with RRC Connection Release Completemessage from SRNC to confirm the RRC connection release.

6. SRNC initiates the release of the link by sending Radio LinkDeletionto Node B (SRNC).

7. SRNC initiates the release of the link by sendingRadio Link

Deletionto Drift RNC.

8. Drift RNC initiates the release of the link by sending RadioLink Deletionto Node B (Drift RNC).

9. Node B (SRNC) confirms the release of the link by sendingRadio Link Deletion Responseto SRNC.

10. Node B (Drift RNC) confirms the release of the link by

sending Radio Link Deletion Responseto Drift RNC.

11. The Drift RNC confirms the release of the link by sendingRadio Link Deletion Responseto SRNC.

12. Node B (SRNC) initiates release of Iub Data Transport bearerusing ALCAP protocol.

13. Node B (Drift RNC) initiates release of Iub Data Transportbearer using ALCAP protocol.

14. Drift RNC initiates release of Iur Data Transport bearer usingALCAP protocol.

RRC Connection Release in Common TransportChannel (RACH/FACH)

RRC Connection release of a common transport channel is shownin Figure 5.


17/82



F I G URE 5 RRC C O NNECT I O N RE L E A S E O F A CO M M O N T R A N S P O R T CH A N N E L

RRC Connection release of a common transport channel is asfollows:

1. CN initiates the release of a dedicated Channel by sendingthe message Iu Release Command to the SRNC. Theparameter involve in this steps is Cause.

2. SRNC confirms the release by sending a Iu ReleaseComplete message to the CN. The parameter involve isData volume Report (if data volume reporting to PS isrequired).

3. SRNC initiates release of Iu Data Transport bearer usingALCAP protocol.

4. SRNC sends RRC Connection Release message to UE toinitiate the RRC connection release. The parameter involve inthis step is Cause.

5. UE responds with RRC Connection Release Completemessage 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.


18/82



F I G URE 6 CA L L SET UP I N CS DO M A I N

RNCUE 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


Commit20. DL_DCCH:Radio Bearer Setup

21. UL_DCCH:Radio Bearer Setup Complete 22. RAB Assignment

Response

23. DL_DCCH:Downlink Direct Transfer(Call Proceeding)

24. DL_DCCH:Downlink Direct Transfer

(Alerting)

25. DL_DCCH:Downlink Direct Transfer

(Connect)

26. UL_DCCH:Uplink Direct Transfer

(Connect Acknowledge) (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 Requestmessage through

the uplink CCCH, requesting for setting up an RRCconnection.

2. Based on the reason for RRC connection request and systemresource status, SRNC decides to set up RRC connection forUE on the dedicated channel, and allocates RNTI and L1 andL2 resources. SRNS then sends the Radio Link Setup

Requestmessage to Node B, asking the Node B to allocatethe specified radio link resources required for RRC connection.

3. At the end of successful resource preparation, Node B

returns Radio Link Setup Responseto SRNC.


19/82



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 Breturns ECF to SRNC.

6. SRNC sends the RRC Connection Setup message to UE

through the downlink CCCH.

7. UE sends the RRC Connection Setup Completemessageto SRNC through the uplink DCCH. At this time, the RRCconnection setup process ends.

8. At the end of successful synchronization between RNC andNode B, Node B returns Radio Link Restore IndicationtoRNC.

9. The signaling between UE and CN is directly transferred byRNC. When RNC receives the first direct transfer message,

that is, Initial Direct Transfer, it sets up the signalingconnection with CN on SCCP. UE sends the Initial DirectTransfer message to RNC.

10. After receiving the initial direct transfer message from UE,RNC sends the SCCP connection request to CN through theIu interface, with data as Initial UE Message sent fromRNC to CN. This message contains the message contentssent from UE to CN.

11. If CN is ready to accept the Connection Request (CR), itreturns the CC SCCP connection confirmation to RNC,confirming successful signaling connection setup.

12. After RNC is confirmed that the signaling connection is set upsuccessfully, 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-3message as Call Setup.

14. Upon receiving Call SetupLayer-3 message, CN sends RABassignment request to UTRAN, asking UTRAN to set up RAB.

15. SRNC maps the QoS parameter of RAB into AAL2 link featureparameter and radio resource feature parameter. ALCAP of

the Iu interface originates user plane transport bearer setupof the Iu interface, based on the AAL2 link feature parameter.At the end of successful terrestrial bearer setup, SRNC sendsthe Radio Link Reconfigurationprepare message to NodeB, asking the subordinate Node B to prepare for adding oneor multiple dedicated transport channels, DCH, on theexisting radio link, for bearing RAB.

16. Node B allocates the corresponding resources and sends theRadio Link Reconfiguration Readymessage to the SRNC,indicating the completion of radio link reconfigurationpreparation.

17. The ALCAP of the Iub interface in SRNC originates the setupof Iub interface user plane transport bearer.


20/82



18. At the end of successful terrestrial bearer setup, Node B

returns ECF to SRNC.

19. SRNC sends the Radio Link Reconfiguration Commitmessage to the subordinate Node B.

20. SRNC sends the Radio Bearer Setupmessage to UE, asking

for RB setup of RRC protocol.

21. After executing RB setup, UE sends theRadio Bearer SetupCompletemessage to SRNC.

22. After receiving this message, SRNC returns the RadioAccess Bearer Assignment Responseto 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 ConnectLayer-3 message to UE.

26. UE sends Connect AckLayer-3 message to CN.

PDP Activation Flow in PS Domain

Packet Datagram Protocol (PDP) activation flow in PS domain isshown in Figure 7.


21/82



F I G URE 7 PDP A CT I VAT I O N F L O W I N PS DO M A I N

RNCUE 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, withLayer-3 message as PDPContext Request.

2. RNC sends the uplink direct transfer message to CN, withLayer-3 message as PDP Context Request.

3. After receiving the PDP Context RequestLayer-3 message,CN sends the RAB Assignment Requestto UTRAN, asking

UTRAN to set up RAB.

4. After receiving the RAB setup request, SRNC maps the QoSparameter of RAB into AAL2 link feature parameter and radio

resource feature parameter. Based on the AAL2 link featureparameter, the ALCAP of the Iu interface originates user

plane transport bearer setup of the Iu interface. At the endof successful terrestrial bearer setup, SRNC sends the Radio

Link Reconfiguration Preparemessage to Node B, askingthe subordinate Node B to prepare for adding one or multiplededicated transport channels DCH on the existing radio link,for bearing RAB.

5. Node B allocates the corresponding resources and sends theRadio Link Reconfiguration Readymessage to the SRNC,indicating the completed radio link reconfigurationpreparation.


22/82



6. The ALCAP of the Iub interface in SRNC originates the setup

of Iub interface user plane transport bearer.


8. RNC sends downlink FP synchronization message to Node B.

9. Node B sends uplink FP synchronization message to RNC.

10. SRNC sends the Radio Link Reconfiguration Commit

message to the subordinate Node B.

11. SRNC sends the Radio Bearer Setupmessage to UE, askingfor RB setup of RRC protocol.

12. After executing RB setup, UE sends the Radio Bearer SetupCompletemessage to SRNC.

13. After receiving this message, SRNC returns the Radio

Access Bearer Assignment Responseto CN. At this time,the RAB setup flow ends.

14.CN sends the PDP Context AcceptLayer-3 message to RNC.

15. RNC transfers the PDP Context AcceptLayer-3 message toUE.

Call Flow in PS Domain

Call flow in PS domain is show in Figure 8.


23/82



F I G URE 8 CA L L SET UP I N PS DO M A I N

RNCUE 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

16. Radio Link Reconfigurat ion Prepare

17. Radio Link Reconfiguration Ready

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 Interface Setup)

Call flow in PS domain is described as follows:

1. UE sends the RRC Connection Requestmessage throughthe uplink CCCH, requesting for setting up an RRCconnection.

2. Based on the reason for RRC connection request and systemresource status, SRNC decides to set up RRC connection forUE on the dedicated channel, and allocates RNT1 and L1 andL2 resources. SRNS then sends the Radio Link SetupRequest 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 Breturns Radio Link Setup Responseto 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.


24/82



6. RNC sends downlink FP synchronization message to Node B.

7. SRNC sends the RRC Connection Setup message to UEthrough the downlink CCCH.

8. Node B sends uplink FP synchronization message to RNC.9. UE sends the RRC Connection Setup Completemessage

to SRNC through the uplink DCCH. At this time, the RRCconnection setup process ends.

10. At the end of successful synchronization between RNC andNode B, Node B returns Radio Link Restore IndicationtoRNC.

11. The signaling between UE and CN is directly transferred byRNC. When RNC receives the first direct transfer message,that is, Initial Direct Transfer, it sets up the signalingconnection 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 throughthe Iu interface, with data as Initial UE Messagesent fromRNC to CN. This message contains the message contentssent from UE to CN.

13. If CN is ready to accept the CR, it returns the CC SCCP

connection confirmation to RNC, confirming successfulsignaling connection setup.

14. After RNC is confirmed that the signaling connection is set upsuccessfully, it sends the downlink direct transfer message to

UE.

15. CN sends the RAB Assignment Requestto UTRAN, askingUTRAN to set up RAB.

16. After receiving the RAB setup request, SRNC maps the QoSparameter of RAB into AAL2 link feature parameter and radioresource feature parameter. Based on the AAL2 link featureparameter, the ALCAP of the Iu interface originates userplane transport bearer setup of the Iu interface. At the endof successful terrestrial bearer setup, SRNC sends the RadioLink Reconfiguration Preparemessage to Node B, askingthe subordinate Node B to prepare for adding one or multiple

dedicated transport channels DCH on the existing radio link,for bearing RAB.

17. Node B allocates the corresponding resources and sends theRadio Link Reconfiguration Readymessage to the SRNC,indicating the completed radio link reconfiguration

preparation.

18. The ALCAP of the Iub interface in SRNC originates the setupof Iub interface user plane transport bearer.



25/82



20. RNC sends the downlink FP synchronization message to Node

B.

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

22. SRNC sends the Radio Link Reconfiguration Commitmessage to the subordinate Node B.

23. SRNC sends the Radio Bearer Setup message to UE, askingfor RB setup of RRC protocol.

24. After executing RB setup, UE sends the Radio Bearer SetupCompletemessage to SRNC.

25. After receiving this message, SRNC returns the Radio

Access Bearer Assignment Responseto CN. At this time,the RAB setup flow ends.


26/82





27/82


C h a p t e r

2

Measurement Procedures

MeasurementUTRAN 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 aMEASUREMENT 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 measurementsconducted on downlink physical channels at the same frequencyas the active set. A measurement object corresponds to one cell.


28/82



Inter-frequency Measurement

It is related to inter-frequency handover. These are the

measurements conducted on downlink physical channels atfrequencies that differ from frequency of the active set and ondownlink physical channels in the active set. A measurementobject corresponds to one cell.

Inter-Radio Access Technology (RAT)Measurement

It is related to inter-system handover. These are themeasurements conducted on downlink physical channelsbelonging 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, forexample, downlink transport Block Error Rate (BLER). Ameasurement object corresponds to one transport channel incase of BLER.

UE internal Measurement

Measurements of UE transmission power and UE received signallevel.


29/82

Chapter 2 MeasurementProcedures


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

F I G URE 9 ME A S U R E M E N T CO NT RO L

UE UTRAN

Measurement Control

The UTRAN should take the UE capabilities into account when ameasurement is requested from the UE.

When a new measurement is created, UTRAN should set theMeasurement identity IE to a value, which is not used forother measurements. UTRAN may use several Measurementidentity for the same Measurement type. In case of settingseveral Measurement identity within a same Measurementtype, the measurement object (or the list of measurement

objects) can be set differently for each measurement withdifferent Measurement identity.

When a current measurement is modified or released, UTRANshould set the Measurement identity IE to the value which isused for the measurement being modified or released. In case ofmodifying IEs within a Measurement identity, UTRAN is only

required to indicate modified IEs. The UE continues to use thecurrent values of IEs that are not modified.

Refer to 3GPP TS 25.331: Radio Resource Control (RRC);

Protocol Specificationfor details.

Purpose

Initiation


30/82



Measurement Report

The purpose of the measurement reporting procedure is to

transfer measurement results from the UE to UTRAN. Themeasurement report procedure is shown in Figure 10.

F I G URE 10 ME A S U R E M E N T R EPO RT

UE UTRAN

Measurement Report

Common MeasurementCommon measurements are to measure the common resourcesof Node B.

Common Measurement Types

The types of common measurement used in the system are asfollows:

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 transmissionfor Cell Portion

Received Total Wideband Power, Transmitted CarrierPowerand Transmitted carrier power of all codes not usedfor HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH

transmission Cell Portionserves the following purposes in thesystem:

Admission control

Congestion control

Load control

Power control


31/82



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 ofmeasurements on common resources in a Node B.

The procedure is initiated with a COMMON MEASUREMENT

INITIATION REQUEST message sent from the CRNC to the NodeB using the Node B Control Port.

Upon reception, the Node B shall initiate the requestedmeasurement according to the parameters given in the request.

The successful communication of Common MeasurementInitiation Procedure is shown in Figure 11.

F I G URE 11 C O M M O N M EASUREM ENT I NI T I AT I O N PRO CEDURE

CRNC Node B

Common Measurement Initiation Request

Common Measurement Initiation Response

If the Common Measurement TypeIE is not set to SFN-SFN

Observed Time Differenceand the SFN Reporting IndicatorIE 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 latteronly 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 reportedby the layer 3 filter, referred to as point C in the measurementmodel (refer to 3GPP TS 25.302: "Services Provided by thePhysical Layer" for more information). If the CommonMeasurement Type IE is set to SFN-SFN Observed Time

Difference, the SFN Reporting IndicatorIE shall be ignored.


32/82



Common Measurement Type

If the Common Measurement Type IE is set to SFN-SFN

Observed Time Difference, then the Node B shall initiate theSFN-SFN Observed Time Differencemeasurements betweenthe reference cell identified by C-IDIE and the neighboring cells

identified by the UTRAN Cell Identifier (UC-Id) IE in theNeighboring Cell Measurement InformationIE.

Report characteristics

The Report Characteristics IE indicates how the reporting ofthe measurement shall be performed.

If the Report CharacteristicsIE is set to On Demandand ifthe SFNIE is not provided, the Node B shall return the result ofthe requested measurement immediately. If the SFN IE isprovided, it indicates the frame for which the measurementvalue shall be provided. The provided measurement value shallbe the one reported by the layer 3 filter, referred to as point C inthe measurement model (refer to 3GPP TS 25.302: ServicesProvided by the Physical Layerfor more information).

If the Report CharacteristicsIE is set to Periodic, the Node B

shall periodically initiate a Common Measurement Reportingprocedure for this measurement, with the requested reportfrequency. If the Common Measurement Type IE is set to

SFN-SFN Observed Time Difference, all the availablemeasurement results shall be reported in the SuccessfulNeighboring Cell SFN-SFN Observed Time DifferenceMeasurement InformationIE in the SFN-SFN Measurement

Value Information IE and the Node B shall indicate in theUnsuccessful Neighboring Cell SFN-SFN Observed TimeDifference Measurement Information IE all the remainingneighboring cells with no measurement result available in theCommon Measurement Reporting procedure. If the SFN IE isprovided, it indicates the frame for which the first measurementvalue of a periodic reporting shall be provided. The providedmeasurement value shall be the one reported by the layer 3

filter, referred to as point C in the measurement model (refer to3GPP TS 25.302: Services Provided by the Physical Layer for

more information).

Dedicated MeasurementDedicated measurements are to measure the dedicatedresources of Node B.

On Demand

Periodic


33/82



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

Dedicated Measurement InitiationThis procedure is used by a CRNC to request the initiation ofmeasurements on dedicated resources in a Node B.

The procedure is initiated with a Dedicated MeasurementInitiation Requestmessage sent from the CRNC to the Node Busing the Communication Control Port assigned to the Node BCommunication Context.

Upon reception, the Node B shall initiate the requestedmeasurement according to the parameters given in theDedicated Measurement Initiation Requestmessage.


34/82



The successful communication of Dedicated Measurement

Initiation Procedure is shown in Figure 12.

F I G URE 12 D EDI CAT ED ME A S U R E M E N T INI T I AT I O N PRO CEDURE

CRNC Node B

Dedicated Measurement Initiation Request

Dedicated Measurement Initiation Response

If the Node B Communication Context ID IE equals the

reserved valueAll NBCC, the following shall be performed:

This measurement request shall apply for all current andfuture Node B Communication Contexts controlled via theCommunication Control Port on which the DEDICATEDMEASUREMENT INITIATION REQUEST message was received.Otherwise, this measurement request shall apply for therequested Node B Communication Context ID only.

The measurement request shall be treated as a singlemeasurement, despite applying to multiple contexts. Thismeans that it may only be terminated or failed onAll NBCC.

The measurement shall be initiated only for those Node B

Communication Contexts handling a mode (3.84 Mcps) forwhich the concerned measurement is specified in respective

protocols (refer to 3GPP TS 25.215: Physical layer Measurements (FDD) for more information). The initiation ofthe measurement for a Node B Communication Context maybe delayed until the Reconfiguration Connection FrameNumber (CFN) has elapsed if either a PreparedReconfiguration exists or a Prepared Reconfiguration nolonger 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 REQUESTmessage, measurement results shall be reported for all indicatedRadio 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 DedicatedMeasurement 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).


35/82




RLS in the Dedicated Measurement Initiation Request

message, measurement results shall be reported for all indicated

Radio Link Sets.

If the Dedicated Measurement Object Type is indicated as beingALL RL in the Dedicated Measurement Initiation Request

message, measurement results shall be reported for all currentand future Radio Links within the Node B CommunicationContext.


ALL RLS in the Dedicated Measurement Initiation Request

message, measurement results shall be reported for all existingand future Radio Link Sets within the Node B CommunicationContext.

If the Node B was able to initiate the measurement requested by

the CRNC, it shall respond with the Dedicated MeasurementInitiation Response message using the CommunicationControl Port assigned to the Node B Communication Context.The message shall include the same Measurement ID that wasused in the measurement request. The DedicatedMeasurement Initiation Response message shall be senteven if the initiation is delayed for some Node B CommunicationContexts 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 ofthe measurement shall be performed.

If the Report CharacteristicsIE is set to On Demand and if the

CFN IE is not provided, the Node B shall return the result of themeasurement immediately. If the CFN IE is provided, it

indicates the frame for which the measurement value shall beprovided. The provided measurement value shall be the one

reported by the layer 3 filter, referred to as point C in therespective 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 dedicatedmeasurement object, in accordance with the conditions providedin the Dedicated Measurement Initiation Requestmessage,as long as the object exists. If no dedicated measurement objectfor which a measurement is defined exists anymore, the Node Bshall terminate the measurement locally, that is, withoutreporting this to the CRNC.

If the Report CharacteristicsIE 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


36/82



frequency. If the CFN IE is provided, it indicates the frame for

which the first measurement value of a periodic reporting shallbe 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 moreinformation).

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 thresholdand stays there for the requested hysteresis time. If theMeasurement Hysteresis TimeIE is not included, the Node Bshall use the value zero for the hysteresis time.

If the Report CharacteristicsIE is set to Event B, the Node B


when the measured entity falls below the requested thresholdand stays there for the requested hysteresis time. If theMeasurement Hysteresis TimeIE is not included, the Node Bshall use the value zero for the hysteresis time.

If the Report CharacteristicsIE is set to Event C, the Node B

shall initiate the Dedicated Measurement Reporting procedurewhen the measured entity rises by an amount greater than therequested threshold within the requested time. After having

reported this type of event, the next C event reporting for thesame measurement cannot be initiated before the rising time

specified by the Measurement Change Time IE has elapsedsince the previous event reporting.

If the Report CharacteristicsIE is set to Event D, the Node B

shall initiate the Dedicated Measurement Reporting procedurewhen the measured entity falls by an amount greater than the

requested threshold within the requested time. After havingreported this type of event, the next D event reporting for thesame measurement cannot be initiated before the falling timespecified by the Measurement Change Time IE has elapsedsince 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 1and stays there for the Measurement HysteresisTime(Report A).

When the conditions for Report A are met and the ReportPeriodicity 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 measuredentity falls below the Measurement Threshold 2 and staysthere for the Measurement Hysteresis Time, the Node B shallinitiate the Dedicated Measurement Reporting procedure (ReportB) as well as terminate any corresponding periodic reporting.

If the Measurement Threshold 2IE 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


37/82



instead. If the Measurement Hysteresis Time IE is not

included, the Node B shall use the value zero as hysteresis timesfor both Report A and Report B.

If the Report CharacteristicsIE is set to Event F, the Node B

shall initiate the Dedicated Measurement Reporting procedurewhen the measured entity falls below the MeasurementThreshold 1and stays there for the Measurement HysteresisTime(Report A).

When the conditions for Report A are met and the ReportPeriodicity IE is provided, the Node B shall also initiate theDedicated Measurement Reporting procedure periodically.

If the conditions for Report A have been met and the measuredentity rises above the Measurement Threshold 2 and staysthere for the Measurement Hysteresis Time, the Node B shallinitiate the Dedicated Measurement Reporting procedure (Report

B) as well as terminate any corresponding periodic reporting.

If the Measurement Threshold 2IE is not present, the Node Bshall use the value of the Measurement Threshold 1 IE

instead.

If the Measurement Hysteresis Time IE is not included, theNode 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 arefulfilled for any of Event A, Event B, Event E or Event F, theNode B shall initiate the Dedicated Measurement Reportingprocedure immediately, and then continue with the

measurements as specified in the Dedicated MeasurementInitiation Requestmessage.

Interaction with Reset Procedure

If a measurement has been requested with the Node BCommunication Context ID IE set toAll NBCC, the Node B

shall terminate the measurement locally if either the CRNC orthe Node B initiates the Reset procedure for the relevantCommunication Control Port or the entire Node B.

Dedicated Measurement Termination

This procedure is used by the CRNC to terminate a measurementpreviously requested by the Dedicated Measurement Initiationprocedure.

The successful Dedicated Measurement Termination procedure isshown in Figure 13.

Event F

DedicatedMeasurement

Reporting

Procedure for

Events A, B, Eand F


38/82



F I G URE 13 D EDI CAT ED ME A S U R E M E N T TERM I NAT I O N PRO CEDURE

CRNC Node B

Dedicated Measurement Termination Request

This procedure is initiated with a Dedicated MeasurementTermination Request message, sent from the CRNC to theNode B using the Communication Control Port assigned to the

Node B Communication Context.

Upon reception, the Node B shall terminate reporting ofdedicated measurements corresponding to the receivedMeasurement IDIE.

Dedicated Measurement Failure

This procedure is used by the Node B to notify the CRNC that ameasurement previously requested by the DedicatedMeasurement Initiation procedure can no longer be reported.

The Node B is allowed to initiate the Dedicated MeasurementFailure Indication message at any time after having sent theRadio Link Setup Responsemessage, as long as the Node BCommunication Context exists.

The successful Dedicated Measurement Failure procedure isshown in Figure 14.

F I G URE 14 D EDI CAT ED ME A S U R E M E N T FA I L UR E PRO CEDURE

This procedure is initiated with a Dedicated MeasurementFailure Indicationmessage, sent from the Node B to the CRNCusing the Communication Control Port assigned to the Node B

Communication Context, to inform the CRNC that a previouslyrequested measurement can no longer be reported. The Node B

has locally terminated the indicated measurement.


39/82


C h 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 discontinuouscommunication of mobile phones when moving a mobile stationfrom 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 differentRNCs (via Iur interface)

Hard handover

Hard handover between different operators

Hard handover in same operator (forced hard handover)

Hard handover between systems (for example, handoverto GSM)

Soft HandoverThe 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)


40/82



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.

F I G URE 15 SO F T HA NDO V ER - RA D I O L I N K A DDI T I O N (B R A N C H A DDI T I O N )

6. Radio Link Restore

Indication

ALCAP Iur Bearer Setup5. ALCAP Iub Bearer Setup

UENode B

Drift RNS

Drift

RNCServing

RNC

Decision to setup

new RL

1. Radio Link Setup

Request

2. Radio Link SetupRequest

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 controlledby another RNC. SRNC requests DRNC for radio resources by

sending RNSAP message Radio Link Setup Request. A newIur signaling connection is established for the first radio linkvia DRNC for UE. This Iur signaling connection will be used

for all RNSAP signaling related to this UE. The information


41/82

Chapter 3 HandoverProcedures


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 Requestto Node B and Node Bstarts the UL reception. The information parameters involvein this process are Cell ID, Transport Format Set per DCH,

Transport Format Combination Set, frequency, and ULscrambling code.

3. Node B allocates requested resources. Successful outcome isreported in NBAP message Radio Link Setup Response.The information parameters involve in this process are

Signaling link termination, Transport layer addressinginformation (AAL2 address, AAL2 Binding Identity(ies)) forData Transport Bearer(s).

4. DRNC sends RNSAP message Radio Link Setup Responseto SRNC. The information parameters involve in thisprocess 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 BindingIdentity to bind the Iub Data Transport Bearer to DCH.

This step gets repeated for each Iur/Iub Data TransportBearer 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 TransportBearer(s) with Node B by means of exchange of theappropriate DCH Frame Protocol frame DownlinkSynchronization,relative already existing radio link(s).

9. Node B responds with DCH Frame Protocol frame UplinkSynchronization. Then Node B starts DL transmission.

10. SRNC sends RRC message Active Set Update (Radio Link

Addition) to UE on DCCH. The information parametersinvolve in this process are Update type, Cell id, DLscrambling code, Power control information, Ncellinformation.

11. UE acknowledges with RRC message Active Set Update

Complete.

Note: The order of transmission of Radio Link RestoreIndicationmessages (steps 6 and 7) is not necessarily identicalas shown. These messages could be sent before the ALCAPbearer setup (step 5) or after the transport bearer

synchronization (steps 8 and 9).


42/82



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.

F I G URE 16 SO F T HA NDO V ER - RA D I O L I N K DE L E T I O N (B R A N C H DE L E T I O N)

The radio link deletion process is described as follows:

1. SRNC decides to delete a radio link from the old cellcontrolled by another RNC. SRNC sends RRC message ActiveSet Update (Radio Link Deletion) to UE on DCCH. Theinformation parameters include Update type, and Cell id.

2. UE deactivates DL reception from old branch, andacknowledges with RRC message Active Set Update

Complete.

3. SRNC requests DRNC to de-allocate radio resources bysending RNSAP message Radio Link Deletion Request.

The information parameters include Cell id, and Transportlayer addressing information.


43/82



4. DRNC sends NBAP message Radio Link Deletion Request

to Node B. The information parameters include Cell id, andTransport 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 DeletionResponseto SRNC.

7. SRNC initiates release of Iur/Iub Data Transport Bearer usingALCAP protocol.

Hard Handover

Hard Handover

This procedure describes intra-RNC inter-Node B hard handover.The successful hard handover is shown in Figure 17.

F I G URE 17 INT RA -RNC I NT ER -NO DE B HA R D HA N DO V ER

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


44/82



1. SRNC sends Radio Link Setup Request message to the

target Node B.

2. Node B allocates resources, starts PHY reception, andresponds 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 BindingIdentity to bind the Iub Data Transport Bearer to the DCH.The request for set-up of Iub Data Transport bearer isacknowledged by Node B.

4. SRNC sends an RRC message Physical ChannelReconfigurationto UE.

5. When the UE switches from the old RL to the new RL, thesource Node B detects a failure on its RL and sends an NBAPmessage Radio Link Failure Indicationto SRNC.

6. Target Node B achieves uplink sync on the Uu and notifiesSRNC with NBAP message Radio Link Restore Indication.

7. When the RRC connection is established with the target NodeB and necessary radio resources have been allocated, the UEsends RRC message Physical Channel ReconfigurationCompleteto the SRNC.

8. The source RNC sends NBAP message Radio Link Deletion

Request to the source Node B. The information parametersinclude Cell id, and Transport layer addressing information.

9. The source Node B de-allocates radio resources. Successfuloperation is reported in NBAP message Radio Link Deletion

Response.

10. The source RNC initiates release of Iub Data Transportbearer using ALCAP protocol.

SRNS Relocation

SRNS Relocation via Iur Interface

Figure 18shows the SRNS relocation processes


45/82



F I G URE 18 SRNS RE L O C A T I O N V I A I UR I NT ERF ACE

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 inSRNC, then SRNC can

trigger relocation

The process of SRNS starts with the normal process of hardhandover. The additional signaling is explained as follows:

1. SRNC request RNC to release Iur Data Transport bearer and

upon completion SRNC sends Relocation Requiredmessage to CN.

2. CN sends Relocation Requestmessage to RNC.

3. RNC reply with Relocation Request Acknowledgemessage.

4. CN sends Relocation Command to SRNC to start therelocation process.

5. SRNC forward Relocation Commit message to RNC.

6. RNC gets relocated and acknowledge CN with Relocation

Completemessage.

7. Upon completion of relocation, CN asks SRNC to release Iuwith Iu Release Command.

8. RNC sends the relocation information to UE through UTRANMobility Informationmessage.

9. UE confirms the information and replies with UTRAN

Mobility Information Confirm.


46/82



10. SRNC informs CN with Iu Release Complete message.

SRNS Relocation not via Iur Interface

When RNC neighboring cell with different frequency does nothave Iur port, hard handover starts with SRNC repositioning.

F I G URE 19 SRNS RE L O C A T I O N N O T V I A IU R I NT ERF ACE

The process of SRNS relocation is explained as follows:

1. The source SRNC sends Relocation Requiredmessage toboth CN. Upon reception of Relocation Requiredmessagethe CN element prepares itself for the switch and may alsosuspend user data traffic and/or signaling between UE and

itself for some bearers.

2. On completion of preparation, the CN conveys a RelocationRequestmessage to the target RNC. The target RNC usesthe UE identifier to link the requests from CN to the

resources (for example Iub links) that the UE is currentlyusing.

3. DRNC sends Radio Link Setup Requestto DNode B.

4. DNode B replies with Radio Link Setup Response message.


47/82



5. After the source RNC and the target RNC have completed its

preparation phase, DRNC sends Relocation RequestAcknowledgemessage 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 sidefor the SRNS Relocation by sending the RelocationCommandto SRNC.

7. The SRNC prepare for the physical channel and sendsPhysical Channel Reconfigurationmessage to UE.

8. DNode B sends Radio Link Restore Indicationmessage toDRNC.

9. DRNC detect the relocation and sends Relocation Detectmessage to CN.

10. When the RRC connection is established with the target Node

B and necessary radio resources have been allocated, the UEsends RRC message Physical Channel ReconfigurationCompleteto the DRNC.

11. DRNC forwards Relocation Completemessage to CN.

12. CN instruct SRNC to release Iu resource by Iu Release

Command.

13. SRNC sends Radio Link Deletion Requestto SNode B.

14. SNode B deletes the radio resource and replies with RadioLink Deletion Response.

15. SRNC forwards Iu Release Completemessage to CN.

CS Inter RAT Hard Handover

3G to 2G Handover Detect

This procedure explains how Hard Handover is performed fromUTRAN to GSM/BSS between a UMTS CN and a 2G-MSC.


48/82



F I G URE 20 UTRAN GSM /BSS HA NDO V ER

UERNC

ServingCN MSC BSC

1. RelocationRequired

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 ReleaseCommand

13. Iu Release

Compelte

14. Send End

Signal Response

The procedure of Inter-RAT (3G to 2G) Hard Handover isexplained as follows:

1. Upon detection of a trigger, SRNC sends RANAP messageRelocation Requiredto 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 messagePrepare Handover).

3. MSC and BSC communicate with each other regarding

handover as normal GSM handover operation. MSC sendsHandover Requestmessage to BSC.

4. BSC responds with Handover Request Ackmessage.


49/82



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 sendingRANAP message Relocation Commandto the SRNC.

7. Via existing RRC connection, SRNC sends RRC message

Handover from UTRAN command to the UE. One or severalmessage from the other system can be included in thismessage. (Procedures related to synchronization etcetera toGSM BSS are not shown.)

8. BSC sends Handover Detect to UE as normal GSMprocedure.

9. UE responds with Handover Complete as normal GSMprocedure.

10. Detection of the UE within the GSM coverage results in the

MSC sending MAP/E message Send End Signal Requesttothe CN.

11. CN initiates release of resources allocated by the formerSRNC (Iu ReleaseCommand).

12. Previously allocated bearer resources are released within

UMTS (for example using RANAP and ALCAP protocols) (IuRelease Complete).

13. Procedure is concluded from UMTS point of view by CNsending MAP/E message Send End Signal Response(thismessage is not sent until the end of the call).

2G to 3G Handover

This procedure explains how Hard Handover is performed fromGSM/BSS to UTRAN between a 2G-MSC and a UMTS CN.


50/82



F I G URE 21 GSM /BSS UTRAN HA ND O VE R

The procedure of Inter-RAT (2G to 3G) Hard Handover isexplained as follows:

1. The BSC sends Handover Required message to the GSMMSC.

2. The MSC sends MAP/E message Prepare Handover to theUMTS CN.

3. The CN sends RANAP message Relocation Request to theTarget RNC.

4. Response Relocation Request Acknowledge is returnedto the CN by the target RNC via RANAP.


51/82



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

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 Detectmessage is sent to the CN node.

9. When the RRC connection is established with the target RNCand necessary radio resources have been allocated the UEsends RRC message Handover to UTRAN Completeto thetarget RNC.

10. Once complete the target RNC sends RANAP messageRelocation Completeto the CN.

11. CN sends MAP/E message Send End Signal Requestto theMSC.

12. The MSC sends Clear Commandmessage to the BSC.

13. The BSC responds with Clear Complete message to the

GSM.

14. The MSC sends MAP/E message Send End SignalResponse 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 CellReselection is shown in Figure 22.


52/82



F I G URE 22 UTRAN S I G N A L I N G PRO CEDURES F O R GPRS T O UTRAN CE L LR ESEL ECT I O N

The UTRAN signaling procedures for GPRS to UTRAN CellReselection 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 ofsecurity functions).

3. After necessary CN-GPRS preparations (for example UEcontext information retrieval), CN initiates establishment ofRadio Access Bearer(s).

UMTS to GPRS Cell Reselection

The UMTS to GPRS Cell Reselection is same as the normalaccess 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 datatransferred from 2G GPRS.

The UTRAN signaling procedures for UTRAN to GPRS cell

reselection initiated by UE is shown in Figure 23.


53/82



F I G URE 23 U T R A N S I G N A L I N G PRO CEDURES F O R UTRAN T O GPRS CE L LR E S E L E C T I O N

UE CNServing RNC

1. Cell Reselection

triggered

2. Iu Release Command

2. Iu Release Complete

The UTRAN signaling procedures for UTRAN to GPRS cellreselection initiated by UE is as follows:

1. The UE selects a GPRS cell, examine system information, andinitiates establishment of UE-GPRS connection.

2. After necessary CN-GPRS preparations (for example UEcontext information retrieval), CN initiates release of Iuconnection. SRNC releases the RRC connection.


54/82





55/82


C h a p t e r

4

MBMS SpecificProcedures

MBMS Service Activation

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


56/82



F I G URE 24 M B M S SERVI CE A CT I VAT I O N S I G N A L I N G FL O W

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 PMMconnected state. UE is in a cell of DRNC. There is no MBMScontext for this service in the DRNC. MBMS Service Activationsignaling procedure is as follows:


57/82

Chapter 4 MBMSSpecific Procedures


1. The Core Network initiates the MBMS UE Linking procedure

by sending RANAP MBMS UE Linking Requestmessage toprovide 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 doesnot know the IP Multicast address or APN for this service.The SRNC request these from the SGSN using theconnectionless RANAP Uplink Information Exchange

Requestmessage. The information parameter is TMGI.

4. SGSN responds with RANAP Uplink InformationExchange Response message. The information parameter

includes TMGI, IP Multicast Address and APN.

5. UE linking in the DRNC is performed using the RNSAP MBMSAttach Command message over the Iur interface. Theinformation parameter is TMGIs.

6. As the DRNC has no MBMS context for this service, it doesnot know the IP Multicast Address and APN for this service.The DRNC request these from the SRNC using theconnectionless RNSAP Information Exchange InitiationRequest message. The information parameter is MBMSBe

ZXWR RNC (V3.07.300) Radio Network Controller Signaling Description

Documents